[gutsy] bad modes in xorg.conf

Bug #148231 reported by parren
4
Affects Status Importance Assigned to Milestone
xresprobe (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Binary package hint: xresprobe

After installing on a Acer TM 8400 with ATI (fglrx), my xorg.conf contains the following:

Section "Screen"
        Identifier "Default Screen"
        Device "Generic Video Card"
        Monitor "Generic Monitor"
        Defaultdepth 24
        SubSection "Display"
                Modes "1280x1024" "(pitch" "1280)"
        EndSubSection
EndSection

The Modes line can't be right, can it?

Revision history for this message
Tormod Volden (tormodvolden) wrote :

Thanks for your report. Yes, that looks wrong. This is similar to bug 136981. Can you please try:
 sudo xresprobe fglrx
(on a virtual console) to see what's returned from the monitor detection?

Changed in xresprobe:
assignee: nobody → tormodvolden
status: New → Incomplete
Revision history for this message
parren (peter-arrenbrecht) wrote :

It returns:

id:
res:
freq:
disptype: lcd/lvds

(which is actually the same if I run it from within a windowed terminal).

Here's the output of ddcprobe, too:

vbe: VESA 3.0 detected.
oem: ATI ATOMBIOS
vendor: (C) 1988-2005, ATI Technologies Inc.
product: M56P 01.00
memory: 16384kb
mode: 640x400x256
mode: 640x480x256
mode: 800x600x256
mode: 1024x768x256
mode: 1280x1024x256
mode: 132x25 (text)
mode: 132x43 (text)
mode: 640x480x32k
mode: 640x480x64k
mode: 640x480x16m
mode: 800x600x32k
mode: 800x600x64k
mode: 800x600x16m
mode: 1024x768x32k
mode: 1024x768x64k
mode: 1024x768x16m
mode: 1280x1024x32k
mode: 1280x1024x64k
mode: 1280x1024x16m
mode: 320x200x32k
mode: 320x200x64k
mode: 320x200x16m
mode: 1600x1200x256
mode: 1600x1200x32k
mode: 1600x1200x64k
edid:
edid: 1 3
id: 3146
eisa: SEC3146
serial: 00000000
manufacture: 0 2005
input: analog signal.
screensize: 33 21
gamma: 2.200000
dpms: RGB, no active off, no suspend, no standby
dtiming: 1680x1050@60
monitorid: SAMSUNG
monitorid: LTN154P1-L02

Where I find it rather ironic that the dtiming resolution is not listed as a proper mode.

Revision history for this message
Tormod Volden (tormodvolden) wrote :

I guess xresprobe is using xprobe.sh instead of ddcprobe. There is an option to xresprobe that makes it leave the Xorg log from running xprobe.sh back in /tmp so you can look at it. Can you find it and attach the log here?

Revision history for this message
parren (peter-arrenbrecht) wrote :
Download full text (33.4 KiB)

Here's the log:

X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: Linux Ubuntu (xorg-server 2:1.3.0.0.dfsg-12ubuntu8)
Current Operating System: Linux pearwood 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686
Build Date: 29 September 2007
 Before reporting problems, check http://wiki.x.org
 to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/tmp/xprobe.11674/xorg.log", Time: Wed Oct 3 17:21:04 2007
(++) Using config file: "/tmp/xprobe.11674/xorg.conf"
(==) ServerLayout "Default Layout"
(**) |-->Screen "Default Screen" (0)
(**) | |-->Monitor "Generic Monitor"
(**) | |-->Device "Generic Device"
(**) |-->Input Device "Generic Keyboard"
(**) Option "XkbRules" "xorg"
(**) XKB: rules: "xorg"
(**) Option "XkbModel" "pc104"
(**) XKB: model: "pc104"
(**) Option "XkbLayout" "us"
(**) XKB: layout: "us"
(==) Keyboard: CustomKeycode disabled
(**) |-->Input Device "Generic Mouse"
(**) Option "AllowMouseOpenFail"
(WW) The directory "/usr/share/X11/fonts/misc" does not exist.
 Entry deleted from font path.
(WW) FontPath is completely invalid. Using compiled-in default.
(==) FontPath set to:
 /usr/share/fonts/X11/misc,
 /usr/share/fonts/X11/cyrillic,
 /usr/share/fonts/X11/100dpi/:unscaled,
 /usr/share/fonts/X11/75dpi/:unscaled,
 /usr/share/fonts/X11/Type1,
 /usr/share/fonts/X11/100dpi,
 /usr/share/fonts/X11/75dpi,
 /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType
(**) RgbPath set to "/etc/X11/rgb.txt"
(==) ModulePath set to "/usr/lib/xorg/modules"
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Loader magic: 0x81ea440
(II) Module ABI versions:
 X.Org ANSI C Emulation: 0.3
 X.Org Video Driver: 1.2
 X.Org XInput driver : 0.7
 X.Org Server Extension : 0.3
 X.Org Font Renderer : 0.5
(II) Loader running on linux
(II) LoadModule: "pcidata"
(II) Loading /usr/lib/xorg/modules//libpcidata.so
(II) Module pcidata: vendor="X.Org Foundation"
 compiled for 1.3.0, module version = 1.0.0
 ABI class: X.Org Video Driver, version 1.2
(--) using VT number 9

(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 8086,27a0 card 1025,0092 rev 03 class 06,00,00 hdr 00
(II) PCI: 00:01:0: chip 8086,27a1 card 0000,0000 rev 03 class 06,04,00 hdr 01
(II) PCI: 00:1b:0: chip 8086,27d8 card 1025,0092 rev 02 class 04,03,00 hdr 00
(II) PCI: 00:1c:0: chip 8086,27d0 card 0000,0000 rev 02 class 06,04,00 hdr 81
(II) PCI: 00:1c:1: chip 8086,27d2 card 0000,0000 rev 02 class 06,04,00 hdr 81
(II) PCI: 00:1c:2: chip 8086,27d4 card 0000,0000 rev 02 class 06,04,00 hdr 81
(II) PCI: 00:1c:3: chip 8086,27d6 card 0000,0000 rev 02 class 06,04,00 hdr 81
(II) PCI: 00:1c:4: chip 8086,27e0 card 0000,0000 rev 02 class 06,04,00 hdr 81
(II) PCI: 00:1c:5: chip 8086,27e2 card 0000,0000 rev 02 class 06,04,00 hdr 81
(II) PCI: 00:1d:0: chip 8086,27c8 card 1025,0092 rev 02 class 0c,03,00 hdr 80
(II) PCI: 00:1d:1: chip 8086,27c9 card 1025,0092 rev 02 class 0c,03,00 hdr 00
(II) PCI: 00:1d:2:...

Revision history for this message
Tormod Volden (tormodvolden) wrote :

Was just going to tell the trick was:
XRESPROBE_DEBUG=1 xresprobe fglrx
but you figured it out obviously. I note it here for myself :)

Please use "Attachment" next time.

The only "pitch" in this log is this line: Virtual size is 1024x768 (pitch 0)
But that is not 1280x1024, so I don't think this log reflects what it did on your initial install. By the way how did you install? The desktop installer doesn't pick fglrx anyway.

Can you try it again on a virtual console, after shutting down X with "sudo /etc/init.d/gdm stop" unless you already did so?

Revision history for this message
parren (peter-arrenbrecht) wrote : Re: [Bug 148231] Re: [gutsy] bad modes in xorg.conf

I tried. But the screen just went blank and never came back (and, yes,
I did wait for it quite a while). Sorry. But I did, meanwhile, update
the system with all the latest patches, so maybe that's got something
to do with it. Might go and reinstall later on.

Revision history for this message
Tormod Volden (tormodvolden) wrote :

I still don't understand how it was installed. Can you please try:
 XRESPROBE_DEBUG=1 xresprobe vesa

Revision history for this message
parren (peter-arrenbrecht) wrote :

OK, I reinstalled Gutsy from scratch. Right after install, the xorg.conf looks like this. Shall now try xresprobe vesa.

Revision history for this message
parren (peter-arrenbrecht) wrote :

Here's the output from xresprobe vesa:

laptop: yes; ddc:
attempting an X probe
forking Xorg
id:
res: 1280x1024 (pitch 1280)
freq:
disptype: lcd/lvds
id:
res: 1280x1024 (pitch 1280)
freq:
disptype: lcd/lvds

I have attached the complete log.

Revision history for this message
Tormod Volden (tormodvolden) wrote :

Thanks, that will explain the issue.

Changed in xresprobe:
assignee: tormodvolden → nobody
status: Incomplete → Confirmed
Revision history for this message
Tormod Volden (tormodvolden) wrote :

Can you please also attach the xorg.conf from /tmp/xprobe.* ?

Revision history for this message
Tormod Volden (tormodvolden) wrote :

Got it. lcdsize would grep for "Virtual Size ?x?" in the server log, and in filtering out "?x?" it would also keep whatever was on the rest of the line.

This patch fixes it for the vesa case, but the regexps for all the drivers have the same issue and should probably be corrected.

Revision history for this message
parren (peter-arrenbrecht) wrote :

Tormod, do you still need the xorg.conf? I would have to reinstall
because I clobbered the partition again testing some other things.

Revision history for this message
Tormod Volden (tormodvolden) wrote :

Fixed for other drivers as well. Comments:
 r128: seems bad, but I don't touch it
 savage: must be typo, changed "[^x]" to "[^ ]"
 NV, first match: match [0-9]* instead
 NV, second match: I removed "pitch" from the regexp, so it will work with and without it.
 trident: I removed "found" so that anything in between can be trimmed away

This patch needs a thorough review though.

Revision history for this message
Tormod Volden (tormodvolden) wrote :

parren, no thanks, it's not needed anylonger.

Revision history for this message
Bryce Harrington (bryce) wrote :

I'm surprised we hadn't run into more issues due to this bug. Blind luck I guess.
Yes, I agree we should get this fix in for xresprobe.

Changed in xresprobe:
importance: Undecided → High
status: Confirmed → Fix Committed
Revision history for this message
parren (peter-arrenbrecht) wrote :

On 10/6/07, Bryce Harrington <email address hidden> wrote:
> I'm surprised we hadn't run into more issues due to this bug. Blind luck I guess.

Well, everyone probably switches away from VESA as quickly as
possible. So no one really notices.

Revision history for this message
Daniel Holbach (dholbach) wrote :

Hum, where is (0.4.24ubuntu6)?

Changed in xresprobe:
status: Fix Committed → Incomplete
Revision history for this message
Tormod Volden (tormodvolden) wrote :

> Hum, where is (0.4.24ubuntu6)?
Sorry, the second patch was made on top of the first patch, hence the two versions in the changelog.

Steve Langasek (vorlon)
Changed in xresprobe:
status: Incomplete → Triaged
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

I don't think it is necessary to touch the other entries than vesa, at least not for gutsy. For instance the current SEDLINE for savage works just fine.

I'll upload a new version with the vesa-change.

Revision history for this message
Tormod Volden (tormodvolden) wrote :

I agree with Timo. Only vesa has any bugs reported on this. For the other drivers it's just an improvement and not critical.

Revision history for this message
Bryce Harrington (bryce) wrote :

Here is a proposed xresprobe upload with just the VESA line fix, along with a fix for 127008.
Thoughts?

Revision history for this message
Daniel Holbach (dholbach) wrote :

Was uploaded and accepted.

Changed in xresprobe:
status: Triaged → Fix Released
Revision history for this message
parren (peter-arrenbrecht) wrote :

It still happens in the Gutsy RC.

Revision history for this message
Tormod Volden (tormodvolden) wrote :

parren, does Gutsy RC have the 0.4.24ubuntu6 version?

Revision history for this message
parren (peter-arrenbrecht) wrote :

Ah, in filesystem.manifest on the CD I find

xresprobe 0.4.24ubuntu5

so it would seem to be too old in the RC.
-peo

On 10/16/07, Tormod Volden <email address hidden> wrote:
> parren, does Gutsy RC have the 0.4.24ubuntu6 version?
>
> --
> [gutsy] bad modes in xorg.conf
> https://bugs.launchpad.net/bugs/148231
> You received this bug notification because you are a direct subscriber
> of the bug.
>

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

Other bug subscribers

Remote bug watches

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