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.
Slackware 14 uses 3.2.29 kernel. in my boot directory after upgrading are vmlinuz-generic-smp-3.2.29-smp and vmlinuz-huge-smp-3.2.29-smp, etc. Is there a difference in these, and which should lilo point to?
See the "switch to a generic kernel" part on this page, it explains them very well.
In short, you want a generic kernel running the system after you're done with the installation, since it runs a little bit faster and loads fewer things.
See the "switch to a generic kernel" part on this page, it explains them very well.
In short, you want a generic kernel running the system after you're done with the installation, since it runs a little bit faster and loads fewer things.
Ah, somehow I messed up. I think I did it right, but there is a kernel panic and now I cant boot. I am using an Ubuntu livedisk to access my slackware data, so I was able to edit the lilo.conf. But now I cant set it to the MBR due to the inability to run the command "lilo -v" from inside the livedisk.
Any way to manually move the new lilo conf to MBR? For now I cant bootmy computer either way.
Ive been using these directions that I found on a different threadZ
Code:
~#mkdir /slacktemp #temporary mount point
~#mount /dev/your_device /slacktemp #the device you installed to
~#chroot /slacktemp #change to yours
~#cd /slacktemp/etc #change to directory with lilo.conf
~#vi lilo.conf #edit lilo.conf, if need be
~#lilo -v -t -b /dev/your_device #sda, hda this will only test
~#lilo -v -b /dev/your_device #this will write to your boot device
So far I was able to mount my slackware inside an Ubuntu liveCD that I happened to have around. Then I was able to chroot it. Finally I am able to run lilo! Very tricky! But there is an error:
I Yeah that was the problem, glad you got it working,
It doesnt kernel panic now, but I still cant boot that generic kernel. It gives an error related to not being able to find "mnt" or to mount /dev/sda2 as root, even though that is root. It also said could not find "init". That is from what I remember. I installed a non-generic kernel in order to get around using that suck livedisk. Though I restarted so many times with that livedisk I became proficient at mounting and chrooting folders and filesystems as root. Good experience, but I would rather just avoid such troubles. Never realized what chroot was for.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.