Eduroam Wifi Issues

[User 15552]

Hey everybody, 

I have the pinebook pro with the standard os that ships with it. 

I have a strange problem. when I am at home, I can stay connected to wifi without really noticing any issues. 

At work, I connect to Eduroam (https://en.wikipedia.org/wiki/Eduroam) and it works just fine for a few minutes. But then it starts to drop the connection -- sometimes it shows up as connected but  is actually not. I can then reconnect but keep having trouble until I reboot the machine. 


I went through the suggestions on the pinebook pro wiki (https://wiki.pine64.org/index.php/Pinebo...iFi_issues) but nothing worked so far. 

Has anyone else experience this problem? 
Does anyone connect to Eduroam without any problem ?

Edit:
Have been at a different institute today and had no issues with Eduroam at all. So it seems to be a local issue.

Update:
Switched to Manjaro: Wifi issues with eduroam are still there. However, it seems to work fine when using a wifi-dongle.

[rillian]

Is there anything in the kernel log about the failure? e.g. run `sudo journalctl -f` in a terminal window and look for red or yellow messages about brcmf when the connection goes bad.

I can't join my school's WPA2 network because of a driver crash after authentication, but your problem sounds different. I'll try connecting to eduroam next time I'm on campus and see if it behaves the same way.

[User 15552]

Is there anything in the kernel log about the failure? e.g. run `sudo journalctl -f` in a terminal window and look for red or yellow messages about brcmf when the connection goes bad.

I can't join my school's WPA2 network because of a driver crash after authentication, but your problem sounds different. I'll try connecting to eduroam next time I'm on campus and see if it behaves the same way.

Thanks for the suggestion. I did run `sudo journalctl -f` and  this is what it told me at the time the wifi dropped. 

Code:

Feb 14 11:11:21 Debian-Desktop kernel: dhd_bus_devreset:  WLAN OFF DONE
Feb 14 11:11:21 Debian-Desktop kernel: wifi_platform_set_power = 0
Feb 14 11:11:21 Debian-Desktop kernel: ======== PULL WL_REG_ON(-1) LOW! ========
Feb 14 11:11:21 Debian-Desktop kernel: [WLAN_RFKILL]: rockchip_wifi_power: 0
Feb 14 11:11:21 Debian-Desktop kernel: [WLAN_RFKILL]: wifi shut off power.
Feb 14 11:11:21 Debian-Desktop kernel: wl_android_wifi_off out
Feb 14 11:11:21 Debian-Desktop kernel: wl_ext_iapsta_dettach_netdev: ifidx=0
Feb 14 11:11:21 Debian-Desktop kernel: dhd_stop: Exit
Feb 14 11:11:21 Debian-Desktop kernel: CFG80211-ERROR) wl_cfg80211_hang : In : chip crash eventing, reason=0x8001
Feb 14 11:11:21 Debian-Desktop dhcpcd[481]: wlan0: carrier lost
Feb 14 11:11:21 Debian-Desktop dhclient[3808]: receive_packet failed on wlan0: Network is down
Feb 14 11:11:21 Debian-Desktop wpa_supplicant[508]: wlan0: CTRL-EVENT-DISCONNECTED bssid=f0:5c:19:04:fe:62 reason=3 locally_generated=1
Feb 14 11:11:21 Debian-Desktop avahi-daemon[367]: Interface wlan0.IPv6 no longer relevant for mDNS.
Feb 14 11:11:21 Debian-Desktop NetworkManager[414]: <info>  [1581675081.7918] device (wlan0): supplicant interface state: completed -> disabled
Feb 14 11:11:21 Debian-Desktop avahi-daemon[367]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::c284:7dff:fe2e:be4e.
Feb 14 11:11:21 Debian-Desktop avahi-daemon[367]: Interface wlan0.IPv4 no longer relevant for mDNS.
Feb 14 11:11:21 Debian-Desktop avahi-daemon[367]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 194.171.31.227.
Feb 14 11:11:21 Debian-Desktop avahi-daemon[367]: Withdrawing address record for fe80::c284:7dff:fe2e:be4e on wlan0.
Feb 14 11:11:21 Debian-Desktop avahi-daemon[367]: Withdrawing address record for 194.171.31.228 on wlan0.
Feb 14 11:11:21 Debian-Desktop avahi-daemon[367]: Withdrawing address record for 194.171.31.227 on wlan0.
Feb 14 11:11:21 Debian-Desktop org.mate.panel.applet.MateMenuAppletFactory[730]: Fontconfig error: Cannot load default config file
Feb 14 11:11:23 Debian-Desktop ntpd[3923]: Deleting interface #3 wlan0, 194.171.31.227#123, interface stats: received=41, sent=41, dropped=0, active_time=3142 secs
Feb 14 11:11:23 Debian-Desktop ntpd[3923]: 192.16.191.36 local addr 194.171.31.227 -> <null>
Feb 14 11:11:23 Debian-Desktop ntpd[3923]: Deleting interface #6 wlan0, fe80::c284:7dff:fe2e:be4e%2#123, interface stats: received=0, sent=0, dropped=0, active_time=3140 secs
Feb 14 11:11:23 Debian-Desktop ntpd[3923]: Deleting interface #7 wlan0, 194.171.31.228#123, interface stats: received=0, sent=0, dropped=0, active_time=3136 secs

Also the following error: `Error getting the SSID`

Also just saw another error message that keeps coming up and I am not sure if it is related. 

Code:

Feb 16 12:26:21 Debian-Desktop kernel: bcmsdh_sdmmc: Failed to Write byte F1:@0x1001f=01, Err: -5

[rillian]

Ok, looks like a different issue from the one I had. I'll try to check a local eduroam ap tomorrow.

[erchache2000]

Hey everybody, 

I have the pinebook pro with the standard os that ships with it. 

I have a strange problem. when I am at home, I can stay connected to wifi without really noticing any issues. 

At work, I connect to Eduroam (https://en.wikipedia.org/wiki/Eduroam) and it works just fine for a few minutes. But then it starts to drop the connection -- sometimes it shows up as connected but  is actually not. I can then reconnect but keep having trouble until I reboot the machine. 


I went through the suggestions on the pinebook pro wiki (https://wiki.pine64.org/index.php/Pinebo...iFi_issues) but nothing worked so far. 

Has anyone else experience this problem? 
Does anyone connect to Eduroam without any problem ?

Edit:
Have been at a different institute today and had no issues with Eduroam at all. So it seems to be a local issue.

I think is a problem of your eduroam spot, talk with your network staff.

I'm running my pinebook pro over eduroam right now without any problem.

With my pinebook non 1080p runs too.

[rillian]

I tried my local eduroam yesterday and saw the same  crash in brcmf_cfg80211_set_pmk I get with their normal WPA2 essid. So it looks like a different issue.

It's definitely an issue with the pinebook pro driver, since my x86_64 laptop and android phone have no trouble, but it probably depends on the details of the access point or authentication server implementation.