Hi all, I have an external Dell E198WFP with a maximum resulution of 1440x900. When Plugging the thing in before the X Server starts, it all works out nicely, but attaching the screen at a running session makes X recognize ====================== *snip* ====================== TMDS-1 connected 1280x960+0+0 (normal left inverted right x axis y axis) 408mm x 255mm ====================== *snap* ====================== My xorg.conf contains ====================== *snip* ====================== Section "Monitor" Identifier "Dell E198WFP" VendorName "Dell" ModelName "E198WFP" DisplaySize 408 255 Option "DPMS" Option "OffTime" "20" Option "PreferredMode" "1440x900" EndSection ====================== *snap* ====================== Full xorg.log is appended. Is there anything else I could do for debugging? Cheers, Nico
please attach your full xorg.conf and xorg.log with ModeDebug option turns on ..
Created attachment 23734 [details] X configuration
Created attachment 23735 [details] Xorg log with incorrect screen size
Pipe A is always set by tv mode, Pls use this method to ignore it for now, then update log file with modedebug option on. Section "Device" ... Option "monitor-TV" "TV" ... EndSection ... Section "Monitor" Identifier "TV" Option "Ignore" "True" EndSection Thanks Ma Ling
Created attachment 23932 [details] Xorg log with incorrect screen size and TV out disabled Allright, updated with manual disabling of the TV out -- which is particularly weird b/c this laptop here in front of me doesn't have a TV out at all! The only two physical connections are to the internal LVDS screen and one of those nasty Macbook mini-DVI connectors. Anyway, the whole TV debug output is gone of course, but the problem still persists. It might actually have to do with that "Not using mode "1440x900" (width too large for virtual size)" line, but I don't know what to make of it. Cheers, Nico
Created attachment 23954 [details] please try the debug patch on your machine, thanks hi Nico let me describe your action(If I were wrong, please correct me): after starting Xserver, then plug DVI monitor, then run "xrandr --output TMDS-1 auto" ? If yes, it is very strange, xserver seem not to call mode set function in driver, the debug patch will narrowdown the problem please try it then upload your log file with modedebug option on. Thanks Ma Ling
Created attachment 23975 [details] Xorg log with incorrect screen size and TV out disabled, patch applied Hi Ma, thanks for your efforts! You see things entirely correct: Start Xserver, plugin a (Mini)DVI, and `xrandr -q` show incorrect mode of the external screen. It *does* work when first plugging the screen in, then starting Xserver. I applied the patch and post the Xorg log here, but I'm afraid to say there not much difference from what I posted before. The function where the patch sits in doesn't seem to be called at all. Cheers, Nico
Created attachment 23976 [details] Xorg log with *correct* screen size, patch applied For reference, I just post the Xorg log that I find when first plugging in, then starting the server. You can actually see some output from the patch here..
Created attachment 24028 [details] please try it on your machine, thanks hi Nico I guss the problem is from max Virtual X configuration, which is set by xorg, not driver. please use the patch on xorg-xserver-1.6.0, and run under "with *correct* screen size" and "incorrect screen size" environment respectively, then upload the two log files with modedebug option on. Thanks Ma Ling
Created attachment 24056 [details] Xorg log with patched xserver, *correct* output there we go.
Created attachment 24057 [details] Xorg log with *correct* screen size, patch applied
Created attachment 24058 [details] Xorg log with *incorrect* screen size, patch applied ... aaand the other one. Cheers! Nico
hi Nico, when X start, the framebuffer is fixed by max virtual size from lvds. so when you connect vga and run xrandr, the max virtual size from lvds determins your mode choice. There is new method which can resize virtual size and resolve the problem, please set xorg.conf as below: Section "Device" ... driver "intel" ... Option "AccelMethod" "UXA" EndSection Thanks Ma Ling
That fixed it indeed! :D Now, I read that UXA will be discontinued sometime, see http://www.phoronix.com/scan.php?page=news_item&px=NjcwNA Does that mean that I'm gonna have to look for another solution in the near future, or have plans changed in any way? Cheers, Nico
(In reply to comment #14) > That fixed it indeed! :D > Now, I read that UXA will be discontinued sometime, see > http://www.phoronix.com/scan.php?page=news_item&px=NjcwNA > Does that mean that I'm gonna have to look for another solution in the near > future, or have plans changed in any way? > Cheers, > Nico hi Nico This is old news, latest plan is to get rid of EXA, but stick to UXA only. Thanks Ma Ling
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.