Wifi & Linksys WUSB11
Posts: 17
Bonjour !
J'utilise pour le connecter ?? internet un adaptateur wifi/usb (le linksys WUSB11 ver 2.6)
J'ai install?? le driver berlios bas?? sur atmel (at76c503-0.11).
Pour ce p??riph??rique il faut modifier une ligne de la source (je l'ai fait).
Apr??s compilation et installation, pourtant, pas moyen d'utiliser le p??riph??rique ! 
Quand je branche le wusb11, dmesg me donne :
usb-uhci.c: interrupt, status 2, frame# 978
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 18 ret -84
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 18 ret -84
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 18 ret -84
usb.c: USB disconnect on device 00:0c.0-1 address 2
M??me si le module est charg??, je ne trouve pas comment d??marrer le p??riph??rique...
Merci de votre aide !
Remarque : je suis un newbie, donc j'ai un peu de mal. La solution est peut-??tre ??vidente, mais je ne sais pas laquelle mettre en place...
Vous ??tes sur la bonne pis
Posts: 178
Vous ??tes sur la bonne piste maintenant..
Thanks for the pointer and the link.
miladus edenensis
But the 2.6 came back to atmel
Posts: 17
Visiblement, seule la version 2.5 a utilis?? un chipset prism.
La 2.6 utilise bien un atmel. J'avais eu la m??me d??marche, et apr??s avoir install?? le driver prism, la machine gelait syst??matiquement quand je branchais le p??riph??rique. Je n'ai plus ce probl??me avec le driver berlios/atmel (m??me si ??a ne fontionne toujours pas).
Mais je peux toujours me tromper !
Merci pour une r??ponse si rapide !
It seems that only the 2.5 uses ths prism chipset.
The 2.6 uses the atmel one. I thought like you first, but after I installed the prism driver, my computer always froze when I plugged the wusb11. And I don't have now this problem with the berlios/atmel driver (however, I still doesn't work).
But I might be wrong !
Thanks for answering so fast !
you're right, pardon!
Posts: 223
You're right. They do claim that the WUSB v2.6 has been verified working with the atmel driver. Sorry!
:-)
Posts: 17
Ca me rassure, je ne m'etais pas non plus compl??tement tromp?? ! 
Mais quelqu'un a-t-il une id??e sur le sens de ce truc ?
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 18 ret -84
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 18 ret -84
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 18 ret -84
usb.c: USB disconnect on device 00:0c.0-1 address 2
Merci de votre aide !
No problem
But does anyone know what's the meaning of my error message ?
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 18 ret -84
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 18 ret -84
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 18 ret -84
Thanks for your help !
wusb11 v2.6 needs uhci.o instead of usb-uhci.o
Posts: 223
Taking another blind stab at something I know nothing about, have you seen this: http://www.qbik.ch/usb/devices/showdev.php?id=1218. The last comments are a year old, but they say with the v2.6, you need to use uhci.o instead of usb-uhci.o. Hopefully that's more helpful than my first comment.
Merci beaucoup ! Je n'ai pl
Posts: 17
Merci beaucoup !
Je n'ai plus ce message d'erreur !
Mais ??a ne fonctionne toujours pas : je n'ai pas de r??ponse de mon point d'acc??s
ifconfig me donne :
wlan0 Lien encap:Ethernet HWaddr 00:06:25:1A:47:13
UP BROADCAST RUNNING MTU:1500 Metric:1
RX packets:80 errors:0 dropped:0 overruns:0 frame:0
TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:100
RX bytes:28448 (27.7 KiB) TX bytes:1548 (1.5 KiB)
et iwconfig :
wlan0 IEEE 802.11-DS ESSID:"linksys" Nickname:"okuwlan"
Mode:Managed Channel:6 Access Point: 00:06:25:9B:CA:28
Bit Rate=11Mb/s
RTS thr=1536 B Fragment thr=1536 B
Encryption key:off
Power Management:off
Link Quality:0 Signal level:40 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
je pense avoir tout bien configur??, pourtant le Mepis System Center m'affiche toujours
wlan0 ip : arr??t??
j'ai tap?? les commandes pour d??clarer que je me connecte via une passerelle :
ifconfig wlan0 192.168.1.1
route add default gw 192.168.1.1 Mais je ne peux ni me connecter au r??seau local, ni acc??der ?? internet.
Au d??marrage, j'ai toujours Operation failed au moment de la conection au r??seau (par contre, ??a fonctionne pour eth0).
Merci de votre aide !!
(Remarque : ce n'est pas un probl??me de configuration de mon routeur, puisque sous windows, ??a fonctionne)
Thank you very much !
The WUSB11 works now !
However, I can't get connecting to my LAN ou to the Internet : my router doesn't give me an IP adress.
I have got the messages upper for ifconfig and iwconfig.
While loading Mepis, it finds the WUSB11, but it can't get an IP adress with DHCP.
Thanks for your help !
more wild guesses from the peanut gallery
Posts: 223
I wish someone who was more of a networking expert than me would speak up so I wouldn't keep having to take guesses at this, or someone who could at least read French maybe... 
By the way, I finally got the idea to try translating this page through Google (I know, I'm slow). And I can't believe you call yourself a newbie. You seem to be more competent than 90% of the people on this forum. You're looking at all the right error messages, getting your hands way dirty before asking for help... Hell, I suggested you might need uhci.o instead of usb-uhci.o, but I don't even know how you would (or did) go about doing that. Thank god for Google, huh?
That said, a couple ideas: Other people on here also seem to have problems with MEPIS trying to bring up network interfaces too early in the boot up sequence, before other necessary services have started. I saw the same thing on a friend's computer where he was bringing Ethernet into it through USB instead of the regular NIC. People have suggested trying "pump -i {interface}" where interface was eth0, but in your case it would be wlan0. Others have put a small script in rc5.d to do an ifup right before X starts up.
The second thing may just be a typing error you made. Did you really mean "ifconfig wlan0 192.168.1.1"? If 192.168.1.1 is your router, the your route command is correct, but your ifconfig should be assigning an IP for your machine, not the router. Any IP in your network that isn't already in use should work, so for example 192.168.1.27?
You're sooooooooo close, it seems a shame to give up now.
Best of luck,
--Yong
~
Posts: 17
I call myself a newbie beacause I am !
All the things I did were found on other forums or mailing-lists !
I'm starting to understand how does Linux work, but not everything !
I still need a lot of help to do a simple task.
For the UHCI, I just replaced in a config file (whichj one I forgot the name) usb-uhci by uhci alone.
And it seems to work...
I'll try the
pump - i wlan0
but I have absolutely no idea about the way to use the script in rc5.d
Sorry, but I may have not understood your sentence :
when I type ifconfig wlan0 192.168.1.1 I set my ROUTER IP ou my COMPUTER IP ?
Thank you for your answers !! And I won't give up now, don't worry !
Alban
ifconfig wlan0 192.168.1.n
Posts: 223
ifconfig wlan0 192.168.1.n sets the IP address on your computer. So you do not want to set it to 192.168.1.1, because that's the IP of your router. You should set it to something else, like 192.168.1.2 or 192.168.1.21 or 192.168.1.243.
Actually, to be more correct, ifconfig sets the IP on the interface on your computer. You could have multiple IPs on your computer, for example if you had two Ethernet NICs, a modem, and a wireless card, you could set eth0 to 192.168.1.2, eth1 to -.3, ppp0 to -.4, and wlan0 to -.5. That is how people can use a computer as a router, by having more than one Ethernet interface.
As for a start script in /etc/rc5.d, let's first find out how to get it working before worrying about how to get it working automatically on startup.
ok, thank you very much ! how
Posts: 17
ok, thank you very much !
however, i have now an other problem.
just after the first reboot, I got each time the computer starts :
hub.c: new USB device 00:0c.0-1, assigned address 3
usbdfu.c: Downloading firmware for USB device 3...
usb.c: USB disconnect on device 00:0c.0-1 address 3
hub.c: new USB device 00:0c.0-1, assigned address 4
usbdfu.c: Downloading firmware for USB device 4...
usb.c: USB disconnect on device 00:0c.0-1 address 4
It doesn't smell good, does it ?
no more MTRRs available
Posts: 223
This thread seems to indicate MTRRs have something to do with RAM, specifically large amounts of RAM and possibly BIOS settings, if you read all the messages in the thread: http://www.ussg.iu.edu/hypermail/linux/kernel/0301.3/1026.html Other than that, I have no idea, sorry.
hum...
Posts: 17
Thank you :!: 
But... I don't understand at all 
on the one hand because I don't speak very well "computering-english", and on the other hand because I am still a newbie.
To sumarize, is there anything to do with my config files ?
Moreover, I read that the answer was for a kernel 2.5 : there may be a difference with my 2.4.22 ?
Thanks again :!:
Alban
I don't know
Posts: 223
Sorry, the main message in my response was that I don't know. I don't even know if the mtrr error is related to the usb errors. It's possible they're entirely unrelated. In the thread above, it sounded like the guy fixed his problem by changing a setting in his BIOS, but I'm not certain. And the problem seemed to only apply to people with a huge amount of RAM, like more than 4 Gb...
ok
Posts: 17
ok, thank you either.
to my mind, the problem comes from usb, because when the wusb11 is not plugged, i don't have this error message.
WUSB11 v2.6 graphical snapshots of Mepis OS center setup
Posts: 13
Fred Finster
WB7ODY
The Linksys WUSB11 has to have firmware downloaded inside it
first for the wireleses adapater to run/operate
here are some console commands to try.
ifconfig wlan0 192.168.1.4 essid any channel 11
ifup wlan0
dhclient wlan0
route
root@1[~]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 wlan0
default 192.168.1.1 0.0.0.0 UG 0 0 0 wlan0
Look to see if in the route command shows the default gateway at your router address of 192.168.1.1
root@1[~]# iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
eth1 no wireless extensions.
wlan0 IEEE 802.11-DS ESSID:"NETGEAR" Nickname:"NETGEAR"
Mode:Managed Frequency:2.462 GHz Access Point: 00:14:6C:1E:83:20
Bit Rate:11 Mb/s Tx-Power=15 dBm
Retry limit:8 RTS thr=1536 B Fragment thr=1536 B
Encryption key:off
Power Management:off
Link Quality=0/0 Signal level=25/255 Noise level=0/0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
dmesg | tail -80
[ 103.976315] usbcore: registered new driver hiddev
[ 103.995750] drivers/usb/net/atmel/at76_usbdfu.c: USB Device Firmware Upgrade (DFU) handler v0.12beta23-fw_dwl loading
[ 103.996891] input: HID 1241:1111 as /class/input/input2
[ 103.997046] input: USB HID v1.10 Mouse [HID 1241:1111] on usb-0000:00:02.3-1.1
[ 103.997078] usbcore: registered new driver usbhid
[ 103.997086] drivers/usb/input/hid-core.c: v2.6:USB HID core driver
[ 104.042242] drivers/usb/net/atmel/at76c503.c: Generic Atmel at76c503/at76c505 routines v0.12beta23-fw_dwl
[ 104.044164] drivers/usb/net/atmel/at76c503-fw_skel.c: Atmel at76c503 (RFMD) Wireless LAN Driver v0.12beta23-fw_dwl loading
[ 104.044236] drivers/usb/net/atmel/at76c503-fw_skel.c: downloading firmware atmel_at76c503-rfmd.bin
[ 104.300588] drivers/usb/net/atmel/at76c503-fw_skel.c: got it.
[ 104.301921] usbcore: registered new driver at76c503-rfmd
[ 106.786084] usb 2-1.2: device firmware changed
[ 106.790054] usb 2-1.2: USB disconnect, address 4
[ 106.790120] drivers/usb/net/atmel/at76c503-fw_skel.c: wlan%d disconnecting
[ 106.790135] drivers/usb/net/atmel/at76c503-fw_skel.c: at76c503-rfmd disconnected
[ 106.818275] powernow-k8: Processor cpuid 642 not supported
[ 106.863070] usb 2-1.2: new full speed USB device using ohci_hcd and address 6
[ 106.864554] powernow: No powernow capabilities detected
[ 106.973040] drivers/usb/net/atmel/at76c503-fw_skel.c: downloading firmware atmel_at76c503-rfmd.bin
[ 107.011716] drivers/usb/net/atmel/at76c503-fw_skel.c: got it.
[ 107.101171] ndiswrapper version 1.8 loaded (preempt=yes,smp=no)
[ 107.150824] drivers/usb/net/atmel/at76c503.c: $Id: at76c503.c,v 1.74 2005/03/08 01:33:14 jal2 Exp $ compiled Jun 19 2006 00:15:21
[ 107.150839] drivers/usb/net/atmel/at76c503.c: firmware version 1.101.4 #84 (fcs_len 4)
[ 107.153826] drivers/usb/net/atmel/at76c503.c: device's MAC 00:06:25:26:fc:40, regulatory domain FCC (U.S) (id 16)
[ 107.153991] drivers/usb/net/atmel/at76c503.c: registered wlan0
[ 107.167031] usbcore: registered new driver ndiswrapper
[ 107.514191] wlan0 (WE) : Driver using old /proc/net/wireless support, please fix driver !
[ 109.536518] NET: Registered protocol family 17
[ 111.233950] ReiserFS: hdb5: found reiserfs format "3.6" with standard journal
[ 111.737739] ReiserFS: hdb5: using ordered data mode
[ 111.780932] ReiserFS: hdb5: journal params: device hdb5, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
[ 111.785047] ReiserFS: hdb5: checking transaction log (hdb5)
[ 111.830991] ReiserFS: hdb5: Using r5 hash to sort names
[ 112.787918] Netfilter messages via NETLINK v0.30.
[ 112.812036] ip_conntrack version 2.4 (4608 buckets, 36864 max) - 232 bytes per conntrack
[ 121.331032] eth0: Media Link Off
[ 124.350681] 0000:00:11.0: tulip_stop_rxtx() failed (CSR5 0xfc664010 CSR6 0xff972113)
[ 124.350703] eth1: Setting full-duplex based on MII#1 link partner capability of 45e1.
[
Look at the at76C503 driver firmware loading then the wlan0 appearing.
My webpage with the the long list of graphic Snapshots for MEPIS old OS Center in MEPIS6.0 rc2. This is now under mutilities in MEPIS6.0 rc 3
http://home.kendra.com/tulip/mepis6
Would like comments in how to setup wireless lans with newer version Mepis6 rc3 and above. Can you take some screen snapshots using program ksnapshot. and e-mail them to me at
fredf at kendra dot com Thank you
WUSB11 v2.5 uses Prism not Atmel
Posts: 223
First of all, I don't speak French, so forgive me if I've misunderstood. But if you look here:
http://www.linux-wlan.org/docs/wlan_adapters.html.gz
it looks like beginning with v2.5, the WUSB11 now uses Prism chips rather than Atmel, so you probably need the wlan-ng driver rather than atmel.