From: Mike Tyson (flood_at_tzidesign.com)
Date: 2002-08-15 06:45:31 UTC
> These are more or less the first things done after card init. If the
> PCI
> BIOS revision does not explain the problem, you could try increasing
> the
> COR sreset delay in hostap_pci.c by defining
> PRISM2_PCI_USE_LONG_DELAYS.
>
>
I did what you suggested, recompiled and installed, but unfortunately received the same error:
sbox:/home/devel/hostap# modprobe hostap_pci /lib/modules/2.4.19/net/hostap_pci.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
/lib/modules/2.4.19/net/hostap_pci.o: insmod /lib/modules/2.4.19/net/hostap_pci.o failed /lib/modules/2.4.19/net/hostap_pci.o: insmod hostap_pci failed
dmesg:
hostap_crypt: registered algorithm 'NULL' hostap_pci: hostap_pci.c 0.0.0 CVS (SSH Communications Security Corp, Jouni Malinen)
hostap_pci: (c) SSH Communications Security Corp <jkm_at_ssh.com> hostap_pci: Registered netdevice wlan0 prism2_hw_init() prism2_hw_config: initialized in 5 iterations wlan0: CMD=0x000a => res=0x7f wlan0: cannot allocate fid, len=2364
hostap_pci: Initialization failed hostap_pci: hardware initialization failed hostap_pci: Netdevice wlan0 unregistered prism2_pci: No devices found, driver not installed. hostap_crypt: unregistered algorithm 'NULL' (deinit)