Problems with hostap driver

arimus25 · 03-18-2004, 09:14 PM

I ran "make" and "make install", that went through properl, but when I try "modprobe hostap_pci" it doesnt work. Here is what it says:

Quote:

[root@localhost root]# modprobe hostap_pci
/lib/modules/2.4.20-8/net/hostap.o: unresolved symbol register_netdevice
/lib/modules/2.4.20-8/net/hostap.o: unresolved symbol __netdev_watchdog_up
/lib/modules/2.4.20-8/net/hostap.o: unresolved symbol eth_type_trans
/lib/modules/2.4.20-8/net/hostap.o: unresolved symbol __wake_up
/lib/modules/2.4.20-8/net/hostap.o: unresolved symbol __kfree_skb
/lib/modules/2.4.20-8/net/hostap.o: unresolved symbol alloc_skb
/lib/modules/2.4.20-8/net/hostap.o: unresolved symbol pskb_expand_head
/lib/modules/2.4.20-8/net/hostap.o: unresolved symbol __write_lock_failed
/lib/modules/2.4.20-8/net/hostap.o: unresolved symbol ether_setup
/lib/modules/2.4.20-8/net/hostap.o: unresolved symbol skb_under_panic
/lib/modules/2.4.20-8/net/hostap.o: unresolved symbol unregister_netdevice
/lib/modules/2.4.20-8/net/hostap.o: unresolved symbol create_proc_entry
/lib/modules/2.4.20-8/net/hostap.o: unresolved symbol alloc_etherdev
/lib/modules/2.4.20-8/net/hostap.o: unresolved symbol remove_wait_queue
/lib/modules/2.4.20-8/net/hostap.o: unresolved symbol unregister_netdev
/lib/modules/2.4.20-8/net/hostap.o: unresolved symbol wireless_send_event
/lib/modules/2.4.20-8/net/hostap.o: unresolved symbol request_module
/lib/modules/2.4.20-8/net/hostap.o: unresolved symbol proc_mkdir
/lib/modules/2.4.20-8/net/hostap.o: unresolved symbol __read_lock_failed
/lib/modules/2.4.20-8/net/hostap.o: unresolved symbol dev_alloc_name
/lib/modules/2.4.20-8/net/hostap.o: unresolved symbol dev_queue_xmit
/lib/modules/2.4.20-8/net/hostap.o: unresolved symbol ___pskb_trim
/lib/modules/2.4.20-8/net/hostap.o: unresolved symbol remove_proc_entry
/lib/modules/2.4.20-8/net/hostap.o: unresolved symbol netif_rx
/lib/modules/2.4.20-8/net/hostap.o: unresolved symbol skb_over_panic
/lib/modules/2.4.20-8/net/hostap.o: unresolved symbol add_wait_queue
/lib/modules/2.4.20-8/net/hostap.o: unresolved symbol proc_net
/lib/modules/2.4.20-8/net/hostap.o: unresolved symbol skb_clone
/lib/modules/2.4.20-8/net/hostap.o: unresolved symbol softnet_data
/lib/modules/2.4.20-8/net/hostap.o: unresolved symbol irq_stat
/lib/modules/2.4.20-8/net/hostap.o: insmod /lib/modules/2.4.20-8/net/hostap.o failed
/lib/modules/2.4.20-8/net/hostap.o: insmod hostap_pci failed
[root@localhost root]#

Does anybody have any ideas?

beyer42 · 03-19-2004, 03:04 AM

Hopefully this is helpful:

Maybe something to try
http://lists.shmoo.com/pipermail/hos...ry/005307.html

Something else to keep in mind/try with versioning info
http://www.freenetworks.org/pipermai...ly/000239.html

Explanation of unresolved symbols and kernel versioning
http://www.tldp.org/HOWTO/Module-HOW...erncompat.html

arimus25 · 03-19-2004, 11:05 AM

Thanks. It looks like the first link will work, but when they say

Quote:

I always forget that the
RH kernel .src.rpm has this at the top of their rpm "spec" file:

I am not sure where that file is to edit it.

beyer42 · 03-19-2004, 11:51 AM

/usr/src/redhat/SPECS

have to install the SRPM file inorder to have the spec file.

Be very careful, save originals of any files that might change.

Have you recompiled your kernel successfully before?

arimus25 · 03-19-2004, 12:17 PM

I tried to recompile before, but it did not go through properly. As for the SPEC folder, there is nothing in it.

arimus25 · 03-19-2004, 07:11 PM

OK, I just tried to recompile my kernel again, and I think it went through properly, but I am not sure on one thing. Do I need to upgrade my lilo for the recompiled kernel?

beyer42 · 03-19-2004, 07:24 PM

I forget if my /etc/grub.conf was automatically updated. I know that the /boot files were updated automatically during make install of kernel.

Find out if you are booting lilo or grub and look at it's configuration file.
If it is not updated automatically then it should be straightforward to add a new entry, be sure to save copies of all config files that you edit.

One problem that I had was problems with LABEL=/root errors on boot which I had fixed by adding support for RAM DISK and size of 8192. I believe this was under block devices.

arimus25 · 03-19-2004, 10:07 PM

Actually, I am using grub, not lilo

Anyways, do I have to modify it? Here is what I have:

Quote:

# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/hdb2
# initrd /initrd-version.img
#boot=/dev/hda
default=0
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
title Red Hat Linux (2.4.20-8)
root (hd0,0)
kernel /vmlinuz-2.4.20-8 ro root=LABEL=/ hdd=ide-scsi
initrd /initrd-2.4.20-8.img

beyer42 · 03-19-2004, 10:26 PM

Here is a sample of what I have for my Redhat WS 3 system

You will want to change hd0,2 to hd0,0 for your system, etc.

default=2
timeout=10
splashimage=(hd0,2)/grub/splash.xpm.gz
title Red Hat Enterprise Linux WS (2.6.0)
root (hd0,2)
kernel /vmlinuz-2.6.0 ro root=LABEL=/ hdd=ide-scsi
initrd /initrd-2.6.0.img
title Red Hat Enterprise Linux WS (2.4.21-4.ELcustom)
root (hd0,2)
kernel /vmlinuz-2.4.21-4.ELcustom ro root=LABEL=/ hdd=ide-scsi
initrd /initrd-2.4.21-4.ELcustom.img
title Red Hat Enterprise Linux WS (2.4.21-4.EL)
root (hd0,2)
kernel /vmlinuz-2.4.21-4.EL ro root=LABEL=/ hdd=ide-scsi
initrd /initrd-2.4.21-4.EL.img
title DOS
rootnoverify (hd0,0)
chainloader +1

arimus25 · 03-19-2004, 10:51 PM

Im not exactly sure what I am looking at here. What lines are for the recompiled kernel?

beyer42 · 03-19-2004, 11:19 PM

Add the following lines and replace 2.4.20-8 with new kernel name.

title Red Hat Linux (2.4.20-8)
root (hd0,0)
kernel /vmlinuz-2.4.20-8 ro root=LABEL=/ hdd=ide-scsi
initrd /initrd-2.4.20-8.img

arimus25 · 03-20-2004, 01:22 AM

OK, now I am lost. When you recompile your kernel, doesnt that mean you are using the same version? Meaning if I am using 2.4.20-8 and if I recompile it, isnt it still 2.4.20-8?

beyer42 · 03-20-2004, 04:38 AM

yes, but need to do ls -l /boot to see what the name is, maybe the new kernel has "custom" or something tagged onto the end of the version.

arimus25 · 03-20-2004, 12:10 PM

When I try ls -l /boot, this is what I get:

Quote:

[root@localhost root]# ls -l /boot
total 6855
-rw-r--r-- 1 root root 5824 Jan 25 2003 boot.b
-rw-r--r-- 1 root root 612 Jan 25 2003 chain.b
-rw-r--r-- 1 root root 44252 Mar 13 2003 config-2.4.20-8
drwxr-xr-x 2 root root 1024 Feb 24 20:26 grub
-rw-r--r-- 1 root root 146218 Feb 24 19:40 initrd-2.4.20-8.img
-rw-r--r-- 1 root root 479 Feb 24 20:29 kernel.h
drwx------ 2 root root 12288 Feb 24 14:33 lost+found
-rw-r--r-- 1 root root 23108 Feb 24 2003 message
-rw-r--r-- 1 root root 21282 Feb 24 2003 message.ja
lrwxrwxrwx 1 root root 20 Feb 24 19:40 module-info -> module-info-2.4.20-8
-rw-r--r-- 1 root root 15436 Mar 13 2003 module-info-2.4.20-8
-rw-r--r-- 1 root root 640 Jan 25 2003 os2_d.b
-rw-r--r-- 1 root root 776482 Mar 6 13:27 System.map
-rw-r--r-- 1 root root 518322 Mar 13 2003 System.map-2.4.20-8
-rw-r--r-- 1 root root 3149072 Mar 13 2003 vmlinux-2.4.20-8
lrwxrwxrwx 1 root root 16 Feb 24 19:40 vmlinuz -> vmlinuz-2.4.20-8
-rw-r--r-- 1 root root 1117254 Mar 13 2003 vmlinuz-2.4.20-8
-rw-r--r-- 1 root root 1141041 Mar 6 13:27 vmlinuz-2.6.3
[root@localhost root]#

They problem that I see is when I recompiled the kernel, I did that on Mar 19, but I dont see that date there. Maybe when I recompiled I did it wrong. Do you have any info on how to do this properly to make sure I did it correctly?

P.S. Thanks for all of the help so far

beyer42 · 03-20-2004, 12:58 PM

Reconfiguring the kernel:

from the top level directory of the kernel source /usr/src/linux-<version> you will do

make mrproper -> done just once

make menuconfig -> brings up menu to set options to add
support for "Wireless LAN (non-hamradio)"

make depend

make modules

make modules_install

make install -> also installs boot images, etc.

Be sure to save off your original .config file before running any makes, this is a text file that contains the kernel configuration settings that are used to build the kernel and altered by make menuconfig.

On the make menuconfig:

Go to:
Network Device support −−>
then Select:
Wireless LAN (non−hamradio) −−−>
Then Choose the options, so that it looks like below, or something as close to this. [*] Wireless LAN (non−hamradio)

I usually have problems with unable to read LABEL on the root device when trying to reboot with the recompiled kernel, which is usually fixed by adding support for RAM disk support under Device Drivers -> Block Devices -> Ram disk support and setting the RAM disk size to 8192 (what works for me on Redhat).