[Solved]catalyst-rt module for realtime kernel

Hello,
I've compiled and intstalled the rtkernel with the directions posted here: http://bbs.archlinux.org/viewtopic.php?id=52201
My laptop uses an ati card and needs catalyst drivers. The fglrx module works fine with the vanilla kernel and pacman does not install it for the rt kernel(I think they are not compatible?) so I think I need the catalyst-rt module(also while installing the kernel, the pkgbuild told me that I needed catalyst-rt).
I could find no packages named catalyst-rt in the repos, but AUR database has one:
http://aur.archlinux.org/packages.php?ID=16825
But I think there is a problem with the install. After I compile the package and run it with "pacman -U", it complains about an unexpected EOF because of an unmatched quote mark. I've extracted the generated "catalyst-rt-8.5-2-i686.pkg.tar.gz" file to see if I can come up with something, there is indeed a missing quote in one of the echo statements in the contained catalyst-rt.install file. I tried fixing and retarring it but pacman complained about missing metadatas in the package. This is my 3rd day with arch(and one of those days my Internet connection was broken) so I don't have many clues.
I figure that there are very few people running ati drivers on a rt kernel here(searching for catalyst-rt yields to nothing) but maybe you can help me fix the issue myself, or maybe there is an easier way to use catalyst with an rt kernel?
Any help will be greatly appreciated. Thanks!
Last edited by pyramind (2008-07-27 18:47:04)

Ok, some more progress:
As I said, the vanilla kernel works fine with the catalyst drivers. Fully accelerated etc. When working with vanilla kernel if I say " dmesg | grep fglrx", the output is fine:
fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.
[fglrx] vendor: 1002 device: 71c5 count: 1
[fglrx] Maximum main memory to use for locked dma buffers: 1898 MBytes.
[fglrx] PAT is enabled successfully!
[fglrx] module loaded - fglrx 8.50.3 [Jun 2 2008] with 1 minors
[fglrx] Reserved FB block: Shared offset:0, size:1000000
[fglrx] Reserved FB block: Unshared offset:1000000, size:5000
[fglrx] Reserved FB block: Unshared offset:ffbf000, size:40000
[fglrx] Reserved FB block: Unshared offset:ffff000, size:1000
[fglrx] Reserved FB block: Shared offset:0, size:1000000
[fglrx] Reserved FB block: Unshared offset:1000000, size:5000
[fglrx] Reserved FB block: Unshared offset:ffbf000, size:40000
[fglrx] Reserved FB block: Unshared offset:ffff000, size:1000
As you can see, the loaded version is fglrx 8.50.3 [Jun 2 2008].
Now if I try the same on rt-kernel with catalyst-rt drivers loaded, the loaded version is shown as the incompatible fglrx 8.49.7 [May 12 2008] version.
The package PKGBUILD downloads is ati-driver-installer-8-5-x86.x86_64
So I assume that should be at least 8.5? Where does this loaded 8.49.7 come from?
I'm checking /lib/modules/<myrtkernel>/ to see if there are any other fglrx.ko floating around but there is only one, the one installed from the package built with ati-driver-installer-8-5-x86.x86_64.run
Since I'm not very competent with linux, I'm hoping some of you can show me some directions. I may try packaging a new ati driver to check but if ati-driver-installer-8-5-x86.x86_64 is actually 8.49, which one should I try then? 8-6? 8-7? I quite don't understand.
Last edited by pyramind (2008-07-27 18:24:34)

Similar Messages

Nvidia module for custom kernel

Hi all. I've compiled a custom kernel using abs according to the instructions on the wiki, but I'm having a hard time installing the nvidia module using the instructions on the Nvidia page of the wiki. The install always aborts complaining of not being able to find the kernel source. I do have the kernel-headers installed:
[root@myhost greg]# pacman -Ss linux-headers
core/linux-headers 3.1.5-1 [installed]
Header files and scripts for building modules for linux kernel
I've also edited the nvidia.install and PKGBUILD files to point to the correct version file:
[greg@myhost ~]$ cat /lib/modules/3.1.5-1-test/extramodules/version
3.1.5-1-test
I've really searched hard, but can find no remedy. Any ideas?
Thanks in advance.

From what I can see, the only installable package that was built is linux-test-3.1.5-1-x86_64.pkg.tar.xz. That's with the PKGBUILD file supplied from /var/abs/core/linux as per the wiki.
Last edited by pressman57 (2011-12-18 21:50:00)

Should modules for different kernels differ?

I'm trying to build acpi_call-git from the AUR. The build seems to go rather too smoothly. I uninstalled a custom kernel (which I only have for debugging) which leaves the standard Arch and Arch LTS kernels installed. I have the headers installed for both kernels:
$ pacman -Qs linux-[lts-]*headers
local/linux-headers 3.11.4-1
Header files and scripts for building modules for Linux kernel
local/linux-lts-headers 3.10.15-1
Header files and scripts for building modules for Linux-lts kernel
What is confusing me is that the package seems to build identical modules for the two kernels and I am not sure whether that's right:
$ diff pkg/acpi_call-git/usr/lib/modules/extramodules-3.11-ARCH/acpi_call.ko.gz pkg/acpi_call-git/usr/lib/modules/extramodules-3.10-lts/acpi_call.ko.gz
$ echo $?
0
Shouldn't there be a difference between the two? That is, I know that you typically need modules which match the kernel - otherwise the modules can't be loaded. So presumably if building module M for kernel K1 produces M1, and building module M for kernel K2 produces M2, then M1 cannot be identical with M2.
Is there a problem here or am I just horribly confused?

If the kernel functions (especially the specifications) used by acpi_call haven't changed, then the module could indeed be the same for both kernels.
You'd have to check the kernel commits for acpi related changes to be sure.

[SOLVED] Catalyst-hook won't build kernel module

I HAVE SOLVED THE PROBLEM. I WAS MISSING /usr/lib/modules/extramodules-3.11-ARCH/version !
Hello, I got a problem with my Arch Linux install. Today I got a new kernel update (Linux-3.11.1-2-ARCH) and catalyst-hook attemptet to rebuild the fglrx kernel module, but failed.
This is my /var/log/catalyst-install.log:
2013-09-25 13:09:13
Building fglrx module for 3.11.1-2-ARCH kernel ...
OsVersion says: SMP=1
file /proc/kallsyms says: SMP=1
file /usr/lib/modules/3.11.1-2-ARCH/build/include/generated/autoconf.h says: SMP=1
file /usr/lib/modules/3.11.1-2-ARCH/build/include/generated/autoconf.h says: MODVERSIONS=1
file /usr/lib/modules/3.11.1-2-ARCH/build/arch/x86/include/asm/compat.h says: COMPAT_ALLOC_USER_SPACE=arch_compat_alloc_user_sp$
make: Entering directory `/usr/src/linux-3.11.1-2-ARCH'
CC [M] /tmp/catalyst.H8Xs1y/firegl_public.o
CC [M] /tmp/catalyst.H8Xs1y/kcl_acpi.o
CC [M] /tmp/catalyst.H8Xs1y/kcl_agp.o
CC [M] /tmp/catalyst.H8Xs1y/kcl_debug.o
CC [M] /tmp/catalyst.H8Xs1y/kcl_ioctl.o
CC [M] /tmp/catalyst.H8Xs1y/kcl_io.o
CC [M] /tmp/catalyst.H8Xs1y/kcl_pci.o
CC [M] /tmp/catalyst.H8Xs1y/kcl_str.o
CC [M] /tmp/catalyst.H8Xs1y/kcl_iommu.o
CC [M] /tmp/catalyst.H8Xs1y/kcl.o
CC [M] /tmp/catalyst.H8Xs1y/kcl_wait.o
LD [M] /tmp/catalyst.H8Xs1y/fglrx.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/catalyst.H8Xs1y/fglrx.mod.o
LD [M] /tmp/catalyst.H8Xs1y/fglrx.ko
make: Leaving directory `/usr/src/linux-3.11.1-2-ARCH'
install: missing destination file operand after ‘fglrx.ko.gz’
Try 'install --help' for more information.
Please let me know if you need more information, and where/how I can get it.
Last edited by xeekei (2013-09-25 21:30:35)

Hey man have had the same issue.
How did you go about solving it?

[SOLVED] Building fglrx module for 3.11.3-1-ARCH kernel error

I got this error today:
2013-09-28 14:07:59
Building fglrx module for 3.11.2-1-ARCH kernel ...
OsVersion says: SMP=1
file /proc/kallsyms says: SMP=1
file /usr/lib/modules/3.11.2-1-ARCH/build/include/generated/autoconf.h says: SMP=1
file /usr/lib/modules/3.11.2-1-ARCH/build/include/generated/autoconf.h says: MODVERSIONS=1
file /usr/lib/modules/3.11.2-1-ARCH/build/arch/x86/include/asm/compat.h says: COMPAT_ALLOC_USER_SPACE=arch_compat_alloc_user_space
make: Entering directory `/usr/src/linux-3.11.2-1-ARCH'
CC [M] /tmp/catalyst.aHP3fa/firegl_public.o
CC [M] /tmp/catalyst.aHP3fa/kcl_acpi.o
CC [M] /tmp/catalyst.aHP3fa/kcl_agp.o
CC [M] /tmp/catalyst.aHP3fa/kcl_debug.o
CC [M] /tmp/catalyst.aHP3fa/kcl_ioctl.o
CC [M] /tmp/catalyst.aHP3fa/kcl_io.o
CC [M] /tmp/catalyst.aHP3fa/kcl_pci.o
CC [M] /tmp/catalyst.aHP3fa/kcl_str.o
CC [M] /tmp/catalyst.aHP3fa/kcl_iommu.o
CC [M] /tmp/catalyst.aHP3fa/kcl.o
CC [M] /tmp/catalyst.aHP3fa/kcl_wait.o
LD [M] /tmp/catalyst.aHP3fa/fglrx.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/catalyst.aHP3fa/fglrx.mod.o
LD [M] /tmp/catalyst.aHP3fa/fglrx.ko
make: Leaving directory `/usr/src/linux-3.11.2-1-ARCH'
Ok.
2013-10-05 14:20:34
Building fglrx module for 3.11.3-1-ARCH kernel ...
Kernel header files are absent: directory /usr/lib/modules/3.11.3-1-ARCH/build doesn't exist! Game over
2013-10-05 14:20:41
Building fglrx module for 3.11.3-1-ARCH kernel ...
Kernel header files are absent: directory /usr/lib/modules/3.11.3-1-ARCH/build doesn't exist! Game over
I don't know why, and I do not know if I care.
Last edited by patrickmaciel (2013-10-06 19:31:53)

fazo96 wrote:I think it's because of the new kernel. Reinstalling is not a solution, it's avoiding the problem ;D
Instead, I switched to catalyst-hook (I used catalyst) and upgraded to kernel 3.11.4, the latest version of xorg (there was a new one), gnome 3.10 and the module compiled perfectly, so now everything works on my system
You right, but you know... I have a lot projects in queue and not have time to search and test evertying
But, now... catalyst has installed successfully, but, I think isn't working 100%, because, when I click (for example), in a Google Chrome tab, and move to left/right, all tabs disappear or are blurry.
Anyway, thanks.

Script to easily build modules for custom kernels

I got bored, and thought of this ages ago. I have no use for it now, but i'm sure someone else will.
run:
abs-module $modulename $kernel
$modulename is any kernel module that's available in /var/abs, so if you have some that arent in a default abs, put em in /var/abs/local and they will be spotted by this.
$kernel is the name of the kernel that you want to compile for. this can be found with 'uname -r'. If $kernel is not specified, then it will default to what you are running now.
this will only work for module packages that have a variable called _kernver which sets the kernel it will be compiled for. I know all the winmodems, ATi and drivers I maintain do, not sure about some of the others. nvidia won't work.
#! /bin/bash
# Set the variables up
module="$1"
kernel="$2"
pacman="1"
current="`uname -r`"
# Check things
if [ -z "$module" ]; then
echo "No module specified"
return 1
fi
if [ -z "$kernel" ]; then
echo "No kernel specified, building for: $current"
kernel="$current"
fi
if [ ! -e "/lib/modules/$kernel/build" ]; then
echo "Specified kernel is not installed"
return 1
fi
# Check if module exists
origdir="`find /var/abs -type d -name $module`"
if [ -z "$origdir" ]; then
echo "Specified module does not exist"
return 1
fi
# Prepare to build
newdir="/var/abs/local/$module-$kernel"
if [ -d "$newdir" ]; then
rm -rf "$newdir"
fi
cp -R $origdir $newdir
cd $newdir
source PKGBUILD
if [ -z "$_kernver" ]; then
echo "PKGBUILD does not have $_kernver."
return 1
fi
sed "s/$_kernver/$kernel/g" -i PKGBUILD
sed "s/pkgname=$pkgname/pkgname=$pkgname-$kernel/g" -i PKGBUILD
# Build!
makepkg
# Post build messages/install
if [ $? = 0 ]; then
package="`find $newdir -name *pkg.tar.gz`"
# variable is at top
if [ "$pacman" = "1" ]; then
pacman -U $package
else
echo "Package is ready to install: $package"
fi
else
echo "Build failed"
fi
sorry if there's any stupid bash in there, i'm tired. and yeah, I know it's a tad verbose and spacy, but it seems to works fine.
James

Iphitus > I'm looking 4 something like your script that will allow me to load spca5xx when running my custom kernelbeyond
Unfortunetely spca5xx seems not to be manageable by your abs-module script, as its PKGBUILD doesn't have a variable called _kernver.
Log :
/usr/bin/abs-make-module spca5xx
No kernel specified, building for: 2.6.17-beyond-LLEWELLYN
PKGBUILD does not have .
/usr/bin/abs-make-module: line 52: return: can only `return' from a function or sourced script
sed: -e expression #1, char 0: no previous regular expression
==> Making package: spca5xx-2.6.17-beyond-LLEWELLYN 0.60.00-2 (Sun Jul 23 11:44:52 CEST 2006)
==> Validating source files with MD5sums
spca5xx-20060501.tar.gz ... Passed
==> Extracting Sources...
==> tar --use-compress-program=gzip -xf spca5xx-20060501.tar.gz
tar: spca5xx-20060501/drivers: implausibly old time stamp 1970-01-01 01:00:00
==> Starting build()...
./PKGBUILD: line 13: cd: /var/abs/local/spca5xx-2.6.17-beyond-LLEWELLYN/src/spca5xx-2.6.17-beyond-LLEWELLYN-20060501: No such file or directory
make: *** No targets specified and no makefile found. Stop.
==> ERROR: Build Failed. Aborting...
Build failed

[Solved] Init not found for new kernels

Hello everyone,
I am experiencing this error message when booting using either the linux-3.7.x or linux-ck-3.8.x kernels. I would investigate towards something being wrong with systemd (i.e. the init= line suggested), but the system boots perfectly fine using linux-lts-3.0.56.1.
Relevant information I can think of:
/ is ext4, LVM. The lvm -3 update has not been done yet.
mkinitcpio 0.13.0-1
I am mostly interested in any direction towards what to investigate -- the fact that there is something wrong with the init not being found, but only for certain kernels, perplexes me.
Thanks for any help,
Jan
(My apologies for the quality.)
http://i.imgur.com/Tv276ds.jpg
-- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code [jwr] --
Last edited by Zuiop (2013-03-06 20:35:51)

/usr is on /.
Here is what lsinitcpio gives me. They all include /usr/bin/init, and in fact the same init related things.
~ /boot for i in initramfs-linux-lts.img initramfs-linux.img initramfs-linux-ck.img ; do
print $i
lsinitcpio $i | grep init
done
initramfs-linux-lts.img
./init
./init_functions
./usr/bin/init
./usr/lib/udev/rules.d/11-dm-initramfs.rules
./etc/initrd-release
initramfs-linux.img
./init
./init_functions
./usr/bin/init
./usr/lib/udev/rules.d/11-dm-initramfs.rules
./etc/initrd-release
initramfs-linux-ck.img
./init
./init_functions
./usr/bin/init
./usr/lib/udev/rules.d/11-dm-initramfs.rules
./etc/initrd-release
Full output (is there a spoiler tag? couldn't find one)
http://paste.kde.org/688802/
Thanks for your continuing help!

Loading modules for old kernel during boot up

Hello
After a kernel update I noticed this message during boot
Usage: modprobe [-v] [-V] [-C config-file] [-d <dirname> ] [-n] [-i] [-q] [-b] [-o <modname>] [ --dump-modversions ] <modname> [parameters...]
modprobe -r [-n] [-i] [-v] <modulename> ...
modprobe -l -t <dirname> [ -a <modulename> ...]
And taking a look at everything.log this came out
May 24 13:57:54 localhost kernel: Pid: 1772, comm: modprobe Tainted: G C 2.6.37-ARCH #1
May 24 14:31:25 localhost kernel: Pid: 1952, comm: modprobe Tainted: G C 2.6.37-ARCH #1
May 24 14:34:45 localhost kernel: Pid: 1872, comm: modprobe Tainted: G C 2.6.37-ARCH #1
May 24 14:54:53 localhost kernel: Pid: 1966, comm: modprobe Tainted: G C 2.6.37-ARCH #1
May 24 15:14:03 localhost modprobe: FATAL: Could not load /lib/modules/2.6.37-ARCH/modules.dep: No such file or directory
Jun 13 13:34:20 localhost modprobe: FATAL: Could not load /lib/modules/2.6.38-ARCH/modules.dep: No such file or directory
I am using 2.6.39 kernel.
Could anybody help me solve this??

slytux wrote:
Samana, what does your error message say? Do you have anything in /lib/modules/2.6.39-ARCH/misc/ ?
You can also try rebuilding the initrd image as jni suggested.
mkinitcpio -p kernel26
I have no "misc" folder in 2.6.39-ARCH
The error is like a resonse from bad syntax when running a modprobe command
Usage: modprobe [-v] [-V] [-C config-file] [-d <dirname> ] [-n] [-i] [-q] [-b] [-o <modname>] [ --dump-modversions ] <modname> [parameters...]
modprobe -r [-n] [-i] [-v] <modulename> ...
modprobe -l -t <dirname> [ -a <modulename> ...]
I rebuilt the image and got a few errors in autodetect that might be a clue.
# mkinitcpio -p kernel26
==> Building image "default"
==> Running command: /sbin/mkinitcpio -k 2.6.39-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [autodetect]
WARNING: All config files need .conf: /etc/modprobe.d/oldusbload, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/oldusbload, it will be ignored in a future release.
:: Parsing hook [pata]
:: Parsing hook [scsi]
:: Parsing hook [sata]
:: Parsing hook [filesystems]
:: Generating module dependencies
:: Generating image '/boot/kernel26.img'
:: Image generation successful
==> SUCCESS
==> Building image "fallback"
==> Running command: /sbin/mkinitcpio -k 2.6.39-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26-fallback.img -S autodetect
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [pata]
:: Parsing hook [scsi]
:: Parsing hook [sata]
:: Parsing hook [filesystems]
:: Generating module dependencies
:: Generating image '/boot/kernel26-fallback.img'
:: Image generation successful
==> SUCCESS
Note that the error does not show up when I boot in fallback mode. So it looks like the error has something to do with autodetect. But I have no idea what it is. I am going to try to get rid of the oldusbload and see what happens. [NOTE: Getting rid of oldusbload did n
ot fix the error]
Last edited by Samana (2011-07-09 17:46:02)

[Solved]ATI video drivers for videocard5670 HD[Catalyst]

I have some problems with catalyst for AMD
I followed the guide on the wiki ( https://wiki.archlinux.org/index.php/AMD_Catalyst )
and when i am at
Checking operation
Assuming that a reboot to your login was successful, you can check if fglrx is running properly with the following commands:
$ lsmod | grep fglrx
$ fglrxinfo
it returns an error
[mark@Arch ~]$ lsmod | grep fglrx
[mark@Arch ~]$ fglrxinfo
X Error of failed request: BadRequest (invalid request code or no such operation)
Major opcode of failed request: 155 (ATIFGLEXTENSION)
Minor opcode of failed request: 66 ()
Serial number of failed request: 13
Current serial number in output stream: 13
[mark@Arch ~]$
The packets were grabbed with pacman from
[catalyst]
Server = http://catalyst.wirephire.com/repo/catalyst/$arch
I've blacklisted radeon from /etc/modprobe.d/modprobe.conf and it isn't loading in /etc/modules-load.d/
also added fglrx in /etc/modules-load.d/ (i think it was added by default)
Someone from romanian forums(i am romanian) suggested me to remove radeon from modules in mkintcpio (did that) and rebuilded the image after ,still no luck.
I think there's a problem with fglrx somewhere (because grep fglrx isn't returning anything.
Last edited by dede24ever (2013-10-19 17:21:35)

Ok,
1) Did you install the catalyst (which only provides the kernel modules for the kernel Vi0L0 had when building it) or do you have one of the other packages installed?
2) Which version did you install? 13.4, 13.11?
3) Did you run "sudo aticonfig --[options required]"?
4) Did you run "sudo catalyst_build_module all"?
Also, remove fglrx from /etc/modules-load-d/ . It should already be added in /etc/mkinitcpio.conf if you've done everything correctly.

Oracle firewire modules for Redhat Linux 2.6.9-34.EL

Hi,
I need oracle firewire modules for Redhat Linux 2.6.9-34.EL. Can you please help where can I find firewire modules for this kernel.
Thanks
Haranath

According to http://www.linux1394.org/download.php you should not need any additional kernel module support. You may need to install the libraw1394 RPM packages, but you can get those from your distribution media or from ULN, if your are subscribed.

Is it possible to compile NVIDIA for multiple kernels simultaneously?

Hi all,
First, the reference is http://wiki.archlinux.org/index.php/NVI … tom_kernel, as well as a small discussion I started at http://aur.archlinux.org/packages.php?ID=20410.
Basically, currently the nvidia-beta (and I'm sure the rest of the nvidia scripts) use `uname -r` to obtain the current kernel name, which is then used for the rest of the PKGBUILD. Its relatively trivial to alter that to the name of whichever kernel, meaning there's no problem compiling nvidia.ko for kernel26-ice from within kernel26 itself, and to alter the name of the package so that your nvidia-beta package does not need to be over-written (you then have two nvidia.ko, each for their own kernel.
My question is, is it possible for a single PKGBUILD to compile nvidia.ko for all kernels currently installed (probably through looking at either /lib/modules or /usr/src)? This would mean only one maintainer is needed for nvidia-beta or nvidia-17xx or whichever series, and the same PKGBUILD could be used on any system, even those with multiple kernels.
I'm not very familiar with the limitations of PKGBUILDs, or the rules governing what they may or may not do (for example, accessing and checking the machine itself outside the fakeroot?), so this may be nonsense, if so feel free to point it out. Another idea would be for a simple bash script to create as many PKGBUILDs as required, based on the most recent nvidia-beta PKGBUILD, simply sed-replacing uname -r with the appropriate kernel names and modifying the PKG name.

Hi,
it's not difficult to do but I DO NOT recommend to do it (see my notes below the code).
PKGBUILD
pkgname=nvidia-beta
pkgver=185.18.04
pkgrel=1
pkgdesc="NVIDIA beta drivers for kernel26."
arch=('i686' 'x86_64')
[ "$CARCH" = "i686" ] && ARCH=x86 && NV=0
[ "$CARCH" = "x86_64" ] && ARCH=x86_64 && NV=0
provides=(nvidia=${pkgver})
url="http://www.nvidia.com/"
depends=(kernel26 nvidia-utils-beta)
conflicts=('nvidia-96xx' 'nvidia-71xx' 'nvidia-legacy')
license=('custom')
install=('nvidia.install')
source=(ftp://download.nvidia.com/XFree86/Linux-$ARCH/${pkgver}/NVIDIA-Linux-$ARCH-${pkgver}-pkg${NV}.run)
md5sums=('95b67e6f17cc54d36ae2743df76c9f6d')
[ "$CARCH" = "x86_64" ] && md5sums=('33967a6d452c562bb8af02b0734ebf22')
build()
# Read list of installed kernels
KERNELS=`ls -1 /lib/modules`
# Extract the nvidia drivers
cd $startdir/src/
sh NVIDIA-Linux-${ARCH}-${pkgver}-pkg${NV}.run --extract-only
cd NVIDIA-Linux-${ARCH}-${pkgver}-pkg${NV}
cd usr/src/nv
ln -s Makefile.kbuild Makefile
# Now build modules for each kernel
for KERNEL in $KERNELS; do
echo "Building for ${KERNEL}"
# Compile the module
make SYSSRC=/lib/modules/${KERNEL}/build module || return 1
# Install kernel module
mkdir -p $startdir/pkg/lib/modules/${KERNEL}/kernel/drivers/video/
install -m644 nvidia.ko $startdir/pkg/lib/modules/${KERNEL}/kernel/drivers/video/ || return 1
# Clean
make clean || return 1
done;
nvidia.install
# arg 1: the new package version
post_install() {
KERNELS=`ls -1 /lib/modules`
for KERNEL in $KERNELS; do
depmod -v $KERNEL > /dev/null 2>&1
done;
# arg 1: the new package version
# arg 2: the old package version
post_upgrade() {
post_install $1
rmmod nvidia || echo 'In order to use the new nvidia module, exit Xserver and unload it manually.'
# arg 1: the old package version
post_remove() {
KERNELS=`ls -1 /lib/modules`
for KERNEL in $KERNELS; do
depmod -v $KERNEL > /dev/null 2>&1
done;
op=$1
shift
$op $*
PS: I haven't test it because I don't use multiple kernels
But be aware of possible problems. Some modifications may influence kernel functionalities, so once you compile a driver for kernel26-xyz on kernel26-zyx the module may not work on kernel26-xyz or may cause unexpected issues.
You also should not (you possibly even won't be able to) build module for different release version (eg. build for 2.6.28 on 2.6.29) due changes in kernel headers.
I'm also not sure if it is safe to generate module dependencies for another kernel then you are currently running.
As you can see above, it is not problem to make such a PKGBUILD, but it also brings too many problems and it's too dangerous that it is better to stay at current model "module package for each kernel". So if you want to you may try to use this PKGBUILD, but I strictly warn everyone else that it may cause more harm then use so don't blame me if something goes wrong. You were warned .
Last edited by ProgDan (2009-04-30 13:48:06)

[Solved] Catalyst fails to load kernel module

I have just been through the Catalyst install guide, I installed from the Vi0L0 repos rather than building myself.
Everything appeared to go fine, however fglrx fails to load when I reboot. The xorg log contains;
fglrx(0): atiddxDriScreenInit failed. Probably kernel module missing or incompatible
fglrx(0): **********************************************************
fglrx(0): * DRI initialization failed
fglrx(0): * kernel module (fglrx.ko) may be missing or incompatible
fglrx(0): * 2D and 3D acceleration disabled
fglrx(0): **********************************************************
Is this recoverable? Or does this mean that the current Vi0L0 module has not been built for my kernel (3.11.5-1-ARCH)?
Last edited by ~lynks (2013-11-03 16:16:00)

This issue has now been resolved after the update to xorg 1.14
lsmod | grep fglrx
shows fglrx is not loaded, and:
modprobe fglrx
returns with;
modprobe: ERROR: could not insert 'fglrx': Exec format error
Does that indicate a 32/64 bit issue?
This issue has now been resolved after the update to xorg 1.14
Last edited by ~lynks (2013-11-03 16:15:48)

[SOLVED] Can't build fglrx module for 3.4.5-1-ARCH kernel

Hello everyone!
I updated my system using
pacman -Syu --ignore glibc
everything was good, I rebooted and my fglrx module isn't working!
I tried:
sudo catalyst_build_module
Building fglrx module for 3.4.5-1-ARCH kernel ...
Failed!!! Check out log: /var/log/catalyst-install.log
Here is log
Here is quote from it: Kernel header files are absent: directory /lib/modules/3.3.4-1-ARCH/build doesn't exist! Game over
But I have the latest versions linux and linux-headers packages.
Help please. Thanks.
Last edited by metalex (2012-07-20 14:53:37)

Yes, this is my problem, I did all from here, but I still can't update glibc.
grep '^lib/' /var/lib/pacman/local/*/files
output:
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/ld-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/ld-linux-x86-64.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libBrokenLocale-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libBrokenLocale.so.1
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libSegFault.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libanl-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libanl.so.1
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libc-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libc.so.6
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libcidn-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libcidn.so.1
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libcrypt-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libcrypt.so.1
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libdl-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libdl.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libm-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libm.so.6
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libmemusage.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnsl-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnsl.so.1
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_compat-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_compat.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_db-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_db.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_dns-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_dns.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_files-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_files.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_hesiod-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_hesiod.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_nis-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_nis.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_nisplus-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_nisplus.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libpcprofile.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libpthread-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libpthread.so.0
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libresolv-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libresolv.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/librt-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/librt.so.1
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libthread_db-1.0.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libthread_db.so.1
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libutil-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libutil.so.1
/var/lib/pacman/local/lib32-glibc-2.15-10/files:lib/
/var/lib/pacman/local/lib32-glibc-2.15-10/files:lib/ld-linux.so.2
I don't know what to do with lib32-glibc...

[solved] catalyst: Building fglrx module for 3.0-ARCH failing

I'm running Arch on my laptop since some time now.
Lately I've done some updates and encountered a problem with my ati (catalyst driver).
Everytime the auto-build module tries to compile, I'm getting an error:
$ sudo catalyst_build_module allg
Building fglrx module for 3.0-ARCH kernel ...
Failed!!! Check out log: /var/log/catalyst-install.log
this is what gets logged:
2011-08-29 15:52:07
Building fglrx module for 3.0-ARCH kernel ...
Kernel header files are absent: directory /lib/modules/3.0-ARCH/build doesn't exist! Game over
I checked it and that build directory is obviously really missing.
I appreciate any help from you guys, since it's really odd to work on this laptop without the correct graphics drivers..
this is my video card:
# lspci -v | grep "VGA"
01:00.0 VGA compatible controller: ATI Technologies Inc Redwood [Radeon HD 5600 Series] (prog-if 00 [VGA controller])
please let me know if you need more information and thanks in advance for your help!
Last edited by derblub (2011-08-29 16:39:22)

well, ok - this was too oblivious now
thank you very much!

[Solved] Can not build modules for VMware Player after kernel updates

I have a problem generating the modules for VMware Player after kernel updates. I am using VMware Player version 5.02 (without patches) and the softlink according to the Wiki.
When I start the installation of the modules from the GUI, the program just closes. Running vmware-modconfig in the CLI generates the following log file:
2013-04-29T09:49:27.891+01:00| vthread-3| I120: Log for VMware Workstation pid=7478 version=9.0.2 build=build-1031769 option=Release
2013-04-29T09:49:27.891+01:00| vthread-3| I120: The process is 64-bit.
2013-04-29T09:49:27.891+01:00| vthread-3| I120: Host codepage=UTF-8 encoding=UTF-8
2013-04-29T09:49:27.891+01:00| vthread-3| I120: Host is Linux 3.8.10-1-ARCH 2012.11.29
2013-04-29T09:49:27.891+01:00| vthread-3| I120: Msg_Reset:
2013-04-29T09:49:27.891+01:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": Datei oder Verzeichnis nicht gefunden.
2013-04-29T09:49:27.891+01:00| vthread-3| I120: ----------------------------------------
2013-04-29T09:49:27.891+01:00| vthread-3| I120: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.
2013-04-29T09:49:27.891+01:00| vthread-3| I120: Msg_Reset:
2013-04-29T09:49:27.891+01:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/config": Datei oder Verzeichnis nicht gefunden.
2013-04-29T09:49:27.891+01:00| vthread-3| I120: ----------------------------------------
2013-04-29T09:49:27.891+01:00| vthread-3| I120: PREF Optional preferences file not found at /root/.vmware/config. Using default values.
2013-04-29T09:49:27.891+01:00| vthread-3| W110: Logging to /tmp/vmware-root/vmware-modconfig-7478.log
2013-04-29T09:49:27.892+01:00| vthread-3| W110: Icon name must be set.
Interestingly, after deinstallation and reinstallation the VMWare Player works fine.
Any hint, what's going wrong?
Last edited by Thomas_Do (2013-08-07 07:25:51)

Today, (Kernel 3.10.5-1, VMware Player version 5.02 with kernel patches) the modules could successful be generated from the CLI:
vmware-modconfig --console --install-all
Solved (somehow).

[Solved]catalyst-rt module for realtime kernel

Similar Messages

Maybe you are looking for