Bug 33059 - [evergreen] xorg cannot detect supported resolutions for external monitor
Summary: [evergreen] xorg cannot detect supported resolutions for external monitor
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-13 06:41 UTC by Nikolay Amiantov
Modified: 2018-06-12 19:07 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Xorg.log when started with connected monitor (49.87 KB, text/plain)
2011-01-13 06:41 UTC, Nikolay Amiantov
no flags Details
dmesg (git kernel) (30.15 KB, text/plain)
2011-01-13 10:26 UTC, Nikolay Amiantov
no flags Details

Description Nikolay Amiantov 2011-01-13 06:41:32 UTC
Created attachment 41962 [details]
Xorg.log when started with connected monitor

Xorg (do not know which component of it is responsible of that) cannot autodetect supported resolutions for external VGA monitor on laptop. (Acer Aspire 4820TG-5454G50Miks/ATI Mobility Radeon HD 5650) Since resolutions are correctly detected when switching on Intel videocard, problem might be in driver. Despite of that, I can still manually add needed resolution to Xrandr and it will work.
Monitor model: Samsung SyncMaster 226BW

Steps to Reproduce:
1. Attach monitor to VGA input before or while running XOrg.
2. run "xrandr" in the Xorg console.

Actual results:
There are default resolutions avaliable for external monitor.

Expected results:
There are native resolutions for my monitor.

Build date & platform:
Linux abbradarbook 2.6.37-gentoo #4 SMP PREEMPT Fri Jan 7 15:20:35 MSK 2011 x86_64 Intel(R) Core(TM) i5 CPU M 450 @ 2.40GHz GenuineIntel GNU/Linux
xorg-server: 1.9.3.901
xf86-video-ati: commit c5b3db18d888552328e9718ea022794fc5bde352

Additional information:
Before 2.6.37 kernel release, VGA output have not worked at all, showing slightly corrupted cloned from first screen image on monitor. Though, there was the same choice of possible resolutions.
Resolutions:
   1024x768       60.0* 
   800x600        60.3     56.2  
   848x480        60.0  
   640x480        59.9     59.9  
   512x384       120.0  
   400x300       120.6    112.7  
   320x240       120.1
Comment 1 Alex Deucher 2011-01-13 08:40:59 UTC
Please attach your dmesg output.  Also, make sure your kernel has this patch:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=ea39302b87b8d944d567ef29c0647c09da5743fa
Comment 2 Nikolay Amiantov 2011-01-13 10:26:10 UTC
Created attachment 41980 [details]
dmesg (git kernel)

Bug is reproducable on the head kernel git commit at this moment:
commit	f878133bf022717b880d0e0995b8f91436fd605c
that has this patch applied.

dmesg (ran on git kernel, monitor had been connected before power-on) is attached.
Also there is no cloning of the Linux console to the second monitor after Xorg starts once - should I file a bug about this?
Comment 3 Alex Deucher 2011-02-13 14:24:24 UTC
Is this a system with switchable graphics?  If so, does it work properly if you force the radeon to be the default video in the bios?  It's possible the oem did not mux the vga connector between the two cards or that the mux is not getting switched properly when you switch between the cards.
Comment 4 Nikolay Amiantov 2011-02-14 00:11:53 UTC
(In reply to comment #3)
> Is this a system with switchable graphics?  If so, does it work properly if you
> force the radeon to be the default video in the bios?  It's possible the oem
> did not mux the vga connector between the two cards or that the mux is not
> getting switched properly when you switch between the cards.

Yes, it's a swithable graphics system, and it really does work properly with disabling the whole switching in BIOS (and setting Radeon to be the only card). Also, as I said earlier, if I'm in switchable mode and using Intel card, monitor is being detected properly.
Comment 5 Adam Jackson 2018-06-12 19:07:15 UTC
Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.


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.