ShALLaX.com Forums

no, a relative path is not possible... the loader has to init and load the fatx filesystem itself since it takes over the system... AFAIK it doesnt know its own path, and its not possible for it to do so.

Ok, it seems that it is broken... I have confirmed... now to try and fix it. I have been pouring over the kernel changelogs for things that may have affected the boot process, and I stumbled across a few things that I think may have affected it... Author: Linus Torvalds <torvalds@g5.osdl.org> Date: ...

your correct about the boot.cfg... it is a hardcoded value. Honestly I dont know about 480p, I run in native mode... The gentoox starts in 640x480, but once linux starts booting I am pretty certain that there isn't anything to stop linux from switching modes... the loader shouldn't make a difference...

Excellent work!!!

I am currently working at getting the 2.6.17 kernel to boot... but when I get a chance I will have a look at this.

Ok... now I know I can build a kernel that boots... I am going to attempts a 2.6.17.13 kernel from kernel.org. I just patched it with the 2.6.17.7 patch, no failures... so looks like I am good to go. BTW: I am doing all this from work... so I wont be able to watch the box boot... just hope it all co...

I have a question... the problem with the 128 MB RAM; is that related to the loader (xbeboot) or to the configuration of xDSL itself? BTW, I did try using xromwell again and it just crashed the XBox since the dash was set to 480p. That's just an infuriating bug... I'm surprised no one ever fixed th...

It booted!!!!

It must be somthing with compiling it on a different machine with a different cpu... hrmmm

I am finally getting somewhere

As I write this, I am compiling a 2.6.16 kernel on the xbox using the following procedure... Downloaded the 2.6.16 kernel from kernel.org. Downloaded the 2.6.16 patch from sourceforge. decompressed the kernel... decompressed the patch... ran "patch -p1 < thepatch..." copied kernel.config t...

true, just pointing out that gentoox is an excellent starting point for a clean/fast system.

adding it is not hard... just get the kernel source from the reposotory... and do a "make menuconfig", turn the option on, and compile. then just emerge the iptables tools set the proxy to your xbox... or to make it transparent (better in my opinion)... do the following. I said it was only...

no, if a drive dies on the same chain as the other hdd, and its critical that the system doesnt crash, it will still crash.. on a seperate chain, the worst that will happen is that controller will lockup, and linux will flag it as bad and stop tryng to use it... no "oops"... no corruption....

sorry, didnt look and was bored @ work.

orochi wrote:[Edit]
Rereading my post, if the ide is bad my solution would not work

lol, now i think about it... i agree cant boot with no CD drive

Oh, to reduce overhead even more... I am looking at using DirectFB...
And I dont like Freevo either (its basically just a variant of MythTV IMO)...

if anybody has any suggestions, let me know.

also for the sake of others... loopback installs are slow... just run top to see how much processor time is devoted to the loopback process.