said Felix Miata via tde-users:
| UEFI BIOS are known to have a myriad of possible bugs, especially older
| ones, like from 2013. BIOS updates are known to have risks. Motherboard
| makers historically have recommended to skip them unless yours is known
| to have particular problem solved by a newer BIOS. As when UEFI booting,
| booting is under the control of the UEFI firmware, and the content of
| NVRAM, corruption of it upon upgrade poses a high risk of things like
| what happened to you. Are your Trixie and Sid installed in UEFI mode? If
| yes, show us output from efibootmgr -v. You may need to purge some junk
| from NVRAM and/or add a new Trixie or Sid NVRAM entry using efibootmgr
| to re-institute predicable boot behavior.
Here's the output:
BootCurrent: 0004
Timeout: 0 seconds
BootOrder: 0004,0000,0001,0002,0003
Boot0000* ubuntu
HD(4,GPT,f3d5923e-cff9-4b47-beb9-be3a8442e1a0,0x800,0x96000)/File(\EFI\ubuntu\shimx64.efi)
dp: 04 01 2a 00 04 00 00 00 00 08 00 00 00 00 00 00 00 60 09 00 00 00
00 00 3e 92 d5 f3 f9 cf 47 4b be b9 be 3a 84 42 e1 a0 02 02 / 04 04 34 00
5c 00 45 00 46 00 49 00 5c 00 75 00 62 00 75 00 6e 00 74 00 75 00 5c 00 73
00 68 00 69 00 6d 00 78 00 36 00 34 00 2e 00 65 00 66 00 69 00 00 00 / 7f
ff 04 00
Boot0001* UEFI OS
HD(4,GPT,f3d5923e-cff9-4b47-beb9-be3a8442e1a0,0x800,0x96000)/File(\EFI\BOOT\BOOTX64.EFI)
dp: 04 01 2a 00 04 00 00 00 00 08 00 00 00 00 00 00 00 60 09 00 00 00
00 00 3e 92 d5 f3 f9 cf 47 4b be b9 be 3a 84 42 e1 a0 02 02 / 04 04 30 00
5c 00 45 00 46 00 49 00 5c 00 42 00 4f 00 4f 00 54 00 5c 00 42 00 4f 00 4f
00 54 00 58 00 36 00 34 00 2e 00 45 00 46 00 49 00 00 00 / 7f ff 04 00
Boot0002* ubuntu
HD(4,GPT,f3d5923e-cff9-4b47-beb9-be3a8442e1a0,0x800,0x96000)/File(EFI\Ubuntu\grubx64.efi)
dp: 04 01 2a 00 04 00 00 00 00 08 00 00 00 00 00 00 00 60 09 00 00 00
00 00 3e 92 d5 f3 f9 cf 47 4b be b9 be 3a 84 42 e1 a0 02 02 / 04 04 32 00
45 00 46 00 49 00 5c 00 55 00 62 00 75 00 6e 00 74 00 75 00 5c 00 67 00 72
00 75 00 62 00 78 00 36 00 34 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04
00
Boot0003* Hard Drive BBS(HD,,0x0)
414d474f414d4e4faf000000010000006f0057004400430020005700440036003000300033004600520059005a002d00300031004600300044004200300000000501090002000000007fff040002010c00d041030a0000000001010600001103120a000000ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce6390056004500480030004c004c00320020002000200020002000200020002000200020002000200000007fff0400414d424f
dp: 05 01 09 00 02 00 00 00 00 / 7f ff 04 00
data: 41 4d 47 4f 41 4d 4e 4f af 00 00 00 01 00 00 00 6f 00 57 00 44 00
43 00 20 00 57 00 44 00 36 00 30 00 30 00 33 00 46 00 52 00 59 00 5a 00 2d
00 30 00 31 00 46 00 30 00 44 00 42 00 30 00 00 00 05 01 09 00 02 00 00 00
00 7f ff 04 00 02 01 0c 00 d0 41 03 0a 00 00 00 00 01 01 06 00 00 11 03 12
0a 00 00 00 ff ff 00 00 7f ff 04 00 01 04 3e 00 ef 47 64 2d c9 3b a0 41 ac
19 4d 51 d0 1b 4c e6 39 00 56 00 45 00 48 00 30 00 4c 00 4c 00 32 00 20 00
20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 00 00 7f
ff 04 00 41 4d 42 4f
Boot0004* debian
HD(4,GPT,f3d5923e-cff9-4b47-beb9-be3a8442e1a0,0x800,0x96000)/File(\EFI\debian\shimx64.efi)
dp: 04 01 2a 00 04 00 00 00 00 08 00 00 00 00 00 00 00 60 09 00 00 00
00 00 3e 92 d5 f3 f9 cf 47 4b be b9 be 3a 84 42 e1 a0 02 02 / 04 04 34 00
5c 00 45 00 46 00 49 00 5c 00 64 00 65 00 62 00 69 00 61 00 6e 00 5c 00 73
00 68 00 69 00 6d 00 78 00 36 00 34 00 2e 00 65 00 66 00 69 00 00 00 / 7f
ff 04 00
In that I don't have ubuntu on the machine anymore, and haven't for awhile,
I'm a little bit surprised that it's there. I do not know which of the
other three I should keep. Ever since the big BIOS rejiggering of a decade
ago, what once was clear has been a mystery to me. So in addition to not
knowing which one(s) to keep, I have no idea how to get rid of any I don't
want or need. Suggestions, advice, or knowledge from the above?
| Check your installations for automatic upgrades to installation and/or
| firmware. One of these could be the reason why the reboot explosion. I
| disable and or purge such things from my installations. They're mine. I
| decide if and when it's time for things like upgrades or new kernel
| additions to occur on mine.
I do not have anything set to automatically upgrade, for exactly the reason
you state. And I should note that the problem appeared before the BIOS
upgrade -- which from the date brought me clear to 2014 -- which does seem
to have been successful.
--
dep
Pictures: http://www.ipernity.com/doc/depscribe/album
Column: https://ofb.biz/author/dep/
____________________________________________________
tde-users mailing list -- users@xxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxx
Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@xxxxxxxxxxxxxxxxxx
