| 1 |
On Wednesday, 18 September 2019 14:20:11 BST Mick wrote: |
| 2 |
> On Wednesday, 18 September 2019 09:43:11 BST Peter Humphrey wrote: |
| 3 |
> > On Tuesday, 17 September 2019 07:23:10 BST Peter Humphrey wrote: |
| 4 |
> > |
| 5 |
> > Well, it seems to be working now - mostly. |
| 6 |
> > |
| 7 |
> > The fix was to write a new gpt label, create all the partitions and build |
| 8 |
> > a new system: no use of earlier packages. User data came from backups. |
| 9 |
> |
| 10 |
> This sounds too drastic a repair procedure, unless the GPT table entries |
| 11 |
> themselves were corrupted, but ... whatever works. :-) |
| 12 |
|
| 13 |
Yes, it is, but by this time I had no confidence in my ability to patch over |
| 14 |
the holes, nor in the system doing as I expected. It seemed time for drastic |
| 15 |
measures. |
| 16 |
|
| 17 |
> > Meanwhile, I used bootctl and efibootmgr to create and delete boot entries |
| 18 |
> > in the efi data until I finished up with this arrangement: |
| 19 |
> > |
| 20 |
> > # bootctl |
| 21 |
> > systemd-boot not installed in ESP. <---- Note 1 |
| 22 |
> > |
| 23 |
> > System: |
| 24 |
> > Firmware: UEFI 2.31 (American Megatrends 5.09) |
| 25 |
> > Secure Boot: disabled |
| 26 |
> > Setup Mode: user |
| 27 |
> |
| 28 |
> If you are not using systemd-boot, is bootctl of any use vis-à-vis the |
| 29 |
> efibootmgr command? |
| 30 |
|
| 31 |
It's simpler to operate, I think, and it's been good enough for me up to now. |
| 32 |
|
| 33 |
--->8 |
| 34 |
|
| 35 |
> Perhaps bootctl is now meant to operate (without breaking things) with |
| 36 |
> systemd-boot fully installed and configured. If you're not using |
| 37 |
> systemd-boot it tries to be too clever by half. |
| 38 |
|
| 39 |
But I haven't seen any version changes in anything relevant to this. |
| 40 |
|
| 41 |
> > Note 2: I've tried to change this with 'efibootmgr -b 00 -L "Gentoo |
| 42 |
> Linux"', |
| 43 |
> |
| 44 |
> > to no avail. It does nothing I can see. |
| 45 |
> |
| 46 |
> I think --label can only be specified when you --create a new entry in the |
| 47 |
> UEFI boot menu. If there is an entry already present, I think you cannot |
| 48 |
> modify it. When I get things wrong at menu entry creation time, I delete |
| 49 |
> the whole entry and reconstitute it afresh. |
| 50 |
|
| 51 |
Ah, now why would the man page not say this? |
| 52 |
|
| 53 |
> > Note 3: This title comes from the file named two lines later; it has |
| 54 |
> nothing to do with the Title of Note 2. |
| 55 |
> |
| 56 |
> Hmm ... I wonder what bootctl reads to populate its "title:" field. Would |
| 57 |
> you care to share the output of: |
| 58 |
> |
| 59 |
> efibootmgr -v |
| 60 |
|
| 61 |
Taken just now, at 16:25 GMT: |
| 62 |
|
| 63 |
# efibootmgr -v |
| 64 |
BootCurrent: 0000 |
| 65 |
Timeout: 1 seconds |
| 66 |
BootOrder: 0000,0001,0002 |
| 67 |
Boot0000* EFI Stub HD(1,GPT,95b0a3f6-eae2-445c- |
| 68 |
b098-3c8174588948,0x800,0x7f800)/File(\EFI\BOOT\BOOTX64.EFI) |
| 69 |
Boot0001* CD/DVD Drive BBS(CDROM,,0x0)..GO..NO........o.T.S.S.T.c.o.r.p. |
| 70 |
.C.D.D.V.D.W. .S.N.-. |
| 71 |
2.0.8.F.B....................A...........................>..Gd-.;.A..MQ..L. |
| 72 |
1.S.3.2.Y.6.G.B.0.C.B.0.G.K. . . . . . ........BO |
| 73 |
Boot0002* Hard Drive BBS(HD,,0x0)..GO..NO........o.C.T.1.0.0.0.B.X. |
| 74 |
1.0.0.S.S.D. |
| 75 |
1....................A...........................>..Gd-.;.A..MQ..L. |
| 76 |
5.1.4.0.0.F.2.0.8.3.4.6. . . . . . . . ........BO..NO........o.C.T. |
| 77 |
1.0.0.0.B.X.1.0.0.S.S.D. |
| 78 |
1....................A...........................>..Gd-.;.A..MQ..L. |
| 79 |
5.1.4.0.0.F.2.0.8.3.F.8. . . . . . . . ........BO..NO..........S.A.M.S.U.N.G. |
| 80 |
.M.Z.V.P.V.2.5.6.H.D.G.L.-. |
| 81 |
0.0.0.0.0....................A.......................................J..Gd-.;.A..MQ..L.S.A.M.S.U.N.G. |
| 82 |
.M.Z.V.P.V.2.5.6.H.D.G.L.-.0.0.0.0.0........BO |
| 83 |
|
| 84 |
Is that the sort of thing you were expecting? I can't say it means much to me. |
| 85 |
|
| 86 |
-- |
| 87 |
Regards, |
| 88 |
Peter. |
Archives