Howto for fglrx / catalyst (Ati driver) - Page 311

HMSS013 · #**4651** 2nd August 2012, 10:24 AM

Quote:

Originally Posted by Yellowman

Still no ****ing interest?

i'd definitely give it a swing if i thought my hardware was still supported...

#**4652** 2nd August 2012, 11:40 AM

Quote:

Originally Posted by HMSS013

i'd definitely give it a swing if i thought my hardware was still supported...

I'm working on getting the legacy driver into rpmfusion and have submitted requests for review.
I tested the legacy driver yesterday after patching it for kernel 3.5 and it works fine, the same can't be said for the standard driver (different patch) which just got pushed to stable untested.

http://download1.rpmfusion.org/nonfr...-catalyst.html

HMSS013 · #**4653** 2nd August 2012, 01:01 PM

Quote:

Originally Posted by Yellowman

I'm working on getting the legacy driver into rpmfusion and have submitted requests for review.
I tested the legacy driver yesterday after patching it for kernel 3.5 and it works fine, the same can't be said for the standard driver (different patch) which just got pushed to stable untested.

http://download1.rpmfusion.org/nonfr...-catalyst.html

last week i gave it a whirl and grub would hang when the count reached 0...

...unless i misread...leighs original post says the Radeon HD 2400 XT isn't supported anymore...

#**4654** 2nd August 2012, 01:14 PM

Quote:

Originally Posted by HMSS013

last week i gave it a whirl and grub would hang when the count reached 0...

...unless i misread...leighs original post says the Radeon HD 2400 XT isn't supported anymore...

You didn't misread it, I'm referring to the new legacy driver (catalyst-legacy-kmod) that I'm trying to get into rpmfusion.

Do you use 64bit? as I have rpm's for it

HMSS013 · #**4655** 2nd August 2012, 01:24 PM

Quote:

Originally Posted by Yellowman

You didn't misread it, I'm referring to the new legacy driver (catalyst-legacy-kmod) that I'm trying to get into rpmfusion.

Do you use 64bit? as I have rpm's for it

yup 64bit...i'll definitely wanna give it a whirl

tho i should mention that i tried installing the latest 12.6 legacy drivers from the amd binary package and was left with a black screen after restart...

...oddly enough i could still hear Skype running...

#**4656** 2nd August 2012, 01:56 PM

Quote:

Originally Posted by HMSS013

yup 64bit...i'll definitely wanna give it a whirl

tho i should mention that i tried installing the latest 12.6 legacy drivers from the amd binary package and was left with a black screen after restart...

...oddly enough i could still hear Skype running...

Did you run

Code:

su
mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r)-radeon.img
dracut /boot/initramfs-$(uname -r).img $(uname -r)

---------- Post added at 01:56 PM ---------- Previous post was at 01:27 PM ----------

Quote:

Originally Posted by Yellowman

Did you run

Code:

su
mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r)-radeon.img
dracut /boot/initramfs-$(uname -r).img $(uname -r)

https://dl.dropbox.com/u/6907158/catalyst-legacy.tar.xz

HMSS013 · #**4657** 2nd August 2012, 04:10 PM

Quote:

Originally Posted by Yellowman

https://dl.dropbox.com/u/6907158/catalyst-legacy.tar.xz

sure enough...these packages do the same thing

a backlit black screen...but i can hear my stuff running...i can even navigate the terminal in the dark to reboot

if i remove the radeon.modeset from the grub line it'll atleast show me plymouth...but then a very black screen

Quote:

Originally Posted by Yellowman

Did you run

Code:

su
mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r)-radeon.img
dracut /boot/initramfs-$(uname -r).img $(uname -r)

gave this a swing too...no change...

#**4658** 2nd August 2012, 05:05 PM

Quote:

Originally Posted by HMSS013

sure enough...these packages do the same thing

a backlit black screen...but i can hear my stuff running...i can even navigate the terminal in the dark to reboot

if i remove the radeon.modeset from the grub line it'll atleast show me plymouth...but then a very black screen

gave this a swing too...no change...

Did you have the matching kernel-devel to your running kernel?

HMSS013 · #**4659** 2nd August 2012, 09:27 PM

Quote:

Originally Posted by Yellowman

Did you have the matching kernel-devel to your running kernel?

most certainly

HMSS013 · #**4660** 4th August 2012, 07:21 PM

i could really use some help to resolve this issue

when attempting to install the Catalyst Legacy drivers from the ATI binary package:

Code:

DKMS part of installation failed.

...and the log...

Code:

Building module:
cleaning build area....
cd /var/lib/dkms/fglrx/8.97.100.3/build; sh make.sh --nohints --uname_r=3.5.0-2.fc17.x86_64 --norootcheck....(bad exit status: 1)
[Error] Kernel Module : Failed to build fglrx-8.97.100.3 with DKMS
[Error] Kernel Module : Removing fglrx-8.97.100.3 from DKMS

#**4661** 4th August 2012, 07:40 PM

Quote:

Originally Posted by HMSS013

i could really use some help to resolve this issue

when attempting to install the Catalyst Legacy drivers from the ATI binary package:

Code:

DKMS part of installation failed.

...and the log...

Code:

Building module:
cleaning build area....
cd /var/lib/dkms/fglrx/8.97.100.3/build; sh make.sh --nohints --uname_r=3.5.0-2.fc17.x86_64 --norootcheck....(bad exit status: 1)
[Error] Kernel Module : Failed to build fglrx-8.97.100.3 with DKMS
[Error] Kernel Module : Removing fglrx-8.97.100.3 from DKMS

No ati driver is compatible with 3.5 kernel without patching.

HMSS013 · #**4662** 7th August 2012, 07:23 AM

help please... i gotta know what i'm doing wrong here...

step by step...using the 3.3.4-5.fc17.x86_64 kernel (with matching devel and headers) and the 12.6 legacy binary:

Development Tools:

Code:

yum groupinstall development-tools

DKMS

Code:

yum install dkms

Mesa

Code:

yum install mesa-dri-drivers mesa-dri-drivers.i686 mesa-libGL mesa-libGL.i686 mesa-dri-filesystem mesa-dri-filesystem.i686 mesa-libEGL mesa-libEGL.i686 mesa-libGLU mesa-libGLU.i686

Repairing Mesa (yes, i know it's erroneous...but what the hey)

Code:

yum reinstall mesa-libGL

Reboot

ATI Binary Installer

Code:

sh ./amd-driver-installer-12.6-legacy-x86.x86_64.run

Remove Radeon From Intramfs

Code:

mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r)-radeon.img
dracut /boot/initramfs-$(uname -r).img $(uname -r)

...the log readout...

Code:

Check if system has the tools required for installation.
Uninstalling any previously installed drivers.

Creating symlink /var/lib/dkms/fglrx/8.97.100.3/source ->
                 /usr/src/fglrx-8.97.100.3

DKMS: add completed.

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area....
cd /var/lib/dkms/fglrx/8.97.100.3/build; sh make.sh --nohints --uname_r=3.3.4-5.fc17.x86_64 --norootcheck......
cleaning build area....

DKMS: build completed.

fglrx:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/3.3.4-5.fc17.x86_64/extra/

depmod....

DKMS: install completed.
[Reboot] Kernel Module : dracut

...and after reboot i'm still getting a blank screen when starting X

mercury305 · #**4663** 7th August 2012, 01:49 PM

Quote:

Originally Posted by HMSS013

help please... i gotta know what i'm doing wrong here...

step by step...using the 3.3.4-5.fc17.x86_64 kernel (with matching devel and headers) and the 12.6 legacy binary:

Development Tools:

Code:

yum groupinstall development-tools

DKMS

Code:

yum install dkms

Mesa

Code:

yum install mesa-dri-drivers mesa-dri-drivers.i686 mesa-libGL mesa-libGL.i686 mesa-dri-filesystem mesa-dri-filesystem.i686 mesa-libEGL mesa-libEGL.i686 mesa-libGLU mesa-libGLU.i686

Repairing Mesa (yes, i know it's erroneous...but what the hey)

Code:

yum reinstall mesa-libGL

Reboot

ATI Binary Installer

Code:

sh ./amd-driver-installer-12.6-legacy-x86.x86_64.run

Remove Radeon From Intramfs

Code:

mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r)-radeon.img
dracut /boot/initramfs-$(uname -r).img $(uname -r)

...the log readout...

Code:

Check if system has the tools required for installation.
Uninstalling any previously installed drivers.

Creating symlink /var/lib/dkms/fglrx/8.97.100.3/source ->
                 /usr/src/fglrx-8.97.100.3

DKMS: add completed.

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area....
cd /var/lib/dkms/fglrx/8.97.100.3/build; sh make.sh --nohints --uname_r=3.3.4-5.fc17.x86_64 --norootcheck......
cleaning build area....

DKMS: build completed.

fglrx:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/3.3.4-5.fc17.x86_64/extra/

depmod....

DKMS: install completed.
[Reboot] Kernel Module : dracut

...and after reboot i'm still getting a blank screen when starting X

My opinion is to just switch distros. Fedora sucks when it comes to support. I have asked for a simple question on not being able to get my CUPS Printer running and no reply. Why? Because Feodra people are too busy coding to be bothered with pesky users with hardware problems. ATI Catalyst has always been a problem because Fedora uses the latest Kernel. Redhat pays Fedora for innovation... so if you like to be a lab rat continue using Fedora. I switched to Slackware and everything got easier for me my ATI Catalyst and Printer both work with its old 2.6.37 kernel.

tuxtard · #**4664** 7th August 2012, 01:54 PM

Well I don't know what's the problem. Catalyst works just fine with my HD6850 and nomodeset grub option. I will check the legacy driver on my HD4850 when I get home.

Fenrin · #**4665** 7th August 2012, 02:07 PM

Quote:

Originally Posted by HMSS013

[...]

I installed this Catalyst 12.6 legacy and I'm using kernel 3.4.6-4.fc17.x86_64, with correct kernel-devel and kernel-headers installed. It works without issues with my Radeon HD 3200.

if you want to reinstall it again, make sure that you first uninstall the proprietary driver properly.

the step "Remove Radeon From Intramfs" is not necessary.

this log file you quoted above is not the file at /usr/ati/fglrx-install.log or is it? I have completely different content in it.

the log /usr/ati/fglrx-install.log should be similar to this content (this log is not complete):

Quote:

[...]
[Message] Kernel Module : Trying to install a precompiled kernel module.
[Message] Kernel Module : Precompiled kernel module version mismatched.
[Message] Kernel Module : Found kernel module build environment, generating kernel module now.
AMD kernel module generator version 2.1
doing Makefile based build for kernel 2.6.x and higher
rm -rf *.c *.h *.o *.ko *.a .??* *.symvers
make -C /lib/modules/3.4.6-4.fc17.x86_64/build SUBDIRS=/usr/lib/modules/fglrx/build_mod/2.6.x modules
make[1]: Entering directory `/usr/src/kernels/3.4.6-4.fc17.x86_64'
[...]
LD [M] /usr/lib/modules/fglrx/build_mod/2.6.x/fglrx.o
Building modules, stage 2.
MODPOST 1 modules
CC /usr/lib/modules/fglrx/build_mod/2.6.x/fglrx.mod.o
LD [M] /usr/lib/modules/fglrx/build_mod/2.6.x/fglrx.ko
make[1]: Leaving directory `/usr/src/kernels/3.4.6-4.fc17.x86_64'
build succeeded with return value 0
duplicating results into driver repository...
done.
You must change your working directory to /lib/modules/fglrx
and then call ./make_install.sh in order to install the built module.
- recreating module dependency list
- trying a sample load of the kernel modules
done.
[Reboot] Kernel Module : dracut