Compile kernel module during install

I have an ASUS USB-N66 wireless adapater. I have verified that it works in Knoppix using the instructions here: https://bbs.archlinux.org/viewtopic.php?pid=1289702.
I would like to now compile the module during the Arch install process, but cannot run make. Is this possible? Is there an Arch image that includes make?
If not, would it be somehow possible to use the kernel module compiled in Knoppix during the Arch install?
Thanks,
Tim

I suggest you use a wired connection for the installation process and install all base-devel packages. Then fetch the pkgbuild for rt3573, patch the source, makepkg -si it.

Similar Messages

Compiling kernel module

Hello. I tryed to compile kernel module
/home/das/job/C/foo.c:
#include <linux/module.h>
#include <linux/kernel.h>
int init_module(void)
printk(KERN_INFO "Hello world 1.\n");
return 0;
void cleanup_module(void)
printk(KERN_INFO "Goodbye world 1.\n");
I created /home/das/job/C/Makefile:
obj-m += foo.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
But when i tryed to compile it with command make I take the error:
make -C /lib/modules/2.6.33-ARCH/build M=/home/das/job/C modules
make: *** /lib/modules/2.6.33-ARCH/build: No such file or directory. Stop.
make: *** [all] Error 2
My question is what is wrong and how i can compile module?
Last edited by F1sher (2011-11-01 15:37:51)

tomk wrote:Install it somewhere under /lib/modules/2.6.32-lts, run depmod, and modprobe it.
After
depmod -a
modprobe module
I can't start my system. GDM start but keyboard and mice don't work

Pass kernel arguments during install to force sata detection

Is it possible to pass kernel arguments during install of the 0.7.1 noodle base iso? I want the installer to detect my harddisc (with is a pata drive but I have a sata controller in my laptop) as sata. (Needed because of this problem http://bbs.archlinux.org/viewtopic.php?t=17696)
Update
I managed to pass the kernel argument (just typed arch hdc=noprobe) but I have to do hdd=noprobe as well because otherwise my harddisc is not recognized at all. But as a result, I'm unable to get my dvd-drive working and for that I'm unable to use the reiserfs to format my root disc. Also my ethernet module can't be loaded so I'm still unable to install
Solved
Problem solved, I managed to chroot into my install with the install cd (after doing the install but not having installed bootloader) and with passing kernel arguments hdc=noprobe hdd=noprobe I was able to install lilo on sda. I edited fstab and the kernel 2.6.15 handles the disc and the dvd-station very well. So I'm happy

Hmm, I saw that klibc before I installed to the pata drive. I just ran pacman -Rd klibc before upgrading and had no problems. Though, since klibc is a dependency of mkinitcpio, I should try removing the symlink rather than the package itself.

Compiled kernel module fails to install

A few moments ago finished compiling my own kernel, but still I can not boot with the new kernel.
When installing modules:
make modules_install
I get this:
Warning: you may need to install module-init-tools
The kernel was compiled in the traditional manner, and I get no error with mkinitcpio:
----> mkinitcpio -k 3.2.9 New -g /boot/initramfs-New.img
==> Starting build: 3.2.9
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [pata]
-> Running build hook: [scsi]
-> Running build hook: [sata]
-> Running build hook: [filesystems]
-> Running build hook: [usbinput]
-> Running build hook: [fsck]
-> Running build hook: [fglrx]
Building fglrx module for 3.2.9 kernel ...
Ok.
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-New.img
==> Image generation successful
I have the entry in grub and I can enter without problem, but there comes a point where you do not start:
Waiting 10 seconds for device /dev/sda4 ...
ERROR: Unable to find root device '/dev/sda4'.
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
sh: can't access tty: job control turned off
[rootfs /]#
And if my partition /root is /dev/sda4,I found a topic like this, but even I can not fix the problem:
https://bbs.archlinux.org/viewtopic.php?id=135851

I compiled the kernel old version that I have problems with the battery life on the newer versions.
The battery only lasts me one hour, but that is another problem.
fdisk:
Disk /dev/sda: 500.1 GB, 500107862016 bytes, 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Identificador del disco: 0x5d8c0991
Disposit. Inicio Comienzo Fin Bloques Id Sistema
/dev/sda1 * 2048 409599 203776 7 HPFS/NTFS/exFAT
/dev/sda2 409600 147210239 73400320 7 HPFS/NTFS/exFAT
/dev/sda3 147219660 862304939 357542640 5 Extendida
/dev/sda4 * 862304940 976773167 57234114 83 Linux
/dev/sda5 147219723 859477499 356128888+ 7 HPFS/NTFS/exFAT
/dev/sda6 859477563 862304939 1413688+ 82 Linux swap / Solaris
/lib/modules:
drwxr-xr-x 4 root root 4096 oct 3 20:40 3.2.9
drwxr-xr-x 3 root root 4096 oct 3 08:55 3.5.4-1-ARCH
drwxr-xr-x 2 root root 4096 oct 3 08:55 extramodules-3.5-ARCH
/boot:
drwxr-xr-x 6 root root 4096 oct 3 06:20 grub
-rw-r--r-- 1 root root 12612222 oct 3 08:55 initramfs-linux-fallback.img
-rw-r--r-- 1 root root 3098536 oct 3 08:55 initramfs-linux.img
-rw-r--r-- 1 root root 2016551 oct 3 20:40 initramfs-New.img
-rw-r--r-- 1 root root 2081862 oct 3 19:37 System.map-New
-rw-r--r-- 1 root root 3444736 sep 15 00:15 vmlinuz-linux
-rw-r--r-- 1 root root 4434400 oct 3 19:35 vmlinuz-New
I install grub-legacy of AUR, but I have to change to syslinux.
For now this is my menu.lst:
# (0) Arch Linux
title Arch Linux
root (hd0,3)
kernel /boot/vmlinuz-linux root=/dev/sda4 nomodeset vga=773 ro
initrd /boot/initramfs-linux.img
# (0) Arch Linux
title Arch Linux NK
root (hd0,3)
kernel /boot/vmlinuz-New root=/dev/sda4 nomodeset ro
initrd /boot/initramfs-New.img

Compiling kernel modules against 2.6.15-ARCH

I recently migrated to arch from Gentoo and Debian for a new webserver, and couldn't be happier. The system has worked great so far, and RAID card aside, I haven't had a single problem with Arch. The base system is easy to configure, and there is actually a list of config files in the install docs. Pacman is an absolute dream... Debian's apt is willfully a year out of date, and Gentoo's portage is a convulted and time-consuming nightmare.
In fact, Gentoo's unprompted and unwarranted removal of libstdc++ was the final straw.
However, one thing that confuses me about arch is the kernel build system.
I have an Areca ARC-1210 PCIe to SATAII hardware RAID card, but I can't figure out how to build the driver as a kernel module. If I compile it on its own it fails with literally hundreds of errors, almost like there's a header missing.
The instructions that came with the source want me to add a
config SCSI_ARCMSR
tristate "ARECA SATA RAID HOST Controller"
depends on PCI && SCSI
help
block to /usr/src/linux/drivers/scsi/Kconfig (which I did: it shows up in menuconfig), and a
obj-$(CONFIG_SCSI_ARCMSR) += arcmsr/
line to /usr/src/linux/drivers/scsi/Makefile.
However, arch doesn't seem to have the recursive makefile kernel build system that I and the good people at Areca used to.
How can I build this driver, preferably as a module, against my 2.6.15 kernel?
There are also precompiled x86 modules availible for Red Hat, SuSE, and TurboLinux. Assuming one of them is built against a reasonably current kernel, could they be used safely? I normally wouldn't try such a thing, but time is of the essence, and the RAID card seems to have such simple dependencies, I imagine it unlikely that all three major distros would have SCSI and PCI drivers patched to incompatability.

having said all that ...do u think compiling the kernel myself would provide any improvment for me???? ( I am haveing freezing and instablility problems..ive used 3 of the arch kernels....check out my thread titled Arch Instable.. (please)
p.s. btw Welcome

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.

Compiling kernel module on 64bit Solaris10 amd64 platform

Hi,
i m compiling my kernel module in Solaris10 booted in 64bit on amd64 platform.
i m using two extra flags: -xarch=amd64 -xmodel=kernel
But i m getting error s as follows:
ld: fatal: file -c : open failed: No sich file or directory.
ld: fatal: symbol '_fini' is multiply defined.
(file /opt/SUNWspro/prod/lib/ctri.o type=FUNC; file bcmod.o type=FUNC) ;
ld: fatal: symbol '_init' is multiply defined.
(file /opt/SUNWspro/prod/lib/ctri.o type=FUNC; file bcmod.o type=FUNC) ;
ld: fatal: file processing errors: No output written to a.out
can somebody give hint .

I think you need to take this question to an Open Solaris community forum at http://www.opensolaris.org
Your question is not about the C compiler, but about how to build the Solaris kernel.

Running Solaris 8 compiled kernel module on Solaris 9

Hi,
I found some differences in the vnode definitions on S8 and S9. This
means a file system kernel module written on S8 would have to be recompiled to run on S9. From what I know, such a constraint did not exist when going from Solaris 7 to 8. Is it true? Has anyone faced a similar situation for device drivers?
Thanks.

well I have tried it actually. and the behavior is weird. On my solaris 8 box. Every thing works perfectly fine. But due to some reason on solaris 10 machine the values i transmit over the tcp socket totally change. i send a msgCode = 1 , 2, or 3 ... but on the other end, which is a windows machine i get strange values 210, 10, 35 49 etc etc ... is this due to version problem.

Kernel panic during install - how to continue?

Mountain Lion downloaded and installed for a long time but then it started rebooting. It comes then with a Kernel panic page
"Panic, Kernel trap at XXX, type 14=page fault" ....
It then reboots and the whole thing keeps repeating itself over and over.
How should I proceed? My iMac has never had any problems prior to this install.
Thanks

I too am having the exact same problem, I guess I should have listened to my spideysense saying don't be the first one to upgrade. I have been on these threads all day and have tried everything, not making any money today....
1. I have the latest and greatest 2 month old MacPro tower, 12 processors, upgraded videocards, 24 gigs of RAM, etc, etc. so I am ruling out a hadware deficiency
2. I tried the Option - R reboot, ran permissions, fixed one permission, same problem, constant re-boot, on it's own
3. I tried the PRAM reset, actually two or three times, same problem, constant re-boot, on it's own
4. I tried the Safe Mode reboot, same problem, constant re-boot, on it's own
5. I didn't set up a Time Machine yet so I couldn't try that.
6. I removed any and all unecessary peripherals, only used the one monitor, got in safe mode and turned off the Wi-Fi. same problem, constant re-boot, on it's own
7. My last option is to reboot with Option - R and re-download and reinstall ML but our office internet is having issues and it says it will take 14 hours to re-download, any other possible solutions out there ?

ATI drivers won't compile kernel modules, what other options?

Just building my first Arch build on my desktop, I've got XFCE working, and ALSA (Finally after some troubleshooting and tweaking), but now I'm up to video drivers.
I've just found out the hard way that FGLRX will not compile, I'm assuming because ATI drivers do not support Kernel 3.1.1. So I got rid of FGLRX and the ATI configuration tools. But now I have a dual head display, running on ati-dri (which I assume is just your run of the mill basic driver for ATI cards) and I'm a bit lost on what to look into in terms of using the 3D power of my ATI 4870, and also to set up my dual head displays, on other distros I used to just use the ATI tool and it wrote an xorg file for me, but now I've just got a cloned display.
Halp?

Thank you tomk, sorry to have wasted a thread on something that I could of found in the wiki, I'll keep it in mind next time.
Going with the easiest and fastest option seeing as all options will give the same end result, that being using the unofficial catalyst repo. From what I understand the Arch wikis are frequently updated, so that method should work with the 3.1.1 kernel, correct?

Compiling STREAM module for 64-bit kernel

Hi,
I am trying to compile a STREAM module for Solaris. The results I get when I execute "isalist" and "isainfo -kv" are:
-"sparcv9+vis sparcv9 sparcv8plus+vis sparcv8plus sparcv8 sparcv8-fsmuld sparcv7 sparc"
-"64-bit sparcv9 kernel modules"
The host is a Ultra5_10 with SunOS 5.7 sun4u sparc.
First I tried to compile the module with gcc 2.8.1 but altough the compilation apparentelly finisihed OK I did not get to load the module. Later I read that, gcc so far does not generate binaries for 64-bit sparc.
So I installed the Sun WorkShop 5 environment (try version) and I tried to compile my sources with the following line:"cc -D_KERNEL -xarch=v9 -xcode=abs32 -xregs=no%appl -x03 -I. -I/usr/include -c mymodule.c"
but I get a huge list of errors such as:
"/usr/include/sys/thread.h/, line73:warning: volatile is a keyworkd in
ANSI C"
"/usr/include/sys/thread.h/, line 73:sintax error before or at:volatile"
so if I compile adding the directire "-D_ASM" to the previous line, the list of errors descreases to 2 lines:
"/usr/include/sys/kstat.h, line 52: sintax error before or at: hrtime_t"
"/usr/include/sys/kstat.h, line 52: cannot recover from previous errors".
I have also tried adding directives such as: -D_LP64 -D__sparcv9 -D_POSIX_C_SOURCE, -D_XOPEN_SOURCE but I do not get to compile it successfully.
Could someone be so kind to give me a clue of what I am doing wrong, and what should I do in order to compile it??.
The header files I have included right now in my ".c" are:
#include <sys/stream.h>
#include <sys/conf.h>
#include <sys/modctl.h>
#include <sys/kmem.h>
#include <sys/cmn_err.h>
#include <sys/ddi.h>
#include <sys/sunddi.h>
If I do not add the directives -I. -I/usr/include to the compile line above I get the following error:
"/usr/include/sys/modctl.h, line 185: major, argument mismatch"
"/usr/include/sys/cred.h, line 51: sintax error before or at: uint_t"
But this is because the environment it is taken the /usr/ucbinclude as default include path instead of the "/usr/include". �which one should I consider?.
Thank in advance for your support.
Looking forward to hearing from you.
(could you please send to me the answeres to this e-mail:[email protected]??)
Regards
Elena

HI,
Maybe a file I can edit that says to run the Garmin stuff in 32-bit mode?
Right or control click the Garmin application (or utility) then click: Get Info
In the Get Info window under the General tab, if it can be enabled you should see:
Open in 32-bit mode.
Activity Monitor (Applications/Utilities) shows all apps running in 64 bit. If it doesn't have 64 bit under Kind on the right, then it's running in 32 bit mode.
Carolyn

VMware fails during VMware Kernel Module Update!

VMware error log
Upon trying to run VMware, it brings up the VMware Kernel Module Updater. When I click Install, it properly stops VMWare Service. Then, it properly compiles the Virtual Machine Monitor, the Virtual Machine Communication Interface, and the VMCI Sockets. It fails to compile both the Virtual Network Device and the VMware Blocking Filesystem. After that, it fails to start the VMware services.
The log is posted above.
Please help! I must get VMware running within the day!
Last edited by qKUqm3wtY4 (2013-01-08 09:29:15)

Doesn't vmware always have problems with the latest kernel i.e. the one Arch ships? That's how I remember it, anyway, from those dark days when I was forced to use it - I had to go looking for patches every time.

Compile radeonfb kernel module

what I want to do, is to compile just radeonfb as a module (so that I could use it), without rebuilding anything else because the entire kernel takes way too long (like an hour or so).
How about this possibility;
a pkgbuild that builds the module seperately off of cvs or whatever the kernel is hosted on, (so that the 40 MB tarball doesn't have to get downloaded?)
not sure exactly how that works out, but it's probably possible, or is it all just not worth the effort?

Do you have a /proc/config.gz that you could use? Otherwise I don't know. I mean, many modules should be compilable simply with the system-installed kernel headers, but not all native modules might follow that rule.
Unfortunatel most of what you find on the web talks about how to create new modules which can be compild against the installed kernel tree, not about how to compile one of the native kernel modules against it.
Actually, try what those links suggest.
Skip the configuration part, and just do:
make -C /lib/modules/`uname -r`/build M=$(PWD)/drivers/video modules
(maybe `make -C /lib/modules/`uname -r`/build M=$(PWD)/drivers/video clean` first )
EDIT: Meh, that uses your config and won't build that driver... there must be some way though
EDIT2: Try:
make -C /lib/modules/`uname -r`/build M=$(PWD)/drivers/video modules CONFIG_FB_VT8623=m CONFIG_FB_SVGALIB=m
The problem though is, that they might have removed some of the dependencies of the module, so if it doesn't compile, you'll have to recompile the kernel.
Good thing is though, you can use their .config as base (found in /usr/src/linux-..../.config)
You can also check if your config "supports" your module by putting it into the kernel source tree, running `make menuconfig` and typing /8623 and pressing enter.
The last line in that screen should read:
Selects: <list of options>
As long as all of those options are either =y or =m, you're good. SVGALIB can be =n because it's part of drivers/video/ and you can compile it together with your module.
Last edited by Blµb (2012-03-02 15:14:16)

[Mini-HOWTO] RPMs needed to compile a kernel-module on / for VM Server

In reply to the question I've asked a couple of days ago in this forum
Compile module for Oracle VM Server
I tried to do it myself, since no answer was given.
And it turned out to be fairly easy afterward too!
Just install these RPM-packages from an Oracle Enterprise Linux v5 i386 distribution (v5, NOT v5U1!) in this order:
kernel-headers-2.6.18-8.el5.i386.rpm
glibc-headers-2.5-12.i386.rpm
glibc-devel-2.5-12.i386.rpm
libgomp-4.1.1-52.el5.i386.rpm
cpp-4.1.1-52.el5.i386.rpm
gcc-4.1.1-52.el5.i386.rpmThese 6 RPMs and finally the
kernel-ovs-devel-2.6.18-8.1.6.0.18.el5 RPM, to be found on the VM Server-CD you've burned from the downloaded ISO.
Hope this helps!
At least I was able to recompile the qla2xxx-modules from the HP-provided sources.
Message was updated by:
hbokho

basically it is the same thing as build a normal kernel module i think. some packages need to be installed first for e.g. the kernel source and development packages.
refer to, (just some google results)
http://www.eece.maine.edu/~sheaff/module.html
http://tldp.org/LDP/lkmpg/2.6/html/index.html
The system I installed the OVS on has a network chip
that is not supported by the kernel in OVS 2.1. I
found the source code for the module, but does anyone
have a clue how to set up an environment so I can
compile the module in a way that it'll be accepted on
the OVS server. I downloaded the Source OVS CD, but
I'm not quite sure what to do from there. Anybody has
some hints?

How to compile a kernel module without recompiling the whole kernel?

Hi,
I'm pretty sure my question is a bit newbish, still I haven't been able to found any information/solution to my problem in 3days.
The kernel I use doesn't come with the module I need for my hardware and I would like to know if there's a way to compile it without having to make a new kernel myself (since compiling the kernel takes ages on my machine).
Even if your answer is a "Let me Google that for you", I'm so desperate that I'll be happy to see it.
Thank you all in advance for your answers!

Do you have a /proc/config.gz that you could use? Otherwise I don't know. I mean, many modules should be compilable simply with the system-installed kernel headers, but not all native modules might follow that rule.
Unfortunatel most of what you find on the web talks about how to create new modules which can be compild against the installed kernel tree, not about how to compile one of the native kernel modules against it.
Actually, try what those links suggest.
Skip the configuration part, and just do:
make -C /lib/modules/`uname -r`/build M=$(PWD)/drivers/video modules
(maybe `make -C /lib/modules/`uname -r`/build M=$(PWD)/drivers/video clean` first )
EDIT: Meh, that uses your config and won't build that driver... there must be some way though
EDIT2: Try:
make -C /lib/modules/`uname -r`/build M=$(PWD)/drivers/video modules CONFIG_FB_VT8623=m CONFIG_FB_SVGALIB=m
The problem though is, that they might have removed some of the dependencies of the module, so if it doesn't compile, you'll have to recompile the kernel.
Good thing is though, you can use their .config as base (found in /usr/src/linux-..../.config)
You can also check if your config "supports" your module by putting it into the kernel source tree, running `make menuconfig` and typing /8623 and pressing enter.
The last line in that screen should read:
Selects: <list of options>
As long as all of those options are either =y or =m, you're good. SVGALIB can be =n because it's part of drivers/video/ and you can compile it together with your module.
Last edited by Blµb (2012-03-02 15:14:16)

Compile kernel module during install

Similar Messages

Maybe you are looking for