I have a framework laptop AMD version on the latest version of fedora 39. It will sometimes wake up to a complete white screen and cannot be recovered by moving the cursor or pressing buttons on the keyboard.
I was wondering if others have encountered the same problem, and if there is any fix this problem
I have set the parameter and let’s see if that helps. I remembered that UMA_GAME_OPTIMIZED option will consume more battery, I wonder if it is true.
Finally, here is a single data point. I used to only have a blinking white strip in the middle of the screen for around once a week, which is not annoying, since I can still install updates and restart. After I added 8 more GB of ram (8 → 16), this problem becomes much worse, the entire screen turns white and happens around once every two days.
I don’t know if this change in behavior is caused by an update or the ram upgrade. But I hope this helps in some way.
Also reporting in on this issue. I have a machine with the exact same configuration and OS version reported by Cheng (Fedora 39 6.6.4-200 and FW v3.03 on 13" AMD, mine was a Batch 11), experiencing a blank white screen occasionally on wake.
Some notes: The system doesn’t seem to be locked up.
The cursor still appears and can be moved around. The cursor will change appropriately according to the content that should be on the screen, e.g. to drag the corner of a window.
Can still access a vterm with CTRL + ALT + FX to reboot.
I had the same issue. As per this thread, I changed UMA_GAME_OPTIMIZED in the BIOS. So far (1 day) the issue seemed to have gone away. I stress ‘tested’ it by running a couple of games where the issue popped up the most reliantly.
I have recently switched to silverblue, the issue did not occur during setup phase (with installation of large packages in distrobox, many rebasing etc.). But come back immediately after I started editing large documents in vscodium. So this align with the assumption that this is a (video) memory issue.
Appreciate the update. I have not needed this myself, but it appears to be one of those issues that affects some folks and not others. There is another bug coming up that we are getting in front of the Fedora team. There is an active patch for it (kernel 6.7.x), but I am working to get this sorted with Fedora shortly.