SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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.
Click here to see the post LQ members have rated as the most helpful post in this thread.
you have to substitute every occurence of /dev/hda with sda in lilo.conf but one
Code:
boot=/dev/hda
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
Code:
lilo
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.
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!
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.
Last edited by gegechris99; 01-06-2010 at 02:48 PM.
Reason: I asked because mkinitrd would be run with 2.6.29 kernel
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.
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)
you have to substitute every occurence of /dev/hda with sda in lilo.conf but one
Code:
boot=/dev/hda
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
Code:
lilo
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.
I managed to get my system running again by using this method. Thanks!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.