This bugzilla is a continuation of a discussion on the mailing list: http://lists.freedesktop.org/archives/xorg/2008-January/031851.html Issue ==== So it appears that DVI has some strange issues with my Samsung 243T and probably other older monitors. Connected on X Startup ----------------------------------- Over DVI the monitor will start with resolution 1280x1024. When I try to send any xrandr commands they are ignored. Using "xrandr --output TDMS-1 --right-of LVDS --auto". The monitor does nothing. I can't get it to change the resolution either. Hot plugged ----------------- When I hot plug over DVI xrandr shows the correct values for my monitor. But when I use the command "xrandr --output TDMS-1 --right-of LVDS --auto" .. nothing comes to the screen! I've seen others report this on the mailing list, but they where using hdmi port.
Created attachment 13744 [details] xorg.conf
Created attachment 13745 [details] Xorg log when connected on startup
Created attachment 13746 [details] Xorg log when monitor is hotplugged
Created attachment 13747 [details] Xorg log when connected on startup from my HACKED code
I am using a Lenovo Thinkpad T61 with an x3100 graphics card. This is connected to a docking station (which has the DVI port). I have attached logs. The HACKED log is where I go into i830_driver.c and move sdvo_init() before lvds_init().
(In reply to comment #5) > I am using a Lenovo Thinkpad T61 with an x3100 graphics card. This is connected > to a docking station (which has the DVI port). > > I have attached logs. The HACKED log is where I go into i830_driver.c and move > sdvo_init() before lvds_init(). > From the log, our driver detects the EDID data correctly when connecting your monitor at startup. It's weird that you can't change resolution with xrandr. What's your version of X server? and have you tried other xrandr commands, (directly change resolution like #xrandr --output TMDS-1 --mode 1920x1200...)? Can you try add following to your xorg.conf to see if everything works? Section "Device" ... Option "monitor-TMDS-1" "TMDS-1" ... EndSection Section "Monitor" Identifier "TMDS-1" Option "PreferredMode" "1920x1200" EndSection From the hotplug log, (II) intel(0): SDVO: W: 0B (SDVO_CMD_GET_ATTACHED_DISPLAYS) (II) intel(0): SDVO: R: 00 00 (Success) ^^^^^ It seems we can't correctly detect the connect status of this monitor, but you say you can get correct data on xrandr? I don't see it in your log. Would you please try to execute #xrandr and #xrandr --output TMDS-1 --mode XXXX (try different modes) several times, and attach the log? Then I can see whether the failure of detection is a random issue. Thanks, Hong
I've been testing with Ubnuntu Hardy builds (wtih the intel driver from git). The xserver that comes with it : xorg server 1.73 xorg core 2.1.4.1 (git 01 18 2008) There have been some updates and I built the latest intel git. xorg.conf has not changed. When monoitor is connected on boot. ========================================================== The monitor still starts at 1280x1024 but has new behavior. So seting the mode explicity does work using: xrandr --output TMDS-1 --mode 1920x1200 Also what seems to work now is xrandr --output TMDS-1 --right-of LVDS --auto which will expand the monitor and also set it to 1920x1200. What is odd though is that the monitor is not starting out at 1920x1200 but 1280x1024. See next line. *So that appears to be now is that when connected on boot and auto detecting it is using 1280x1024 and not the full 1920x1200. This could be a correct feature as the Samsung 243T cannot do 1400x900 and 1280x1024 is the closest to it for cloning. BUT it does cause Gnome in on the 1400x900 screen to only use 1280x1024 (the LVDS is displaying 1400x900 .. but Gnome is only using 1280x1024 square of this). Or should it not be displaying 1920x1200 and Gnome on using a small square of that (That would be 1400x900)? I attached a picture to show what is going on (picture1). Now adding to xorg: Section "Monitor" Identifier "TMDS-1" Option "PreferredMode" "1920x1200" EndSection It now starts up at 1920x1200 (and the LVDS only able to show 1400x900) of Gnome. But it does work. (picture2) * Conclusion somehow over time it now works on startup! Don't know if the point above is a cause for concern. * log is Xorg.0.log_connected_on_startup_WORKS_NOW. HOT PLUG ======================================= xrandr --output TMDS-1 --mode 1920x1200 now works too! But when I use command: xrandr --output TMDS-1 --same-as LVDS --auto The monitor changes to 1920x1200 (horray)! What it does not do is clone the LVDS, it instead takes over and instead of having 1920x1200 with a square of 1400x900 showing Gnome. It instead uses the full 1920x1200 and on my LVDS the Gnome bar is cut (it can only show 1400x900).. while on the TDMS the gnome bar is full (because it has now assumed the 1920x1200). Same goes for the bottom Gnome bar .. no longer visible in on LVDS, because it is at the bottom of 1920x1200, which it cannot view. But this is another issue. Another issue. Things are now working! * Not sure maybe it was the xorg core update that was added but now things are working today! But it appears that the monitor detection now works. I am a little bothered by the clone issue. As a laptop user I want my LVDS to stay put and TMDS to clone it. Not the other way around. This is another issue though.
Created attachment 13819 [details] Xorg log when connected on startup NOW WORKS
Created attachment 13820 [details] Xorg log when monitor is hotplugged NOW WORKS
Created attachment 13821 [details] Picture1
Created attachment 13822 [details] Picture1
Created attachment 13823 [details] Picture2
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.