I really wanna know what caused this. Doing a Google search on this topic gives thousands of results but aren't of any help.

I'm on ZipSlack, the most recent one, downloaded from /slackware-current/ (so its 10.0). What I did was compiled a 2.6.7 kernel *after configuring it properly* and did all the necessary procedures. This because Slackware still uses the 2.4.26 kernel that's running in my compie right now (I could recover my OS) and I wanted to go 2.6.x.

So when I boot ZipSlack, I use loadlin.exe from DOS, and just pass "root=/dev/hda5" (the root partition). Then "rw". Everything works with 2.4.x, but when I replace vmlinuz with my newly compiled one, this happens. The kernel panics and the whole thing gets stuck there.

Like I already said I think the configuration was proper. The only thing I remember compiling as a module was my sound card and APM my old computer uses so I can modprobe it and shutdown my machine. Filesystems, harddrive stuff etc. were compiled to the kernel.

So... what is it? What did I do wrong?

Regards,
Bamse

This may or may not help but did you include a support for initrd support in your kernel? If you included support for initrd and you didnt make an initrd.2.6.7.img in your /boot partition, it may be causing problems.

Also your filesystem cannot be module or else you'll need a init ram disk.

Sorry if this doesnt help,
Tux

Yeah that's what causes it, I guess.

So I need
this .

It's tough to remember your kernel configuration by heart. But I guess the config is still stored in the folder for the kernel source is/was, or? Maybe I included initrd support, maybe not.

My filesystem is not a module, is compiled to the kernel.

About the boot partition... I'm not quite sure about that since ZipSlack doesn't have partitions. So if I put initrd in /boot, will it be able to find it? I hope so...

How about the init= option, do I need that then?

This thread belongs to the Slackware forum...

Thanks...

Regards,
Bamse

Conclusion: I guess I can't run 2.6.x kernel on ZipSlack unless I compile it myself and use some quirky tweaks to get it working with a umsdos filesystem. I grabbed the generic 2.6.7 kernel with modules and all the stuff from the Slackware FTP but it doesn't work with ZipSlack. Am I right when I say that the precompiled kernel can't be used with ZipSlack? I think I should get a real operating system -- only if I had CD-RW.

Regards,
Bamse