Since installing the 2.6.0 kernel... Ive got a new problem...

Everytime I recompile the kernel, copy, run LILO and reboot.. the system fails to boot!!! I get the: LI .... prompt and the system hangs.... I then have to insert a CDROM and resue the system to get it working again... If I then rerun LILO under a 2.4.10 kernel during rescue... the system boots again.

GEEZ!!!

So what happens if you boot to the new kernel and then reinstall LILO.

BTW - a more helpful thread title would be useful. Your current one tells us nothing about your problem.

And what about posting your lilo.conf? Are you saying you are copying the kernel to /boot? Are you using a different name? LI tells you about which stage LILO managed to progress.

man lilo has plenty of information.

Please edit the subject line too. You'll get more answers this way.

Anytime I run LILO under 2.6.0, the system will fail to boot the next time.

Caught youre eye didnt it?

Only because I have nothing better to do. And while I know the answer to your question, and you failed to post what I requested, you get no help.

Good luck.

Only slightly - if the board was any more busy I'd have probably ignored it.

What error messages are you getting, can you post lilo.conf?

I dont get any error messages at all... the System simply prints out: LI , then hangs.

When I then boot using the Distro CD, I am able to boot a 2.4.10 kernel... If I then type lilo again, under the 2.4.10 kernel, and reboot, everything works fine. Since I am using the same lilo.conf under each kernel, I dont think thats the problem. Maybe there is a config option in the 2.6.0 kernel that would cause LILO not to be able to write to the MBR?

No there's no config option in 2.6 that affects the MBR. Once more, post the /etc/lilo.conf and your /etc/fstab. You boot a 2.4.10 kernel b/c you are using rescue, right? Guess where that kernel is coming from? Yep. The rescue cd.

Its also helpful if you let us know your hardware. Does this machine dual-boot? Is it a laptop? is it x86-based? This sort of information can help others solve YOUR problem quicker than you can continue to type posts that only reiterate what your first post said.

IF you want help, please comply. Your problem is solvable, btw.

I am not really using rescue... I am actually going through a manual installation menu, and selecting "Boot Installed System" which prompts me for a device where root is... I enter /dev/hda7 , and it loads a 2.4.10 kernel that I have compiled on this machine...

Guaranteed!!! it is not lilo.conf but....here yar!

# Modified by YaST2. Last modification on Wed Dec 24 22:59:53 2003


boot = /dev/hda
vga = normal
prompt
timeout = 80
default = Linux-2.4.22

image = /boot/vmlinuz
label = linux
root = /dev/hda7
initrd = /boot/initrd
append = "enableapic"

image = /boot/vmlinuz.suse
label = failsafe
root = /dev/hda7
initrd = /boot/initrd.suse
append = "disableapic ide=nodma apm=off"
optional

image = /boot/memtest.bin
label = memtest86

image = /boot/vmlinuz-2.4.22
label = Linux-2.4.22
optional
root = /dev/hda7

image = /boot/vmlinuz-2.6.0
label = Linux-2.6.0
optional
root = /dev/hda7

And /etc/fstab:

/dev/hda7 / reiserfs defaults 1 1
/dev/hda6 /boot ext2 defaults 1 2
/dev/cdrom /media/cdrom auto ro,noauto,user,exec 0 0
devpts /dev/pts devpts defaults 0 0
/dev/fd0 /media/floppy auto noauto,user,sync 0 0
proc /proc proc defaults 0 0
usbdevfs /proc/bus/usb usbdevfs defaults,noauto 0 0
/dev/hda5 swap swap pri=42 0 0

You are using LILO, correct? Do you get the LILO prompt and the opportunity to choose which label to boot? Have you tried the "failsafe" one? I had problems with 2.6.0 on my laptop and had to append "noapic" to the 2.6.0 kernel. Hopefully you did remember to build reiserfs support into 2.6.0, right? I have completely FUBAR'd that type of stuff before. Also, I enabled sysfs on my 2.6.0 with a line in /etc/fstab like:

none /sys sysfs defaults 0 0

Did you follow a HOW-TO for compiling/installing 2.6? I am not a SuSe user and I'm curious if the SuSe forums may not have a super-quick answer for you.

1. Make sure filesystem support exists.
2. Try with the noapic append line.
3. Run lilo -v and make sure it finishes properly.

And let us know if that works. Good luck.

Once again...

When I run LILO while running the 2.6.0, it gives me all of the Added... messages... Then when I reboot. I get no menu for selecting a kernel. I just get the LI and the system hangs.

In lieu of any other suggestions......have you tried removing and reinstalling LILO? Obviously taking a note of your present settings.

There's a line in LILO that you may have to uncomment: that says:

prompt

You want that to be uncommented. This will give you the menu. If there's anyway you can post your lilo.conf, this can be fixed.

You said you did make install, right? in the 2.6 kernel make instal uses the system's /bin/installkernel or /sbin/installkernel program. You don't need that if you ALREADY copied the kernel to boot. All I do with 2.6 is make && make modules modules_install.

Sounds like you wrote over the /vmlinuz symlink or the /boot/vmlinuz kernel with your 2.6. Look and see if their date stamps are the same as your vmlinuz-2.6.0 kernel. You may need to edit the first stanza...