no wlan device with volumio-2.029-2016-11-18-cuboxi.img

Help and Support Help
1

I just switched from Volumio1.5Cuboxi.img to volumio-2.029-2016-11-18-cuboxi.img .
Wlan worked within 1.5.

With Volumio2 eth0 works , but there no wlan interface .

But wireless.services are not started:

[code]root@volumio:~# systemctl status -l wireless.service
● wireless.service - Wireless Services
Loaded: loaded (/lib/systemd/system/wireless.service; enabled)
Active: failed (Result: exit-code) since Fri 2016-11-18 13:00:21 UTC; 1 weeks 1 days ago
Process: 733 ExecStart=/volumio/app/plugins/system_controller/network/wireless.js start (code=exited, status=1/FAILURE)

Nov 18 13:00:21 volumio wireless.js[733]: at /volumio/app/plugins/system_controller/network/wireless.js:175:16
Nov 18 13:00:21 volumio wireless.js[733]: at /volumio/node_modules/wireless-tools/iwconfig.js:129:16
Nov 18 13:00:21 volumio wireless.js[733]: at ChildProcess.exithandler (child_process.js:213:5)
Nov 18 13:00:21 volumio wireless.js[733]: at emitTwo (events.js:106:13)
Nov 18 13:00:21 volumio wireless.js[733]: at ChildProcess.emit (events.js:191:7)
Nov 18 13:00:21 volumio wireless.js[733]: at maybeClose (internal/child_process.js:877:16)
Nov 18 13:00:21 volumio wireless.js[733]: at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
Nov 18 13:00:21 volumio systemd[1]: wireless.service: control process exited, code=exited status=1
Nov 18 13:00:21 volumio systemd[1]: Failed to start Wireless Services.
[/code]

root@volumio:~# uname -a
Linux volumio 4.7.2 #13 SMP Mon Sep 26 10:50:12 CEST 2016 armv7l GNU/Linux
root@volumio:~# lsmod
Module                  Size  Used by
nfsd                  281319  2 
nfs_acl                 2925  1 nfsd
xt_REDIRECT             1286  1 
nf_nat_redirect         3057  1 xt_REDIRECT
iptable_nat             1766  1 
nf_conntrack_ipv4      15524  1 
nf_defrag_ipv4          1620  1 nf_conntrack_ipv4
nf_nat_ipv4             5476  1 iptable_nat
nf_nat                 17646  2 nf_nat_redirect,nf_nat_ipv4
nf_conntrack          144992  3 nf_nat,nf_nat_ipv4,nf_conntrack_ipv4
ip_tables              12862  1 iptable_nat
brcmfmac              187380  0 
brcmutil                8562  1 brcmfmac
dw_hdmi_ahb_audio       4082  0 
evbug                   2004  0 
squashfs               31268  1 
overlay                30534  1

As firmware is installed

root@volumio:~# aptitude search "firmware-brcm*"
i   firmware-brcm80211

with these files:

root@volumio:~# ls -1 /lib/firmware/brcm/ bcm43xx-0.fw bcm43xx_hdr-0.fw brcmfmac43143-sdio.bin brcmfmac43241b0-sdio.bin brcmfmac43241b4-sdio.bin brcmfmac4329-sdio.bin brcmfmac4330-sdio.bin brcmfmac4334-sdio.bin brcmfmac4335-sdio.bin brcmfmac43362-sdio.bin brcmfmac4354-sdio.bin 

root@volumio:~# ifconfig
eth0      Link encap:Ethernet  HWaddr d0:63:b4:00:c4:0f  
          inet addr:192.168.1.100  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:23195 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10378 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:29406606 (28.0 MiB)  TX bytes:1721142 (1.6 MiB)

ip6tnl0   Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
          UP RUNNING NOARP  MTU:1452  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:1 dropped:1 overruns:0 carrier:0
          collisions:0 txqueuelen:1 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:6032 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6032 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1 
          RX bytes:549502 (536.6 KiB)  TX bytes:549502 (536.6 KiB)

sit0      Link encap:IPv6-in-IPv4  
          UP RUNNING NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:1 dropped:0 overruns:1 carrier:0
          collisions:0 txqueuelen:1 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

From dmesg

    8.847598] evbug: Connected device: input1 (MCE IR Keyboard/Mouse (gpio-rc-recv) at /input0)
[    8.847614] evbug: Connected device: input2 (Dell Dell QuietKey Keyboard at usb-ci_hdrc.0-1/input0)
[    8.847659] evbug: Connected device: input3 (gpio-keys at gpio-keys/input0)
[    9.592274] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac4330-sdio.txt failed with error -2
[   10.569356] systemd-journald[262]: Received request to flush runtime journal from PID 1
[   10.757930] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
[   10.853365] ip_tables: (C) 2000-2006 Netfilter Core Team
[   10.893096] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[   11.777571] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
[   12.028951] Atheros 8035 ethernet 2188000.ethernet:00: attached PHY driver [Atheros 8035 ethernet] (mii_bus:phy_addr=2188000.ethernet:00, irq=-1)
[   16.059746] fec 2188000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[   24.189769] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).

Any idea what could be wrong and how I can fix it ?
Any hints are apreciated .

2

Hi,
This is a known problem we’re still trying to fix. There is a cubox on it’s way from SolidRun but obviously takes ages to get here.
-Gé-

3

Ok, thanks for the quick info.
So, first of all I downgrade to 1.5 again.

4

Yes, we’ll post progress as soon as we have some.
Thanks for the info though, I noticed the nvram file brcmfmac4330-sdio.txt seems missing from /lib/firmware/brcm.
I will check that, if really missing, then it must be the root cause.

-Gé-

5

@Wanda,
could you pls. unpack the attachment and copy brcmfmac4330-sdio.txt to /lib/firmware/brcm and retry?
I haven’t got a cubox here otherwise I would have tested it.
Cheers
-Gé-
brcmfmac4330-sdio.txt.gz (445 Bytes)

6

With this file I can see wireless networks, but cannot connect to them.

7

Thank you for taking the time to try this out, very much appreciated!
You now verified the driver works and wlan0 devices are available.
Next we need to create a new image and use it for solving the next issue.
-Gé-

8

I will do it now!

9

Here you have it!
updates.volumio.org/cuboxi/volum … xi.img.zip

10

It’s not working more with volumio-2.032-2016-11-27-cuboxi.img

Also, in the screenshot below, you can see that the UI shows wireless networks even if the wireless service networking is supposedly off. Putting it at on and saving will throw an error, also shown in the screenshot. I get the same error when I try to connect to my wireless network: Les3p’titscochons2.4

Capture du 2016-11-28 22-17-00.png

11

I have the same issue with volumio-2.029-2016-11-18-cuboxi.img
Could I kindly ask to fix it?

12

You probably make lots of friends with asking for things the “nice” way you do.
Lucky you to have at least managed “please” in that long first post :wink:

Trust me, we would really like to fix this, but can’t as SolidRun is still to deliver their promised unit.
Apparently they’ve been out-of-stock for nearly 2 months now.
Until I have one here, nothing much is going to happen I’m afraid.
-Gé-

13

Thanks for reply,
Could I test something on mine?

14

Depends on your skills, any experience with networking using dhclient vs. dhcpcd?
Some WiFi devices & driver combos seem to work well with dhcpcd as the dhcp client (this is what volumio implements), other don’t at all.
Cubox might belong the “others”, as does pine64. The latter I can get connected with using the isc dhclient instead of dchpcd.

15

I tried SSH dhcpcd - look like it do not work for this case

volumio@volumio:~$ sudo dhcpcd wlan0
dhcpcd[1227]: control_open: Connection refused
dhcpcd[1227]: version 6.0.5 starting
dhcpcd[1227]: wlan0: waiting for carrier
dhcpcd[1227]: timed out
dhcpcd[1227]: allowing 8 seconds for IPv4LL timeout
dhcpcd[1227]: timed out
dhcpcd[1227]: exited
volumio@volumio:~$ sudo dhclient wlan0
sudo: dhclient: command not found

Manual set wlan0 addresses also did not help, just hangs cubox

ifconfig wlan0 192.168.31.10 ...