Vbox Kernel Module and .24

Hi,
does someone else have the problem that he isn't able to build the virtualbox kernel module with the .24 kernel?
[root@arch holger]# vbox_build_module
Building Virtualbox-1.5.2 kernel modules for kernel 2.6.24-ARCH #1 SMP PREEMPT Sun Feb 10 15:21:33 UTC 2008
for f in . linux r0drv r0drv/linux; do rm -f $f/*.o $f/.*.cmd $f/.*.flags; done
rm -rf .vboxdrv* .tmp_ver* vboxdrv.* Module.symvers Modules.symvers
make KBUILD_VERBOSE=1 -C /lib/modules/2.6.24-ARCH/build SUBDIRS=/opt/VirtualBox-1.5.2/src SRCROOT=/opt/VirtualBox-1.5.2/src modules
make[1]: Entering directory `/usr/src/linux-2.6.24-ARCH'
test -e include/linux/autoconf.h -a -e include/config/auto.conf || ( \
echo; \
echo " ERROR: Kernel configuration is invalid."; \
echo " include/linux/autoconf.h or include/config/auto.conf are missing."; \
echo " Run 'make oldconfig && make prepare' on kernel src to fix it."; \
echo; \
/bin/false)
mkdir -p /opt/VirtualBox-1.5.2/src/.tmp_versions ; rm -f /opt/VirtualBox-1.5.2/src/.tmp_versions/*
make -f scripts/Makefile.build obj=/opt/VirtualBox-1.5.2/src
gcc -m32 -Wp,-MD,/opt/VirtualBox-1.5.2/src/linux/.SUPDrv-linux.o.d -nostdinc -isystem /usr/lib/gcc/i686-pc-linux-gnu/4.2.3/include -D__KERNEL__ -Iinclude -include include/linux/autoconf.h -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -O2 -pipe -msoft-float -mregparm=3 -freg-struct-return -mpreferred-stack-boundary=2 -march=i686 -mtune=generic -ffreestanding -maccumulate-outgoing-args -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -Iinclude/asm-x86/mach-default -fomit-frame-pointer -fno-stack-protector -Wdeclaration-after-statement -Wno-pointer-sign -I/lib/modules/2.6.24-ARCH/build/include -I/opt/VirtualBox-1.5.2/src/ -I/opt/VirtualBox-1.5.2/src/include -I/opt/VirtualBox-1.5.2/src/r0drv/linux -D__KERNEL__ -DMODULE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DCONFIG_VBOXDRV_AS_MISC -DRT_ARCH_X86 -DVBOX_WITHOUT_IDT_PATCHING -DUSE_NEW_OS_INTERFACE_FOR_MM -DMODULE -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(SUPDrv_linux)" -D"KBUILD_MODNAME=KBUILD_STR(vboxdrv)" -c -o /opt/VirtualBox-1.5.2/src/linux/SUPDrv-linux.o /opt/VirtualBox-1.5.2/src/linux/SUPDrv-linux.c
In file included from /opt/VirtualBox-1.5.2/src/include/iprt/types.h:72,
from /opt/VirtualBox-1.5.2/src/include/VBox/types.h:21,
from /opt/VirtualBox-1.5.2/src/SUPDRV.h:26,
from /opt/VirtualBox-1.5.2/src/linux/SUPDrv-linux.c:22:
include/linux/types.h:40: Fehler: Redefinition des typedef »uintptr_t«
/opt/VirtualBox-1.5.2/src/include/iprt/stdint.h:118: Fehler: Vorherige Deklaration von »uintptr_t« war hier
In Datei, eingefügt von include/linux/thread_info.h:33,
von include/linux/preempt.h:9,
von include/linux/spinlock.h:49,
von /opt/VirtualBox-1.5.2/src/SUPDRV.h:87,
von /opt/VirtualBox-1.5.2/src/linux/SUPDrv-linux.c:22:
include/linux/bitops.h:6:1: Warnung: »BIT« redefiniert
In Datei, eingefügt von /opt/VirtualBox-1.5.2/src/include/VBox/cdefs.h:20,
von /opt/VirtualBox-1.5.2/src/SUPDRV.h:25,
von /opt/VirtualBox-1.5.2/src/linux/SUPDrv-linux.c:22:
/opt/VirtualBox-1.5.2/src/include/iprt/cdefs.h:1042:1: Warnung: dies ist die Stelle der vorherigen Definition
make[2]: *** [/opt/VirtualBox-1.5.2/src/linux/SUPDrv-linux.o] Fehler 1
make[1]: *** [_module_/opt/VirtualBox-1.5.2/src] Fehler 2
make[1]: Leaving directory `/usr/src/linux-2.6.24-ARCH'
make: *** [vboxdrv] Fehler 2

ise wrote:Solution is here: http://bbs.archlinux.org/viewtopic.php?id=43709
or install virtualbox-modules from aur

Similar Messages

Questions: On NVIDIA Kernel module and install process

Hi everyone,
I have a PCIe 7600 GT card, and trying to get it to work in its full power.
So far I have not succeeded, and condemned to run in VESA mode. But have one more try to do following the advisory of upgrading kernel and reinstalling the Nvidia driver.
I have few questions though:
- I know my kernel as 2.6.15-ARCH (from the dir in /usr/src), but in the above mentioned advisory, there were more digits after ("2.6.16.14-1"). Where in my system, I can locate those micro version numbers, if I need to?
- My not-yet-working Nvidia driver insrtall (from [testing]) left a kernel module with "agp" in the name. Is it the way it should be, taking into account that I have a PCIe card? Or is this pointing to an install problem?
- I have browsed the stuff in the 8756 vintage of the Nvidia driver, and noticed that there are references to X11R6 which I do not have (have an X R7 Xorg). Which one of the driver-install-script or Arch-PKGBUILD-file has the intelligence to place the files correctly in R6 and R7 installs?
- The 8756 text also refers to nvidia-xconfig utility, and I did use it in my 64-bit Gentoo install. In my Arch install it is no where to be found. Again, is this pointing to an install problem?
Thanks,

1.
pacman -Q kernel26
will give you the minor numbers
2. no clue
3. the 8751 driver works fine with xorg 7, so i presume the new one should work also.
4. no clue
as an alternative to VESA :
pacman -S xf86-video-nv
this will install the open source nvidia driver. It supports only 2D acceleration, but should improve your screen a lot over standard VESA.
put
Driver "nv"
in your device section in xorg.conf to enable it.

Unable to load the kernel module 'nvidia.ko' [SOLVED]

After my most recent kernel upgrade, I can't get my GUI to run. I've tried reinstalling the nvidia driver to no avail.
Any insight would be greatly appreciated. I'm using a GeForce 8400 GS
cat /var/log/nvidia-installer.log
ERROR: Unable to load the kernel module 'nvidia.ko'. This happens most
frequently when this kernel module was built against the wrong or
improperly configured kernel sources, with a version of gcc that differs
from the one used to build the target kernel, or if a driver such as
rivafb/nvidiafb is present and prevents the NVIDIA kernel module from
obtaining ownership of the NVIDIA graphics device(s), or NVIDIA GPU
installed in this system is not supported by this NVIDIA Linux graphics
driver release.
Please see the log entries 'Kernel module load error' and 'Kernel
messages' at the end of the file '/var/log/nvidia-installer.log' for
more information.
-> Kernel module load error: insmod: error inserting './usr/src/nv/nvidia.ko':
-1 No such device
-> Kernel messages:
NVRM: This can occur when a driver such as nouveau, rivafb,
NVRM: nvidiafb, or rivatv was loaded and obtained ownership of
NVRM: the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA graphics adapter probed!
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as nouveau, rivafb,
NVRM: nvidiafb, or rivatv was loaded and obtained ownership of
NVRM: the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA graphics adapter probed!
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as rivafb, nvidiafb or
NVRM: rivatv was loaded and obtained ownership of the NVIDIA
NVRM: device(s).
NVRM: Try unloading the rivafb, nvidiafb or rivatv kernel module
NVRM: (and/or reconfigure your kernel without rivafb/nvidiafb
NVRM: support), then try loading the NVIDIA kernel module again.
NVRM: No NVIDIA graphics adapter probed!
ERROR: Installation has failed. Please see the file
'/var/log/nvidia-installer.log' for details. You may find suggestions
on fixing installation problems in the README available on the Linux
driver download page at www.nvidia.com.
Last edited by wsims (2010-06-22 15:06:04)

if you used the packages from repos, the blacklist is done automatically in nvidia,
$ pacman -Qo /etc/modprobe.d/nouveau_blacklist.conf
/etc/modprobe.d/nouveau_blacklist.conf is owned by nvidia 195.36.31-1
$ cat /etc/modprobe.d/nouveau_blacklist.conf
blacklist nouveau
but i guess you just want to mess your system by using unsupported and very bad ways and you are way smarter than the devs if you used that installer
Last edited by wonder (2010-06-22 14:10:01)

[Solved]Failed to start Load Kernel Modules

When I boot up Arch it says that it Failed to start Load Kernel Modules and when I get into my Desktop, the screen is tearing.
Using the latest kernel with i3wm
my systemctl status systemd-modules-load
● systemd-modules-load.service - Load Kernel Modules
Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static)
Active: failed (Result: exit-code) since Sat 2014-09-20 17:28:06 PDT; 5min ago
Docs: man:systemd-modules-load.service(8)
man:modules-load.d(5)
Process: 144 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
Main PID: 144 (code=exited, status=1/FAILURE)
Sep 20 17:28:06 green systemd-modules-load[144]: Failed to insert 'fglrx': Invalid argument
Sep 20 17:28:06 green systemd[1]: systemd-modules-load.service: main process exited, code=exited, status=1/FAILURE
Sep 20 17:28:06 green systemd[1]: Failed to start Load Kernel Modules.
Sep 20 17:28:06 green systemd[1]: Unit systemd-modules-load.service entered failed state.
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
Last edited by Green (2014-09-21 07:31:08)

anatolik wrote:
It looks like it is unable to load fglrx.
Do you have any fglrx specific configuration? Do you have anything in your /etc/modprobe.d ?
Could it be that fglrx is compiled for previous versions of kernel and this is a problem?
I don't have any specific fglrx configuration and in /etc/modprobe.d/ I have a file called modprobe.conf that contains
blacklist radeon
fglrx
I dont think fglrx was compiled for previous versions of the kernel because I used the kernel that the latest release contained. My kernel version is 3.16.3-1.
Last edited by Green (2014-09-21 05:44:03)

VMware keeps Rebuilding Kernel Modules [Solved]

Hi, and thanks. After the last kernel upgrade everytime I start vmware player the first instance to run will rebuild the kernel modules and there is a warning icon next to the "Blocking File System" entry in the build list. I am using the latest kernel 3.4.2.2-Arch, my vmware player is version 4.0.2 build-591240. It runs fine after it rebuilds but the warning icon has me concerned. Does anyone know what this is? Do I have to move up a vmware version?
thanks in advance for your help.
--jerry
Last edited by jk121960 (2012-06-27 20:04:08)

If anyone is interested, here is the complete console output when I run the player.
$ vmplayer
Logging to /tmp/vmware-citmkd/modconfig-9164.log
HostinfoReadDistroFile: could not open file/etc/redhat-release: 2
HostinfoReadDistroFile: could not open file/etc/redhat_version: 2
HostinfoReadDistroFile: could not open file/etc/sun-release: 2
HostinfoReadDistroFile: could not open file/etc/SuSE-release: 2
HostinfoReadDistroFile: could not open file/etc/novell-release: 2
HostinfoReadDistroFile: could not open file/etc/sles-release: 2
HostinfoReadDistroFile: could not open file/etc/debian_version: 2
HostinfoReadDistroFile: could not open file/etc/debian_release: 2
HostinfoReadDistroFile: could not open file/etc/mandrake-release: 2
HostinfoReadDistroFile: could not open file/etc/mandriva-release: 2
HostinfoReadDistroFile: could not open file/etc/mandrakelinux-release: 2
HostinfoReadDistroFile: could not open file/etc/turbolinux-release: 2
HostinfoReadDistroFile: could not open file/etc/fedora-release: 2
HostinfoReadDistroFile: could not open file/etc/gentoo-release: 2
HostinfoReadDistroFile: could not open file/etc/nld-release: 2
HostinfoReadDistroFile: could not open file/etc/lsb-release: 2
HostinfoReadDistroFile: could not open file/etc/annvix-release: 2
HostinfoReadDistroFile: Cannot work with empty file.
HostinfoReadDistroFile: could not open file/etc/arklinux-release: 2
HostinfoReadDistroFile: could not open file/etc/aurox-release: 2
HostinfoReadDistroFile: could not open file/etc/blackcat-release: 2
HostinfoReadDistroFile: could not open file/etc/cobalt-release: 2
HostinfoReadDistroFile: could not open file/etc/conectiva-release: 2
HostinfoReadDistroFile: could not open file/etc/immunix-release: 2
HostinfoReadDistroFile: could not open file/etc/knoppix_version: 2
HostinfoReadDistroFile: could not open file/etc/lfs-release: 2
HostinfoReadDistroFile: could not open file/etc/linuxppc-release: 2
HostinfoReadDistroFile: could not open file/etc/mklinux-release: 2
HostinfoReadDistroFile: could not open file/etc/pld-release: 2
HostinfoReadDistroFile: could not open file/etc/slackware-version: 2
HostinfoReadDistroFile: could not open file/etc/slackware-release: 2
HostinfoReadDistroFile: could not open file/etc/e-smith-release: 2
HostinfoReadDistroFile: could not open file/etc/release: 2
HostinfoReadDistroFile: could not open file/etc/tinysofa-release: 2
HostinfoReadDistroFile: could not open file/etc/ultrapenguin-release: 2
HostinfoReadDistroFile: could not open file/etc/UnitedLinux-release: 2
HostinfoReadDistroFile: could not open file/etc/va-release: 2
HostinfoReadDistroFile: could not open file/etc/yellowdog-release: 2
HostinfoOSData: Error: no distro file found
filename: /lib/modules/3.4.4-2-ARCH/misc/vmmon.ko
supported: external
license: GPL v2
description: VMware Virtual Machine Monitor.
author: VMware, Inc.
depends:
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
filename: /lib/modules/3.4.4-2-ARCH/misc/vmnet.ko
supported: external
license: GPL v2
description: VMware Virtual Networking Driver.
author: VMware, Inc.
depends:
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
ERROR: Module vmblock not found.
filename: /lib/modules/3.4.4-2-ARCH/misc/vmci.ko
supported: external
license: GPL v2
version: 9.1.18.0
description: VMware Virtual Machine Communication Interface (VMCI).
author: VMware, Inc.
srcversion: F659B534EA5CC5FFD4A08BF
alias: pci:v000015ADd00000740sv*sd*bc*sc*i*
depends:
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
parm: disable_host:Disable driver host personality - (default=0) (bool)
parm: disable_guest:Disable driver guest personality - (default=0) (bool)
parm: disable_msi:Disable MSI use in driver - (default=0) (bool)
parm: disable_msix:Disable MSI-X use in driver - (default=0) (bool)
filename: /lib/modules/3.4.4-2-ARCH/misc/vsock.ko
supported: external
alias: vmware_vsock
license: GPL v2
version: 9.1.1.0
description: VMware Virtual Socket Family
author: VMware, Inc.
srcversion: 5A37036862692504058A712
depends: vmci
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
filename: /lib/modules/3.4.4-2-ARCH/misc/vmmon.ko
supported: external
license: GPL v2
description: VMware Virtual Machine Monitor.
author: VMware, Inc.
depends:
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
filename: /lib/modules/3.4.4-2-ARCH/misc/vmnet.ko
supported: external
license: GPL v2
description: VMware Virtual Networking Driver.
author: VMware, Inc.
depends:
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
ERROR: Module vmblock not found.
filename: /lib/modules/3.4.4-2-ARCH/misc/vmci.ko
supported: external
license: GPL v2
version: 9.1.18.0
description: VMware Virtual Machine Communication Interface (VMCI).
author: VMware, Inc.
srcversion: F659B534EA5CC5FFD4A08BF
alias: pci:v000015ADd00000740sv*sd*bc*sc*i*
depends:
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
parm: disable_host:Disable driver host personality - (default=0) (bool)
parm: disable_guest:Disable driver guest personality - (default=0) (bool)
parm: disable_msi:Disable MSI use in driver - (default=0) (bool)
parm: disable_msix:Disable MSI-X use in driver - (default=0) (bool)
filename: /lib/modules/3.4.4-2-ARCH/misc/vsock.ko
supported: external
alias: vmware_vsock
license: GPL v2
version: 9.1.1.0
description: VMware Virtual Socket Family
author: VMware, Inc.
srcversion: 5A37036862692504058A712
depends: vmci
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
filename: /lib/modules/3.4.4-2-ARCH/misc/vmmon.ko
supported: external
license: GPL v2
description: VMware Virtual Machine Monitor.
author: VMware, Inc.
depends:
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
filename: /lib/modules/3.4.4-2-ARCH/misc/vmnet.ko
supported: external
license: GPL v2
description: VMware Virtual Networking Driver.
author: VMware, Inc.
depends:
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
ERROR: Module vmblock not found.
filename: /lib/modules/3.4.4-2-ARCH/misc/vmci.ko
supported: external
license: GPL v2
version: 9.1.18.0
description: VMware Virtual Machine Communication Interface (VMCI).
author: VMware, Inc.
srcversion: F659B534EA5CC5FFD4A08BF
alias: pci:v000015ADd00000740sv*sd*bc*sc*i*
depends:
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
parm: disable_host:Disable driver host personality - (default=0) (bool)
parm: disable_guest:Disable driver guest personality - (default=0) (bool)
parm: disable_msi:Disable MSI use in driver - (default=0) (bool)
parm: disable_msix:Disable MSI-X use in driver - (default=0) (bool)
filename: /lib/modules/3.4.4-2-ARCH/misc/vsock.ko
supported: external
alias: vmware_vsock
license: GPL v2
version: 9.1.1.0
description: VMware Virtual Socket Family
author: VMware, Inc.
srcversion: 5A37036862692504058A712
depends: vmci
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
filename: /lib/modules/3.4.4-2-ARCH/misc/vmmon.ko
supported: external
license: GPL v2
description: VMware Virtual Machine Monitor.
author: VMware, Inc.
depends:
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
filename: /lib/modules/3.4.4-2-ARCH/misc/vmnet.ko
supported: external
license: GPL v2
description: VMware Virtual Networking Driver.
author: VMware, Inc.
depends:
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
ERROR: Module vmblock not found.
filename: /lib/modules/3.4.4-2-ARCH/misc/vmci.ko
supported: external
license: GPL v2
version: 9.1.18.0
description: VMware Virtual Machine Communication Interface (VMCI).
author: VMware, Inc.
srcversion: F659B534EA5CC5FFD4A08BF
alias: pci:v000015ADd00000740sv*sd*bc*sc*i*
depends:
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
parm: disable_host:Disable driver host personality - (default=0) (bool)
parm: disable_guest:Disable driver guest personality - (default=0) (bool)
parm: disable_msi:Disable MSI use in driver - (default=0) (bool)
parm: disable_msix:Disable MSI-X use in driver - (default=0) (bool)
filename: /lib/modules/3.4.4-2-ARCH/misc/vsock.ko
supported: external
alias: vmware_vsock
license: GPL v2
version: 9.1.1.0
description: VMware Virtual Socket Family
author: VMware, Inc.
srcversion: 5A37036862692504058A712
depends: vmci
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
filename: /lib/modules/3.4.4-2-ARCH/misc/vmmon.ko
supported: external
license: GPL v2
description: VMware Virtual Machine Monitor.
author: VMware, Inc.
depends:
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
filename: /lib/modules/3.4.4-2-ARCH/misc/vmnet.ko
supported: external
license: GPL v2
description: VMware Virtual Networking Driver.
author: VMware, Inc.
depends:
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
ERROR: Module vmblock not found.
filename: /lib/modules/3.4.4-2-ARCH/misc/vmci.ko
supported: external
license: GPL v2
version: 9.1.18.0
description: VMware Virtual Machine Communication Interface (VMCI).
author: VMware, Inc.
srcversion: F659B534EA5CC5FFD4A08BF
alias: pci:v000015ADd00000740sv*sd*bc*sc*i*
depends:
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
parm: disable_host:Disable driver host personality - (default=0) (bool)
parm: disable_guest:Disable driver guest personality - (default=0) (bool)
parm: disable_msi:Disable MSI use in driver - (default=0) (bool)
parm: disable_msix:Disable MSI-X use in driver - (default=0) (bool)
filename: /lib/modules/3.4.4-2-ARCH/misc/vsock.ko
supported: external
alias: vmware_vsock
license: GPL v2
version: 9.1.1.0
description: VMware Virtual Socket Family
author: VMware, Inc.
srcversion: 5A37036862692504058A712
depends: vmci
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
(vmware-gksu:9164): GLib-GObject-WARNING **: Two different plugins tried to register 'BasicEngineFc'.
(vmware-gksu:9164): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
(vmware-gksu:9164): Pango-WARNING **: Failed to load Pango module '/usr/lib/vmware/libconf/lib/pango/1.6.0/modules/pango-basic-fc.so' for id 'BasicScriptEngineFc'
(vmware-gksu:9164): GLib-GObject-WARNING **: Two different plugins tried to register 'BasicEngineFc'.
(vmware-gksu:9164): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
(vmware-gksu:9164): GLib-GObject-WARNING **: Two different plugins tried to register 'BasicEngineFc'.
(vmware-gksu:9164): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
(vmware-gksu:9164): GLib-GObject-WARNING **: Two different plugins tried to register 'BasicEngineFc'.
(vmware-gksu:9164): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
(vmware-gksu:9164): GLib-GObject-WARNING **: Two different plugins tried to register 'BasicEngineFc'.
(vmware-gksu:9164): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
(vmware-gksu:9164): GLib-GObject-WARNING **: Two different plugins tried to register 'BasicEngineFc'.
(vmware-gksu:9164): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
(vmware-gksu:9164): GLib-GObject-WARNING **: Two different plugins tried to register 'BasicEngineFc'.
(vmware-gksu:9164): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
(vmware-gksu:9164): GLib-GObject-WARNING **: Two different plugins tried to register 'BasicEngineFc'.
(vmware-gksu:9164): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
(vmware-gksu:9164): GLib-GObject-WARNING **: Two different plugins tried to register 'BasicEngineFc'.
(vmware-gksu:9164): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
(vmware-gksu:9164): GLib-GObject-WARNING **: Two different plugins tried to register 'BasicEngineFc'.
(vmware-gksu:9164): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
(vmware-gksu:9164): GLib-GObject-WARNING **: Two different plugins tried to register 'BasicEngineFc'.
(vmware-gksu:9164): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
(vmware-gksu:9164): GLib-GObject-WARNING **: Two different plugins tried to register 'BasicEngineFc'.
(vmware-gksu:9164): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
(vmware-gksu:9164): GLib-GObject-WARNING **: Two different plugins tried to register 'BasicEngineFc'.
(vmware-gksu:9164): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
(vmware-gksu:9164): GLib-GObject-WARNING **: Two different plugins tried to register 'BasicEngineFc'.
(vmware-gksu:9164): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
Logging to /tmp/vmware-root/modconfig-9275.log
HostinfoReadDistroFile: could not open file/etc/redhat-release: 2
HostinfoReadDistroFile: could not open file/etc/redhat_version: 2
HostinfoReadDistroFile: could not open file/etc/sun-release: 2
HostinfoReadDistroFile: could not open file/etc/SuSE-release: 2
HostinfoReadDistroFile: could not open file/etc/novell-release: 2
HostinfoReadDistroFile: could not open file/etc/sles-release: 2
HostinfoReadDistroFile: could not open file/etc/debian_version: 2
HostinfoReadDistroFile: could not open file/etc/debian_release: 2
HostinfoReadDistroFile: could not open file/etc/mandrake-release: 2
HostinfoReadDistroFile: could not open file/etc/mandriva-release: 2
HostinfoReadDistroFile: could not open file/etc/mandrakelinux-release: 2
HostinfoReadDistroFile: could not open file/etc/turbolinux-release: 2
HostinfoReadDistroFile: could not open file/etc/fedora-release: 2
HostinfoReadDistroFile: could not open file/etc/gentoo-release: 2
HostinfoReadDistroFile: could not open file/etc/nld-release: 2
HostinfoReadDistroFile: could not open file/etc/lsb-release: 2
HostinfoReadDistroFile: could not open file/etc/annvix-release: 2
HostinfoReadDistroFile: Cannot work with empty file.
HostinfoReadDistroFile: could not open file/etc/arklinux-release: 2
HostinfoReadDistroFile: could not open file/etc/aurox-release: 2
HostinfoReadDistroFile: could not open file/etc/blackcat-release: 2
HostinfoReadDistroFile: could not open file/etc/cobalt-release: 2
HostinfoReadDistroFile: could not open file/etc/conectiva-release: 2
HostinfoReadDistroFile: could not open file/etc/immunix-release: 2
HostinfoReadDistroFile: could not open file/etc/knoppix_version: 2
HostinfoReadDistroFile: could not open file/etc/lfs-release: 2
HostinfoReadDistroFile: could not open file/etc/linuxppc-release: 2
HostinfoReadDistroFile: could not open file/etc/mklinux-release: 2
HostinfoReadDistroFile: could not open file/etc/pld-release: 2
HostinfoReadDistroFile: could not open file/etc/slackware-version: 2
HostinfoReadDistroFile: could not open file/etc/slackware-release: 2
HostinfoReadDistroFile: could not open file/etc/e-smith-release: 2
HostinfoReadDistroFile: could not open file/etc/release: 2
HostinfoReadDistroFile: could not open file/etc/tinysofa-release: 2
HostinfoReadDistroFile: could not open file/etc/ultrapenguin-release: 2
HostinfoReadDistroFile: could not open file/etc/UnitedLinux-release: 2
HostinfoReadDistroFile: could not open file/etc/va-release: 2
HostinfoReadDistroFile: could not open file/etc/yellowdog-release: 2
HostinfoOSData: Error: no distro file found
filename: /lib/modules/3.4.4-2-ARCH/misc/vmmon.ko
supported: external
license: GPL v2
description: VMware Virtual Machine Monitor.
author: VMware, Inc.
depends:
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
filename: /lib/modules/3.4.4-2-ARCH/misc/vmnet.ko
supported: external
license: GPL v2
description: VMware Virtual Networking Driver.
author: VMware, Inc.
depends:
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
ERROR: Module vmblock not found.
filename: /lib/modules/3.4.4-2-ARCH/misc/vmci.ko
supported: external
license: GPL v2
version: 9.1.18.0
description: VMware Virtual Machine Communication Interface (VMCI).
author: VMware, Inc.
srcversion: F659B534EA5CC5FFD4A08BF
alias: pci:v000015ADd00000740sv*sd*bc*sc*i*
depends:
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
parm: disable_host:Disable driver host personality - (default=0) (bool)
parm: disable_guest:Disable driver guest personality - (default=0) (bool)
parm: disable_msi:Disable MSI use in driver - (default=0) (bool)
parm: disable_msix:Disable MSI-X use in driver - (default=0) (bool)
filename: /lib/modules/3.4.4-2-ARCH/misc/vsock.ko
supported: external
alias: vmware_vsock
license: GPL v2
version: 9.1.1.0
description: VMware Virtual Socket Family
author: VMware, Inc.
srcversion: 5A37036862692504058A712
depends: vmci
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
filename: /lib/modules/3.4.4-2-ARCH/misc/vmmon.ko
supported: external
license: GPL v2
description: VMware Virtual Machine Monitor.
author: VMware, Inc.
depends:
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
filename: /lib/modules/3.4.4-2-ARCH/misc/vmnet.ko
supported: external
license: GPL v2
description: VMware Virtual Networking Driver.
author: VMware, Inc.
depends:
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
ERROR: Module vmblock not found.
filename: /lib/modules/3.4.4-2-ARCH/misc/vmci.ko
supported: external
license: GPL v2
version: 9.1.18.0
description: VMware Virtual Machine Communication Interface (VMCI).
author: VMware, Inc.
srcversion: F659B534EA5CC5FFD4A08BF
alias: pci:v000015ADd00000740sv*sd*bc*sc*i*
depends:
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
parm: disable_host:Disable driver host personality - (default=0) (bool)
parm: disable_guest:Disable driver guest personality - (default=0) (bool)
parm: disable_msi:Disable MSI use in driver - (default=0) (bool)
parm: disable_msix:Disable MSI-X use in driver - (default=0) (bool)
filename: /lib/modules/3.4.4-2-ARCH/misc/vsock.ko
supported: external
alias: vmware_vsock
license: GPL v2
version: 9.1.1.0
description: VMware Virtual Socket Family
author: VMware, Inc.
srcversion: 5A37036862692504058A712
depends: vmci
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
filename: /lib/modules/3.4.4-2-ARCH/misc/vmmon.ko
supported: external
license: GPL v2
description: VMware Virtual Machine Monitor.
author: VMware, Inc.
depends:
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
filename: /lib/modules/3.4.4-2-ARCH/misc/vmnet.ko
supported: external
license: GPL v2
description: VMware Virtual Networking Driver.
author: VMware, Inc.
depends:
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
ERROR: Module vmblock not found.
filename: /lib/modules/3.4.4-2-ARCH/misc/vmci.ko
supported: external
license: GPL v2
version: 9.1.18.0
description: VMware Virtual Machine Communication Interface (VMCI).
author: VMware, Inc.
srcversion: F659B534EA5CC5FFD4A08BF
alias: pci:v000015ADd00000740sv*sd*bc*sc*i*
depends:
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
parm: disable_host:Disable driver host personality - (default=0) (bool)
parm: disable_guest:Disable driver guest personality - (default=0) (bool)
parm: disable_msi:Disable MSI use in driver - (default=0) (bool)
parm: disable_msix:Disable MSI-X use in driver - (default=0) (bool)
filename: /lib/modules/3.4.4-2-ARCH/misc/vsock.ko
supported: external
alias: vmware_vsock
license: GPL v2
version: 9.1.1.0
description: VMware Virtual Socket Family
author: VMware, Inc.
srcversion: 5A37036862692504058A712
depends: vmci
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
filename: /lib/modules/3.4.4-2-ARCH/misc/vmmon.ko
supported: external
license: GPL v2
description: VMware Virtual Machine Monitor.
author: VMware, Inc.
depends:
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
filename: /lib/modules/3.4.4-2-ARCH/misc/vmnet.ko
supported: external
license: GPL v2
description: VMware Virtual Networking Driver.
author: VMware, Inc.
depends:
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
ERROR: Module vmblock not found.
filename: /lib/modules/3.4.4-2-ARCH/misc/vmci.ko
supported: external
license: GPL v2
version: 9.1.18.0
description: VMware Virtual Machine Communication Interface (VMCI).
author: VMware, Inc.
srcversion: F659B534EA5CC5FFD4A08BF
alias: pci:v000015ADd00000740sv*sd*bc*sc*i*
depends:
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
parm: disable_host:Disable driver host personality - (default=0) (bool)
parm: disable_guest:Disable driver guest personality - (default=0) (bool)
parm: disable_msi:Disable MSI use in driver - (default=0) (bool)
parm: disable_msix:Disable MSI-X use in driver - (default=0) (bool)
filename: /lib/modules/3.4.4-2-ARCH/misc/vsock.ko
supported: external
alias: vmware_vsock
license: GPL v2
version: 9.1.1.0
description: VMware Virtual Socket Family
author: VMware, Inc.
srcversion: 5A37036862692504058A712
depends: vmci
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
filename: /lib/modules/3.4.4-2-ARCH/misc/vmmon.ko
supported: external
license: GPL v2
description: VMware Virtual Machine Monitor.
author: VMware, Inc.
depends:
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
filename: /lib/modules/3.4.4-2-ARCH/misc/vmnet.ko
supported: external
license: GPL v2
description: VMware Virtual Networking Driver.
author: VMware, Inc.
depends:
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
ERROR: Module vmblock not found.
filename: /lib/modules/3.4.4-2-ARCH/misc/vmci.ko
supported: external
license: GPL v2
version: 9.1.18.0
description: VMware Virtual Machine Communication Interface (VMCI).
author: VMware, Inc.
srcversion: F659B534EA5CC5FFD4A08BF
alias: pci:v000015ADd00000740sv*sd*bc*sc*i*
depends:
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
parm: disable_host:Disable driver host personality - (default=0) (bool)
parm: disable_guest:Disable driver guest personality - (default=0) (bool)
parm: disable_msi:Disable MSI use in driver - (default=0) (bool)
parm: disable_msix:Disable MSI-X use in driver - (default=0) (bool)
filename: /lib/modules/3.4.4-2-ARCH/misc/vsock.ko
supported: external
alias: vmware_vsock
license: GPL v2
version: 9.1.1.0
description: VMware Virtual Socket Family
author: VMware, Inc.
srcversion: 5A37036862692504058A712
depends: vmci
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
filename: /lib/modules/3.4.4-2-ARCH/misc/vmmon.ko
supported: external
license: GPL v2
description: VMware Virtual Machine Monitor.
author: VMware, Inc.
depends:
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
filename: /lib/modules/3.4.4-2-ARCH/misc/vmnet.ko
supported: external
license: GPL v2
description: VMware Virtual Networking Driver.
author: VMware, Inc.
depends:
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
ERROR: Module vmblock not found.
filename: /lib/modules/3.4.4-2-ARCH/misc/vmci.ko
supported: external
license: GPL v2
version: 9.1.18.0
description: VMware Virtual Machine Communication Interface (VMCI).
author: VMware, Inc.
srcversion: F659B534EA5CC5FFD4A08BF
alias: pci:v000015ADd00000740sv*sd*bc*sc*i*
depends:
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
parm: disable_host:Disable driver host personality - (default=0) (bool)
parm: disable_guest:Disable driver guest personality - (default=0) (bool)
parm: disable_msi:Disable MSI use in driver - (default=0) (bool)
parm: disable_msix:Disable MSI-X use in driver - (default=0) (bool)
filename: /lib/modules/3.4.4-2-ARCH/misc/vsock.ko
supported: external
alias: vmware_vsock
license: GPL v2
version: 9.1.1.0
description: VMware Virtual Socket Family
author: VMware, Inc.
srcversion: 5A37036862692504058A712
depends: vmci
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
Stopping VMware services:
VMware Authentication Daemon done
VM communication interface socket family done
Virtual machine communication interface done
Virtual machine monitor done
Blocking file system done
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmmon-only'
make -C /lib/modules/3.4.4-2-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.4.4-2-ARCH'
CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driverLog.o
CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driver.o
CC [M] /tmp/vmware-root/modules/vmmon-only/linux/hostif.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/memtrack.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/apic.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/cpuid.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/vmx86.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/task.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/hashFunc.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/comport.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/phystrack.o
CC [M] /tmp/vmware-root/modules/vmmon-only/vmcore/moduleloop.o
LD [M] /tmp/vmware-root/modules/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vmmon-only/vmmon.mod.o
LD [M] /tmp/vmware-root/modules/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-3.4.4-2-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmmon-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmmon-only'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-root/modules/vmmon-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmnet-only'
make -C /lib/modules/3.4.4-2-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.4.4-2-ARCH'
CC [M] /tmp/vmware-root/modules/vmnet-only/driver.o
CC [M] /tmp/vmware-root/modules/vmnet-only/hub.o
CC [M] /tmp/vmware-root/modules/vmnet-only/userif.o
CC [M] /tmp/vmware-root/modules/vmnet-only/netif.o
CC [M] /tmp/vmware-root/modules/vmnet-only/bridge.o
CC [M] /tmp/vmware-root/modules/vmnet-only/filter.o
CC [M] /tmp/vmware-root/modules/vmnet-only/procfs.o
CC [M] /tmp/vmware-root/modules/vmnet-only/smac_compat.o
CC [M] /tmp/vmware-root/modules/vmnet-only/smac.o
CC [M] /tmp/vmware-root/modules/vmnet-only/vnetEvent.o
CC [M] /tmp/vmware-root/modules/vmnet-only/vnetUserListener.o
LD [M] /tmp/vmware-root/modules/vmnet-only/vmnet.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vmnet-only/vmnet.mod.o
LD [M] /tmp/vmware-root/modules/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/linux-3.4.4-2-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmnet-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmnet-only'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/vmware-root/modules/vmnet-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmblock-only'
make -C /lib/modules/3.4.4-2-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.4.4-2-ARCH'
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/dbllnklst.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/dentry.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/block.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/file.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/module.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/super.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/filesystem.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/stubs.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/inode.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/control.o
/tmp/vmware-root/modules/vmblock-only/linux/filesystem.c: In function 'FsOpReadSuper':
/tmp/vmware-root/modules/vmblock-only/linux/filesystem.c:528:4: error: implicit declaration of function 'd_alloc_root' [-Werror=implicit-function-declaration]
/tmp/vmware-root/modules/vmblock-only/linux/filesystem.c:528:15: warning: assignment makes pointer from integer without a cast [enabled by default]
cc1: some warnings being treated as errors
make[2]: *** [/tmp/vmware-root/modules/vmblock-only/linux/filesystem.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [_module_/tmp/vmware-root/modules/vmblock-only] Error 2
make[1]: Leaving directory `/usr/src/linux-3.4.4-2-ARCH'
make: *** [vmblock.ko] Error 2
make: Leaving directory `/tmp/vmware-root/modules/vmblock-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmci-only'
make -C /lib/modules/3.4.4-2-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.4.4-2-ARCH'
CC [M] /tmp/vmware-root/modules/vmci-only/linux/driver.o
CC [M] /tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDatagram.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDriver.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciResource.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciContext.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciHashtable.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciEvent.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciQPair.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciRoute.o
CC [M] /tmp/vmware-root/modules/vmci-only/driverLog.o
/tmp/vmware-root/modules/vmci-only/linux/driver.c: In function '__check_disable_host':
/tmp/vmware-root/modules/vmci-only/linux/driver.c:2498:1: warning: return from incompatible pointer type [enabled by default]
/tmp/vmware-root/modules/vmci-only/linux/driver.c: In function '__check_disable_guest':
/tmp/vmware-root/modules/vmci-only/linux/driver.c:2501:1: warning: return from incompatible pointer type [enabled by default]
/tmp/vmware-root/modules/vmci-only/linux/driver.c: In function '__check_disable_msi':
/tmp/vmware-root/modules/vmci-only/linux/driver.c:2504:1: warning: return from incompatible pointer type [enabled by default]
/tmp/vmware-root/modules/vmci-only/linux/driver.c: In function '__check_disable_msix':
/tmp/vmware-root/modules/vmci-only/linux/driver.c:2507:1: warning: return from incompatible pointer type [enabled by default]
LD [M] /tmp/vmware-root/modules/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vmci-only/vmci.mod.o
LD [M] /tmp/vmware-root/modules/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/linux-3.4.4-2-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmci-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/vmware-root/modules/vmci-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmci-only'
make -C /lib/modules/3.4.4-2-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.4.4-2-ARCH'
Building modules, stage 2.
MODPOST 1 modules
make[1]: Leaving directory `/usr/src/linux-3.4.4-2-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmci-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/vmware-root/modules/vmci-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vsock-only'
make -C /lib/modules/3.4.4-2-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.4.4-2-ARCH'
CC [M] /tmp/vmware-root/modules/vsock-only/linux/af_vsock.o
CC [M] /tmp/vmware-root/modules/vsock-only/linux/vsockAddr.o
CC [M] /tmp/vmware-root/modules/vsock-only/linux/notifyQState.o
CC [M] /tmp/vmware-root/modules/vsock-only/linux/util.o
CC [M] /tmp/vmware-root/modules/vsock-only/linux/stats.o
CC [M] /tmp/vmware-root/modules/vsock-only/linux/notify.o
CC [M] /tmp/vmware-root/modules/vsock-only/driverLog.o
LD [M] /tmp/vmware-root/modules/vsock-only/vsock.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vsock-only/vsock.mod.o
LD [M] /tmp/vmware-root/modules/vsock-only/vsock.ko
make[1]: Leaving directory `/usr/src/linux-3.4.4-2-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vsock-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vsock-only'
cp -f vsock.ko ./../vsock.o
make: Leaving directory `/tmp/vmware-root/modules/vsock-only'
Starting VMware services:
Virtual machine monitor done
Virtual machine communication interface done
VM communication interface socket family done
Blocking file system done
Virtual ethernet done
VMware Authentication Daemon done
Shared Memory Available done
filename: /lib/modules/3.4.4-2-ARCH/misc/vmmon.ko
supported: external
license: GPL v2
description: VMware Virtual Machine Monitor.
author: VMware, Inc.
depends:
vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
No value set for `/system/http_proxy/use_http_proxy'
No value set for `/system/proxy/mode'
No value set for `/system/http_proxy/use_http_proxy'
No value set for `/system/proxy/mode'
No value set for `/system/http_proxy/use_http_proxy'
No value set for `/system/proxy/mode'
$
Last edited by med1972 (2012-07-01 00:41:46)

Kernel module version in-tree meaning

I'm trying to determine the version of one of my kernel modules, and modinfo <module-name> says
version: in-tree:
What does this mean? I looked at the first few results of google-ing for "arch linux kernel module version in-tree meaning site:bbs.archlinux.org" with no success.

I'm trying to determine the version of one of my kernel modules, and modinfo <module-name> says
version: in-tree:
What does this mean? I looked at the first few results of google-ing for "arch linux kernel module version in-tree meaning site:bbs.archlinux.org" with no success.

Oracle Unbreakable Enterprise Linux come with an ndiswrapper kernel module?

Hello
Does Oracle Unbreakable Enterprise Linux come with an ndiswrapper kernel module?
Does Oracle Unbreakable Enterprise Linux come with a package for the ndiswrapper kernel module that matches the kernel version?
What wireless driver is compatible with Oracle Unbreakable Enterprise Linux?

Hi,
Oracle Unbreakable Linux does not come with any ndiswrapper kernel module and any package for ndiswrapper module. But it includes many wireless network drivers. You can look at them from kernel package. For example
rpm -qlp kernel-2.6.18-8.el5.i686.rpm |grep wireless
From the output, you can find which wireless drivers are coming with Oracle Unbreakable Linux kernel.

[kernel] kernel update and third party modules management

Hi all,
I turned to Archlinux with my new thinkpad X220 just for a few days, while I have used Ubuntu for 4 years. I had never controlled my system in such a degree, and feel happy about it.
However, I have a question about kernel update, for I had install some modules from AUR with yaourt( e.g. tp_smapi, acpi_call). For my poor knowledge about pacman, I don't know how to handle those modules while I upgrade my kernel. I cannot remember to re-install all of them!
I think there must be a solution that I didn't found, so I write this thread to ask for help.
Any help would be appreciate.

Mr.Elendig wrote:You can use some silly wrapper around pacman that rebuilds them when there is a kernel update. I'm sure someone has written one already.
Thank you, Mr.Elendig. Do you mean some kind of frontend such as yaourt?
Or some kind of hooks like this:
aur/mkinitcpio-vbox 2.0-3 (Out of Date) (29)
VirtualBox hook for mkinitcpio that rebuilds kernel modules on next reboot
Using the key words you provided, I searched " kernel upgrade module rebuild " and found that gentoo offically provide a tool called "module-rebuild" to reinstall external modules. Maybe it's because gentoo always compile source code? But no other results.
However, now I found what I need to do is just to build the modules listed in the /etc/rc.conf, and that is acceptable. Maybe after a few weeks of study, I can find out my way to solve this problem.
And thanks for your reply.
Last edited by ywarlock (2012-03-09 16:20:36)

Open-vm-tools-modules and kernel rebuild

Initially when I installed open-vm-tools-modules the wiki instructed me to rebuild the kernel to include the VMWare drivers.
Today there was an upgrade to open-vm-tools-modules and I was wondering if a kernel rebuild is required every time this package is upgraded.

I would just like to note that I am having the same problem in VMware Fusion 4. But this is an update. I read what you said about having a problem doing pacman -S open-vm-tools-modules: when I enter the command it succeeds. But despite this, when I do sudo /etc/rc.d/open-vm-tools start it still fails, but it doesn't print anything about the vmblock. Doing strace produces some output that I really can't understand at all.
You should see my post here https://bbs.archlinux.org/viewtopic.php … 0#p1048450

VBox Guest Additions Kernel Modules

Hey, semi-literate Linux user/Arch n00b here. I apologize in advance as I realize that this issue has been addressed in this forum previously, but after several hours of hunting, I have yet to find a proper solution. I am trying to run Arch64 as a guest in VirtualBox (host is Ubuntu 10.10, x86-64 if it matters). I have the system up and running, but I can't seem to get the Guest Additions going, as the system won't build the kernel modules. This is the terminal output while running the installer:
Uncompressing VirtualBox 3.2.6 Guest Additions for Linux........
VirtualBox Guest Additions installer
Removing installed version 3.2.6 of VirtualBox Guest Additions...
:: Building the VirtualBox Guest Additions kernel modules [FAIL]
Your system does not seem to be set up to build kernel modules.
Look at /var/log/vboxadd-install.log to find out what went wrong. Once you have corrected it, you can
run
/etc/init.d/vboxadd setup
to build them.
:: Doing non-kernel setup of the Guest Additions [DONE]
:: Installing the Window System drivers [BUSY]
:: Installing X.Org Server 1.8 modules [DONE]
:: Setting up the Window System to use the Guest Additions [DONE]
You may need to restart the hal service and the Window System (or just restart
the guest system) to enable the Guest Additions.
:: Installing graphics libraries and desktop services components [DONE]
And this is the output of the log file:
Makefile:23: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again.. Stop.
Creating user for the Guest Additions.
Creating udev rule for the Guest Additions kernel module.
Any help would be greatly appreciated.

Guest additions for VirtualBox 4.0.4 are broken, in several ways. Try a newer build for them:
http://www.virtualbox.org/download/test … r70281.iso
It's working OK for me, while with the regular 4.0.4 additions I had numerous crashes on my XP guest.

Raid Driver and Kernel Module

I am having trouble getting the kernel to recognize the raid drivers which my card uses. The install of arch is fresh. The raid card is a HighPoint RocketRaid 2300. I browsed the AUR and found a PKGBUILD for an older version of the driver written by LoneWolf. I updated it to fit my needs.
The PKGBUILD I have is:
# Contributor: LoneWolf --Edited by Vitechy
pkgname=rr231x-0x
pkgver=2.1
pkgrel=3
pkgdesc="Kernel modules for Highpoint RocketRAID 230x and 231x SATA cards"
arch=('i686' 'x86_64')
url="http://www.highpoint-tech.com/USA/bios_rr2300.htm"
license=('custom')
groups=()
depends=('kernel26')
makedepends=()
provides=()
conflicts=()
replaces=()
backup=()
options=()
install=rr231x-0x.install
source=(http://www.support-highpoint-tech.com/Main/rr231x_00/Linux/opensrc/rr231x_0x-linux-src-v2.5-091022-1618.tar.gz)
noextract=()
md5sums=('59ce7354ed06f780584fed124c57c222')
_kernver=2.6.31-ARCH
# Note : pkgname should be rr231_0x , but using this name gives problems with the 2007.08 base installer --Not sure what this means so ill leave it alone.
build() {
mkdir -p $startdir/pkg/lib/modules/${_kernver}/kernel/drivers/scsi/
cd $startdir/src/rr231x_0x-linux-src-v2.5/product/rr2310pm/linux/
make || return 1
# Install the kernel module
install -m 644 -D rr2310_00.ko $startdir/pkg/lib/modules/${_kernver}/kernel/drivers/scsi/
mkdir -p $startdir/pkg/usr/share/licenses/$pkgname
cp $startdir/src/rr231x_0x-linux-src-v2.5/README $startdir/pkg/usr/share/licenses/$pkgname/
The post install script I used is:
# This is a default template for a post-install scriptlet. You can
# remove any functions you don't need (and this header).
# arg 1: the new package version
pre_install() {
/bin/true
# arg 1: the new package version
post_install() {
KERNEL_VERSION='2.6.35-ARCH'
depmod -v $KERNEL_VERSION > /dev/null 2>&1
# arg 1: the new package version
# arg 2: the old package version
post_upgrade() {
KERNEL_VERSION='2.6.35-ARCH'
depmod -v $KERNEL_VERSION > /dev/null 2>&1
# arg 1: the old package version
post_remove() {
KERNEL_VERSION='2.6.35-ARCH'
depmod -v $KERNEL_VERSION > /dev/null 2>&1
op=$1
shift
$op $*
Executing the PKGBUILD with the makepkg command creates a .pkg.tar.gz file. Installing the package with pacman -U nameofpackage.pkg.tar.gz reports that the package has been installed. Running pacman -Qs reports that there is a package, local/rr231x-0x on the system.
The raid card is still not functioning. Instead of seeing a raid array I see the individual HDD's which are connected to the raid card which is something I could see even before running makepkg. I am not sure what I am doing wrong. I have rebooted the PC but that has done nothing. Also running modprobe rr230x_0x or modprobe rr2310_00 returns FATAL:Module rr230x_0x/rr2310_00 not found.
Any help is appreciated.
Zlatan
PS. The md5sums in the PKGBUILD example I provided above is not the same one as the one in the PKGBUILD which is actually compiling on the server. The PKGBUILD above I recited from memory; however, I do not remember the actual number which I obtained by running makepkg -g. I will update as soon as I have access to the server again. I have updated the PKGBUILD above to exactly match the one im using on the server.
Last edited by Vitechy (2010-09-21 02:00:13)

Oh, wow I didn't even notice that.
Modprobe was able to load the modules now; however, now I see the HDD's and the raid array. In other words running fdisk -l shows all of the HDD's connected to the raid card, /dev/sda, /dev/sdb, /dev/sdc as well as the raid array /dev/sdd.
The raid array has not finished building, so is it a possibility that that is why it is showing up. I will post updates when the raid array has finished initializing.
Zlatan
Last edited by Vitechy (2010-09-22 13:06:40)

Problems with Intel 4965AGN and iwlagn kernel module

Hi everyone.
I having a couple of issues since my last kernel upgrade (2.6.27.5-1) and wanted to check if its my problem or if it is some kind of bug, before reporting it to the tracker.
I have the iwlagn (or iwl4965, as it is the same) kernel module in the MODULES array in /etc/rc.conf. Even tried removing it from there and leaving all the work to the module autodetect. No changes.
This is my dmesg | grep iwl output after boot:
iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27ks
iwlagn: Copyright(c) 2003-2008 Intel Corporation
iwlagn 0000:0b:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
iwlagn 0000:0b:00.0: setting latency timer to 64
iwlagn: Detected Intel Wireless WiFi Link 4965AGN REV=0x4
iwlagn: Tunable channels: 11 802.11bg, 13 802.11a channels
iwlagn 0000:0b:00.0: PCI INT A disabled
phy0: Selected rate control algorithm 'iwl-agn-rs'
iwlagn: Failed to register hw (error -2)
iwlagn: probe of 0000:0b:00.0 failed with error -2
I do have the firmaware (iwlwifi-4965-ucode) installed and enabled "firmware" in the mkinitcipio.conf image.
I have to do the following to get it working:
modprobe -r iwlagn
modprobe iwlagn
After which the output of dmesg | grep iwl is the following (added a line to split the reload of the module):
iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27ks
iwlagn: Copyright(c) 2003-2008 Intel Corporation
iwlagn 0000:0b:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
iwlagn 0000:0b:00.0: setting latency timer to 64
iwlagn: Detected Intel Wireless WiFi Link 4965AGN REV=0x4
iwlagn: Tunable channels: 11 802.11bg, 13 802.11a channels
iwlagn 0000:0b:00.0: PCI INT A disabled
phy0: Selected rate control algorithm 'iwl-agn-rs'
iwlagn: Failed to register hw (error -2)
iwlagn: probe of 0000:0b:00.0 failed with error -2
///////////////////// this is added after reload of iwlagn ///////////////
iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27ks
iwlagn: Copyright(c) 2003-2008 Intel Corporation
iwlagn 0000:0b:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
iwlagn 0000:0b:00.0: setting latency timer to 64
iwlagn: Detected Intel Wireless WiFi Link 4965AGN REV=0x4
iwlagn: Tunable channels: 11 802.11bg, 13 802.11a channels
phy0: Selected rate control algorithm 'iwl-agn-rs'
iwlagn 0000:0b:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
firmware: requesting iwlwifi-4965-2.ucode
Registered led device: iwl-phy0:radio
Registered led device: iwl-phy0:assoc
Registered led device: iwl-phy0:RX
For what i can tell... the module seems to be loading to soon. Could this be the problem?
On the other hand, it happened a couple of times that I just lost the device (the module quit working in the middle of a session).
Any ideas?
ps. I already reinstalled the previous kernel without results. Remade the kernel26.img changing options (HOOKS) and modified the order of services in the DAEMONS array, to no avail.

Nope. I'm still having problems.
Replaced NetworkManager with ntcfg2, but no changes so far.
Here is the kernel package I have installed:
core/kernel26 2.6.27.6-1 (x86-64)
Keep having to reload the module:
modprobe -r iwlagn
modprobe iwlagn
Output from dmesg | grep iwlagn seems to be the same:
[23:06:57 crow]$ dmesg | grep iwl
sda:<6>iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27ks
iwlagn: Copyright(c) 2003-2008 Intel Corporation
iwlagn 0000:0b:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
iwlagn 0000:0b:00.0: setting latency timer to 64
iwlagn: Detected Intel Wireless WiFi Link 4965AGN REV=0x4
iwlagn: Tunable channels: 11 802.11bg, 13 802.11a channels
iwlagn 0000:0b:00.0: PCI INT A disabled
phy0: Selected rate control algorithm 'iwl-agn-rs'
iwlagn: Failed to register hw (error -2)
iwlagn: probe of 0000:0b:00.0 failed with error -2
iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27ks
iwlagn: Copyright(c) 2003-2008 Intel Corporation
iwlagn 0000:0b:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
iwlagn 0000:0b:00.0: setting latency timer to 64
iwlagn: Detected Intel Wireless WiFi Link 4965AGN REV=0x4
iwlagn: Tunable channels: 11 802.11bg, 13 802.11a channels
phy0: Selected rate control algorithm 'iwl-agn-rs'
iwlagn 0000:0b:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
firmware: requesting iwlwifi-4965-2.ucode
Registered led device: iwl-phy0:radio
Registered led device: iwl-phy0:assoc
Registered led device: iwl-phy0:RX
Registered led device: iwl-phy0:TX
My loaded modules: lsmod
[23:12:15 crow]$ lsmod | grep iwl
iwlagn 102148 0
iwlcore 86084 1 iwlagn
rfkill 12068 2 iwlcore
led_class 6408 1 iwlcore
mac80211 182184 2 iwlagn,iwlcore
cfg80211 29840 3 iwlagn,iwlcore,mac80211
On the other hand, I found someone with the same problem in the Poland Arch Linux Forums:
http://forum.archlinux.pl/viewtopic.php?pid=31341
But I dont understand if the second person is giving its setup (and has it working) or if it is reporting problems too.
No one else is having issues with this wireless card?

Vmware-server-modules and kernel 2.6.19 [solved]

I'm trying to rebuild the vmware server modules from AUR for the new kernel. After adjusting the files for the kernel version and doing makepkg I get the following:
==> Validating source files with MD5sums
VMware-server-1.0.1-29996.tar.gz ... Passed
==> Extracting Sources...
==> tar --use-compress-program=gzip -xf VMware-server-1.0.1-29996.tar.gz
==> Starting build()...
Using 2.6.x kernel build system.
make: Entering directory `/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only'
make -C /lib/modules/2.6.19-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.19-ARCH'
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/linux/driver.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/linux/hostif.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/common/cpuid.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/common/hash.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/common/memtrack.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/common/phystrack.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/common/task.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/common/vmx86.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/vmcore/moduleloop.o
LD [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST 1 modules
CC /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/vmmon.mod.o
LD [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-2.6.19-ARCH'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only'
Using 2.6.x kernel build system.
make: Entering directory `/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only'
make -C /lib/modules/2.6.19-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.19-ARCH'
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/driver.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/hub.o
CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/userif.o
/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/userif.c: In function 'VNetCopyDatagramToUser':
/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/userif.c:629: error: 'CHECKSUM_HW' undeclared (first use in this function)
/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/userif.c:629: error: (Each undeclared identifier is reported only once
/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/userif.c:629: error: for each function it appears in.)
make[2]: *** [/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/userif.o] Error 1
make[1]: *** [_module_/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.19-ARCH'
make: *** [vmnet.ko] Error 2
make: Leaving directory `/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only'
==> ERROR: Build Failed. Aborting...
It seems the userif module breaks. I haven't a clue how to solve this. :?

Progress:
AUR
which leads to
http://www.vmware.com/community/thread. … 4&tstart=0
EDIT: package in AUR has been updated. Thnx pizzapunk.

Delaying a service until a kernel module has loaded and "settled"

Hi,
I have a problem: a certain program is started too soon before a kernel module has had time to settle down. That means that the program needs to be restarted manually after each reboot, otherwise it won't detect the hardware.
The service in question is tvheadend (from aur) and the module ddbridge, which I've installed from outside of the kernel tree (since the one in kernel is out of date). That is a beta driver so probably it should settle sooner, but it doesn't.
From the recent boot (and others) I can see this:
$ journalctl -b | grep -i ddbridge
experimental: 1969cdc5388b711e2aef3d1747b5f7dd1cd965f3 experimental/ddbridge: Fix 'inlining failed in call to always_inline ...: recursive inlining'.
huhti 27 20:25:59 ArkkiVille kernel: ddbridge 0000:02:00.0: enabling device (0000 -> 0002)
huhti 27 20:25:59 ArkkiVille kernel: DDBridge driver detected: Digital Devices Octopus DVB adapter
huhti 27 20:25:59 ArkkiVille kernel: ddbridge 0000:02:00.0: irq 41 for MSI/MSI-X
huhti 27 20:25:59 ArkkiVille kernel: DDBridge using 1 MSI interrupt(s)
huhti 27 20:25:59 ArkkiVille kernel: DVB: registering new adapter (DDBridge)
huhti 27 20:25:59 ArkkiVille kernel: DVB: registering new adapter (DDBridge)
experimental: 1969cdc5388b711e2aef3d1747b5f7dd1cd965f3 experimental/ddbridge: Fix 'inlining failed in call to always_inline ...: recursive inlining'.
huhti 27 20:26:01 ArkkiVille kernel: ddbridge 0000:02:00.0: DVB: registering adapter 0 frontend 0 (DRXK DVB-C DVB-T)...
huhti 27 20:26:03 ArkkiVille kernel: ddbridge 0000:02:00.0: DVB: registering adapter 0 frontend 1 (DRXK DVB-C DVB-T)...
But the tvheadend unit file is run right after the module is loaded at 20:26:00, which is too soon before the device nodes have actually populated:
huhti 27 20:26:00 ArkkiVille systemd[1]: Starting tvheadend...
huhti 27 20:26:00 ArkkiVille systemd[1]: Started tvheadend.
huhti 27 20:26:00 ArkkiVille tvheadend[502]: charset: 71 entries loaded
huhti 27 20:26:00 ArkkiVille tvheadend[502]: CSA: Using SSE2 128bit parallel descrambling
huhti 27 20:26:00 ArkkiVille tvheadend[502]: epggrab: module eit created
huhti 27 20:26:00 ArkkiVille tvheadend[502]: epggrab: module uk_freesat created
huhti 27 20:26:00 ArkkiVille tvheadend[502]: epggrab: module uk_freeview created
huhti 27 20:26:00 ArkkiVille tvheadend[502]: epggrab: module viasat_baltic created
huhti 27 20:26:00 ArkkiVille tvheadend[502]: epggrab: module opentv-skyuk created
huhti 27 20:26:00 ArkkiVille tvheadend[502]: epggrab: module opentv-skyit created
huhti 27 20:26:00 ArkkiVille tvheadend[502]: epggrab: module opentv-ausat created
huhti 27 20:26:00 ArkkiVille tvheadend[502]: epggrab: module pyepg created
huhti 27 20:26:00 ArkkiVille tvheadend[502]: epggrab: module xmltv created
huhti 27 20:26:00 ArkkiVille tvheadend[502]: epgdb: loaded v2
huhti 27 20:26:00 ArkkiVille tvheadend[502]: epgdb: channels 0
huhti 27 20:26:00 ArkkiVille tvheadend[502]: epgdb: brands 0
huhti 27 20:26:00 ArkkiVille tvheadend[502]: epgdb: seasons 0
huhti 27 20:26:00 ArkkiVille tvheadend[502]: epgdb: episodes 10870
huhti 27 20:26:00 ArkkiVille tvheadend[502]: epgdb: broadcasts 10869
huhti 27 20:26:00 ArkkiVille tvheadend[502]: dvr: Creating new configuration ''
huhti 27 20:26:00 ArkkiVille tvheadend[502]: AVAHI: Service 'Tvheadend' successfully established.
huhti 27 20:26:00 ArkkiVille tvheadend[502]: START: HTS Tvheadend version started, running as PID:502 UID:1337 GID:91, settings located in '/home/hts/.hts/tvheadend'
Restarting the service manually 'fixes' the issue:
huhti 27 20:27:16 ArkkiVille tvheadend[1311]: dvb: Found adapter /dev/dvb/adapter0 (DRXK DVB-C DVB-T) via PCI
huhti 27 20:27:16 ArkkiVille tvheadend[1311]: dvb: Found adapter /dev/dvb/adapter0 (DRXK DVB-C DVB-T) via PCI
huhti 27 20:27:16 ArkkiVille tvheadend[1311]: dvb: Found adapter /dev/dvb/adapter1 (DRXK DVB-C DVB-T) via PCI
Any ideas how to 'delay' the service? Is there a .target or service (or similar) in systemd which can see if the kernel modules have settled down?
Is my only option making a dirty script that will check that the device nodes are there, or hard-coding a delay in the unit file? How would one do that?
Cheers!
Last edited by Wild Penguin (2015-04-27 21:15:44)

A simple way to do that would be to use a systemd timer unit, named '/etc/systemd/system/tvheadend.timer':
[Unit]
Description=Delaying tvheadend start
[Timer]
OnStartupSec=20
AccuracySec=5
Then:
# cp /usr/lib/systemd/system/tvheadend.service /etc/systemd/system
# cd /etc/systemd/system
# vim tvheadend.service
# diff /usr/lib/systemd/system/tvheadend.service tvheadend.service
14c14
< WantedBy=multi-user.target
> #WantedBy=multi-user.target
Edit: The above part is superfluous, sorry, see the next posts
Finally:
# systemctl disable tvheadend.service
# systemctl add-wants multi-user.target tvheadend.timer
# systemctl daemon-reload
This timer will start the 'tvheadend.service' 20 seconds (+~5 seconds) after systemd start time.
To my opinion, this is the easiest way to do that (no udev rule to write with the systemd device unit features which is much more complicated).
Last edited by berbae (2015-04-28 15:13:47)

Kernel versions and rogue modules

Hello.
Can anyone tell me why the kernel-headers package and the kernel26 package never seem to carry the same version?
Right now in current, kernel-headers' version is 2.6.20.X while the kernel26 is at 2.6.21.
Also, why do I always have a directory in /lib/modules/ of the name of the next kernel version? (in this case /lib/modules/2.6.21-ARCH while I'm at 2.6.20) .
I've had numerous problems around this over the last few months. Today it happened again: I just installed gspcav1 from the repository tree, which is a webcam module, and the module was installed for kernel 2.6.21 (in /lib/modules/2.6.21-ARCH/**/usbvideo/gspca.ko), which I'm not running yet. I really wish I didn't have to upgrade my kernel for this sort of things.
Can anyone help?

External module packages are provided for the current kernel package only. If you choose to run an older kernel, any modules that you have already installed will continue to function as expected, but if you need to install new ones, as with gspcav1 above, you will need to either build it yourself or find the previous version of the package somewhere.
You have a /lib/modules/2.6.21-ARCH directory because that is where pacman installed gspcav1. There are no "rogue modules" here, simply an incorrect expectation of how module packages are handled.

Vbox Kernel Module and .24

Similar Messages

Maybe you are looking for