Print

[jrbush82]

I'm attempting to compile the latest version of the kernel (2.4.32) with the 2.4.32 xbox linux patch, however anytime I get it compiled and move it over to the xbox, I get a kernel panic after the init file is executed.  From what I can tell it runs everything in the init file, (nothing works - I get mount errors which confuses me because fatx support is compiled in) then gives the kernel panic.

If you would like a copy of my .config (kernel config used for compiling), let me know and I'll e-mail it to you.  I would also be happy to use someone elses (save me a headache) if you don't mind sharing a 2.4.32 working .config.  My e-mail is [email protected]

[Keo-Keo]

What distro are you compiling?

Did you make sure you added the modules in to that distro?

Are you useing a compressed filesystem such as cloop? If so did you add cloop?

[jrbush82]

QUOTE(Keo-Keo @ Feb 25 2006, 12:40 AM)

What distro are you compiling?

Did you make sure you added the modules in to that distro?

Are you useing a compressed filesystem such as cloop? If so did you add cloop?

Using slackware to build kernel, then loading into xmugen for testing.

I compiled everything into the kernel, so no modules, but I did check and CONFIG_BLK_DEV_LOOP is configured for yes since I'm using an initrd image for fs.  Would you like me to send you a copy of my .config?

[friedgold]

QUOTE(jrbush82 @ Feb 25 2006, 12:11 PM)

Using slackware to build kernel, then loading into xmugen for testing.

I compiled everything into the kernel, so no modules, but I did check and CONFIG_BLK_DEV_LOOP is configured for yes since I'm using an initrd image for fs.  Would you like me to send you a copy of my .config?

Do you know if the initrd ever gets mounted? If not what filesystem does your initrd use and do you have this filesystem compiled into the kernel (If you are using the initrd that comes with xmugen I think you'll need ext2 compiled in).

If the initrd is being mounted OK and the mount errors are to do with fatx do you have support for the Xbox's partitioning system compiled in? Is /dev setup correctly (if you are not using devfs you need to make sure the correct device nodes are available in /dev, if you are using devfs you need to make sure it is mounted correctly over /dev and you are using the correct device names).

If you are after a working .config there's one included in a 'minilinux' I put together a few months back which can be downloaded here. The config is for 2.4.31 but I can't imagine too much has changed since.

[jrbush82]

QUOTE(friedgold @ Feb 25 2006, 01:16 PM)

Do you know if the initrd ever gets mounted? If not what filesystem does your initrd use and do you have this filesystem compiled into the kernel (If you are using the initrd that comes with xmugen I think you'll need ext2 compiled in).

If the initrd is being mounted OK and the mount errors are to do with fatx do you have support for the Xbox's partitioning system compiled in? Is /dev setup correctly (if you are not using devfs you need to make sure the correct device nodes are available in /dev, if you are using devfs you need to make sure it is mounted correctly over /dev and you are using the correct device names).

If you are after a working .config there's one included in a 'minilinux' I put together a few months back which can be downloaded here. The config is for 2.4.31 but I can't imagine too much has changed since.

I checked the image and it has all the devices already in the dev directory, maybe since I have dev enabled in the kernel that is what is screwing things up?  I definately have ext2 support (which is being used to mount the image) and fatx support compiled in, so maybe thats why it can't find anything because the dev support compiled in.  I'll remove that and give it a shot.

[jrbush82]

Well taking out dev support worked like a charm.  My next question regards output.  Right now, the 2.4.31 kernel that came with xmugen (I think agl5 took it from another release and just used it, not sure with one though) shows very little output, while mine shows every flippin thing for the dmesg.  How can I make the minimal like 2.4.31?

[friedgold]

QUOTE(jrbush82 @ Feb 25 2006, 08:56 PM)

Well taking out dev support worked like a charm.  My next question regards output.  Right now, the 2.4.31 kernel that came with xmugen (I think agl5 took it from another release and just used it, not sure with one though) shows very little output, while mine shows every flippin thing for the dmesg.  How can I make the minimal like 2.4.31?

Do you have quiet in the append line of the linuxboot.cfg? If not add it.

[jrbush82]

This is great, thanks for that.  Not what the other kernel does because it shows little output rather than none, however when I pass the quiet option, I notice the following error:

PCI: Failed to allocated resource 2((8000000-(7ffffff) for 01:00.0
agpgart: Unsupported NVIDIA chipset (device id: 02a5), you might want to boot with agp=try_unsupported

Should I pass the agp=try_unsupported, or did I do something wrong in the compiling of the kernel?

[bollywood]

QUOTE(jrbush82 @ Feb 26 2006, 02:43 AM)

This is great, thanks for that.  Not what the other kernel does because it shows little output rather than none, however when I pass the quiet option, I notice the following error:

PCI: Failed to allocated resource 2((8000000-(7ffffff) for 01:00.0
agpgart: Unsupported NVIDIA chipset (device id: 02a5), you might want to boot with agp=try_unsupported

Should I pass the agp=try_unsupported, or did I do something wrong in the compiling of the kernel?

you added devfs=mount line in linuxboot.cfg i think i added slackware kermels 2.6.15 and 2.4.21
and modules at sxb project site you could try thoes.Good to see others doing kernels,hence
in the nex sxb release i add full kernel src and dev stuff so people can now be able to compile
there own kernels and modules when needed,All you do is with sxb-stacker stick in pc or xbox
and you can compile kernels modules on the fly just by using sxb-stacker as a livecd.Its best
to stick sxb iso in pc as we have more memory so its quick.
When i need to add new modules etc to sxb,i use my sxb-stacker iso and i am not sure people
know this sxb iso can run in memory on pc add the command copy2ram method.
i have 1 gb memory on my pc and this new sxb-stacker i done is largest sxb yet at over 2gb
compressed on a 640 mb cd.So yes i run this on pc using xbox sxb kernel as livecd copied
straight in to memory 640 mb memory hence very fast and i compile sxb in memory on pc
using my own sxb iso.I only have to add some graphics and change some stuff.
Then i release new sxb-stacker and then people like you doing kernels to test etc can do so
using sxb-stacker as a livecd or sxb modular installed on win or linux xbox and in memory
only on pc with 1gb mem plus.
good luck.
bollywood.

[jrbush82]

QUOTE(bollywood @ Feb 26 2006, 09:31 AM)

you added devfs=mount line in linuxboot.cfg i think i added slackware kermels 2.6.15 and 2.4.21
and modules at sxb project site you could try thoes.Good to see others doing kernels,hence
in the nex sxb release i add full kernel src and dev stuff so people can now be able to compile
there own kernels and modules when needed,All you do is with sxb-stacker stick in pc or xbox
and you can compile kernels modules on the fly just by using sxb-stacker as a livecd.Its best
to stick sxb iso in pc as we have more memory so its quick.
When i need to add new modules etc to sxb,i use my sxb-stacker iso and i am not sure people
know this sxb iso can run in memory on pc add the command copy2ram method.
i have 1 gb memory on my pc and this new sxb-stacker i done is largest sxb yet at over 2gb
compressed on a 640 mb cd.So yes i run this on pc using xbox sxb kernel as livecd copied
straight in to memory 640 mb memory hence very fast and i compile sxb in memory on pc
using my own sxb iso.I only have to add some graphics and change some stuff.
Then i release new sxb-stacker and then people like you doing kernels to test etc can do so
using sxb-stacker as a livecd or sxb modular installed on win or linux xbox and in memory
only on pc with 1gb mem plus.
good luck.
bollywood.

My original problem with nothing working on boot was because I compiled devfs support into the kernel when it wasn't needed, not that I had passed the option to use devfs via linuxboot.cfg.  With the exception of the agpgart error, everything is working well with the kernel.  I think its just a matter of turning that option  off so that it doesn't try to use the NVIDIA chipset in the kernel, which I'll do tonight after I get home from work.

I'm not actually using sxb, I'm using Slack 10.2 on an old 1ghz system to do all of this, and its working out well so far.  Since sxb is currently using the 2.4.31 kernel, I can send you the 2.4.32 kernel and my .config once I recompile and get rid of that last error if you'd like, that way you can update sxb with a newer kernel.

[bollywood]

QUOTE(jrbush82 @ Feb 26 2006, 05:58 PM)

My original problem with nothing working on boot was because I compiled devfs support into the kernel when it wasn't needed, not that I had passed the option to use devfs via linuxboot.cfg.  With the exception of the agpgart error, everything is working well with the kernel.  I think its just a matter of turning that option  off so that it doesn't try to use the NVIDIA chipset in the kernel, which I'll do tonight after I get home from work.

I'm not actually using sxb, I'm using Slack 10.2 on an old 1ghz system to do all of this, and its working out well so far.  Since sxb is currently using the 2.4.31 kernel, I can send you the 2.4.32 kernel and my .config once I recompile and get rid of that last error if you'd like, that way you can update sxb with a newer kernel.

HI,thanks but i already done sxb kernel 2.4.32 and 2.6.15 4 weeks ago.I was asking you
if you need slackware xbox kernel use sxb  2.4.32 kernel latest or latest 2,6.15
i added these weeks back if people neede at sxb project site,

So if you have any problems compiling kernel 2.4.32 just download kernel 2.4.32 sxb kernel

i do not upgrade sxb just because new kernel come out i like to add extra ideas and things

other wise i would have released sxb with 2.4 32 kernel long ago I  added sxb kernel

at sxb site for people if they need to upgrade sxb to newer kernel they can do so by building

an new lib module with newer kernels i placed in project site.

The new sxb-stacker i am finishing already was build with new latest kernels 2.4.32
three weeks back i  am wating for newer version of slackware 1.03 coming out soon
as sxb latest is 1.02
ok good luck

[alg5]

QUOTE(jrbush82 @ Feb 25 2006, 09:56 PM)

Well taking out dev support worked like a charm.  My next question regards output.  Right now, the 2.4.31 kernel that came with xmugen (I think agl5 took it from another release and just used it, not sure with one though) shows very little output, while mine shows every flippin thing for the dmesg.  How can I make the minimal like 2.4.31?

the bzImage i used in xmugen is compiled by myself. in order to have minimal output, i commented out all the non relevant output. so the user has still informative output and the errors are still displayed (in case there are some). so it s better than quiet because with quiet if it hangs for some user, you don't know why.