You are not logged in.

#1 2014-02-22 18:34:20

rejak
Member
Registered: 2013-08-16
Posts: 10

nvidia update breaks optimus configuration

the linux kernel update has broken my nvidia optimus configuration. I'm using the proprietary nvidia driver

xorg.conf

Section "ServerLayout"
    Identifier "layout"
    Screen 0 "nvidia"
    Inactive "intel"
EndSection

Section "Device"
    Identifier "nvidia"
    Driver "nvidia"
    BusID "PCI:1:0:0"
EndSection

Section "Screen"
    Identifier "nvidia"
    Device "nvidia"
    # Uncomment this line if your computer has no display devices connected to
    # the NVIDIA GPU.  Leave it commented if you have display devices
    # connected to the NVIDIA GPU that you would like to use.
    Option "UseDisplayDevice" "none"
EndSection

Section "Device"
    Identifier "intel"
    Driver "modesetting"
EndSection

Section "Screen"
    Identifier "intel"
    Device "intel"
EndSection

xorg.0.log

[  1652.633] (II) modesetting(1): using drv /dev/dri/card1
[  1652.633] (II) modesetting(G0): using drv /dev/dri/card1
[  1652.633] (EE) Screen 1 deleted because of no matching config section.
...
[  1652.776] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA GPU at PCI:1:0:0.  Please
[  1652.776] (EE) NVIDIA(GPU-0):     check your system's kernel log for additional error
[  1652.776] (EE) NVIDIA(GPU-0):     messages and refer to Chapter 8: Common Problems in the
[  1652.776] (EE) NVIDIA(GPU-0):     README for additional information.
[  1652.776] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA graphics device!
[  1652.776] (EE) NVIDIA(0): Failing initialization of X screen 0
...
[  1652.780] (EE) Screen(s) found, but none have a usable configuration.
[  1652.780] (EE) 
Fatal server error:
[  1652.780] (EE) no screens found(EE) 
[  1652.780] (EE) 

dmesg

[ 1654.058124] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95)
[ 1654.058178] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95)
[ 1654.058206] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95)
[ 1654.058232] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95)
[ 1654.058257] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95)
[ 1654.058282] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95)
[ 1654.058322] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95)
[ 1654.058349] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95)
[ 1654.089576] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95)
[ 1654.181763] NVRM: RmInitAdapter failed! (0x24:0x28:1130)
[ 1654.181770] NVRM: rm_init_adapter failed for device bearing minor number 0
[ 1654.181788] NVRM: nvidia_frontend_open: minor 0, module->open() failed, error -5
[ 1654.058124] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95)
[ 1654.058178] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95)
[ 1654.058206] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95)
[ 1654.058232] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95)
[ 1654.058257] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95)
[ 1654.058282] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95)
[ 1654.058322] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95)
[ 1654.058349] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95)
[ 1654.089576] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95)
[ 1654.181763] NVRM: RmInitAdapter failed! (0x24:0x28:1130)
[ 1654.181770] NVRM: rm_init_adapter failed for device bearing minor number 0
[ 1654.181788] NVRM: nvidia_frontend_open: minor 0, module->open() failed, error -5

I've looked into my /usr/share/doc/nvidia/README and it's told me to use

    Option "AllowEmptyInitialConfiguration"

instead of

    Option "UseDisplayDevice" "none"

what happened?

Offline

#2 2014-02-23 11:44:46

Rexilion
Member
Registered: 2013-12-23
Posts: 784

Re: nvidia update breaks optimus configuration

I think it should be:

    Option "AllowEmptyInitialConfiguration" "true"


fs/super.c : "Self-destruct in 5 seconds.  Have a nice day...\n",

Offline

#3 2014-03-18 15:20:31

aaronp24
Member
Registered: 2014-03-04
Posts: 4

Re: nvidia update breaks optimus configuration

Rexilion, that doesn't matter.  It's a boolean option so just specifying it without an argument defaults to "true".  However, that's probably unrelated to the topic of this post, which sounds like either a regression in the kernel's ACPI handling, or better error checking in the kernel that's revealing an error in your system's ACPI tables.  rejak, is there any chance you could identify which kernel change broke it?  Also, which version of the driver are you using and does the problem still occur with the latest version?

Offline

#4 2014-05-01 18:24:14

OzanGuven
Member
From: Istanbul, Turkey
Registered: 2009-08-24
Posts: 14
Website

Re: nvidia update breaks optimus configuration

Did you solve this issue?

I keep getting the same errors on linux 3.13.11-2-ck with latest nvidia driver.
I am able to run gnome, but it freezes at some point.

Offline

#5 2014-05-27 19:34:40

gautamadude
Member
Registered: 2012-02-09
Posts: 4

Re: nvidia update breaks optimus configuration

--Edit--
Never mind, my problem had to do with the nvidia drivers not actually being installed!

--Original post--
I'm getting the same problem, is there any fix to this?

X doesn't start and I get the same X log errors and dmesg warnings.

Last edited by gautamadude (2014-05-27 19:50:14)

Offline

#6 2014-05-28 17:27:07

jaz
Member
Registered: 2014-05-28
Posts: 1

Re: nvidia update breaks optimus configuration

My Optimus works great, though it would just work occasionally using the current arch kernel. I'm now running the 3.15 mainline kernel and anything works fine.

Also i guess your X-Server misses a Monitor section in your xorg.conf?

Offline

#7 2014-05-29 18:12:49

GSF1200S
Member
Registered: 2008-12-24
Posts: 467

Re: nvidia update breaks optimus configuration

I had the same issue when setting up Optimus. I could not get optirun or primusrun to launch an application with the nvidia card and had the same errors in xorg.8.log. In my case however, I launched X using the intel card...

Since your log is xorg.0.log, im assuming your case actually breaks X from starting (and that youre trying to start X using the discrete graphics card). So a few ideas...

I cant boot my T530 on the discrete graphics card unless I append:

noapic

to the kernel line in grub.cfg. Note that is noapic and NOT noacpi. However, in my case the kernel panics; I dont even get to login, so this might not really help you.

Also, I managed to fix applications not opening with optirun/primusrun/nvidia by removing:

BusID "PCI:1:0:0"

from the xorg.conf. This despite the fact that my nvidia card is clearly listed as having that exact PCI address, and despite the fact that nearly all guides to get Optimus working say to add that to the xorg.conf. I dont know why it caused problems, but it did.

Offline

Board footer

Powered by FluxBB