Ever since I got this laptop sometimes while booting it causes some strange glitches, like it’s loosing sync
https://files.catbox.moe/mue1dq.mp4
But this only happens during boot and stops once the OS is loaded (also happened with just Windows before I installed Fedora)
https://files.catbox.moe/s2yiqz.mp4
Is this a known issue? Did I setup something wrong?
Seems to have stopped since I upgraded the kernel to 6.8.4
I just received my laptop and the same thing is happening to me. It only happens during boot (once an os is loaded, even live ones, it goes away), and it happened before I even installed anything. I updated the BIOS to 3.03 and the kernel to 6.8.7 (using fedora 40) it still persist.
Edit: it doesn’t always happen, about half of the time
Just had it happen while entering BIOS, definitively has nothing to do with any OS then
It seems unrelated to OS. Glitches in grub would confirm the same, since the OS is not yet loaded.
Maybe the cable of the monitor is not well attached. You could try to open your laptop, detach the monitor cable and reattach it.
But a connection issue wouldn’t disappear once the driver loads right?
That is indeed surprising. Nevertheless, if I see screen flicker like this in bootloader and bios, I would suspect hardware, either broken or poorly connected. With a FW laptop this shouldn’t take too much time, right?
In other words, if it was my laptop, I would try it. 
I’ve been talking to support trying to diagnose the issue. It doesn’t seem to be a hardware issue since once the laptop is booted it works perfectly and there is no hint of a flicker. From looking at a verbose boot the point where it’s resolved is when the amdgpu driver is loaded. Up until now I did many things and none of them resolved it for now:
The last step was sending support a bunch of logs, but this was yesterday so I don’t expect to hear anything until next week. I have to say that support was very responsive and through, even if we didn’t find the issue yet, it was a very nice experience.
One question if you don’t mind, are you using the RAM/SSD bought from framework or a third party one? Also, you don’t have a dGPU either, right?
Any news I have on my front I’ll let you know
Wanted to but then it stopped happening, since it is back now I’ll try it once I’m home
The RAM I got from Framework (32GB), SSD I bought my own (SK hynix Gold P31 1TB)
And no, I don’t have the dGPU only the integrated one from the 7840HS
Ok, I asked because I am using ram from Crucial and I was worried that was the issue (it’s on the supported list but still), but if you are using the one from framework it makes it less likely. I also have no dGPU.
And mine come and goes, sometimes it boots 5 times without issue and then others it happens every time.
Update on this (!!!)
A few days ago I received the new screen that support sent me, and I just made the repair now (I couldn’t sooner because I wasn’t in my home town) which was literally 15 minutes carefully following instructions with 7 steps, and the glitches are gone! So it was likely a defect with the screen.
I really want to thank support for how they handled it, because they were very through and every person on the team knew what they were talking about. Though a tad long, the diagnostics process to find the issue was very directed and easy to follow, and this was just because this was a very weird problem. Most of the time was actually waiting for FedEx to deliver and waiting to be able to go home to collect the part.
It gives me a lot of confidence, not only on the resilience of this laptop, but on the company that supports it c:
Edit: Another fun fact is that now it seems to boot faster? It may be placebo effect because I did not do any kind of measurement, but before it seemed to be on the logo screen for about 3 seconds and now it doesn’t appear more than one (and I didn’t change any configuration in between)
Glad to hear you fixed your laptop, although I am very curious how the screen itself can be defective in a way so this only appears during boot
My guess is the problem only shows itself at particular resolutions.
Maybe the BIOS and GRUB screens are different resolutions than the OS.
I am very curious about that too. The most reasonable culprit seemed to be drivers or something like that, and I was a bit skeptical if changing the screen would work, but it did the trick.
Maybe it has to do with resolution as James say, or it has different presenting modes and the default one from the BIOS triggers the issue. It was also weird because it didn’t always happen.
Anyways, it’s a mystery for now. I would love to know if Framework figures out what was the issue eventually.