Bug 94577 - Black screen with Nvidia Optimus (proprietary driver) since 1.18.1
Summary: Black screen with Nvidia Optimus (proprietary driver) since 1.18.1
Status: NEW
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nVidia (proprietary) (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: high critical
Assignee: Aaron Plattner
QA Contact: Aaron Plattner
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-16 19:24 UTC by vylaern
Modified: 2018-04-09 12:59 UTC (History)
5 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description vylaern 2016-03-16 19:24:05 UTC
Since February and xorg-server 1.18.1 cannot start X with Nvidia Optimus (proprietary driver), as I have a black screen.

I use Gentoo with xorg-server 1.18.2, kernel 4.5.0, intel driver 2.99.917_p20160313, nvidia driver 361.28-r2. All configuration (.xinitrc and xorg.conf) are like recomended by nvidia. In last 2 years I had no such problems wit Optimus.

To have working X, I use startx form text console and Xorg.0.log shows only 1 error:
http://pastebin.com/rSLBSkFf

(EE) modeset(G0): failed to set mode: No space left on device

^^ In Google looks like this error was only in Gentoo. No idea what's wrong.

I thought it was related to this bug:
https://bugs.freedesktop.org/show_bug.cgi?id=92313
But 1.18.2 did not solve this problem
Comment 1 vylaern 2016-03-27 06:49:12 UTC
After last days drivers update (both intel & nvidia) I have such error on the screen after typing 'startx' from the console: 

xrandr: Configure crtc 2 failed 
X Error of failed request: BadValue (integer parameter out of range for operation) 
Major Opcode of failed request: 139 (RANDR) 
Minor Opcode of failed request: 21 (RRSetCrtcConfig) 
Value in failed request: 0x0 
Serial number of failed request: 45 
Current serial number in output stream: 45 
xinit: connection to X server lost
Comment 2 vylaern 2016-04-14 08:23:32 UTC
Hi,

As there is no answer, I would like to ask if there is any linux website with professional support, where I could pay for the help?

Do you think this error is related to modesetting in kernel?
(EE) modeset(G0): failed to set mode: No space left on device
Comment 3 Samuel Renaud 2016-05-21 12:47:07 UTC
Hi and sorry, I've struggled with the same issue for one week, and I forgot to post something.

I had xorg >= 1.18 working on a previous installation of gentoo on a Clevo P170EM with an Intel HD 4000 and Nvidia GTX 680M.
It was working great with xf86-video-intel from February, but it is no more available it seems.

So on my new install, I've been forced to downgrade to xorg 1.17.x and everything works with xf86-video-intel 2.99.917-r2 and the nvidia driver 364.19.

Otherwise, I got the same error of yours on every (newer) other intel driver version.
Comment 4 smellyfis 2016-07-15 18:55:56 UTC
I am having the same issue
nvidia card
01:00.0 VGA compatible controller: NVIDIA Corporation GM204GLM [Quadro M4000M] (rev a1)

intel card
00:02.0 VGA compatible controller: Intel Corporation HD Graphics P530 (rev 06)

I have tried both modesetting and just the intel module for the integrated GPU and the both have the same results
when i run
$ xrandr --setprovideroutputsource modesetting NVIDIA-0
$ xrandr --auto
xrandr: Configure crtc 4 failed
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  139 (RANDR)
  Minor opcode of failed request:  21 (RRSetCrtcConfig)
  Value in failed request:  0x0
  Serial number of failed request:  62
  Current serial number in output stream:  62

and xrandr --auto creates the following line in Xorg log
[  1738.258] (EE) modeset(G0): failed to set mode: No space left on device

If there is anything I can post to help find the bug faster I can
Comment 5 Jack Coulter 2016-08-31 08:44:25 UTC
I encountered this exact issue (xrandr reporting BadValue and Xorg.0.log showing "failed to set mode: No space left on device) with xorg-server 1.18.4 and nvidia-drivers 370.23, also on Gentoo, with the same Nvidia PRIME setup.


After much experimentation, enabling the "glamor" USE flag on x11-base/xorg-server fixes this. I've not the faintest idea as to _why_ this fixes it. It's especially odd, as enabling Glamor should actually break things, according to Nvidia's own documentation:

>   o Some versions of the "modesetting" driver try to load a sub-module called
>     "glamor", which conflicts with the NVIDIA GLX implementation. Please
>     ensure that the 'libglamoregl.so' X module is not installed.
Comment 6 smellyfis 2016-09-01 00:57:45 UTC
I can confirm that  on xorg 1.18.4 with glamor enabled nvidia-drivers 370.23 indeed does work  as expected with optimus
Comment 7 vylaern 2016-10-04 05:45:00 UTC
I could confirm, compiling xorg-server (18.4) with glamor enabled, solved the issue with unfamous black screen. However, it is strange as this is against Nvidia advise which says:
...Some versions of the “modesetting” driver try to load a sub-module called “glamor”, which conflicts with the NVIDIA GLX implementation. Please ensure that the libglamoregl.so X module is not installed...

Tested with Nvidia 370.28 driver.

Works fine for time testing, but switching [Rendering Backend] in KDE Plasma 5 settings form [OpenGL 3.1] into [XRandr], makes desktop bit unstable wit artefacts. No such issue with xorg-server 17.4
Comment 8 Sgt. Garcia 2016-10-20 13:27:04 UTC
same here
Comment 9 Marco Leise 2018-04-09 12:59:35 UTC
I just disabled glamor on Gentoo and get the same results on xorg-server 1.19.5.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.