/etc/default/grub is missing on my newly installed F20. What's replacing its functionality?
On 12/21/13 17:43, Erik P. Olsen wrote:
/etc/default/grub is missing on my newly installed F20. What's replacing its functionality?
It is there on mine....
[egreshko@f20f default]$ ll /etc/default/grub -rw-r--r--. 1 root root 382 Dec 19 06:34 /etc/default/grub
On 21/12/13 16:25, Ed Greshko wrote:
On 12/21/13 17:43, Erik P. Olsen wrote:
/etc/default/grub is missing on my newly installed F20. What's replacing its functionality?
It is there on mine....
[egreshko@f20f default]$ ll /etc/default/grub -rw-r--r--. 1 root root 382 Dec 19 06:34 /etc/default/grub
Weird. To verify I made an F20 installation on a virtual machine and there it was.
I'll do another F20 installation to see if it shows up this time. If not I suppose it is hardware related. Maybe anaconda doesn't like bios with uefi turned off. I had no problems with F19 though.
On 21/12/13 16:48, Erik P. Olsen wrote:
On 21/12/13 16:25, Ed Greshko wrote:
On 12/21/13 17:43, Erik P. Olsen wrote:
/etc/default/grub is missing on my newly installed F20. What's replacing its functionality?
It is there on mine....
[egreshko@f20f default]$ ll /etc/default/grub -rw-r--r--. 1 root root 382 Dec 19 06:34 /etc/default/grub
Weird. To verify I made an F20 installation on a virtual machine and there it was.
I'll do another F20 installation to see if it shows up this time. If not I suppose it is hardware related. Maybe anaconda doesn't like bios with uefi turned off. I had no problems with F19 though.
OK, this new F20 system (the third) produced the missing file!
On Dec 21, 2013, at 8:48 AM, Erik P. Olsen epodata@gmail.com wrote:
I'll do another F20 installation to see if it shows up this time. If not I suppose it is hardware related. Maybe anaconda doesn't like bios with uefi turned off. I had no problems with F19 though.
I forget if it's still possible to disable the install boot loader feature on UEFI. It's a meaningless option, except that /etc/default/grub will not be created. grub2-efi is still installed, shim.efi is still installed, and you do in fact still get a boot loader installed on UEFI systems regardless of this option. And I think there's a RHBZ on this issue also, but I don't know if that's been implemented in F20.
Chris Murphy
On 21/12/13 19:44, Chris Murphy wrote:
On Dec 21, 2013, at 8:48 AM, Erik P. Olsen epodata@gmail.com wrote:
I'll do another F20 installation to see if it shows up this time. If not I suppose it is hardware related. Maybe anaconda doesn't like bios with uefi turned off. I had no problems with F19 though.
I forget if it's still possible to disable the install boot loader feature on UEFI. It's a meaningless option, except that /etc/default/grub will not be created. grub2-efi is still installed, shim.efi is still installed, and you do in fact still get a boot loader installed on UEFI systems regardless of this option. And I think there's a RHBZ on this issue also, but I don't know if that's been implemented in F20.
I don't think there is an option to disable boot loader feature (or rather I haven't found it :-) The bios of my system is uefi capable but I have disabled it. Anyhow my last F20 build did produce /etc/default/grup even though I didn't make any change to the installation procedure. But I did use netinst so some changes may have come in this way.
On Dec 21, 2013, at 12:38 PM, "Erik P. Olsen" epodata@gmail.com wrote:
On 21/12/13 19:44, Chris Murphy wrote:
On Dec 21, 2013, at 8:48 AM, Erik P. Olsen epodata@gmail.com wrote:
I'll do another F20 installation to see if it shows up this time. If not I suppose it is hardware related. Maybe anaconda doesn't like bios with uefi turned off. I had no problems with F19 though.
I forget if it's still possible to disable the install boot loader feature on UEFI. It's a meaningless option, except that /etc/default/grub will not be created. grub2-efi is still installed, shim.efi is still installed, and you do in fact still get a boot loader installed on UEFI systems regardless of this option. And I think there's a RHBZ on this issue also, but I don't know if that's been implemented in F20.
I don't think there is an option to disable boot loader feature (or rather I haven't found it :-)
Installation Destination, bottom page click on Full disk summary and bootloader, you get this dialog:
https://dl.dropboxusercontent.com/u/3253801/ssanacondanobootldr.png
Click on the device, then click button Do not installer bootloader.
The bios of my system is uefi capable but I have disabled it.
It's the manufacturer's confusing us royally, and unnecessarily. Your computer is UEFI it has no BIOS really. The option to disable UEFI in the interface actually *enables a CSM, an EFI Compatibility Support Module. It presents a BIOS interface for the operating system and it's a legacy feature meant to support operating systems that don't understand UEFI firmware. It's kinda like BIOS emulation. But the computer is UEFI and it can't be disabled, unlike what the UI suggests.
You're almost certainly better off having installed Fedora with UEFI "enabled" which means CSM disabled. But if it's working I'd probably leave it alone, unless it's a laptop that you regularly use as a mobile (not plugged into power) device.
Anyhow my last F20 build did produce /etc/default/grup even though I didn't make any change to the installation procedure. But I did use netinst so some changes may have come in this way.
It would be good to track this down if you can reproduce it. Save the /tmp/program.log from the install environment, or the /var/log/anaconda.program.log from the post-installed system, it might give a hint why this wasn't created.
Chris Murphy
On 21/12/13 21:53, Chris Murphy wrote:
On Dec 21, 2013, at 12:38 PM, "Erik P. Olsen" epodata@gmail.com wrote:
On 21/12/13 19:44, Chris Murphy wrote:
On Dec 21, 2013, at 8:48 AM, Erik P. Olsen epodata@gmail.com wrote:
I'll do another F20 installation to see if it shows up this time. If not I suppose it is hardware related. Maybe anaconda doesn't like bios with uefi turned off. I had no problems with F19 though.
I forget if it's still possible to disable the install boot loader feature on UEFI. It's a meaningless option, except that /etc/default/grub will not be created. grub2-efi is still installed, shim.efi is still installed, and you do in fact still get a boot loader installed on UEFI systems regardless of this option. And I think there's a RHBZ on this issue also, but I don't know if that's been implemented in F20.
I don't think there is an option to disable boot loader feature (or rather I haven't found it :-)
Installation Destination, bottom page click on Full disk summary and bootloader, you get this dialog:
https://dl.dropboxusercontent.com/u/3253801/ssanacondanobootldr.png
Click on the device, then click button Do not installer bootloader.
I never saw this. It said just "Set as boot device" and I never clicked on the device, just closed the window and "Done".
The bios of my system is uefi capable but I have disabled it.
It's the manufacturer's confusing us royally, and unnecessarily. Your computer is UEFI it has no BIOS really. The option to disable UEFI in the interface actually *enables a CSM, an EFI Compatibility Support Module. It presents a BIOS interface for the operating system and it's a legacy feature meant to support operating systems that don't understand UEFI firmware. It's kinda like BIOS emulation. But the computer is UEFI and it can't be disabled, unlike what the UI suggests.
You're almost certainly better off having installed Fedora with UEFI "enabled" which means CSM disabled. But if it's working I'd probably leave it alone, unless it's a laptop that you regularly use as a mobile (not plugged into power) device.
Thanks for the insight into this matter. It is actually a laptop that I use as mobile device. Why is it that UEFI "enabled" is better in this situation? Power?
Anyhow my last F20 build did produce /etc/default/grup even though I didn't make any change to the installation procedure. But I did use netinst so some changes may have come in this way.
It would be good to track this down if you can reproduce it. Save the /tmp/program.log from the install environment, or the /var/log/anaconda.program.log from the post-installed system, it might give a hint why this wasn't created.
I doubt that I can reproduce it now that it apparently works. But I'll try a few system build to see if I can.
On Dec 21, 2013, at 2:48 PM, Erik P. Olsen epodata@gmail.com wrote:
Thanks for the insight into this matter. It is actually a laptop that I use as mobile device. Why is it that UEFI "enabled" is better in this situation? Power?
Yes. ACPI and AHCI are sometimes not native. Most of the CSM-BIOS mode booted systems I've seen have more limited battery life, and fast SATA drives like SSDs are in IDE mode so they're also quite a bit slower. But this varies on the CSM implementation. It's not a linux thing, so you just have to test it.
Also, if the laptop has dual graphics, like Intel integrated graphics and also discrete graphics, then UEFI mode boots tend to activate both, causing neither to work. So you have to figure out how to disable one of them with a modeset kernel parameter option.
Chris Murphy
On Dec 21, 2013, at 2:43 AM, Erik P. Olsen epodata@gmail.com wrote:
/etc/default/grub is missing on my newly installed F20. What's replacing its functionality?
This file is created by anaconda BIOS and UEFI computers. It's not created if the install boot loader option is disabled in the installer, and there is a long convoluted RFE in RHBZ (maybe there's a short one, but if not one needs to be created) to create this file even if the install boot loader option is disabled.
Chris Murphy
-
Chris Murphy -
Ed Greshko -
Erik P. Olsen