LinuxQuestions.org - Error installing ATI Catalyst Driver

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Error installing ATI Catalyst Driver (https://www.linuxquestions.org/questions/slackware-14/error-installing-ati-catalyst-driver-4175492202/)

Error installing ATI Catalyst Driver

I am getting this:

Code:

cat /usr/share/ati/fglrx-install.log 

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.10.17-slack/build SUBDIRS=/home/pedro/Downloads/fglrx-install.edC7d7/common/lib/modules/fglrx/build_mod/2.6.x modules

make[1]: Entrando no diretório `/usr/src/linux-3.10.17'

  CC [M]  /home/pedro/Downloads/fglrx-install.edC7d7/common/lib/modules/fglrx/build_mod/2.6.x/firegl_public.o

  CC [M]  /home/pedro/Downloads/fglrx-install.edC7d7/common/lib/modules/fglrx/build_mod/2.6.x/kcl_acpi.o

/home/pedro/Downloads/fglrx-install.edC7d7/common/lib/modules/fglrx/build_mod/2.6.x/kcl_acpi.c: In function ‘KCL_ACPI_ParseTable’:

/home/pedro/Downloads/fglrx-install.edC7d7/common/lib/modules/fglrx/build_mod/2.6.x/kcl_acpi.c:999:5: warning: passing argument 1 of ‘(acpi_status (*)(u32,  void *, void *))handler’ makes integer from pointer without a cast [enabled by default]

    ((acpi_table_handler)handler)(hdr);

    ^

/home/pedro/Downloads/fglrx-install.edC7d7/common/lib/modules/fglrx/build_mod/2.6.x/kcl_acpi.c:999:5: note: expected ‘u32’ but argument is of type ‘struct acpi_table_header *’

/home/pedro/Downloads/fglrx-install.edC7d7/common/lib/modules/fglrx/build_mod/2.6.x/kcl_acpi.c:999:5: error: too few arguments to function ‘(acpi_status (*)(u32,  void *, void *))handler’

make[2]: ** [/home/pedro/Downloads/fglrx-install.edC7d7/common/lib/modules/fglrx/build_mod/2.6.x/kcl_acpi.o] Erro 1

make[1]: ** [_module_/home/pedro/Downloads/fglrx-install.edC7d7/common/lib/modules/fglrx/build_mod/2.6.x] Erro 2

make[1]: Saindo do diretório `/usr/src/linux-3.10.17'

make: ** [kmod_build] Erro 2

build failed with return value 2

ERROR: I didn't make module

[Error] Generate Package - error generating package : Slackware/Slackware

And yes I have kernel-modules and kernel-source installed.

Which driver revision did you install?

ill tryed it too.. forget it - 13.12 doesnt support slackwares (14.1 x86+x86_64) xorg version.

dont try the betadriver.. it really doesnt work so good.

im must be part happy with the radeon driver.

its all known. :)

Here's a good question:

Which video card do you have exactly?

Quote:

Originally Posted by moisespedro (Post 5103161)

I am getting this:

Code:

cat /usr/share/ati/fglrx-install.log 

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.10.17-slack/build SUBDIRS=/home/pedro/Downloads/fglrx-install.edC7d7/common/lib/modules/fglrx/build_mod/2.6.x modules

make[1]: Entrando no diretório `/usr/src/linux-3.10.17'

  CC [M]  /home/pedro/Downloads/fglrx-install.edC7d7/common/lib/modules/fglrx/build_mod/2.6.x/firegl_public.o

  CC [M]  /home/pedro/Downloads/fglrx-install.edC7d7/common/lib/modules/fglrx/build_mod/2.6.x/kcl_acpi.o

/home/pedro/Downloads/fglrx-install.edC7d7/common/lib/modules/fglrx/build_mod/2.6.x/kcl_acpi.c: In function ‘KCL_ACPI_ParseTable’:

/home/pedro/Downloads/fglrx-install.edC7d7/common/lib/modules/fglrx/build_mod/2.6.x/kcl_acpi.c:999:5: warning: passing argument 1 of ‘(acpi_status (*)(u32,  void *, void *))handler’ makes integer from pointer without a cast [enabled by default]

    ((acpi_table_handler)handler)(hdr);

    ^

/home/pedro/Downloads/fglrx-install.edC7d7/common/lib/modules/fglrx/build_mod/2.6.x/kcl_acpi.c:999:5: note: expected ‘u32’ but argument is of type ‘struct acpi_table_header *’

/home/pedro/Downloads/fglrx-install.edC7d7/common/lib/modules/fglrx/build_mod/2.6.x/kcl_acpi.c:999:5: error: too few arguments to function ‘(acpi_status (*)(u32,  void *, void *))handler’

make[2]: ** [/home/pedro/Downloads/fglrx-install.edC7d7/common/lib/modules/fglrx/build_mod/2.6.x/kcl_acpi.o] Erro 1

make[1]: ** [_module_/home/pedro/Downloads/fglrx-install.edC7d7/common/lib/modules/fglrx/build_mod/2.6.x] Erro 2

make[1]: Saindo do diretório `/usr/src/linux-3.10.17'

make: ** [kmod_build] Erro 2

build failed with return value 2

ERROR: I didn't make module

[Error] Generate Package - error generating package : Slackware/Slackware

And yes I have kernel-modules and kernel-source installed.

Looks like you are having the same issue as on this post. Try using this solution to build the fglrx modules.

I have a radeon 6670 and I will take a look at that, thanks larry

Try the free 'radeon' driver, but use it in KMS mode. Meaning:

Add the 'radeon' module explicitly to your initrd.
Remove any 'nomodeset' kernel options from lilo.conf
Eventually, use 'video=1024x768' or similar for your console.

The Arch wiki has some detailed articles about setting up the free radeon drivers with KMS. I'm using it on two machines, one with a very old (and officially unsupported) ATi card, one with a brand-new one.

Quote:

Originally Posted by Stuferus (Post 5103994)

I wonder what's wrong with the beta driver? I been using it with the 3.12 kernels and I don't have any problems.Working fine.

Well considering how ATi/AMD supports their hardware, I'm not surprised. You might have better luck with the default xorg Radeon driver in this case. Radeons support using glamouregl for 2D rendering in OpenGL and Mesa3D support through Gallium3D is progressing well for the Islands series GPUs, and the 6670 should be well supported in fact.

You should probably grab driconf from SlackBuilds.org as well.

Greetz
To be fair, although I don't know the terms of the buyout, AMD could have easily sworn off any support for any products made by Ati before the buyout and been within their rights. AMD's ATI drivers are a pita very often but they do seem to be improving some. I'm assuming they have been helpful to the boys building the Linux radeon driver because that driver has gotten GOOD! I was shocked to discover that on an ancient P4 1.8GHz box with a Radeon 9200 that I could watch youtube videos with the OS radeon driver. Kudos, fellows!

hd6850 here.. i tryed the beta driver with the default generic kernel from 14.1 x64.. for example: minecraft looks unplayable with it only artefacts.. so i reverted to the default radeon driver.. works well.. minecraft (for example) has 30fps, thats more than fine for me.

i dont think i want to compile 3.12 kernel never did in slackware so im a bit feard something could go wrong. 3.10.17 is ok.. an unofficial 3.10.27 package would be nice i must admit.

Quote:

I wonder what's wrong with the beta driver? I been using it with the 3.12 kernels and I don't have any problems.Working fine.

Probably nothing, but, with kernel 3.12.1, version 13.11v9.95 black screens and hangs the keyboard. Fortunately one can still ssh into the system. There appears to be a dmar error, related to IOMMU/vt-d. I don't know whether that's a driver fault, or a flaky bios though. The radeon drivers appear to work fine however.

Hardware behavior will vary between drivers and chipsets with different kernels. Just because a drivers works well with one chipset and a specific kernel doesn't mean the equal will apply with a different variable. AMD/ATI's proprietary drivers have been known to have issues. You probably should report these to AMD though to ensure those get patches.

I think it's safe to say if you have an issue with the FGLRX driver you should revert back to xorg-Radeon to ensure maximum compatibility.

Quote:

Originally Posted by Stuferus (Post 5104403)

<snip>
i dont think i want to compile 3.12 kernel never did in slackware so im a bit feard something could go wrong. 3.10.17 is ok.. an unofficial 3.10.27 package would be nice i must admit.

Just FTR, as long as you keep your working kernel listed in whatever bootloader you use, and simply add on any new ones, there is nothing to "go wrong". That plus using "make oldconfig" insures all of the checklist of existing settings that make your current kernel work will be automatically transposed to your new build. The kernel build will only show you new additional settings that have yet to be set, and unless you see something interesting that applies to your specific hardware that you lacked before and decide to try that, the defaults are perfectly OK.