Bug 447239
|
Description
c.h.
2008-05-19 01:21:20 UTC
Created attachment 305886 [details]
nv driver selected PRO-458 15" LCD connected Xorg.1.log
Created attachment 305887 [details]
Xorg.0.log "vesa" driver with DELL 2405FPW screen (works)
Created attachment 305888 [details]
Xorg.0.log for Functional setup NV driver, DELL2405FPW on VGA1 / PRO-458 on VGA2 / 1024x768 on both.
Xorg.0.log for Functional setup NV driver, DELL2405FPW on VGA1 / PRO-458 on
VGA2 / 1024x768 on both.
Created attachment 305889 [details]
xorg.conf for Functional setup NV driver, DELL2405FPW on VGA1 / PRO-458 on VGA2 / 1024x768 on both.
xorg.conf for Functional setup NV driver, DELL2405FPW on VGA1 / PRO-458 on VGA2
/ 1024x768 on both.
Created attachment 305890 [details]
Xorg.0.log for Functional setup NV driver, DELL2405FPW on VGA1 1920x1200
Xorg.0.log for Functional setup NV driver, DELL2405FPW on VGA1 1920x1200
I unplugged the PRO-458 monitor from VGA2 and the DELL 2405FPW 24" screen
started working at 1920x1200 now.
There is a DVI->VGA connector on the VGA2 port, but no monitor connected.
That's the only hardware difference between the present time and the times when
the VGA1 DELL was giving a black screen starting X with the nv driver but the
vesa driver worked with it correctly.
Perhaps some software state changed between the non-functional and functional
periods, but if so it was nothing that I directly know of.
Here's the current (working) xorg.conf too:
# Xorg configuration created by system-config-display
Section "ServerLayout"
Identifier "single head configuration"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "InputDevice"
# keyboard added by rhpxl
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection
Section "Device"
Identifier "Videocard0"
Driver "nv"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Videocard0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
It looks like the server's allowing a reduced-blanking mode through that it shouldn't. Apparently the RANDR 1.2 mode validation code doesn't check for that case at all. Le sigh. Fixed in Fedora 10. |