Announcement

Collapse
No announcement yet.

Catalyst 10.1 and Xorg 7.5 / 1.7.x?

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

  • the-me
    started a topic Catalyst 10.1 and Xorg 7.5 / 1.7.x?

    Catalyst 10.1 and Xorg 7.5 / 1.7.x?

    Hello,

    currently fglrx is RC buggy in Debian unstable, because Xorg 7.5/1.7.x is uploaded and fglrx 9-12 still does not have support for it.

    Does anyone know, if 10-1 will add the missing support?

  • dalingrin
    replied
    Originally posted by Kirurgs View Post
    I may add that I'm running fglrx on mobility radeon 3650 with xserver 1.6.3 and synaptics are there and working.
    So, it's not that You need 1.7 to have synaptics

    P.S. I just can't figure out (didn't try much) how to improve performance with fglrx in KDE4...
    Of course you can run older synaptics driver versions. I have a newer type of synaptics touchpad and need the newer driver for full functionality.

    Leave a comment:


  • energyman
    replied
    Originally posted by Kirurgs View Post
    I may add that I'm running fglrx on mobility radeon 3650 with xserver 1.6.3 and synaptics are there and working.
    So, it's not that You need 1.7 to have synaptics

    P.S. I just can't figure out (didn't try much) how to improve performance with fglrx in KDE4...
    that is X fault. X was broken for Intel graphics. If you want a fast desktop, you need to unbreak X. After doing that, it flies.

    Search for
    xserver-xorg-backclear.patch

    get the sources for xorg-server, patch them, compile them, install them. Very easy with gentoo. If you are using something else - search your distros forums/mailing lists. I am sure somebody has done something about it.

    Leave a comment:


  • krionius
    replied
    Originally posted by Kirurgs View Post
    I may add that I'm running fglrx on mobility radeon 3650 with xserver 1.6.3 and synaptics are there and working.
    So, it's not that You need 1.7 to have synaptics

    P.S. I just can't figure out (didn't try much) how to improve performance with fglrx in KDE4...
    Yeah, pretty much of the functionality is okay with 1.6.3. Synaptics and even its scrolling is working. As things go catalyst is pretty much slowly getting there to 1.7. What will be the case with 1.8 where HAL will be removed?... another couple of years without compatible catalyst?

    Leave a comment:


  • Kirurgs
    replied
    I may add that I'm running fglrx on mobility radeon 3650 with xserver 1.6.3 and synaptics are there and working.
    So, it's not that You need 1.7 to have synaptics

    P.S. I just can't figure out (didn't try much) how to improve performance with fglrx in KDE4...

    Leave a comment:


  • dalingrin
    replied
    Originally posted by energyman View Post
    and what is so important about 1.7 that you must have it? Apart from the version number?

    oh wait.. nothing.
    I need the updated drivers that depend on 1.7 such as input drivers like synaptics. Just because you do not need it doesn't mean others don't.

    Leave a comment:


  • monraaf
    replied
    Yes I know you can use Mplayer with gl output to get tear-free playback. And nothing negative about Mplayer, but it's just a video player, not a solution. I mostly use Miro. It has two backends GStreamer and Xine. The Xine backend chokes on my mkv files, so that's not an option. And the GStreamer backend works great with Xv output but the GStreamer gl output is horribly broken.

    Leave a comment:


  • bridgman
    replied
    What happens when you watch video using gl or gl2 output with fglrx and vsync turned on ? I think there's one player that is hard-wired to Xv but the rest should be able to use GL or Xv interchangeably.

    Leave a comment:


  • monraaf
    replied
    Originally posted by djee View Post
    I've got a Mobility HD 3650. It's been supported since recently, at least officially. Yet older drivers works perfectly well without "official" support. I had OpenGL 3.0, then 3.1, then 3.2 support and was able to use the latest functionality. That was more than expected. Now I'm stuck with OpenGL 2.1 with open source drivers
    Lucky you. My HD 5750 is not yet supported by the open source drivers, so now I'm stuck with fglrx. Cannot even enjoy watching a video. Tear-fest galore!

    If only I could run these drivers side-by-side. The oss driver on my IGP for normal desktop usage and video watching, and fglrx on my HD 5750 for the casual 3D gaming.

    Leave a comment:


  • djee
    replied
    Originally posted by monraaf View Post
    I don't know exactly which community you are speaking out for, but I think a lot of people who bought a HD 5xxxx card, me included, would disagree with this.
    I've got a Mobility HD 3650. It's been supported since recently, at least officially. Yet older drivers works perfectly well without "official" support. I had OpenGL 3.0, then 3.1, then 3.2 support and was able to use the latest functionality. That was more than expected. Now I'm stuck with OpenGL 2.1 with open source drivers, and barely can do 3D. There is support and support. I'm just asking for a driver that works with basic functionalities. As of today on Xorg 7.5 the driver does not even load.

    Originally posted by energyman View Post
    and what is so important about 1.7 that you must have it? Apart from the version number?

    oh wait.. nothing.
    Thanks to read posts instead of being sarcastic:
    Originally posted by djee View Post
    From what I know, given that most distributions are moving to Xorg 7.5/1.7.x and that downgrading is a mess (impossible?) most users will end up being totally unable to use ATI proprietary drivers because of their daily/weekly upgrade.
    Or if you don't understand:
    Originally posted by not.sure View Post
    True. But if something is already old enough to be in Debian testing(!!), and you still say it's 'too new'.. well.. that can't be good. Then even users with a rather conservative upgrade philosophy will be stuck.
    And finally thanks to bridgman for its explanations. Regarding the control panel though I think it's not a reason for delays, since it's totally optional to a working configuration: cf. "Display driver only" downloads for Windows; why not on Linux? I guess there are some other "chunks of functionality" in the core of the driver though...

    Leave a comment:

Working...
X