Kernel module for D30 TPM Chip Linux?

Seems that Linux does not recognize the TPM chip. Could it be that there is no module for it in Linux Kernel? I Thought D30 supports RHEL6?
Manufacturer: LENOVO
Product Name: 422916G
Version: ThinkStation D30
BIOS Revision: 0.37
Solved!
Go to Solution.

Sorry for the noise. Issue is fixed. Needed to install kernel-modules-extras package for tpm_tis kernel module

Similar Messages

Trouble building kernel module for sensor support

Hi, I'm new here but have been using Arch for a while. Recently, I decided to install Arch on an old laptop (Toshiba A70) and have managed to work out most of the kinks to where it runs nicely. Unfortunately, ACPI support is spotty and the /sys/class/thermal directory gives me only cooling_device0. I installed the lm-sensors package and ran sensors-detect, which yielded no results. Although the laptop runs smoothly otherwise, I would like to know the CPU's temp so that I would be able to set up a fan control scheme and CPU scaling (so far it's stuck at the lowest frequency, and that's kind of a big deal for me since the laptop runs on an archaic mobile P4 chip).
Sorry for the story but I felt some context was necessary. I did manage to find a kernel module that would connect those sensors to ACPI for me (http://sourceforge.net/projects/omnibook/), however I'm having trouble building it on the latest kernel. Here is the output from running make:
make -C /lib/modules/3.16.1-1-ARCH/build SUBDIRS=/root/omnibook-2.20070211 modules
make[1]: Entering directory '/usr/lib/modules/3.16.1-1-ARCH/build'
CC [M] /root/omnibook-2.20070211/init.o
In file included from /root/omnibook-2.20070211/init.c:26:0:
/root/omnibook-2.20070211/laptop.h:25:3: warning: initialization from incompatible pointer type
.callback = dmi_matched,
^
/root/omnibook-2.20070211/laptop.h:25:3: warning: (near initialization for ‘omnibook_ids[0].callback’)
/root/omnibook-2.20070211/laptop.h:34:3: warning: initialization from incompatible pointer type
.callback = dmi_matched,
^
/root/omnibook-2.20070211/laptop.h:34:3: warning: (near initialization for ‘omnibook_ids[1].callback’)
/root/omnibook-2.20070211/laptop.h:43:3: warning: initialization from incompatible pointer type
.callback = dmi_matched,
^
// I left out most of the 'incompatible pointer type' warnings since they repeat for a while.
^
/root/omnibook-2.20070211/laptop.h:1001:3: warning: (near initialization for ‘omnibook_ids[108].callback’)
/root/omnibook-2.20070211/init.c: In function ‘dmi_matched’:
/root/omnibook-2.20070211/init.c:141:16: warning: assignment discards ‘const’ qualifier from pointer target type
laptop_model = dmi_get_system_info(DMI_PRODUCT_VERSION);
^
/root/omnibook-2.20070211/init.c: In function ‘omnibook_init’:
/root/omnibook-2.20070211/init.c:281:3: error: implicit declaration of function ‘create_proc_entry’ [-Werror=implicit-function-declaration]
proc_entry = create_proc_entry(feature->name, pmode, omnibook_proc_root);
^
/root/omnibook-2.20070211/init.c:281:14: warning: assignment makes pointer from integer without a cast
proc_entry = create_proc_entry(feature->name, pmode, omnibook_proc_root);
^
/root/omnibook-2.20070211/init.c:290:13: error: dereferencing pointer to incomplete type
proc_entry->data = feature;
^
/root/omnibook-2.20070211/init.c:291:13: error: dereferencing pointer to incomplete type
proc_entry->read_proc = &procfile_read_dispatch;
^
/root/omnibook-2.20070211/init.c:293:14: error: dereferencing pointer to incomplete type
proc_entry->write_proc = &procfile_write_dispatch;
^
/root/omnibook-2.20070211/init.c:294:13: error: dereferencing pointer to incomplete type
proc_entry->owner = THIS_MODULE;
^
cc1: some warnings being treated as errors
scripts/Makefile.build:257: recipe for target '/root/omnibook-2.20070211/init.o' failed
make[2]: *** [/root/omnibook-2.20070211/init.o] Error 1
Makefile:1333: recipe for target '_module_/root/omnibook-2.20070211' failed
make[1]: *** [_module_/root/omnibook-2.20070211] Error 2
make[1]: Leaving directory '/usr/lib/modules/3.16.1-1-ARCH/build'
Makefile:88: recipe for target 'omnibook.ko' failed
make: *** [omnibook.ko] Error 2
I have honestly no idea what to make of any of this and would really appreciate any help towards a solution. Thanks for reading

Welcome to Arch Linux
That looks like it is a 2.6 kernel module
http://sourceforge.net/p/omnibook/bugs/58/
Did you try either of these AUR offerings?
ewaller$@$odin ~ 1001 %packer -Ss omnibook
aur/omnibook-git 20110911-9 (7)
Kernel module for HP OmniBook,Pavilion,Toshiba and Compal ACL00 laptops
aur/omnibook-svn-zen 268-1 (1)
Kernel module for HP OmniBook, Pavilion, Toshiba and Compal ACL00 laptops
ewaller$@$odin ~ 1002 %
Last edited by ewaller (2014-08-23 23:33:53)

Need Help with Oracleasm - a kernel module for the ASM library

I am a beginner, trying to install Oracle RAC. I have a system with SuSE Linx 11 (64 bit) loaded. I need to get the correct ASMLib packages needed for installing ASM. I think I got the following packages that are needed for installing ASM
1) oracleasmlib- the ASM libraries (oracleasmlib-2.0.4-1.SLE11.x86_64.rpm)
2) oracleasm-support- utilities needed to administer ASMLib (oracleasm-support-2.1.3-1.SLE11.x86_64.rpm)
I am unable to find the third package.
3) Oracleasm - a kernel module for the ASM library
I looked at my kernel version it says "2.6.27.19-5-default". I am not sure where I can get the above third package. If you have an answer/know ase share your thoughts.
Thank You

Hi!
Don't use ASMLib, it will be no longer available, it will only came in Oracle Unbreakable Kernel for Linux 6.
The easly way to set the permissions on your devices is with a /etc/init.d script that do the job.
Here is an example:
#! /bin/bash
# chkconfig: 2345 25 19
# description: Set ASM Permissions on to devices at boot.
case "$1" in
start)
/bin/chown oracle:oinstall /dev/sdb1
/bin/chmod 0660 /dev/sdb1
stop)
#do nothing
status)
ls -l /dev/sdb1
echo "Usage: $0 {start|stop|status}"
exit 1
esac
exit o
You need to replace the /dev/sdb1 for your acctual partitions.
Please check the Docs to be sure that you meet all pre-reqs.
http://docs.oracle.com/cd/E11882_01/relnotes.112/e23558/toc.htm
http://docs.oracle.com/cd/E11882_01/install.112/e22489/toc.htm
http://docs.oracle.com/cd/E11882_01/install.112/e24321/toc.htm
Hope it's helps.
Best Regards,
Julio

How to write a kernel module for Solaris

Hi
I would like to know where I can find information about writing a kernel module for Solaris. Is there a pdf developers reference?

http://docs.sun.com
Search "writing device drivers".Even if I don't intend writing a device driver?

Which kernel module for Intel PRO/100 S Desktop Adapt

Which kernel module I should load for support LAN Card "Intel® PRO/100 S Desktop Adapter" Board ID "751767-004" , Based on Controller 82550

Finded in /usr/src/linux-2.6.5/drivers/net/Kconfig
config E100
tristate "Intel(R) PRO/100+ support"
depends on NET_PCI && PCI
select MII
---help---
   This driver supports Intel(R) PRO/100 family of adapters, which
   includes:
   Controller Adapter Name Board IDs
   82558 PRO/100+ PCI Adapter 668081-xxx,
   689661-xxx
   82558 PRO/100+ Management Adapter 691334-xxx,
   701738-xxx,
   721383-xxx
   82558 PRO/100+ Dual Port Server Adapter 714303-xxx,
   711269-xxx,
   A28276-xxx
   82558 PRO/100+ PCI Server Adapter 710550-xxx
   82550 PRO/100 S Server Adapter 752438-xxx
   82559 A56831-xxx,
   A10563-xxx,
   A12171-xxx,
   A12321-xxx,
   A12320-xxx,
   A12170-xxx
   748568-xxx
   748565-xxx
   82550 PRO/100 S Desktop Adapter 751767-xxx
   82559 748592-xxx,
   A12167-xxx,
   A12318-xxx,
   A12317-xxx,
   A12165-xxx,
   748569-xxx
   82559 PRO/100+ Server Adapter 729757-xxx
   82559 PRO/100 S Management Adapter 748566-xxx,
   748564-xxx
   82550 PRO/100 S Dual Port Server Adapter A56831-xxx
   82551 PRO/100 M Desktop Adapter A80897-xxx
   PRO/100 S Advanced Management Adapter
   747842-xxx,
   745171-xxx
   CNR PRO/100 VE Desktop Adapter A10386-xxx,
   A10725-xxx,
   A23801-xxx,
   A19716-xxx
   PRO/100 VM Desktop Adapter A14323-xxx,
   A19725-xxx,
   A23801-xxx,
   A22220-xxx,
   A23796-xxx
   To verify that your adapter is supported, find the board ID number
   on the adapter. Look for a label that has a barcode and a number
   in the format 123456-001 (six digits hyphen three digits). Match
   this to the list of numbers above.
   For more information on how to identify your adapter, go to the
   Adapter & Driver ID Guide at:
   http://support.intel.com/support/networ … /21397.htm
   For the latest Intel PRO/100 network driver for Linux, see:
   http://appsr.intel.com/scripts-df/support_intel.asp
   More specific information on configuring the driver is in
   <file:Documentation/networking/e100.txt>.
   To compile this driver as a module, choose M here and read
   <file:Documentation/networking/net-modules.txt>. The module
   will be called e100.

CIFS Kernel module for Ideatab S6000L

I just bought an Ideatab S6000L and I tried to mount my share as a local folder using CIFS. After some research it seems some modules are missing. I tried with modules from other version (for example in this topic http://forums.lenovo.com/t5/Idea-Android-based-Tablets/CIFS-Kernel-Module-can-t-mount-CIFS-share-on-...
It didn't work and I don't know how to build thoses modules for this specific version, could someone provide me thoses modules or help me to build them please?

Thank you for your response
I'm thinking of returning my tablet, this is something I really needed.
So in summary, all of the lenovo tablet have this problem and the module can't be built on some of them?

Advice on writing kernel module for old pen device (ISA)

I have not really a programming question, I need an advice.
I have an old mobile computer for which no driver exists for the pen pointing device yet. Although it has USB so I can use a mice, it would be very nice if I could use the pen under linux. It came to my mind that this could be a good start to get into kernel programming since I have a problem to solve. It functions well under Windows NT and I know the address range it uses from driver.
So, I have no imagination how hard it can be to program a device driver without any documentation. I need basically an advice on what the possible caveats may be and if I should start the project at all.

stb wrote:So, I have no imagination how hard it can be to program a device driver without any documentation. I need basically an advice on what the possible caveats may be and if I should start the project at all.
well, there's documentation
Kernelnewbies.org is a good place to start. Heaps of documentation, and importantly, help for when you get stuck.
Firstly, if you want a good introduction the kernel, there's Robert Love's Linux Kernel Development.
I bought this one myself, it's a really good read, well written, and covers lots of interesting things.
http://www.amazon.com/Linux-Kernel-Deve … 0672327201
Then, there's Linux Device Drivers, 3rd Ed. Edition is important, Ed3 is 2.6.x, Ed2 is 2.4.x. Big difference.
http://www.amazon.co.uk/Linux-Device-Dr … 874&sr=8-1
This is available for free in PDF:
http://lwn.net/Kernel/LDD3/
Hope that helps,
James

Network module for ADMtek am983b chip [Solved].

I would like to install Arch from ftp to get a current installation. The problem is to get a network card up and running. My card is based on ADMtek am983b chip.
It doesn't get autodetected in setup. So what do I need to do to get it up? Obviously load the module by hand, but witch module?

Well, it seems like tulip works.

Proper method for building kernel modules? [solved]

I am attempting to build a custom kernel module for a PCI express interface to an FPGA. However, I seem to be running into some issues with getting the standard kernel module makefile to work correctly. Here is my makefile:
# object files to build
obj-m += nnic.o
nic-objs += nnic_driver.o
all:
make -C /lib/modules/$(shell uname -r)/build M=$(pwd) modules
clean:
make -C /lib/modules/$(shell uname -r)/build M=$(pwd) clean
However, the first time I ran 'make', I got this output:
make -C /lib/modules/3.14.1-1-ARCH/build M= modules
make[1]: Entering directory '/usr/lib/modules/3.14.1-1-ARCH/build'
Makefile:608: Cannot use CONFIG_CC_STACKPROTECTOR_REGULAR: -fstack-protector not supported by compiler
scripts/kconfig/conf --silentoldconfig Kconfig
*** Error during update of the configuration.
/usr/lib/modules/3.14.1-1-ARCH/build/scripts/kconfig/Makefile:36: recipe for target 'silentoldconfig' failed
make[3]: *** [silentoldconfig] Error 1
/usr/lib/modules/3.14.1-1-ARCH/build/Makefile:512: recipe for target 'silentoldconfig' failed
make[2]: *** [silentoldconfig] Error 2
scripts/Makefile.build:44: /usr/lib/modules/3.14.1-1-ARCH/build/arch/x86/syscalls/Makefile: No such file or directory
make[2]: *** No rule to make target '/usr/lib/modules/3.14.1-1-ARCH/build/arch/x86/syscalls/Makefile'. Stop.
/usr/lib/modules/3.14.1-1-ARCH/build/arch/x86/Makefile:183: recipe for target 'archheaders' failed
make[1]: *** [archheaders] Error 2
make[1]: Leaving directory '/usr/lib/modules/3.14.1-1-ARCH/build'
Makefile:7: recipe for target 'all' failed
make: *** [all] Error 2
After poking around online, I decided to try running make as root. I got the following output:
make -C /lib/modules/3.14.1-1-ARCH/build M= modules
make[1]: Entering directory '/usr/lib/modules/3.14.1-1-ARCH/build'
scripts/kconfig/conf --silentoldconfig Kconfig
scripts/Makefile.build:44: /usr/lib/modules/3.14.1-1-ARCH/build/arch/x86/syscalls/Makefile: No such file or directory
make[2]: *** No rule to make target '/usr/lib/modules/3.14.1-1-ARCH/build/arch/x86/syscalls/Makefile'. Stop.
/usr/lib/modules/3.14.1-1-ARCH/build/arch/x86/Makefile:183: recipe for target 'archheaders' failed
make[1]: *** [archheaders] Error 2
make[1]: Leaving directory '/usr/lib/modules/3.14.1-1-ARCH/build'
Makefile:7: recipe for target 'all' failed
make: *** [all] Error 2
Now, when runing 'make' as a normal user, I get:
make -C /lib/modules/3.14.1-1-ARCH/build M= modules
make[1]: Entering directory '/usr/lib/modules/3.14.1-1-ARCH/build'
Makefile:608: Cannot use CONFIG_CC_STACKPROTECTOR_REGULAR: -fstack-protector not supported by compiler
scripts/Makefile.build:44: /usr/lib/modules/3.14.1-1-ARCH/build/arch/x86/syscalls/Makefile: No such file or directory
make[2]: *** No rule to make target '/usr/lib/modules/3.14.1-1-ARCH/build/arch/x86/syscalls/Makefile'. Stop.
/usr/lib/modules/3.14.1-1-ARCH/build/arch/x86/Makefile:183: recipe for target 'archheaders' failed
make[1]: *** [archheaders] Error 2
make[1]: Leaving directory '/usr/lib/modules/3.14.1-1-ARCH/build'
Makefile:7: recipe for target 'all' failed
make: *** [all] Error 2
I have the linux-headers package installed. I do not need to build the whole kernel, only this small module. What am I missing here? What is the correct procedure for this?
Last edited by alex.forencich (2014-04-25 08:16:31)

Sigh, found the problem. Should be $(PWD) and not $(pwd) in my makefile.

Kernel module pointer for modctl structures

Hi,
Can anybody tell me where is the kernel module pointer that is pointing at the modctl structure? How can I use the module pointer?
Thanks.

Welcome to Arch Linux
That looks like it is a 2.6 kernel module
http://sourceforge.net/p/omnibook/bugs/58/
Did you try either of these AUR offerings?
ewaller$@$odin ~ 1001 %packer -Ss omnibook
aur/omnibook-git 20110911-9 (7)
Kernel module for HP OmniBook,Pavilion,Toshiba and Compal ACL00 laptops
aur/omnibook-svn-zen 268-1 (1)
Kernel module for HP OmniBook, Pavilion, Toshiba and Compal ACL00 laptops
ewaller$@$odin ~ 1002 %
Last edited by ewaller (2014-08-23 23:33:53)

Unable to compile module for Intel VTUNE with 3.16.4-1 kernel

I am currently running 3.16.4-1-ARCH #1 and I tried to compile the kernel module for Intel Vtune XE 2013 (r17).
Unluckily, GCC stops reporting the following errors:
/opt/intel/vtune_amplifier_xe_2013/sepdk/src/vtsspp/collector.c: In function ‘vtss_target_new’:
/opt/intel/vtune_amplifier_xe_2013/sepdk/src/vtsspp/collector.c:985:35: error: ‘VSYSCALL_START’ undeclared (first use in this function)
addr = (unsigned long)VSYSCALL_START;
^
/opt/intel/vtune_amplifier_xe_2013/sepdk/src/vtsspp/collector.c:985:35: note: each undeclared identifier is reported only once for each function it appears in
/opt/intel/vtune_amplifier_xe_2013/sepdk/src/vtsspp/collector.c:986:36: error: ‘VSYSCALL_MAPPED_PAGES’ undeclared (first use in this function)
size = (unsigned long)(VSYSCALL_MAPPED_PAGES * PAGE_SIZE)
As the source code points out:
#include <asm/fixmap.h> /* VSYSCALL_START */
The missing symbols are expected to be found under /usr/lib/modules/3.16.4-1-ARCH/build/arch/x86/include/asm/fixmap.h, but it seems that they are not present anymore.
Grepping the headers could not help at all.
What am I missing here ?

It looks like the macros:
VSYSCALL_START
VSYSCALL_SIZE
VSYSCALL_END
VSYSCALL_MAPPED_PAGES
got dropped after v3.15
I wonder if I need to downgrade.

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)

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

Missing kernel modules in 2.6.35.12

I'm building the LTS kernel 2.6.35.12 and have noticed several key modules are completely missing: lirc_i2c and lirc_dev. If I compare the confg from ARCH 2.6.35 to that of ARCH 2.6.37, I see that the entire section within the config that builds these is missing. I know for a fact that there are supported under 2.6.35 because I have been using this same setup since 2.6.26 just fine.
Here is a bit from 2.6.37's config that shows where these are:
# Texas Instruments shared transport line discipline
CONFIG_ST_BT=m
CONFIG_ADIS16255=m
CONFIG_FB_XGI=m
CONFIG_LIRC_STAGING=y
CONFIG_LIRC_BT829=m
CONFIG_LIRC_I2C=m
CONFIG_LIRC_IGORPLUGUSB=m
CONFIG_LIRC_IMON=m
CONFIG_LIRC_IT87=m
This section for 2.6.37 is found:
-> Device Drivers
-> Staging drivers (STAGING [=y])
-> Exclude Staging drivers from being built (STAGING_EXCLUDE_BUILD [=n])
-> Linux Infrared Remote Control IR receiver/transmitter drivers (LIRC_STAGING [=y])
Again, under 2.6.35 there is no corresponding entry for the "Linux Infrared Remote Control IR receiver/transmitter drivers" but again, I know that my remote worked back when Arch had 2.6.35.x in [core].
Thoughts as to how to enable building them under the LTS 2.6.35.x is appreciated!

iphitus wrote:Kernel modules for 2.6 have a .ko NOT .o filename.
The included makefile is written for a 2.6 kernel and produces a .o, and Gentoo used to mix the two, although Gentoo is hardly the golden standard.
Please ensure that you use the included makefiles and installation options included with the driver and run depmod -a after installing.
Both the vanilla kernel and the pkgbuild include the source and makefile unchanged in the correct place. Both are patched correctly as per the included readme.
If the driver is precompiled and has no make options, then it will *not* work under any circumstances.
I don't think I can precompile it, since it depends on about a dozen headers from include/scsi, which all have compile-time macros set by the kernel's makefiles. Even if I could track down every #ifdef and set the macro by hand, I wouldn't want to.
What driver is it? It would help us identify your problem much more easily.
Areca ARC1210 Source driver. Before you spend any time on this particular module, I should reiterate that I don't think there's anything wrong with the module itself, I was just looking for a minimum effort method to install the module, preferably without a custom kernel. I don't see this as a very likely option anymore, so more than likely I will use the pkgbuild I wrote for the purpose.

Loading Kernel Modules in 2.6.15

I'm trying to install drivers for an Areca RAID card. The company has source drivers as well as binaries for SuSE, RedHat, etc. I downloaded the Areca source drivers and the vanilla kernel sources and patched the Kconfig and Makefile in drivers/scsi/ to generate a kernel module, arcmsr.o built against a 2.6.15 kernel.
When i try
modprobe ./arcmsr.o
it fails with
FATAL: module ./arcmsr.o not found
What do I do now? Do I need to run a utility to index the new module for modprobe?
I built the whole set of vanilla kernel modules (but not the kernel itself) with the arch kernel26 config file, should I
make modules_install
to install the whole set and then recreate /lib/modules/linux-2.6.15-ARCH as a symlink to the new module repository?
Or should I write a pkgbuild (or edit the kernel26 pkgbuild) to install the ARC1210 patches and rebuild the kernel instead of doing it by hand? A pkgbuild is less than ideal (though I have one that seems to work), as I would also like to be able to do
pacman -Syu
and upgrade the kernel. I'm afraid that if I tell pacman not to update the kernel, I'll forget and run 2.6.15 forever .

iphitus wrote:Kernel modules for 2.6 have a .ko NOT .o filename.
The included makefile is written for a 2.6 kernel and produces a .o, and Gentoo used to mix the two, although Gentoo is hardly the golden standard.
Please ensure that you use the included makefiles and installation options included with the driver and run depmod -a after installing.
Both the vanilla kernel and the pkgbuild include the source and makefile unchanged in the correct place. Both are patched correctly as per the included readme.
If the driver is precompiled and has no make options, then it will *not* work under any circumstances.
I don't think I can precompile it, since it depends on about a dozen headers from include/scsi, which all have compile-time macros set by the kernel's makefiles. Even if I could track down every #ifdef and set the macro by hand, I wouldn't want to.
What driver is it? It would help us identify your problem much more easily.
Areca ARC1210 Source driver. Before you spend any time on this particular module, I should reiterate that I don't think there's anything wrong with the module itself, I was just looking for a minimum effort method to install the module, preferably without a custom kernel. I don't see this as a very likely option anymore, so more than likely I will use the pkgbuild I wrote for the purpose.

Kernel module for D30 TPM Chip Linux?

Similar Messages

Maybe you are looking for