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.
I just did that yesterday and had a heck of a time. What I did that finally worked was use mkinitrd add the initrd.gz file to lilo.conf after the image line, then (hopefully this wont be a problem for you, but) I rebooted to which I had to mount /dev/sda# on /mnt, then exit, then it finally booted into the hd, then you will be able to rerun lilo to fix it.
<Edit> Just thinking about it, while it's running and all, better get a second opinion from someone who knows more first...
Can you list the sda layout ... ? (Can you access /dev/sda1)
Code:
fdisk -l /dev/sda
# or even...
fdisk -l /dev/sda1
There is no /dev/sda yet. I started all this using Slack 13 which is using /hd*, after upgrading I'm changing all instances of /hd* to /sd* in fstab and lilo.conf to avoid a kernel panic upon reboot.
What worked for me was to boot from the Slackware 13 install disk and continue until after selection of a keyboard and you have a root login. Then:
'mkdir /mnt/tmp'
'mount /dev/hda1 /mnt/tmp'
'chroot /mnt/tmp'
If using an initrd then, 'cd /boot' and run mkinitrd specifying -r /dev/sda1
Edit /etc/lilo.conf so that "boot=/dev/hda" in the global section and "root=/dev/hda1" in the partition config section. Also check that "image=<your new kernel>" and you have an "initrd=/boot/initrd.gz".
'exit'
'/mnt/tmp/lilo -r /mnt/tmp' - lilo should run without error
Now you should be able to boot using the root=/dev/sda1 option, so you can fix up lilo.conf and rerun lilo.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.