16 Dec
2024
16 Dec
'24
6:02 a.m.
dep composed on 2024-12-16 05:24 (UTC):
Not even remotely a TDE problem, but you lot are known
to throw a float to a drowning man even if he fell off some other boat.
System is an Asus vanilla AMD-64 running Debian Trixie
and TDE Testing. Was running fine, long uptimes. Got up yesterday to an exploded reboot,
so something had taken place during the night. Did a power-off reboot. Now it booted to
the point of /dev/sda1 clean. Tried a reboot from grub using linux advanced mode. Once I
got it to boot all the way in rescue mode. Fiddled around, found nothing wrong, rebooted.
That's the last time I saw TDE.
Poking around, I saw a case similar to mine in which
it was suggested that the bios needed upgrading. I looked, and the date on my bios was in
2013, leading ne to think it was possible that this was true, even though I'd changed
nothing since it had been booting just fine. So on another machine I d/led the latest bios
file and flashed it. Which of course wiped all my settings because bioses seem to be dumb.
Now, when I start the machine it of course has the
bios banner, and then grub, and then:
ACPI BIOS Warning (bug): Optional FADT field
Pm2ControlBlock has valid Length but zero Address: 0x[many zeros]/0x1
(20240322/tbfadt-611)
amd_pstate: the_CPC object is not present in SBIOS or ACPI disabled
r8169 0000:05:00.0: can't disable ASPM; OS doesn't have ASPM control
/dev/sda1: recovering journal
/dev/sda1: clean, 435913/4579328 files, 5183079/18310546 blocks
If I do a warm reboot, it dies at the bios banner.
After a minute it tells me the boot device (normal hard drive) is not supported and to set
the comparability mode, press F1 to set it. Which I do, and bext boot gives me:
grub>
Which is no use at all so I reboot and now again have
a normal grub menu. This time I select Advanced mode for my Linux boot. Now it boots
happily along. And I can boit into Debian, TDE, the whole works, though now I am in rescue
mode (which looks and acts just like any ordinary boot).
Which is where I am now. In slight terror it will
crash again, but otherwise wondering how I can proceed to make things normal again,
Anyone have any ideas?
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.
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.
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata