Installing Kernel Header files ?

hemanth83_in · 04-09-2008, 03:32 AM

Quote:

Originally Posted by colucix

Code:

ifeq ($(KVER),2.6)
default:
$(MAKE) -C $(KERNELDIR) M=$(PWD) modules
@if [ ! -w $(PWD)/release2.6 ] ; \
then mkdir $(PWD)/release2.6 ; \
fi
mv *.ko $(PWD)/release2.6 @echo "----------------- WLAN modules kernel 2.6 built ----------------"
endif

hemanth83_in, I think you've found where the problem comes from. It looks like the KERNELDIR variable is not properly assigned in the Makefile (and left empty). The resulting command line should be something like

Code:

make -C /usr/src/linux M=/root/src modules

but since the value of KERNELDIR is null, it generates a wrong make command. Try to investigate further.

Thank you for the reply Colucix. Yes i too think the same about the KERNELDIR variable. But the Makefile is very big, the makefile supports different kernel versions and for different versions of OS. So i donot exactly know where to assign the KERNELDIR.

One question is: Is the kernel directory /usr/src/linux/ ?????? if so i could see one more folder in usr/src/ as Kernels containing folder called 2.6.24.4-64.fc8 -i686, Is this not the Kerneldir ??

hemanth83_in · 04-09-2008, 03:39 AM

when i edit makefile and make
Kerneldir= /usr/src/linux, and run the command it returns the following:

[root@wireless src]# make KVER=2.6
make -C /usr/src/linux M=/root/src modules
make[1]: Entering directory `/usr/src/kernels/2.6.24.4-64.fc8-i686'
scripts/Makefile.build:46: *** CFLAGS was changed in "/root/src/Makefile". Fix it to use EXTRA_CFLAGS. Stop.
make[1]: *** [_module_/root/src] Error 2
make[1]: Leaving directory `/usr/src/kernels/2.6.24.4-64.fc8-i686'
make: *** [default] Error 2

colucix · 04-09-2008, 05:19 AM

Uuuuhh... this make is a little boring!

Try this

Code:

make KVER=2.6 KBUILD_NOPEDANTIC=1

hemanth83_in · 04-09-2008, 06:28 AM

Yes its a bit boring, i tried but then i get

[root@wireless src]# make KVER=2.6 KBUILD_NOPEDANTIC=1
make -C /usr/src/linux M=/root/src modules
make[1]: Entering directory `/usr/src/kernels/2.6.24.4-64.fc8-i686'
Building modules, stage 2.
MODPOST 0 modules
make[1]: Leaving directory `/usr/src/kernels/2.6.24.4-64.fc8-i686'
mv *.ko /root/src/release2.6
mv: cannot stat `*.ko': No such file or directory
make: *** [default] Error 1
[root@wireless src]#

colucix · 04-09-2008, 07:08 AM

Code:

Building modules, stage 2.
MODPOST 0 modules

Sorry... but I'm totally lost now! For some reason it does not build any module and it's difficult for me to investigate without being sit in front of your machine. As a last chance, can you let me know where to donwload the source code of the driver, so I can test?

hemanth83_in · 04-09-2008, 07:47 AM

Quote:

Originally Posted by colucix

Code:

Building modules, stage 2.
MODPOST 0 modules

Sorry... but I'm totally lost now! For some reason it does not build any module and it's difficult for me to investigate without being sit in front of your machine. As a last chance, can you let me know where to donwload the source code of the driver, so I can test?

Hi,

Thank you very much for the help. you can download the drivers from the following link http://rapidshare.com/files/10609476...aptor.tar.html

If you have any sucess please let me kow. Thank you again

hemanth83_in · 04-10-2008, 01:53 AM

Hey, did you try to install the drivers? Is there any sucess?

colucix · 04-10-2008, 05:10 AM

Yes, I've just tried but with no success. It tries to compile but there are a lot of different C errors (wrong declaration, wrong number of arguments passed to function, files not found and so on). I tried to workaround some of them, but it look like an endless circle.

Anyway I did not tweak the Makefile adding the assigment of KERNELDIR, nor I received the message "Building modules, stage 2." at the beginning. Here are my steps.

1. verify kernel-devel and kernel-headers are installed

2. cd /root/src
cp -p config-8686 .config
and edit .config assigning KVER=2.6

3. cd /usr/src
ln -s /usr/src/kernels/2.6.23.15-137.fc8-i686 linux

4. cd /root/src
make KVER=2.6

Also, after any attempt to compile I issued the command

Code:

make distclean

this clear any reference to the previous compilation attempt and delete any (already) built object file. Unfortunately, I cannot be of much help at this point.

hemanth83_in · 04-10-2008, 05:27 AM

Quote:

Originally Posted by colucix

Yes, I've just tried but with no success. It tries to compile but there are a lot of different C errors (wrong declaration, wrong number of arguments passed to function, files not found and so on). I tried to workaround some of them, but it look like an endless circle.

Anyway I did not tweak the Makefile adding the assigment of KERNELDIR, nor I received the message "Building modules, stage 2." at the beginning. Here are my steps.

1. verify kernel-devel and kernel-headers are installed

2. cd /root/src
cp -p config-8686 .config
and edit .config assigning KVER=2.6

3. cd /usr/src
ln -s /usr/src/kernels/2.6.23.15-137.fc8-i686 linux

4. cd /root/src
make KVER=2.6

Also, after any attempt to compile I issued the command

Code:

make distclean

this clear any reference to the previous compilation attempt and delete any (already) built object file. Unfortunately, I cannot be of much help at this point.

Thanks. Do you think its the version of GCC you are using is creating a problem? which version of gcc are you using?

colucix · 04-10-2008, 05:42 AM

Code:

# gcc --version
gcc (GCC) 4.1.2 20070925 (Red Hat 4.1.2-33)

I tested on a Fedora Core 8 with kernel 2.6.23.15-137.fc8 to match your conditions as much as possible. It could be a problem with gcc, as previously suggested by lazlow. You can always give it a try. Fedora Core 8 gives the possibility to install gcc 3.4.6 (look for compat-gcc-34 and related packages).

hemanth83_in · 04-10-2008, 06:31 AM

ok i ll ry with the gcc 3.4.6 version. I am using the kernel 2.6.24.4-64.fc8-i686 version, does it have any influence to the installation. Do you think that i have to downgrade my kernel version to the one which you are using?

colucix · 04-10-2008, 09:13 AM

No. I don't see any reason to do that, right now! I tested on the previous kernel because I could not reboot my machine to install the new one.