Ubuntu 7.10 won't use full capability of my ATI graphics card, only get 800x600 now, 6.06 allowed higher resolutions

[rob]

Binary package hint: hal

I have an ATI 7500 All In Wonder graphics card. Earlier versions of Kubuntu (6.06) recognized and used the full capability of the card. I had Ubuntu 7.04 installed for about 5-10 minutes before I upgraded to 7.10 and I think it allowed higher resolutions but I'm not 100% sure. The highest resolution I can choose with Ubuntu 7.10 is 800x600.

ProblemType: Bug
Architecture: i386
Date: Sun Nov 11 23:34:17 2007
DistroRelease: Ubuntu 7.10
Package: hal 0.5.9.1-6ubuntu5
PackageArchitecture: i386
SourcePackage: hal
Uname: Linux rob-desktop 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux

[Corey Burger (corey.burger)]

Is this default Kubuntu without the binary ATI drivers?

[sherbert (sherbert-lawwest)]

ditto on my machine, too, Rob. I download all the offered changes and this is a recent development on my screen. (ver 7.10) Prior versions offered other resolutions.

[rob (rtshwood)]

Hi Corey,

  Sorry I took so long to respond.

  Both the Kubuntu and Ubuntu installs were from the standard download. To date, I have not download any extra binary ATI drivers.

  I did find some extra monitor settings in Gnome desktop which have helped. My current panel menus are at a resolution that I like but the icons on the desktop are still quite large. I'm getting closer...

Corey Burger <email address hidden> wrote:
  Is this default Kubuntu without the binary ATI drivers?

** Changed in: xserver-xorg-video-ati (Ubuntu)
Sourcepackagename: hal => xserver-xorg-video-ati
Status: New => Incomplete

--
Ubuntu 7.10 won't use full capability of my ATI graphics card, only get 800x600 now, 6.06 allowed higher resolutions
https://bugs.launchpad.net/bugs/162136
You received this bug notification because you are a direct subscriber
of the bug.

---------------------------------
Be a better sports nut! Let your teams follow you with Yahoo Mobile. Try it now.

[Tormod Volden (tormodvolden)]

Please attach Xorg.0.log and if possible, try the newer test versions from https://wiki.ubuntu.com/XorgOnTheEdge

[Rolf Leggewie (r0lf)]

I believe I have seen this exact same problem as well. Currently, I work around this and two other serious problems I had (bug 148408 and bug 187967) with the gutsy version by just downgrading xserver-xorg-video-ati to feisty.

https://launchpad.net/ubuntu/feisty/i386/xserver-xorg-video-ati/1:6.6.3-2ubuntu6
https://launchpad.net/ubuntu/gutsy/i386/xserver-xorg-video-ati/1:6.7.195-1ubuntu2

[Rolf Leggewie (r0lf)]

I will try out the latest versions from hardy, recompiled for gutsy (my ppa or that from Tormod).

My computer is a Thinkpad X24 with a Radeon M6 LY graphics chip.

[Rolf Leggewie (r0lf)]

I installed http://launchpadlibrarian.net/11689116/xserver-xorg-video-ati_6.7.197%2Bgit20080201.bcd59010-0ubuntu0tormod%7Egutsy_i386.deb for testing and the situation is at least "changed"

My internal display is 1024x768. This has never been a problem. The external display is a TFT with 1680x1050 native resolution, working fine with the feisty driver. After installing above package and restarting X, I get a 1024x768 clone display. "System - Preference - Screen resolution" still does not show anything else, but I am told this applet is still a work in progress, some might even say outright broken (did work fine for me with the feisty driver!).

xrandr does seem capable of making this into a dual-head setup, though. Albeit with 1280x1024 for the external display as max (see attached log).

[Tormod Volden (tormodvolden)]

Please attach Xorg.0.log

[Rolf Leggewie (r0lf)]

I am back on feisty and I am not installing that package again anytime soon. I am back to some serious problems I had previously fixed by downgrading to feisty. Me trying to help out by testing is now again leaving me with a machine that completely freezes when switching to a VT and then back to X. I should have thought about providing that log. Now it won't be me at before some providing that Xorg.0.log. Desolé.

[Bugs-freedesktop-org (bugs-freedesktop-org)]

Hi,

I have a Thinkpad X24 with the ATI Radeon M6 LY chip. When I upgraded from feisty to gutsy the external, secondary monitor stopped working. This has been reported as https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/162136

The situation has changed over time but the regression has still not been fixed 100%

https://launchpad.net/ubuntu/feisty/i386/xserver-xorg-video-ati/1:6.6.3-2ubuntu6
* everything was working fine, external resolution of 1680x1050

https://launchpad.net/ubuntu/gutsy/i386/xserver-xorg-video-ati/1:6.7.195-1ubuntu2
* 2nd monitor completely broken, clone mode

http://launchpadlibrarian.net/11689116/xserver-xorg-video-ati_6.7.197%2Bgit20080201.bcd59010-0ubuntu0tormod%7Egutsy_i386.deb
* with this inofficial, bleeding-edge package, xrandr is back to reporting
  1280x1024 resolution for the external monitor which is better than nothing
  but still not the truth

I am sorry, I can not provide an Xorg.0.log for the last deb. My mistake.

Regards

Rolf

[Bugzi09-fdo-tormod (bugzi09-fdo-tormod)]

It will be difficult to debug this without any log file at all. Would it be possible for you to for instance try a live CD like Ubuntu Hardy Alpha 4, and install a "bleeding-edge" package on it? Thanks.

[Bugs-freedesktop-org (bugs-freedesktop-org)]

(In reply to comment #1)
> It will be difficult to debug this without any log file at all.

http://launchpadlibrarian.net/11989952/Xorg.0.log

[Bugs-freedesktop-org (bugs-freedesktop-org)]

I deleted xorg.conf and restarted gdm before uploading that log.

[Rolf Leggewie (r0lf)]

situation is still the same for 1:6.7.197+git20080208.8606c1bd-0ubuntu0tormod~gutsy

[agd5f (agd5f)]

your log looks fine. I think this is configuration issue. the default virtual size for your chips 1600x1200 which won't fit a 1680x1050 mode. you'll need to add a virtual line to the display subsection of the screen section your config to allocate a large enough desktop:

Virtual 2704 1050

[Bugs-freedesktop-org (bugs-freedesktop-org)]

Created an attachment (id=15675)
external monitor

I retried with the latest package from Tormod (http://launchpadlibrarian.net/12175308/xserver-xorg-video-ati_6.8.0-1ubuntu0tormod%7Egutsy_i386.deb) and the Virtual-line, but the result is not good. On login, the external monitor looks as in the screenshot above. The internal monitor is the same, only that it shows the 1024x768 area only (anything non-green with the flower). After login, the external monitor completely blanks and I have only the internal monitor with 1024x768.

[Bugs-freedesktop-org (bugs-freedesktop-org)]

Created an attachment (id=15676)
the xorg.conf I used (I am sure there are lots of errors in there)

[Bugs-freedesktop-org (bugs-freedesktop-org)]

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

[Bugs-freedesktop-org (bugs-freedesktop-org)]

While logged in, I queried xrandr

~$ xrandr -q
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 2704 x 1050
VGA-0 connected (normal left inverted right)
   1680x1050 60.0 +
   1280x1024 74.9 75.0 59.9
   1152x864 75.0 74.8
   1024x768 74.9 75.1 70.1 60.0
   832x624 74.6
   800x600 72.2 75.0 74.9 60.3
   640x480 75.0 72.8 66.7 60.0
   720x400 70.1
   640x350 70.1
LVDS connected 1024x768+0+0 (normal left inverted right) 0mm x 0mm
   1024x768 60.0*+ 60.0
   800x600 60.3 59.9
   640x480 59.9 59.4

"~$ xranrd --fb 2704x1050" did get me a bigger screen, but it was still on the internal screen only. The external screen was still in suspend.

[agd5f (agd5f)]

(In reply to comment #5)
> Created an attachment (id=15675) [details]
> external monitor
>

that's clone mode :)

> I retried with the latest package from Tormod
> (http://launchpadlibrarian.net/12175308/xserver-xorg-video-ati_6.8.0-1ubuntu0tormod%7Egutsy_i386.deb)
> and the Virtual-line, but the result is not good. On login, the external
> monitor looks as in the screenshot above. The internal monitor is the same,
> only that it shows the 1024x768 area only (anything non-green with the flower).
> After login, the external monitor completely blanks and I have only the
> internal monitor with 1024x768.
>

looks like gnome strikes again. If you used the gnome gui to change the mode, it will reset that mode every time you log in. it's not randr 1.2 aware, so it has no concept of multiple heads. There's some gconf key you have to remove (I can't remember where is lives off hand).

xrandr --output VGA-0 --right-of LVDS
will switch to dualhead. you can set up your xorg.conf if you want dualhead to be permanently on.

[agd5f (agd5f)]

(In reply to comment #9)

> xrandr --output VGA-0 --right-of LVDS
> will switch to dualhead. you can set up your xorg.conf if you want dualhead to
> be permanently on.
>

xrandr --output VGA-0 --auto
to turn on the output.

[Rolf Leggewie (r0lf)]

still unresolved with http://launchpadlibrarian.net/12175308/xserver-xorg-video-ati_6.8.0-1ubuntu0tormod%7Egutsy_i386.deb

[Bugs-freedesktop-org (bugs-freedesktop-org)]

(In reply to comment #9)
> (In reply to comment #5)
> > Created an attachment (id=15675) [details] [details]
> > external monitor

> that's clone mode :)

Which is basically still what I've got even with the commands you gave.

> looks like gnome strikes again. If you used the gnome gui to change the mode,
> it will reset that mode every time you log in. it's not randr 1.2 aware, so it
> has no concept of multiple heads. There's some gconf key you have to remove (I
> can't remember where is lives off hand).

I search for randr with gconf-editor but found only two entries which I think are unrelated. I think this setting is creating problems at my end. Would you mind helping me to find that key?

I am still completely stuck with the newer Xorg on Thinkpad X24. Latest output from "xrandr -q" is now again back to

$ xrandr -q

Screen 0: minimum 320 x 200, current 1024 x 768, maximum 1280 x 1200
VGA-0 connected (normal left inverted right)
   1280x1024 74.9 75.0 59.9
   1152x864 75.0 74.8
   1024x768 74.9 75.1 70.1 60.0
   832x624 74.6
   800x600 72.2 75.0 74.9 60.3
   640x480 75.0 72.8 66.7 60.0
   720x400 70.1
   640x350 70.1
LVDS connected 1024x768+0+0 (normal left inverted right) 0mm x 0mm
   1024x768 60.0*+ 60.0
   800x600 60.3
   640x480 59.9

(resolution of external monitor is not correctly discovered.)

[Bugs-freedesktop-org (bugs-freedesktop-org)]

Created an attachment (id=15794)
Log for latest tormod package (April 4th, I believe), empty xorg.conf

[agd5f (agd5f)]

(In reply to comment #11)
> I search for randr with gconf-editor but found only two entries which I think
> are unrelated. I think this setting is creating problems at my end. Would you
> mind helping me to find that key?

~/.gconf/desktop/gnome/screen/*

>
> I am still completely stuck with the newer Xorg on Thinkpad X24. Latest output
> from "xrandr -q" is now again back to
>
> $ xrandr -q
>
> Screen 0: minimum 320 x 200, current 1024 x 768, maximum 1280 x 1200
> VGA-0 connected (normal left inverted right)
> 1280x1024 74.9 75.0 59.9
> 1152x864 75.0 74.8
> 1024x768 74.9 75.1 70.1 60.0
> 832x624 74.6
> 800x600 72.2 75.0 74.9 60.3
> 640x480 75.0 72.8 66.7 60.0
> 720x400 70.1
> 640x350 70.1
> LVDS connected 1024x768+0+0 (normal left inverted right) 0mm x 0mm
> 1024x768 60.0*+ 60.0
> 800x600 60.3
> 640x480 59.9
>
> (resolution of external monitor is not correctly discovered.)
>

it is, but as I said, the max size of your desktop is not big enough to accommodate it:
(II) RADEON(0): Not using mode "1680x1050" (width too large for virtual size)

you'll need to add a virtual line (like your previous config) to the display subsection of the screen section your config to allocate a large enough desktop:
Virtual 2704 1050

[agd5f (agd5f)]

Also, don't use the gnome display config gui or it will screw it up again. use xrandr directly.

[Bugs-freedesktop-org (bugs-freedesktop-org)]

Alex, thank you for the quick reply.

(In reply to comment #13)
> > mind helping me to find that key?
>
> ~/.gconf/desktop/gnome/screen/*

nothing there. The only directory under ~/.gconf/ is apps. But I remember I *do* have used that gnome GUI thing in the past. If only I knew where to go to get rid of the changes it made.

> you'll need to add a virtual line (like your previous config) to the display
> subsection of the screen section your config to allocate a large enough
> desktop:
> Virtual 2704 1050

OK, I will. It is only that when I tried to carry over my previous xorg.conf things where even worse than with an empty xorg.conf. I'll try out a few things and report back.

(In reply to comment #14)
> Also, don't use the gnome display config gui or it will screw it up again. use
> xrandr directly.

not there yet, but after things are fixed, I'll stay away from the Gnome applet, I promise.

[Bugs-freedesktop-org (bugs-freedesktop-org)]

(In reply to comment #14)
> Also, don't use the gnome display config gui or it will screw it up again. use
> xrandr directly.

BTW, are you talking about gnome-display-properties or displayconfig-gtk? gnome-display-properties is the default for gnome, I believe.

[Bugs-freedesktop-org (bugs-freedesktop-org)]

(In reply to comment #15)
> > ~/.gconf/desktop/gnome/screen/*
>
> nothing there.

;-)

Hehe, silly me. I failed to realize that I was looking at the wrong computer (ssh console login to another machine). So, what do I do? "rm -Rf ~/.gconf/desktop/gnome/screen/"? I'll try that now, gconf-editor gave me no option to remove that branch.

[Bugs-freedesktop-org (bugs-freedesktop-org)]

OK, here is the current status. I am using grandr GUI to make any changes (I am not so familiar with the xrandr command line, yet. The version in gutsy crashed (https://bugs.launchpad.net/ubuntu/+source/grandr/+bug/214892) so I backported the hardy one which works fine (https://launchpad.net/~r0lf/+archive).

I can set up a dual screen, but only with both displays set to 640x480 (wow, what an experience ;-)). The problem seems to be that for some reason the display cannot be wider than 1280 pixels. I'll try meddling with xorg.conf and the Virtual line as suggested, now.

[Bugs-freedesktop-org (bugs-freedesktop-org)]

Created an attachment (id=15802)
xorg.conf I used (created by "sudo dpkg-reconfigure xserver-xorg -phigh" and adding the Virtual line)

X would not even start with this. I had to go back to an empty xorg.conf for now.

[Bugs-freedesktop-org (bugs-freedesktop-org)]

Created an attachment (id=15803)
X log file

not sure what the "(EE) RADEON(0): Memory manager initialization to (0,0) (2704,775) failed" line is about

[Bugs-freedesktop-org (bugs-freedesktop-org)]

IT'S WORKING!!!

I had to reduce Default Depth to 16. Fonts do look as good as before, but I remember I tweaked something. I'll need to look into that. I am just glad that I am back up to date with X and still have my dual-head setup. Thanks, guys, for all the good work.

[Bugs-freedesktop-org (bugs-freedesktop-org)]

(In reply to comment #21)
> Fonts do look as good as before

I missed a 'not' there. The fonts do not look as nice as previously, but I am sure this can be worked out eventually.

[agd5f (agd5f)]

(In reply to comment #22)
> I missed a 'not' there. The fonts do not look as nice as previously, but I am
> sure this can be worked out eventually.
>

Your LCD does not provide an edid, so there is no way to determine it's physical size and hence dpi. you might try adjusting the dpi with xrandr:
xrandr --fbmm <width in mm>x<height in mm>
Alternatively, you can add a DisplaySize line to the monitor section for your LVDS panel.

[Rolf Leggewie (r0lf)]

The very latest package from tormod fixed this for me. Take a look at https://bugs.freedesktop.org/show_bug.cgi?id=14336. Thanks, guys.

[Tormod Volden (tormodvolden)]

So it works with my package and not with the normal hardy one? Just asking since this was not clear for me in the upstream report. Marking the bug accordingly as "fix committed" for now.

Did you use 16bit in 6.06? Could this be the reason it worked back then?

[Rolf Leggewie (r0lf)]

I am on gutsy and have not tried the hardy package. I also used 16bit before, but this cannot be the reason for this bug since I always used my xorg.conf with those packages. There was a genuine bug in there.

[Bryce Harrington (bryce)]

Tormod, ideas on what the patch might have been that fxied it?

[Tormod Volden (tormodvolden)]

Unfortunately not. Maybe Rolf can help us to narrow down which version works and which doesn't?

[Rolf Leggewie (r0lf)]

I always reported the versions that worked and which did not here

[Tormod Volden (tormodvolden)]

Rolf, it needs a clear mind to merge and analyze the information in these bug reports :) If I got it right, you mention 6.8.0-1 not working, but 6.8.0+git20080404 working. However you did other configuration changes in between. Did you try the old one again with the exact same known-good configuration? Or any intermediate versions?

[Rolf Leggewie (r0lf)]

My testing time is limited and testing X is actually quite cumbersome. How much benefit vs. cost is there?

[Tormod Volden (tormodvolden)]

If we could identify a single change that makes this work, we could apply it to the official Hardy version, to the benefit of all users having this issue. I guess for every bug report there are dozens or hundreds of users having the same problem, but not being active enough to do something about it, like even signing up for a launchpad account to say "me too"... Therefore we are very grateful for (and depending on) competent users like you that identify these issues and help getting them fixed.

But in the end it's a question of priorities, for you and for us. Personally I wouldn't spend so much time on a problem that has been fixed already upstream. For instance, if we would have something like 6.8.1 soon, we could maybe push it to hardy-backports. According to the Ubuntu release policy it would be too risky to just upgrade Hardy to the git version right now, we don't want any regressions surprising us - a handful of known bugs is better than a handful of new ones.

[Rolf Leggewie (r0lf)]

well, after going down as far as the official 1:6.7.195-1ubuntu2 xserver-xorg-video-ati from gutsy, it starts to look like a configuration issue (which I find somewhat hard to believe, although I did have a hard time reconfiguring the newer xorg correctly. Maybe a dependency was missing?). With the attached xorg.conf and the help of grandr I can get out of the clone mode and into a dualhead setup.

[Rolf Leggewie (r0lf)]

BTW, how do I enable dualhead by default so that I don't have to use grandr all the time?

[Rolf Leggewie (r0lf)]

the xorg.conf I previously used is at https://bugs.freedesktop.org/attachment.cgi?id=15676

[Bryce Harrington (bryce)]

I'm a little unclear, but it sounds like the issue got worked out, so I'm closing. If it still exists on Hardy, though, of course please feel free to reopen, with additional details.