Page 3 of 3 FirstFirst 123
Results 21 to 25 of 25

Thread: real fglrx 12.3 released

  1. #21
    Join Date
    Apr 2011
    Posts
    405

    Default

    Quote Originally Posted by bridgman View Post
    The PCI IDs in the code determine which hardware the driver will *try* to run on. The code might work perfectly, or be buggy, or fail to run at all.

    The PCI IDs in the control file show which hardware the driver has passed QA on.

    Once testing and bug fixing on specific hardware is completed, the IDs in the control file are updated to reflect that these binaries form a production driver for the hardware it's running on, whereas previously it displayed a "hey this might run but be aware it's not a production driver" message.

    The time and effort is not to add IDs to the control file (that's all automated anyways) but to do the testing, bug fixing and re-testing required to pass QA on the hardware and make it appropriate to mark the resulting binaries as production-ready in the control file.
    When are they planning to do QA to make sure power management doesn't crash the X server and that creating an OpenGL context doesn't panic the kernel sometimes?

    Both of those are issues on Ubuntu with Catalyst. Can you have one of your devs let his monitor go to sleep a few times and make sure it comes back up? BTW, if you need to know what monitors do it, I have a Westinghouse monitor from 2008 and a Samsung monitor from 2011 that both have the same exact issue.

    Edit, it happens with two cards as well, a 4670 and a 5670.
    Last edited by DaemonFC; 03-29-2012 at 04:32 AM.

  2. #22
    Join Date
    May 2011
    Posts
    14

    Default

    On my aspire with hd4200 I run a java application for charting, the speed difference between this driver and the radeon is so big I don't understand it, fglrx simply is unusable.
    it's probably what you call 2d

  3. #23
    Join Date
    Jan 2008
    Posts
    46

    Default gnome-shell random freezes

    Still random freezes in gnome-shell, back to free radeon driver. One would have thought that by now AMD would have sorted that problem. Apparently not so. Shame....

  4. #24
    Join Date
    Aug 2011
    Posts
    9

    Default

    At least we can use xf86-video-intel-2.18 now (those of us on laptops with dual muxless intel + amd GPU). With 12.2 we were stuck on 2.15.

  5. #25
    Join Date
    Nov 2010
    Location
    Grenoble - França
    Posts
    29

    Post found a solution to intel iGP no direct rendering

    I've found a solution for getting the gnome-shell working when switch to iGP card through aticonfig or CCC. Now I have gnome-shell runing in iGP without tearing and XBMC runing over iGP with an acceptable performance!

    It's a weird thing done by AMD fglrx driver during installation, but to make sure it'll work, let's verify if you have the same diagnostic:
    First thing is about glxinfo, if it show no direct rendering, just execute this command:
    Code:
     LIBGL_DEBUG=verbose; glxinfo
    the first output lines, if appears a lot of 'libGL errors' like below:

    libGL error: dlopen /usr/lib32/fglrx/dri/swrast_dri.so failed
    libGL error: dlopen /usr/lib32/fglrx/dri/i915_dri.so failed

    if you saw, there's an i915 dri driver that couldn't be loaded for some reason. As you can see, the directory is /usr/lib32/fglrx/dri/ but, if you ls this directory you will not see more than one driver named
    fglrx_dri.so

    So, I've figured out that when fglrx driver installs it changes the LIBGL_DRIVERS_PATH to its own particular path, such that is: /usr/lib/fglrx/dri:/usr/lib32/fglrx/dri

    if you write the command below you'll see the output like above:

    Code:
     echo $LIBGL_DRIVERS_PATH
    the output will be something like that: /usr/lib/fglrx/dri:/usr/lib32/fglrx/dri

    if you have the same output as above you just have to add the directory where is the intel dri drivers, lets do that!
    as you can see in this file : /etc/X11/Xsession.d/10fglrx

    Code:
    $ gksu gedit /etc/X11/Xsession.d/10fglrx
    Code:
     LIBGL_DRIVERS_PATH=/usr/lib/fglrx/dri 
    if [ `uname -m` = 'x86_64' ]; then 
      if [ -d /usr/lib32/fglrx/dri ]; then 
        LIBGL_DRIVERS_PATH=${LIBGL_DRIVERS_PATH}:/usr/lib32/fglrx/dri
        if [ ! -z $LD_LIBRARY_PATH ]; then 
    	LD_LIBRARY_PATH=$LD_LIBRARY_PATH: 
        fi 
        LD_LIBRARY_PATH=${LD_LIBRARY_PATH}/usr/lib32 
        export LD_LIBRARY_PATH 
      fi 
    fi 
    export LIBGL_DRIVERS_PATH
    in the fourth line you have the LIBGL_DRIVERS_PATH defined as: /usr/lib/fglrx/dri:/usr/lib32/fglrx/dri
    if you have the same as above, just add the following path in that fourth line:

    for x86_64 (64 bits): /usr/lib/x86_64-linux-gnu/dri/

    for x86 (32 bits) linux: /usr/lib32/dri/

    just add is with a “:” (without quotes) in the end of 4th line to get the direct render working!
    The file will be like this:
    File /etc/X11/Xsession.d/10fglrx for 64 bits (x86_64) linux:
    Code:
    LIBGL_DRIVERS_PATH=/usr/lib/fglrx/dri 
    if [ `uname -m` = 'x86_64' ]; then 
      if [ -d /usr/lib32/fglrx/dri ]; then 
        LIBGL_DRIVERS_PATH=${LIBGL_DRIVERS_PATH}:/usr/lib32/fglrx/dri:/usr/lib/x86_64-linux-gnu/dri 
        if [ ! -z $LD_LIBRARY_PATH ]; then 
    	LD_LIBRARY_PATH=$LD_LIBRARY_PATH: 
        fi 
        LD_LIBRARY_PATH=${LD_LIBRARY_PATH}/usr/lib32 
        export LD_LIBRARY_PATH 
      fi 
    fi 
    export LIBGL_DRIVERS_PATH
    File /etc/X11/Xsession.d/10fglrx for 32 bits (x86) linux:
    Code:
    LIBGL_DRIVERS_PATH=/usr/lib/fglrx/dri 
    if [ `uname -m` = 'x86_64' ]; then 
      if [ -d /usr/lib32/fglrx/dri ]; then 
        LIBGL_DRIVERS_PATH=${LIBGL_DRIVERS_PATH}:/usr/lib32/fglrx/dri://usr/lib32/dri
        if [ ! -z $LD_LIBRARY_PATH ]; then 
    	LD_LIBRARY_PATH=$LD_LIBRARY_PATH: 
        fi 
        LD_LIBRARY_PATH=${LD_LIBRARY_PATH}/usr/lib32 
        export LD_LIBRARY_PATH 
      fi 
    fi 
    export LIBGL_DRIVERS_PATH
    then save the /etc/X11/Xsession.d/10fglrx (must have root privileges) and reboot your system

    then
    Code:
     $ glxinfo | egrep render
    and check it out if you'll have direct rendering!
    Voilà! Shaazaam! Works

    I've got gnome-shell loading and working sweeeeeeeeeetly!! XBMC also are working sweeeeetly and without video tearing! Good bye cruel World!!!!

    Can someone tell me if Unity 3D works?

Posting Permissions

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