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 recently decided to upgrade my kernel to 2.6.10. First time, it worked fine, but had a few problems, so I decided to go again. Anyways, long story short, is there anyway to restore /boot to the way it was upon installation without touching anything else? I tried chaging the symlinks to vmlinuz, etc. back to the stock 2.4.26 kernel by booting from the installation CD, but no luck.
Also, LILO seems to have stopped working. Apparently some error with time stamps?
Is there any way I can just reconfigure lilo and reintsall the kernel without losing everything else?
When I first tried to boot the 2.6 kernel, it would say "Booting Kernel..." (or something to that effect). However, the screen would go completely blank where the usual booting messages should be. The computer continues to make noise for a while, then stops. It sounds like it's just booting normally, only minus the monitor output. I figured I had made some grave error re. graphics card configuration, so I tried to change the symlinks to vmlinuz, etc. back to the stock 10.0 kernel, but to no avail. (I did this with the CD, so yes, that works).
Also, I tried to add the 2.4 kernel, so I could boot that should the 2.6 fail, but it never shows up on booting. This is what I added to lilo.conf :
Although perhaps it should simply read "vmlinuz-2.4.26" under image, since /dev/hda3 is partitioned just for /boot. Actually, I originally had "/dev/hda7" in place of "/dev/hda3". hda7 is the root parition.
Also, I actually deleted everything in the /boot partition (NOT VERY SMART, I know.), and it continued to behave in exactly the same way, loading minus monitor output. Which is odd.
I can't post lilo.conf right now, since I don't have access to my computer.
But is it possible to simply restore the contents of /boot and the lilo stuff?
I would think of a framebuffer typical error, say no framebuffer support compiled in kernel
so it causes no output on screen if vga option in lilo.conf is set.
If it is that, edit your lilo.conf, locate the vga=... line and change it to vga=normal
save the file, run lilo and boot on hd
[edit]
I did not read the line
Quote:
I actually deleted everything in the /boot partition
What do you want to do now ? Install a kernel from CD ?
Well, yeah, I don't think I have much choice. But how would I go about doing that?
And the reason I deleted it (well, aside from it being late and I'm not entirely sure what i was thinking) was that even when I changed the vmlinuz symlink to the 2.4 kernel, it kept booting in exactly the same way. Even when I deleted everything in /boot, it kept behaving the same. The timestamp errors happened when I was messing with the vga= lines in lilo.conf.
So really all I need to do is restore the original contents of boot and rerun lilo. However, that (lilo) didn't work when I tried to do it off the CD. (use the lilo/liloconfig commands, that is)
Also, how do I configure lilo so that I can choose from two different kernels? Like I said, it dien't work the first time.
When I get home (uh, this weekend) I'll try changing the lilo stuff and booting the 2.6 kernel (which I can still use, I just don't know how to get the normal 2.4 one back).
Oh and thanks for assisting me with my quite odd and rather idiotic problem.
Although perhaps it should simply read "vmlinuz-2.4.26" under image, since /dev/hda3 is partitioned just for /boot. Actually, I originally had "/dev/hda7" in place of "/dev/hda3". hda7 is the root parition.
----------------------------
you should use :" root=/dev/hda7 " because that's your root partition.
and as said, compile in the framebuffer-support on your next try.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.