Announcement

Collapse
No announcement yet.

10.4/fglrx in Lucid w/ ATI HD 4xxx or 5xxx

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

  • Panix
    started a topic 10.4/fglrx in Lucid w/ ATI HD 4xxx or 5xxx

    10.4/fglrx in Lucid w/ ATI HD 4xxx or 5xxx

    What's going on? What's the update? I had the impression you could use R700 cards with either FOSS or fglrx driver but does that only apply to certain situations or combinations? In other words, depends on distro, Catalyst and the related versions? I'm confused.

    I read these threads:
    http://www.phoronix.com/forums/showt...708#post120708

    http://ubuntuforums.org/showthread.p...434064&page=21


    There's problems (again)?!?

    That is pretty bad. Can anyone explain the problem(s)? Hmmm....I don't buy that AMD/ATI is dedicated at providing Linux support and devoting much to this support. I read that the support is late and they're catching up. So, if you are building a house and you throw a brick in the mud, you can say you're starting support? Then you throw a few more bricks, some two-by-fours and some tools into the mud and claim you have increasing support and made great progress?!?

    I'm looking at getting an ATI card but I need to know two things:
    1) how to switch between drivers, fglrx and FOSS - sorry, I forget how. Is there a how-to of steps? It sounds like this must be done quite often as you have to test the drivers with a trial and error to see if there's improvement.

    2) "Official Support" - Ubuntu is one of the distros with official support. Are the issues/problems attributable to the newer Catalyst version and the progression in the kernel? If that is part of it, is there other variables? What is the estimated time frame for 'fixing' or solving these bugs and issues? Doesn't ATI/AMD have a timeline that they are trying to achieve? Aren't goals set? I'm just curious. I don't read of any estimations but it might help if I know I can count on something in a month from now, six months from now and so on.

    One more question is about patches. How do you know which patches to use and for what? I don't know if these end up on AMD's ATI site or not. I guess I would just post or ask here for locations of patches and for instructions to install if I have trouble. If no one minds. I hope not.

    I'm considering the HD 4850 and HD 4770 for an all-purpose, cheap card but especially for movies/video (DivX, HD) and streaming video (youtube, video seminars etc.) and stuff like Google Earth. I also would like to use other video and 3D stuff but if it gets bad, I'll boot up Windoze to accomplish tasks until I figure out a solution in Linux.

    The other thing to consider is a Nvidia card, 240 GT or GTS 250 but I really want to go with ATI if they can deliver some needed improvements.

    I'm waiting a bit longer to see if HD 5xxx series of cards obtains better support (no FOSS driver support yet?) but I might not be able to budget for one anyway....

  • Kano
    replied
    The first apps directly show glsl errors. specviewperf is just an extra, but game speed should be compared with all features set to max. When a highend cards with oss is slower than a lowend with fglrx then something is wrong.

    Leave a comment:


  • bridgman
    replied
    With respect, your list might be just the tiniest bit Kano-centric

    Leave a comment:


  • Kano
    replied
    to define a driver at least basically feature complete it has to run these things without any errors and REASONABLE speed compared to fglrx. it does not help when it runs like a dia show.

    a) gl2benchmark
    b) zero ballistics
    c) all common oss games - you find serveral in pts
    d) ut2004, quake4, etqw
    e) specviewperf

    when a card is dropped before then something is wrong with the policy.

    Leave a comment:


  • PsynoKhi0
    replied
    Originally posted by Kano View Post
    Hopefully next time when there are new legacy cards these work directly not 1+ years after last fglrx driver for em.
    Damn... When that happens there will be one less thing for you to farm post count with pointless whining Tough...

    But fear not! There might still be hope in case video acceleration still isn't good enough for your taste! Actually I've written a letter for bridgman to use (licensed under Creative Commons so I won't sue anyone):
    PRIORITY : CRITICAL

    To whom it may concern,
    I hereby pledge the fglrx development team to stop focusing its bug tracking efforts on any topic that might impact our paying business customers, to instead focus on Xv video output - because you know, it's the only thing that counts - for the sake of one guy on the Phoronix forums who almost prouds himself for not having shelled out the money for the only ATI card he owns.
    Sarcasm aside, but right before I stop being polite, how much thought do you put in your posts here? Do you SERIOUSLY think you help push things forward with that attitude?

    Leave a comment:


  • bridgman
    replied
    The open source drivers already exist for 6xx/7xx so not sure where the delay would come from...

    Leave a comment:


  • Kano
    replied
    Hopefully next time when there are new legacy cards these work directly not 1+ years after last fglrx driver for em.

    Leave a comment:


  • bridgman
    replied
    Sure, but one requires developer effort to resolve, one primarily needs user feedback, and the third one just needs people to ask "so, like, why isn't xxx enabled by default ?".

    Leave a comment:


  • Kano
    replied
    Well the result is the same for the normal user. Till i would suggest somebody using oss drivers for ati cards then those will be legacy.

    Leave a comment:


  • bridgman
    replied
    If something is not enabled by default there are usually three possible explanations :

    - there are known problems which are sufficiently serious to keep it disabled for now

    - there are no known serious problems but the devs don't feel there is sufficient user/test coverage to enable by default yet

    - the feature is ready to go but nobody got around to enabling it by default (the devs normally have the WIP features enabled on their systems anyways so it's not actually obvious when a default needs to change)

    Leave a comment:

Working...
X