Chumby WiFi cookbook fail
Moderators: adafruit_support_bill, adafruit
Please be positive and constructive with your questions and comments.
-
- Posts: 12151
- Joined: Thu Apr 06, 2006 4:21 pm
Re: Chumby WiFi cookbook fail
That would be great. Thanks for helping us out with this. we will get it working!
- dbc
- Posts: 62
- Joined: Thu Jan 06, 2011 7:37 pm
Re: Chumby WiFi cookbook fail
OK, this is hopeful, but something isn't quite right and I'm a little confused.
Using the new driver and the same procedure I outlined earlier in the thread, plug-in events generate this:
Which looks pretty happy, as does this:
But... two odd things. When I try to run my modified start_ap.sh (see wiki article about stand alone AP) I get this:
nl80211 not found???? But the config file from /proc/config.gz says:
so I would think nl80211 would be built into the kernel. Something is wacky here and I don't understand the WiFi driver stack well enough to know where to look.
The second curious thing is that I'm now getting periodic empty lines printed to the dmesg output... which of course is intermixed in the serial console output so it tends to come up in the middle of typing a command line causing severe ugliness and some confusion. So my guess is the driver has some kind of periodic logging going on in it that needs to be squashed.
I'm not sure how to chase down either of these two oddities. Send clues if you have them.
Using the new driver and the same procedure I outlined earlier in the thread, plug-in events generate this:
Code: Select all
[ 49.120000] usb 1-1.3: new high speed USB device using fsl-ehci and
4
[ 49.330000] usb 1-1.3: configuration #1 chosen from 1 choice
[ 49.870000] rtusb init --->
[ 49.880000]
[ 49.880000]
[ 49.880000] === pAd = c4a73000, size = 500648 ===
[ 49.880000]
[ 49.890000] <-- RTMPAllocAdapterBlock, Status=0
[ 49.940000] usbcore: registered new interface driver rt2870
[ 50.960000] <-- RTMPAllocTxRxRingMemory, Status=0
[ 50.980000] -->RTUSBVenderReset
[ 50.990000] <--RTUSBVenderReset
[ 51.740000] Key1Str is Invalid key length(0) or Type(0)
[ 51.740000] Key2Str is Invalid key length(0) or Type(0)
[ 51.750000] Key3Str is Invalid key length(0) or Type(0)
[ 51.750000] Key4Str is Invalid key length(0) or Type(0)
[ 51.760000] 1. Phy Mode = 5
[ 51.770000] 2. Phy Mode = 5
[ 51.770000] NVM is Efuse and its size =2d[2d0-2fc]
[ 51.920000] RTMPSetPhyMode: channel is out of range, use first channel=1
[ 51.990000] 3. Phy Mode = 9
[ 52.150000] MCS Set = ff 00 00 00 01
[ 52.190000] <==== rt28xx_init, Status=0
[ 52.190000] 0x1300 = 00064300
Code: Select all
chumby-:/ # iwlist wlan0 scan
[ 1536.000000] ===>rt_ioctl_giwscan. 6(6) BSS returned, data->length = 863
wlan0 Scan completed :
Cell 01 - Address: B0:E7:54:47:08:41
Protocol:802.11b/g
<the rest of my neighbor's WiFi info snipped out :) >
Code: Select all
chumby-:/BANNED/rfs1 # ./start_ap.sh [ 1669.350000] #
[ 1671.440000] ---> RTMPFreeTxRxRingMemory
[ 1671.440000] <--- RTMPFreeTxRxRingMemory
Configuration file: /tmp/hostapd.conf
nl80211 not found.
nl80211 driver initialization failed.
rmdir[ctrl_interface]: No such file or directory
[ 1672.320000] <-- RTMPAllocTxRxRingMemory, Status=0
[ 1672.340000] -->RTUSBVenderReset
[ 1672.340000] <--RTUSBVenderReset
[ 1673.110000] CfgSetCountryRegion():CountryRegion in eeprom was programmed
[ 1673.120000] CfgSetCountryRegion():CountryRegion in eeprom was programmed
[ 1673.140000] Key1Str is Invalid key length(0) or Type(0)
[ 1673.140000] Key2Str is Invalid key length(0) or Type(0)
[ 1673.150000] Key3Str is Invalid key length(0) or Type(0)
[ 1673.150000] Key4Str is Invalid key length(0) or Type(0)
[ 1673.170000] 1. Phy Mode = 5
[ 1673.170000] 2. Phy Mode = 5
[ 1673.170000] NVM is Efuse and its size =2d[2d0-2fc]
[ 1673.320000] RTMPSetPhyMode: channel is out of range, use first channel=1
[ 1673.380000] 3. Phy Mode = 9
[ 1673.540000] MCS Set = ff 00 00 00 01
[ 1673.580000] <==== rt28xx_init, Status=0
[ 1673.590000] 0x1300 = 00064300
Code: Select all
CONFIG_WIRELESS=y
CONFIG_CFG80211=m
CONFIG_NL80211=y
The second curious thing is that I'm now getting periodic empty lines printed to the dmesg output... which of course is intermixed in the serial console output so it tends to come up in the middle of typing a command line causing severe ugliness and some confusion. So my guess is the driver has some kind of periodic logging going on in it that needs to be squashed.
I'm not sure how to chase down either of these two oddities. Send clues if you have them.
- dbc
- Posts: 62
- Joined: Thu Jan 06, 2011 7:37 pm
Re: Chumby WiFi cookbook fail
and a third odd thing... unplugging the dongle generates an infinite loop of:
which is a pretty ugly bug.
Code: Select all
[ 2526.600000] WIFI device has been disconnected
-
- Posts: 46
- Joined: Sat Dec 25, 2010 9:19 pm
Re: Chumby WiFi cookbook fail
With the original driver, have you tried bringing the interface up before you scan? I have that problem with with one of my wireless cards. Try issuing
and then scanning, that might fix things. Then again it could be something completely different
Code: Select all
ifconfig up wlan0
- dbc
- Posts: 62
- Joined: Thu Jan 06, 2011 7:37 pm
Re: Chumby WiFi cookbook fail
Which driver do you mean by "original driver"? The first one I tried won't load because it was compiled against the wrong kernel. The second one scans OK.
-
- Posts: 1
- Joined: Sat Feb 05, 2011 8:10 am
Re: Chumby WiFi cookbook fail
Same issue here, I hope Adafruit will find a solution for the wireless controller they recommended to us...
Ps: with the base driver does not help.
Ps:
Code: Select all
ifconfig wlan0 up
-
- Posts: 12151
- Joined: Thu Apr 06, 2006 4:21 pm
Re: Chumby WiFi cookbook fail
we are on it! this coming week we will do our best to adapt the tutorial or find some other way to solve the problem
- dbc
- Posts: 62
- Joined: Thu Jan 06, 2011 7:37 pm
Re: Chumby WiFi cookbook fail
I really think this is very close. The "infinite unplug messages" issue should be a simple bug, or maybe even something I didn't configure correctly. The 'nl80211 not found' issue is either a minor build issue, or a PEBKAC on my part. But the driver loads and is recognized, so we should be down to minor tweaks at this point.
A couple of days ago I was able to cross-compile "hello world" with ScratchBox and it actually worked, so in theory I should be able to build drivers now. Unfortunately, I'm not at all familiar with the WiFi driver stack, so while I suspect these bugs are shallow in principal, they aren't shallow for me
A couple of days ago I was able to cross-compile "hello world" with ScratchBox and it actually worked, so in theory I should be able to build drivers now. Unfortunately, I'm not at all familiar with the WiFi driver stack, so while I suspect these bugs are shallow in principal, they aren't shallow for me
- jlynn
- Posts: 1
- Joined: Thu Feb 24, 2011 1:33 am
Re: Chumby WiFi cookbook fail
Has their been any progress on this issue? I also have the same problem with a recent purchase of the wifi adapter with the chumby board. The unit I have shows v4, and the same diagnostic messages.
Thanks,
Jonathan
Thanks,
Jonathan
-
- Posts: 12151
- Joined: Thu Apr 06, 2006 4:21 pm
Re: Chumby WiFi cookbook fail
we're working on it today
-
- Posts: 12151
- Joined: Thu Apr 06, 2006 4:21 pm
Re: Chumby WiFi cookbook fail
OK thank you everyone for your patience! We wanted to make sure this was really good to go. We've had no problems with this new driver
Please visit:
http://www.ladyada.net/wiki/chumbyhacke ... ifi#dongly
Download the RT2800 driver script and run it
Let us know if it does/doesn't work for you!
Please visit:
http://www.ladyada.net/wiki/chumbyhacke ... ifi#dongly
Download the RT2800 driver script and run it
Let us know if it does/doesn't work for you!
-
- Posts: 4
- Joined: Fri Feb 26, 2010 9:21 pm
Re: Chumby WiFi cookbook fail
I am happy to report that it does indeed work. My CHB is now WiFi connected and happily humming along.
I have one of the V4 TP-Link RT2800 based modules. I started over with a clean install of falconwing and added the new driver. Everything went just like the tutorial.
Thanks,
Randy
I have one of the V4 TP-Link RT2800 based modules. I started over with a clean install of falconwing and added the new driver. Everything went just like the tutorial.
Thanks,
Randy
-
- Posts: 1
- Joined: Fri Jan 07, 2011 7:48 pm
Re: Chumby WiFi cookbook fail
Really appreciate the work that has gone into getting this to work with the RT2800 version 4 wifi dongles. That being said would it be possible to update the wiki to be a bit more clear that - if you get no networks returned from a iwlist wlan0 scan - you might have a version 4 dongle and need to install the RT2800 update? Glossed over that little fact a bunch of times since there is nothing that really points out there are different versions of the dongle in the wild on the wiki. Finally found this post and got it sorted!!
Please be positive and constructive with your questions and comments.