xorg downgraded to 1024x768 with hoary upgrade

Bug #13642 reported by Hubert Figuiere
18
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Fix Released
Medium
Daniel Stone

Bug Description

I installed warty, then dist-upgraded to hoary. I was in 1600x1200, and I have
been downgraded to 1024x768 after the upgrade....

Revision history for this message
Hubert Figuiere (hub) wrote :

video card is a Rage128. Platform is i386.

Revision history for this message
Daniel Stone (daniels) wrote :

Please attach a full /etc/X11/xorg.conf and /var/log/Xorg.0.log; preferably also
/etc/X11/XF86Config-4 and /var/log/XFree86.0.log.

Revision history for this message
Hubert Figuiere (hub) wrote :

Created an attachment (id=1551)
XF86Config-4

Revision history for this message
Hubert Figuiere (hub) wrote :

Created an attachment (id=1552)
XFree86.0.log

Revision history for this message
Hubert Figuiere (hub) wrote :

Created an attachment (id=1553)
Xorg.0.log

Revision history for this message
Hubert Figuiere (hub) wrote :

Created an attachment (id=1554)
xorg.conf

Revision history for this message
Hubert Figuiere (hub) wrote :

All the requested files have been attached.

Revision history for this message
Navreet (ngill-imsa) wrote :

Same thing happened to me. I am using a Geforce FX 5700 Ultra and a Dell 1901
FP, I did a dpkg-reconfigure xserver-xorg and manually put in my frequencies,
and selected the desired resolution. Works, but I wish it would have just
autodetected.

Revision history for this message
Navreet (ngill-imsa) wrote :

Same thing happened to me. I am using a Geforce FX 5700 Ultra and a Dell 1901
FP, I did a dpkg-reconfigure xserver-xorg and manually put in my frequencies,
and selected the desired resolution. Works, but I wish it would have just
autodetected.

Oh btw, if you need more info, please don't hesitate to contact me at ngill at
imsa dot edu.

Revision history for this message
Daniel Stone (daniels) wrote :

Right, it absolutely should have autodetected. Could you please also include
the output of 'sudo ddcprobe'?

Revision history for this message
Navreet (ngill-imsa) wrote :

$ sudo ddcprobe
VESA BIOS Extensions not detected.

Revision history for this message
Daniel Stone (daniels) wrote :

Let me guess -- amd64?

Revision history for this message
Navreet (ngill-imsa) wrote :

your guess is right, I am running AMD64

Revision history for this message
Hubert Figuiere (hub) wrote :

I forgot to add that my keyboard also got switched from "us" to "ca" which is
unlekily what I wanted (location is set to Canada as I'm in Montreal)

Revision history for this message
Hubert Figuiere (hub) wrote :

$ sudo ddcprobe
vbe: VESA 2.0 detected.
oem: ATI RAGE128
memory: 32768kb
mode: 800x600x16
mode: 1024x768x16
mode: 320x200x32k
mode: 320x200x64k
mode: 320x200x16m
mode: 1600x1200x256
mode: 640x400x256
mode: 640x480x256
mode: 640x480x32k
mode: 640x480x64k
mode: 640x480x16m
mode: 1600x1200x32k
mode: 800x600x256
mode: 800x600x32k
mode: 800x600x64k
mode: 800x600x16m
mode: 1600x1200x64k
mode: 1024x768x256
mode: 1024x768x32k
mode: 1024x768x64k
mode: 1024x768x16m
mode: 1280x1024x256
mode: 1280x1024x32k
mode: 1280x1024x64k
mode: 1280x1024x16m
mode: 132x25 (text)
mode: 132x43 (text)
edid: 1 3
id: 61d3
eisa: NEC61d3
serial: 01010101
manufacture: 24 2002
input: composite sync, sync on green, analog signal.
screensize: 37 27
gamma: 2.200000
dpms: RGB, active off, suspend, standby
timing: 720x400@70 Hz (VGA 640x400, IBM)
timing: 720x400@88 Hz (XGA2)
timing: 640x480@60 Hz (VGA)
timing: 640x480@67 Hz (Mac II, Apple)
timing: 640x480@72 Hz (VESA)
timing: 640x480@75 Hz (VESA)
timing: 800x600@56 Hz (VESA)
timing: 800x600@60 Hz (VESA)
timing: 800x600@72 Hz (VESA)
timing: 800x600@75 Hz (VESA)
timing: 832x624@75 Hz (Mac II)
timing: 1024x768@87 Hz Interlaced (8514A)
timing: 1024x768@60 Hz (VESA)
timing: 1024x768@70 Hz (VESA)
timing: 1024x768@75 Hz (VESA)
timing: 1280x1024@75 (VESA)
ctiming: 640x480@85
ctiming: 800x600@85
ctiming: 1024x768@85
ctiming: 1152x864@85
ctiming: 1280x960@85
ctiming: 1280x1024@85
ctiming: 1600x1200@75
ctiming: 1920x1440@60
dtiming: 1280x1024@99
monitorrange: 31-96, 55-160
monitorname: MultiSync 97
monitorserial: 2602684YA

Revision history for this message
Daniel Stone (daniels) wrote :

Could you please also attach the output of 'sudo xresprobe dummy'?

Revision history for this message
Navreet (ngill-imsa) wrote :

id:
res:
freq:
disptype:

(amd64 box)

Revision history for this message
Matt Brown (mattbrown) wrote :

I'm also experiencing this bug after upgrading to the latest xserver-xorg
package (6.8.2-7), upon restarting the Xserver my desktop is at 1024x768 which
has a nasty tiling effect on my laptop making it unusable :(

 I upgraded to hoary a number of weeks ago and experienced the problems then
too. In all cases running dpkg-reconfigure xserver-xorg and hitting enter until
it exits (ie. Using the defaults completely) results in a perfectly working
configuration at 1400x1050.

Hardware is an IBM T42 Laptop

ddcprobe output:

vbe: VESA 2.0 detected.
oem: ATI MOBILITY RADEON 9600
memory: 65472kb
mode: 320x200x32k
mode: 320x200x64k
mode: 320x200x16m
mode: 1600x1200x256
mode: 640x400x256
mode: 640x480x256
mode: 640x480x32k
mode: 640x480x64k
mode: 640x480x16m
mode: 1600x1200x32k
mode: 800x600x256
mode: 800x600x32k
mode: 800x600x64k
mode: 800x600x16m
mode: 1600x1200x64k
mode: 1024x768x256
mode: 1024x768x32k
mode: 1024x768x64k
mode: 1024x768x16m
mode: 1280x1024x256
mode: 1280x1024x32k
mode: 1280x1024x64k
mode: 1280x1024x16m
edidfail

matt@neon ~ $ sudo xresprobe dummy
id:
res:
freq:
disptype: lcd/lvds

Hope this helps

Revision history for this message
Sebastien Bacher (seb128) wrote :

*** Bug 14708 has been marked as a duplicate of this bug. ***

Revision history for this message
Daniel Stone (daniels) wrote :

bam, got it.

Revision history for this message
Daniel Stone (daniels) wrote :

fixed with the current upgrade; you'll need to do sudo dpkg-reconfigure
xserver-xorg, to get your proper config back. subsequent upgrades won't stomp
your config anymore. cheers.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.