Bug 21716 - Detected (native) modes not available for external monitor
Summary: Detected (native) modes not available for external monitor
Status: RESOLVED WORKSFORME
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/radeonhd (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Luc Verhaegen
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-13 07:01 UTC by Matthew Turnbull
Modified: 2011-10-16 16:34 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Xorg.0.log (81.79 KB, text/plain)
2009-05-13 07:01 UTC, Matthew Turnbull
no flags Details
xrandr verbose output (14.65 KB, text/plain)
2009-05-13 07:02 UTC, Matthew Turnbull
no flags Details
xorg.conf (1.89 KB, text/plain)
2009-05-13 09:45 UTC, Matthew Turnbull
no flags Details

Description Matthew Turnbull 2009-05-13 07:01:49 UTC
Created attachment 25817 [details]
Xorg.0.log

When connecting to an external monitor (IBM L200p) I use at work, radeonhd appears to correctly detect the available modes, however, they are not available via xrandr. However, I can manually create and add the mode via xrandr and they work just fine.

This is a bit odd, as last summer I'm pretty sure I was also using the same model monitor. So I guess this particular one is a bit quirky or something got changed in the driver.

I was able to get the xf86-video-ati driver to make the detected modes available, but IIRC I had to have the monitor attached when I started the xserver.
Comment 1 Matthew Turnbull 2009-05-13 07:02:29 UTC
Created attachment 25818 [details]
xrandr verbose output
Comment 2 Matthias Hopf 2009-05-13 07:54:03 UTC
Is the xrandr output from after adding the modelines manually? Otherwise your description wouldn't make sense. Can you add the output before adding the modelines? Also attach your xorg.conf.
Comment 3 Matthew Turnbull 2009-05-13 09:45:06 UTC
Created attachment 25829 [details]
xorg.conf

The xrandr output is right after I restarted X with the monitor attached. I hadn't added any additional modes yet.

And just to be clear, these were the modelines that were detected, according to the log:

Modeline "1600x1200"x0.0  130.89  1600 1620 1700 1780  1200 1201 1204 1225 +hsync +vsync (73.5 kHz)
Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz)
Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz)
Modeline "640x480"x0.0   25.20  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz)
Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz)
Modeline "1024x768"x0.0   78.80  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.1 kHz)
Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz)
Modeline "832x624"x0.0   57.28  832 864 928 1152  624 625 628 667 -hsync -vsync (49.7 kHz)
Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz)
Modeline "1152x864"x0.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz)
Modeline "640x480"x60.0   23.86  640 656 720 800  480 481 484 497 -hsync +vsync (29.8 kHz)
Modeline "640x480"x85.0   35.71  640 672 736 832  480 481 484 505 -hsync +vsync (42.9 kHz)
Modeline "800x600"x85.0   56.55  800 840 928 1056  600 601 604 630 -hsync +vsync (53.5 kHz)
Modeline "1024x768"x85.0   94.39  1024 1088 1200 1376  768 769 772 807 -hsync +vsync (68.6 kHz)
Modeline "1280x1024"x60.0  108.88  1280 1360 1496 1712  1024 1025 1028 1060 -hsync +vsync (63.6 kHz)
Modeline "1280x1024"x70.0  128.94  1280 1368 1504 1728  1024 1025 1028 1066 -hsync +vsync (74.6 kHz)

But this is what xrandr had:

1400x1050      60.0  
1280x1024      75.0     69.8     59.9     60.0  
1280x960       60.0  
1152x864       75.0  
1024x768       84.9     85.0     75.1     75.0     70.1     60.0  
832x624        74.6  
800x600        84.7     85.1     72.2     75.0     60.3     56.2  
640x480        85.0     84.4     75.0     72.8     75.0     60.0     59.9  
720x400        85.0     70.1  
640x400        85.1  
640x350        85.1  

Aside from the fact that xrandr has modes that the monitor doesn't even support (1400x1050, 640x400, 640x350), it's missing the native resolution (1600x1200).
Comment 4 Jeremy Huddleston Sequoia 2011-10-16 15:58:05 UTC
Does this issue occur with the preferred ati driver (xf86-vide-ati)?  If so, please move this to the Driver/Radeon component.  

Development of radeonhd has pretty much halted and development focus is on the ati driver.  Please see http://www.x.org/wiki/radeonhd

If the issue does not exist in the ati driver (or if there is no response to this message), this bug will be closed as WONTFIX unless someone contributes a patch.
Comment 5 Matthew Turnbull 2011-10-16 16:34:34 UTC
I haven't noticed any issues with xf86-vide-ati + KMS. And anyways, I no longer have access to the problematic monitor.


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.