Linux Driver 352.09 fails to initialize adapter

Graphics / Linux Linux
1

Hi,

I run OpenSuSE Tumbleweed on my Lenovo T530.
I’m currently attempting to test the 352.09 Driver (I like to test out beta drivers)

The Driver builds correctly and installs without issue.

When attempting to start X it appears the kernel module runs into an issue.

[ 69.123410] [drm] Initialized nvidia-drm 0.0.0 20150116 for 0000:01:00.0 on minor 0
[ 69.123415] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 352.09 Tue May 12 14:47:49 PDT 2015
[ 69.125106] nvidia_uvm: Loaded the UVM driver, major device number 245
[ 69.127896] nvidia_uvm: Unregistered the UVM driver
[ 99.290118] ACPI Warning: _SB_.PCI0.PEG_.VID_.DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150410/nsarguments-95)
[ 99.290325] ACPI Warning: _SB.PCI0.PEG_.VID_.DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150410/nsarguments-95)
[ 99.290506] ACPI Warning: _SB.PCI0.PEG_.VID_.DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150410/nsarguments-95)
[ 99.290671] ACPI Warning: _SB.PCI0.PEG_.VID_.DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150410/nsarguments-95)
[ 99.290827] ACPI Warning: _SB.PCI0.PEG_.VID_.DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150410/nsarguments-95)
[ 99.291408] ACPI Warning: _SB.PCI0.PEG_.VID_.DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150410/nsarguments-95)
[ 99.291955] ACPI Warning: _SB.PCI0.PEG_.VID_.DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150410/nsarguments-95)
[ 99.292116] ACPI Warning: _SB.PCI0.PEG_.VID_.DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150410/nsarguments-95)
[ 99.362885] ACPI Warning: _SB.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150410/nsarguments-95)
[ 99.367303] NVRM: RmInitAdapter failed! (0x2c:0x59:1340)
[ 99.367312] NVRM: rm_init_adapter failed for device bearing minor number 0
[ 99.367332] NVRM: nvidia_frontend_open: minor 0, module->open() failed, error -5

This does not happen with the 349.16 driver.

I will attach an nvidia-bug-report.log.gz.

This was generated on my laptop after installing 352.09 attempting to start X and having it fail. Then installing 349.16 and having it work. So the dmesg output covers both drivers… I will also include my Xorg.0.log.old file which has the Xorg start attempt that failed with 352.09 as the one in the nvidia-bug-report.log.gz does not include that information.

nvidia-bug-report.log.gz (99.5 KB)
Xorg.0.log.old.gz (2.03 KB)

2

Hi Guys,

Bit of a bump, but it happens with the freshly released 352.21 as well.

Exact same errors.

Can I get you more info? What have I missed in reporting this?

3

Just tried 355.06. Same issue.

This is starting to get serious as this laptop is my daily driver and if/when the next stable driver comes out I would kind of like to run it.

What’s the point of posting bug reports here if nobody even looks at them let alone responds?

4

I’m seeing the exact same issue with 352.30 and 355.06 with a K2000M.

349.16 lets the laptop boot and start x. That said, with 349.16 i’m having serious graphics performance issues where i can actually see the screen scan in new frames when switching desktops, chrome tabs, and other things that update large portions of the screen at once. I reported the performance issues here but received no replies.

nvidia-bug-report-discrete.log.gz (58.9 KB)
nvidia-bug-report-optimus.log.gz (185 KB)