this post was submitted on 07 Apr 2026
7 points (100.0% liked)
Linux Questions
3854 readers
7 users here now
Linux questions Rules (in addition of the Lemmy.zip rules)
- stay on topic
- be nice (no name calling)
- do not post long blocks of text such as logs
- do not delete your posts
- only post questions (no information posts)
Tips for giving and receiving help
- be as clear and specific
- say thank you if a solution works
- verify your solutions before posting them as facts.
Any rule violations will result in disciplinary actions
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Hello, I'm the one the post is about, and I did a bit more digging: turns out the laptop does have advanced optimus, but switching to dGPU only from the bios just made the problem appear as soon as i logged in. So, I did a bit more digging, and it turns out i can trigger the issue with anything that actually gets the dGPU to get up and do something, such as turning on blender, or running firefox with prime-run and opening a website that can stress the gpu a tiny bit. For some reason anything that puts over a miniscule amount of work on the dGPU is enough to make either of the ports i can connect the thunderbolt dock through fail, somehow.
For added detail I'm on a phn16-73, one of the ports is actually thunderbolt 4 while the other is merely a USB-C that happens to have support for displayport over usb c.
Also, here's a full journalctl excerpt of the display breaking because i open blender and coming back as soon as i quit.
spoiler
Not saying this will solve your issue. But you might also want to check dmesg logs. Since this has to do with hardware it could be driver issues and those might not show up in journal. Especially since it has to do with USB.