@hart, i use connman, some users don’t like that. I was never able to get the Schematic’s from WandBoard on the Rev D’s, so I don’t know if WiFi works on those models…
Regards,
OK. Mine is rev B1.
I looked over at the screen from being away, and the screen was black with the cursor blinking in the upper left corner. No response to mouse or keyboard. Ideas on what happened? Understand, I might be on my own at this point since system is built.
@hart, it might be an RT thing with the v5.0.x-rt kernel you are using… I’ve been using 5.4.x all day in testing. While my WandBoards in my build farm are still on v4.19.x… I had updated the wiki documentation this morning with 5.4.x/5.6.x options.
Regards,
I had changed my mind and rebuilt with 4.19 RT. I turned off the auto lock and see if that helps. If not, I’ll try another kernel build. Thanks again for all your help. (and patience for the HW guy).
-best regards
@hart, i just switched to the v4.19.x-rt to debug, caught this gem:
armada(0): etnaviv_dri2_ScheduleSwap: common_drm_queue_msc_event failed: Invalid argument
v5.4.x-rt just did the same thing, testing non-rt…
v5.4.x also just did it…
let’s try updating mesa…
Got it… It’s Power Management issues…
debian@arm:~$ cat .xsessionrc
#!/bin/sh
xset -dpms
xset s off
xsetroot -cursor_name left_ptr
Then nuke:
sudo apt remove xfce4-power-manager --purge
Edit:
I think that solved it. 
debian@arm:~$ uname -r ; uptime -p
5.4.39-armv7-x26
up 11 hours, 23 minutes
Still running glxgears, no gui crashes…
Regards,
@RobertCNelson xfce4 power manager wasn’t installed when I tried to remove it. Looks like problem is solved if screen locker isn’t loaded. The system seems to work even with screen saver turning off to save power. With the screen lock enabled, it seemed to fail. I got the same symptom when I manually locked it with the keyboard sequence. Told xcfe not to load screen locker on startup. I’ll use xset as described if I have further problems.
As for the WiFi, having troubles. I installed wicd to manage it. It shows signal strength, channel, etc. It will actually connect for about 10 seconds. I can ping the router and with other computers can ping the ARM board.
Ethernet is unplugged trying to connect to wifi. I get these messages on the console:
[ 3360.241242] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 3360.575842] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 3360.581810] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -52
[ 3360.594487] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -52
[ 3360.632220] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -52
[ 3361.184871] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 3361.194471] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -52
[ 3361.617634] Atheros 8031 ethernet 2188000.ethernet-1:01: attached PHY driver [Atheros 8031 ethernet] (mii_bus:phy_addr=2188000.ethernet-1:01, irq=POLL)
[ 3361.631444] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 3364.197789] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 3364.713479] fec 2188000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[ 3364.721175] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 3372.853701] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -52
Ethernet plugged in and trying to connect wifi get these messages
[ 4712.245579] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -52
[ 4712.302315] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -52
[ 4712.342620] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -52
[ 4712.911832] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 4712.918567] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -52
[ 4712.936650] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -52
[ 4713.088708] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -52
[ 4713.867987] Atheros 8031 ethernet 2188000.ethernet-1:01: attached PHY driver [Atheros 8031 ethernet] (mii_bus:phy_addr=2188000.ethernet-1:01, irq=POLL)
[ 4399.908351] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 4402.139869] fec 2188000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[ 4402.147577] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 4402.683578] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 4402.689560] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -52
[ 4402.702664] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -52
[ 4402.836013] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -52
[ 4405.063380] brcmfmac: brcmf_cfg80211_scan: Connecting: status (3)
[ 4405.239377] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 4405.253013] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -52
[ 4405.265710] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -52
[ 4406.229843] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -52
[ 4406.303384] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -52
[ 4407.931089] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -52
debian@arm:~$ dmesg | grep brcm
[ 3360.632220] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -52
[ 3361.194471] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -52
[ 3372.853701] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -52
(over and over again)
debian@arm:~$ /sbin/ifconfig -a
eth0: flags=-28605<UP,BROADCAST,RUNNING,MULTICAST,DYNAMIC> mtu 1500
inet 192.168.1.6 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::21f:7bff:feb4:668 prefixlen 64 scopeid 0x20
ether 00:1f:7b:b4:06:68 txqueuelen 1000 (Ethernet)
RX packets 7579 bytes 1436606 (1.3 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3573 bytes 328226 (320.5 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Local Loopback)
RX packets 84 bytes 7004 (6.8 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 84 bytes 7004 (6.8 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=-28605<UP,BROADCAST,RUNNING,MULTICAST,DYNAMIC> mtu 1500
inet 192.168.1.11 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::422c:f4ff:feae:2bea prefixlen 64 scopeid 0x20
ether 40:2c:f4:ae:2b:ea txqueuelen 1000 (Ethernet)
RX packets 1556 bytes 356208 (347.8 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 747 bytes 120541 (117.7 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Any thoughts?
best regards,
@RobertCNelson, been up 18+ hours also, so looks like problem with power management / screen locker xflock4 as you thought… Anyone any thoughts on WiFi issue?
@hart, for WiFi, I’m unable to test today. I’ve looked thru my collection of spare WandBoards (at home) and all i have is a Rev A and Rev C. Your Rev B used a different WiFi module then Rev C or D… (Rev A’s WiFi wasn’t populated)… I believe i have a few Rev B’s at my cube at work. I’m scheduled to go in tomorrow and help out in shipping, so i’ll grab a Rev B so I can test over the weekend…
Regards,
@RobertCNelson Realized connman was installed and I think was conflicting with wicd. There was a wpa_supplicant running and then wicd started another one. Not sure if these were colliding or what. Removed wicd, configured with connman and wifi working now. Will run pings overnight and report back if any issues [still working great in morning, only brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed,-52 errors are when link starts up, nothing continuous like before]. Thanks for all the help!