On Sun, 2001-09-16 at 06:01, Aquarion wrote: > On Fri, 14 Sep 2001 22:40:06 +0200, in linux.debian.user you wrote: > > >On Fri, 2001-09-14 at 14:28, Nicholas Avenell wrote: > >> > >> Scsi support was one of the main reasons I decided to get a new kernel. > >> Also for the USB Filesystem and other neatocool things, > > > >What arguments are you passing to the kernel at boot time? > > None at all, for either kernel > > >> > > >> >> > >> >> I've compiled the newest kernel, 2.4.9 (Actually, I tried this for > >> 2.4.6 > >> > > >> >snip > >> > > >> >> > >> >> However. > >> >> > >> >> Every time I boot into the new kernel, it gets as far as running the > >> >> autodetect on the IDE chain (Which it does sucessfully) and then says: > >> >> > >> >> invalid operand 0000 > >> >> > >> >> (Whole string of hex and other associated stuff, see below) > >> >> > >> >> Kernel Panic: Attempted to kill init. > >> *snip* > >> > > >> >Can you reboot with the old kernel or is the new hardware blocking any > >> >successfull boot? > >> > >> I can reboot fine with the old (2.2.17) kernel, and am doing so > >> > >Ok. That means it's a software issue in the new kernel at least. > > *nod* And the kernel compiles cleanly. > How likely is this to be something I've misselected in menuconfig? And > how would I find out what it is if I have?
I guess I'd try looking at the IDE compilation options, I'd try and put in as much IDE stuff as modules as I could (not the disk support if you boot from it) and then load and inspect as I went after a succesful reboot. Does the kernel find the SCSI system incidentally when it starts? --mike
