# Framework Laptop 13 Ryzen 7040 BIOS 3.05 Release and Driver Bundle **URL:** \ **Category:** Framework Laptop 13\ **Tags:** bios-announcement\ **Created:** [April 4, 2024, 8:26am UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-05-release-and-driver-bundle/48276 "2024-04-04T08:26:02Z")\ **Posts on this page:** 20\ **Page:** 3
**Author:** ![mikeymop](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/mikeymop/32/12494_2.png) [@mikeymop](https://community.frame.work/u/mikeymop)\ **Post date:** [April 6, 2024, 12:34am UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-05-release-and-driver-bundle/48276/42 "2024-04-06T00:34:54Z")
Already on it šŸ™‚ Iā€™ll post back in a few days with any findings. But it seems promising so far, my easy reproduction of changing gnomeā€™s scaling factor did not trigger the flickering. Also very promising, is this being the _only_ error I see in dmesg: ```auto cros_ec_lpcs cros_ec_lpcs.0: EC ID not detected ``` The touchpad is still laggy though, Iā€™m starting to think thatā€™s just the touchpadā€™s refresh rate not being proportional to 60hz. ---
**Author:** ![Mario\_Limonciello](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/mario_limonciello/32/19277_2.png) [@Mario\_Limonciello](https://community.frame.work/u/Mario_Limonciello)\ **Post date:** [April 6, 2024, 1:10am UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-05-release-and-driver-bundle/48276/43 "2024-04-06T01:10:34Z")
I donā€™t see a laggy touchpad, maybe this is indicative of another issue? Check whether something is pegging a CPU, like a constant interrupt. ---
**Author:** ![mikeymop](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/mikeymop/32/12494_2.png) [@mikeymop](https://community.frame.work/u/mikeymop)\ **Post date:** [April 6, 2024, 1:21am UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-05-release-and-driver-bundle/48276/44 "2024-04-06T01:21:58Z")
Sorry should have been clear I donā€™t associate the touchpad with anything on AMDā€™s side. I actually attributed it to the i2c errors in dmesg on `<=3.03`. This is more speaking for the topic of the `3.05b` update and no longer seeing those i2c errors. Both the flickering, and the i2c errors Iā€™ve suspected were bios / IOMMU issues so I was very eager a week ago when they announced the beta. ---
**Author:** ![Kyle\_Farnung](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/kyle_farnung/32/17460_2.png) [@Kyle\_Farnung](https://community.frame.work/u/Kyle_Farnung)\ **Post date:** [April 6, 2024, 2:21am UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-05-release-and-driver-bundle/48276/45 "2024-04-06T02:21:56Z")
Installed the BIOS and drivers on Windows 11 without issue. ---
**Author:** ![Eric\_Busch](https://avatars.discourse-cdn.com/v4/letter/e/7cd45c/32.png) [@Eric\_Busch](https://community.frame.work/u/Eric_Busch)\ **Post date:** [April 6, 2024, 2:22am UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-05-release-and-driver-bundle/48276/46 "2024-04-06T02:22:26Z")
Installed the new BIOS and the driver bundle under Windows 11 on my 7840U FW13, and now the internal display turns off at the login screen. The splash boot screen displays fine, then it goes blank, and then a few seconds later the backlight turns off. Iā€™m able to connect external displays and use the machine, but the laptop display remains dark (no backlight on) and even though Windows detects the internal display (as ā€œIntegrated Monitorā€) in Device Manager, it does not appear as an available display for extension or mirroring in Display settings. troubleshooting steps taken: - reset BIOS to defaults - rolled back graphics driver - rolled back chipset driver - manually installed monitor .inf driver from the driver pack (and then rolled it back when nothing changed) This is clearly a windows/driver issue, as the display works fine in while booting, when in safe mode, and when booted from a live linux USB disk. Please help! EDIT: rolling back the display driver fixes the issue. I have opened a support ticket and will post the outcome of that here. EDIT 2: Running DDU and reinstalling the new driver from scratch has fixed the problem. Thank you Zeke and the other support staff! ---
**Author:** ![pierce](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/pierce/32/18894_2.png) [@pierce](https://community.frame.work/u/pierce)\ **Post date:** [April 6, 2024, 3:12am UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-05-release-and-driver-bundle/48276/47 "2024-04-06T03:12:02Z")
I installed the update with the EFI updater. Iā€™m running Arch Linux with kernel 6.8.2. No problems so far, dmesg looks good. But, the first boot-up after the efi update, only 512MB ram was reserved for the iGPU, even though I had configured UMA\_GAME mode in the bios. Hmm did it reset? Checking the bios config, no, it was correctly configured there, as were the all the rest of my changes. I did notice that the name and help text for this option were greatly improved! Itā€™s now called ā€œiGPU memoryā€ and explains how much is assigned in ā€œautoā€ vs ā€œgameā€ mode, depending on total memory installed. Nice. So ā€¦ I toggled it to auto, and back to game, saved and booted, and now itā€™s allocated 4GB as expected out of my 32GB total. So was it a first boot problem, and a plain reboot would have fixed it, or did toggling and re-saving the setting fix it? Iā€™m not sure ā€¦ ---
**Author:** ![Emanuel\_Loffler](https://avatars.discourse-cdn.com/v4/letter/e/71e660/32.png) [@Emanuel\_Loffler](https://community.frame.work/u/Emanuel_Loffler)\ **Post date:** [April 6, 2024, 9:04am UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-05-release-and-driver-bundle/48276/48 "2024-04-06T09:04:07Z")
Update worked for me after trying it with two old pendrives that failed. I used the microSD expansion card and a fresh microSD instead. It took about 15 minutes and required mains connected. Iā€™m in for the Beta especially because of the new password regulations. And it works like a charm! Thanks! ---
**Author:** ![Rei](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/rei/32/13593_2.png) [@Rei](https://community.frame.work/u/Rei)\ **Post date:** [April 6, 2024, 9:22am UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-05-release-and-driver-bundle/48276/49 "2024-04-06T09:22:07Z")
also successfully updated bios with efi Game mode is set for iGPU and now the available ram is 29 GB. I am curious since it isnā€™t quite the 4GB the bios claims to allocate out of my 32ā€¦ ---
**Author:** ![Charlie\_6](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/charlie_6/32/22087_2.png) [@Charlie\_6](https://community.frame.work/u/Charlie_6)\ **Post date:** [April 6, 2024, 9:27am UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-05-release-and-driver-bundle/48276/50 "2024-04-06T09:27:55Z")
I got 27.2GiB(read from btop)RAM and 4005M VRAM(read from radeontop), where did you read 29GB ---
**Author:** ![Rei](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/rei/32/13593_2.png) [@Rei](https://community.frame.work/u/Rei)\ **Post date:** [April 6, 2024, 9:37am UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-05-release-and-driver-bundle/48276/51 "2024-04-06T09:37:24Z")
I use Pop!\_OS, thereā€™s a built-in ā€œsystem monitorā€ edit: `top` gives me MiB mem: 27868.7 total. ---
**Author:** ![articulate\_elf](https://avatars.discourse-cdn.com/v4/letter/a/e47c2d/32.png) [@articulate\_elf](https://community.frame.work/u/articulate_elf)\ **Post date:** [April 6, 2024, 11:36am UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-05-release-and-driver-bundle/48276/52 "2024-04-06T11:36:55Z")
Think of Z States a bit like Intel C States. They are particular modes a processor can drop down into that disable features not necessary at a certain time for power management. Please take anything below this with a grain of salt as my understanding is very far from good. AMD 6000 series and up (as of writing this 06/04/2024) have two Z states: - Z10, which basically means the processor is turned off. Think sleep mode, but a little deeper and more power efficient. - Z9 is a slightly less low power state, where the display is still turned on and can be updated every so often, for example, to change what the clock says or to display notifications. So itā€™s less deep than normal sleep mode. This is almost certainly an oversimplification, but in one sentence, Z states are a way of radically reducing how much power your processor is drawing. If Iā€™ve got anything wrong, please let me know. ---
**Author:** ![Rijnder\_Wever](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/rijnder_wever/32/20177_2.png) [@Rijnder\_Wever](https://community.frame.work/u/Rijnder_Wever)\ **Post date:** [April 6, 2024, 2:15pm UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-05-release-and-driver-bundle/48276/53 "2024-04-06T14:15:23Z")
I got an error trying to upgrade through the Gnome Firmware application. The update _is_ listed after I ran `fwupdmgr enable-remote lvfs-testing`, but when pressing the upgrade button, I get: > Failed to create ā€˜/boot/EFI/UpdateCapsuleā€™: Read-only file system Might be a Gnome issue, though. **Solution:** Follow the steps outlined here: [fwupd - ArchWiki](https://wiki.archlinux.org/title/Fwupd#Prepare_ESP) In my case `sudo mkdir /boot/EFI`, and then restarting `fwupd.service`. ---
**Author:** ![kirelagin](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/kirelagin/32/16165_2.png) [@kirelagin](https://community.frame.work/u/kirelagin)\ **Post date:** [April 6, 2024, 2:21pm UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-05-release-and-driver-bundle/48276/54 "2024-04-06T14:21:04Z")
> [@Kieran\_Levin](#): > > UCSI I have just upgraded and I am still getting: ```auto ucsi_acpi USBC000:00: ucsi_handle_connector_change: ACK failed (-110) ``` after resuming. Nothing is even connected to the laptop (except for the modules: 2ƗUSB-C, 1ƗHDMI, 1xMicroSD). ---
**Author:** ![Hussain\_Arif](https://avatars.discourse-cdn.com/v4/letter/h/977dab/32.png) [@Hussain\_Arif](https://community.frame.work/u/Hussain_Arif)\ **Post date:** [April 6, 2024, 4:28pm UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-05-release-and-driver-bundle/48276/55 "2024-04-06T16:28:35Z")
How do I disable sg\_display=0? Will ā€˜sudo grubby --update-kernel=ALL --args=ā€œamdgpu.sg\_display=1ā€ā€™ do the job? Iā€™m really new to this ---
**Author:** ![inverse](https://avatars.discourse-cdn.com/v4/letter/i/c6cbf5/32.png) [@inverse](https://community.frame.work/u/inverse)\ **Post date:** [April 6, 2024, 4:37pm UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-05-release-and-driver-bundle/48276/56 "2024-04-06T16:37:26Z")
I havenā€™t experienced the white screen bug since Iā€™ve re-enabled scatter/gather and disabled game mode ---
**Author:** ![Hussain\_Arif](https://avatars.discourse-cdn.com/v4/letter/h/977dab/32.png) [@Hussain\_Arif](https://community.frame.work/u/Hussain_Arif)\ **Post date:** [April 6, 2024, 4:38pm UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-05-release-and-driver-bundle/48276/57 "2024-04-06T16:38:35Z")
Can you please tell me how can I re-enable it? Thank you ---
**Author:** ![Rijnder\_Wever](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/rijnder_wever/32/20177_2.png) [@Rijnder\_Wever](https://community.frame.work/u/Rijnder_Wever)\ **Post date:** [April 6, 2024, 4:45pm UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-05-release-and-driver-bundle/48276/58 "2024-04-06T16:45:14Z")
Wrong thread, but that should do the job. Better yet is to not set `amdgpu.sg_display` at all, and remove it from your configuration. However, I do not use GRUB, so Iā€™m not sure how to do that. If memory serves, you could just edit the file `/etc/default/grub`, remove all references to `amdgpu.sg_display` there, and finally regenerate using `sudo grub-mkconfig -o /boot/grub/grub.cfg`. ---
**Author:** ![Leonard](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/leonard/32/28363_2.png) [@Leonard](https://community.frame.work/u/Leonard)\ **Post date:** [April 6, 2024, 5:06pm UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-05-release-and-driver-bundle/48276/59 "2024-04-06T17:06:44Z")
I think this is the command youā€™re looking for: `sudo grubby --update-kernel=ALL --remove-args=ā€œamdgpu.sg_display=0` ---
**Author:** ![jhoff80](https://avatars.discourse-cdn.com/v4/letter/j/f0a364/32.png) [@jhoff80](https://community.frame.work/u/jhoff80)\ **Post date:** [April 6, 2024, 10:49pm UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-05-release-and-driver-bundle/48276/60 "2024-04-06T22:49:51Z")
Iā€™ve had a couple BSODs when resuming from standby. I assume this is likely related to the IRQ1 known issue, since I didnā€™t have any such issues on the previous 3.0.3 EC fix beta. BSOD is ā€œCritical process diedā€. ---
**Author:** ![mikeymop](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/mikeymop/32/12494_2.png) [@mikeymop](https://community.frame.work/u/mikeymop)\ **Post date:** [April 7, 2024, 8:34am UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-05-release-and-driver-bundle/48276/61 "2024-04-07T08:34:55Z")
After about a dayā€™s worth of use, the only alarming issue I see is that `dmesg` is spammed with ```auto xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot ``` Is this the IRQ1 failure mentioned in the known issues? [Previous page](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-05-release-and-driver-bundle/48276.md?page=2) [Next page](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-05-release-and-driver-bundle/48276.md?page=4)