QUOTE(luther349 @ Jul 12 2011, 06:58 PM)
the kernel is one step 1 of like 40. everything else needs updating to fatx video drivers etc. you can keep patching the broken fatx in 2,6 all you liek its still broken your still using a very old xorg and and alisa and cant run on non cromwell boxes.
An Xbox-Native Linux + Xbox-Native installer (Xebian, GentooX, etc) will probably take some serious effort.
To get any "standard" 2.6-based Linux running on an Xbox, however, your best bet is to do a "Cross-Installation" -- drop the hard drive into a real PC, perform the installation there, boot into the installed Linux, and (finally) install the Xbox-Linux kernel into /boot and create a suitable linux boot menu for Cromwell/Xromwell. Once that's done, drop the hard drive into your Xbox and cross your fingers.
Modern 2.6 distributions are usually configured with a small (100 Megs or so) /boot partition formatted as ext2 for maximum compatibility (Cromwell/Xromwell see ext2 just fine). The main Linux Root partition can be formatted in the filesystem of your choice as long as your kernel (and initrd) have support for that filesystem. I used to use ext3fs for XFedora.
ALSA should work fine, though you'll probably need to pass a module option to the sound driver to get it into the correct mode. 'Same as always.
Xorg will probably run if you configure it to use a FrameBuffer driver such as vesafb. If you're serious about doing Native 3D, have a look at the nvidia driver in xorg -- it's much improved over what we had 5 years ago, and may be a better candidate for patching into supporting the Xbox GPU than what we had back then.
FatX.. is definitely in need of a rewrite. The Linux Kernel unified the msdos/fat drivers, in a way that begs for someone to jump in and add an extension driver to handle FatX. It's not impossible do do -- just a lot of painfully tedious work and research on information that isn't documented anywhere except "in the code".
The best bet to get a working FATX driver running for 2.6 is to grab Xbox-Linux source at the 2.4 level, and reverse-engineer (diff-compare and document) the FATX extensions. If I recall, everything about FATX is in the /fs/fatx directory, and they have equivalents in /fs/fat or /fs/msdos.
The closer you can get to Gimli's first working FATX driver checkin, compared against the Linux Kernel version that he based those files upon would be ideal, as that's the minimum set of changes. As the Linux Kernel revisions go higher, the FATX driver (being 'frozen') lags behind, and ends up picking up more diffs against /fs/msdos and /fs/fat that really came from the Linux Upstream.
The original FATX driver was literally just variable and constant name changes to avoid naming collisions when compiling the kernel. Beyond that, it was a handful of hooks when FATX "Magic Constants" are found.
-LaleeThis post has been edited by lalee: Jul 15 2011, 08:55 AM