You are not logged in.
Let be upfront and say I apologize on the vagueness but I not sure how to describe it other than post my method.
[~]: cat /proc/acpi/bbswitch
0000:01:00.0 ON
[~]: sudo tee /proc/acpi/bbswitch <<<OFF
[sudo] password for jarvis:
OFF
[~]: cat /proc/acpi/bbswitch
0000:01:00.0 ON
[~]: optirun glxgears
[VGL] ERROR: in readback--
[VGL] 246: Window has been deleted by window manager ## Me killing the optirun window
[~]: sudo tee /proc/acpi/bbswitch <<<OFF
OFF
[~]: cat /proc/acpi/bbswitch
0000:01:00.0 OFF
[~]: I have to run 'optirun glxgears' after ever boot to have the ability to use bbswitch. This seems to have started with the latest bbswitch update and I am not sure how to resolve this.
bbswitch 0.6-7
linux 3.9.2-1
bumblebee 3.2.1-1Cheers.
Last edited by doug piston (2013-05-15 12:32:14)
Offline
I maybe have similar issues with bumblebee. For me bumblebee doesn't get started correctly on boot, so I have to run systemctl restart bumblebeed manually to get it fixed.
Can you try running systemctl restart bumblebeed before trying to change the cards status with bbswitch to see if it fixes your issues? ![]()
Offline
Interesting...
[~]: sudo systemctl status bumblebeed
[sudo] password for jarvis:
bumblebeed.service - Bumblebee C Daemon
Loaded: loaded (/usr/lib/systemd/system/bumblebeed.service; enabled)
Active: active (running) since Thu 2013-05-16 08:38:34 PDT; 1min 28s ago
Main PID: 304 (bumblebeed)
CGroup: name=systemd:/system/bumblebeed.service
└─304 /usr/sbin/bumblebeed
May 16 08:38:35 watson bumblebeed[304]: [ 2.559700] [INFO]/usr/sbin/bumblebeed 3.2.1 started
May 16 08:38:35 watson bumblebeed[304]: rmmod: ERROR: Module nvidia is in use
May 16 08:38:37 watson bumblebeed[304]: [ 5.570892] [ERROR]Unloading nvidia driver timed out.
[~]: cat /proc/acpi/bbswitch
0000:01:00.0 ON
[~]: sudo tee /proc/acpi/bbswitch <<<OFF
OFF
[~]: cat /proc/acpi/bbswitch
0000:01:00.0 ON
[~]: sudo systemctl restart bumblebeed
[~]: cat /proc/acpi/bbswitch
0000:01:00.0 OFFSo yes it seems restarting bumblebee fixes the issue. Have you submitted a bug report?
Offline
do you use nouveau or the nvidia binary driver?
i know that
sudo tee /proc/acpi/bbswitchhas no effect when the nvidia driver is loaded, you have to rmmod nvidia first
I don't know why the driver would be loaded at boot though
Offline
Yes, I already submitted a bug report. It seems like it isn't an upstream bug though. The solution is blacklisting the nvidia module on boot.
Create a file /etc/modprobe.d/blacklist-nvidia.conf with this code:
blacklist nvidiaOffline
You should submit a bug report about this next time. I only found this on the forums by chance. I fixed it in the package but you can't sensibly expect devs to check the forums all day.
Offline
@Svenstaro Post #6 states a bug was submitted. That is why I did not submit one. I completely understand that it is impossible for developers to follow every forum. Next time I will submit my own bug report.
Last edited by doug piston (2013-05-17 00:35:34)
Offline
I think that you may not have read theat post #6 closely enough. He said he submitted a bug, but it does not seem like an upstream problem. I take this to mean he reported it upstream.
Offline
Right, and this was clearly a packaging problem and should have been reported to Arch, not upstream.
Offline
I removed the blacklisting from /etc/modprobe.d/ before upgrading and works as intended. Next time I will submit a bug. Thanks.
Edit: Meant before, not after. Kind of a big difference.. ![]()
Last edited by doug piston (2013-05-17 22:33:22)
Offline
I added the blacklist to that file in the new package. Why would you remove it? You want nvidia blacklisted.
Offline
I meant I removed the one created. I looked through the PKGBUILD before install and saw that was what you had done. Just wanted to get rid of the one I created myself.
Offline