I did see this consistently on my natty install, however I got to natty
from lucid by way of maverick, so I don't know where my graphics stack
was at that point (didn't do anything fancy with it though, so
presumably it went to Gallium and I didn't notice).
Since that box is oneiric now, it's too
Just upgraded to Oneiric (I know, I'm crazy), and this bug has
disappeared. A little poking around indicates that the open-source ati
stack in Oneiric has switched to gallium by default instead of mesa,
which is probably why I'm not seeing this anymore.
I don't know if that switch is one we're
Very peculiar.
I managed to get my hands on a second machine with the same graphics
card, and it works fine (using the exact same monitor). Here's the
card's section of lspci on the second machine:
00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express
Integrated Graphics
I suspend/resume frequently, and this has only happened a few more times
since I reported the bug, but I've noticed something very interesting.
Normally upon resume, my monitor displays garbage in the form of ~15
horizontal light and dark stripes of static. This happens for about a
second,
A little more progress. Disabling kernel mode-setting (with nomodeset in
grub) seems to consistently force it into the state described by comment
#2 (correctly named, with an even smaller list of available
resolutions).
--
[Karmic,Lucid] 82G33/G31 Card Fails to detect proper resolutions
Public bug reported:
Binary package hint: xorg
Up-to-date 10.04. Fresh Install.
ATI Radeon 2600XT. Open-source driver. Kernel modesetting enabled
(assumed from the 1440x900 plymouth resolution)
This is an r600 card, so lucid is the first release with open-source 3D.
While the performance isn't
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/48983539/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/48983540/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/48983541/Dependencies.txt
**
Since the glxinfo line from apport gives an error instead of any
information, I am attaching the output of running 'glxinfo' in the bad
state.
I hope it's useful.
** Attachment added: glxinfo.txt
http://launchpadlibrarian.net/48984614/glxinfo.txt
** Description changed:
Binary package
Oddly enough, after three reboots the situation has changed slightly.
Now the monitor is detected 'correctly' (it is listed as a Dell 22
Inch instead of unknown), but the list of resolutions is even worse
than before. It can only go up to 1024x768, and has no 16x9 or 16x10
resolutions available.
And after another reboot it's back to the old behavior. I'll try and
nail down what causes the different behaviors, but at this point it
seems completely random.
--
[Karmic,Lucid] 82G33/G31 Card Fails to detect proper resolutions
https://bugs.launchpad.net/bugs/578460
You received this bug
Public bug reported:
Binary package hint: xorg
Started at Jaunty, everything worked great.
Upgraded to Karmic yesterday, saw the issue. Upgraded to lucid today,
the issue persists.
The monitor should be at 1680x1050. The PreferencesMonitors dialog
reports the current resolution as 1360x768,
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/48232708/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/48232709/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/48232710/Dependencies.txt
**
Thank you, the x-updates ppa is a little more comforting to use than
xorg-edgers :)
--
[RV630-XT] (Needs 8.602) Memory leak in fglrx
https://bugs.launchpad.net/bugs/368271
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in ubuntu.
It is definitely fixed. Any chance of this getting an SRU in Jaunty?
--
[RV630-XT] (Needs 8.602) Memory leak in fglrx
https://bugs.launchpad.net/bugs/368271
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in ubuntu.
The packages in the ppa do not appear to be affected by this bug. I
haven't spent a huge amount of time with them yet, but they should be
OK. I'll report back in a few days when I have some serious uptime under
my belt.
--
[RV630-XT] (Needs 8.602) Memory leak in fglrx
15 matches
Mail list logo
