Page 3 of 3 FirstFirst 123
Results 21 to 28 of 28

Thread: AMD Catalyst 13.3 Beta 3 Available For Linux Users

  1. #21
    Join Date
    Dec 2012
    Location
    Persia
    Posts
    5

    Default

    I have a question, what's difference between driver that support kernel version x.y and driver that patched to support kernel version x.y?

  2. #22
    Join Date
    Nov 2008
    Location
    Old Europe
    Posts
    932

    Default

    Quote Originally Posted by Shabahang View Post
    I have a question, what's difference between driver that support kernel version x.y and driver that patched to support kernel version x.y?
    A patch only changes the glue code to match the kernel driver API.
    If AMD releases a driver which supports a new kernel release they can, in principle,
    make further changes to the driver code to optimise it for the new kernel.

  3. #23
    Join Date
    Aug 2007
    Posts
    6,641

    Default

    You live in a fully unrealistic world. The fglrx kernel module is definitely not "optimized" for a new kernel, only build fixes have been applied, thats common practice. In this case you can look at the fix from AMD:

    http://kanotix.com/files/fix/fglrx.w...8-support.diff

    And what Debian used:

    http://kanotix.com/files/fix/fglrx.w...linux-3.7.diff
    http://kanotix.com/files/fix/fglrx.w...linux-3.8.diff

    What you see that it is 1:1 the same, just an extra tiny modification thats not needed for Debian because the module build is done differently without that script. That code is standard, nothing that you have to think of long time.

  4. #24
    Join Date
    Nov 2008
    Location
    Old Europe
    Posts
    932

    Default

    Quote Originally Posted by Kano View Post
    You live in a fully unrealistic world. The fglrx kernel module is definitely not "optimized" for a new kernel ...
    I didn't say that.

  5. #25
    Join Date
    Jul 2012
    Posts
    148

    Default

    Quote Originally Posted by n3wu53r View Post
    Correction: Serious Sam 3 is not a Valve game, nor does it use the Source engine. The game is developed by Croteam and uses their in-house engine.
    Team Fortress 2 is from Valve and does use the source engine.
    +1
    Michael, please fix your article!

  6. #26
    Join Date
    Jan 2008
    Posts
    38

    Default Still doing it wrong.

    Quote Originally Posted by mark45 View Post
    Linux 3.7 & 3.8 now supported - what does it take to support a new Linux kernel? I mean Linux is backwards compatible, what's the deal exactly?
    LOL - I had the previous driver on my laptop and when I installed the 3.8.4 kernel, dkms failed during build and said "Unsupported kernel". AMD your still doing it wrong.

    On the upside this fglrx driver works

  7. #27
    Join Date
    Sep 2007
    Location
    Athens-Hellas
    Posts
    255

    Default 2D KDE Performance

    For anyone that has 2D problems with fglrx-catalyst at KDE 4.X environment try using Raster as 2D rendering mode... For me it showed great difference than native Xrender!
    System Settings -> Desktop effects -> Advanced Tab -> Qt Graphic System that's for KDE 4.10 and 4.9 I think, for older versions it was a separate app in the system settings you had to install manually, Qt 2D something it was called!
    Also at KDE 4.10 openGL ES 2 interfaces work so use them for Kwin...

  8. #28
    Join Date
    Oct 2009
    Location
    Brisbane, Queensland, Australia
    Posts
    154

    Default

    Quote Originally Posted by Kano View Post
    Now to Serious Sam 3, there is absolutely no working fix, the lastest public beta from SS3 shows the menu correct, but the first logo is with artefacts. When you don't use gfxRestart() while the menu is shown (or via pressing Alt+Enter twice) then serveral textures like trees flicker in the level you start then.
    The bug fixed in Catalyst 13.3 Beta 3 was:

    [370253]: Serious Sam 3 - Color of Objects turning into be red when enabling separate shader object

    It sounds as if you are seeing separate issues. I do agree though that it is disappointing that it's not working right.

Posting Permissions

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