Wirless Problems

sykotik · 2004-10-07 04:13:39

I have a Compaq Evo n800c laptop with a w200 multiport wireless network card that utilizes usb. The actual power is wired to the key combination FN(function)+F2. Hotplug seems to load the prism2_usb module as well as p80211.

Ive searched all over for imformation on this type of wireless device and I find conflicting information no matter where I go. On the gentoo forums, they said the module needed for this device is orinoco_usb.

One thing I do not understand is when I run iwconfig( i have wireless-tools and wlan-ng26 installed) i get a wlan0 interface, althought it says "no wireless devices available" I still shows up. It also shows up via ifconfig -a. If I rmmod the module prism2_usb, and do the same, the wlan0 interface does not show up in either iwconfig or ifconfig -a. If i modprobe orinoco it still does not show up. At this point I do not know which module to use since wlan0 shows up with prism2_usb loaded, yet on the gentoo forums, in a thread specific to my exact laptop they agreed the module needed was orinoco.

There also seems to be a problem bringing up the interface and or recognizing the interface. I downloaded the cvs version of orinoco drivers so that might be a problem, but I doubt it.

/var/log/messages after I unplug/plug back in the card

Oct  6 22:24:36 localhost net.agent[4295]: how do I bring interfaces up on this distro?
Oct  6 22:24:36 localhost net.agent[4295]: add event not handled

Something also may be wrong with the firmware because of this dmesg error:

usb 2-3: USB disconnect, address 9
usb 2-3: new full speed USB device using address 10
usb 2-3: config 1 has an invalid interface number: 1 but max is 0
usb 2-3: config 1 has no interface number 0
prism_usb_hard_reset - dummy
prism_usb_init - dummy
prism_usb_init - dummy
prism_usb_allocate - dummy
prism_usb_read_ltv - dummy
eth1: Cannot read hardware identity: error -95
eth1: Incompatible firmware, aborting
prism_usb: Cannot register network device
prism_usb: probe of 2-3:1.1 failed with error -95

Any help is greatly appreciated.

In addition this is the cat /proc/bus/usb/devices output for the device:

T:  Bus=02 Lev=01 Prnt=01 Port=02 Cnt=02 Dev#= 11 Spd=12  MxCh= 0
D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=049f ProdID=0033 Rev= 1.32
S:  SerialNumber=00217A001E4
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=500mA
I:  If#= 1 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=prism2_usb
E:  Ad=81(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=83(I) Atr=03(Int.) MxPS=   8 Ivl=1ms

Edit
After googling the device info, it reports as an orinoco device, seems udev got the driver wrong, or something else happened.

I think I need to have udev/hotplug load a different module, everytime I turn on the device the prism modules are loaded. Can anyone tell me how I can have a different module loaded when this device turns on.

phrakture · 2004-10-07 14:08:55

well, as far as the "how do i bring interfaces up" portion - you can nano /etc/hotplug/net.agent and see what it does (it's real small)....

if you want this functionality i would make a /sbin/ifup script as follows

#!/bin/bash
/sbin/ifconfig $1 up

and that message should be fixed...

phrakture · 2004-10-07 14:21:14

ok well i just came across this:

http://folk.uio.no/oeysteio/orinoco-usb/building.html

go to the "distros without rpms" section and grab that script - it downloads some junk and installs it (basically just orinoco cvs"

but it also does some firmware stuff - i'm not exactly sure whats going on - it makes some odd header file and then asks you to put it in a dir which doesn't exist (at least on my machine)

edit: it appears that the problem has to do with the firmware... this script above installs the proper crap needed - try that out... if there's any problems let me know

sykotik · 2004-10-07 16:01:57

After running that script, installing the latest orinoco drivers, and installing the last firmware, I unplugged/replugged in my wireless card. The same message were generate in dmesg and /var/log/messages.

phrakture · 2004-10-07 16:29:54

ok try

pacman -Rsn wlan-ng26

then rerun that build script above.
now

depmod -a

also make

#!/bin/bash
ifconfig $1 up

and save it as /sbin/ifup with 755 permissions

then rm /var/log/messages and reboot

hopefully your messages file will be cleaned up (the ifup script will make it so the "how do I bring up interfaces on this distro" messages are gone).
with wlan-ng26 gone, and that build script ran you shouldn't even have prism2 on your machine

sykotik · 2004-10-08 08:45:30

did this, but the prism_usb drivers are still on my system(i think they may be default of some sort) So when I power on the device(or attempt to) it is still trying to load the prism_usb instead of orinoco.

Note that the LED on the outside doesnt even turn on when I attempt to power it on(LED denotes power on/off)

phrakture · 2004-10-08 15:16:40

if it's anything like my laptop, my button is just for show... if i probe ndiswrapper with my right driver, the light comes on... button doesnt do jack.... when i rmmod ndiswrapper, the light turns off...

phrakture · 2004-10-08 17:23:06

brother, i made an ndiswrapper driver package for you - add my repo and grab

ndiswrapper-wlcomall

and see if it works

phrakture · 2004-10-08 19:06:46

now that everything has failed....

this guy overwriote his firmware and used prism2_usb.... you're getting firmware issues... may work:
http://www.psychosis.net/evo-linux/

also, try using fxload to load the firmware from the previous post...

there's also this:
http://www.foobar.be/~javdbuss/switchbl … 6649330744

Corneliax · 2004-11-23 05:48:39

I have an Evo n800c with 802.11b MultiPort Wireless LAN module. I'm not sure if that's the same wireless card as the w200 or not, but I do have the card working in Arch using the prism2_usb driver. The device may be on even if the light is off; after the reset step the light should come on.

Here's the process for loading the module then configuring it for your network:

install the wlan-ng26 arch package

####LOAD MODULE
modprobe prism2_usb prism2_doreset=1

####RESET CARD
wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable

####SETUP FOR WEP AND THEN CONNECT
wlanctl-ng wlan0 lnxreq_hostwep decrypt=true encrypt=true
wlanctl-ng wlan0 dot11req_mibset mibattribute=dot11WEPDefaultKeyID=0
wlanctl-ng wlan0 dot11req_mibset mibattribute=dot11ExcludeUnencrypted=true
wlanctl-ng wlan0 dot11req_mibset mibattribute=dot11PrivacyInvoked=true
wlanctl-ng wlan0 dot11req_mibset mibattribute=dot11WEPDefaultKey0=xx:xx:xx:xx:xx
wlanctl-ng wlan0 lnxreq_autojoin ssid="<your ssid>" authtype=sharedkey ##or opensystem

####DHCP
dhcpcd wlan0

Let me know if you need any more help

phrakture · 2004-11-24 00:56:07

holy crizzap that worked....
I think the key was the "ifstate=enable" which actually turns the hardware on

Corneliax · 2004-11-24 03:02:18

same reaction I had...

glad it helped out

famavolat · 2004-11-24 03:03:27

phrakture wrote:

holy crizzap that worked....
I think the key was the "ifstate=enable" which actually turns the hardware on

Actually it was probably the fact that he used wlanctl-ng and not iwconfig.
As I said at the bottom of this post:
http://bbs.archlinux.org/viewtopic.php? … light=wlan

iwconfig won't work for prism2-usb, it has something to do with the fact that the hardware/firmware doesn't support the commands given by the program, or vice versa.
I was having the same issue with my DWL-122

cjdj · 2004-11-26 22:12:02

famavolat wrote:

I was having the same issue with my DWL-122

I have a DWL-122 as well. Do you have a problem where your system wont shutdown if you dont down the interface first?

I forget the message it gives, but something about waiting for all clients to close.

usenix · 2005-02-24 00:30:16

i also have a dlink dwl-122 and this was the first time i got to run it on linux with the procede of corneliax - but is there a way to fix this configuration? i mean its boring to repeat these 9 steps at every reboot

cactus · 2005-02-24 00:49:52

usenix wrote:

i also have a dlink dwl-122 and this was the first time i got to run it on linux with the procede of corneliax - but is there a way to fix this configuration? i mean its boring to repeat these 9 steps at every reboot

couldn't you put them into a script, and attach it to hotplug so that every time the device is detected, it runs the script?

usenix · 2005-02-24 01:11:55

ok, let's see if we can bring together all informations in order to get work the usb dwl-122 (and should be the same procedure for all devices with prism2 chips):

be sure you have installed the wlan-ng package

# pacman -Q wlan-ng26

save a script called "wlan" in /etc/hotplug/usb and make it executable with chmod 755.

#!/bin/sh

###Load module (prism2_pci for pci devices)
modprobe prism2_usb prism2_doreset=1

###Reset Card
wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable

###SETUP FOR WEP AND THEN CONNECT
wlanctl-ng wlan0  dot11req_mibset  mibattribute=dot11WEPDefaultKeyID=0
wlanctl-ng wlan0  dot11req_mibset  mibattribute=dot11ExcludeUnencrypted=true
wlanctl-ng wlan0  dot11req_mibset  mibattribute=dot11PrivacyInvoked=true
wlanctl-ng wlan0  dot11req_mibset  mibattribute=dot11WEPDefaultKey0=00:01:02:03:04:05:06:07:08:09:0a:0b:0c
wlanctl-ng wlan0 lnxreq_autojoin ssid=<your_ssid> authtype=opensystem

###Static IP
#ifconfig wlan0 <ip_adresse>
#route add default gw <ip_gateway>

###DHCP
dhcpcd wlan0

exit 0

don't forget to set your WEP and SSID

then make a usermap called "wlan.usermap" and also save it in /etc/hotplug/usb
wlan is the script above which will be executed when the usb stick has been detected,
0x0003 seems to be the same id for all usb devices,
0x2001 is the vendor id,
0x3700 is the product id (both ids can be found with hwd -e).

#dwl-122
wlan    0x0003    0x2001    0x3700    0x0000    0x0000    0x00    0x00    0x00    0x00    0x00    0x00    0x00000000

so far, it works great for me but if you see something i could improve - please, let me know ...

iphitus · 2007-03-16 12:45:18

please file a bug for the 2.6.20-ARCH kernel at http://bugs.archlinux.org

Arch Linux

#1 2004-10-07 04:13:39

Wirless Problems

#2 2004-10-07 14:08:55

Re: Wirless Problems

#3 2004-10-07 14:21:14

Re: Wirless Problems

#4 2004-10-07 16:01:57

Re: Wirless Problems

#5 2004-10-07 16:29:54

Re: Wirless Problems

#6 2004-10-08 08:45:30

Re: Wirless Problems

#7 2004-10-08 15:16:40

Re: Wirless Problems

#8 2004-10-08 17:23:06

Re: Wirless Problems

#9 2004-10-08 19:06:46

Re: Wirless Problems

#10 2004-11-23 05:48:39

Re: Wirless Problems

#11 2004-11-24 00:56:07

Re: Wirless Problems

#12 2004-11-24 03:02:18

Re: Wirless Problems

#13 2004-11-24 03:03:27

Re: Wirless Problems

#14 2004-11-26 22:12:02

Re: Wirless Problems

#15 2005-02-24 00:30:16

Re: Wirless Problems

#16 2005-02-24 00:49:52

Re: Wirless Problems

#17 2005-02-24 01:11:55

Re: Wirless Problems

#18 2007-03-16 12:45:18

Re: Wirless Problems

Board footer