Now it's:
Ubuntu
Memtest
Windows 7
I want:
Windows 7
Ubuntu
Memtest
How do I go about doing it? Do I rename "30_os-prober" in /etc/grub.d/ to "10_os-prober" and "10_linux" to "30_linux"?
As it stands right now, Grub2 seems to generate menu entries in this order (for my pc)
Ubuntu 2.6.32-22
Ubuntu 2.6.32-22 (recovery)
Ubuntu 2.6.32-21
Ubuntu 2.6.32-21 (recovery)
Windows XP
How can I make it so that Grub generates entries in this order
Ubuntu 2.6.32-22
Windows XP
Ubuntu 2.6.32-22 (recovery
Ubuntu 2.6.32-21
Ubuntu 2.6.32-21 (recovery)
If you're wondering why I care about the order, its because I just installed Grub with an icon based theme. In that situation, it looks silly to have 4 Ubuntu Icons next to each other, and then the windows one at the end.
It's quite easy to change the default boot entry through etc/default/grub. However, this only allows for the first entry to be changed. I want to be able to move all the entries in any order I like. What is the best/easiest way to do this?
View 1 Replies View RelatedMy grub2 boot entries never change. I have run sudo update-grub and it finds all the proper kernels and such and says that it has updated. I check with the menu.lst and grub.cfg and they both look to be correct
View 13 Replies View RelatedSo my grub menu is showing several selections for each of my OS's. In Ubuntu, my OS of choice for now, how can I access the grub and edit it.
I would like to know the steps for console, but also I hope somebody can show me how to use Super Grub to do it.
Just installed Ubuntu 10.4 on a computer that normally runs XP Pro. I used a separate drive and unplugged the windows drive while installing Ubuntu (error number one right?). Ubuntu installed perfectly, plugged in windows drive, Windows boots perfectly. My only problem is that I don't have the boot list option unless I go into the BIOS and change default boot drive every time I want to switch OS.After a bit of research I configured GRUB to allow me to dual boot (Windows did not appear at first), but it boots directly into Ubuntu (fine for me, but my mother uses XP for work) instead of Windows. Unfortunately I have some sort of keyboard issue that makes the arrow keys inoperable until the machine has once booted into an OS.
View 8 Replies View RelatedMy GRUB is working fine, but I want windows to be first on the list. How can i change it?
View 2 Replies View RelatedI've just got a question about this. What if you wanted to change only the display sequence in Grub 2 (Ubuntu 9.10) and not which o/s boots first or is the deault o/s? In previous versions of grub you could just copy & paste the lines in /boot/grub/menu.lst, but this version of grub doesn't allow you to edit /boot/grub/grub.cfg...
View 11 Replies View RelatedI may be in the wrong section here (hardware) but I do believe this is a hardware issue. If indeed it is not, I welcome any admins to move this post to the correct section. That said, here's the issue:After years of frustration and problems with Windows XP, my parents finally asked me to install a Linux distro onto their machine. Taking their needs and lack of experience outside Windows in mind, I suggested Ubuntu and Linux Mint to them (as I do to pretty much anyone who wants an easy and beginner-friendly distro). Running first Mint's live session and then Ubuntu's on my own machine to give them an idea of how their new desktop would look, they picked Ubuntu and I grabbed the disk, my external hard drive, and proceeded to back up all their pics, music, docs, etc onto the external.
Once finished, I popped Ubuntu (10.04 LTS) into their machine for a reboot. Realizing when the Windows XP logo came up that the boot order is set to boot from the hard drive first, I went into BIOS and changed the boot order to check the appropriate DVD drive first (they have two DVD drives, both can and have burned onto DVDs without issue), and then the hard drive. Saving my changes and exiting, I did another reboot.I got as far as the splash screen where the dots under the Ubuntu logo lit up as normal, and then after a bit of a wait on my part, suddenly exits to a screen with a prompt telling me a boot device could not be found. Trying again with Linux Mint proved similar.Next I tried simply letting it boot into Windows as normal where I could then use Wubi to install Ubuntu beside Windows but again, the screen got as far as the Windows logo with the blue "loading bar" underneath and then would simply reboot. Having to focus my attention elsewhere for a couple minutes I found out upon return that the system was stuck in an endless loop of rebooting, asking to select between a safe mode, normal boot and last known configuration for Windows, then to the logo and starting over again.I went back into the BIOS and returned the settings to booting from the hard drive first as before (nothing else had been changed), and attempted another reboot. Same loop.I had made a boot "stick" for Ubuntu some time ago, and I've used it once when installing Ubuntu on a friend's laptop which had a broken CD drive. After it wouldn't boot from the USB device I looked in BIOS and selected "look for other devices to boot from" as there was not option to boot from USB in the standard option list (just hard drive, DC/DVD, and disabled). Still no luck.
Calling up my self-proclaimed computer expert uncle, he assured me that returning the BIOS to its default settings would allow it to boot normally back into Windows, probably after performing a disk check.Taking his advice I returned the BIOS to its default settings and reboot. No change, same loop! Frustrated I called him up again, and he said he'd have a look at it when he next gets a chance. heh. That may not be for a while as he is known for taking on projects he can't (or won't) finish.Anyway, tired and now uncertain, I thought perhaps it's something to do with a live disk. I tried an openSUSE installation disk and ended up with "please insert disk 1 into drive" prompt after selecting "install" from the first menu on the disk.
I'm working my way through my Linux self-education and I'm hitting a slight road block. After consulting forum posts here and elsewhere, I have tried to alter my grub boot order by editing my menu.lst file found in /boot/grub. I don't seem to be having any luck. Changing the default [value] doesn't seem to work, nor does the savedefault. Below is a copy of my file.
Code:
# 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 4
# 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 use 'savedefault' or your
# array will desync and will not let you boot your system.
default0
## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout10
## 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
# titleWindows 95/98/NT/2000
# root(hd0,0)
# makeactive
# chainloader+1
# titleLinux
# 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=18250e14-e47e-4bf9-a927-6456120575f8 ro
## default grub root device
## e.g. groot=(hd0,0)
# groot=18250e14-e47e-4bf9-a927-6456120575f8
## 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=0x317 resume=/dev/hda5
# defoptions=vga=0x317
## 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
## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false
## ## End Default Options ##
splashimage=18250e14-e47e-4bf9-a927-6456120575f8/boot/grub/splash.xpm.gz
titleBackTrack 4 R2, kernel 2.6.35.8
uuid18250e14-e47e-4bf9-a927-6456120575f8
kernel/boot/vmlinuz-2.6.35.8 root=UUID=18250e14-e47e-4bf9-a927-6456120575f8 ro quiet splash
initrd/boot/initrd.img-2.6.35.8
quiet
titleBackTrack 4 R2, kernel 2.6.35.8 (recovery mode)
uuid18250e14-e47e-4bf9-a927-6456120575f8
kernel/boot/vmlinuz-2.6.35.8 root=UUID=18250e14-e47e-4bf9-a927-6456120575f8 ro single
initrd/boot/initrd.img-2.6.35.8
titleBackTrack 4 R2, memtest86+
uuid18250e14-e47e-4bf9-a927-6456120575f8
kernel/boot/memtest86+.bin
quiet
### END DEBIAN AUTOMAGIC KERNELS LIST
# This is a divider, added to separate the menu items below from the Debian
# ones.
titleOther operating systems:
root
# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda1
titleWindows Vista/Longhorn (loader)
root(hd0,0)
savedefault
makeactive
chainloader+1
I am upgrading a system to have encrypted disks, it's a two disk system, so I want the BIOS to look at /dev/hdb first to unlock it, then it should reboot, see that isn't a system disk and try to boot /dev/hda. Then that gets unlocked, and the system boots. After unlocking hdb I get a Grub error 17. I can't edit Grub to look at hda as on normal boot it hasn't been unlocked yet, so it can't see the file system at that point. I reformatted an old XP disk as hdb, and it worked fine, but I'd rather not install windows every time, just to reformat it as ext3. Is there a simple way of clearing the boot sector of hdb?
View 4 Replies View RelatedMy boot order has automatically changed, before I was booting Windows XP/ Vista as the default OS, now all of the sudden Fedora has become the default OS. So plz help me change the boot order. These are my grub settings at the moment.
# 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.
[code].....
I installed Ubuntu in my new notebook. It originally comes with Windows 7 installed on it.Everything works nice however every time i boot into Windows7 the grub menu doesn't work any more. i can't boot into windows or ubuntu any more. How do I stop this? Its rather annoying to have to boot, chroot and fix this problem everytime.
View 1 Replies View Relatedi downloaded backtrack 4 (final) and booted the iso onto a flash drive using unetbootin. i then changed the boot order so the flash drive was first. after i did that i got into backtrack 4 did the install.sh and now i cant boot windows 7. even after changing the boot order to default, i turn my computer on and get a message that says:
Ubuntu 8.10, kernel 2.6.30.9
Ubuntu 8.10, kernel 2.6.30.9 (recovery mode)
Ubuntu 8.10, memtest86+
Other operating systems :
Memory Test (on /dev/sda1)
Ubuntu 8.10, kernel 2.6.30.9 (on dev/sda1)
Ubuntu 8.10, kernel 2.6.30.9 (recover mode) (on dev/sda1)
Ubuntu 8.10, memtest86+ (on dev/sda1)
[Code]....
i can only boot backtrack 4 OS, i really want to know what can i do to be able to boot my windows 7 home premium os.
I recently upgraded to Ubuntu 10.04 from earlier versions. I have a dual boot system with Windows 7. Grub was set to boot Windows by default Things were working fine. I decided to upgrade to Grub2. It seemed like a good idea at the time. Now when booting up,the name at the top of the Grub menu is 1.98, which is Grub 2. When I run grub-install -v, it comes back grub-install (GNU GRUB 0.97) which is not Grub2. Now when I boot up, Ubuntu 10.04 is the default. I have to manually choose Windows if I want to use that system. I have been unable to change the boot order following instructions from this site. Any Way changing the boot order to make Windows 7 the default. I am using a Toshiba Satellite.
View 5 Replies View RelatedIntalled GRUB using Live CD. My problem is very similar to these..
Code:
1. sudo grub-install --root-directory=/mnt /dev/sda
2. sudo mount -o bind /dev /mnt/dev
3. sudo mount -t proc none /mnt/proc
[Code]....
There are 2 osx entries in the grub menu one is 32-bit and the other is 64-bit, how i can get rid of the 32-bit one? i am using ubuntu 10.4 and snow leopard 10.6.3
View 9 Replies View RelatedIt is needed because of my portable audio player does not order entries and just leaves it as in FAT directory.
Current way of handling this is only moving files around and re-creating directories and placing files there in correct order (keeping in mind where are "holes" in directory list that will be filled by new file in placed to that directory).
What is the more proper way of doing it? (Apart from re-creating all directories each time or using hex editor on disk).
i'm using ubuntu 9.10... i'm working on some projects on L4 microkernel... i want to add it to the grub...i was familiar with the earlier grub, i.e editing the menu.lst...
title = L4Ka:istachio/i586 pingpong
kernel=/boot/kickstart
module=/boot/i586-kernel
module=/boot/sigma0
module=/boot/pingpong
how can i do this in new grub version...? i tried adding the following to /etc/grub.d/40_custom but failed...
menuentry "L4Ka:istachio" {
set root=(hd0,9)
kernel=/boot/kickstart[code ]..........
grub is giving me six (6!) repetitions of my Ubuntu Lucid install on sda5, five repetitions of my old karmic install on sda1, and I think four of the recovery option.Where have I told it to do that? How do I fix it??The grub choices look like this:
Code:
most recent lucid kernel on sda5
most recent lucid kernel recovery option
[code]....
I have a dual-boot grub2. On the list, there are Ubuntu 10.04, Memtest x86, and Windows7. I was wondering if it is possible to make Windows 7 first in the grub boot list. At the moment Ubuntu is first, so if it's possible to make windows 7 first.
View 2 Replies View RelatedI have made a custom grub2 menu however, both the default and the custom show together. So my grub looks like the list below, the bolded entries are my custom ones. How do I get rid of the duplicates? I have tried apt-get remove and deleting old kernels.
ubuntu,linux ...
ubuntu,linux recovery
memtest
memtest
windows7
windows7
ubuntu linux
ubuntu linux recover
i have an entry in grub that i don't use at all "Windows recovey " and i want to know if there is a way to remove it or just hide it i have an other problem is grub confuses some partitions names so is there a way to rename them
View 3 Replies View RelatedI have been fooling around with some of the new kernels and have ended up with a lot of options in my grub at boot. I have been checking this page:[URL].. ... and it appears hiding the entries in grub2 is not as easy as hashing them out (#) which was the convention in grub.
My problem: I have installed kernel 2.6.36 and 2.6.37 just to fool around. Neither works in anything but low-graphics as it seems the ATI graphics driver is not working in either yet. They both also kill my wireless (don't recognise the card). BUT I don't want to completely uninstall them as I'd like to keep playing around as time goes on and they develop. I'd like to just hide them from the menu.
Is there some easy way of doing this? The link I provide only gives options to make the kernel non-executable (overly complicated process) or remove the kernel completely, neither of which I want to do. This used to be simple in grub, open a file and add or remove a #, and - although overall I prefer grub2 - IMHO this 'improvement' seems a little like a backward step. Sure a million people will disagree, but .
I got a new ipod touch the other day and have been unable to get anything to read it properly. it automounts just fine and i can browse the file system. Normally with my old ipod i just used gtkpod and it worked fine. With gtkpod you have to tell it where the ipod is mounted. The problem is that i cannot see where the ipod touch is mounted It is connected right now and i can see it in nautilus and i can browse the file system, however...
[code]...
Partition table entries are not in disk order. what the?
When I originally installed Ubuntu 9.10 64 bit, I had the following operating systems already installed:
Kubuntu 9.04
Windows 7
Windows XP
Ubuntu automagically created a GRUB2 menu that offered all of these, plus of course itself, which was fine for a while.
Later on, I deleted and reformatted the partitions that had been dedicated to Kubuntu 9.04. GRUB2 has failed to keep up. Despite running "sudo update-grub" multiple times, the GRUB2 menu continues to show entries for Kubuntu 9.04.
How do I get rid of these obsolete entries? The partitions it was on simply do not exist any longer, so I don't know how GRUB2 is picking it up.
I had already edited my fstab file to reflect the new partitioning scheme, so I don't know where GRUB2 is getting the idea that I still have Kubuntu 9.04 installed.
i have been running Kubuntu 10.04 on my primary hard drive, and i have a second 1.5TB HD that i use for storage. so shrunk the secondary HD partition and created a second 50GB partition and i installed Ubuntu 10.10 on it and told it to rewrite the mbr on my primary HD. Where i am at: i took the menu entry from my Kubuntu "grub.cfg" and the entry from my Ubuntu "grub.cfg" and put them in the 40_custom file. so now when i boot-up my computer, it shows both installations at the bottom of Grub2s menu list. with all the menu entries that Grub automatically adds.
What i would like to know is how do i make it so that the Grub2 menu only shows the entries that i add to the 40_Custom file and not the randomly generated list aswell.
Is it possible to add menu entries for older kernels to boot instead of the latest?
I have tried this in Ubuntu 10.04 and it hasn't worked.
This used to be possible with ease in grub legacy.
I copied the current menu entry from /boot/grub/grub.cfg and pasted it in the /etc/grub.d/ 20_custom file.
Then I changed the kernel number to the older kernel number and the initrd number too. #update-grub puts this entry into 'grub.cfg', but it doesn't work.
I get:
The old kernel is in /boot as well as the respective initrd and config files.
I have been reading this but could not resolve my issue: [URL]. The problem is as follows. I got a samsung laptop and there is some kind of recovery utility installed. After installing Ubuntu I get too windows grub entries, one is called Windows Vista (loader) on /dev/sda1 and the other one is Windows 7 (loader) on /dev/sda2. The latter is correct and the first one is something that I'd rather not have active at all in the grub menu. Both of them are of course created by 30_os-prober in /etc/grub.d. I figured that I would most likely prefer a custom entry for Windows 7 and remove the x flag from 30_os-prober. I tried to create a file 50_windows7 in a described manner:
#! /bin/sh -e
echo "Adding Windows 43_custom" >&2
menuentry "Windows Vista 43_custom" {
insmod ntfs
set root=(hd0,2)
search --no-floppy --fs-uuid --set 7cecddfbecddb01e
chainloader +1 }
Unfortunately during update-grub I get following:
Found linux image: /boot/vmlinuz-2.6.31-17-generic
Found initrd image: /boot/initrd.img-2.6.31-17-generic
Found linux image: /boot/vmlinuz-2.6.31-14-generic
Found initrd image: /boot/initrd.img-2.6.31-14-generic
Found Windows Vista (loader) on /dev/sda1
Found Windows 7 (loader) on /dev/sda2
Adding Windows 43_custom
/etc/grub.d/50_windows7: 4: menuentry: not found
I like to load other distro's via their own grub.
So at the min I add an entry to code...
however when update-grub2 is run it also adds its own entries (for arch linux).
Is there a way to stop the update-grub2 script automatically adding a entry on a specific partition ?