can´t boot updated kernel slackware current
 

Hi Guys:
I updated my kernel in slackware current but can´t install lilo, when i was with my old kernel it gave an error about not finding the sda drives (they were named hda before the upgrade).
I booted into the slackware 13.0 dvd and modified fstab and lilo.conf replacing hda with sda but lilo still gives an error of not finding sda drives.
How can i install lilo so i can boot into my sistem????

I´m really lost here.
Can anyone help???

Thanks in advance.

Can you post your after booting with Slackware DVD.

you have to substitute every occurence of /dev/hda with sda in lilo.conf but one
has to be left because lilo still see the drive as /dev/hda until you reboot and it needs a valid install target. then issue
and reboot.
after reboot (remember that in need you can specify the root partition with root=/dev/sdax kernel option at boot prompt) you can fix the line in lilo.conf above.

Just had a look at my lilo.conf, setup by -current with the 2.6.32.2 kernel and boot = /dev/sda and it works fine.

samac

I'm planning to upgrade to 2.6.32.2-smp kernel and I need to use an initrd.gz image.

File README.initrd was also updated in -current and it does not contain any warning about change of drive naming convention.

So my question is: which -r option should I use:

or

Feedback from any user who upgraded kernel in -current and who's using initrd.gz image would be appreciated.

Right from the changelog for current, x86 and x86_64:

Mon Jan 4 21:43:02 UTC 2010
New kernels... and this deserves a mention/warning: the last bits of the "old" IDE/ATA system have been removed now. Everything should be using the libata based drivers now, so if you have any drives that are currently running as /dev/hda, /dev/hdb, etc., when you reboot with these kernels all drives will be renamed as /dev/sda, /dev/sdb, etc. If you had any /dev/sd* already, they might get renamed. Adjustments may be required in /etc/lilo.conf, /etc/fstab, the initrd, and elsewhere. Good luck!

@SqdnGuns

Yes I've read the Changelog file. My remark about lack of information about change of drive name applied to README.initrd. Thus my question regarding the most appropriate syntax for the mkinitrd command.

Based on your post, I would undestand that I need to use the -r /dev/sdd2 option.

[EDIT] I asked because I plan to run mkinitrd with 2.6.29 kernel running just after upgrading the kernel packages.

I just copied the command for mkinitrd ext3 and modified it for ext4 and kernel 2.6.32.2 and it works just fine. Remembering of course to make a new lilo.conf entry and re-running lilo.

samac

Thanks samac for quick feedback.

But I'm not sure how to interpret your feedback regarding the -r option. Which one did you use -r /dev/hdxx or - r /dev/sdxx or nothing?

According to "man mkinitrd":

As I'm using /dev/hdd2 as my Slackware partition, there is a good chance that kernel default will not be correct (or am I wrong?).

I also upgraded to current. I changed all occurences of hda to sda in /etc/fstab, and tried various combinations of hda and sda in lilo.conf (after which I called lilo every time), but no matter what I try, my system always stops after
Loading vmlinuz...........................................................

Is it mandatory to use initrd with this kernel version? (all my partitions are ext4)

Isn't bash history wonderful.

samac

I take that as a yes then :p

No it is only required when you use the generic.s kernel (recommended) if you use the huge.s kernel you will not need and initrd.gz

samac

Thank you samac.

I'll try with this syntax.

I managed to get my system running again by using this method. Thanks!