Problems with new kernel (2.6.23.14)

l0rddarkf0rce · 01-22-2008, 05:55 PM

Here are the vitals on the system

Dell Latitude D820
Slack 12.0 (configured with encrypted FS using Eric's, aka Alien, instructions)
Kernel huge-smp-2.6.21.5
HD: SATA 160GB

Everything is working OK, but I want the system to be a bit less bloated. I compile the new kernel no error messages or anything. First time I forgot to enable the SCSI devices for the box so I couldn't read the drive. Then since I did not know exactly which one I would need I built all of them into the kernel. I know it breaks the definition of less bloated, but the idea was to get the system to boot and then get rid of un-needed junk be removing SCSI drivers until it broke.

I created my initrd and everything but the system refuses to boot. just before I get prompted by my luks password I get the following messages:

Code:

Can't open device: /dev/sda3
mount: mounting cryptroot on /mnt failed
ERROR: No /sbin/init found on rootdev (or not mounted).  Trouble ahead.
Kernel panic - not syncing: Attempted to kill init!

How can I find exactly which one of all of the SCSI drivers will I need. I went as far as building every single one of them into the kernel to no avail.

Any ideas will be appreciated.

oddo · 01-22-2008, 07:04 PM

As far as I know you need to compile your kernel with your SATA drivers as module, and with mkinitrd make a image that include support for ext3/reiserfs. Also don't forget to include this image in lilo.conf.

Not quite sure about this...

randomsel · 01-22-2008, 07:33 PM

try booting back with the default huge kernel and see if it works.

Is / being mounted? I had a similar problem where the computer couldn't find /sbin/init. Turns out I had to redo initrd with the -r option, and edit /etc/fstab location for my root dir.

l0rddarkf0rce · 01-22-2008, 10:57 PM

Quote:

Originally Posted by randomsel

try booting back with the default huge kernel and see if it works.

Old Kernel still works just fine. I just enabled all of the SATA devices. And I'm compiling as I type.

Quote:

Originally Posted by randomsel

Is / being mounted? I had a similar problem where the computer couldn't find /sbin/init. Turns out I had to redo initrd with the -r option, and edit /etc/fstab location for my root dir.

Is / being mounted? That is the question. Why would the location of /sbin/init change?

l0rddarkf0rce · 01-23-2008, 12:28 AM

My last 2 tries did not work (enable all of the SATA devices, and do a make oldconfig).

still the same problem. going back to the drawing board.

Carpo · 01-23-2008, 04:51 AM

after recompiling the kernel did you make a initrd - adding the modules for the sata drives and crypto stuff ? also did you add this to lilo ?

Ilgar · 01-23-2008, 06:04 AM

In case you haven't noticed, for crypto stuff you will need

Multiple devices driver support (RAID and LVM) --->
<*> Device mapper support
<*> Crypt target support

(this one took me some time to figure out when I was compiling my minimalist kernel

).

l0rddarkf0rce · 01-23-2008, 07:31 AM

Quote:

Originally Posted by Carpo

after recompiling the kernel did you make a initrd - adding the modules for the sata drives and crypto stuff ? also did you add this to lilo ?

Yes... I'm going to assume that by "add this to lilo" you meant

Code:

initrd=/initrd.gz

if this is true, then yes i did.

l0rddarkf0rce · 01-23-2008, 07:35 AM

Quote:

Originally Posted by Ilgar

In case you haven't noticed, for crypto stuff you will need

Multiple devices driver support (RAID and LVM) --->
<*> Device mapper support
<*> Crypt target support

(this one took me some time to figure out when I was compiling my minimalist kernel

).

I'm almost sure I enabled them, but I'll check to make sure.

gopi.d · 01-25-2008, 04:58 AM

dont enable the new sata driver which is marked "conflicts with libsata driver". becoz already there is a driver for sata in drivers menu. for more accurace just re-compile the default huge kernel with config files from /boot folder and use the .config file to build your new kernel don't enable or disable any disk drivers as your old kernel is working fine.