Advertisement
Help Keep Boards Alive. Support us by going ad free today. See here: https://subscriptions.boards.ie/.
If we do not hit our goal we will be forced to close the site.

Current status: https://keepboardsalive.com/

Annual subs are best for most impact. If you are still undecided on going Ad Free - you can also donate using the Paypal Donate option. All contribution helps. Thank you.
https://www.boards.ie/group/1878-subscribers-forum

Private Group for paid up members of Boards.ie. Join the club.

Which Linux?

2»

Comments

  • Registered Users, Registered Users 2 Posts: 13,947 ✭✭✭✭Johnboy1951


    Boot the PC using a liveCD of any Linux and edit it from there.


  • Registered Users, Registered Users 2 Posts: 12,051 ✭✭✭✭L'prof


    Boot the PC using a liveCD of any Linux and edit it from there.

    Sound, I'll give it a go. I thought I tried that yesterday (when I did something similar) but I couldn't find it / didn't know where to look.


  • Registered Users, Registered Users 2 Posts: 535 ✭✭✭Dorsanty


    Hit 'e' when grub shows up to edit the values. Then 'b' to boot.

    Of course you'll need to know what was wrong with your edit. Then fix the menu.lst once you are up and running.
    menu.lst is in /boot/grub/


  • Registered Users, Registered Users 2 Posts: 12,051 ✭✭✭✭L'prof


    Dorsanty wrote: »
    Hit 'e' when grub shows up to edit the values. Then 'b' to boot.

    Of course you'll need to know what was wrong with your edit. Then fix the menu.lst once you are up and running.
    menu.lst is in /boot/grub/

    I think this worked. I knew what the code looked like so I knew what to change back anyway.

    I had this and what's in red didn't seem to boot properly:
    # grub.conf generated by anaconda
    #
    # Note that you do not have to rerun grub after making changes to this file
    # NOTICE:  You have a /boot partition.  This means that
    #          all kernel and initrd paths are relative to /boot/, eg.
    #          root (hd0,5)
    #          kernel /vmlinuz-version ro root=/dev/mapper/vg_jasonlaptop-lv_root
    #          initrd /initrd-version.img
    #boot=/dev/sda
    default=0
    timeout=5
    splashimage=(hd0,5)/grub/splash.xpm.gz
    hiddenmenu
    [COLOR="Red"]title Fedora (2.6.30.5-43.fc11.i586)
    	root (hd0,5)
    	kernel /vmlinuz-2.6.30.5-43.fc11.i586 ro root=/dev/mapper/vg_jasonlaptop-lv_root rhgb quiet
    	initrd /initrd-2.6.30.5-43.fc11.i586.img[/COLOR]
    title Fedora
    	root (hd0,5)
    	kernel /vmlinuz-2.6.29.4-167.fc11.i586 ro root=/dev/mapper/vg_jasonlaptop-lv_root rhgb quiet
    	initrd /initrd-2.6.29.4-167.fc11.i586.img
    title Windows Vista
    	rootnoverify (hd0,0)
    	chainloader +1
    

    And these are the changes I made:
    # grub.conf generated by anaconda
    #
    # Note that you do not have to rerun grub after making changes to this file
    # NOTICE:  You have a /boot partition.  This means that
    #          all kernel and initrd paths are relative to /boot/, eg.
    #          root (hd0,5)
    #          kernel /vmlinuz-version ro root=/dev/mapper/vg_jasonlaptop-lv_root
    #          initrd /initrd-version.img
    #boot=/dev/sda
    default=0
    timeout=5
    splashimage=(hd0,5)/grub/splash.xpm.gz
    hiddenmenu
    #title Fedora (2.6.30.5-43.fc11.i586)
    [COLOR="Red"]#[/COLOR]	root (hd0,5)
    [COLOR="Red"]#[/COLOR]	kernel /vmlinuz-2.6.30.5-43.fc11.i586 ro root=/dev/mapper/vg_jasonlaptop-lv_root rhgb quiet
    [COLOR="Red"]#[/COLOR]	initrd /initrd-2.6.30.5-43.fc11.i586.img
    title Fedora
    	root (hd0,5)
    	kernel /vmlinuz-2.6.29.4-167.fc11.i586 ro root=/dev/mapper/vg_jasonlaptop-lv_root rhgb quiet
    	initrd /initrd-2.6.29.4-167.fc11.i586.img
    title Windows Vista
    	rootnoverify (hd0,0)
    	chainloader +1
    

    I thought the # would ignore the rest of the line, just in case I made a mistake and needed to change it back.


Advertisement