Print

[luther349]

i finnly found all the files to make this work but i will be diving bliend into this. hears hopin

[luther349]

55 views i guess people still care. well i had to get a old distro to compile the kernel. now i gotta figure out how to move it to a new distro.

[Red_Breast]

It looks like you'd like to hear from somebody. So here goes.
I think I like the idea of what you're doing but I can't tell because I'm having trouble understanding your posts.
Another case of dyslexia? - it seems like loads of people suffer from it these days.

[lawdawg0931]

Dsl is a very handy, easy to use program....so any update of that or similar Linux distro for xbox is always a welcome thing. I myself just cannot say "Goodbye" to the 'ole Xbox.

[ldotsfan]

I see 2 options:
1. Remaster Puppy into a compatible filesystem that your kernel supports.
2. Use an older version of Squashfs, I had luck compiling Squashfs 2.2 against stock 2.4.32 kernel before applying xbox linux patches. http://sourceforge.n...m2/files/LBA48/ Yes, the sequence of applying patches matters. The xbox linux patch may fail at certain thunks and I manually edited the points of failure to merge in the changes.

When working on xdsl, I hit a wall with cloop and only one single version of cloop will compile cleanly with my patched kernel.

Good luck on your endeavours with Puppy.

[ldotsfan]

The 2.4.32 kernel tarball was uploaded to the link I gave above. I started with 2.4.32 which was the last version in xbox linux CVS before moving onto 2.4.37.9. I didn't write the 2.4.37.9 patch as well. Shallax from Gentoox did. I merely applied his 2.4.37 patch against the 2.4.37.9 tree knowing that in general the mainline kernel don't usually make changes affecting the xbox linux patches.

The failed thunks wasn't something complicated hence I was able to merge in the changes. You probably can do a diff of your kernel tree against mine to see the differences.

[luther349]

well i finnly got it to compile lol. now to try and get it to run. attempt one remaster cd with new vmlinz.

[luther349]

puppy did not like that at all but im sure its a mistake i made. i never have been good at this sort of stuff granted i did pupeee 4 but that was mostly just binary patching no recompiling. isotsfan you relly should grab lucid pup and the devx file for it. also install the older gcc manually they don't conflict just when compiling the kernel use CC=gcc-2.95. it may be a squish fs problem being it uses 4 i dunno. puppy it pretty easy to turn into a full c environment boot cd download devx file put in /mnt/home reboot save session somewhere cdrw to a hdd whatever go to the boot manager in system add devx to it reboot again saving its a dev puppy version after that. you can do it on a fill hdd install to put then you cant remove the files by removing devx from the boot manager. making the distro bigger then it needs to be.

i relly wish 2.6 and fatx where stable. if 2.6 was stable i could use the woof builder to completely compile a new puppy with whatever kernel i wanted as well as all the other xbox patches. but it uses gcc 4 and 2.4 will not compile with that.

[ldotsfan]

What's the error message? You can remove the silent flag in linuxboot.cfg to see the boot messages. Even a kernel panic error message will help.

[ldotsfan]

2.6.22 cannot boot and I don't know why and 2.6.18 FATX is broken. I managed to cause a kernel oops just by deleting a file from the FATX partition.

Instead of moving forward on the versions, I guess we have to move backwards. IMHO there are no real issues using an older version of squashfs. You still have the remastering option which I suggested a few posts back.

[luther349]

yes i tried to remaster with the 2.4 kernel it crashed.