Page 2 of 4 FirstFirst 1234 LastLast
Results 11 to 20 of 37

Thread: Success Stories with 8.42.3 and AIGLX

  1. #11
    Join Date
    Sep 2007
    Posts
    128

    Default

    Yep. I'm still going to use 8.42.3, just without the effects as the driver works smoothly without the effects enabled.

    I've never really complained about ATI/AMD drivers before, and I have no reason to start now either. I'm seeing some progress being made, so I'm happy.

  2. #12
    Join Date
    Sep 2007
    Posts
    54

    Default

    Quote Originally Posted by Uchikoma View Post
    Then we seem to be on opposite ends here -_-
    One finds it usable, the other is unusable!
    Lol...
    Well.. better late than never.. these drivers need a good beating though..

  3. #13
    Join Date
    Apr 2007
    Location
    Bulgaria
    Posts
    269

    Default

    Any Ideas why my desktop looks like this after I ran compiz --replace ?



    Adept appears in the upper left corner out of nowhere and the rest is quite visible.
    Last edited by sundown; 10-26-2007 at 05:58 AM.

  4. #14
    Join Date
    Jul 2007
    Location
    Seoul, Korea
    Posts
    22

    Default

    I got the log message.
    Code:
    cat /var/log/Xorg.0.log | grep AIGLX
    (==) AIGLX enabled
    (WW) AIGLX: 3D driver claims to not support visual 0x23
    (WW) AIGLX: 3D driver claims to not support visual 0x24
    (WW) AIGLX: 3D driver claims to not support visual 0x25
    (WW) AIGLX: 3D driver claims to not support visual 0x26
    (WW) AIGLX: 3D driver claims to not support visual 0x27
    (WW) AIGLX: 3D driver claims to not support visual 0x28
    (WW) AIGLX: 3D driver claims to not support visual 0x29
    (WW) AIGLX: 3D driver claims to not support visual 0x2a
    (WW) AIGLX: 3D driver claims to not support visual 0x2b
    (WW) AIGLX: 3D driver claims to not support visual 0x2c
    (WW) AIGLX: 3D driver claims to not support visual 0x2d
    (WW) AIGLX: 3D driver claims to not support visual 0x2e
    (WW) AIGLX: 3D driver claims to not support visual 0x2f
    (WW) AIGLX: 3D driver claims to not support visual 0x30
    (WW) AIGLX: 3D driver claims to not support visual 0x31
    (WW) AIGLX: 3D driver claims to not support visual 0x32
    (WW) AIGLX: 3D driver claims to not support visual 0x33
    (WW) AIGLX: 3D driver claims to not support visual 0x34
    (WW) AIGLX: 3D driver claims to not support visual 0x35
    (WW) AIGLX: 3D driver claims to not support visual 0x36
    (WW) AIGLX: 3D driver claims to not support visual 0x37
    (WW) AIGLX: 3D driver claims to not support visual 0x38
    (WW) AIGLX: 3D driver claims to not support visual 0x39
    (WW) AIGLX: 3D driver claims to not support visual 0x3a
    (WW) AIGLX: 3D driver claims to not support visual 0x3b
    (WW) AIGLX: 3D driver claims to not support visual 0x3c
    (WW) AIGLX: 3D driver claims to not support visual 0x3d
    (WW) AIGLX: 3D driver claims to not support visual 0x3e
    (WW) AIGLX: 3D driver claims to not support visual 0x3f
    (WW) AIGLX: 3D driver claims to not support visual 0x40
    (WW) AIGLX: 3D driver claims to not support visual 0x41
    (WW) AIGLX: 3D driver claims to not support visual 0x42
    (WW) AIGLX: 3D driver claims to not support visual 0x43
    (WW) AIGLX: 3D driver claims to not support visual 0x44
    (WW) AIGLX: 3D driver claims to not support visual 0x45
    (WW) AIGLX: 3D driver claims to not support visual 0x46
    (WW) AIGLX: 3D driver claims to not support visual 0x47
    (WW) AIGLX: 3D driver claims to not support visual 0x48
    (WW) AIGLX: 3D driver claims to not support visual 0x49
    (WW) AIGLX: 3D driver claims to not support visual 0x4a
    (WW) AIGLX: 3D driver claims to not support visual 0x4b
    (WW) AIGLX: 3D driver claims to not support visual 0x4c
    (WW) AIGLX: 3D driver claims to not support visual 0x4d
    (WW) AIGLX: 3D driver claims to not support visual 0x4e
    (WW) AIGLX: 3D driver claims to not support visual 0x4f
    (WW) AIGLX: 3D driver claims to not support visual 0x50
    (WW) AIGLX: 3D driver claims to not support visual 0x51
    (WW) AIGLX: 3D driver claims to not support visual 0x52
    (WW) AIGLX: 3D driver claims to not support visual 0x53
    (WW) AIGLX: 3D driver claims to not support visual 0x54
    (WW) AIGLX: 3D driver claims to not support visual 0x55
    (WW) AIGLX: 3D driver claims to not support visual 0x56
    (WW) AIGLX: 3D driver claims to not support visual 0x57
    (WW) AIGLX: 3D driver claims to not support visual 0x58
    (WW) AIGLX: 3D driver claims to not support visual 0x59
    (WW) AIGLX: 3D driver claims to not support visual 0x5a
    (WW) AIGLX: 3D driver claims to not support visual 0x5b
    (WW) AIGLX: 3D driver claims to not support visual 0x5c
    (WW) AIGLX: 3D driver claims to not support visual 0x5d
    (WW) AIGLX: 3D driver claims to not support visual 0x5e
    (WW) AIGLX: 3D driver claims to not support visual 0x5f
    (WW) AIGLX: 3D driver claims to not support visual 0x60
    (WW) AIGLX: 3D driver claims to not support visual 0x61
    (WW) AIGLX: 3D driver claims to not support visual 0x62
    (WW) AIGLX: 3D driver claims to not support visual 0x63
    (WW) AIGLX: 3D driver claims to not support visual 0x64
    (WW) AIGLX: 3D driver claims to not support visual 0x65
    (WW) AIGLX: 3D driver claims to not support visual 0x66
    (WW) AIGLX: 3D driver claims to not support visual 0x67
    (WW) AIGLX: 3D driver claims to not support visual 0x68
    (WW) AIGLX: 3D driver claims to not support visual 0x69
    (WW) AIGLX: 3D driver claims to not support visual 0x6a
    (WW) AIGLX: 3D driver claims to not support visual 0x6b
    (WW) AIGLX: 3D driver claims to not support visual 0x6c
    (WW) AIGLX: 3D driver claims to not support visual 0x6d
    (WW) AIGLX: 3D driver claims to not support visual 0x6e
    (WW) AIGLX: 3D driver claims to not support visual 0x6f
    (WW) AIGLX: 3D driver claims to not support visual 0x70
    (WW) AIGLX: 3D driver claims to not support visual 0x71
    (WW) AIGLX: 3D driver claims to not support visual 0x72
    (II) AIGLX: Loaded and initialized /usr/lib64/dri/fglrx_dri.so
    Code:
    fglrxinfo 
    display: :0.0  screen: 0
    OpenGL vendor string: ATI Technologies Inc.
    OpenGL renderer string: ATI RADEON 9600 Series
    OpenGL version string: 2.0.6958 Release
    AIGLX of my machine is correctly working or not?

  5. #15
    Join Date
    Oct 2007
    Posts
    8

    Default

    i have been successful so far. aiglx works!

    i am under debian sid and just followed the howto at http://sonique54.free.fr/compiz-fusi...iz-fusion.html.

    plus: i added the following lines to my xorg.conf:
    Code:
    Section "Extensions"
             Option      "Composite" "1"
    EndSection
    plus: i did a "vim $(which compiz-manager)" and added "fglrx" to the whitelist at about line 54 of that file...


    a few more notes:
    - i am running debian sid amd64
    - i have a radeon HD 2600 pro
    - i use xfce
    - i am using a 2.6.22.9 vanilla kernel
    - and: yes, my firefox is usable with aiglx enabled.. but: aiglx seems to be a little slow.
    Last edited by stealth; 10-26-2007 at 07:15 PM.

  6. #16
    Join Date
    Oct 2007
    Posts
    1

    Default Mixed Bag

    Its been a mixed bag for me. The card is Asus Eax 1950Pro PCIE. Previously running smoothly with 8.36 and XGL on Feisty.

    With the new driver, Compiz works with AIGLX. But that's about it. I have the crazy flickering with compiz on, but it goes away when you switch compiz off so that's a sucess. Even with Compiz off the machine feels a bit heavy, sluggish, not as light and responsive as with 8.36. Lots of AIGLX error messages in Xorg and a couple of kernel errors on logoff. However this is a success thread and I think its 60% there. Not a total failure, its working just not as smooth as it should.

    However I am not going back to XGL or a previous driver, too much hassle, will wait this through until ATI delivers.

  7. #17
    Join Date
    Oct 2007
    Posts
    8

    Default

    I have a DellE1505 (same as the 6400, dunno what the diff is though) also with an ATI Mobility X1400 and everything works fine for me.

    I don't know about videos b/c I haven't tried playing any yet. But with effects enabled, I'm not getting any problems in firefox.

    This is all on a squeaky fresh install of 7.10 as well. It took me a few tries to actually get the driver installed and working correctly.

    Will report back on the video later.

    Off subject, but I'm curious if hypermemory even works with linux???

    ---------edit---------

    Ok, I tried a video out and yes it flickers. And I actually tried scrolling in firefox with compiz disabled and yeah its much faster that way. But in the end, I doubt if I'll be watching videos on the laptop. I can already say that web videos like on youtube work fine though. And also the firefox problem isn:t so bad. meh.
    Last edited by b4sakenxx; 10-27-2007 at 10:47 AM.

  8. #18
    Join Date
    Oct 2007
    Posts
    17

    Default

    Without the compiz effects everything is fine.

    I run a Xinerama desktop with 3D accleration. Bevor this driver release I did not had the Xinerama extension and 3D accleration together.

    So, very nice new features in the driver version 8.42.3

  9. #19
    Join Date
    Sep 2007
    Posts
    27

    Default

    for me everything is fine ,

    In fact just after the installation i complain about those driver because i was waiting a lot for it and on the firsts attempts , compiz did not work , But after digging , i found this topic : http://bgoglin.livejournal.com/11253.html

    and now , i have no problem with compiz neither with Firefox.

    For the VIdeo flickering , it is the same on my computer as for the others , but on another comnputer with an intel card , i have the same problems , i think it is more a compiz related problem.

    My card : Ati mobility radeon hd 2400
    Os : DEbian Testing / compiz 0.6.2

  10. #20
    Join Date
    Jun 2007
    Posts
    406

    Default

    xpress200m xorg7.2, xorg-server-1.3, kernel 2.6.22-r9, gentoo i run beryl at 700-800fps, while i run normal kwin at the same fps. after i forced the xvoverlay, and set the XAANoOffscreenPixmaps "true" i had a drop of kwin from 1800fps to 700-800 but the tearing and the other artifacts disappeared and i could use beryl with no speed loss. if you look at how much i was losing without these options (from 1800 to about 500-600 fps) and now that i have about the same fps i really think that this is not bad.
    maybe for using this driver well users should use it on xorg-7.2, xserver-1.3 and kernel 2.6.22-r9. it seems that using these settings makes it run without particular problems.
    as for compiz, i couldn't use it. i had about 100-200fps when running compiz and no window decorator working. so i gave up. maybe that is due to the unprecised bug with compiz mentioned when was released.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •