Hi,
So, as mentioned in the topic desc.:
I've just installed Mandriva 2007 Xtreme (PL) and restarted when it's finished. Then.. Nothing happened. WinXP started as usual. No OS selection screen. F8 switches to windows boot menu, no linux in there. Like I just haven't installed it..
Additional info:
- Lilo installed using the first sector of the main partition.
- Hardware: IBM/Lenovo ThinkPad T60p (possible ThinkVentage software conflict?)
Help?
Full Version: LILO doesn't run [solved]
Are you sure you installed LILO to the MBR? ( /dev/hda in Linux terms ). From your description it sounds like you installed LILO to dev/hdax, which is bootable only when using another primary bootloader.
Browse your Linux root partition under XP ( you can use Total Commander and the ext2/Reiser filesystem plugin, or any other established solution ) and read/paste here the contents of the file /etc/lilo.conf
Regards.
Browse your Linux root partition under XP ( you can use Total Commander and the ext2/Reiser filesystem plugin, or any other established solution ) and read/paste here the contents of the file /etc/lilo.conf
Regards.
Been there, done that.. seen none 
No lilo.conf anywhere, but:
where a file named lilo.conf.5.bz2 (archive) with the same named file inside (-archive extension) can be found.
The other thing that looks to have something to do with the boot is
which is actually what has been installed in fact as the "Lilo" (linux loader) I guess..
What now? Create that .conf file? Or maybe reinstall it but use the first sector of the disk now? (as I said, I've chosen the 'first sector of the main partition' option before)
I'm all in ears..
No lilo.conf anywhere, but:CODE
\hda5\usr\share\man\pl\man5
where a file named lilo.conf.5.bz2 (archive) with the same named file inside (-archive extension) can be found.
The other thing that looks to have something to do with the boot is
CODE
\hda5\boot\grub\
which is actually what has been installed in fact as the "Lilo" (linux loader) I guess..
What now? Create that .conf file? Or maybe reinstall it but use the first sector of the disk now? (as I said, I've chosen the 'first sector of the main partition' option before)
I'm all in ears..
First, you have to decide if you installed LILO or Grub as bootloader...
In case you did install Grub, paste here the file /boot/grub/menu.lst
Anyway, to avoid reinstalling you must:
1. Boot from the installation CD (or virtually any Linux liveCD)
2. Chrooting to the installed root partition
3. Running the command
(it may take some one minute to complete)
For LILO, it's done differently- but still you need a liveCD and chrooting.
In case you did install Grub, paste here the file /boot/grub/menu.lst
Anyway, to avoid reinstalling you must:
1. Boot from the installation CD (or virtually any Linux liveCD)
2. Chrooting to the installed root partition
3. Running the command
CODE
grub-install /dev/hda
(it may take some one minute to complete)
For LILO, it's done differently- but still you need a liveCD and chrooting.
Here you are:
Now.. I told about LILO 'cause the installator used this expression, but it obviously meant GRUB as the LInux-LOader in this case. It was not my choice or something. I was just clinking next, next, next
CODE
timeout 10
color black/cyan yellow/cyan
gfxmenu (hd0,4)/usr/share/gfxboot/themes/Mandriva/boot/message
default 0
title linux
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=linux root=/dev/sda5 splash=silent vga=788
initrd (hd0,4)/boot/initrd.img
title linux-nonfb
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=/dev/sda5 splash=silent
initrd (hd0,4)/boot/initrd.img
title windows
root (hd0,0)
makeactive
chainloader +1
title windows1
root (hd0,1)
makeactive
chainloader +1
title 2.6.17-11
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=2.6.17-11 root=/dev/sda5 splash=silent vga=791
initrd (hd0,4)/boot/initrd.img
title failsafe
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=failsafe root=/dev/sda5 failsafe splash=silent
initrd (hd0,4)/boot/initrd.img
title alt_windows
root (hd0,0)
makeactive
chainloader +1
title alt_windows1
root (hd0,1)
makeactive
chainloader +1
color black/cyan yellow/cyan
gfxmenu (hd0,4)/usr/share/gfxboot/themes/Mandriva/boot/message
default 0
title linux
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=linux root=/dev/sda5 splash=silent vga=788
initrd (hd0,4)/boot/initrd.img
title linux-nonfb
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=/dev/sda5 splash=silent
initrd (hd0,4)/boot/initrd.img
title windows
root (hd0,0)
makeactive
chainloader +1
title windows1
root (hd0,1)
makeactive
chainloader +1
title 2.6.17-11
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=2.6.17-11 root=/dev/sda5 splash=silent vga=791
initrd (hd0,4)/boot/initrd.img
title failsafe
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=failsafe root=/dev/sda5 failsafe splash=silent
initrd (hd0,4)/boot/initrd.img
title alt_windows
root (hd0,0)
makeactive
chainloader +1
title alt_windows1
root (hd0,1)
makeactive
chainloader +1
Now.. I told about LILO 'cause the installator used this expression, but it obviously meant GRUB as the LInux-LOader in this case. It was not my choice or something. I was just clinking next, next, next
Alright.. Re-installing + choosing MBR solved the problem.. New ones came but screw it Gonna read bout it.
Thanks and c'ya..
Gonna read bout it.Thanks and c'ya..
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.