Re: [gentoo-user] Bootloaders: SILENT CRISIS!!!

[Tom H]

On Mon, Jan 30, 2017 at 1:54 PM, Mick  wrote:
> On Monday 30 Jan 2017 06:10:47 Tom H wrote:
>>
>> AFAIK, since the advent of defaulting to CoreStorage (OS X 10.10? - OS
>> X's equivalent of LVM) and full-disk encryption (OS X 10.10?),
>> bootx64.efi/boot.efi cannot be loaded from disk0s2.
>
> I suspect you're right ...
>
> This is what my MBP EFI reports:
>
> # efibootmgr -v
> BootCurrent: 
> Timeout: 5 seconds
> BootOrder: ,0080
> Boot* Gentoo-4.4.39-28_Jan HD(1,GPT,a28905fe-b74d-46b3-b68b-
> ee342a73f72b,0x28,0x64000)/File(\EFI\LINUX\bootx64-4.4.39-gentoo.efi)
> Boot0080* Mac OS X
> PciRoot(0x0)/Pci(0x1c,0x4)/Pci(0x0,0x0)/Sata(0,0,0)/HD(3,GPT,15fd7906-
> a899-4912-b52b-3e034f7a62ea,0xdcfa748,0x135f20)
> Boot0081* Mac OS X
> PciRoot(0x0)/Pci(0x1c,0x4)/Pci(0x0,0x0)/Sata(0,0,0)/HD(3,GPT,15fd7906-
> a899-4912-b52b-3e034f7a62ea,0xdcfa748,0x135f20)
> Boot0082*
> PciRoot(0x0)/Pci(0x1c,0x4)/Pci(0x0,0x0)/Sata(0,0,0)/HD(3,GPT,15fd7906-
> a899-4912-b52b-3e034f7a62ea,0xdcfa748,0x135f20)
> Boot*
> PciRoot(0x0)/Pci(0x1c,0x4)/Pci(0x0,0x0)/Sata(0,0,0)/HD(2,GPT,41293e5b-9bdc-405a-
> ba22-5ece4b11f91e,0x64028,0x1bb18c80)/File(\System\Library\CoreServices\boot.efi)
>
> Both Boot0080 and Boot0081 are on the 3 partition. Boot points to the
> \System\Library\CoreServices\boot.efi file on the 2nd partition. However, 
> there
> same path and file also exists on the 3rd partition, but as you mention the 
> 3rd
> partition is unencrypted.

On my MacBook, bought in December, un-upgraded and un-linuxed:

# nvram -p | grep efi-boot-device
efi-boot-device
IOMatchIOProviderClassIOMediaIOPropertyMatchUUIDB6F965B2-2CF9-4A9E-85EA-544300583A35BLLastBSDNamedisk0s3%00
efi-boot-device-data
%02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%00%1c%01%01%06%00%00%00%03%16%10%00%01%00%00%00%f9
%16X7%02%05%00%04%01*%00%03%00%00%00,BE%07%00%00%00%00%e4k%02%00%00%00%00%00%b2e%f9%b6%f9,%9eJ%85%eaTC%00X:5%02%02%7f%ff%04%00
#

Re: [gentoo-user] Bootloaders: SILENT CRISIS!!!

[Mick]

On Monday 30 Jan 2017 06:10:47 Tom H wrote:
> On Sun, Jan 29, 2017 at 6:26 PM, Mick  wrote:
> > On Sunday 29 Jan 2017 14:44:45 Tom H wrote:
> >> [1] Apple's EFI firmware can read hfsplus and it boots (IIRC since OS
> >> X 10.10) from a kernel on the Apple_Boot partition (disk0s3).
> > 
> > Yes, Apple's firmware reads the blessed hfs+ partition and fishes out
> > its bootx64.efi file kernel image, but I thought this was from the
> > second partition where the OS is installed. I'll have a look tomorrow
> > when I boot it up.
> 
> AFAIK, since the advent of defaulting to CoreStorage (OS X 10.10? - OS
> X's equivalent of LVM) and full-disk encryption (OS X 10.10?),
> bootx64.efi/boot.efi cannot be loaded from disk0s2.

I suspect you're right ...

This is what my MBP EFI reports:

# efibootmgr -v
BootCurrent: 
Timeout: 5 seconds
BootOrder: ,0080
Boot* Gentoo-4.4.39-28_Jan  HD(1,GPT,a28905fe-b74d-46b3-b68b-
ee342a73f72b,0x28,0x64000)/File(\EFI\LINUX\bootx64-4.4.39-gentoo.efi)
Boot0080* Mac OS X  
PciRoot(0x0)/Pci(0x1c,0x4)/Pci(0x0,0x0)/Sata(0,0,0)/HD(3,GPT,15fd7906-
a899-4912-b52b-3e034f7a62ea,0xdcfa748,0x135f20)
Boot0081* Mac OS X  
PciRoot(0x0)/Pci(0x1c,0x4)/Pci(0x0,0x0)/Sata(0,0,0)/HD(3,GPT,15fd7906-
a899-4912-b52b-3e034f7a62ea,0xdcfa748,0x135f20)
Boot0082*   
PciRoot(0x0)/Pci(0x1c,0x4)/Pci(0x0,0x0)/Sata(0,0,0)/HD(3,GPT,15fd7906-
a899-4912-b52b-3e034f7a62ea,0xdcfa748,0x135f20)
Boot*   
PciRoot(0x0)/Pci(0x1c,0x4)/Pci(0x0,0x0)/Sata(0,0,0)/HD(2,GPT,41293e5b-9bdc-405a-
ba22-5ece4b11f91e,0x64028,0x1bb18c80)/File(\System\Library\CoreServices\boot.efi)

Both Boot0080 and Boot0081 are on the 3 partition.  Boot points to the 
\System\Library\CoreServices\boot.efi file on the 2nd partition.  However, 
there 
same path and file also exists on the 3rd partition, but as you mention the 3rd 
partition is unencrypted.

-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Bootloaders: SILENT CRISIS!!!

[Tom H]

On Sun, Jan 29, 2017 at 6:26 PM, Mick  wrote:
> On Sunday 29 Jan 2017 14:44:45 Tom H wrote:
>>
>> [1] Apple's EFI firmware can read hfsplus and it boots (IIRC since OS
>> X 10.10) from a kernel on the Apple_Boot partition (disk0s3).
>
> Yes, Apple's firmware reads the blessed hfs+ partition and fishes out
> its bootx64.efi file kernel image, but I thought this was from the
> second partition where the OS is installed. I'll have a look tomorrow
> when I boot it up.

AFAIK, since the advent of defaulting to CoreStorage (OS X 10.10? - OS
X's equivalent of LVM) and full-disk encryption (OS X 10.10?),
bootx64.efi/boot.efi cannot be loaded from disk0s2.

Re: [gentoo-user] Bootloaders: SILENT CRISIS!!!

[Mick]

On Sunday 29 Jan 2017 14:44:45 Tom H wrote:
> On Sat, Jan 28, 2017 at 2:31 PM, Mick  wrote:
> > rEFInd is definitely a slick and useful boot manager for multibooting.
> > On this occasion I did not install it, but decided to remain
> > minimalist, because I do not want to interfere much with the AppleMac
> > installation.
> > 
> > So, I created /boot/EFI/LINUX/ on /dev/sda1, leaving the original
> > /boot/EFI/APPLE as was and copied in the LINUX/ directory just the
> > gentoo kernel image, .config and System files. I named the kernel
> > image 'bootx64-4.4.39-gentoo.efi' to differentiate from other images I
> > will install over time.
> > 
> > Then using the efibootmgr I set up bootx64-4.4.39-gentoo.efi as the
> > default boot kernel and when the MackBook is started it boots straight
> > into Gentoo, in what it feels like milliseconds. :-)
> > 
> > When I need to boot into MacOS I have to press the alt key (aka Option
> > ⌥ key) as I power it on and the Apple firmware boot loader takes over.
> > What I don't know yet is if a MacOS upgrade will wipe the
> > /boot/EFI/LINUX/ in /dev/sda1 as it upgrades the APPLE files, but it
> > is easy to boot with a LiveUSB and copy over the Linux kernel once
> > more.
> 
> Apple doesn't boot from the ESP [1] so it most likely won't touch
> "/boot/EFI/LINUX/".
> 
> For example, on my MacBook, the ESP only has what looks like hardware
> updaters.

Yes, this is where firmware updates install images for the hardware and these 
are flashed/loaded when the MacOS boots.


> # diskutil list disk0
> /dev/disk0 (internal):
>#:   TYPE NAMESIZE  
> IDENTIFIER 0:  GUID_partition_scheme 500.3 GB  
> disk0 1:EFI EFI 314.6 MB  
> disk0s1 2:  Apple_CoreStorage Macintosh HD499.3 GB  
> disk0s2 3: Apple_Boot Recovery HD 650.0 MB  
> disk0s3
> 
> 
> # diskutil mount readOnly -mountpoint ESP disk0s1
> Volume EFI on disk0s1 mounted
> 
> 
> # ls -R ESP/EFI
> APPLE
> 
> ESP/EFI/APPLE:
> EXTENSIONS FIRMWARE UPDATERS
> 
> ESP/EFI/APPLE/EXTENSIONS:
> Firmware.scap
> 
> ESP/EFI/APPLE/FIRMWARE:
> MB91_0154_B09_LOCKED.fd
> 
> ESP/EFI/APPLE/UPDATERS:
> MULTIUPDATER USBCH USBCVA
> 
> ESP/EFI/APPLE/UPDATERS/MULTIUPDATER:
> HPMUtil.efi Mac-9AE82516C7C6B903.epm MultiUpdater.efi flasher_base.smc
> Mac-9AE82516C7C6B903-B0_3.72.bin Mac-9AE82516C7C6B903.smc
> SmcFlasher.efi flasher_update.smc
> 
> ESP/EFI/APPLE/UPDATERS/USBCH:
> HPMUtil_v39.efi J93-USBC-NVM-2.72.0-P_B0-S.bin
> 
> ESP/EFI/APPLE/UPDATERS/USBCVA:
> HPMUtil.efi fw-p1-USBCVideoAdapter-S.bin
> #
> 
> 
> [1] Apple's EFI firmware can read hfsplus and it boots (IIRC since OS
> X 10.10) from a kernel on the Apple_Boot partition (disk0s3).

Yes, Apple's firmare reads the blessed hfs+ partition and fishes out its 
bootx64.efi file kernel image, but I thought this was from the second partition 
where the OS is installed.  I'll have a look tomorrow when I boot it up.
-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Bootloaders: SILENT CRISIS!!!

[Tom H]

On Sat, Jan 28, 2017 at 2:31 PM, Mick  wrote:
>
> rEFInd is definitely a slick and useful boot manager for multibooting.
> On this occasion I did not install it, but decided to remain
> minimalist, because I do not want to interfere much with the AppleMac
> installation.
>
> So, I created /boot/EFI/LINUX/ on /dev/sda1, leaving the original
> /boot/EFI/APPLE as was and copied in the LINUX/ directory just the
> gentoo kernel image, .config and System files. I named the kernel
> image 'bootx64-4.4.39-gentoo.efi' to differentiate from other images I
> will install over time.
>
> Then using the efibootmgr I set up bootx64-4.4.39-gentoo.efi as the
> default boot kernel and when the MackBook is started it boots straight
> into Gentoo, in what it feels like milliseconds. :-)
>
> When I need to boot into MacOS I have to press the alt key (aka Option
> ⌥ key) as I power it on and the Apple firmware boot loader takes over.
> What I don't know yet is if a MacOS upgrade will wipe the
> /boot/EFI/LINUX/ in /dev/sda1 as it upgrades the APPLE files, but it
> is easy to boot with a LiveUSB and copy over the Linux kernel once
> more.

Apple doesn't boot from the ESP [1] so it most likely won't touch
"/boot/EFI/LINUX/".

For example, on my MacBook, the ESP only has what looks like hardware updaters.


# diskutil list disk0
/dev/disk0 (internal):
   #:   TYPE NAMESIZE   IDENTIFIER
   0:  GUID_partition_scheme 500.3 GB   disk0
   1:EFI EFI 314.6 MB   disk0s1
   2:  Apple_CoreStorage Macintosh HD499.3 GB   disk0s2
   3: Apple_Boot Recovery HD 650.0 MB   disk0s3


# diskutil mount readOnly -mountpoint ESP disk0s1
Volume EFI on disk0s1 mounted


# ls -R ESP/EFI
APPLE

ESP/EFI/APPLE:
EXTENSIONS FIRMWARE UPDATERS

ESP/EFI/APPLE/EXTENSIONS:
Firmware.scap

ESP/EFI/APPLE/FIRMWARE:
MB91_0154_B09_LOCKED.fd

ESP/EFI/APPLE/UPDATERS:
MULTIUPDATER USBCH USBCVA

ESP/EFI/APPLE/UPDATERS/MULTIUPDATER:
HPMUtil.efi Mac-9AE82516C7C6B903.epm MultiUpdater.efi flasher_base.smc
Mac-9AE82516C7C6B903-B0_3.72.bin Mac-9AE82516C7C6B903.smc
SmcFlasher.efi flasher_update.smc

ESP/EFI/APPLE/UPDATERS/USBCH:
HPMUtil_v39.efi J93-USBC-NVM-2.72.0-P_B0-S.bin

ESP/EFI/APPLE/UPDATERS/USBCVA:
HPMUtil.efi fw-p1-USBCVideoAdapter-S.bin
#


[1] Apple's EFI firmware can read hfsplus and it boots (IIRC since OS
X 10.10) from a kernel on the Apple_Boot partition (disk0s3).

Re: [gentoo-user] Bootloaders: SILENT CRISIS!!!

[Mick]

On Saturday 28 Jan 2017 12:20:12 Tom H wrote:
> On Fri, Jan 27, 2017 at 5:50 PM, Bill Kenworthy  wrote:
> > On 28/01/17 00:25, Tom H wrote:
> >> On Thu, Jan 26, 2017 at 7:10 PM, Bill Kenworthy  
wrote:
> >>> I tried grub2 and dumped it for "rEFit" - ended up a lot easier and
> >>> more robust.
> >> 
> >> rEFIt or rEFInd?
> > 
> > Sorry, yes it is rEFInd I am using.
> 
> No worries. I had to check out of curiosity because I mix them up...

rEFInd is definitely a slick and useful boot manager for multibooting.  On this 
occasion I did not install it, but decided to remain minimalist, because I do 
not want to interfere much with the AppleMac installation.

So, I created /boot/EFI/LINUX/ on /dev/sda1, leaving the original 
/boot/EFI/APPLE as was and copied in the LINUX/ directory just the gentoo 
kernel image, .config and System files.  I named the kernel image 
'bootx64-4.4.39-gentoo.efi' to differentiate from other images I will install 
over time.

Then using the efibootmgr I set up bootx64-4.4.39-gentoo.efi as the default 
boot 
kernel and when the MackBook is started it boots straight into Gentoo, in what 
it feels like milliseconds.  :-)

When I need to boot into MacOS I have to press the alt key (aka Option ⌥  key) 
as I power it on and the Apple firmware boot loader takes over.  What I don't 
know yet is if a MacOS upgrade will wipe the /boot/EFI/LINUX/ in /dev/sda1 as 
it upgrades the APPLE files, but it is easy to boot with a LiveUSB and copy 
over the Linux kernel once more.

This way I don't have to bless a hfs+ partition, or mess about with the MacOS 
firmware files, bootx64.efi, or anything else.  I wonder why Apple did not 
develop their boot manager to be able to identify and boot Linux kernels too, 
but are happy to make it boot MSWindows ...

-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Bootloaders: SILENT CRISIS!!!

[Tom H]

On Fri, Jan 27, 2017 at 5:50 PM, Bill Kenworthy  wrote:
> On 28/01/17 00:25, Tom H wrote:
>> On Thu, Jan 26, 2017 at 7:10 PM, Bill Kenworthy  wrote:
>>>
>>> I tried grub2 and dumped it for "rEFit" - ended up a lot easier and
>>> more robust.
>>
>> rEFIt or rEFInd?
>
> Sorry, yes it is rEFInd I am using.

No worries. I had to check out of curiosity because I mix them up...

Re: [gentoo-user] Bootloaders: SILENT CRISIS!!!

[Peter Humphrey]

On Thursday 26 Jan 2017 18:58:07 Neil Bothwick wrote:
> On Thu, 26 Jan 2017 12:03:24 -0500, Alan Grimes wrote:
> > I looked for more information on GRUB form upstream but, on first
> > impression, it's been an abandoned project since 2012...
> 
> That's legacy GRUB, not GRUB2.
> 
> But if you want an EFI bootloader, it is much simpler to use bootctl if
> you use systemd or gummiboot if you don't (they are essentially the same
> thing). Gummiboot is no longer in the man tree but is available from a
> couple of overlays.

I've installed systemd-boot for bootctl, which avoids having to use an 
overlay. It appears to be happy on this openrc box.

-- 
Regards
Peter

Re: [gentoo-user] Bootloaders: SILENT CRISIS!!!

[Mick]

On Saturday 28 Jan 2017 07:49:13 Bill Kenworthy wrote:
> On 28/01/17 07:27, Mick wrote:
> > On Saturday 28 Jan 2017 06:50:32 Bill Kenworthy wrote:
> >> On 28/01/17 00:25, Tom H wrote:
> >>> On Thu, Jan 26, 2017 at 7:10 PM, Bill Kenworthy 
> > 
> > wrote:
>  I tried grub2 and dumped it for "rEFit" - ended up a lot easier and
>  more robust.
> >>> 
> >>> rEFIt or rEFInd?
> >> 
> >> Sorry, yes it is rEFInd I am using.
> >> 
> >> BillK
> > 
> > Where did you install rEFInd?  In the EFI partition?  I am about to
> > install
> > gentoo on a MackBook Pro, but do not want to mess up the original 3
> > partitions installed by OSX, any more than is absolutely necessary.
> > 
> > I could start a new thread if this is hijacking the OP's, but there are
> > some parallels with boot loaders at least.  I am thinking of trying out
> > the sys- boot/systemd-boot (ex-gumiboot) instead of rEFInd.  Will it be
> > able to launch the OSX  boot64.efi?
> 
> mounted at /boot/efi
> 
> /boot
> └── efi
> └── EFI
> ├── Boot
> ├── gentoo
> ├── Microsoft
> │   ├── Boot
> │   │   ├── ar-SA
> snip
> │   └── Recovery
> ├── refind
> │   ├── banners
> │   ├── drivers_x64
> │   ├── fonts
> │   ├── icons
> │   │   ├── licenses
> │   │   └── svg
> │   ├── images
> │   ├── keys
> │   └── tools_x64
> └── tools
> 
> bunyip ~ # fdisk -l /dev/nvme0n1
> Disk /dev/nvme0n1: 238.5 GiB, 256060514304 bytes, 500118192 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disklabel type: gpt
> Disk identifier: 8607528E-5D14-4725-BC44-F325B97B6736
> 
> Device Start   End   Sectors   Size Type
> /dev/nvme0n1p1  2048534527532480   260M EFI System
> /dev/nvme0n1p2534528796671262144   128M Microsoft reserved
> /dev/nvme0n1p3796672 251281407 250484736 119.5G Microsoft basic data
> /dev/nvme0n1p4 496185344 500117503   3932160   1.9G Windows recovery
> environment
> /dev/nvme0n1p5 251281408 276447231  2516582412G Linux swap
> /dev/nvme0n1p6 276447232 496185343 219738112 104.8G Linux filesystem
> 
> Partition table entries are not in disk order.
> 
> /boot/efi/EFI/refind/refind.conf
> timeout 2
> showtools shell, gdisk, memtest, mok_tool, windows_recovery, about,
> reboot, exit, firmware
> scanfor manual
> menuentry Linux-4.9.5-gentoo {
> icon /EFI/refind/icons/os_gentoo.png
> volume 760df07d-ec40-452f-95ee-cb47acf22069
> loader /EFI/gentoo/kernel-genkernel-x86_64-4.9.5-gentoo.efi
> initrd /EFI/gentoo/initramfs-genkernel-x86_64-4.9.5-gentoo.img
> options "acpi_osi=Linux i915.semaphores=1 intel_iommu=off
> pcie_port_pm=off rootdelay=15 ro
> root=UUID=fc556f9c-e9b9-4ed3-8244-94f9f1a7d4d0 dobtrfs maxcpus=1 zcache
> resume=/dev/nvme0n1p5"
> }
> menuentry Linux-4.9.4-gentoo {
> icon /EFI/refind/icons/os_gentoo.png
> volume 760df07d-ec40-452f-95ee-cb47acf22069
> loader /EFI/gentoo/kernel-genkernel-x86_64-4.9.4-gentoo.efi
> initrd /EFI/gentoo/initramfs-genkernel-x86_64-4.9.4-gentoo.img
> options "acpi_osi=Linux i915.semaphores=1 intel_iommu=off
> pcie_port_pm=off rootdelay=15 ro
> root=UUID=fc556f9c-e9b9-4ed3-8244-94f9f1a7d4d0 dobtrfs maxcpus=1 zcache
> resume=/dev/nvme0n1p5"
> }
> menuentry "Windows 10" {
> loader \EFI\Microsoft\Boot\bootmgfw.efi
> }

Thanks, I may have a go installing rEFInd or systemd-boot this weekend.
-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Bootloaders: SILENT CRISIS!!!

[Bill Kenworthy]

On 28/01/17 07:27, Mick wrote:
> On Saturday 28 Jan 2017 06:50:32 Bill Kenworthy wrote:
>> On 28/01/17 00:25, Tom H wrote:
>>> On Thu, Jan 26, 2017 at 7:10 PM, Bill Kenworthy  
> wrote:
 I tried grub2 and dumped it for "rEFit" - ended up a lot easier and
 more robust.
>>>
>>> rEFIt or rEFInd?
>>
>> Sorry, yes it is rEFInd I am using.
>>
>> BillK
> 
> Where did you install rEFInd?  In the EFI partition?  I am about to install 
> gentoo on a MackBook Pro, but do not want to mess up the original 3 
> partitions 
> installed by OSX, any more than is absolutely necessary.
> 
> I could start a new thread if this is hijacking the OP's, but there are some 
> parallels with boot loaders at least.  I am thinking of trying out the sys-
> boot/systemd-boot (ex-gumiboot) instead of rEFInd.  Will it be able to launch 
> the OSX  boot64.efi?
> 

mounted at /boot/efi

/boot
└── efi
└── EFI
├── Boot
├── gentoo
├── Microsoft
│   ├── Boot
│   │   ├── ar-SA
snip
│   └── Recovery
├── refind
│   ├── banners
│   ├── drivers_x64
│   ├── fonts
│   ├── icons
│   │   ├── licenses
│   │   └── svg
│   ├── images
│   ├── keys
│   └── tools_x64
└── tools

bunyip ~ # fdisk -l /dev/nvme0n1
Disk /dev/nvme0n1: 238.5 GiB, 256060514304 bytes, 500118192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 8607528E-5D14-4725-BC44-F325B97B6736

Device Start   End   Sectors   Size Type
/dev/nvme0n1p1  2048534527532480   260M EFI System
/dev/nvme0n1p2534528796671262144   128M Microsoft reserved
/dev/nvme0n1p3796672 251281407 250484736 119.5G Microsoft basic data
/dev/nvme0n1p4 496185344 500117503   3932160   1.9G Windows recovery
environment
/dev/nvme0n1p5 251281408 276447231  2516582412G Linux swap
/dev/nvme0n1p6 276447232 496185343 219738112 104.8G Linux filesystem

Partition table entries are not in disk order.

/boot/efi/EFI/refind/refind.conf
timeout 2
showtools shell, gdisk, memtest, mok_tool, windows_recovery, about,
reboot, exit, firmware
scanfor manual
menuentry Linux-4.9.5-gentoo {
icon /EFI/refind/icons/os_gentoo.png
volume 760df07d-ec40-452f-95ee-cb47acf22069
loader /EFI/gentoo/kernel-genkernel-x86_64-4.9.5-gentoo.efi
initrd /EFI/gentoo/initramfs-genkernel-x86_64-4.9.5-gentoo.img
options "acpi_osi=Linux i915.semaphores=1 intel_iommu=off
pcie_port_pm=off rootdelay=15 ro
root=UUID=fc556f9c-e9b9-4ed3-8244-94f9f1a7d4d0 dobtrfs maxcpus=1 zcache
resume=/dev/nvme0n1p5"
}
menuentry Linux-4.9.4-gentoo {
icon /EFI/refind/icons/os_gentoo.png
volume 760df07d-ec40-452f-95ee-cb47acf22069
loader /EFI/gentoo/kernel-genkernel-x86_64-4.9.4-gentoo.efi
initrd /EFI/gentoo/initramfs-genkernel-x86_64-4.9.4-gentoo.img
options "acpi_osi=Linux i915.semaphores=1 intel_iommu=off
pcie_port_pm=off rootdelay=15 ro
root=UUID=fc556f9c-e9b9-4ed3-8244-94f9f1a7d4d0 dobtrfs maxcpus=1 zcache
resume=/dev/nvme0n1p5"
}
menuentry "Windows 10" {
loader \EFI\Microsoft\Boot\bootmgfw.efi
}

Re: [gentoo-user] Bootloaders: SILENT CRISIS!!!

[Mick]

On Saturday 28 Jan 2017 06:50:32 Bill Kenworthy wrote:
> On 28/01/17 00:25, Tom H wrote:
> > On Thu, Jan 26, 2017 at 7:10 PM, Bill Kenworthy  
wrote:
> >> I tried grub2 and dumped it for "rEFit" - ended up a lot easier and
> >> more robust.
> > 
> > rEFIt or rEFInd?
> 
> Sorry, yes it is rEFInd I am using.
> 
> BillK

Where did you install rEFInd?  In the EFI partition?  I am about to install 
gentoo on a MackBook Pro, but do not want to mess up the original 3 partitions 
installed by OSX, any more than is absolutely necessary.

I could start a new thread if this is hijacking the OP's, but there are some 
parallels with boot loaders at least.  I am thinking of trying out the sys-
boot/systemd-boot (ex-gumiboot) instead of rEFInd.  Will it be able to launch 
the OSX  boot64.efi?

-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Bootloaders: SILENT CRISIS!!!

[Bill Kenworthy]

On 28/01/17 00:25, Tom H wrote:
> On Thu, Jan 26, 2017 at 7:10 PM, Bill Kenworthy  wrote:
>>
>> I tried grub2 and dumped it for "rEFit" - ended up a lot easier and
>> more robust.
> 
> rEFIt or rEFInd?
> 

Sorry, yes it is rEFInd I am using.

BillK

Re: [gentoo-user] Bootloaders: SILENT CRISIS!!!

[Tom H]

On Thu, Jan 26, 2017 at 7:10 PM, Bill Kenworthy  wrote:
>
> I tried grub2 and dumped it for "rEFit" - ended up a lot easier and
> more robust.

rEFIt or rEFInd?

Re: [gentoo-user] Bootloaders: SILENT CRISIS!!!

[Tom H]

On Thu, Jan 26, 2017 at 12:03 PM, Alan Grimes  wrote:


> I looked for more information on GRUB form upstream but, on first
> impression, it's been an abandoned project since 2012... Apparently
> some users have posted patches to things like the invalid sector size
> problem but the project has been deaf to these problems and has done
> nothing whatsoever. =(

That's grub1 (which doesn't understand efi). grub2 is still being developed.


> I thought maybe I could go simple and use something like elilo.

Unfortunately elilo's been abandoned.

Re: [gentoo-user] Bootloaders: SILENT CRISIS!!!

[Ian Bloss]

Syslinux family has been my go to boot loader

On Thu, Jan 26, 2017, 4:12 PM Bill Kenworthy  wrote:

> On 27/01/17 01:03, Alan Grimes wrote:
> > I looked for more information on GRUB form upstream but, on first
> > impression, it's been an abandoned project since 2012... Apparently some
> > users have posted patches to things like the invalid sector size problem
> > but the project has been deaf to these problems and has done nothing
> > whatsoever. =(
> >
> > I thought maybe I could go simple and use something like elilo, The
> > manual was written in moonspeak, it was very missleading and had lots of
> > omissions, and misdirection. I downloaded the 2,200 page specification
> > for EFI an quickly came to realize that the Elilo documentation was a
> > geyser of bullshit. I think it's going to be my new standard example of
> > how awful linux documentation is.
> >
> > Seriously, It deserves a few hundred more pages of ragging, and flaming,
> > and rage-ing but I've got a piece of junk to boot. =|
> >
> >
> > I don't know where Gentoo is getting it's source for Grub...
> >
> >
> > Apparently the git version of Grub was abandoned in 2015, as far as I
> > can tell... I'm trying to build it from source. As is appropriate the
> > git repository doesn't have the git scripts, I tried running autoreconf
> > on it but got error messages...
> >
> > I cleared a few of them but I'm like:
> >
> > ##
> > atg@localhost ~/source/grub $ autoreconf
> > autoreconf-2.69: configure.ac: AM_GNU_GETTEXT is used, but not
> > AM_GNU_GETTEXT_VERSION
> > automake-1.15: error: cannot open < Makefile.util.am: No such file or
> > directory
> > autoreconf-2.69: automake failed with exit status: 1
> > atg@localhost ~/source/grub $
> > ##
> >
> > Is there a way to ebuild a "grub-git" and produce a grub install with
> > version = date of most recent commit on active fork?
> >
>
> I tried grub2 and dumped it for "rEFit" - ended up a lot easier and more
> robust.
>
> This was on an apple air laptop a few years back, and currently on a MS
> surface 4.
>
> BillK
>
>
>

Re: [gentoo-user] Bootloaders: SILENT CRISIS!!!

[Bill Kenworthy]

On 27/01/17 01:03, Alan Grimes wrote:
> I looked for more information on GRUB form upstream but, on first
> impression, it's been an abandoned project since 2012... Apparently some
> users have posted patches to things like the invalid sector size problem
> but the project has been deaf to these problems and has done nothing
> whatsoever. =(
> 
> I thought maybe I could go simple and use something like elilo, The
> manual was written in moonspeak, it was very missleading and had lots of
> omissions, and misdirection. I downloaded the 2,200 page specification
> for EFI an quickly came to realize that the Elilo documentation was a
> geyser of bullshit. I think it's going to be my new standard example of
> how awful linux documentation is.
> 
> Seriously, It deserves a few hundred more pages of ragging, and flaming,
> and rage-ing but I've got a piece of junk to boot. =|
> 
> 
> I don't know where Gentoo is getting it's source for Grub...
> 
> 
> Apparently the git version of Grub was abandoned in 2015, as far as I
> can tell... I'm trying to build it from source. As is appropriate the
> git repository doesn't have the git scripts, I tried running autoreconf
> on it but got error messages...
> 
> I cleared a few of them but I'm like:
> 
> ##
> atg@localhost ~/source/grub $ autoreconf
> autoreconf-2.69: configure.ac: AM_GNU_GETTEXT is used, but not
> AM_GNU_GETTEXT_VERSION
> automake-1.15: error: cannot open < Makefile.util.am: No such file or
> directory
> autoreconf-2.69: automake failed with exit status: 1
> atg@localhost ~/source/grub $
> ##
> 
> Is there a way to ebuild a "grub-git" and produce a grub install with
> version = date of most recent commit on active fork?
> 

I tried grub2 and dumped it for "rEFit" - ended up a lot easier and more
robust.

This was on an apple air laptop a few years back, and currently on a MS
surface 4.

BillK

Re: [gentoo-user] Bootloaders: SILENT CRISIS!!!

[Neil Bothwick]

On Thu, 26 Jan 2017 12:03:24 -0500, Alan Grimes wrote:

> I looked for more information on GRUB form upstream but, on first
> impression, it's been an abandoned project since 2012...

That's legacy GRUB, not GRUB2.

But if you want an EFI bootloader, it is much simpler to use bootctl if
you use systemd or gummiboot if you don't (they are essentially the same
thing). Gummiboot is no longer in the man tree but is available from a
couple of overlays.


-- 
Neil Bothwick

WinErr 815: Insufficient Memory - Only 50,312,583 Bytes available


pgpk9k7UqOq3F.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] Bootloaders: SILENT CRISIS!!!

[Michael Morak]

On 26 January 2017 at 18:03, Alan Grimes  wrote:

> I looked for more information on GRUB form upstream but, on first
> impression, it's been an abandoned project since 2012... Apparently some
> users have posted patches to things like the invalid sector size problem
> but the project has been deaf to these problems and has done nothing
> whatsoever. =(
>

The official repository for grub shows regular activity (last commit was 2
days ago), see here: http://git.savannah.gnu.org/cgit/grub.git/log/


> *snip
>
> I don't know where Gentoo is getting it's source for Grub...
>

You can find this info by looking in the relevant ebuilds. Gentoo is
getting it's grub source from the official GNU grub repository: http://git.
savannah.gnu.org/r/grub.git


> Apparently the git version of Grub was abandoned in 2015, as far as I
> can tell...


See above.


> I'm trying to build it from source. As is appropriate the
> git repository doesn't have the git scripts, I tried running autoreconf
> on it but got error messages...
>
> I cleared a few of them but I'm like:
>
> ##
> atg@localhost ~/source/grub $ autoreconf
> autoreconf-2.69: configure.ac: AM_GNU_GETTEXT is used, but not
> AM_GNU_GETTEXT_VERSION
> automake-1.15: error: cannot open < Makefile.util.am: No such file or
> directory
> autoreconf-2.69: automake failed with exit status: 1
> atg@localhost ~/source/grub $
> ##
>
> Is there a way to ebuild a "grub-git" and produce a grub install with
> version = date of most recent commit on active fork?
>

If you'd like to build the most recent version directly from the git
repository you could emerge "=grub-" (portage will do everything for
you, that is, it pulls the sources directly from the master branch and
builds from them). Otherwise, clone the sources yourself and, instead of
autoreconf, run the provided autogen.sh script, which is what you should
generally do for autotools-projects instead of running autoconf yourself.

Hope this helps,
Michael

[gentoo-user] Bootloaders: SILENT CRISIS!!!

[Alan Grimes]

I looked for more information on GRUB form upstream but, on first
impression, it's been an abandoned project since 2012... Apparently some
users have posted patches to things like the invalid sector size problem
but the project has been deaf to these problems and has done nothing
whatsoever. =(

I thought maybe I could go simple and use something like elilo, The
manual was written in moonspeak, it was very missleading and had lots of
omissions, and misdirection. I downloaded the 2,200 page specification
for EFI an quickly came to realize that the Elilo documentation was a
geyser of bullshit. I think it's going to be my new standard example of
how awful linux documentation is.

Seriously, It deserves a few hundred more pages of ragging, and flaming,
and rage-ing but I've got a piece of junk to boot. =|


I don't know where Gentoo is getting it's source for Grub...


Apparently the git version of Grub was abandoned in 2015, as far as I
can tell... I'm trying to build it from source. As is appropriate the
git repository doesn't have the git scripts, I tried running autoreconf
on it but got error messages...

I cleared a few of them but I'm like:

##
atg@localhost ~/source/grub $ autoreconf
autoreconf-2.69: configure.ac: AM_GNU_GETTEXT is used, but not
AM_GNU_GETTEXT_VERSION
automake-1.15: error: cannot open < Makefile.util.am: No such file or
directory
autoreconf-2.69: automake failed with exit status: 1
atg@localhost ~/source/grub $
##

Is there a way to ebuild a "grub-git" and produce a grub install with
version = date of most recent commit on active fork?

-- 
Strange Game.
The only winning move is not to play. 

Powers are not rights.