Page 4 of 37 FirstFirst ... 2345614 ... LastLast
Results 31 to 40 of 366

Thread: AMD Dropping R300-R500 Support In Catalyst Driver

  1. #31
    Join Date
    Sep 2007
    Posts
    158

    Default

    Ok, so:
    - with all the architecture changes showing up, proprietary drivers have a tough time ahead, and unless AMD spent big time engineering on these old cards ...
    - this will create more demand for the open source driver, which will recieve more testing and attention (Gallium has R300-R500 support under development right now)
    - in concrete terms, you still get about 6 more months with the closed source driver, assuming you update your distro often
    - radeonhd is a failed effort from day one (started behind closed doors by Novell; what a great plan ...), so would it be possible to stop mentioning it ?

    But useless whining is good, this is the Internet, yah

  2. #32
    Join Date
    Apr 2007
    Location
    Bulgaria
    Posts
    269

    Default

    It's funny. In a way they are stopping the support of something that wasn't quite supported in the first place. That stupid driver was always half-chewed, half something else and now they are throwing it up on us. That's right, that diriver was always a vomit.

  3. #33
    Join Date
    Jan 2008
    Location
    South Africa
    Posts
    235

    Default

    It isn't made very clear.

    Will the last drivers with R300-R500 support X.Org 1.6?

    If no:
    - That sux

    If yes:
    - That sux too, (although less)
    - What if the last drivers has a problem which will essentially stop X.Org 1.6 from working? - No more support, means that we won't ever get it working.

    So, I would like to find out the following: (Michael?)
    Will the last drivers support X.Org 1.6?
    If so, is there a chance of at least one more driver to fix any significant X.Org 1.6 compatibility bugs that may arise?

  4. #34

    Default

    Quote Originally Posted by grigi View Post
    So, I would like to find out the following: (Michael?)
    Will the last drivers support X.Org 1.6?
    If so, is there a chance of at least one more driver to fix any significant X.Org 1.6 compatibility bugs that may arise?
    AMD doesn't know the answer to it at this time. There's a chance the X Server 1.6 support may be back-ported, but I would not hold my breath. Don't count on any more legacy driver releases to "clean up" the support.

  5. #35
    Join Date
    Jan 2008
    Location
    South Africa
    Posts
    235

    Default

    Thanks for the answer. It seems to call for a "wait and see" policy...
    You will at least post it as as news item when it is confirmed either way?

  6. #36

    Default

    Quote Originally Posted by grigi View Post
    Thanks for the answer. It seems to call for a "wait and see" policy...
    You will at least post it as as news item when it is confirmed either way?
    Sure thing.

  7. #37
    Join Date
    Jul 2008
    Location
    Greece
    Posts
    3,801

    Default

    This has no real consequence on Windows since new Catalyst drivers didn't add anything new to X1000 cards and below. Quite the contrary; people were still running 7.x versions on those cards because those worked best (faster, more stable). I did too on my old X1950XT. Catalyst 7.11 was faster than anything newer and rock stable.

    On Linux, however, this screws people. The Linux driver is bugged like hell and people were always waiting for new Catalyst releases to fix them, contrary to Windows where nothing really new was added and everything was working 100% in old drivers.

    But, this has no consequence to AMD. Even if Linux people go NVidia now, AMD isn't affected much by it. They don't make money out of Linux people. Why should they consider us if there's no monetary gain for them in doing so? To sell 1 or 2 cards to Linux people while they sell 100 to Windows ones?

    That's how it is. We don't have to like it, but that's the situation.

  8. #38
    Join Date
    Dec 2008
    Location
    Poland
    Posts
    119

    Thumbs down

    In my point of view ATI can't manage to fix essential bugs with R300/R400/R500 so they drooped support for older Hardware.
    Their developers are saying:
    We aren't able to write good graphic driver and we should additional support something that we haven't ever properly supported? Let us make life easier and drop support for this Hardware, the buyers of R300/R400/R500 will understand it for sure.

  9. #39
    Join Date
    Jul 2008
    Location
    Greece
    Posts
    3,801

    Default

    Quote Originally Posted by NSLW View Post
    the buyers of R300/R400/R500 will understand it for sure.
    Nope. It's more I like I wrote above: "who cares about the buyers of those since there's no income there."

  10. #40
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,543

    Default

    Quote Originally Posted by Jon4u!SvenJonsson View Post
    The current opensource driver (xf-86-video-ati and the mesa stack) is nowhere near fglrx in terms of stability and features (at least for me). 3D using the opensource drivers (eg for playing older games like doom3 or nwn) results in lockups or graphical corruption. Features like powerplay are not supported. Using the opensource-driver on my x700 results in white-screen on modeswitch / vt-switch. Using the opensource-driver on my x700 and my x800 with kde-4.2 results in lockups when desktop-effects are enabled.

    I know that this is not amd's fault, and i also know that the opensource-developers work hard to improve the situation, but current situation is not good for owners of r400 based cards. There are too few opensource-developers working on the drivers, and the current focus seems to be more on bringing new features to the driver, then fixing bugs, resulting in an total loss of stability. The modeswitch for example worked great around xf-video-ati-6.8.0, but now with everyone switching to kms i frequently get a white-screen on my laptop. 3D worked somewhat (at least i could play nwn) until mesa-7.0, but now even starting glxgears results in an hardlock on my x800.
    Jon, most of the current open source work is going into exactly the areas you mentioned, and the "new features" you're talking about are aimed primarily at those two areas -- kernel modesetting to provide a generic solution for system-specific VT-switch and suspend/resume issues, and rewriting the bottom end of the 3D stack to deal with ongoing performance and stability issues.

    Gallium3D work for your GPUs has moved into Mesa master (rather than being a branch-off-a-branch, and I expect power management work will resume once some of the other projects rewriting the kernel driver settle down a bit. Bottom line, however, is that the level of activity on the open source drivers is higher than it has ever been before.

Posting Permissions

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