Announcement

Collapse
No announcement yet.

Catalyst shit 12.3 - Can help me with install ???

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

  • DjDiabolik
    started a topic Catalyst shit 12.3 - Can help me with install ???

    Catalyst shit 12.3 - Can help me with install ???

    I'm redirected here from amd shi* forum....... i hope i can found a solution here :

    I have try to install so many time the ATI Catalyst 12.3 on Ubuntu 11.10.
    First time i have try with kernel 3.0.0.-12,17,19 etc etc without success!! now i have try to upgrade to 3.3.1 and retry again but on every kernel i try i have the exact same problems!

    I have read so many guide... the latest i have read this:
    http://wiki.cchtml.com/index.php/Ubu...TI.27s_site.29
    But not working!

    I have created correctly the 3 file .deb....... but during the installation of this i obtain this:
    Code:
    [email protected]:~/catalyst12.3$ sudo dpkg -i fg*.deb
    Selezionato il pacchetto fglrx.
    (Lettura del database... 322768 file e directory attualmente installati.)
    Estrazione di fglrx (da fglrx_8.951-0ubuntu1_i386.deb)...
    Selezionato il pacchetto fglrx-amdcccle.
    Estrazione di fglrx-amdcccle (da fglrx-amdcccle_8.951-0ubuntu1_i386.deb)...
    Selezionato il pacchetto fglrx-dev.
    Estrazione di fglrx-dev (da fglrx-dev_8.951-0ubuntu1_i386.deb)...
    Configurazione di fglrx (2:8.951-0ubuntu1)...
    update-alternatives: viene usato /usr/lib/fglrx/ld.so.conf per fornire /etc/ld.so.conf.d/i386-linux-gnu_GL.conf (i386-linux-gnu_gl_conf) in modalit? automatica.
    update-alternatives: attenzione: saltata la creazione di /etc/OpenCL/vendors/amdocl64.icd poich? il file /usr/lib/fglrx/etc/OpenCL/vendors/amdocl64.icd associato (del gruppo i386-linux-gnu_gl_conf) non esiste.
    update-alternatives: attenzione: saltata la creazione di /usr/lib32/libaticalcl.so poich? il file /usr/lib32/fglrx/libaticalcl.so associato (del gruppo i386-linux-gnu_gl_conf) non esiste.
    update-alternatives: attenzione: saltata la creazione di /usr/lib32/libaticalrt.so poich? il file /usr/lib32/fglrx/libaticalrt.so associato (del gruppo i386-linux-gnu_gl_conf) non esiste.
    update-alternatives: attenzione: viene forzata l'installazione dell'alternativa /usr/lib/fglrx/ld.so.conf poich? il gruppo i386-linux-gnu_gl_conf ? danneggiato.
    update-alternatives: attenzione: saltata la creazione di /etc/OpenCL/vendors/amdocl64.icd poich? il file /usr/lib/fglrx/etc/OpenCL/vendors/amdocl64.icd associato (del gruppo i386-linux-gnu_gl_conf) non esiste.
    update-alternatives: attenzione: saltata la creazione di /usr/lib32/libaticalcl.so poich? il file /usr/lib32/fglrx/libaticalcl.so associato (del gruppo i386-linux-gnu_gl_conf) non esiste.
    update-alternatives: attenzione: saltata la creazione di /usr/lib32/libaticalrt.so poich? il file /usr/lib32/fglrx/libaticalrt.so associato (del gruppo i386-linux-gnu_gl_conf) non esiste.
    update-alternatives: viene usato /usr/lib/fglrx/alt_ld.so.conf per fornire /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf (x86_64-linux-gnu_gl_conf) in modalit? automatica.
    update-initramfs: deferring update (trigger activated)
    update-initramfs: Generating /boot/initrd.img-3.3.1-030301-generic-pae
    Loading new fglrx-8.951 DKMS files...
    First Installation: checking all kernels...
    Building only for 3.3.1-030301-generic-pae
    Building for architecture i686
    Building initial module for 3.3.1-030301-generic-pae
    Error! Bad return status for module build on kernel: 3.3.1-030301-generic-pae (i686)
    Consult /var/lib/dkms/fglrx/8.951/build/make.log for more information.
    update-initramfs: deferring update (trigger activated)
    Elaborazione dei trigger per ureadahead...
    Elaborazione dei trigger per gnome-menus...
    Elaborazione dei trigger per bamfdaemon...
    Rebuilding /usr/share/applications/bamf.index...
    Configurazione di fglrx-amdcccle (2:8.951-0ubuntu1)...
    Configurazione di fglrx-dev (2:8.951-0ubuntu1)...
    Elaborazione dei trigger per initramfs-tools...
    update-initramfs: Generating /boot/initrd.img-3.3.1-030301-generic-pae
    Elaborazione dei trigger per libc-bin...
    ldconfig deferred processing now taking place
    [email protected]:~/catalyst12.3$
    Other time i have read a simple guide invite me to use the automatic gui installation but i obtain this:
    Code:
    [email protected]:/home/diabolik/catalyst12.3# sh ./amd-driver-installer-12-3-x86.x86_64.run --keep
    Created directory fglrx-install.OnFD7H
    Verifying archive integrity... All good.
    Uncompressing AMD Catalyst(TM) Proprietary  Driver-8.951...............................................................................................    ....................................................................................................    ....................................................................................................    ....................................................................................................    ....................................................................................................    ....................................................................................................    ....................................................................................................    ....................................................................................................    ....................................................................................................    ....................................................................................................   ................................................
    =====================================================================
     AMD Catalyst(TM) Proprietary Driver Installer/Packager 
    =====================================================================
    Detected configuration:
    Architecture: i686 (32-bit)
    X Server: X.Org 6.9 or later
    loki_setup: directory: (null)
    DKMS part of installation failed.  Please refer to /usr/share/ati/fglrx-install.log for details
    And this is the contain of the log file:
    Code:
    Uninstalling any previously installed drivers.
    
    Creating symlink /var/lib/dkms/fglrx/8.951/source ->
                     /usr/src/fglrx-8.951
    
    DKMS: add Completed.
    
    Kernel preparation unnecessary for this kernel.  Skipping...
    
    Building module:
    cleaning build area....
    cd /var/lib/dkms/fglrx/8.951/build; sh make.sh --nohints --uname_r=3.3.1-030301-generic-pae --norootcheck....(bad exit status: 1)
    [Error] Kernel Module : Failed to build fglrx-8.951 with DKMS
    [Error] Kernel Module : Removing fglrx-8.951 from DKMS
    
    ------------------------------
    Deleting module version: 8.951
    completely from the DKMS tree.
    ------------------------------
    Done.
    [Reboot] Kernel Module : update-initramfs
    This 12.3 it's a shit driver and AMD shit on Linux... on windows and on mac ?

  • energyman
    replied
    first of all, don't post output in your fairy tale language and expect help.

    second, 12.3 works fine. If you can not install it, blame yourself or the guy who packaged it for your broken distribution.

    gentoo works.

    Leave a comment:


  • PsynoKhi0
    replied
    Originally posted by iczer1 View Post
    Hi all,

    I remembered from a few threads ago about failed to compile module.
    You need to look at the log, find a file called uaccess_xx.h and delete the "else ... endif"
    for a total of 3 lines to compile.

    br,
    Still, getting a newer kernel shouldn't be needed to get fglrx up and running on a released version of Ubuntu.
    If the installation goes wrong with the stock kernel, usually the reasons are:
    - Lack of some required packages to build the module, see the cchtml wiki
    - Having left-overs from Jockey
    - To be on the safe side, switch to a tty and stop Xorg when installing:
    Code:
    sudo service lightdm stop
    - If you build .deb packages, remember to run
    Code:
    sudo aticonfig --initial -f
    to get your xorg.conf prior to rebooting, and remember to delete that file when uninstalling

    You know... Stuff you learn when actually reading available information...

    Leave a comment:


  • iczer1
    replied
    Hi all,

    I remembered from a few threads ago about failed to compile module.
    You need to look at the log, find a file called uaccess_xx.h and delete the "else ... endif"
    for a total of 3 lines to compile.

    br,

    Leave a comment:


  • Kano
    replied
    As soon as you call the amd-installer without buildpkg option it directly writes files at places which will NOT be the position you get with the fglrx ubuntu package. jockey is the name of ubuntu's the restricted modules manager and allows the install of binary drivers from the ubunut repository. When you mix that your system will most likely break on the next update. As U has got latest 8.96 drivers for 12.4 i would not use the amd-installer at all for this version. My script basically checks for the Ubuntu version, then it installs the needed depends (maybe a few more which have been needed for older releases, some will fail on newer distributions but those are not critical) then it applies patches to the fglrx module for better kernel support if needed. In case of Ubuntu it just creates the packages using buildpkg option, deletes all older fglrx packages, installs the new ones, calls aticonfig to write a /etc/X11/xorg.conf file. This step is not done by ubuntu normally as they install one additional package which i just delete as it is not required (and useless) on Debian. The script therefore works on Debian up to Squeeze, it does not (yet) work for Wheezy/Sid. There i patch some things to use Ubuntu packages on Debian. With current drivers i would not need to patch that much (just a few depend issues), informer i needed to override the XORG driver version depending on the installed X because up to 3 different variants have been shipped in the amd installer - this is now unified.

    This was the general way what my script does, but what is also different is what happens when it detects radeon kms drivers nor not. Compared to nouveau kms which can be unloaded with a trick and then you can switch over to nvidia binary (using screen) this is not possible for fglrx. It worked with radeon without kms, but not always. It works more often when (older) fglrx is running, but not in all cases. You need to stop X in that case then you unload fglrx and install everything then you start X up again. This way you can avoid a reboot. If you want to make it saver you can FORCE the script not to stop X at all even when it would be possible in theory. The "-z" option is just for this and is default when radeon kms is detected. In that case you have to reboot to activate fglrx.

    But: i only test Ubuntu when a new release is in first alpha or directly after release. Usually it should work in the development time between as well, but i have got no permanent U install.

    Leave a comment:


  • geqo
    replied
    Originally posted by Kano View Post
    If you have got an install with loaded fglrx module but borken userspace it would try to stop the xserver and install it then. that will not work in most cases. Usually you break ubuntu when you run the installer without buildpkg option. the next ubuntu update will kill it when it tries to install the fglrx driver via jockey.
    Kano I have to admit I have very little idea what you're talking about :S I'm still learning a lot here... Any chance you could try that again in English?

    Leave a comment:


  • geqo
    replied
    A small (huge?) caveat... The next time I restarted my machine, it got stuck. I was only able to get back in after going back into Single User mode, and reinstalling the 12.3 driver (with the --force command again). Now it's running again, although I'm a little scared to restart it :P

    Leave a comment:


  • Kano
    replied
    If you have got an install with loaded fglrx module but borken userspace it would try to stop the xserver and install it then. that will not work in most cases. Usually you break ubuntu when you run the installer without buildpkg option. the next ubuntu update will kill it when it tries to install the fglrx driver via jockey.

    Leave a comment:


  • geqo
    replied
    Admittedly it was a couple days ago that I ran it, so I can't remember whether or not I used the -z option, but I imagine I would have followed the instructions... Now sure now

    Leave a comment:


  • Kano
    replied
    Did you really run the script with -z option?

    Leave a comment:

Working...
X