| 1 |
Hello, Peter. |
| 2 |
|
| 3 |
On Fri, Apr 21, 2017 at 06:56:32 +0100, Peter Humphrey wrote: |
| 4 |
|
| 5 |
[ .... ] |
| 6 |
|
| 7 |
> I also have an Asus motherboard, but for Intel hardware. |
| 8 |
|
| 9 |
> In your BIOS secure-boot page, do you have a section called Key Management? |
| 10 |
> When I was working on getting my machine to boot, a year ago, I was advised* |
| 11 |
> to hit the item "Load default keys". This was to clear out any dross that |
| 12 |
> might have found its way into the secure-boot mechanism and enable me to |
| 13 |
> boot in Other mode - i.e. not a Microsoft secure boot. |
| 14 |
|
| 15 |
I tried this, yes. |
| 16 |
|
| 17 |
> As Mick says, you need to install a kernel image in the boot partition |
| 18 |
> (which must be FAT32). There are several ways to do this; I use bootctl from |
| 19 |
> sys-boot/systemd-boot (don't worry - it doesn't depend on having the rest of |
| 20 |
> systemd around it). It allows a choice of system to boot, without the |
| 21 |
> gymnastics needed by GRUB-2, but you have to maintain the different images' |
| 22 |
> config files manually. |
| 23 |
|
| 24 |
I actually used the standard grub2 stuff as documented in the Gentoo |
| 25 |
handbook. |
| 26 |
|
| 27 |
I've managed to get the BIOS to see and boot into grub2. The critical |
| 28 |
step which enabled this was copying grubx64.efi into |
| 29 |
/boot/efi/boot/bootx64.efi, as hinted at by the Gentoo handbook. It |
| 30 |
seems the Asus BIOS is one which will only recognise the boot image at |
| 31 |
precisely that location. |
| 32 |
|
| 33 |
Gentoo itself, of course, doesn't boot yet. Nothing is ever that |
| 34 |
simple. In the grub2 article in the Gentoo wiki, there is a most |
| 35 |
infuriating injunction, which could scarcely be worse, except by being |
| 36 |
absent entirely: |
| 37 |
|
| 38 |
"The grub-mkconfig utility does not work properly when using |
| 39 |
software RAID. Manual configuration of the scripts in /etc/grub.d/ |
| 40 |
is necessary, as otherwise after installation, the system will be |
| 41 |
left in a non-bootable state." |
| 42 |
|
| 43 |
. It would have been nice if the author of that warning could have left |
| 44 |
one or two hints about precisely needs doing. The scripts in |
| 45 |
/etc/grub.d/ are massive (~1200 lines), and I'll probably need to read |
| 46 |
the grub manual, which is over 7000 lines long. Come back, lilo, all is |
| 47 |
forgiven! |
| 48 |
|
| 49 |
Could somebody here please give me some hints about what I need to do to |
| 50 |
these grub scripts to get my mdadm RAID-1 root partition recognised and |
| 51 |
started by grub? |
| 52 |
|
| 53 |
> Let me know if I can' help with bootctl. Good luck! |
| 54 |
|
| 55 |
grub2 is a monstrosity. All I want to do is to boot Gentoo Linux, not |
| 56 |
go through all the machinations required by grub. |
| 57 |
|
| 58 |
I think I'll look at bootctl. It's looks far more likely to give me |
| 59 |
what I want than grub2. Does it cope OK with mdadm RAID setups? |
| 60 |
|
| 61 |
> * An advantage of buying a newfangled system ready built. |
| 62 |
|
| 63 |
> -- |
| 64 |
> Regards |
| 65 |
> Peter |
| 66 |
|
| 67 |
-- |
| 68 |
Alan Mackenzie (Nuremberg, Germany). |
Archives