Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 488714 - x11-drivers/nvidia-drivers - black screen on startup
Summary: x11-drivers/nvidia-drivers - black screen on startup
Status: RESOLVED OBSOLETE
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Jeroen Roovers (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-20 11:54 UTC by igel
Modified: 2020-10-29 22:39 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info nvidia-drivers when having 313.30 (working) installed (nvidia-drivers-313.30-info,17.56 KB, text/plain)
2013-10-20 11:55 UTC, igel
Details
xorg log (black screen) with 331.13 (Xorg.0.log,17.22 KB, text/plain)
2013-10-24 07:28 UTC, igel
Details
dmesg with 331.13 (black screen) (dmesg,85.49 KB, text/plain)
2013-10-24 07:28 UTC, igel
Details
emerge --info nvidia-drivers with 331.13 (black screen) (emerge--info,16.99 KB, text/plain)
2013-10-24 07:29 UTC, igel
Details
lspci of the nvidia card (lspci,2.80 KB, text/plain)
2013-10-24 17:22 UTC, igel
Details
emerge --info nvidia-drivers (damp,5.92 KB, text/plain)
2014-09-05 09:56 UTC, ivan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description igel 2013-10-20 11:54:03 UTC
Until recently, I ran =x11-drivers/nvidia-drivers-319.32 with newest Xorg. However, 319.32 got removed from the portage tree in favor of 319.49 (marked stable), so I updated to 319.49. With 319.49 however, I consistently get a black screen without error message in /var/log/Xorg.0.log or syslog. However, if I switch to <x11-drivers/nvidia-driver-319.49 (which in fact is 313.30 for me now) then everything works.

Reproducible: Always

Steps to Reproduce:
1. emerge '>x11-drivers/nvidia-drivers-319.32'
2. modprobe -r nvidia; modprobe nvidia  (or reboot, doesn't matter)
3. startx
Actual Results:  
screen goes black (I can, however, switch to text-console and back, but it's still black)

Expected Results:  
X should come up showing at least a mouse pointer

1. I can literally switch back and forth to non-working X by installing 319.49 (or any other >319.32) [broken] and 313.30 [working]

2. I'm running sys-kernel/aufs-sources-3.8.10

3. This is my video card:
01:00.0 VGA compatible controller: NVIDIA Corporation G96M [GeForce 9650M GT] (rev a1)
Comment 1 igel 2013-10-20 11:55:15 UTC
Created attachment 361426 [details]
emerge --info nvidia-drivers   when having 313.30 (working) installed
Comment 2 igel 2013-10-21 09:37:02 UTC
uh oh, this seems to get stranger by the hour...

Here's the story: yesterday, before reporting this, the situation was as I described above. Today morning, I fired up the system and it black-screened again on me (even with 313.30). I tried all morning to get any version of nvidia-drivers to run, but without success. I even downgraded the xorg-server to 1.11, no gain! Black screen, no error message to be found. Here's a hint tho: If I clear my $XSESSION and "startx" from console into black screen, then the last thing X outputs on the console is "loading XINERAMA".

Anyways, since I need this system running, I switched to nouveau which (seemingly - after this episode with nvidia-drivers I got a little suspicious) works fine.
Comment 3 igel 2013-10-24 07:28:07 UTC
Created attachment 361760 [details]
xorg log (black screen) with 331.13
Comment 4 igel 2013-10-24 07:28:44 UTC
Created attachment 361762 [details]
dmesg with 331.13 (black screen)
Comment 5 igel 2013-10-24 07:29:15 UTC
Created attachment 361764 [details]
emerge --info nvidia-drivers with 331.13 (black screen)
Comment 6 igel 2013-10-24 07:30:33 UTC
Comment on attachment 361760 [details]
xorg log (black screen) with 331.13

unfortunately, the evdev xorg-driver is not up to date with the xorg-server in this log, so it contains some (EE)'s regarding that, sorry...
Comment 7 igel 2013-10-24 07:33:34 UTC
these last few logs have been made with aufs-sources-3.10.9 (black screens persist)
Comment 8 Jeroen Roovers (RETIRED) gentoo-dev 2013-10-24 15:49:24 UTC
How many graphics devices does your system have?
Comment 9 igel 2013-10-24 16:47:24 UTC
(In reply to Jeroen Roovers from comment #8)
> How many graphics devices does your system have?

just this one it's an old ASUS N50Vn
Comment 10 Jeroen Roovers (RETIRED) gentoo-dev 2013-10-24 16:59:31 UTC
(In reply to igel from comment #9)
> (In reply to Jeroen Roovers from comment #8)
> > How many graphics devices does your system have?
> 
> just this one it's an old ASUS N50Vn

I have no idea what that is.

According to [1], that *might* be an "NVIDIA® GeForce® 9650M GT, with 1GB VRAM". Your lspci output would really help, here.


[1] http://www.asus.com/Notebooks_Ultrabooks/N50Vn/#specifications
Comment 11 igel 2013-10-24 17:19:04 UTC
(In reply to Jeroen Roovers from comment #10)
> (In reply to igel from comment #9)
> > (In reply to Jeroen Roovers from comment #8)
> > > How many graphics devices does your system have?
> > 
> > just this one it's an old ASUS N50Vn
> 
> I have no idea what that is.
> 
> According to [1], that *might* be an "NVIDIA® GeForce® 9650M GT, with 1GB
> VRAM". Your lspci output would really help, here.
> 
> 
> [1] http://www.asus.com/Notebooks_Ultrabooks/N50Vn/#specifications

of course:

01:00.0 VGA compatible controller: NVIDIA Corporation G96M [GeForce 9650M GT] (rev a1) (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Device 1912
  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
  Latency: 0, Cache Line Size: 32 bytes
  Interrupt: pin A routed to IRQ 16
  Region 0: Memory at fc000000 (32-bit, non-prefetchable) [size=16M]
  Region 1: Memory at d0000000 (64-bit, prefetchable) [size=256M]
  Region 3: Memory at fa000000 (64-bit, non-prefetchable) [size=32M]
  Region 5: I/O ports at cc00 [size=128]
  [virtual] Expansion ROM at fd000000 [disabled] [size=512K]
  Capabilities: <access denied>
  Kernel driver in use: nouveau
  Kernel modules: nouveau, nvidia
Comment 12 igel 2013-10-24 17:22:11 UTC
Created attachment 361806 [details]
lspci of the nvidia card

sorry for the earlier lspci without sufficient permissions
Comment 13 igel 2013-11-04 18:00:26 UTC
okay, so I somehow got 319.49 to at least fire up an X with twm now (using aufs-sources-3.10.17). To this end, I made a new xorg.conf using nvidia-xconfig disabling just about everything related to glx and xinerama:

nvidia-xconfig --no-composite --no-dynamic-twinview --no-xinerama --only-one-x-screen --no-render-accel --no-nvidia-xinerama-info-order --no-add-argb-glx-visuals --no-allow-glx-with-composite

Funny though that I actually do get both my laptop display and a connected monitor in what I understand is xinerama mode anyways...

I'll try slowly add options back into my X and running an eye-candy window manager and report back... If I'm feeling brave, maybe I'll try the newer nvidia-drivers once more...
Comment 14 igel 2013-11-04 18:47:02 UTC
Indeed, it all appears to be up and running smoothly (with 319.49, I don't dare to change this running system until I'm forced to) - for now (careful not to jinx). I'll report back on first sign of failure...

Sorry for taking up your time so far, I've got no clue what happened and why, I'll quickpkg xorg and nvidia-drivers now I think.
Comment 15 Billy DeVincentis 2013-11-15 11:18:03 UTC
I am having similar problems with any driver higher than 325.15, I have a desaktop and if I switch from the desktop on tty7 to tty1 or tty2 and switch back, I get a garbled screen, works fine with 325.15.
Oh forgot to mention, any driver past 325 causes emerge issues where emerge will freeze on checking for working sleep among other things
Comment 16 b14wc@hotmail.com 2014-01-10 02:59:19 UTC
Stop the X server and then delete ~/.nvidia config.  Restart the X server and then log into your desktop.  If that works for you then you have the same issue as me whenever I open nvidia-settings on the next reboot I get a black screen instead of kde desktop.  I saw an error message when I tried to run startx as a normal user will post it later.
Comment 17 ivan 2014-09-05 09:56:31 UTC
Created attachment 384224 [details]
emerge --info nvidia-drivers
Comment 18 ivan 2014-09-05 09:57:06 UTC
Reprodused on Nvidia GF GT440.
Comment 19 Jeroen Roovers (RETIRED) gentoo-dev 2014-09-05 10:07:34 UTC
Comment on attachment 361760 [details]
xorg log (black screen) with 331.13

(II) Loading /usr/lib64/xorg/modules/input/evdev_drv.so
(II) Module evdev: vendor="X.Org Foundation"
	compiled for 1.11.4, module version = 2.7.3
 	Module class: X.Org XInput Driver
 	ABI class: X.Org XInput driver, version 13.0
(EE) module ABI major version (13) doesn't match the server's version (19)

This happens repeatedly for the evdev and synaptics modules.
Comment 20 Jeroen Roovers (RETIRED) gentoo-dev 2014-09-05 10:09:26 UTC
Comment on attachment 361762 [details]
dmesg with 331.13 (black screen)

This shows nothing out of the ordinary. The nvidia kernel module was apparently doing fine at the time.
Comment 21 Jeroen Roovers (RETIRED) gentoo-dev 2014-09-05 10:14:04 UTC
(In reply to b14wc@hotmail.com from comment #16)
> Stop the X server and then delete ~/.nvidia config.  Restart the X server
> and then log into your desktop.  If that works for you then you have the
> same issue as me whenever I open nvidia-settings on the next reboot I get a
> black screen instead of kde desktop.

Well, that's interesting. Which nvidia-settings was automatically run - the one in /opt/bin (x11-drivers/nvidia-drivers[tools] or the (very likely incompatible) one in /usr/bin (installed from source by media-video/nvidia-settings)?

> I saw an error message when I tried to run startx as a normal user will post it later.

You never did.