little radio driver needed
geek at uniserve.com
Thu Dec 31 17:56:02 UTC 2015
Quoting Nils Kassube <kassube at gmx.net>:
> Dave Stevens wrote:
>> Quoting Nils Kassube <kassube at gmx.net>:
>> > So the first of these two lines indicates, that your part should be
>> > supported by the wily kernel.
>> Thanks, Connie, Nils. I'm almost there. I found and installed the
>> driver and now have a script like this:
> Could you elaborate? Which Ubuntu version do you have and how did you
> install the driver? Is it the Wily kernel for 14.04 or something else?
please see below.
>> #! /bin/bash
>> ifconfig wlan0
>> iwconfig wlan0 essid bigkahoona
>> dhclient wlan0
>> At this point the activity log on the router shows that it has
>> connected a wireless pc but as you can see from above there isn't an
>> ip address on 192.168.x.x. Any ideas why?
> In your script I don't see the WLAN passphrase, so unless you have an
> open network, the router might see the device connecting, but without
> the authentication it doesn't hand out an IP address. And for connecting
> to a WPA/WPA2 network you would also need wpasupplicant.
> Usually the wireless network is configured with the network manager. If
> you really want to do it manually, you should better use the file
> "/etc/network/interfaces" to do that. But using network manager is much
I have found a potentially useful message in dmesg (I don't know why I
didn't look there first) like this:
[ 4293.353404] wlan0: authenticate with 00:1c:f0:f0:c3:18
[ 4293.398731] wlan0: send auth to 00:1c:f0:f0:c3:18 (try 1/3)
[ 4293.401167] wlan0: authenticated
[ 4293.403511] mt7601u 1-1.4:1.0 wlan0: disabling HT as WMM/QoS is not
supported by the AP
[ 4293.403553] mt7601u 1-1.4:1.0 wlan0: disabling VHT as WMM/QoS is
not supported by the AP
[ 4293.413239] wlan0: associate with 00:1c:f0:f0:c3:18 (try 1/3)
[ 4293.416990] wlan0: RX AssocResp from 00:1c:f0:f0:c3:18 (capab=0x421
[ 4293.457810] wlan0: associated
[ 4293.460431] wlan0: disassociating from 00:1c:f0:f0:c3:18 by local
choice (Reason: 3=DEAUTH_LEAVING)
and I found a handy table here:
that tells me the access point went offline. I think that isn't the
case because I'm continuously attached to the same AP as I write this,
on my laptop.
Now, to answer your questions Nils.
I have tested this dongle first on u14.04 with the stock kernel, all
updates in place; that was the source of the vendor ID codes I first
sent and that you tracked down. I wanted at first to make the unit
work on my U14.04 laptop as being easier to manage, having internet
access available and a keyboard and screen and so on. But the intended
end-use was not like that, rather I want to strap a Raspberry Pi under
a hexacopter with the dongle attached and then stream images from the
rover back to another computer. So I switched to using the Pi from my
laptop by ssh, hence the command line stuff. You are right that there
is no password, that simplifies the setup so I can have fewer
breakpoints and will reflect the end use quite nicely, there are very
few security issues far off-road at 55N 129W.
The kernel in use is: Linux raspberrypi 4.1.15+ #830 Tue Dec 15
16:58:28 GMT 2015 armv6l GNU/Linux
I found the mt7601u.bin file on github and that's what's in use.
The dmesg output says that the dongle connects then immediately
disconnects with the message above. The router is an old D-link
WBR-2310 which works ok but has crappy diagnostics and minimal logs
and isn't likely to work with openwrt.
The distance from the dongle to the AP is perhaps 20 cm, so it isn't
likely that signal strength is an issue. The script will in any case
need to be rewritten for each different router, I suppose I'll have a
collection of them by the time I'm finished.
I hope this clarifies matters, thanks for any help.
> ubuntu-users mailing list
> ubuntu-users at lists.ubuntu.com
> Modify settings or unsubscribe at:
"As long as politics is the shadow cast on society by big business,
the attenuation of the shadow will not change the substance."
-- John Dewey
More information about the ubuntu-users