Subject: Re: wlan-ng
From: Andy Firman (email@example.com)
Date: Sat May 03 2003 - 08:48:38 AKDT
> init_module: prism2_cs.o: 0.2.0 Loaded
> init_module: dev_info is: prism2_cs
> prism2_cs: index 0x01: Vcc 5.0, irq 3, io 0x0100-0x013f
> hfa384x_docmd_wait: hfa384x_cmd timeout(1), reg-0x8000
> hfa384x_drvr_start: Allocate(tx) command failed.
> hfa384x_drvr_start: Failed, result=-110
> prism2sta_ifstate: hfa384x_drvr_start() failed,result =-100
> I never paid any attention to the dmesg when it worked, but I'm sure all
> that hfa384x stuff wasn't there. It won't allow me to set the ip manually,
> I get the SIOCSFFLAGS: No such device error. Although, when I do iwconfig,
> it shows
> wlan0 IEEE 802.11b Mode:Auto Access Point: 00:00:00:00:00:00
> Encryption key:off
> wlan0 also shows up when I 'ifconfig -a' It seems funny for it to show up,
> but not exist at the same time. The wlan0 comes from the wlan-ng
> drivers...if I use the orinoco_cs drivers, it becomes ethX. (the orinoco
> drivers don't work anymore either)
> Nothinf\g has changed on the system. The only thing I've done, is used the
> card on WindowsXP pro. Think thats got something to do with it?
Sounds to me like you are having driver problems. When you put the card in,
do you hear a high beep and then a low beep?
I only have experience with the orinoco_cs driver.
So you have been using both drivers at different times?
This could be a bit messy. It took me a long time to get mine setup.
Sorry I could not be more help.
To unsubscribe, send email to <firstname.lastname@example.org>
with 'unsubscribe' in the message body.
This archive was generated by hypermail 2a23 : Sat May 03 2003 - 08:48:49 AKDT