Grub timing - Solved itself

[dangbert]

I downloaded the 2012.12 KDE torrent and did the install, which was flawless - well almost.  The problem is, Grub is not activating the delay before it goes to the default setting.  The only way around this is to keep hitting the "down arrow" as soon as the boot cycle clears the BIOS. Grub will pop up and you can make your selection as normal.  Without hitting the "down arrow" Grub flashes by so quickly as to be nothing more than a blur.

I have reset the delay in the CC,Boot, Setup Boot System to 30sec and there was no change.  

Before I start thrashing around in the dark and mysterious innards of the system, I thought I would ask some wiser and more seasoned heads.

Deb

[johnmart]

hmmm....that is how I set my grub timing.
You could check it manually to confirm that pcc is saving your setting.
/boot/grub/menu.lst (as root)

**the first entry**
timeout 04
color black/cyan yellow/cyan
gfxmenu (hd0,4)/boot/gfxmenu
default 0

Do you by chance have the system set to login your default user automatically?

[dangbert]

Menu.1st looks just like your sample, except the timeout is set to 10

Yes, I do have an autologon set, but then I always do that.  I am confused on why you asked.  What does the autologon have to do with the time the Grub Menu displays?

Thanks

Deb

[Just17]

Can you post the contents of your

/boot/grub/menu.lst

file please?

In case you have more than one OS installed please ensure the one you post is the one used by Grub.

[dangbert]

As requested.  The default is PCLinuxOS 2012.8

Deb

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

timeout 10
color black/cyan yellow/cyan
gfxmenu (hd0,5)/boot/gfxmenu
default 0

title PCLinuxOS 3.2.18-pclos2.pae.bfs
kernel (hd0,5)/boot/vmlinuz-3.2.18-pclos2.pae.bfs BOOT_IMAGE=PCLinuxOS_3218-pclos2paebfs root=UUID=e6a0995b-13b9-452f-a70c-b06d29d84d4e quiet nokmsboot vmalloc=256M acpi=on resume=UUID=9adb5ce2-8c4d-48a7-a945-baea5255df88 splash=silent vga=788
initrd (hd0,5)/boot/initrd-3.2.18-pclos2.pae.bfs.img

title PCLinuxOS 3.2.18-pclos2.bfs
kernel (hd0,5)/boot/vmlinuz-3.2.18-pclos2.bfs BOOT_IMAGE=PCLinuxOS_3.2.18-pclos2.bfs root=UUID=e6a0995b-13b9-452f-a70c-b06d29d84d4e quiet nokmsboot vmalloc=256M acpi=on resume=UUID=9adb5ce2-8c4d-48a7-a945-baea5255df88 splash=silent vga=788
initrd (hd0,5)/boot/initrd-3.2.18-pclos2.bfs.img

title PCLinuxOS 2012.2 (64 bit)
kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_2012.2_(64_bit) root=UUID=e6a0995b-13b9-452f-a70c-b06d29d84d4e quiet nokmsboot vmalloc=256M acpi=on resume=UUID=9adb5ce2-8c4d-48a7-a945-baea5255df88 splash=silent vga=788
initrd (hd0,5)/boot/initrd.img

title PCLinuxOS 2011.9
root (hd0,0)
configfile /boot/grub/menu.lst

title linux-nonfb
kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=e6a0995b-13b9-452f-a70c-b06d29d84d4e quiet nokmsboot vmalloc=256M acpi=on resume=UUID=9adb5ce2-8c4d-48a7-a945-baea5255df88
initrd (hd0,5)/boot/initrd.img

title failsafe
kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=e6a0995b-13b9-452f-a70c-b06d29d84d4e quiet nokmsboot failsafe vmalloc=256M acpi=on
initrd (hd0,5)/boot/initrd.img

title memtest-4.20
kernel (hd0,5)/boot/memtest-4.20 BOOT_IMAGE=memtest-4.20

title linux
kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=e6a0995b-13b9-452f-a70c-b06d29d84d4e quiet nokmsboot vmalloc=256M acpi=on resume=UUID=9adb5ce2-8c4d-48a7-a945-baea5255df88 splash=silent vga=788
initrd (hd0,5)/boot/initrd.img

[Just17]

title PCLinuxOS 3.2.18-pclos2.pae.bfs
kernel (hd0,5)/boot/vmlinuz-3.2.18-pclos2.pae.bfs BOOT_IMAGE=PCLinuxOS_3218-pclos2paebfs root=UUID=e6a0995b-13b9-452f-a70c-b06d29d84d4e quiet nokmsboot vmalloc=256M acpi=on resume=UUID=9adb5ce2-8c4d-48a7-a945-baea5255df88 splash=silent vga=788
initrd (hd0,5)/boot/initrd-3.2.18-pclos2.pae.bfs.img

Maybe the typo is interfering ......

pclos2pae.bfs

[dangbert]

OOPS !!!   Wrong file.  Well the right file from the wrong computer.  Just a moment.

Deb

[dangbert]

OOPS !!!   Wrong file.  Well the right file but from the wrong computer.  The Menu.1st on this computer works just fine.

Now for the really weird stuff.  I rebooted the other computer out of XP and was all ready for the Grub screen to flash by on its way to booting PCLinuxOS 2012.12.  Imagine my surprise when the Grub screen popped up and showed no indication that it was anything but what it should have been.

Back in the days when I was a technician, I used to hate it when the problem fixed itself.  For two reasons, 1) the Operators would never believe it and 2) You knew, all over again, life is just weird sometimes.

Thanks for the time

Deb

[Just17]

Best mark the first post heading with a [SOLVED] although you don't know the reason