[Solved] Change GRUB2 boot order

Sector11 · 2012-05-30 03:57:41

Solved: See post #2

{sigh} /boot/grub/menu.lst was sooooooooooooooooo easy.

I have read:
Where is /boot/grub/menu.lst?
where snowpine says:

1. The script snippets in /etc/grub.d/
2. The configuration file /etc/default/grub

And from other things read --- its:

/etc/grub.d/10_linux

that is the all important one there to edit that he's talking about in 1.

as well as a few other threads found here

Well Women are from Venus Men are from Mars and this Noob is from Pluto.

I tried something else from that thread:

GRUB_DEFAULT=2

because it starts at 0 - right?
At least that's what it is:

.. yea! That worked - NOT! so it's back at 0

sudo medit /etc/default/grub

# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`echo CrunchBang`
GRUB_CMDLINE_LINUX_DEFAULT="quiet nomodeset nouveau.modeset=0"
GRUB_CMDLINE_LINUX=" vga=769"

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"

On boot I see:

Debian <---> liquorix-amd64
Debian <---> liquorix-amd64 (recovery mode)
CrunchBang <---> 3.2.0-2-amd64 (on /dev/sda1)
CrunchBang <---> 3.2.0-2-amd64 (on /dev/sda1) (recovery mode)

so more reading ... it looks like:

/etc/grub.d/10_linux

that is the all important one there to edit ...

totally lost!

How do I get CrunchBang to be the default boot in GRUB2?

OH, I even installed 'startupmanager' --> total waste of time!

Last edited by Sector11 (2012-05-30 12:37:23)

VastOne · 2012-05-30 04:19:44

Interesting, I use startupmanager and it works fine... Can you define what it is or is not doing? I think I know, but need more info

So you want the CrunchBang <---> 3.2.0-2-amd64 (on /dev/sda1) to be the grub master?

Easy

Boot to that install

sudo grub-install /dev/sda

That brings back grub2 to that partition and it becomes the master grub and

CrunchBang <---> 3.2.0-2-amd64 (on /dev/sda1) will be the first shown

You will just have to remember to

sudo update-grub

on that install anytime you make a kernel upgrade on the Sid back 40 so that the master boot record picks up the new kernels

Anytime I install a new distro to test or build another Sid install, I always make sure that grub to installed to that partition and never let a new install become the master grubber... It is just easier for me that way

pvsage · 2012-05-30 05:10:47

Sector11 wrote:

GRUB_DEFAULT=2

Odd...this worked for me. Ya sure you remembered to `sudo update-grub` after editing it?

CBizgreat! · 2012-05-30 06:53:03

^ +1

Been a bit since messed with grub2, still using legacy and you just put whichever you want default as the 1st entry with it. With grub2, think you're on the right track, that'd be /etc/default/grub. Goes like this me thinks. Chit have babbled about this before, let me try n track down and copy paste that babble, in the interests of saving time. Here's the link 2 the related babble, post #10.

cbiz. smile

Last edited by CBizgreat! (2012-05-30 06:54:54)

gurtid · 2012-05-30 07:11:03

well changing the grub default has worked for me in the past also. U are working on the incorrect grub config file.

Sector11 · 2012-05-30 12:21:15

pvsage wrote:

Sector11 wrote:
GRUB_DEFAULT=2
Odd...this worked for me. Ya sure you remembered to `sudo update-grub` after editing it?

Yes. It was a given.

Last edited by Sector11 (2012-05-30 12:35:07)

Sector11 · 2012-05-30 12:24:55

CBizgreat! wrote:

^ +1
Been a bit since messed with grub2, still using legacy and you just put whichever you want default as the 1st entry with it. With grub2, think you're on the right track, that'd be /etc/default/grub. Goes like this me thinks. Chit have babbled about this before, let me try n track down and copy paste that babble, in the interests of saving time. Here's the link 2 the related babble, post #10.

cbiz.

Yes, I read that and my post reflects that I did that and did

sudo update-grub

after as well.
Just didn't work.

Sector11 · 2012-05-30 12:26:32

gurtid wrote:

well changing the grub default has worked for me in the past also. U are working on the incorrect grub config file.

Look at my first post:

sudo medit /etc/default/grub

I'm doing everything it said to do. It just didn't work.

Sector11 · 2012-05-30 12:34:17

VastOne wrote:

Interesting, I use startupmanager and it works fine... Can you define what it is or is not doing? I think I know, but need more info

I start it, enter my password and a little box comes up saying it's doing something.

When the screen opens it says the Default boot OS is:

CrunchBang <---> 3.2.0-2-amd64 (on /dev/sda1)

Closed the program and booted to see:

Debian <---> liquorix-amd64
Debian <---> liquorix-amd64 (recovery mode)
CrunchBang <---> 3.2.0-2-amd64 (on /dev/sda1)
CrunchBang <---> 3.2.0-2-amd64 (on /dev/sda1) (recovery mode)

VastOne wrote:

So you want the CrunchBang <---> 3.2.0-2-amd64 (on /dev/sda1) to be the grub master?
Easy
Boot to that install
sudo grub-install /dev/sda
That brings back grub2 to that partition and it becomes the master grub and
CrunchBang <---> 3.2.0-2-amd64 (on /dev/sda1) will be the first shown
You will just have to remember to
sudo update-grub
on that install anytime you make a kernel upgrade on the Sid back 40 so that the master boot record picks up the new kernels
Anytime I install a new distro to test or build another Sid install, I always make sure that grub to installed to that partition and never let a new install become the master grubber... It is just easier for me that way

Now that worked. Which is interesting for two reasons:

1. both are on /dev/sda
- sda1
- sda6
2. In my quest, searching here and on Google, I never came across that little trick.

NOTE Self: Remember to put only ONE grub on the MBR.

Thank you VastOne.

Last edited by Sector11 (2012-05-30 12:34:40)

CBizgreat! · 2012-05-30 12:47:55

*** EDIT *** ... Ya solved it while I was typing this BOOK !!! Arghhhh, oh well, at least ya solved it.

Do +1 what gurtid said. Someone definitely has to make sure they're editing the /etc/default/grub file in the OS that controls the boot ( or make that the RIGHT file, for the OS you're trying to change something in.) and like you already know, any changes made need the "sudo update-grub" to take effect. Which you've done ... am kinda confused here. Not sure what's/where ... how many are involved etc.

Stuff like this is the reason I still use legacy. Though the other 2 distro's onboard use grub2 and haven't had any issues with them. You do more distro juggling than I do ( multibooting) by far. If you have a buncha kernels installed for each on top of it. Can see where it'd quickly get complicated managing them all. Only thing can think to suggest and not at all sure it'll help. Is ... theorhetical scenario here.

I have distro a ... Use grub2 as it's bootloader ( it's the one handling the boot process ... mbr). It's setup to boot distro b in it's /etc/default/grub file. As the default choice, after GRUB_TIMEOUT=5. When the pc boots, after the 5secs, distro a's grub2 boots distro b. And passes it off to distro's b's bootloader to do the rest.

Additional babble ( sheesh am confusing myself now.) Let's say I want to.
1. Tell distro a, not to boot distro b anymore ... I want it to boot itself with kernel x instead. Then I'd have to edit distro a's /etc/default/grub or otherwise fiddle with it's bootloader to get that done.
2. However if wanted distro b still to be the default, but wanted IT to boot another kernel I had installed on it. Then I'd need to edit distro b's /etc/default/grub to get that done.
Of course again, doing "sudo update-grub" in either distro a or distro b. After making any changes to it's /etc/default/grub file.

Not sure what's going on there. Kinda suspect you're getting caught up in a maze of chainloading bootloaders probs. If you haven't might check out Xaos52's how to on the subject here. I don't mess with custom_40 and etc though. Hope any of this babble helps ya sort it out though Sector.

More babble: My pc has 3 distro's + XP. Grub legacy boots xp default after 4secs ( for the gf.) If I select one of the two OS's with grub2, legacy passes the boot process off to that OS's bootloader. Which I've got both of them set to boot the default kernel I want w/o any timeout in their /etc/default/grub files. aka: Set to GRUB_TIMEOUT=0 But I don't do alot of fiddling around with tons of kernels, one OS has only 1 kernel installed on it, the other only has 2 on it. Blahblahblah ... just trying to be thorough etc. Glad ya got it sorted out Sector. smile

cb. smile

Last edited by CBizgreat! (2012-05-30 13:07:43)

gurtid · 2012-05-30 13:37:36

Sector11 wrote:

gurtid wrote:
well changing the grub default has worked for me in the past also. U are working on the incorrect grub config file.
Look at my first post:
sudo medit /etc/default/grub
I'm doing everything it said to do. It just didn't work.

i've only ever edited /boot/grub/grub.cfg files and it always seems to work for me . . . am i doing it wrong?

. . . anyway u solved it by another means

Sector11 · 2012-05-30 13:40:25

CBizgreat! wrote:

*** EDIT *** ... Ya solved it while I was typing this BOOK !!! Arghhhh, oh well, at least ya solved it.
Do +1 what gurtid said. Someone definitely has to make sure they're editing the /etc/default/grub file in the OS that controls the boot ( or make that the RIGHT file, for the OS you're trying to change something in.) and like you already know, any changes made need the "sudo update-grub" to take effect. Which you've done ... am kinda confused here. Not sure what's/where ... how many are involved etc.
... just trying to be thorough etc. Glad ya got it sorted out Sector.
cb.

Are you talking "Advantage of chain-loading" with GRUB Legacy? It seems that you are matching my little cheat sheet for that almost parallel. Excepy you have two other distros using GRUB2. Definitely more distro juggling, your words, than I do.

AND ----> you said something very important!!!!!!

When I responded to "gurtid" and said I was working on such and such a file --- the

U are working on the incorrect grub config file.

just didn't click.

You just gave the key where I was going wrong: A silly noob mistake:

they're editing the /etc/default/grub file in the OS that controls the boot. Obviously the last install controls the grub. Obvious now, that is!!!!

DUH!!!!!!!!!!!!!!!

@ gurtid - a 1000 apologies and thank you.

Time to update my cheat-sheet ....

Sector11 · 2012-05-30 14:15:38

gurtid wrote:

i've only ever edited /boot/grub/grub.cfg files and it always seems to work for me . . . am i doing it wrong?
. . . anyway u solved it by another means

My /boot/grub/grub.cfg says:

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###

Just an opinion here but GRUB2 could take some lessons from GRUB Legacy of the easy of configuring it. Because it is not user friendly. Oh sure, you know scripts and such ... but come on ... in /boot/grub/ there are 207 files. And most places I went to never mentioned /boot/grub/grub.cfg - they talk about /etc/default/grub.

And most places I Googled talked about GRUB2 and Windows - almost like people don't dual boot two, or more, Linux systems and NO Windows. The same happened when I Googled about GRUB Legacy.

One of the best things going (if I remember to use it: - )
I keep telling people: my forgetter is getting better!

Google: change GRUB2 boot order -windows

Someone that knows the ins and outs of GRUB2 and dual-booking 'list ordering' should really do a nice HowTo.

Somewhere just today I saw something like this....

Last Loaded Distro = 0
Last Loaded Distro (recovery mode) = 1
2nd Last Loaded Distro = 3
2nd Last Loaded Distro (recovery mode) = 4
etc
etc

And I'm guessing here but if you have unused kernels:

Last Loaded Distro - Liquorix = 0
Last Loaded Distro - Liquorix (recovery mode) =1
Last Loaded Distro (old kernel) = 2
Last Loaded Distro (recovery mode) = 3
2nd Last Loaded Distro - Liquorix = 4
2nd Last Loaded Distro - Liquorix (recovery mode) = 5
2nd Last Loaded Distro = 6
2nd Last Loaded Distro (recovery mode) = 7
etc
etc

I think the trick is like VastOne said. One GRUB on the MBR!!!! One Grub To Rule Them All!

VastOne wrote:

Anytime I install a new distro to test or build another Sid install, I always make sure that grub is installed to that partition and never let a new install become the master grubber... It is just easier for me that way

NOTE: is - my edit

Last edited by Sector11 (2012-05-30 14:16:27)

VastOne · 2012-05-30 15:29:38

Sector11 wrote:

Now that worked. Which is interesting for two reasons:
1. both are on /dev/sda
- sda1
- sda6
2. In my quest, searching here and on Google, I never came across that little trick.
NOTE Self: Remember to put only ONE grub on the MBR.
Thank you VastOne.

Sure... I am glad it worked out.. big_smile

/dev/sda is the MBR and the whole disk , sda1 and sda6 are partitions of it..

That is the Master part of MBR smile

Sector11 · 2012-05-30 17:38:50

VastOne wrote:

Sure... I am glad it worked out..
/dev/sda is the MBR and the whole disk , sda1 and sda6 are partitions of it..
That is the Master part of MBR

Yea, that makes sense. And I probably would have come up with that on my own at some point but I'm running in at least half a dozen directions here at the moment. Just super glad to have #! back at #1 slot for my wife. If she turned the computer on and went to the kitchen for something ... and came back to see Xfce4!

"Where's my mail? What's this?" mad

"You're in the back 40 dear!" responding cool

"I want my mail YA!" mad

"Yes, dear!" sometimes people have no sense of humour. roll lol

I'm kidding of course, she knows it's there.

CrunchBang Linux

SEARCH

#1 2012-05-30 03:57:41

[Solved] Change GRUB2 boot order

#2 2012-05-30 04:19:44

Re: [Solved] Change GRUB2 boot order

#3 2012-05-30 05:10:47

Re: [Solved] Change GRUB2 boot order

#4 2012-05-30 06:53:03

Re: [Solved] Change GRUB2 boot order

#5 2012-05-30 07:11:03

Re: [Solved] Change GRUB2 boot order

#6 2012-05-30 12:21:15

Re: [Solved] Change GRUB2 boot order

#7 2012-05-30 12:24:55

Re: [Solved] Change GRUB2 boot order

#8 2012-05-30 12:26:32

Re: [Solved] Change GRUB2 boot order

#9 2012-05-30 12:34:17

Re: [Solved] Change GRUB2 boot order

#10 2012-05-30 12:47:55

Re: [Solved] Change GRUB2 boot order

#11 2012-05-30 13:37:36

Re: [Solved] Change GRUB2 boot order

#12 2012-05-30 13:40:25

Re: [Solved] Change GRUB2 boot order

#13 2012-05-30 14:15:38

Re: [Solved] Change GRUB2 boot order

#14 2012-05-30 15:29:38

Re: [Solved] Change GRUB2 boot order

#15 2012-05-30 17:38:50

Re: [Solved] Change GRUB2 boot order

Board footer