GRUB 2 Introduction

**kstarkey1** · October 27th, 2009

Originally Posted by drs305

That happened because "update-grub" would have reset the value back to -1.

The only thing I can think of it to go through and select every item in your menu. If they work, perhaps it will reset the value of whatever is making the recordfail -1. That, as they say, is just a WAG.

I tried loading an incorrect splash image to see if that would freeze the menu, but it didn't. It just booted to the mono background.

I'm going to play around in a VM to see if I can duplicate it.

I gave it a shot and tried all the options from the boot screen (recovery mode, 2 memtest86+), but still no change. I ran update-grub again too.

I guess I'll move on to my printing issue now. If you all have any other suggestions, I'd love to hear them

Thanks again for all the help!

**ranch hand** · October 28th, 2009

Well, the onlything that I can think of is to get rid of the;

cat << EOF
if [ \${recordfail} = 1 ]; then
set timeout=-1
else
set timeout=${GRUB_TIMEOUT}
fi
EOF

part of your 00_header file (/etc/grub.d/00_header).

We know from the stuff that drs305 had you run that the lack of that in your menuentry does not hose your boot, and that you get a 3 second timeout on your menu.

I would hash out that whole section like so;
[code]
cat << EOF
## if [ \${recordfail} = 1 ]; then
## set timeout=-1
## else
## set timeout=${GRUB_TIMEOUT}
## fi
## EOF
[code]
and see what happens.

**kstarkey1** · October 28th, 2009

Originally Posted by ranch hand

Well, the onlything that I can think of is to get rid of the;

part of your 00_header file (/etc/grub.d/00_header).

We know from the stuff that drs305 had you run that the lack of that in your menuentry does not hose your boot, and that you get a 3 second timeout on your menu.

I would hash out that whole section like so;
[code]
cat << EOF
## if [ \${recordfail} = 1 ]; then
## set timeout=-1
## else
## set timeout=${GRUB_TIMEOUT}
## fi
## EOF
[code]
and see what happens.

Thanks for taking the time to help ranch hand!

I'm sorry to report, but it didn't make a bit of difference. I made the change, did sudo update-grub, rebooted, and after waiting about a minute at the grub2 menu I hit enter, and ...

I put the 00_header file back the way it was, just in case.

Any other ideas would be greatly appreciated!

(I'm not having any luck w/ my cups or touchpad issues either

)

**Paool** · October 28th, 2009

good introduction

ok, but I used to put 'apci=off' to menu.lst, where can I turn it off now?

**drs305** · October 28th, 2009

Originally Posted by Paool

good introduction

ok, but I used to put 'apci=off' to menu.lst, where can I turn it off now?

If you want it in normal boots, open /etc/default/grub:

Code:

gksudo gedit /etc/default/grub

Change this line (acpi=off to it if you already have "quite" and/or "splash"). Adding it to this line will cause normal boots to start with this option:

GRUB_CMDLINE_LINUX_DEFAULT="acpi=off"

Save the file, then run:

Code:

sudo update-grub

**Paool** · October 28th, 2009

works like a charm now, thank you very much!

**kstarkey1** · October 29th, 2009

Does anyone know whether it's possible that a future update will fix my grub2 boot menu issues?

I'm still really bummed that we can't fix this.

I'm not having any luck squashing my other bugs either

Any help would be greatly appreciated.

thx

**ranch hand** · October 29th, 2009

Grub 1.97 has been released. We are using 1.97beta4.

I am not sure what the change log is, I thought I had it bookmarked. It will probably be one of the early updates after release of 9.10.

If you filed the bug report, at least the Ubuntu devs know about the issue. It might be good to file with the grub devs too.

I hope the update fixes your problems. There are still several with grrub2.

The priority is probably the improvement of os-prober performance.

**andrewabc** · October 29th, 2009

Originally Posted by ranch hand

I am not sure what the change log is, I thought I had it bookmarked. It will probably be one of the early updates after release of 9.10.

Announcement

Changelog

**VMC** · October 29th, 2009

Originally Posted by kstarkey1

...I'm still really bummed that we can't fix this...

So your problem is that once you turn on your pc and presented with a grub2 menu, there is no count down timer to boot the default partition, correct?

output

Code:

sudo fdisk -l

and

Code:

sudo blkid

I know this may have nothing to do with anything, but just complete the picture. I feel your frustration. Also, you may have mentioned this before, but have you have any OS installed and any quirks with them?