Announcement

Collapse
No announcement yet.

AMD Catalyst 10.1 Driver For Linux Released

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

  • kernelOfTruth
    replied
    any patch or hint how to compile 10.1 on Gentoo ?

    I updated the ebuild according to the patch in following bug:

    http://bugs.gentoo.org/show_bug.cgi?id=297322

    unfortunately the patch mentioned in the bug: 2.6.32-9.11-fix_compilation.patch

    or

    2.6.32-9.12-fix_compilation.patch (in renamed form)

    doesn't seem to work anymore or I'm running into another kind of problem:

    CC [M] /var/tmp/portage/x11-drivers/ati-drivers-10.1/work/common/lib/modules/fglrx/build_mod/2.6.x/firegl_public.o
    CC [M] /var/tmp/portage/x11-drivers/ati-drivers-10.1/work/common/lib/modules/fglrx/build_mod/2.6.x/kcl_acpi.o
    In file included from /var/tmp/portage/x11-drivers/ati-drivers-10.1/work/common/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:449:
    /var/tmp/portage/x11-drivers/ati-drivers-10.1/work/common/lib/modules/fglrx/build_mod/2.6.x/drm_proc.h: In function ?FGLDRM__vma_info?:
    /var/tmp/portage/x11-drivers/ati-drivers-10.1/work/common/lib/modules/fglrx/build_mod/2.6.x/drm_proc.h:497: warning: format ?%08lx? expects type ?long unsigned int?, but argument 5 has type ?phys_addr_t?
    /var/tmp/portage/x11-drivers/ati-drivers-10.1/work/common/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c: In function ?KCL_SetPageCache_Array?:
    /var/tmp/portage/x11-drivers/ati-drivers-10.1/work/common/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:1322: warning: passing argument 1 of ?KCL_ConvertPageToKernelAddress? makes pointer from integer without a cast
    /var/tmp/portage/x11-drivers/ati-drivers-10.1/work/common/lib/modules/fglrx/build_mod/2.6.x/firegl_public.h:337: note: expected ?void *? but argument is of type ?long unsigned int?
    /var/tmp/portage/x11-drivers/ati-drivers-10.1/work/common/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c: In function ?__ke__cmpxchg?:
    /var/tmp/portage/x11-drivers/ati-drivers-10.1/work/common/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:1479: error: variable or field ?__ret? declared void
    /var/tmp/portage/x11-drivers/ati-drivers-10.1/work/common/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:1479: error: variable or field ?__old? declared void
    /var/tmp/portage/x11-drivers/ati-drivers-10.1/work/common/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:1479: error: variable or field ?__new? declared void
    /var/tmp/portage/x11-drivers/ati-drivers-10.1/work/common/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c: In function ?KCL_MapPageToPfn?:
    /var/tmp/portage/x11-drivers/ati-drivers-10.1/work/common/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:1621: warning: unused variable ?bus_addr?
    make[2]: *** [/var/tmp/portage/x11-drivers/ati-drivers-10.1/work/common/lib/modules/fglrx/build_mod/2.6.x/firegl_public.o] Error 1
    make[2]: *** Waiting for unfinished jobs....
    make[1]: *** [_module_/var/tmp/portage/x11-drivers/ati-drivers-10.1/work/common/lib/modules/fglrx/build_mod/2.6.x] Error 2
    make[1]: Leaving directory `/usr/src/linux-2.6.33-rc5-zen1_bfs'
    make: *** [kmod_build] Error 2
    * ERROR: x11-drivers/ati-drivers-10.1 failed:
    * Unable to emake HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= GCC_VER_MAJ=4 KVER=2.6.33-rc5-zen1 KDIR=/usr/src/linux kmod_build
    *
    * Call stack:
    * ebuild.sh, line 48: Called src_compile
    * environment, line 8045: Called linux-mod_src_compile
    * environment, line 7201: Called die
    * The specific snippet of code:
    * eval "emake HOSTCC=\"$(tc-getBUILD_CC)\" CROSS_COMPILE=${CHOST}- LDFLAGS=\"$(get_abi_LDFLAGS)\" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS} " || die "Unable to emake HOSTCC="$(tc-getBUILD_CC)" CROSS_COMPILE=${CHOST}- LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS}";
    Help please !

    thanks

    Leave a comment:


  • dopehouse
    replied
    Originally posted by aromanos View Post
    It's very disappointing that packages don't build on Ubuntu 9.10 x86_64. Production support added... yeah sure.

    Anyway, this worked for me:

    chmod +x ./ati-driver-installer-10-1-x86.x86_64.run

    ./ati-driver-installer-10-1-x86.x86_64.run --extract

    cd fglrx-install.xxxx/arch/x86_64/usr/lib64/
    (Replace "fglrx-install.xxxx" with the name of the directory that the installer created on your system)

    ln -s libatiuki.so.1.0 libatiuki.so.1

    cd ../../../..

    sudo ./ati-installer.sh 10.1 --buildandinstallpkg Ubuntu/karmic

    Done!

    Happy building,

    -- Andr?s
    Thanks, it works.

    Leave a comment:


  • monraaf
    replied
    Originally posted by storma View Post
    Amidst all this rambling, I would just like to mention that I've seen a fps increase in my Unigine tropics/sanctuary benchmarks.

    *ducks for cover..
    Yeah, I also got a 3.5fps boost in Unigine tropics benchmark.

    Leave a comment:


  • tball
    replied
    Originally posted by elmo23x View Post
    and does it have OpenCL? or we still have to use 9.12 hotfix?
    10.1 doesn't work with opencl. Just tried :-). You have to use 9.12 hotfix.

    Leave a comment:


  • tball
    replied
    Originally posted by energyman View Post
    what 'hotfix'? what is broken?
    The driver itself might work okay. fglrx usually work fine with my computer. But the driver broke the deb packaging :S Thats quite important for most Ubuntu / Debian users, who wants to keep their system clean.

    I expect a hotfix for this driver, because of the "Ubuntu 9.10 production support" label. Don't get me wrong, I like fglrx. But labeling a driver production ready, when it even can't be packaged for the system is kinda unprofessional.

    Leave a comment:


  • krionius
    replied
    Originally posted by aromanos View Post
    ln -s libatiuki.so.1.0 libatiuki.so.1


    -- Andr?s
    yeah, that same thing was fixed to let the arch linux AUR build work. when the author of the AUR build file got report of this problem. it was fixed and made working in less than a day. http://aur.archlinux.org/packages.php?ID=29111

    Leave a comment:


  • aromanos
    replied
    It's very disappointing that packages don't build on Ubuntu 9.10 x86_64. Production support added... yeah sure.

    Anyway, this worked for me:

    chmod +x ./ati-driver-installer-10-1-x86.x86_64.run

    ./ati-driver-installer-10-1-x86.x86_64.run --extract

    cd fglrx-install.xxxx/arch/x86_64/usr/lib64/
    (Replace "fglrx-install.xxxx" with the name of the directory that the installer created on your system)

    ln -s libatiuki.so.1.0 libatiuki.so.1

    cd ../../../..

    sudo ./ati-installer.sh 10.1 --buildandinstallpkg Ubuntu/karmic

    Done!

    Happy building,

    -- Andr?s

    Leave a comment:


  • energyman
    replied
    what 'hotfix'? what is broken?

    Leave a comment:


  • LibertyZero
    replied
    Originally posted by unimatrix View Post
    Could you guys test Compiz's Window Blur? I wanna know if they really broke it.
    They really broke it.

    The question is imho what makes Compiz blur so special? I read in the "Compiz blur with fglrx"-thread that it requires OpenGL 2.0 to work. This should be no problem for fglrx. So I'd really like to know, why fgrlx has such problems with Compiz blur. By the way, is it just the blur-implementation within Compiz or is it really impossible to get alpha blur working on e.g. OGL 1.5 or even 1.4?

    Originally posted by unimatrix View Post
    Another thing, did they at least fix the issue where it was not possible to have two X sessions to run at the same time? (for example starting the guest session concurrently)
    No, it does not work.

    Another thing which still does not work is netbook-launcher while running compiz. It simply results in garbage:
    http://img109.imageshack.us/img109/5...reenshotwr.png

    Can this be reproduced on other systems?

    The xserver-backclear patch is still needed as well as it seems.

    3D performance and Power management are looking OK to me though. I still don't know, why aticonfig does not allow me to set the clocks as low as the windows driver offers it, but as long as the fan is quiet, I am pretty much satisfied.

    Leave a comment:


  • dopehouse
    replied
    Let us hope, that they fix this driver and give us a hotfix.

    Leave a comment:

Working...
X