Multi Boot Loader - Which one?

[snminc]

Evening all, I've just added Ubuntu to my dual boot of Win XP/PCLOS which uses Lilo. I told Ubuntu's GRUB to install on the Ubuntu partition (Hda9) which lead to a critical failure during the installationWhat should I have done?ThanksScott

[Bruno]

I told Ubuntu's GRUB to install on the Ubuntu partition (Hda9) which lead to a critical failure during the installation

Ouch ! . . . . Well that is an ugly problem . . . . the Ubuntu installer should have nicely installed the bootloader in that partition !What you can do is a bit of a risk . . . . but try anyway: Reinstall Ubuntu and write the bootloader to the MBR . . . . . it will automatically include PCLos and Windows. ( Now, I hope it does not give you the same critical failure because it could then mess up the MBR )Next you boot Ubuntu and give the command "sudo grub-install /dev/hdaXX" ( where you replace the XX to the partition number ) . . . if that is successful you boot PCLos and restore the PCLOs bootloader to the MBR, add the entry for Ubuntu and you are smiling again :DNow Imagine Ubuntu messes up your MBR, just boot the PCLos Live CD and give the command "redo-lilo" as root Bruno

[tommyj12]

Bruno, I just recently noticed in test 4 there is a menu entry for redo-mbr. It's under system-configuration-boot and init- redo-mbr. For all those cli challenged folks! Tommy

[Bruno]

That is good to know Tommy !I just am not sure what version of PCLos he has installed and if on the CD of that HD install the command is redo-lilo ( as in 9.3 ) or redo-mbr ( as in 9.4 test versions ). But since he was talking about lilo ( and not grub what the 9.4 is using ) I assumed it would be redo-lilo. Bruno

[tommyj12]

Your right about .93 or eariler being redo-lilo. But as with mandravia spring you can choose lilo as the bootloader on install in the boot section of the installer, it defaults to grub.(see pic) So even though he is referring to lilo it could still be redo-mbr. Tommy

[snminc]

Apologies to all, I should have said I'm using PCLinuxOS 2007 TR4. I has assumed because PCLOS bootloader had pretty colours it was lilo as Ubuntu's bootloader is just white text on a black background.I tried following your advice (Using Redo-MBR as Redo-lilo came back with unknown command) Slaps self on forehead again I ended up with a whole list of missing files reported whilst Ubuntu was starting and it couldn't "see" my network connection.I subsequently reinstalled Ubuntu and now WinXP, PCLOS 2007 TR4 & Ubuntu 7.04 are all booting quite happily. Is there away to switch back to PCLOS's bootloader or should I just leave the D*** thing alone before I break it AGAIN.Many thanks, Scott

[tommyj12]

I subsequently reinstalled Ubuntu and now WinXP, PCLOS 2007 TR4 & Ubuntu 7.04 are all booting quite happily. Is there away to switch back to PCLOS's bootloader or should I just leave the D*** thing alone before I break it AGAIN.

I would say leave it, but if you are a glutton for punishment like me then you won't be able to. Tommy

[Bruno]

Is there away to switch back to PCLOS's bootloader

Sure there is . . . . but why would you go through the trouble ?Anyway if you do . . . don't forget to re-write the Ubuntu Grub to the Ubuntu partition . . . . else you will have trouble booting Ubuntu after you restore the PCLos Lilo to the MBR. Bruno

[snminc]

Tommy, Your right I probably won't be able to leave the bootloader alone Bruno, I'm a tad confused again (I know it's easy done I've only got two operational braincells left, too much headbangin' as a teenager)

after you restore the PCLos Lilo to the MBR. Bruno

I thought PCLOS 2007 TR4 used Grub as well. Should I just use Redo-mbr?I'm currently booting from Ubuntu's Grub I think my plan of attack should be 1. sudo grub-install /dev/hda9 in ubuntu2. Reboot into PCLOS and redo-mbr3. Add Ubuntu to PCLOS Grub (Still pondering that one)4. Reboot to all OS to make sure they work5. Promise never ever ever to play with the bootloaders again, well not for the rest of this week anyway Sound feasible?Thanks, Scott

[tommyj12]

Tommy,Your right I probably won't be able to leave the bootloader alone wacko.gif

I knew there was something I liked about you. 1. sudo grub-install /dev/hda9 in ubuntu Not sure about that one, better get some conformation first. Everything else looks good to me though. Tommy

[Bruno]

1. sudo grub-install /dev/hda9 in ubuntu2. Reboot into PCLOS and redo-mbr3. Add Ubuntu to PCLOS Grub (Still pondering that one)4. Reboot to all OS to make sure they work

Hi Scott . . . . 1). "sudo grub-install /dev/hda9" looks okay to me2). "Reboot into PCLOS and redo-mbr" is okay but once in PCLos you can also simply do "# grub-install /dev/hda" and it will install grub in the MBR3). "Add Ubuntu to PCLOS Grub" is a good idea . . . . . . what you will have to add to the /boot/grub/menu.lst is this section:

title Ubunturoot (hd0,8)chainloader +1

4). Next you can reboot and check if the Ubuntu entry in your Grub menu worksB) Bruno

[snminc]

Evening Bruno, I tried to follow your suggestion as laid out above. Ubuntu now appears on PCLinuxOS TR4's Grub but when I select the ubuntu option I get the following kernel (hd0,8)Error 1 Filename must be either an absolute filename or blocklistPress any key to continueI'm not sure if it's relevant but here's my PCLOS menu.lst filetimeout 10color black/cyan yellow/cyangfxmenu (hd0,5)/usr/share/gfxboot/themes/pclinuxos/boot/messagedefault 3title PCLinuxOSkernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS root=/dev/hda6 splash=silent vga=788initrd (hd0,5)/boot/initrd.imgtitle linux-nonfbkernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=/dev/hda6 initrd (hd0,5)/boot/initrd.imgtitle failsafekernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=failsafe root=/dev/hda6 failsafeinitrd (hd0,5)/boot/initrd.imgtitle WinXProot (hd0,0)makeactivechainloader +1title Ubuntukernel (hd0,8)chainloader+1PCLOS fstab & Fdisk # /dev/hda6, size=21045087, type=131: Journalised FS: ext3 (extended)/dev/hda6 / ext3 defaults 1 1none /dev/pts devpts mode=0620 0 0# fd: H1440/dev/fd0 /mnt/floppy auto user,exec,rw,noauto 0 0# /dev/hda11, size=19475820, type=131: Journalised FS: ext3 (extended)/dev/hda11 /mnt/hda11 ext3 user,exec,rw,noauto 1 2# /dev/hda8, size=14731542, type=131: Journalised FS: ext3 (extended)/dev/hda8 /mnt/hda8 ext3 user,exec,rw,noauto 1 2# /dev/hda9, size=21173607, type=131: Journalised FS: ext3 (extended)/dev/hda9 /mnt/hda9 ext3 user,exec,rw,noauto 1 2# /dev/hda1, size=61464627, type=7: NTFS (primary)/dev/hda1 /mnt/win_c ntfs user,exec,ro,noauto,iocharset=iso8859-1,umask=0 0 0# /dev/hda5, size=16386237, type=11: FAT32 (extended)/dev/hda5 /mnt/win_d vfat umask=0,iocharset=iso8859-1,codepage=850 0 0# /dev/hdb5, size=234420417, type=11: FAT32 (extended)/dev/hdb5 /mnt/win_e vfat user,exec,rw,noauto,iocharset=iso8859-1,codepage=850,umask=0 0 0none /proc proc defaults 0 0none /proc/bus/usb usbfs defaults 0 0# /dev/hda7, size=1012032, type=130: Linux swap (extended)/dev/hda7 swap swap defaults 0 0# /dev/hda10, size=1012032, type=130: Linux swap (extended)/dev/hda10 swap swap defaults 0 0Disk /dev/hda: 80.0 GB, 80026361856 bytes255 heads, 63 sectors/track, 9729 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System/dev/hda1 * 1 3826 30732313+ 7 HPFS/NTFS/dev/hda2 3827 9730 47418368 f W95 Ext'd (LBA)Partition 2 does not end on cylinder boundary./dev/hda5 3827 4846 8193118+ b W95 FAT32/dev/hda6 4847 6156 10522543+ 83 Linux/dev/hda7 6157 6219 506016 82 Linux swap / Solaris/dev/hda8 6220 7136 7365771 83 Linux/dev/hda9 7137 8454 10586803+ 83 Linux/dev/hda10 8455 8517 506016 82 Linux swap / Solaris/dev/hda11 8518 9730 9737910 83 LinuxDisk /dev/hdb: 120.0 GB, 120034123776 bytes255 heads, 63 sectors/track, 14593 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System/dev/hdb1 2 14593 117210240 f W95 Ext'd (LBA)/dev/hdb5 2 14593 117210208+ b W95 FAT32Disk /dev/sda: 4095 MB, 4095737344 bytes255 heads, 63 sectors/track, 497 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System/dev/sda1 1 5 40131 0 Empty/dev/sda2 6 497 3951990 b W95 FAT32Ubuntu's fstab & fdisk# /etc/fstab: static file system information.## <file system> <mount point> <type> <options> <dump> <pass>proc /proc proc defaults 0 0# /dev/hda9UUID=bce9ac5e-bb73-4ca2-b0cb-72eebc0f5c7e / ext3 nouser,defaults,errors=remount-ro,atime,auto,rw,dev,exec,suid 0 1# /dev/hda1UUID=1A5CDD125CDCEA11 /media/hda1 ntfs defaults,nls=utf8,umask=007,uid=0,gid=46,auto,rw,nouser 0 1# /dev/hda11UUID=c2fa7a8e-ec6a-11db-863b-916bfc482b89 /media/hda11 ext3 nouser,defaults,atime,auto,rw,dev,exec,suid 0 2# /dev/hda5LABEL=DOCUMENTS /media/hda5 vfat umask=0,iocharset=iso8859-1,codepage=850,uid=0,gid=46,auto,rw,nouser 0 0# /dev/hda6UUID=2696ac66-7976-4126-892e-e944b2e58c65 /media/hda6 ext3 nouser,defaults,atime,auto,rw,dev,exec,suid 0 2# /dev/hda8UUID=e726304e-21b3-4c84-800d-cb6b6fb83ebd /media/hda8 ext3 nouser,defaults,atime,auto,rw,dev,exec,suid 0 2# /dev/hdb5LABEL=DOCUMENTS /media/hda5 vfat umask=0,iocharset=iso8859-1,codepage=850,uid=0,gid=46,auto,rw,nouser 0 0# /dev/hda10UUID=eb370d5a-1862-44d3-9933-87fbe37803e3 none swap sw 0 0# /dev/hda7UUID=16a7a03d-0889-4b8a-bbc3-59666cef0dac none swap sw 0 0/dev/hdc /media/cdrom0 udf,iso9660 user,atime,noauto,rw,dev,exec,suid 0 0/dev/fd0 /media/floppy0 auto user,atime,noauto,rw,dev,exec,suid 0 0Disk /dev/hda: 80.0 GB, 80026361856 bytes255 heads, 63 sectors/track, 9729 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System/dev/hda1 * 1 3826 30732313+ 7 HPFS/NTFS/dev/hda2 3827 9730 47418368 f W95 Ext'd (LBA)Partition 2 does not end on cylinder boundary./dev/hda5 3827 4846 8193118+ b W95 FAT32/dev/hda6 4847 6156 10522543+ 83 Linux/dev/hda7 6157 6219 506016 82 Linux swap / Solaris/dev/hda8 6220 7136 7365771 83 Linux/dev/hda9 7137 8454 10586803+ 83 Linux/dev/hda10 8455 8517 506016 82 Linux swap / Solaris/dev/hda11 8518 9730 9737910 83 LinuxDisk /dev/hdb: 120.0 GB, 120034123776 bytes255 heads, 63 sectors/track, 14593 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System/dev/hdb1 2 14593 117210240 f W95 Ext'd (LBA)/dev/hdb5 2 14593 117210208+ b W95 FAT32Apologies for all the blurb if it's irrelevantScott

[Bruno]

But Scot . . . when you choose the Ubuntu entry in your PCLos Grub does it than chainload the Ubuntu grub so you can choose an entry there ? And what entry do you choose from the 2nd ( Ubuntu's ) Grub ? Bruno

[snminc]

Evening Bruno, From the PCLOS Grub if I select Ubuntu I get the Error 1 message then Ubuntu's Grub, If I select Ubuntu from it I get the Error 1 message and back to Unbuntu's Grub.Again and again and errrr....... Again On the plus side PCLOS TR4 now has shared Firefox & Thunderbird with Win XP (Not that you needed to know that)As always any help/support or offers to remove my DVD Drive (My better halfs gettin a bit ticked off at a different boot sequence greeting her every morning )will be greatly appreciatedScott

[Bruno]

Evening Bruno, From the PCLOS Grub if I select Ubuntu I get the Error 1 message then Ubuntu's Grub, If I select Ubuntu from it I get the Error 1 message and back to Unbuntu's Grub.

Ouch ! . . . means something is wrong with the grub you installed in the / partition of Ubuntu . . . . . Means we will have to add Ubuntu in a different way to the PCLos grub.Can you mount the Ubuntu partition in PCLos and do "cat /mnt/hda??/boot/grub/menu.list" to show me the menu.lst of the Ubuntu partition ?? ( if you need help mounting let me know ) Bruno

[snminc]

Evening Bruno, Are you ready for this??# menu.lst - See: grub(8), info grub, update-grub(8)# grub-install(8), grub-floppy(8),# grub-md5-crypt, /usr/share/doc/grub# and /usr/share/doc/grub-doc/.## default num# Set the default entry to the entry number NUM. Numbering starts from 0, and# the entry number 0 is the default if the command is not used.## You can specify 'saved' instead of a number. In this case, the default entry# is the entry saved with the command 'savedefault'.# WARNING: If you are using dmraid do not change this entry to 'saved' or your# array will desync and will not let you boot your system.default 0## timeout sec# Set a timeout, in SEC seconds, before automatically booting the default entry# (normally the first entry defined).timeout 10## hiddenmenu# Hides the menu by default (press ESC to see the menu)#hiddenmenu# Pretty colours#color cyan/blue white/blue## password ['--md5'] passwd# If used in the first section of a menu file, disable all interactive editing# control (menu entry editor and command-line) and entries protected by the# command 'lock'# e.g. password topsecret# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/# password topsecret## examples## title Windows 95/98/NT/2000# root (hd0,0)# makeactive# chainloader +1## title Linux# root (hd0,1)# kernel /vmlinuz root=/dev/hda2 ro### Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST### BEGIN AUTOMAGIC KERNELS LIST## lines between the AUTOMAGIC KERNELS LIST markers will be modified## by the debian update-grub script except for the default options below## DO NOT UNCOMMENT THEM, Just edit them to your needs## ## Start Default Options #### default kernel options## default kernel options for automagic boot options## If you want special options for specific kernels use kopt_x_y_z## where x.y.z is kernel version. Minor versions can be omitted.## e.g. kopt=root=/dev/hda1 ro## kopt_2_6_8=root=/dev/hdc1 ro## kopt_2_6_8_2_686=root=/dev/hdc2 ro# kopt=root=UUID=bce9ac5e-bb73-4ca2-b0cb-72eebc0f5c7e ro## Setup crashdump menu entries## e.g. crashdump=1# crashdump=0## default grub root device## e.g. groot=(hd0,0)# groot=(hd0,8)## should update-grub create alternative automagic boot options## e.g. alternative=true## alternative=false# alternative=true## should update-grub lock alternative automagic boot options## e.g. lockalternative=true## lockalternative=false# lockalternative=false## additional options to use with the default boot option, but not with the## alternatives## e.g. defoptions=vga=791 resume=/dev/hda5# defoptions=quiet splash## should update-grub lock old automagic boot options## e.g. lockold=false## lockold=true# lockold=false## Xen hypervisor options to use with the default Xen boot option# xenhopt=## Xen Linux kernel options to use with the default Xen boot option# xenkopt=console=tty0## altoption boot targets option## multiple altoptions lines are allowed## e.g. altoptions=(extra menu suffix) extra boot options## altoptions=(recovery) single# altoptions=(recovery mode) single## controls how many kernels should be put into the menu.lst## only counts the first occurence of a kernel, not the## alternative kernel options## e.g. howmany=all## howmany=7# howmany=all## should update-grub create memtest86 boot option## e.g. memtest86=true## memtest86=false# memtest86=true## should update-grub adjust the value of the default booted system## can be true or false# updatedefaultentry=false## ## End Default Options ##title Ubuntu, kernel 2.6.20-15-genericroot (hd0,8)kernel /boot/vmlinuz-2.6.20-15-generic root=UUID=bce9ac5e-bb73-4ca2-b0cb-72eebc0f5c7e ro quiet splashinitrd /boot/initrd.img-2.6.20-15-genericquietsavedefaulttitle Ubuntu, kernel 2.6.20-15-generic (recovery mode)root (hd0,8)kernel /boot/vmlinuz-2.6.20-15-generic root=UUID=bce9ac5e-bb73-4ca2-b0cb-72eebc0f5c7e ro singleinitrd /boot/initrd.img-2.6.20-15-generictitle Ubuntu, memtest86+root (hd0,8)kernel /boot/memtest86+.binquiet### END DEBIAN AUTOMAGIC KERNELS LIST# This is a divider, added to separate the menu items below from the Debian# ones.title Other operating systems:root# This entry automatically added by the Debian installer for a non-linux OS# on /dev/hda1title Microsoft Windows XP Professionalroot (hd0,0)savedefaultmakeactivechainloader +1# This entry automatically added by the Debian installer for an existing# linux installation on /dev/hda6.title PCLinuxOS (on /dev/hda6)root (hd0,5)kernel /boot/vmlinuz BOOT_IMAGE=PCLinuxOS root=/dev/hda6 splash=silent vga=788 initrd (hd0,5)/boot/initrd.imgsavedefaultboot# This entry automatically added by the Debian installer for an existing# linux installation on /dev/hda6.title linux-nonfb (on /dev/hda6)root (hd0,5)kernel /boot/vmlinuz BOOT_IMAGE=linux-nonfb root=/dev/hda6 initrd (hd0,5)/boot/initrd.imgsavedefaultboot# This entry automatically added by the Debian installer for an existing# linux installation on /dev/hda6.title failsafe (on /dev/hda6)root (hd0,5)kernel /boot/vmlinuz BOOT_IMAGE=failsafe root=/dev/hda6 failsafe initrd (hd0,5)/boot/initrd.imgsavedefaultboot# This entry automatically added by the Debian installer for an existing# linux installation on /dev/hda6.title Ubuntu (on /dev/hda6)root (hd0,5)kernel /boot/vmlinuz-2.6.18.8.tex4 BOOT_IMAGE=Ubuntu root=/dev/hda9 initrd (hd0,5)/boot/initrd.imgsavedefaultbootI think the last entry might be a problem as hda6 is PCLOS TR4, Ubuntu is on hda9.What do you think?Scott

[Bruno]

Hi ScottAdd these 2 entries to your PCLos Grub menu.lst:

title Ubuntu, kernel 2.6.20-15-genericroot (hd0,8)kernel /boot/vmlinuz-2.6.20-15-generic root=hda9 ro quiet splashinitrd /boot/initrd.img-2.6.20-15-genericquietsavedefaulttitle Ubuntu, kernel 2.6.20-15-generic (recovery mode)root (hd0,8)kernel /boot/vmlinuz-2.6.20-15-generic root=hda9 ro singleinitrd /boot/initrd.img-2.6.20-15-generic

After that try to reboot and boot the Ubuntu entries . . . . Bruno

[V.T. Eric Layton]

Whoops! Nevermind. Bruno answered at the same time I did. :)I will say this, though... that last entry for Ubuntu in your menu.lst is definitely incorrect and should probably just be removed.

Edited May 3, 2007 by V.T. Eric Layton

[Bruno]

I will say this, though... that last entry for Ubuntu in your menu.lst is definitely incorrect and should probably just be removed.

Yep I agree on that one ! Bruno

[snminc]

Many thanks Eric & Bruno.I Entered the script provided and deleted the previous entry for Ubuntu. When I booted into Ubuntu the chainloader didn't load instead it went straight to the kubuntu splash screen and the alpha & scroll lock lights flashedI rebooted into Ubuntu's recovery mode and got the followingBegin: mounting root filesystem/init/init: 148: syntax error 0xdha9[23.749245] kernel panic - not syncing: Attempted to kill initAny ideas?PS Bruno I noticed from your profile your 5 years younger than my dad to the day!Except he is to computers what Adolf Hitler was too world peace Thanks againScott

[V.T. Eric Layton]

Bruno's about 7 months younger than my brother, who is to computers what Elmer Fudd was to rabbit hunting. ;)Does your menu.lst look like this now?

title Ubuntu, kernel 2.6.20-15-genericroot (hd0,8)kernel /boot/vmlinuz-2.6.20-15-generic root=hda9 ro quiet splashinitrd /boot/initrd.img-2.6.20-15-genericquietsavedefaulttitle Ubuntu, kernel 2.6.20-15-generic (recovery mode)root (hd0,8)kernel /boot/vmlinuz-2.6.20-15-generic root=hda9 ro singleinitrd /boot/initrd.img-2.6.20-15-generictitle Ubuntu, memtest86+root (hd0,8)kernel /boot/memtest86+.binquiet### END DEBIAN AUTOMAGIC KERNELS LIST# This is a divider, added to separate the menu items below from the Debian# ones.title Other operating systems:root# This entry automatically added by the Debian installer for a non-linux OS# on /dev/hda1title Microsoft Windows XP Professionalroot (hd0,0)savedefaultmakeactivechainloader +1# This entry automatically added by the Debian installer for an existing# linux installation on /dev/hda6.title PCLinuxOS (on /dev/hda6)root (hd0,5)kernel /boot/vmlinuz BOOT_IMAGE=PCLinuxOS root=/dev/hda6 splash=silent vga=788initrd (hd0,5)/boot/initrd.imgsavedefaultboot# This entry automatically added by the Debian installer for an existing# linux installation on /dev/hda6.title linux-nonfb (on /dev/hda6)root (hd0,5)kernel /boot/vmlinuz BOOT_IMAGE=linux-nonfb root=/dev/hda6initrd (hd0,5)/boot/initrd.imgsavedefaultboot# This entry automatically added by the Debian installer for an existing# linux installation on /dev/hda6.title failsafe (on /dev/hda6)root (hd0,5)kernel /boot/vmlinuz BOOT_IMAGE=failsafe root=/dev/hda6 failsafeinitrd (hd0,5)/boot/initrd.imgsavedefaultboot

By the way, you're not (or shouldn't be) chainloading Ubuntu. Your only chainloader entry in your menu.lst is Windows. Did you delete that last Ubuntu entry on your menu.lst... the one way down at the bottom?Also, just for to be sure of what we're doing here, can you mount /dev/hda9 from PClos and give the output of this command:

 # mount /dev/hda9 /mnt# cd /mnt# ls /boot

Edited May 3, 2007 by V.T. Eric Layton

[Bruno]

Hi Scott . . . . . Looks like something is wrong with your Ubnutu install . . . . it should have booted from that entry without problems. BrunoPS: What is this thing about my age ?? . . .

[Urmas]

Age? What age?Methus'lah lived nine hundred yearsMethus'lah lived nine hundred yearsBut who calls dat livin' when no gal'll give inTo no man what's nine hundred yearsIce age? Stone age?

[snminc]

Thanks to all for taking the time to postEric my PCLOS menu.lst file is as followstimeout 10color black/cyan yellow/cyangfxmenu (hd0,5)/usr/share/gfxboot/themes/pclinuxos/boot/messagedefault 3title PCLinuxOSkernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS root=/dev/hda6 splash=silent vga=788initrd (hd0,5)/boot/initrd.imgtitle linux-nonfbkernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=/dev/hda6 initrd (hd0,5)/boot/initrd.imgtitle failsafekernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=failsafe root=/dev/hda6 failsafeinitrd (hd0,5)/boot/initrd.imgtitle WinXProot (hd0,0)makeactivechainloader +1title Ubuntu, kernel 2.6.20-15-genericroot (hd0,8)kernel /boot/vmlinuz-2.6.20-15-generic root=hda9 ro quiet splashinitrd /boot/initrd.img-2.6.20-15-genericquietsavedefaulttitle Ubuntu, kernel 2.6.20-15-generic (recovery mode)root (hd0,8)kernel /boot/vmlinuz-2.6.20-15-generic root=hda9 ro singleinitrd /boot/initrd.img-2.6.20-15-genericls boot givesconfig@ kernel.h@ System.map-2.6.18.8.tex4config-2.6.18.8.tex4 kernel.h-2.6.18.8.tex4 us.kltgrub/ memtest-1.65.bin vmlinuz@initrd-2.6.18.8.tex4.img message-graphic vmlinuz-2.6.18.8.tex4initrd.img@ System.map@Bruno, Apologies for drawing attention to your age, I was just contrasting the difference in knowledge between various members of the mature surfers Scott

[tommyj12]

PS: What is this thing about my age ??

Maybe it's just that he would have to live much longer to be as wise as you are now. Enough with the arse kissing.... Scot next time you install ubuntu why not write the bootloader to the / that way you can just add it to pclos, and not have to go through this again. Trust me I have been exactly where you are, in fact my first post here was almost like this one. I learned a lot since then, and usually can get it right on my own now. All in the learning process.... Tommy

[Bruno]

Hi ScottMaybe a small change to the Ubuntu entry of your PCLos menu.lst:

title Ubuntu, kernel 2.6.20-15-genericroot (hd0,8)kernel /boot/vmlinuz-2.6.20-15-generic root=hda9 ro quiet splashinitrd /boot/initrd.img-2.6.20-15-genericsavedefaultboot

From there ( if indeed the 2.6.20-15-generic kernel is in /boot of the Ubuntu partition ) it should be able to boot . . . Bruno

[V.T. Eric Layton]

Scott,I wasn't curious about your menu.lst. I wanted to know which kernels were listed in the /boot of the hda9 partition (Ubuntu).

[snminc]

Morning All, Tommy, Everytime I think I'm ready to fly solo I end up crashing and burning but like your goodself I'll persevere.Bruno, I amended the menu.lst file as suggested with the same result I'm afraid the Kubuntu splash screen appears the alpha and scroll lock lights starting flashing SOS (I know how they feel ) But the harddrive light is suspiciously unlit.Any more ideas or should I try a re-install and if so to boot from where?Eric apologies if I misunderstood your postScott

[Bruno]

Hi ScottI think we can have one more go at it . . . please boot PCLos and mount your Ubuntu partition . . . I would like to see "ls -al /mnt/hda9/boot" so:

# mkdir /mnt/hda9# mount /dev/hda9 /mnt/hda9# ls -al /mnt/hda9/boot

Bruno

[V.T. Eric Layton]

No need to apologize, Scott. Bruno is also requesting the same information that I was previously. Knowing what is actually in /boot of hda9 would be helpful to us to assist you further. Follow Bruno's commands in the post just above this one.