LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Restoring /boot, lilo problems. (https://www.linuxquestions.org/questions/slackware-14/restoring-boot-lilo-problems-287250/)

Duo 02-07-2005 08:09 AM

Restoring /boot, lilo problems.
 
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?

egag 02-07-2005 08:29 AM

well..can you boot the machine with the cd ?

if so, can you post your lilo.conf file ( it's in /etc)
and the output of " ls -al /boot " ?

the point is that the linux section (s ) in the config-file should point at the kernel (s) you've got.
then run " #lilo " and all should be well.

need some help....then just post what i asked.

egag

Duo 02-07-2005 10:38 AM

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 :

image = /boot/vmlinuz-2.4.26
root = /dev/hda3
label = Linux24
read-only

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?

keefaz 02-07-2005 10:41 AM

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 ?

Duo 02-07-2005 11:06 AM

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. ;)

egag 02-07-2005 11:16 AM

-----------------
image = /boot/vmlinuz-2.4.26
root = /dev/hda3
label = Linux24
read-only

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.

good luck

egag


All times are GMT -5. The time now is 07:06 AM.