Announcement

Collapse
No announcement yet.

Drivers for linux are rubbish

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

  • ahhyes
    started a topic Drivers for linux are rubbish

    Drivers for linux are rubbish

    Seriously, whats up with AMD? I am always able to install nvidia's drivers fine, never a problem. With with the ATI drivers, constant fglrx build issues, kernel incompatibilities:

    So here we go again, I download ati-driver-installer-10-5-x86.x86_64.run after upgrading my kernel to 2.6.34, surprise surprise, ATI *still* hasn't realized that in the kernel source tree include/linux/utsrelease.h (and a number of other files have been moved to ../generated

    this change occurred quite a while ago in the linux kernel source tree, but AMD don't seem to give a toss, of course the compilation of fglrx fails because its looking for these files in the wrong place. So after spending time and creating symlinks in the source tree to work around AMD's stupidity, fglrx still wont build.

    make[2]: Entering directory `/usr/src/linux-2.6.34'
    CC [M] /usr/src/fglrx-8.732/2.6.x/firegl_public.o
    In file included from /usr/src/fglrx-8.732/2.6.x/firegl_public.c:443:
    /usr/src/fglrx-8.732/2.6.x/drm_proc.h: In function ?FGLDRM__vma_info?:
    /usr/src/fglrx-8.732/2.6.x/drm_proc.h:497: warning: format ?%08lx? expects type ?long unsigned int?, but argument 5 has type ?phys_addr_t?
    /usr/src/fglrx-8.732/2.6.x/firegl_public.c: In function ?KCL_SetPageCache_Array?:
    /usr/src/fglrx-8.732/2.6.x/firegl_public.c:1316: warning: passing argument 1 of ?KCL_ConvertPageToKernelAddress? makes pointer from integer without a cast
    /usr/src/fglrx-8.732/2.6.x/firegl_public.c: In function ?__ke__cmpxchg?:
    /usr/src/fglrx-8.732/2.6.x/firegl_public.c:1473: error: variable or field ?__ret? declared void
    /usr/src/fglrx-8.732/2.6.x/firegl_public.c:1473: error: variable or field ?__old? declared void
    /usr/src/fglrx-8.732/2.6.x/firegl_public.c:1473: error: variable or field ?__new? declared void
    /usr/src/fglrx-8.732/2.6.x/firegl_public.c: In function ?KCL_MapPageToPfn?:
    /usr/src/fglrx-8.732/2.6.x/firegl_public.c:1615: warning: unused variable ?bus_addr?
    make[3]: *** [/usr/src/fglrx-8.732/2.6.x/firegl_public.o] Error 1
    make[2]: *** [_module_/usr/src/fglrx-8.732/2.6.x] Error 2
    make[2]: Leaving directory `/usr/src/linux-2.6.34'
    make[1]: *** [kmod_build] Error 2
    make[1]: Leaving directory `/usr/src/fglrx-8.732/2.6.x'
    build failed with return value 2
    make: *** [all] Error 1
    PATHETIC.

    The other thing is also, if you do not set MALLOC_CHECK_=0 before running the installer, the installer crashes during the fglrx build.

    Why do they make it so difficult? I've been from kernel 2.6.32, .33, .34 and never had an nvidia driver install go bad. It just always seems to be with ATI i am forever stuffing around to get their drivers to install.

    So, is there another patch to fix this fglrx issue with 2.6.34 kernels?

    Sorry for the rant, but I am so sick to death of constantly running into the same issues with ATI drivers on linux.

  • ahhyes
    replied
    thank you Kano

    kano's script has fixed it. I missed that post on the first page.

    Thanks Kano, you are a god *bows*

    Leave a comment:


  • ahhyes
    replied
    wow

    Well this thread has spiraled way off course since I started it.

    Ok, so where can I find ALL the WORKING patches I need to install the ati drivers for linux (using the ATI installer), against my 2.6.34 system? As I said in the original OP, I have had this issue with using pretty much any kernel beyond 2.6.28 and have had to scavenge around the net for patches.

    I don't feel like having to wad through 1000 pages of posts. Perhaps someone should start a thread on this, make it sticky, and have it purely for patches only, so they don't get lost in the thousands of posts.

    Leave a comment:


  • hotnikkelz
    replied
    Ahh, it's all clear now, thanx much. I'm on ubuntu right now using ubuntu's open source drivers, lag free. When the new drivers come out, i'll give them a spin. I haven't even come close to diving into Wine yet, i'm still trying to work out the indicator applet. It's more complicated than it seems on the surface, i haven't grasped its power. One step at a a time eh.
    I must thank you all again for taking the time to answer all my questions, and so quickly too.

    Leave a comment:


  • bridgman
    replied
    Yes, but when I made that post they were soon-to-be-released, not recently-released

    Leave a comment:


  • SolidSteel144
    replied
    How about the recently released 10.6 drivers? Isn't the new 2D acceleration feature complete-ish?

    Leave a comment:


  • bridgman
    replied
    "fglrx" is the internal name for the Catalyst Linux Edition proprietary driver, and the string appears in a number of file names and messages. Just two names for the same thing.

    Note that the fglrx driver installed by Ubuntu is slightly different from the final 10.4 driver available at amd.com - we gave the Ubuntu folks a pre-release version of what would eventually become the 10.4 driver in order to meet their internal schedules. All three versions (Ubuntu, final 10.4 and 10.5) use XAA by default, and the XAA code is the same other than bug fixes, so unless you are forcing on the unreleased "new 2D" code you should see the same behaviour on all three.

    If you force the unreleased "new 2D" code on (recognizing that it is *not* ready for normal use yet) then 10.5 is probably quite a bit better than 10.4, but still not good enough for us to enable it by default.

    Leave a comment:


  • pingufunkybeat
    replied
    Just to clear up. There are two drivers for your card currently available and being developed:

    FGLRX = Catalyst = proprietary = closed-source = ATi official driver (that's the 10.5 thing you had to download)

    and

    Open Source driver = kernel + Mesa + radeon = "radeon driver" = free driver (that's the thing that is installed on Ubuntu by default)

    If you are going to be playing lots of WINE stuff, you'll need the proprietary drivers. They are very optimized and have latest whizbang, but as you've seen, they have their issues with 2d and video.

    For most regular use (including desktop effects and some native gaming), the open source drivers are a good choice.

    Leave a comment:


  • hotnikkelz
    replied
    ohhh ok, i understand much more now *phew*
    Thanks you guys. Must have taken you guys a while to learn the ins and outs of how these things work lol, i'm only now tinkering with linux since it's going to take over the world

    I have one final question i believe. If fglrx (which is basically compiled 10.4 drivers right?) whose 2D accel uses XAA and thus is unable to accelerate the download, what does 10.5's 2D accel code use and do you know how it differs with the even newer 2D accel code in 10.6.
    And yes i will definitely go with option B, time flies fast, I'll be trying to learn the basics of ubuntu during that time

    Leave a comment:


  • bridgman
    replied
    Originally posted by hotnikkelz View Post
    Is 2D acceleration code DISABLED by default in 10.5? If that's the case...why? and wouldn't another solution to my problem be to just edit something that enables 2D acceleration?

    So, XAA controls 2D acceleration, and X server is tied in with that (in layman terms), which is why a prepatched x server will solve my problem as well right?

    And where did fglxr go 'wrong' where all this is concerned?
    2D acceleration is enabled by default, but it uses the standard XAA interface which does not happen to accelerate the specific download operation required when running an unpatched X server with a compositor and unminimizing a window etc...

    Patching the X server eliminates the download when unminimizing -- the download is normally wasted anyways because the downloaded data usually gets over-written immediately after the transfer. Unfortunately the patch has been gone for a year or so and a few more programs have started relying on the downloaded data. As an example, if you are running newer versions of KDE you will see small black squares briefly appearing when running with a patched X server, corresponding to areas where the downloaded data would have been used.

    The only thing fglrx does "wrong" here is that it uses the XAA interface for acceleration. The upcoming 2D acceleration code replaces the XAA standard with a new and larger set of functions, including one which accelerates the download operation.

    As others have posted, the currently shipping drivers include in-development versions of the new acceleration code, but since the new code has not been completed we disable it by default. Future versions of the driver (probably this month's release) will include newer versions of the code and at some point it will be considered ready to enable by default. Until then your options are (a) use a patched X server, (b) use the open source drivers which are enabled by default when installing Lucid, (c) enable the work-in-process accel code in the 10.5 driver and see how it works on your system, (d) live with the delays.

    Given that the new accel code is likely to appear in the next regular driver release I would probably go with option (b).

    Leave a comment:

Working...
X