Announcement

Collapse
No announcement yet.

AMD Catalyst For Linux On The "Blacklist Of Junk"

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • mibo
    replied
    Will this Catalyst hate of Michael Larabel never end? Will there be a time when he is bored of that ATI/AMD bashing?

    I mean, you can find a person that hates a specific software - for every software. But, only Catalyst haters will make it on the Phoronix front page.
    I, for example could hate the nvidia driver as it triggered Kwin slow downs in my notebook for years. There were many complaints in the nvnews forum and Kwin coder Martin was really annoyed of the nvidia-black-box...

    Leave a comment:


  • barkas
    replied
    Originally posted by .CME. View Post
    fglrx only shows "Advanced Micro Devices, Inc." when it detects glxinfo, take a look at /etc/ati/atiogl.xml
    Code:
            <!-- glxinfo -->
            <profile exename="glxinfo">
                    <OpenGLCapsEx>0x02000000</OpenGLCapsEx>
            </profile>
    That sort of negates any usefulness glxinfo may have. That hack is, indeed, unbelievably stupid.

    Leave a comment:


  • .CME.
    replied
    fglrx only shows "Advanced Micro Devices, Inc." when it detects glxinfo, take a look at /etc/ati/atiogl.xml
    Code:
            <!-- glxinfo -->
            <profile exename="glxinfo">
                    <OpenGLCapsEx>0x02000000</OpenGLCapsEx>
            </profile>

    Leave a comment:


  • GreatEmerald
    replied
    Originally posted by makomk View Post
    Not terribly surprising. Wine doesn't have to test for the NVidia vendor string before enabling NVidia-specific fixes because they develop for NVidia hardware by default and then fix up anything that doesn't work on AMD later.
    No. This has nothing to do with Wine and everything to do with crappy Windows programs.

    Leave a comment:


  • PsynoKhi0
    replied
    Originally posted by molecule-eye View Post
    One anecdote from one guy who ran into one stupid problem years ago does not make for an interesting story. It is also not evidence that the Catalyst drivers are, today on modern hardware, junk.
    Though it makes for quite a few ad hits from the sensationalism and the ensuing "yeah fglrx is teh sux" rally in the forum... Mission accomplished.

    Leave a comment:


  • molecule-eye
    replied
    One anecdote from one guy who ran into one stupid problem years ago does not make for an interesting story. It is also not evidence that the Catalyst drivers are, today on modern hardware, junk.

    Leave a comment:


  • makomk
    replied
    Originally posted by Vi0L0 View Post
    diff -uN glxinfo wine_glxinfo:

    -OpenGL vendor string: Advanced Micro Devices, Inc.
    +OpenGL vendor string: ATI Technologies Inc.
    Not terribly surprising. Wine doesn't have to test for the NVidia vendor string before enabling NVidia-specific fixes because they develop for NVidia hardware by default and then fix up anything that doesn't work on AMD later.

    Leave a comment:


  • dcc24
    replied
    Originally posted by bleubugs View Post
    dcc24: do you write a Composite Manager ? My guess is no as if you were, you would just agree.
    So what? That developer might be right in saying that, but it still doesn't make this *thing* an actual article with any level of journalistic integrity.

    Leave a comment:


  • GreatEmerald
    replied
    Originally posted by disgrace View Post
    they cant do it on windows or they will break a lot of stuff. they are relying on the process name since a long time even on windows, take a look at the file atiogl.xml . if you know a better way to detect a specific apps tell them.
    How about a compatibility checkbox in CCC?

    Leave a comment:


  • disgrace
    replied
    Originally posted by barkas View Post
    Nope. It's just wrong. A driver should never ever do something depending on process name. Possibly they should report ATI in any case - they obviously did not dare to change it on windows, why should they do it for linux?
    they cant do it on windows or they will break a lot of stuff. they are relying on the process name since a long time even on windows, take a look at the file atiogl.xml . if you know a better way to detect a specific apps tell them.

    Leave a comment:

Working...
X