Everything appears to be working fine on my 13in AMD. It even kept my EFI boot entries & settings this time.
Does this mean I won’t get blinking diagnostic LED’s with the new 2.8k display? Exciting if so and really happy to finally see that this was a problem with the BIOS and not an issue with my display / laptop. I’d be ignoring it (apart from my post on here) but was silently still concerned there was an underlying issue with my display which might come back to haunt me.
I’m getting the same issue on Arch and clearing the cache, clearing /var/lib/fwupd/metadata, disabling remotes and restarting the fwupd systemd unit does nothing and still doesn’t find the update even though it’s present in the lvfs-testing firmware.xmlb
There’s an update to fwupd available. I updated then ran the fwupdmgr updates and it showed up.
I very much welcome this BIOS update.
In the post above, I read: ‘This release supports standalone updates without a battery attached’. I take it that a ‘standalone update’ just is a BIOS update performed when the battery is not attached. It would be clearer - and would help those who do not know the term already - to spell that out within the post (and within any other relevant documentation).
(I was unsure whether this comment of mine should go here or else here on Github.)
@Kieran_Levin any idea if this would fix any issue mentioned here ?
I’ll be waiting for the stable upgrade to do the BIOS update.
I’m running 2.0.1, which version are you using?
Currently running into the same issue on my 7840U with 64GB RAM, with a 2.8k screen.
Had the initial bright white screen and then a black screen, then loaded into Windows and the resolution was screwed up and the AMD driver wouldn’t load.
Edit: Reinstalling the driver seems to have fixed it.
1 Like
My Laptop 13 AMD 7840U (first gen. screen) running Windows 11 24H2 with all the latest AMD drivers (Adrenaline 24.10.1, and Chipset 6.10.17.152) just updated with no problems at all. Nothing unusual happened at all. So much so that afterwards I felt I had to go into the BIOS to confirm that the update had actually installed.
1 Like
Glad you got it fixed! I freaked out for a moment… but troubleshot without emotion 
.
3.06 beta BIOS is working fine here with Linux (Manjaro) kernel 6.12 and KDE with the 2.8K screen.
PS. Running virtual machines is broken, however, “Virtualbox can’t enable the AMD-V extension. …”
hello
if that help here is the list of commands i executed:
fwupdmgr get-updates
fwupdmgr update
# here nothing appeared
fwupdmgr get-remotes
# lvfs-testing was showing but just to be sure
fwupdmgr enable-remote lvfs-testing
fwupdmgr get-remotes
# lvfs-testing still present
fwupdtool get-updates -vv
# this one showed the update
fwupdmgr refresh --force
fwupdmgr get-updates
# still nothing here no updates showing
rm -rf /var/cache/fwupd/
systemctl stop fwupd.service
systemctl start fwupd.service
fwupdmgr refresh --force
fwupdtool get-updates
# finally saw it
fwupdtool update
# bios installed
Hope that can help you, i thought the refresh --force would invalidate the cache, but it’s seems not to be the case, and i don’t know fwupdmgr well enough to go further.
tldr: success
I installed this on my FW13 today via fwupdmgr (LVFS-testing), it did require that I had power connected (failed the first time because of this), but once power was connected I was able to update without issue.
I did not do anything at the “PD auto flash detecting AC…” screen, the laptop seemed to continue without my input but also appears to be okay? USB-C power was connected to the top-right port at the time.
Reusing a template from the (infamous) 12th-gen firmware thread, here are the versions I see in the BIOS after the update:
| Component | Version |
|---|---|
| BIOS | JFP30.03.06 |
| EC | -ec:f666c |
| PD1 | 0.0.1C |
| PD2 | 0.0.1C |
Installed on FW13 AMD with original matt screen. Got the white screen, which then turned black and then, after waiting a couple of minutes, defaulted to the standard (non AMD) driver. Got lots of error messages from Adrenaline. Clicked through them. Then restarted the laptop (didn’t reinstall drivers). Everything was OK after restart!
Did it work before?
If you re-run the VirtualBox module install, what happens?
The command is ''sudo rcvboxdrv setup’ (from Installation Details)
I upgraded the BIOS on my Framework with the 2.8k screen, I haven’t noticed any issues so far. The one thing I’m missing on the BIOS still is an option to enable ReBAR for the eGPU; is it on the radar?
For Virtual machines to work on FW13 AMD, you need “SVM”.
So, look for svm in
cat /proc/cpuinfo
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good amd_lbr_v2 nopl xtopology nonstop_tsc cpuid extd_apicid aperfmperf rapl pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy
svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 hw_pstate ssbd mba perfmon_v2 ibrs ibpb stibp ibrs_enhanced vmmcall fsgsbase bmi1 avx2 smep bmi2 erms invpcid cqm rdt_a avx512f avx512dq rdseed adx smap avx512ifma clflushopt clwb avx512cd sha_ni avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local user_shstk avx512_bf16 clzero irperf xsaveerptr rdpru wbnoinvd cppc arat npt lbrv
svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold vgif x2avic v_spec_ctrl vnmi avx512vbmi umip pku ospke avx512_vbmi2 gfni vaes vpclmulqdq avx512_vnni avx512_bitalg avx512_vpopcntdq rdpid overflow_recov succor smca fsrm flush_l1d amd_lbr_pmc_freeze
Just a note that I updated last night, and its working great so far
Presumably it’d also be fine if they just permanently enable it. Yes?
I installed this on my laptop with the 2.8k display and Linux. The installation proceeded without issues, though I did have to wipe the /var/cache/fwupd directory and rerun sudo fwupdmgr refresh in order to get it to show up. On the first reboot after installation, it printed a bunch of usb usb1-port1: Cannot enable. Maybe the USB cable is bad? messages to the kernel log and the Ethernet module wouldn’t work. I shut down the system, removed power, and waited for the EC to shut down (when the lights on the Ethernet module turned off). After plugging it back in and booting again, everything seems to be working fine. That’s not a new issue though; I have noted USB screwiness on the first boot after previous firmware updates too. Other than that, everything seems to be working fine.