bug: 314205 title: [RS482] wine screen updates faulty in Jaunty date-reported: Mon, 05 Jan 2009 23:44:14 -0000 date-updated: Wed, 13 Jan 2010 04:46:23 -0000 reporter: Stephen Cradock (s-cradock) duplicate-of: duplicates: attachments: https://bugs.launchpad.net/bugs/314205/+attachment/458774/+files/glxinfo.txt text/plain https://bugs.launchpad.net/bugs/314205/+attachment/552960/+files/Xorg.0.log text/plain patches: tags: jaunty subscribers: Stephen Cradock (s-cradock) Scott Ritchie (scottritchie) Hanen Ben Rhouma (hanen105) Sergio Zanchetta (primes2h) task: compiz (Ubuntu) status: Invalid date-created: Tue, 06 Jan 2009 08:23:10 -0000 date-left-new: Wed, 15 Apr 2009 02:41:47 -0000 date-closed: Wed, 15 Apr 2009 02:41:47 -0000 reporter: Scott Ritchie (scottritchie) importance: Undecided component: universe assignee: milestone: task: wine (Ubuntu) status: Invalid date-created: Mon, 05 Jan 2009 23:44:14 -0000 date-left-new: Sat, 11 Apr 2009 19:16:25 -0000 date-closed: Sat, 11 Apr 2009 19:16:25 -0000 reporter: Stephen Cradock (s-cradock) importance: Undecided component: universe assignee: milestone: task: xserver-xorg-video-ati (Ubuntu) status: Fix Released date-created: Sat, 11 Apr 2009 19:13:26 -0000 date-left-new: Sat, 11 Apr 2009 21:16:09 -0000 date-confirmed: Sat, 29 Aug 2009 19:17:26 -0000 date-triaged: Sat, 29 Aug 2009 19:17:26 -0000 date-inprogress: Sat, 29 Aug 2009 19:17:26 -0000 date-closed: Wed, 02 Sep 2009 05:05:21 -0000 date-fix-committed: Wed, 02 Sep 2009 05:05:21 -0000 date-fix-released: Wed, 02 Sep 2009 05:05:21 -0000 reporter: Scott Ritchie (scottritchie) importance: Medium component: main assignee: milestone: Content-Type: multipart/mixed; boundary="===============2627186761150590563==" MIME-Version: 1.0 --===============2627186761150590563== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Binary package hint: wine After upgrading to Jaunty, I experienced the ia32libs problems reported earlier due to the missing libuuid. This showed up in wine as well as other programs. The ia32libs problem has now been addressed, but wine still behaves strangely. The wine window opens, but screen updates are jerky and slow, and (in spider) the cards progressively fail to redraw as the game progresses, leaving black holes in place of the card faces. uname -a Linux sc-laptop 2.6.28-4-generic #6-Ubuntu SMP Thu Jan 1 22:53:33 UTC 2009 = x86_64 GNU/Linux wine 1.0.1-0ubuntu4 xserver-xorg-video-radeon 1:6.9.0.91-1ubuntu4 compiz is installed and running. Without compiz (metacity as the window manager) wine behaves correctly. with compiz turned back on, I cannot access Wine Drive C:, open Notepad.exe or spider.exe in Wine, open Wine Config, or get anything but an empty Wine window. [lspci] 00:00.0 Host bridge [0600]: ATI Technologies Inc RS480 Host Bridge [1002:59= 50] Subsystem: Hewlett-Packard Company Device [103c:3085] 01:05.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon XPRES= S 200M 5955 (PCIE) [1002:5955] Subsystem: Hewlett-Packard Company Device [103c:3085] --===============2627186761150590563== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Scott Ritchie (scottritchie) Date: Tue, 06 Jan 2009 08:21:42 -0000 Message-Id: <20090106082142.16265.62941.malone@gandwana.canonical.com> Compiz has always messed up Wine: https://bugs.edge.launchpad.net/ubuntu/+source/wine/+bug/237209 --===============2627186761150590563== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Stephen Cradock (s-cradock) Date: Tue, 06 Jan 2009 14:54:44 -0000 Message-Id: <20090106145444.13447.73441.malone@gangotri.canonical.com> Thanks, Scott. They play together just fine in Intrepid, at least on my machine (same one as above). I've tried turning off various effects, but haven't found a sub-set that restores Wine to normality in Jaunty. Now that Compiz seems to be "on" by default it would be good if Wine was working correctly. --===============2627186761150590563== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Stephen Cradock (s-cradock) Date: Sat, 31 Jan 2009 03:24:31 -0000 Message-Id: <20090131032432.28371.61582.malone@palladium.canonical.com> Is anything happening? Wine and programs running under Wine in Jaunty continue to behave strangely. Some of the strange behavior (progressive failure of the Wine "desktop" window to update correctly, leaving blue patches in place of card images in Spider, for instance) does appear to be due to some interaction or failure of interaction with compiz, but even without compiz effects enabled Wine still doesn't feel as if it's working right under Jaunty. The problems with wineconfig and with browsing "C:" seem to have been fixed. Strong contrast with Intrepid - Wine and programs in it work fine in Intrepid whether compiz is enabled or not. Running (for instance) wine spider.exe in a terminal raises some alsa configuration errors, but no helpful terminal output. Any chance of some workaround short of turning off compiz? --===============2627186761150590563== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Luke Faraone (lfaraone) Date: Sun, 08 Feb 2009 22:22:21 -0000 Message-Id: <20090208222221.22275.79854.malone@potassium.ubuntu.com> metacity --replace & wine foo. --===============2627186761150590563== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Stephen Cradock (s-cradock) Date: Sun, 08 Feb 2009 22:45:50 -0000 Message-Id: <20090208224550.500.2929.malone@potassium.ubuntu.com> That looks as if it switches window manager to metacity - thus turning off compiz. If there is a general problem with Wine in jaunty, let's talk about it and help to get it fixed. If there is a general problem with compiz in Jaunty, ditto. If the problem is some esoteric interaction between them, ditto. I'm sorry if my simple-minded approach is offending anyone - I thought the purpose of testing a new pre-release was to spot little niggles like this so the developers could fix them before the final release. I've drawn attention to this one - it's real, it's reproducible, at least on my machine, and it's minor - not really a show-stopper. If anyone needs more information about what's going on they could: a) ask me for logs, etc b) try running both wine and compiz in Jaunty and see if they get the same effects as I've described. Or just ignore it, in which case I will find Jaunty less satisfactory than Intrepid, where wine and compiz work together just fine. --===============2627186761150590563== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Stephen Cradock (s-cradock) Date: Tue, 10 Feb 2009 07:04:44 -0000 Message-Id: <20090210070444.6449.28822.malone@potassium.ubuntu.com> Further information: I get the same errors in screen re-drawing in Wine even with compiz disabled, i.e. using the "Normal" setting in Visual Effects tab of the Appearance Preferences. This suggests to me that the errors occur with any window manager that tries to use compositing, including metacity. Once I reset the Visual Effects setting to "None", which I believe uses metacity without compositing, I get normal screen re-drawing in Wine. I'm using amd64, kernel 2.6.28-7-generic, and the open-source ati/radeon drivers xserver-xorg-video-ati and xserver-xorg-video-radeon, on an old hp pavilion with the Radeon Xpress 200M 5955 chipset. In Jaunty the drivers are version 1:6.10.0-1ubuntu1. I'm attaching the glxinfo output for the situation when Wine is redrawing correctly. --===============2627186761150590563== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Stephen Cradock (s-cradock) Date: Sat, 11 Apr 2009 18:10:40 -0000 Message-Id: <20090411181040.14658.48372.malone@potassium.ubuntu.com> Very disappointed to see no response! I have upgraded to the Wine 1.1.19 beta, but no change in this unacceptable behavior. Jaunty is up to date, now in beta; Wine is the latest available version, and the problem persists. It is NOT a problem with compiz, as it occurs with metacity/compositing as the window manager. --===============2627186761150590563== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Steve Dodier-Lazaro (sidi) Date: Sat, 11 Apr 2009 18:39:26 -0000 Message-Id: <20090411183926.774.72960.malone@palladium.canonical.com> Hello Stephen, You may not know it, but we switched to X.org server 1.6 in Jaunty, which may have, as a result, an increase of instability for the GPUs. This issue is, imho, nonely related to Wine, and you're likely to run into same trouble with any OpenGL game, because Compiz + openGL have always been messy, and because we use a new x.org server, and because ATi does take time to make good and stable drivers. The only ways to make this significantly better would be to contribute in making great free drivers (since we can't contribute on proprietary ones), and find out a way to make compiz (and other composite wms, such as XFCE/KDE ones) behave more smoothly with OpenGL apps (obviously i don't know what's wrong with it, but remember compiz fusion is still under development). I'm sorry to say it, but i don't think this is going to improve in a close future, and there is nothing the people at wine can do to change that. --===============2627186761150590563== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Scott Ritchie (scottritchie) Date: Sat, 11 Apr 2009 19:16:24 -0000 Message-Id: <20090411191625.14658.92592.malone@potassium.ubuntu.com> Sorry I couldn't figure this one out sooner Stephen, but unfortunately I believe Steve is right that this is a binary driver bug. --===============2627186761150590563== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Stephen Cradock (s-cradock) Date: Sat, 11 Apr 2009 19:58:36 -0000 Message-Id: <20090411195836.25859.39658.malone@gandwana.canonical.com> You could both be right - should I file another bug against xserver-xorg 1.6 itself? I don't play many games - mostly the standard gnome set, which don't show any problems for me. The only one I use Wine for is spider solitaire. From what you say, this might be a problem with the composite extension in the x-x-v-ati driver, which should show up with other OpenGL apps. glxgears shows a normal output screen, but a low frame rate, with or without compiz. Compiz without Wine/spider works fine, smooth rotating cube, fire effect, all that jazz. Any suggestions about what else I can check - combinations of video settings/effects/apps that might show problems? --===============2627186761150590563== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Steve Dodier-Lazaro (sidi) Date: Sat, 11 Apr 2009 20:09:43 -0000 Message-Id: <20090411200943.23831.8769.malone@gangotri.canonical.com> Hello, You might want to try OpenArena / ET:QW / Nexuiz in order to see if you have a big FPS difference between Intrepid and Jaunty, this may help to confirm the problem. --===============2627186761150590563== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Stephen Cradock (s-cradock) Date: Sat, 11 Apr 2009 20:26:06 -0000 Message-Id: <20090411202607.694.56489.malone@palladium.canonical.com> That would not work for me - I don't want my machine to play violent shooting games. I want it to run regular everyday apps without showing video artefacts and crashing. If OpenGL is only useful for fast-action games it doesn't bother me whether it works or not; but please would developers not try to use it for anything else in that case. If it is, on the other hand, a general purpose video layer that everyone uses, then I believe it is important that it does that well with the latest and greatest xserver-xorg, the cutting-edge ubuntu, and the OS drivers. --===============2627186761150590563== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Bryce Harrington (bryce) Date: Sat, 11 Apr 2009 21:16:08 -0000 Message-Id: <20090411211609.23406.26442.malone@potassium.ubuntu.com> Please attach your Xorg.0.log, and the output of 'lspci -vvnn'. If you've made any customizations to your xorg.conf, attach that as well. One point of confusion we need cleared up: This bug is filed against the open source -ati driver, but some comments are referring to the proprietary driver (-fglrx). If you could, please clarify which driver you are using. Also, if you have had -fglrx installed previously but are now using -ati, be aware that the latter can cause some incompatibilities with the former if not properly uninstalled. See the guide at http://wiki.ubuntu.com/X/Troubleshooting if this could be the situation; it includes instructions for how to rectify it. --===============2627186761150590563== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Steve Dodier-Lazaro (sidi) Date: Sat, 11 Apr 2009 21:42:49 -0000 Message-Id: <20090411214249.694.50374.malone@palladium.canonical.com> Hello Bryce, I'm the one who referred to proprietary drivers but I was probably wrong, i really can't recognise ATi prop/free drivers' names, I apologize for that. Cordially, SD. --===============2627186761150590563== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Bryce Harrington (bryce) Date: Sat, 11 Apr 2009 21:59:39 -0000 Message-Id: <20090411215939.GC18089@bryceharrington.org> On Sat, Apr 11, 2009 at 09:42:49PM -0000, Steve Dodier wrote: > Hello Bryce, >=20 > I'm the one who referred to proprietary drivers but I was probably > wrong, i really can't recognise ATi prop/free drivers' names, I > apologize for that. No prob, once you attach your Xorg.0.log that should tell. Also, do refer to the troubleshooting page to make sure you don't have leftover fglrx bits installed - they can sometimes cause problems not unlike what's described here. Bryce --===============2627186761150590563== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Stephen Cradock (s-cradock) Date: Sat, 11 Apr 2009 22:01:15 -0000 Message-Id: <20090411220115.14559.38022.malone@potassium.ubuntu.com> I am using the opensource drivers - have been exclusively since early testing Intrepid, AFAIK. The current Jaunty install was upgraded from Intrepid last week, after beta release, and updated daily since. Here is lspci -vvnn, and Xorg.0.log as an attachment: sc@sc-laptop:~$ lspci -vvnn 00:00.0 Host bridge [0600]: ATI Technologies Inc RS480 Host Bridge [1002:59= 50] Subsystem: Hewlett-Packard Company Device [103c:3085] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Steppi= ng- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=3Dmedium >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel modules: shpchp 00:04.0 PCI bridge [0604]: ATI Technologies Inc RS480 PCI Bridge [1002:5a36] Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Steppi= ng- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=3Dfast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport-driver Kernel modules: shpchp 00:13.0 USB Controller [0c03]: ATI Technologies Inc IXP SB400 USB Host Cont= roller [1002:4374] (prog-if 10) Subsystem: ATI Technologies Inc IXP SB400 USB Host Controller [1002:4374] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Steppi= ng- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=3Dmedium >TAbort- SERR- Kernel driver in use: ohci_hcd 00:13.1 USB Controller [0c03]: ATI Technologies Inc IXP SB400 USB Host Cont= roller [1002:4375] (prog-if 10) Subsystem: ATI Technologies Inc IXP SB400 USB Host Controller [1002:4375] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Steppi= ng- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=3Dmedium >TAbort- SERR- Kernel driver in use: ohci_hcd 00:13.2 USB Controller [0c03]: ATI Technologies Inc IXP SB400 USB2 Host Con= troller [1002:4373] (prog-if 20) Subsystem: ATI Technologies Inc IXP SB400 USB2 Host Controller [1002:4373] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Steppi= ng- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=3Dmedium >TAbort- SERR- Kernel driver in use: ehci_hcd 00:14.0 SMBus [0c05]: ATI Technologies Inc IXP SB400 SMBus Controller [1002= :4372] (rev 10) Subsystem: Hewlett-Packard Company Device [103c:3085] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Steppi= ng- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=3Dmedium >TAbort- SERR- Kernel driver in use: piix4_smbus Kernel modules: i2c-piix4 00:14.1 IDE interface [0101]: ATI Technologies Inc IXP SB400 IDE Controller= [1002:4376] (prog-if 8a [Master SecP PriP]) Subsystem: Hewlett-Packard Company Device [103c:3085] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Steppi= ng- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=3Dmedium >TAbort- SERR- Kernel driver in use: pata_atiixp 00:14.3 ISA bridge [0601]: ATI Technologies Inc IXP SB400 PCI-ISA Bridge [1= 002:4377] Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Steppi= ng- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=3Dmedium >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- 00:14.5 Multimedia audio controller [0401]: ATI Technologies Inc IXP SB400 = AC'97 Audio Controller [1002:4370] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:3085] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Steppi= ng- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=3Dslow >TAbort- SERR- Kernel driver in use: ATI IXP AC97 controller Kernel modules: snd-atiixp 00:14.6 Modem [0703]: ATI Technologies Inc SB400 AC'97 Modem Controller [10= 02:4378] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:3085] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Steppi= ng- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=3Dslow >TAbort- SERR- Kernel driver in use: ATI IXP MC97 controller Kernel modules: snd-atiixp-modem 00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opter= on] HyperTransport Technology Configuration [1022:1100] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Steppi= ng- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=3Dfast >TAbort- SERR- 00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opter= on] Address Map [1022:1101] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Steppi= ng- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=3Dfast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel modules: radeonfb 03:00.0 FireWire (IEEE 1394) [0c00]: Texas Instruments TSB43AB22/A IEEE-139= 4a-2000 Controller (PHY/Link) [104c:8023] (prog-if 10) Subsystem: Hewlett-Packard Company Device [103c:3085] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Steppi= ng- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=3Dmedium >TAbort- SERR- Kernel driver in use: ohci1394 Kernel modules: firewire-ohci, ohci1394 03:02.0 Network controller [0280]: Broadcom Corporation BCM4306 802.11b/g W= ireless LAN Controller [14e4:4320] (rev 03) Subsystem: Hewlett-Packard Company Device [103c:12f8] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Steppi= ng- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=3Dfast >TAbort- SERR- TAbort- SERR- Reset+ 16bInt+ PostWrite+ 16-bit legacy interface ports at 0001 Kernel driver in use: yenta_cardbus Kernel modules: yenta_socket 03:04.3 Mass storage controller [0180]: Texas Instruments PCIxx21 Integrate= d FlashMedia Controller [104c:8033] Subsystem: Hewlett-Packard Company Device [103c:3085] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Steppi= ng- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=3Dmedium >TAbort- SERR- Kernel driver in use: tifm_7xx1 Kernel modules: tifm_7xx1 03:04.4 SD Host controller [0805]: Texas Instruments PCI6411/6421/6611/6621= /7411/7421/7611/7621 Secure Digital Controller [104c:8034] Subsystem: Hewlett-Packard Company Device [103c:3085] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Steppi= ng- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=3Dmedium >TAbort- SERR- Kernel driver in use: sdhci-pci Kernel modules: sdhci-pci 03:06.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-813= 9/8139C/8139C+ [10ec:8139] (rev 10) Subsystem: Hewlett-Packard Company Device [103c:3085] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Steppi= ng- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=3Dmedium >TAbort- SERR- Kernel driver in use: 8139too Kernel modules: 8139too, 8139cp --===============2627186761150590563== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Stephen Cradock (s-cradock) Date: Sat, 11 Apr 2009 22:12:53 -0000 Message-Id: <20090411221253.14658.57484.malone@potassium.ubuntu.com> I checked, but could only find fglrx-modaliases; I've removed that to be quite sure. The dpkg -l '*fglrx*' call gave a list including the xorg- driver-fglrx and fglrx-driver, but they don't appear to be installed (no version #,flagged pn and un respectively. apt-get remove fglrx* didn't find them. --===============2627186761150590563== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Julien Plissonneau Duquene (julien-plissonneau-duquene) Date: Wed, 15 Apr 2009 02:41:45 -0000 Message-Id: <20090415024146.28385.15205.malone@gangotri.canonical.com> Marking as invalid in compiz: - see #237209 in wine for the desktop effects / wine issue - follow this bug in xserver-xorg-video-ati for the probable driver issue --===============2627186761150590563== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Stephen Cradock (s-cradock) Date: Wed, 15 Apr 2009 04:02:10 -0000 Message-Id: <20090415040211.28385.21015.malone@gangotri.canonical.com> Thanks Julien; there doesn't seem to have been any progress on #237209, does there? I have confirmed that the problem is not related to compiz itself; it happens with metacity set to use compositing. So there is a problem with the Composite extension, that shows itself in Wine for some reason on my system. Interestingly it doesn't show up with Photoshop 7 in wine, as far as I can see, only with the spider solitaire game! --===============2627186761150590563== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Stephen Cradock (s-cradock) Date: Mon, 20 Apr 2009 03:03:33 -0000 Message-Id: <20090420030333.24837.23151.malone@gandwana.canonical.com> I believe I have found the problem. The "empty" xorg.conf results in my case in the video driver (radeon) trying to use exa acceleration, not uxa, which I believe is the new default. Adding the Option "AccelMethod" "XAA" line to the device section removes the problem. I haven't tried explicitly requesting "UXA" instead - maybe that would work. --===============2627186761150590563== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Stephen Cradock (s-cradock) Date: Mon, 20 Apr 2009 03:17:32 -0000 Message-Id: <20090420031732.10875.49716.malone@gangotri.canonical.com> Nope - setting Option "AccelMethod" "UXA" results in the driver defaulting to EXA. It seems I shall have to continue to specify XAA acceleration...... --===============2627186761150590563== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Stephen Cradock (s-cradock) Date: Wed, 22 Apr 2009 04:28:26 -0000 Message-Id: <20090422042826.10875.3685.malone@gangotri.canonical.com> Further checking: comparing Intrepid and Jaunty on same machine - both using radeon OS drivers, most recent versions in each case; Intrepid - specifying either XAA or EXA in Device section of xorg.conf (or leaving no option specified) gives normal behavior in the specific situation I described - Compiz or metacity+compositing as window manager, spider.exe running in Wine. Jaunty - specifiying XAA gives normal behavior as above. Specifying EXA or leaving no option specified gives the faulty screen-redraws originally described. Please let me know if any further information is required/helpful; it is disconcerting to send the info asked for and see the bug still marked Incomplete. --===============2627186761150590563== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Bryce Harrington (bryce) Date: Wed, 13 May 2009 19:42:42 -0000 Message-Id: <20090513194242.9422.4053.malone@gangotri.canonical.com> "UXA" is only applicable for the -intel driver. -ati only supports "XAA" and "EXA". Yes, "EXA" is now the default for -ati starting with Jaunty. Pardon for your discomfort; I simply have been completely focused on intel problems the last couple months. With over 1800 X bugs it is hard to give immediate attention to every bug. I need to learn how Santa Claus does it... --===============2627186761150590563== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Stephen Cradock (s-cradock) Date: Thu, 14 May 2009 05:01:09 -0000 Message-Id: <20090514050109.29968.32430.malone@palladium.canonical.com> Thanks for getting back to this one. I have added the following two Option lines in xorg.conf, and they allow me to use EXA: Section "Device" Identifier "Configured Video Device" Option "MigrationHeuristic" "smart" Option "EXANoComposite" "Yes" EndSection This works in Jaunty and also in Karmic - Wine screen updates complete correctly even when compiz is running. Hope that helps --===============2627186761150590563== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Bryce Harrington (bryce) Date: Sat, 29 Aug 2009 09:36:43 -0000 Message-Id: <20090829093643.3188.50020.malone@potassium.ubuntu.com> [This is an automatic notification.] A new version of the -ati driver is now available in Karmic. This is a significant update to -ati which brings in kernel mode-setting (currently disabled) and scores of fixes for DRI2, EXA, etc. I've posted the new version of this driver to the following PPA, would you mind testing it and seeing if it resolves the bug you reported? https://edge.launchpad.net/~bryceharrington/+archive/ppa/+sourcepub/709908/= +listing- archive-extra If you're not running this release of Ubuntu, you can try booting the Karmic LiveCD and loading the PPA onto it, and then log out/in to restart X. ISOs are available at http://cdimages.ubuntu.com/releases/ After testing Karmic, report back here whether it's still an issue or not, and if it is please post a fresh Xorg.0.log and 'dmesg' output. Note there could be new bugs... please file these as new reports using the command 'ubuntu-bug xorg'. --===============2627186761150590563== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Stephen Cradock (s-cradock) Date: Sat, 29 Aug 2009 14:39:09 -0000 Message-Id: <20090829143909.20978.58071.malone@palladium.canonical.com> Thanks, Bryce. I have installed the amd64 versions from your ppa in a fresh Karmic install, and there are no apparent problems. That's good! However, that particular Karmic install was working fine with the repo versions of the drivers, even without the extra lines I had had to add to xorg.conf in May to get Jaunty working correctly. In fact, as a fresh install, it has no xorg.conf at all, so it was using EXA by default without any options. Will the ppa drivers work in Jaunty? I could try installing them and checking to see if the extra option lines are still needed..... --===============2627186761150590563== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Stephen Cradock (s-cradock) Date: Sat, 29 Aug 2009 16:02:35 -0000 Message-Id: <20090829160235.8034.24820.malone@potassium.ubuntu.com> I have now tried the new drivers with an older Karmic, upgraded from jaunty, that still has xorg.conf and uses it to set the options I mentioned above (EXANoComposite=3Dyes, MigrationHeuristic=3Dsmart). The new versions work whether the options are included or not; the difference is apparent in Xorg.0.log, but does not seem to alter behavior. (Before the new versions, disabling those options gave the behavior I was complaining about). That means the workaround (including options in xorg.conf) is no longer necessary. Thanks! --===============2627186761150590563== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Bryce Harrington (bryce) Date: Sat, 29 Aug 2009 19:12:03 -0000 Message-Id: <20090829191203.29998.95129.malone@gandwana.canonical.com> Hi Stephen, thanks for the swift feedback! To answer some of your questions... I don't know if the ppa drivers would work in Jaunty. Maybe once the driver's been deployed for karmic I'll look into porting it if it doesn't have messy depends. I think the majority of the changed code will have no effect on Jaunty (except to potentially introduce new bugs) but might be some relevant fixes. The no-xorg.conf situation is the new default for Karmic. The code paths are slightly different whether you're using a blank xorg.conf vs. none at all, but that probably doesn't matter here. --===============2627186761150590563== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Stephen Cradock (s-cradock) Date: Sat, 29 Aug 2009 20:22:54 -0000 Message-Id: <20090829202254.31218.70610.malone@gandwana.canonical.com> I checked the possibility of installing in Jaunty - the new driver packages require xserver-xorg-core >=3D 2:1.6.2, but Jaunty only goes as far as 2:1.6.0. So that's out for now. I'm curious as to why and when the Karmic upgrades made it possible for my system to work without EXANoComposite, which clearly happened some time before Alpha4, when I did the fresh install (without xorg.conf). Anyway, it works for me now. --===============2627186761150590563== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Launchpad Janitor (janitor) Date: Wed, 02 Sep 2009 05:05:07 -0000 Message-Id: <20090902050521.31589.64015.malone@cocoplum.canonical.com> This bug was fixed in the package xserver-xorg-video-ati - 1:6.12.99+git20090825.fc74e119-0ubuntu1 --------------- xserver-xorg-video-ati (1:6.12.99+git20090825.fc74e119-0ubuntu1) karmic; ur= gency=3Dlow * Checkout from git 20090825 (master branch) up to commit fc74e1194c980d978667e02c60a29a761a694bde + Adds DRI2 / redirected direct rendering (LP: #96991) + Fix freeze on opengl games (bzflag, alienarena) (when KMS on) (LP: #348450) + Fix intermittent short screen blanking behavior (LP: #310864) + Fix faulty wine screen updates with EXA Compositing (LP: #314205) + Fix screen corruption issues when switching windows (LP: #406731) + Fix SIGSEGV crash in drmCommandNone() (LP: #352567) + Fix smeared/tearing of display on reboot (LP: #367741 [Tormod Volden] * 199_add_git_version_to_log.diff: Log git commit id in RadeonPreInit() * sed -i s/DRI2BufferPtr/DRI2Buffer2Ptr/ src/radeon_dri2.c so it compiles against xserver 1.6.2.+ [Bryce Harrington] * Restore patch system and quilt to build-depends * Drop patches already present upstream + 107_check_unsupported_composit_ops.patch + 108_quirk_agpmode_m6_ali.patch: AGPMode quirk. + 109_quirk_agpmode_m7_intel.patch: AGPMode quirk. + 110_quirk_agpmode_r420_sis.patch: AGPMode quirk. + 111_use_xaa_for_lowmem_or_nodri.patch -- Bryce Harrington Sat, 29 Aug 2009 12:16:53 -0700 --===============2627186761150590563==--