Description of problem: After having reinstalled grub with the "grub-install /dev/sda" command, grub works fine except for the 'silent mode' that is not triggered : grub still displays 'booting Fedora (2.6.27.4-79.fc10.i686) in xx s" I can see the 'solar' grub background behind the letters but not around. Version-Release number of selected component (if applicable): grub-0.97-36.fc10.i386 How reproducible: always Steps to Reproduce: 1.open a terminal window, enter su - mode 2.type 'grub-install /dev/your_hd' 3.reboot Actual results: grub displays "booting Fedora (2.6.27.4-79.fc10.i686) in xx s" Expected results: 'silent mode' described there : http://fedoraproject.org/wiki/Features/BetterStartup#Tasks Additional info:
Is this a new installation or an upgrade? Could you attach your /etc/grub.conf?
(In reply to comment #1) > Is this a new installation or an upgrade? > > Could you attach your /etc/grub.conf? It is a fresh install. But I made a mistake in the first bug report. the exact command I typed was "grub-install /dev/sda2" where /dev/sda2 contains the fedora 10 install (WITH /boot, it is not a separate patition), and the command was run from this install. It is unlikely that a grub-install /dev/sda changed anything, right ? maybe grub-install have changed something in my /boot directory that led to this ? here is my grub.conf : # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You do not have a /boot partition. This means that # all kernel and initrd paths are relative to /, eg. # root (hd0,1) # kernel /boot/vmlinuz-version ro root=/dev/sda2 # initrd /boot/initrd-version.img #boot=/dev/sda default=0 timeout=3 splashimage=(hd0,1)/boot/grub/splash.xpm.gz hiddenmenu title Fedora (2.6.27.5-94.fc10.i686) root (hd0,1) kernel /boot/vmlinuz-2.6.27.5-94.fc10.i686 ro root=UUID=3034eca0-ba4d-4ec9-bef4-399b1c6a18f6 rhgb quiet vga=791 initrd /boot/initrd-2.6.27.5-94.fc10.i686.img
Are you sure you want to install grub to /dev/sda2? Usually /dev/sda is used. Are you sure anaconda installed bootloader on sda2? And why do you want to run grub-install at all? How is your disk layout? Output of "fdisk -l"? Where do you have and want which bootloader? But ... as far as I know then anaconda uses booty to write grub.conf. And as far as I can see it will always insert a chaintimeout line. So something is not what it pretends to be ... AFAIK booty also defaults to timeout=0, and that is what makes grub not display the "Booting %s in %d seconds..." message.
That's the scenario : * I installed F10 beta with the DVD on /dev/sda2. I let anaconda install the bootloader, and grub into /boot * I installed another distro on /dev/sda1 that erased the MBR. I managed to boot my F10 part with this distro's grub. * Then I wanted to reinstall the mbr but I made a mistake and typed grub-install /dev/sda2 . I know I shouldn't have done that but it also shouldn't have messed up with the 'silent mode' as it should install an F10 grub. * the reason why there is timeout=3 is because I changed it manually when grub used to run without errors (before the grub-install), and it worked, I mean, at least,it didn't make grub display anything. now : fdisk -l Disque /dev/sda: 120.0 Go, 120034123776 octets 255 heads, 63 sectors/track, 14593 cylinders Units = cylindres of 16065 * 512 = 8225280 bytes Disk identifier: 0x000a271d Périphérique Amorce Début Fin Blocs Id Système /dev/sda1 * 1 3265 26226081 83 Linux /dev/sda2 3397 5446 16466625 83 Linux /dev/sda3 3266 3396 1052257+ 82 Linux swap / Solaris /dev/sda4 5447 14593 73473277+ 83 Linux Les entrées de la table de partitions ne sont pas dans l'ordre du disque
I am pretty sure that running grub-install on sda2 didn't change anything if you also have installed on sda (unless you have a chainloader to sda2). But timeout=3 is really what causes the messages in grub: int print_message = grub_timeout != 0; ... if (print_message) grub_printf("\rPress any key to enter the menu\n\n\n"); ... if (print_message) grub_printf ("\rBooting %s in %d seconds...", What happens if you set timeout=0 ?
Duh... It works. my grub.conf originally had timeout=5 (I guess the beta installer put it this way) and it used to work. I just changed to timeout=3 because I used to do the same with older releases of fedora. I saw no change in the boot sequence until I ran grub-install. So I guess this is not a bug anymore...apart from making sure anaconda now puts timeout=0.... And this strange behavior (no background, except around the letters, but I guess this has to do with the grub_printf function) thanks !
If are feel like it you can set the status to close/worksforme. (I can't)