Your message dated Thu, 21 Jun 2007 22:35:14 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#373219: xserver-xorg: Runs at inappropriate resolution,
despite successful video and monitor detection
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: xserver-xorg
Version: 1:7.0.20
Severity: normal
I generated this bug report a few days ago using reportbug, but it failed to
send automatically. So, I'm forwarding it now by hand, and I've attached
copies of my xorg.conf file and the results of "debconf-show xserver-xorg".
(The report is from the same day as the email. I've now updated to version
7.0.22, but the problem persists.)
-------------------------------------------------------------------
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Kristina Santilli <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: xserver-xorg: Runs at inappropriate resolution,
despite successful video and monitor detection
Message-ID: <[EMAIL PROTECTED]>
X-Mailer: reportbug 3.20
Date: Mon, 05 Jun 2006 12:41:15 -0400
Package: xserver-xorg
Version: 1:7.0.20
Severity: normal
When I run X, it runs at 640x480 and reports the refresh rate as
somewhere around -17000 Hz. When I check /var/log/Xorg.0.log, it appears
to have correctly detected my video card (ATI Radeon X800 XL) and my
monitor (DELL 2405FPW) and confirmed that various resolutions up to
[EMAIL PROTECTED] are valid on the primary head.
I upgraded my monitor to the current one in early May and at first it worked
very nicely at 1920x1200. As far as I know, my packages were up to date at
that time, as I update frequently. About a week later, in mid-May, I
updated my packages without any apparent errors, but the next time I ran
X this problem occured. In all other ways, X seems to run ok still. But,
I consider it unusable at 640x480 (at least with my current settings for
fonts/icons, etc.) so it is effectively completely broken for me.
I've tried auto-updating my xorg.conf file, in case that was the
problem (even though the file I had worked fine for a week).
Unfortunately, I'm having problems that seem to have been mentioned in
previous bugs (e.g., #363965), and I can't get the file to regenerate.
I've tried "dpkg-reconfigure xserver-xorg", and I've tried it with the
-phigh flag, but in both cases it doesn't even touch the modification
time. With the -phigh flag, it doesn't even ask all of the setup
questions.
I don't know why debconf-show failed in the system info below.
"debconf-show xserver-xorg" worked when I ran it by hand. It's difficult
for me to paste the information into this message, since I'm running at
console now, but I will be happy to try to provide any system/config
information you would like to see if you let me know. I am eager to fix
this problem and get my system back into a usable state.
By the way, I don't know if this is the source of the problem or
irrelevant, BUT:
In the log file, the radeon driver "Failed to detect secondary monitor
DDC", which is appropriate since I'm not using a secondary monitor. It
then assigns default statistics to this non-existant monitor, rules out
all resolutions as invalid (including 640x480), and assigns it a default
resolution of 640x480. It is clearly aware that this is the secondary
display, and my xorg.conf is set up for only one screen, but it seemed
worth mentioning since the primary display isn't working correctly.
Thank you for your work on these packages, and I hope this problem can
be resolved without too much trouble.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages xserver-xorg depends on:
ii debconf 1.5.1 Debian configuration management
sy
ii x11-common 1:7.0.20 X Window System (X.Org)
infrastruc
ii xbase-clients 1:7.0.1-2 miscellaneous X clients
ii xkb-data 0.8-5 X Keyboard Extension (XKB)
configu
ii xserver-xorg-core 1:1.0.2-8 X.Org X server -- core server
ii xserver-xorg-input-all 1:7.0.20 the X.Org X server -- input
driver
ii xserver-xorg-input-evdev [xs 1:1.1.2-1 X.Org X server -- evdev input
driv
ii xserver-xorg-input-kbd [xser 1:1.0.1.3-2 X.Org X server -- keyboard
input d
ii xserver-xorg-input-mouse [xs 1:1.0.4-3 X.Org X server -- mouse input
driv
ii xserver-xorg-video-ati [xser 1:6.5.8.0-1 X.Org X server -- ATI display
driv
ii xserver-xorg-video-dummy [xs 1:0.1.0.5-2 X.Org X server -- dummy display
dr
ii xserver-xorg-video-fbdev [xs 1:0.1.0.5-2 X.Org X server -- fbdev display
dr
ii xserver-xorg-video-vesa [xse 1:1.0.1.3-2 X.Org X server -- VESA display
dri
ii xserver-xorg-video-vga [xser 1:4.0.0.5-2 X.Org X server -- VGA display
driv
Versions of packages xserver-xorg recommends:
ii discover 2.0.7-2.1 hardware identification system
ii laptop-detect 0.12.1 attempt to detect a laptop
ii mdetect 0.5.2.1 mouse device autodetection tool
ii xresprobe 0.4.23debian1 X Resolution Probe
-- debconf-show failed
xorg.conf
Description: Binary data
debconf.report
Description: Binary data
--- End Message ---
--- Begin Message ---
Kristina Bennett wrote:
> Hello,
>
> Please close the bug, although I never did find out what the problem was.
>
> At the time I was forced to switch to the proprietary drivers, which I still
> use. I did try the xorg driver again recently, and it seemed to work well
> enough, except for a documented problem with slowdown while rendering a GL
> scene. I didn't test it much, but the old problem was immediately obvious,
> so I expect it's no longer an issue.
>
> Thank you,
> Kristina
>
Thanks for the quick reply, closing this bug now. If anybody ever
reproduces, feel free to reopen.
Brice
--- End Message ---
