Random Linux fix: machine would not obey changes to efibootmgr... kept on repopulating (old) grub entry. Fix was to delete the folder in /boot/efi manually. Also UEFI sucks. #Linux#efibootmgr#uefi
Spent the afternoon trying to get my 3500U to downclock to anything lower than 1.4GHz... long story short, amd_pstate is gatekept by Lenovo's unwillingness to allow us to enable ACPI on the BIOS of the Thinkpad T495, where there is a huge amount of people complaining about this and yet no BIOS update has been provided... some work is ongoing on kernel 6.8+ to bring compatibility to AMD APUs but we are not there yet... Of course, if I had Windows, this works, regardless of the BIOS. So there's that. I'll wait for the geniuses to crack this CPU power savings and underclocking. Meantime? Will carry my laptop charger, just in case I need to juice it up.
I tried to update the Framework 13 AMD according to the help page and it does not work. :blobcatsadpats:
I get an "update progess: completed" from H2OFFT but then the screen goes black, device stays powered on but is unresponsive. I forced a shutdown (hold power button) after 2 hours. On booting again I get "Update Failed! EFI Error Code 2, Decompress failed!"
Modder made an IRC client that runs entirely inside the motherboard’s BIOS chip
Phillip Tennen, developer of the open-source axleOS, has recently decided to use what he learned from that project to create an IRC client that runs entirely within the UEFI pre-boot environment, with no operating system required. This “UEFIRC” is n ...continues
Wenn man schon einmal dabei ist, sein Windows von dem Rechner wegzuputzen und ein frisches modernes und sicheres Linux aufzusetzen, sollte man auch gleich das BIOS aktualisieren.
So it seems my Thinkpad T14 AMD Gen 1 is bricked somehow. No idea how it happened. LEDs and fan are working but I don' t get anything on the screen (internal and external).
Disconnecting batteries and using the reset switch doesn't help.
It seems like these are the typical signs for a bricked BIOS and I'm thinking about trying to reflash the SPI NOR on the mainboard.
Oh dear, why do such things happen when warranty has expired...
Ok, the laptop is finally up and running again. But what a journey!
I'm still not hundred percent sure what happened, but my guess is that #kdediscover (with integrated support for #lvfs) initiated a #bios update without me noticing the day before. And as I was in a hurry and distracted, I accidentally hard-reset the machine during the update that ran on the next boot and therefore corrupting the flash content.
I guess I will disable LVFS as update source in Discover for now...
Before I add the E5-1660, I will first test the E5-1620 that came with this motherboard.
The idea is to see it post, run it for a few days, and then make the original upgrade I had originally planned.
Originally, I had an E5-1650 in the other motherboard. Things didn't go so well -A mix of what may have been discovery of liquid metal (likely something else) and myself bending the pins trying to clean it out.
This is how we ended up with this "new" motherboard with CPU.
I noticed a significant performance improvement after updating the bios.
Prior to this, I was generally concerned, as I noticed my PC was running a little hotter and seemed a little sluggish, plus the auto fan speed didn't seem to be as responsive.
The moment the BIOS completed the update, it was an instant improvement.