Anno domini 2024 Mon, 16 Dec 05:24:39 +0000
dep via tde-users scripsit:
Greetings, one and all.
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?
1) make a backup - just in case it's your harddisk that's dying.
2) run memtest.
3) preoare a backup machine
IMO when things die unexpectidly while powered up it's hdd/ram/somecard/mainboard in
this order.
The error on r8169: that's a bug of the hardware or kernel, not sure which to blame.
It leads to dropping network connections now and then and with network-manager the kernel
modul crashes when you have wifi enabled and plug in the lan cable. I notized it to appear
~ 2 months ago (amd AMD Ryzen 7 PRO 4750U on lenovo T14 AMD gen1). You can work around it
with "pcie_aspm=off pcie_port_pm=off" added to /default/grub.
Nik
dep
Pictures:
http://www.ipernity.com/doc/depscribe/album
Column:
https://ofb.biz/author/dep/
____________________________________________________
tde-users mailing list -- users(a)trinitydesktop.org
To unsubscribe send an email to users-leave(a)trinitydesktop.org
Web mail archive available at
https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskt…
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...