[SOLVED] Can't compile fglrx kernel module for kernel 3.2.13 in -current

DjDiabolik · 04-06-2012, 07:26 PM

For now i have resolve after install the FLGRX included in UBUNTU official repository.

In AMD forum i have read some people have so many problems with ATI driver 12.2 and 12.3 and, if i don't commit an error, latest FLGRX it's based on Catalyst 11.8....

Otherwise now i stay to post from another computer... tommorow (in italy it's 2:30AM) i come turn on pc with ubuntu and i can paste the log...

DjDiabolik · 04-09-2012, 07:55 PM

Quote:

Originally Posted by delta function

Hi,

I had the same issues after upgrading to --current (Kernel 3.2.12) with an ati hd5xx series card. The bug fix has not yet been implemented in the latest ati driver 12.3.

Thanks to this threat, I got it solved. However, it was not that easy as it sounds in the threat for me:

extract the files
apply patch
install

So, I just wanted to tell, how I finally did it.
1. Get the patch file ( see attachment )
place the file somewhere ( e.g /etc/ati/patch/ ) and get rid of the txt extension.

2. Drop out of X and into root mode
3. run the amd installer with the --keep option ( sh amd-xxx.sh --keep )
At the end of the installer procedure, the installer will give you a message that the installation was not successful due to some errors.
4. cd /lib/modules/fglrx/build_mod
5. Run the patch: patch -p0 < /etc/ati/patch/ati_patch
You should get a message that the patch was successfull.

6. sh make.sh ( to build the kernel files )
7. cd .. ( /lib/modules/fglrx)
8. sh make_install.sh ( to install the kernel files )
aticonfig --initial
9. Drop to user account ( e.g ctl-D )
10.startx
Note:
On the save side, I rebooted my machine, but It is not required.

Hope this will help some people.

Again this guide it's not working.... on ubuntu!
After running the command:

Code:

sh ./amd-driver-installer-12-3-x86.x86_64.run --keep

I go to /lib/modules and here the folder fglrx it's not present!! look here:

Code:

root@Diabolik-ubuntu:/lib# cd modules
root@Diabolik-ubuntu:/lib/modules# ls
3.0.0-12-generic      3.0.0-18-generic      3.0.0-19-generic      3.3.1-030301-generic
3.0.0-17-generic-pae  3.0.0-18-generic-pae  3.0.0-19-generic-pae  3.3.1-030301-generic-pae
root@Diabolik-ubuntu:/lib/modules#

On ubuntu this procedure it's no valid..........

*EDIT*
I have found on UBUNTU how the setup put the file!!!!
I have used:
[CODE]./amd-driver-installer-12-3-x86.x86_64.run --extract Temp[/CODE0]
After that a folder called "Temp" it's been created on same folder of .run!!
Inside this folder exist so many sub-folders:

Code:

root@Diabolik-ubuntu:/home/diabolik/catalyst12.3/Temp# ls
amd-uninstall.sh         config_install.sh          packages       pre_drv.sh
arch                     copy_uninstall_files.sh    post_cp.sh     pre_km.sh
ati-installer.sh         create_log.sh              post_drv.sh    preun_doc.sh
ati-packager-helper.sh   default_policy.sh          post_km.sh     preun_km.sh
ati-packager-wrapper.sh  detect_previous.sh         postun_cp.sh   README.distro
automatic-install.exp    fglrx-uninstall.sh         postun_drv.sh  setup.data
check.sh                 installer_creation_policy  postun_km.sh   verify_install.sh
cimle-xdgsu              LICENSE.TXT                postun_rn.sh   xpic
common                   lokixml.sh                 pre_cp.sh      xpic_64a
component_config.sh      map_xname.sh               pre_doc.sh

The file make_install.sh it's in common -> lib -> modules -> fglrx !

Another sub-folder it's still present here... it's "build_mod", i have try to apply the patch on this folder... but after that the "sh make.sh" not working

This is the full Exit when i try to execute sh make.sh:

Code:

root@Diabolik-ubuntu:/home/diabolik/catalyst12.3/fglrx-install.Jg6XLB/common/lib/modules/fglrx/build_mod# sudo sh ./make.sh
AMD kernel module generator version 2.1
[: 393: 1: unexpected operator
[: 399: 1: unexpected operator
doing Makefile based build for kernel 2.6.x and higher
rm -rf *.c *.h *.o *.ko *.a .??* *.symvers
make -C /lib/modules/3.3.1-030301-generic-pae/build SUBDIRS=/home/diabolik/catalyst12.3/fglrx-install.Jg6XLB/common/lib/modules/fglrx/build_mod/2.6.x modules
make[1]: ingresso nella directory "/usr/src/linux-headers-3.3.1-030301-generic-pae"
  CC [M]  /home/diabolik/catalyst12.3/fglrx-install.Jg6XLB/common/lib/modules/fglrx/build_mod/2.6.x/firegl_public.o
  CC [M]  /home/diabolik/catalyst12.3/fglrx-install.Jg6XLB/common/lib/modules/fglrx/build_mod/2.6.x/kcl_acpi.o
  CC [M]  /home/diabolik/catalyst12.3/fglrx-install.Jg6XLB/common/lib/modules/fglrx/build_mod/2.6.x/kcl_agp.o
  CC [M]  /home/diabolik/catalyst12.3/fglrx-install.Jg6XLB/common/lib/modules/fglrx/build_mod/2.6.x/kcl_debug.o
  CC [M]  /home/diabolik/catalyst12.3/fglrx-install.Jg6XLB/common/lib/modules/fglrx/build_mod/2.6.x/kcl_ioctl.o
  CC [M]  /home/diabolik/catalyst12.3/fglrx-install.Jg6XLB/common/lib/modules/fglrx/build_mod/2.6.x/kcl_io.o
  CC [M]  /home/diabolik/catalyst12.3/fglrx-install.Jg6XLB/common/lib/modules/fglrx/build_mod/2.6.x/kcl_pci.o
  CC [M]  /home/diabolik/catalyst12.3/fglrx-install.Jg6XLB/common/lib/modules/fglrx/build_mod/2.6.x/kcl_str.o
  CC [M]  /home/diabolik/catalyst12.3/fglrx-install.Jg6XLB/common/lib/modules/fglrx/build_mod/2.6.x/kcl_iommu.o
  CC [M]  /home/diabolik/catalyst12.3/fglrx-install.Jg6XLB/common/lib/modules/fglrx/build_mod/2.6.x/kcl.o
  CC [M]  /home/diabolik/catalyst12.3/fglrx-install.Jg6XLB/common/lib/modules/fglrx/build_mod/2.6.x/kcl_wait.o
make[2]: ***  Nessuna regola per generare l'obiettivo "/home/diabolik/catalyst12.3/fglrx-install.Jg6XLB/common/lib/modules/fglrx/build_mod/2.6.x/libfglrx_ip.a", necessario per "/home/diabolik/catalyst12.3/fglrx-install.Jg6XLB/common/lib/modules/fglrx/build_mod/2.6.x/fglrx.o".  Arresto.
make[1]: *** [_module_/home/diabolik/catalyst12.3/fglrx-install.Jg6XLB/common/lib/modules/fglrx/build_mod/2.6.x] Errore 2
make[1]: uscita dalla directory "/usr/src/linux-headers-3.3.1-030301-generic-pae"
make: *** [kmod_build] Errore 2
build failed with return value 2
root@Diabolik-ubuntu:/home/diabolik/catalyst12.3/fglrx-install.Jg6XLB/common/lib/modules/fglrx/build_mod#

After a installation failed.. this is the log indicated... flgrx_install.log:

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

TobiSGD · 04-26-2012, 06:47 PM

Update: Same error with version 12.4, patch still needed.

nitrobandit · 05-06-2012, 10:32 PM

This patch allowed to install fglrx into slackware-current. Thanks. But
Still cannot startx, apparently fglrx is not compatible with xorg 1.12 and when I downgraded to xorg 1.9.5 from 13.37 repo I get a black screen and system freeze when trying to start that.

I guess wait for amd to get to new xorg support. I went back to full 13.37 and will see how develops over next month.

TobiSGD · 05-07-2012, 04:13 AM

I currently have a grudge against AMD. I think when they develop further in the same tempo I can't use an up-to-date -current anymore on my laptop before they drop support for my chipset and also have to revert to 13.37.

zakame · 06-06-2012, 06:03 AM

Quote:

Originally Posted by willysr

try visiting Walecha's blog http://www.walecha.net/content/memba...di-kernel-3213
It's in Indonesian, but i believe you can understand by looking at the code snippet or use Google Translate

Just found myself doing this now on my laptop to try out the beta 12.6 drivers. I don't understand Indonesian, but good thing the blog had the terminal output, so let me explain here:

Get the Catalyst patch from AUR:

Code:

lftp -c 'get http://aur.archlinux.org/packages/ca...atalyst.tar.gz'

Create the /etc/ati/patch directory:
Code:
```
mkdir -p /etc/ati/patch
```
Unpack the catalyst.tar.gz and copy the relevant patch inside to /etc/ati/patch, the filename being of the format "patch-<fglrx-version>-<kernel-version>", e.g.
Code:
```
cat catalyst/3.2.8.patch /etc/ati/patch/patch-8.961-3.2.13
```
for patching Catalyst 12.4 stable on -current kernel, or
Code:
```
cat catalyst/3.4.patch /etc/ati/patch/patch-8.98-3.4.1
```
for patching Catalyst 12.6 beta on kernel.org mainline; change the patch filename to suit your environment.
Edit the patch in /etc/ati/patch to remove the pathnames of files in each hunk, leaving only the basename. That is, if the patch contains
Code:
```
a/common/lib/modules/fglrx/build_mod/firegl_public.c
```
strip that down to just the filename,
Code:
```
firegl_public.c
```

Build the driver:

Code:

sh amd-driver-installer-<version>-<arch>.run --buildpkg Slackware/Slackware

Hopefully you end up with an fglrx-*.tgz

ponce · 06-10-2012, 12:03 PM

Hi toby, this is a slackware forum, not the ubuntu bug tracker

guilem · 06-23-2012, 12:28 PM

Hi all

@ delta function

I'm going through the same problems with a radeon HD 4350 card, and was very anxious to experiment the patch, but got stuck here:

Quote:

Originally Posted by delta function

4. cd /lib/modules/fglrx/build_mod

Forgive me if this sounds rather newbeish, but I running debian squeeze (in fact crunchbang statler) and I don't have such a directory. I don't know if I should create it or what would be the equivalent in debian?

*edit*
Well, it's newbeish enough, I ought to have read a little bit more of the thread, I'd have understood it's slackware forum here. Sorry!

guilem

ReaperX7 · 06-23-2012, 03:02 PM

Forgive the bluntness but this topic was raised earlier by another member.

http://www.linuxquestions.org/questi...el-4175411217/

Because Slackware's -Current tree is a rolling release style developer/tester branch of the software, usage of proprietary drivers may or may not work depending on which version of packages you have. The proprietary drivers are aimed at stable releases like 12.2, 13.0, and 13.37.

The Xorg drivers do include full support for all modern Radeon series cards for both 2D and 3D hardware acceleration.

TobiSGD · 06-24-2012, 12:18 AM

Quote:

Originally Posted by ReaperX7

The Xorg drivers do include full support for all modern Radeon series cards for both 2D and 3D hardware acceleration.

Sorry, but no, they don't. The X.Org drivers have currently no usable support for the HD7000 series, they don't support the UVD block of the chips and the power management is faulty, which makes it unusable for many laptops. To see which feautures are really supported have a look here: http://www.x.org/wiki/RadeonFeature
They are still far away from being feature complete or have the same performance. I hope that gets better after they have made their major deal with China.