Open gawells opened 8 years ago
Check your power management rules.
Could you please elaborate? I don't see any obvious settings in bumblebee.conf that would affect this. There's nothing in my /etc/udev/rules.d directory and I can't run nvidia-settings (even when the nvidia module is loaded or via primusrun). Nothing in the kde power saving profiles seems to be relevant either.
This sounds like a communication interrupt between cpu process and your graphics card. My idea was that this is triggered by closing your laptop lid, which typically initiates a suspend or hibernate. I doubt a solution would be in udev rules, from what I know, thats associated with booting, loading drivers and/or plugging in devices; I believe the issue lies with the pci.See "PCI configuration space" under github's bumblebee project wiki called acpi-for-developers and use that information to tease out whats going on.Else, turn off all power management events, no idea how kde works, I just use raw arch linux so check the arch wiki for power management. There is probably a blurb about kde in there.I can't help you troubleshoot further, but am interested in hearing about your solution. Godspeed.
'PmMethod=" in bumblebee.conf might lead to somethingCheck out the multi-monitor-setup on the bumblebee wiki, you may find a solution there maybe.
Thanks, I'll see what I can find. What I forgot to mention: this happens when the programs are still running. If I close them before closing the lid there isn't a problem
Well, there indeed seems to be something triggered when you close the lid that interrupts the running application. Currently we do not support suspend for instance, so if something alike happens you’re screwed. Is there anything in dmesg?
I've encountered this with two molecular graphics programs (vmd and pymol) launched with primusrun. If I close the laptop (Asus N751JX) lid for long enough, and then try to access them after opening the lid again, both programs freeze. Additionally an xorg process consumes 100% of one of my cpu cores. I'm forced to do a hard reset afterwards.