Compiz blacklist an old ati card, known to work

Bug #139384 reported by erdtmann
16
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

As of the update from 1:0.5.2+git20070912-0ubuntu2 compiz stop working, and the command line returns:

$compiz --replace
Checking for Xgl: not present.
Blacklisted 'ati' driver is in use
aborting and using fallback: /usr/bin/metacity
Aviso do gerenciador de janelas: "" localizado no banco de dados de configurações não é um valor válido para a tecla de atalho "toggle_shaded"

Which suggests my video card is blacklisted. It is known to work, though (it was working before update).

The video card is a ATI Technologies Inc Radeon Mobility U1, which performed pretty well with compiz before.

Tags: compiz gutsy
Revision history for this message
erdtmann (erdtmann) wrote :

Changing the compiz init script in /usr/bin/compiz "solve" the problem... Maybe a more detailed blacklist is needed..

# driver blacklist
#BLACKLIST="nv vga vesa vmware via sis ati"
BLACKLIST="nv vga vesa vmware via sis"

Revision history for this message
Quiketaz (quiketaz) wrote :

thanks erdtmann this was useful for me..

Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

Thank you for your bug report. I'm marking this as confirmed as Quiketaz had the same issue.

Changed in compiz:
importance: Undecided → Medium
status: New → Confirmed
Changed in compiz:
status: Confirmed → Fix Committed
Revision history for this message
Martin Lettner (m.lettner) wrote :

same here, thank you for the hint, everything works again!
(ati mobility radeon 9700/9600)

Revision history for this message
Nemes Ioan Sorin (nemes-sorin) wrote :

today 13 September 2007 - after Compiz upgrade - I have to confirm this bug.

In the name of thousands Ubuntu users with ati drivers I think.

also I have to confirm that this fix is good ..is working for me.

but the problem is -> PLEASE GUYS READ 2 TIMES BEFORE UPLOAD on repositories things that can affect thousands other users [ yes I know Gutsy is not recommended for production - but I mean testing users that are here to test other parts of Gutsy and like to use Compiz ].

Other few upgrades like that and a big part of Ati users will do other useful things with their free time.
some guys are here to test other kind of things - I am sure 80% will not search and apply this solution (change blacklist).

Yes - is not my problem - but I said the truth. I know some peoples testing blender, gimp, webmin ... and other beta programs from this Ubuntu beta - they like Compiz too, they will ask themselfs - why ati driver was good yesterday ..and today is not ?.

so - please take care at the first stage - else the generated traffic regarding the results of a little error from the first stage could be huge - a huge lost energy - for 1 minute extra checking.

also the "blind patching policy" is a lazy, Microsoft genuine technique - should not be followed on any form - they will sue everyone, even sugar babes for that.

;)

sorry is someone is offset. I was too. That's why I do this request for a bit more attention before uploading on repositories.

Peace brothers and sisters.

Revision history for this message
Travis Watkins (amaranth) wrote :

There was an obvious reason for making this change. It was just a little too broad.

Revision history for this message
Alberto Stefani (endymion75) wrote :

I have an old Ati 7000 and I want use compiz with my "only 16 depht"....

thanks to erdtmann!

Bye

--
Alberto

Revision history for this message
Marsu42 (marsu42) wrote :

If some ati cards break compiz and such a change is made, there should be an easy gui option to opt in to using the driver no matter what (my radeon mobility 9000/r250 works just fine). Imho, expecting users to fiddle with default scripts which which thus cannot be auto-upgraded is not an option.

Revision history for this message
Travis Watkins (amaranth) wrote :

We now blacklist the individual cards.

Changed in compiz:
status: Fix Committed → Fix Released
Revision history for this message
erdtmann (erdtmann) wrote :

plz, no troll people (just lemme introduce one more).

I am almost certain that the developer(s) regret such mistake. I personally think that's why we post bugs. If we can found errors more quickly than the developers (they do not have all the hardware they wanted, too!), why not!

I am proud of the developers of compiz, xorg, and ubuntu.

Lean coding is this... quick, dinamic and ... sometimes ... needs the participation of the community. Maybe if they do not made this small mistake they would never implement a complete blacklist.

Anyway, this modification would not be made if this was a stable branch (really, this was not made in feisty, for example).

I test experimental software because of several reasons:
1- bleeding edge
2- help community
3- I can

Glad to help you people, sorry if offended someone,
Erdtmann

Revision history for this message
mon (javiermon-deactivatedaccount) wrote :

Hi

In my case it blacklisted an intel gma x3000. The reason is because video playblack doesn't work. I think the proper solution would be to disable the desktop effects tab, or some other logic different than compiz refusing to start (like by default not starting it at all, but if the user wants compiz, then let him start it). I understand the philosophy of "just works", but I still think this is not an appropriate solution. my 2€

Revision history for this message
Nemes Ioan Sorin (nemes-sorin) wrote : Re: [Bug 139384] Re: Compiz blacklist an old ati card, known to work

kmon,

I talk with those guys because 'ati' driver is used now maybe on 30% of
Gutsy installations. You blacklist ati driver - nest second U just cut
Compiz from 30% of users - This is the problem - SO I request a bit of
"supra" control before upload the code on repositories

kmon wrote:
> Hi
>
> In my case it blacklisted an intel gma x3000. The reason is because
> video playblack doesn't work. I think the proper solution would be to
> disable the desktop effects tab, or some other logic different than
> compiz refusing to start (like by default not starting it at all, but if
> the user wants compiz, then let him start it). I understand the
> philosophy of "just works", but I still think this is not an appropriate
> solution. my 2€
>

Revision history for this message
Sergio Zanchetta (primes2h) wrote :

Using Gutsy daily live cd (26-09-2007) compiz doesn't work with my ati IGP 340M.
In Feisty it works.

Changed in compiz:
status: Fix Released → Confirmed
Revision history for this message
Sergio Zanchetta (primes2h) wrote :
Download full text (3.5 KiB)

UPDATE:

Gutsy Beta Live CD.

No compiz with ATI IGP 340M

01:05.0 0300: 1002:4337 (prog-if 00 [VGA])
        Subsystem: 103c:002a
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B+
        Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 66 (2000ns min), Cache Line Size: 32 bytes
        Interrupt: pin A routed to IRQ 10
        Region 0: Memory at d8000000 (32-bit, prefetchable) [size=128M]
        Region 1: I/O ports at 9000 [size=256]
        Region 2: Memory at d0300000 (32-bit, non-prefetchable) [size=64K]
        [virtual] Expansion ROM at d0320000 [disabled] [size=128K]
        Capabilities: <access denied>

I checked in /usr/bin/compiz but 1002:4337 is not blacklisted.

I tried:
SKIP_CHECKS=yes compiz
in terminal
and this is the output:

Checking for Xgl: not present.
Detected PCI ID for VGA: 01:05.0 0300: 1002:4337 (prog-if 00 [VGA])
Checking for texture_from_pixmap: present.
Checking for non power of two support: present.
Checking for Composite extension: present.
Comparing resolution (1400x1050) to maximum 3D texture size (2048): Passed.
Checking for nVidia: not present.
Checking for FBConfig: present.
Checking for Xgl: not present.
Starting gtk-window-decorator
/usr/bin/compiz.real (core) - Fatal: No GLXFBConfig for default depth, this isn't going to work.
/usr/bin/compiz.real (core) - Error: Failed to manage screen: 0
/usr/bin/compiz.real (core) - Fatal: No manageable screens found on display :0.0

All worked with Feisty and Open Source driver.

My xorg.conf

Section "Files"
EndSection

Section "InputDevice"
 Identifier "Generic Keyboard"
 Driver "kbd"
 Option "CoreKeyboard"
 Option "XkbRules" "xorg"
 Option "XkbModel" "pc105"
 Option "XkbLayout" "it"
EndSection

Section "InputDevice"
 Identifier "Configured Mouse"
 Driver "mouse"
 Option "CorePointer"
 Option "Device" "/dev/input/mice"
 Option "Protocol" "ImPS/2"
 Option "ZAxisMapping" "4 5"
 Option "Emulate3Buttons" "true"
EndSection

Section "InputDevice"
 Identifier "Synaptics Touchpad"
 Driver "synaptics"
 Option "SendCoreEvents" "true"
 Option "Device" "/dev/psaux"
 Option "Protocol" "auto-dev"
 Option "HorizScrollDelta" "0"
EndSection

Section "InputDevice"
 Driver "wacom"
 Identifier "stylus"
 Option "Device" "/dev/input/wacom"
 Option "Type" "stylus"
 Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"
 Driver "wacom"
 Identifier "eraser"
 Option "Device" "/dev/input/wacom"
 Option "Type" "eraser"
 Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"
 Driver "wacom"
 Identifier "cursor"
 Option "Device" "/dev/input/wacom"
 Option "Type" "cursor"
 Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "Device"
 Identifier "ATI Technologies Inc Radeon IGP 330M/340M/350M"
 Driver "ati"
 BusID "PCI:1:5:0"
EndSection

Section "Monitor"
 Identifier "Monitor Generico"
 Option "DPMS"
EndSection

Section "Screen"
 Identifier "Default Screen"
 Device "ATI Technologies Inc Radeon IGP 330M/340M/350M"
 Monitor "Monitor Generico"
 DefaultDepth 24
 SubSec...

Read more...

Revision history for this message
Travis Watkins (amaranth) wrote :

Please do not hijack bugs for new problems. Open a new bug report.

Changed in compiz:
status: Confirmed → Fix Released
Revision history for this message
Sergio Zanchetta (primes2h) wrote :

Sorry, I thought it could be related to this because the behaviour was similar.
After I found that it wasn't blacklisted.

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.