Well. I don't know where I should sort this report in. But here is the description what happens if I upgrade from 3.9.6 to 3.9.7: It seems that the X-server failed to start. Downgrading the kernel resolved the problem. What I'm seeing: I did further investigate the problem, and curiously no error was printed, if I started an X-server by hand. So I discovered everything works unless the fact I can't switch to the Server. If I try to, the screen freezes and switching back to a tty takes it time. What's happening: The Kernel doesn't recognize with 3.9.7, that on my graphic card (nv50 type (NVIDIA 8800 GTS)) only one connector is used. xRandr aligns both ports. I can work on tty, but can't switch to an x-server Some logs: With Linux 3.9.6: xrandr message: xRandr: Found crtc's: 2 xRandr: Linking output DVI-I-1 with crtc 0 Output of xrandr --current: Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 8192 x 8192 DVI-I-1 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 473mm x 296mm 1680x1050 59.9*+ 1400x1050 74.9 1280x1024 75.0 1440x900 75.0 59.9 1152x864 75.0 1024x768 75.1 70.1 60.0 832x624 74.6 800x600 72.2 75.0 60.3 56.2 640x480 72.8 75.0 66.7 60.0 720x400 70.1 DVI-I-2 disconnected (normal left inverted right x axis y axis) Logs with Linux 3.9.7: xrandr message: xRandr: Found crtc's: 2 xRandr: Linking output DVI-I-1 with crtc 0 xRandr: Linking output DVI-I-2 with crtc 1 Output of xrandr --current: Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192 DVI-I-1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 473mm x 296mm 1680x1050 59.9 + 1400x1050 74.9 1280x1024 75.0 1440x900 75.0 59.9 1152x864 75.0 1024x768 75.1 70.1 60.0* 832x624 74.6 800x600 72.2 75.0 60.3 56.2 640x480 72.8 75.0 66.7 60.0 720x400 70.1 DVI-I-2 connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 60.0* 800x600 60.3 56.2 848x480 60.0 640x480 59.9 Possible source for the problem: From the 3.9.7 changelog https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.9.7 commit aed4802d2a0d2f6c7179a2c03e184860741788c0 Author: Ben Skeggs <bskeggs@redhat.com> Date: Mon Jun 3 16:40:14 2013 +1000 drm/nv50/kms: use dac loadval from vbios, where it's available commit d40ee48acde16894fb3b241d7e896d5fa84e0f10 upstream. Regression from merging the old nv50/nvd9 code together, and may be needed to fully fix fdo#64904. The value is ignored completely by the hardware starting from nva3. Reported-by: Emil Velikov <emil.l.velikov@gmail.com> Signed-off-by: Ben Skeggs <bskeggs@redhat.com> commit b242745947ed7562ad91dad9e9fde1a92e40d666 Author: Ben Skeggs <bskeggs@redhat.com> Date: Mon Jun 3 16:07:06 2013 +1000 drm/nv50/disp: force dac power state during load detect commit ea9197cc323839ef3d5280c0453b2c622caa6bc7 upstream. fdo#64904 Reported-by: Gerhard Bräunlich <wippbox@gmx.net> Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
It seems I have the same kind of problem on my nvidia/nouveau card on 3.9.7, but it happens even with a monitor connected to the second output. The card is: 02:00.0 VGA compatible controller [0300]: NVIDIA Corporation G86 [Quadro NVS 290] [10de:042f] (rev a1) I'll try to revert the commit and see what happens.
(In reply to Yves-Alexis Perez from comment #1) > It seems I have the same kind of problem on my nvidia/nouveau card on 3.9.7, > but it happens even with a monitor connected to the second output. > > The card is: > > 02:00.0 VGA compatible controller [0300]: NVIDIA Corporation G86 [Quadro NVS > 290] [10de:042f] (rev a1) > > I'll try to revert the commit and see what happens. Any news on this problem? Is there another bug report on a more appropriate place?
More information on the topic: Help, nouveau detects with my graphic card a ghost monitor which causes a failing X. https://bugs.freedesktop.org/show_bug.cgi?id=67382
Fixed with 3.12rc1 https://github.com/torvalds/linux/commit/5087f51da805f53cba7366f70d596e7bde2a5486 But I don't know if this will included with 3.10.x (lts)
Fixed with 3.12rc1+, 3.11.3 and 3.10.4