Hi, I'm relaying a problem my gf is having. She has an acer laptop with Intel + nvidia hardware and a ThinkPad Thunderbolt dock. Running arch with kde. Whenever she starts bevy engine, including its demos, the dock disconnects and reconnects, causing everything connected to it to also do the same.
The journal has some GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT errors but I also have some in my journal so I think they aren't specific to bevy.
I don't understand how a user program can cause such an issue. Even if bevy has a bug I don't think it should affect peripherals? Has anyone seen something like this?
4 Comments
fuckwit_mcbumcrumble@lemmy.dbzer0.com · 5 pts · 155d
When you connect the dock does it directly connect to the Nvidia GPU or does the laptop have a mux that switches when the GPU is activated? I think Nvidia calls it advanced Optimus.maybe try forcing dGPU only in the bios and see if it still happens.
therawmeatball@piefed.social · 1 pts · 155d
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 spoiler
:::
Archr@lemmy.world · 2 pts · 154d
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.
therawmeatball@piefed.social · 2 pts · 151d
Now solved: this was a power delivery issue where if the power draw for the machine got too high and the laptops dedicated power brick wasn't connected, the dock would try and fail to deliver the amount of power needed, trip over itself, and end up shutting down entirely instead of just not delivering as much power.