Regression in the gpu-manager: bbswitch quirks erroneously applied

Bug #1289420 reported by Marcin Sągol on 2014-03-07
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
ubuntu-drivers-common (Ubuntu)
High
Alberto Milone

Bug Description

Latest update to 0.6 with small 331 drivers update results with some artefacts and not working prime-select:

$ sudo prime-select nvidia
Error: alternatives are not set up properly
Error: nvidia mode can't be enabled

Alberto Milone (albertomilone) wrote :

Please make sure that ubuntu-drivers-common (1:0.2.89.3) is installed.

Marcin Sągol (soee) wrote :

Hi Alberto,
yes exactly this version is installed.

Alberto Milone (albertomilone) wrote :

Please attach the following files:

1) The output of "dkms status"
2) your /var/log/gpu-manager.log

Marcin Sągol (soee) wrote :
Marcin Sągol (soee) wrote :
Marcin Sągol (soee) wrote :

Both files added. Sorry that in separate comment, but i couldn't find option to send both in one :)

Alberto Milone (albertomilone) wrote :

can you also attach the output of "dmesg" please?

Marcin Sągol (soee) wrote :

dmesg output

affects: nvidia-prime (Ubuntu) → ubuntu-drivers-common (Ubuntu)
Changed in ubuntu-drivers-common (Ubuntu):
assignee: nobody → Alberto Milone (albertomilone)
importance: Undecided → High
status: New → Triaged
Changed in ubuntu-drivers-common (Ubuntu):
status: Triaged → In Progress
Alberto Milone (albertomilone) wrote :

I've just committed and uploaded a fix for this bug. ubuntu-drivers-common (1:0.2.89.4) will solve the problem.

summary: - Can't switch to nvidia - prime-select fails
+ Regression in the gpu-manager: bbswitch quirks erroneously applied
Alin Andrei (nilarimogard) wrote :

I just upgraded to ubuntu-drivers-common and bbswitch is only partially fixed: now bbswitch works, but it's always on, even if I select to use the Intel card:

$sudo prime-select intel
Info: the intel profile is already in use

$cat /proc/acpi/bbswitch
0000:01:00.0 ON

Alberto Milone (albertomilone) wrote :

please attach the new dmesg and /var/log/gpu-manager.log

Alin Andrei (nilarimogard) wrote :
Alin Andrei (nilarimogard) wrote :

dmesg log attached here. I'm guessing this is what's causing the issue:

    7.355529] init: Failed to spawn hybrid-gfx main process: unable to execute: No such file or directory
[ 7.396415] bbswitch: version 0.7
[ 7.396425] bbswitch: Found integrated VGA device 0000:00:02.0: \_SB_.PCI0.GFX0
[ 7.396434] bbswitch: Found discrete VGA device 0000:01:00.0: \_SB_.PCI0.PEG0.PEGP
[ 7.396446] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95)
[ 7.396855] bbswitch: detected an Optimus _DSM function
[ 7.396868] bbswitch: Succesfully loaded. Discrete card 0000:01:00.0 is on

Alberto Milone (albertomilone) wrote :

This is just a completely harmless leftover:

7.355529] init: Failed to spawn hybrid-gfx main process: unable to execute: No such file or directory

there's probably something wrong with bbswitch.

What happens if you type:

echo "OFF" | sudo tee /etc/prime-discrete

and then you log out and log back in? (please attach both dmesg and /var/log/gpu-manager.log after that)

Changed in ubuntu-drivers-common (Ubuntu):
status: In Progress → Fix Released
Alin Andrei (nilarimogard) wrote :

$ echo "OFF" | sudo tee /etc/prime-discrete
OFF

After log out:
$ cat /proc/acpi/bbswitch
0000:01:00.0 ON

Alin Andrei (nilarimogard) wrote :

I was able to switch the Nvidia card off manually, by using these commands which were present in the old prime-switch script (from nvidia-prime pre 0.6):

/sbin/initctl emit nvidia-off
/sbin/rmmod nvidia
echo "OFF" | sudo tee /proc/acpi/bbswitch

$ cat /proc/acpi/bbswitch
0000:01:00.0 OFF

Alberto Milone (albertomilone) wrote :

that's one more bug. I know exactly what's going on. Thanks

Alberto Milone (albertomilone) wrote :

ubuntu-drivers-common (1:0.2.89.6) will solve the problem.

In case of further issues, please file new bug reports against ubuntu-drivers-common.

Thank you again for your help debugging the problem.

Alin Andrei (nilarimogard) wrote :

Thank you! I can't test it right now but I'll give it a try later.

Alin Andrei (nilarimogard) wrote :

I upgraded to version 1:0.2.89.6 and it seems to work. Thanks again!

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers