smarttop MX connected to hdmi->dvi screen reports frequency/resolution out of range
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Genesi EfikaMX Support Project |
Fix Released
|
High
|
Matt Sealey |
Bug Description
I have a smarttop MX with the latest (13/12-2010) Ubuntu 10.10 Maverick Meerkat image installed.
The MX is connected to a fujitsu siemens S20-1W dvi screen that is connected via "noname" hdmi->dvi adapter.
Backlight is turned on, but the screen reports that the resolution/
When connected to a Samsung screen there is no problem (that would indicates that the adapter works).
dmesg output when connected to Fujitsu Siemens screen:
[ 0.920966] =======
[ 0.920978] Display Information (EDID)
[ 0.920986] =======
[ 0.920996] EDID Version 1.3
[ 0.921005] Manufacturer: FUS
[ 0.921013] Model: 600
[ 0.921020] Serial#: 672
[ 0.921028] Year: 2005 Week 47
[ 0.921039] Monitor Name: S20-1W
[ 0.921048] Serial Number: YENH000671
[ 0.921056] Display Characteristics:
[ 0.921064] Monitor Operating Limits: From EDID
[ 0.921080] H: 30-82KHz V: 56-75Hz DCLK: 150MHz
[ 0.921089] Digital Display Input
[ 0.921097] Sync:
[ 0.921106] Max H-size in cm: 43
[ 0.921117] Max V-size in cm: 27
[ 0.921126] Gamma: 2.30
[ 0.921139] DPMS: Active yes, Suspend no, Standby no
[ 0.921148] RGB Color Display
[ 0.921156] Chroma
[ 0.921164] RedX: 0.640 RedY: 0.352
[ 0.921176] GreenX: 0.288 GreenY: 0.628
[ 0.921188] BlueX: 0.144 BlueY: 0.076
[ 0.921201] WhiteX: 0.313 WhiteY: 0.329
[ 0.921212] First DETAILED Timing is preferred
[ 0.921234] Detailed Timings
[ 0.921248] "1680x1050@59" 146 1680 1784 1960 2240 1050 1053 1059 1089 +hsync +vsync
[ 0.921271] Supported VESA Modes
[ 0.921288] 720x400@70Hz
[ 0.921296] 640x480@60Hz
[ 0.921303] 640x480@75Hz
[ 0.921314] 1024x768@75Hz
[ 0.921322] Manufacturer's mask: 0
[ 0.921329] Standard Timings
[ 0.921339] 1680x1050@60Hz
[ 0.921356] 1440x900@60Hz
[ 0.921367] 1440x900@75Hz
[ 0.921378] 1280x800@60Hz
[ 0.921389] 1280x800@75Hz
[ 0.921400] 960x600@60Hz
[ 0.921411] 960x600@75Hz
[ 0.921420] Detail Timings
[ 0.921433] =======
[ 0.921443] SII9022: 12 Supported Modelines:
[ 0.921464] SII9022: "1680x1050@59" 146.262980 1680 1784 1960 2240 1050 1053 1059 1089 +hsync +vsync
[ 0.921487] SII9022: "720x400@70" 26.171159 720 737 808 896 400 401 404 417 -hsync -vsync
[ 0.921508] SII9022: "640x480@60" 25.200342 640 656 752 800 480 490 492 525 -hsync -vsync
[ 0.921529] SII9022: "640x480@75" 31.500031 640 656 720 840 480 481 484 500 -hsync -vsync
[ 0.921551] SII9022: "1024x768@75" 78.802206 1024 1040 1136 1312 768 769 772 800 +hsync +vsync
[ 0.921573] SII9022: "1680x1050@60" 146.864444 1680 1786 1966 2252 1050 1051 1054 1087 -hsync -vsync
[ 0.921595] SII9022: "1440x900@60" 106.780565 1440 1523 1675 1910 900 901 904 932 -hsync -vsync
[ 0.921617] SII9022: "1440x900@75" 136.780194 1440 1534 1689 1939 900 901 904 940 -hsync -vsync
[ 0.921639] SII9022: "1280x800@60" 83.647009 1280 1347 1481 1683 800 801 804 828 -hsync -vsync
[ 0.921661] SII9022: "1280x800@75" 107.296137 1280 1359 1495 1711 800 801 804 835 -hsync -vsync
[ 0.921683] SII9022: "960x600@60" 45.867351 960 997 1095 1230 600 601 604 622 -hsync -vsync
[ 0.921705] SII9022: "960x600@75" 59.98162 960 1008 1108 1256 600 601 604 627 -hsync -vsync
[ 0.921729] SII9022: Setting Resolution: 1280x800
Changed in efikamx: | |
assignee: | nobody → Matt Sealey (mwsealey) |
importance: | Undecided → High |
status: | New → In Progress |
Changed in efikamx: | |
status: | In Progress → Fix Committed |
Changed in efikamx: | |
status: | Fix Committed → Fix Released |
Runi, can you paste the rest of the dmesg output so we can see what the SII9022 thinks of the PLLs?
I can tell you right away though that 1680x1050@59 will not be supported regardless on your monitor (pixel clock needs to be under 133MHz). 1440x900@60 is the best you will see.. the code for picking that mode out is still being written (we are having trouble picking modes which match the monitor dimensions - widescreen monitors should fall back to widescreen modes, but we are getting wide modes on normal monitors and normal modes on wide monitors because of rounding problems and the heuristic is a little rough).
Luckily part of the fixes is cleaning everything up and I think the new HDMI driver will detect DVI monitors better, has a little less quirky clock setting and should enable more monitor features where relevant.