Bug 20558 - Problems with 1920x1200 resolution on dual screen
Summary: Problems with 1920x1200 resolution on dual screen
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: 7.4 (2008.09)
Hardware: x86 (IA32) Linux (All)
: high major
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-09 04:02 UTC by Piotr
Modified: 2018-06-12 19:06 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
xorg.conf. Iv'e tryed many combinations, with, without aiglx and many more.This one I'm using now (794 bytes, text/plain)
2009-03-09 07:56 UTC, Piotr
no flags Details
Xorg log (206.38 KB, text/plain)
2009-03-09 07:58 UTC, Piotr
no flags Details
xrandr output (951 bytes, text/plain)
2009-03-09 08:00 UTC, Piotr
no flags Details

Description Piotr 2009-03-09 04:02:36 UTC
I have Thinkpad T60 with Radeon x1400. It's native screen resolutions 1400x1040, but at work I connect it to external monitor Belinea 2485 S1W with native resolution 1920x1200 via d-sub. When I had Fedora 9 I used krandrtray to set desktop resolution to 1920x1200 - the internal screen was displaying upper left part of the screen, but that was fine for me - I used only external monitor. Unfortunately after upgrade to Fedora 10 when I set resolution of external monitor to 1920x1200 the monitor shows resolution 1600x1200 and the desktop has no left part. I'm forced to use 1600x1200 resolution to see all desktop. The same effect is with radeonhd driver but it always worked this way, even with Fedora 9.
Comment 1 Alex Deucher 2009-03-09 07:07:17 UTC
please attach your xorg config, log, and the output of xrandr.
Comment 2 Piotr 2009-03-09 07:56:54 UTC
Created attachment 23693 [details]
xorg.conf. Iv'e tryed many combinations, with, without aiglx and many more.This one I'm using now
Comment 3 Piotr 2009-03-09 07:58:21 UTC
Created attachment 23694 [details]
Xorg log
Comment 4 Piotr 2009-03-09 08:00:09 UTC
Created attachment 23695 [details]
xrandr output

As You can see there is 1920x1200 mode - but it's not working
Comment 5 Alex Deucher 2009-03-09 08:25:26 UTC
try:

xrandr --output VGA-0 --crtc 1 --mode 1920x1200

You might also try booting with the nomodeset option on the kernel command line.
Comment 6 Piotr 2009-03-09 23:57:25 UTC
(In reply to comment #5)
> try:
> 
> xrandr --output VGA-0 --crtc 1 --mode 1920x1200
> 
> You might also try booting with the nomodeset option on the kernel command
> line.
> 

The command xrandr... didn't help. It thought that the resolution is 1920x1200 but in fact it was 1600x1200 with left part of the screen cut of - the same as with krandrtray.But when I've booted with "nomodeset" option it works fine even with krandrtray. Only when mouse cursor is about 1 cm from right edge of screen some stripes come up on it. But this is not very anoying.
So this is a pretty good workaround. I don't know if i should leave this bug open or not?
Comment 7 Alex Deucher 2009-03-10 07:13:59 UTC
(In reply to comment #6)
> The command xrandr... didn't help. It thought that the resolution is 1920x1200
> but in fact it was 1600x1200 with left part of the screen cut of - the same as
> with krandrtray.But when I've booted with "nomodeset" option it works fine even
> with krandrtray. Only when mouse cursor is about 1 cm from right edge of screen
> some stripes come up on it. But this is not very anoying.
> So this is a pretty good workaround. I don't know if i should leave this bug
> open or not?
> 

yeah, it's a bug in the kms drm code.  We'll get it fixed there too eventually.
Comment 8 Alex Deucher 2010-10-19 17:09:49 UTC
Is this still an issue with a newer KMS kernel?
Comment 9 Adam Jackson 2018-06-12 19:06:47 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.