 |
 |
 |
 |
| Using Fedora General support for current versions. Ask questions about Fedora and it's software that do not belong in any other forum. |

22nd August 2012, 07:12 PM
|
|
Registered User
|
|
Join Date: Jul 2012
Location: Canada
Posts: 6

|
|
|
Grub arguments missing on boot
I just got a new ASUS UX32a, and put Fedora 17 on it, and to optimize the power settings, I added the following arguments to etc/default/grub:
Code:
pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1
Then, I ran the following:
Code:
grub2-mkconfig -o /boot/grub2/grub.cfg
And when I look at /boot/grub2/grub.conf, the new arguments are in there:
Code:
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub2-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default="${saved_entry}"
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if loadfont unicode ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Fedora' --class fedora --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-947f4334-8354-4986-8662-531a19246ce5' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set root='hd0,gpt7'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt7 --hint-efi=hd0,gpt7 --hint-baremetal=ahci0,gpt7 a180ac34-ef60-4d78-8565-2a875ddcb4d7
else
search --no-floppy --fs-uuid --set=root a180ac34-ef60-4d78-8565-2a875ddcb4d7
fi
echo 'Loading Linux 3.5.2-1.fc17.x86_64 ...'
linux /vmlinuz-3.5.2-1.fc17.x86_64 root=UUID=947f4334-8354-4986-8662-531a19246ce5 ro quiet rhgb acpi_backlight=vendor pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1
echo 'Loading initial ramdisk ...'
initrd /initramfs-3.5.2-1.fc17.x86_64.img
}
submenu 'Advanced options for Fedora' $menuentry_id_option 'gnulinux-advanced-947f4334-8354-4986-8662-531a19246ce5' {
menuentry 'Fedora, with Linux 3.5.2-1.fc17.x86_64' --class fedora --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.5.2-1.fc17.x86_64-advanced-947f4334-8354-4986-8662-531a19246ce5' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set root='hd0,gpt7'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt7 --hint-efi=hd0,gpt7 --hint-baremetal=ahci0,gpt7 a180ac34-ef60-4d78-8565-2a875ddcb4d7
else
search --no-floppy --fs-uuid --set=root a180ac34-ef60-4d78-8565-2a875ddcb4d7
fi
echo 'Loading Linux 3.5.2-1.fc17.x86_64 ...'
linux /vmlinuz-3.5.2-1.fc17.x86_64 root=UUID=947f4334-8354-4986-8662-531a19246ce5 ro quiet rhgb acpi_backlight=vendor pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1
echo 'Loading initial ramdisk ...'
initrd /initramfs-3.5.2-1.fc17.x86_64.img
}
menuentry 'Fedora, with Linux 3.3.4-5.fc17.x86_64' --class fedora --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.3.4-5.fc17.x86_64-advanced-947f4334-8354-4986-8662-531a19246ce5' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set root='hd0,gpt7'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt7 --hint-efi=hd0,gpt7 --hint-baremetal=ahci0,gpt7 a180ac34-ef60-4d78-8565-2a875ddcb4d7
else
search --no-floppy --fs-uuid --set=root a180ac34-ef60-4d78-8565-2a875ddcb4d7
fi
echo 'Loading Linux 3.3.4-5.fc17.x86_64 ...'
linux /vmlinuz-3.3.4-5.fc17.x86_64 root=UUID=947f4334-8354-4986-8662-531a19246ce5 ro quiet rhgb acpi_backlight=vendor pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1
echo 'Loading initial ramdisk ...'
initrd /initramfs-3.3.4-5.fc17.x86_64.img
}
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/20_ppc_terminfo ###
### END /etc/grub.d/20_ppc_terminfo ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows 7 (loader) (on /dev/sda3)' --class windows --class os $menuentry_id_option 'osprober-chain-0EEC3E6EEC3E5067' {
insmod part_gpt
insmod ntfs
set root='hd0,gpt3'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3 0EEC3E6EEC3E5067
else
search --no-floppy --fs-uuid --set=root 0EEC3E6EEC3E5067
fi
chainloader +1
}
menuentry 'Windows Recovery Environment (loader) (on /dev/sda5)' --class windows --class os $menuentry_id_option 'osprober-chain-B6BA44F7BA44B621' {
insmod part_gpt
insmod ntfs
set root='hd0,gpt5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt5 --hint-efi=hd0,gpt5 --hint-baremetal=ahci0,gpt5 B6BA44F7BA44B621
else
search --no-floppy --fs-uuid --set=root B6BA44F7BA44B621
fi
drivemap -s (hd0) ${root}
chainloader +1
}
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
Yet, when I boot and look at the arguments at boot-time in grub, my new arguments are missing. What do I do to get that updated? Thank you.
edit:
grub2-install -v gives me:
Code:
grub2-install (GRUB) 2.00~beta6
but the version of grub I see when I boot says version 0.97-03.fc17.
Last edited by sintheta; 22nd August 2012 at 07:20 PM.
|

23rd August 2012, 12:05 AM
|
|
Registered User
|
|
Join Date: Aug 2011
Posts: 697

|
|
|
Re: Grub arguments missing on boot
You are booting into Grub 1/legacy?
Also you seem to be using gpt & uefi? which I'm not yet familiar with
|

23rd August 2012, 01:10 AM
|
 |
Administrator
|
|
Join Date: Aug 2009
Posts: 6,612

|
|
|
Re: Grub arguments missing on boot
Did you upgrade from a previous release of Fedora?
Upgrades don't update the actual bootloader that is installed. It updates the packages on your system, but the actual bootloader code doesn't get updated.
try installing the updated bootloader.
Code:
su -
(root password)
grub2-install /dev/sda
Change the device to be the device you boot from.
|

23rd August 2012, 04:27 PM
|
|
Registered User
|
|
Join Date: Jul 2012
Location: Canada
Posts: 6

|
|
|
Re: Grub arguments missing on boot
This was a fresh install of Fedora 17, although I have since run yum upgrade on the system.
I just tried running grub2-install /dev/sda while root, and I got the following error message:
Code:
source_dir doesn't exist. Please specify --target or --directory
|

26th August 2012, 07:37 PM
|
|
Registered User
|
|
Join Date: Jul 2012
Location: Canada
Posts: 6

|
|
|
Re: Grub arguments missing on boot
Googling around, I tried specifying a target, but this only gets me an error message:
Code:
[root@localhost grub2]# grub2-install --target=i386-pc/ /dev/sda
/usr/sbin/grub2-bios-setup: warning: this GPT partition label contains no BIOS Boot Partition; embedding won't be possible.
/usr/sbin/grub2-bios-setup: warning: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged..
/usr/sbin/grub2-bios-setup: error: will not proceed with blocklists.
|

27th August 2012, 12:21 AM
|
 |
Registered User
|
|
Join Date: May 2005
Location: Sonoran Desert
Posts: 2,112

|
|
|
Re: Grub arguments missing on boot
Quote:
Originally Posted by sintheta
Googling around, I tried specifying a target, but this only gets me an error message:
Code:
[root@localhost grub2]# grub2-install --target=i386-pc/ /dev/sda
/usr/sbin/grub2-bios-setup: warning: this GPT partition label contains no BIOS Boot Partition; embedding won't be possible.
/usr/sbin/grub2-bios-setup: warning: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged..
/usr/sbin/grub2-bios-setup: error: will not proceed with blocklists.
|
I had the same error message trying to install grub2 to a partition (not the mbr). You can try
Code:
# grub2-install --force /dev/sdxy
No idea if that will work under your circumstances, but if your system isn't bootable it can't hurt.
|

27th August 2012, 03:07 AM
|
|
Registered User
|
|
Join Date: Jul 2012
Location: Canada
Posts: 6

|
|
|
Re: Grub arguments missing on boot
Thanks. Tried it, still no luck :\
It claimed to be a successful install, but when I rebooted it's still the old version of Grub.
|

27th August 2012, 04:26 AM
|
 |
Administrator
|
|
Join Date: Aug 2009
Posts: 6,612

|
|
|
Re: Grub arguments missing on boot
This error here explains it all:
Quote:
|
/usr/sbin/grub2-bios-setup: warning: this GPT partition label contains no BIOS Boot Partition; embedding won't be possible.
|
You have your boot drive set up with GPT partition table, not MBR. On a GPT disk, you must have a BIOS_Boot partition defined. (unless you are booting in uEFI mode)
If you have a few MB of free space on the drive, you can create you a BIOS_Boot partition, then grub2-install will work for you.
You can create your BIOS_Boot partition using either gdisk or gparted.
|

27th August 2012, 05:54 AM
|
 |
Registered User
|
|
Join Date: May 2005
Location: Sonoran Desert
Posts: 2,112

|
|
|
Re: Grub arguments missing on boot
And an EFI system?
http://ask.fedoraproject.org/questio...ng-grub-legacy
Since you get a grub 0.97 message, there may be a grub.conf file somewhere in /boot.
|

28th December 2012, 08:09 AM
|
|
Registered User
|
|
Join Date: Dec 2012
Location: Portsmouth, UK
Posts: 1

|
|
|
Re: Grub arguments missing on boot
I also run Fedora 17 on my UX32A. When I booted from the live USB there were two choices - EFI USB or standard USB.
I have found that by choosing the latter, I have no boot problems. Incidentally, using manual partitioning, I have the boot partition in Vfat and / on the SSD, with the home partition and swap area on the HD.
Mike
PS just joined the forum.
|
| Thread Tools |
Search this Thread |
|
|
|
| Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
Current GMT-time: 23:04 (Saturday, 25-05-2013)
|
|
 |
 |
 |
 |
|
|