I was on 3.04 beta, and on my machine fwupdmgr wasn’t able to find the 3.05 stable update until I disabled the lvfs-testing remote using fwupdmgr disable-remote lvfs-testing
- then everything worked.
It still won’t boot if its connected to a TB4 dock. I’m not impressed.
@H_Sundelin
Which make/model of TB4 dock is it?
A Dock I have was having all sorts of problems with my FW16, until a firmware upgrade for my dock came out about 1 month ago. No problems ever since. I had to plug the dock into a windows PC to get its firmware updated, but after the update it works fine on a FW16 and Linux.
So, it might be worth checking for any Dock firmware updates from the Dock manufacturer.
Its a Lenovo TB4 Universal Dock (40B00135EU). I upgraded its firmware recently.
@H_Sundelin
When you say it won’t boot. Does it boot, but just not see the TB4, or does it fail to get past the BIOS and not even try to boot the OS?
Are you using Windows or Linux?
With my Dock, it boots into the Linux OS, but does not see the Dock until I unplug/plug it in.
It does not boot at all. Screen stays completely black, only thing that works is the power button (you get the white light). You can only boot with the dock disconnected.
I’m using Win11, but I don’t get even to BIOS startup screen with the memory stuff. (First comes this short message with memory, then the logo splashscreen) I only get black screen with the dock connected.
I did make a ticket to FW about it in the summer, but no progress.
@H_Sundelin
When you say “Screen stays completely black”, do you mean the Laptop screen, or an external screen. The BIOS will only ever display on the Laptop screen, not the external screen.
Have you raised the issue here:
It might make more progress there.
Is your 1st boot device set to SSD or USB in the BIOS?
No. I even tried to set all USB boot off in the BIOS, but no effect.
All screens stay black. Only thing that turn on is the power button light. If you wait, the fan might start. If you push power button again it turns off immediately.
If you unplug the dock, everything works fine.
If anyone with some time on there hands could consider extending the BIOS section of the visually impaired guide for this new BIOS, that would be extremely helpful.
This would include detaisl of the battery extender settings.
I have noted in the BIOS section that different BIOS versions that varied in whether the cursor starts on the first item of the advanced menu or above it. It would be good to know whether this applied in the same way to the other menus.
There is no need to edit the visually impared guide directly if you’d rather post the info in a new post and I’ll edit it all together.
Also any individual snippets of info rather than a complete coverage of the new BIOS is fine.
Thank you!
Is this update available in fwupdmgr
yet? It seems to believe I’m up to date.
Edit: After running system updates and then trying to use fwupdmgr got me to install the update. Not sure why that’s needed and what the purpose of refresh and get-updates is, but oh well I suppose.
Yes, I installed it yesterday using the stable LVFS channel.
Did the bios update change the default vram values?
Setting the option to “Gaming” in the bios, and now my iGPU is reporting 8gb of vram. Not really an issue for me since I have 64gb. But I did prefer having 4gb as an option.
You can still set it to 4GB with Smokeless_UMAF
On 3.05 I am unable to boot into windows with Auto iGPU VRAM settings. On gaming mode I am booting just fine. I have tried loading optimized defaults, booting in safe mode, and reinstalling graphics drivers. When booting on auto I get to a white screen and freeze.
Windows 11 24H2, 7840HS, 7700S, and 64GB 5600MTs CL40 RAM.
You have the exact System Config thats problemstic with current AMD Drivers. There is a note on the 3.05 Bios, that Systems with 64+GB of Ram can have Problems with later than 24.8.1 Adrenaline Drivers when not beeing set to Gaming in Bios.
I have the exact same system, except Windows 10. I’ve been using latest drivers since day 1, and nary an issue. Eat it, 11.
I am unfortunately experiencing major GPU flakyness on Fedora 41 after the upgrade. I filed an issue here. I hope it gets resolved soon, as this gets in my way a ton, as it isn’t only affecting gaming but also video playback in Firefox and MPV and requires frequent hard resets.
wait, smokeless_UMAF work on framework?