some problems with run0 freebsd11/rpi2
Kevin Lo
kevlo at FreeBSD.org
Thu Sep 17 15:25:57 UTC 2015
On Wed, Sep 16, 2015 at 05:25:47PM +0100, John wrote:
>
> Hello list,
Hi John,
> I'm having a devil of a job getting a usb wifi dongle to work properly. I'm
> using CURRENT r286947. The dongle is identified as:
>
> run0: MAC/BBP RT5390 (rev 0x0502), RF RT5370 (MIMO 1T1R), address 00:87:RE:DA:CT:ED
>
> The man page for run says a firmware needed to be loaded, so it was:
>
> Sep 16 03:34:18 potato kernel: run0: firmware RT3071 ver. 0.33 loaded
>
> also found I had to load ccmp because at the moment, contrary to the wlan man
> page, it doesn't auto-load:
>
> Sep 16 03:23:50 potato kernel: ieee80211_load_module: load the wlan_ccmp module by hand for now.
>
> kldstat looks line this:
>
> $ kldstat
> Id Refs Address Size Name
> 1 35 0xc0100000 784e20 kernel
> 2 1 0xc4417000 b000 fdescfs.ko
> 3 1 0xc4586000 b000 ums.ko
> 4 1 0xc4498000 b000 uhid.ko
> 5 1 0xc45bf000 20000 if_run.ko
> 6 3 0xc45e0000 51000 wlan.ko
> 7 2 0xc463b000 b000 firmware.ko
> 8 1 0xc4663000 a000 pflog.ko
> 9 1 0xc468c000 40000 pf.ko
> 10 1 0xc44cf000 b000 runfw.ko
> 11 1 0xc5df7000 12000 uhci.ko
> 12 1 0xc5e09000 12000 ohci.ko
> 13 1 0xc4efe000 a000 wlan_amrr.ko
> 14 1 0xc6603000 e000 wlan_ccmp.ko
>
> What the actual problem is, is the interface comes up, is available for 10
> seconds to a minute, goes down, comes up, ad nauseam. Is it me, the wifi usb,
> usb itself, or the kernel/driver?
Does it work on your PC or laptop?
> Sep 16 06:47:19 potato wpa_supplicant[38412]: wlan0: Associated with 10:0d:RE:DA:CT:ED
> Sep 16 06:47:22 potato wpa_supplicant[38412]: wlan0: WPA: Key negotiation completed with 10:0d:RE:DA:CT:ED [PTK=CCMP GTK=CCMP]
> Sep 16 06:47:22 potato wpa_supplicant[38412]: wlan0: CTRL-EVENT-CONNECTED - Connection to 10:0d:RE:DA:CT:ED completed [id=0 id_str=]
> Sep 16 06:47:39 potato wpa_supplicant[38412]: wlan0: CTRL-EVENT-DISCONNECTED bssid=10:0d:RE:DA:CT:ED reason=0
> Sep 16 06:47:39 potato kernel: wlan0: link state changed to DOWN
> Sep 16 06:47:41 potato wpa_supplicant[38412]: wlan0: Trying to associate with 10:0d:RE:DA:CT:ED (SSID='REDACTED' freq=2412 MHz)
> Sep 16 06:47:51 potato wpa_supplicant[38412]: wlan0: Authentication with 10:0d:RE:DA:CT:ED timed out.
> Sep 16 06:47:51 potato wpa_supplicant[38412]: wlan0: CTRL-EVENT-DISCONNECTED bssid=10:0d:RE:DA:CT:ED reason=3 locally_generated=1
> Sep 16 06:48:09 potato wpa_supplicant[38412]: wlan0: Trying to associate with 10:0d:RE:DA:CT:ED (SSID='REDACTED' freq=2412 MHz)
> Sep 16 06:48:09 potato kernel: wlan0: link state changed to UP
> Sep 16 06:48:09 potato wpa_supplicant[38412]: wlan0: Associated with 10:0d:RE:DA:CT:ED
> Sep 16 06:48:11 potato wpa_supplicant[38412]: wlan0: WPA: Key negotiation completed with 10:0d:RE:DA:CT:ED [PTK=CCMP GTK=CCMP]
> Sep 16 06:48:11 potato wpa_supplicant[38412]: wlan0: CTRL-EVENT-CONNECTED - Connection to 10:0d:RE:DA:CT:ED completed [id=0 id_str=]
> Sep 16 06:48:29 potato kernel: wlan0: link state changed to DOWN
> Sep 16 06:48:29 potato wpa_supplicant[38412]: wlan0: CTRL-EVENT-DISCONNECTED bssid=10:0d:RE:DA:CT:ED reason=0
> Sep 16 06:48:31 potato wpa_supplicant[38412]: wlan0: Trying to associate with 10:0d:RE:DA:CT:ED (SSID='REDACTED' freq=2412 MHz)
> Sep 16 06:48:31 potato kernel: wlan0: link state changed to UP
> Sep 16 06:48:31 potato wpa_supplicant[38412]: wlan0: Associated with 10:0d:RE:DA:CT:ED
> Sep 16 06:48:32 potato wpa_supplicant[38412]: wlan0: WPA: Key negotiation completed with 10:0d:RE:DA:CT:ED [PTK=CCMP GTK=CCMP]
> Sep 16 06:48:32 potato wpa_supplicant[38412]: wlan0: CTRL-EVENT-CONNECTED - Connection to 10:0d:RE:DA:CT:ED completed [id=0 id_str=]
> Sep 16 06:49:13 potato wpa_supplicant[38412]: wlan0: CTRL-EVENT-DISCONNECTED bssid=10:0d:RE:DA:CT:ED reason=0
> Sep 16 06:49:13 potato kernel: wlan0: link state changed to DOWN
>
> ping: sendto: Network is down
> ping: sendto: Network is down
> ping: sendto: Network is down
> ping: sendto: No buffer space available
> ping: sendto: No buffer space available
> 64 bytes from 192.168.1.1: icmp_seq=250 ttl=64 time=9.297 ms
> 64 bytes from 192.168.1.1: icmp_seq=254 ttl=64 time=13.435 ms
> 64 bytes from 192.168.1.1: icmp_seq=256 ttl=64 time=5.430 ms
> 64 bytes from 192.168.1.1: icmp_seq=257 ttl=64 time=3.670 ms
> 64 bytes from 192.168.1.1: icmp_seq=259 ttl=64 time=6.287 ms
> ping: sendto: Network is down
> ping: sendto: Network is down
> ping: sendto: Network is down
> ping: sendto: No buffer space available
> 64 bytes from 192.168.1.1: icmp_seq=264 ttl=64 time=19.030 ms
> 64 bytes from 192.168.1.1: icmp_seq=265 ttl=64 time=4.295 ms
> 64 bytes from 192.168.1.1: icmp_seq=266 ttl=64 time=3.199 ms
> 64 bytes from 192.168.1.1: icmp_seq=267 ttl=64 time=2.705 ms
> 64 bytes from 192.168.1.1: icmp_seq=268 ttl=64 time=3.570 ms
> 64 bytes from 192.168.1.1: icmp_seq=269 ttl=64 time=4.039 ms
> 64 bytes from 192.168.1.1: icmp_seq=271 ttl=64 time=30.060 ms
> 64 bytes from 192.168.1.1: icmp_seq=273 ttl=64 time=3.649 ms
> 64 bytes from 192.168.1.1: icmp_seq=274 ttl=64 time=4.681 ms
> 64 bytes from 192.168.1.1: icmp_seq=278 ttl=64 time=28.680 ms
> 64 bytes from 192.168.1.1: icmp_seq=279 ttl=64 time=25.553 ms
> 64 bytes from 192.168.1.1: icmp_seq=280 ttl=64 time=21.684 ms
> 64 bytes from 192.168.1.1: icmp_seq=282 ttl=64 time=23.208 ms
> 64 bytes from 192.168.1.1: icmp_seq=284 ttl=64 time=11.321 ms
> ping: sendto: Network is down
> ping: sendto: Network is down
> ping: sendto: No buffer space available
> ping: sendto: No buffer space available
> 64 bytes from 192.168.1.1: icmp_seq=291 ttl=64 time=10.184 ms
> 64 bytes from 192.168.1.1: icmp_seq=298 ttl=64 time=5.662 ms
> 64 bytes from 192.168.1.1: icmp_seq=299 ttl=64 time=4.545 ms
> 64 bytes from 192.168.1.1: icmp_seq=300 ttl=64 time=4.888 ms
> 64 bytes from 192.168.1.1: icmp_seq=301 ttl=64 time=6.296 ms
> 64 bytes from 192.168.1.1: icmp_seq=304 ttl=64 time=14.067 ms
> 64 bytes from 192.168.1.1: icmp_seq=306 ttl=64 time=24.352 ms
>
> 192.168.1.1 is my wireless router. Might be worthwhile to note that the
> device, though recognised in dmesg, would not associate at all while connected
> to the (powered) usb extended hub but would while directly connected
> to a usb port mounted on the pi PCB itself.
>
> thanks,
> --
> John
Kevin
More information about the freebsd-arm
mailing list