[Closed] Volumio 2 Beta versions for Odroid

gkkpch · December 3, 2016, 9:39am

volumio itself does not have a UI, you need to use a browser, pointing to the XU4, this you can do from any device.

There is a plugin to turn the device into kioskmode, this has been prepared for the C1 and C2 but I’m not sure about the XU4. As far as I remember I did not enable the framebuffer as this was done before the plugin existed. I need to have a look at this.

EddieA · December 3, 2016, 6:10pm

I understand that there is no UI/console and I can connect successfully from a browser and also via ssh.

I just wondered that as there appears to be no signal at all from the HDMI, that that was the reason that no sound card/device was discovered.

This is what I get on the Playback Options screen:

Cheers.

gkkpch · December 3, 2016, 7:50pm

oops never tested that…
Ok, the kernel I used obviously had no support for hdmi (which didn’t bother me as I started off headless).
I would need to see if it supported now and then recompile the kernel. with hdmi audio.
Not likely going to happen soon, as this means a lot of work with only one potential user and plenty of other things to do…
Yes, bugger, I know but hope you understand.
In the meantime, get a good USB DAC and you’ll be OK.

EddieA · December 3, 2016, 9:58pm

Yeah, I understand.

I just realised that I had one of these sitting at the bottom of a drawer from when I was in road-warrior mode. Seems to work perfectly, so at least I can now evaluate Volumio.

Cheers.

EddieA · December 5, 2016, 9:09pm

OK, next issue. Trying to connect to my wireless network with an EdiMax USB dongle.

Navigating to the Network screen an enabling the Wireless Network, I see all the AP’s around me. Great, that shows the dongle has been recognised and is (I hope) supported. Pick my AP and enter it’s password, hit Connect and see a flash of red in the top right corner. Hmm, not good.

To start with, the red error message doesn’t really stay on the screen long enough to read it, to see what really is happening. So, after hitting “Print screen” while the message was there, here is the output is asked me to collect:

volumio@volumio:~$ journalctl -xn No journal files were found. volumio@volumio:~$

[code]volumio@volumio:~$ systemctl status -l wireless.service
● wireless.service - Wireless Services
Loaded: loaded (/lib/systemd/system/wireless.service; enabled)
Active: failed (Result: exit-code) since Mon 2016-12-05 20:56:25 UTC; 1min 42s ago
Process: 4014 ExecStart=/volumio/app/plugins/system_controller/network/wireless.js start (code=exited, status=1/FAILURE)

Dec 05 20:56:25 volumio wireless.js[4014]: at emitTwo (events.js:106:13)
Dec 05 20:56:25 volumio wireless.js[4014]: at ChildProcess.emit (events.js:191:7)
Dec 05 20:56:25 volumio wireless.js[4014]: at maybeClose (internal/child_process.js:877:16)
Dec 05 20:56:25 volumio wireless.js[4014]: at Socket. (internal/child_process.js:334:11)
Dec 05 20:56:25 volumio wireless.js[4014]: at emitOne (events.js:96:13)
Dec 05 20:56:25 volumio wireless.js[4014]: at Socket.emit (events.js:188:7)
Dec 05 20:56:25 volumio wireless.js[4014]: at Pipe._handle.close [as _onclose] (net.js:498:12)
Dec 05 20:56:25 volumio systemd[1]: wireless.service: control process exited, code=exited status=1
Dec 05 20:56:25 volumio systemd[1]: Failed to start Wireless Services.
Dec 05 20:56:25 volumio systemd[1]: Unit wireless.service entered failed state.
volumio@volumio:~$[/code]
What other information is needed at this point. Or should I now be reporting this under the “normal” support forum.

Cheers.

volumio · December 6, 2016, 6:01am

Unfortunately we can’t tell where it fails like this…
Could you try
sudo journalctl -f ?
Did you do manual changes to the system?

EddieA · December 6, 2016, 8:47am

No manual changes at all.

Here’s the output from when I hit “Connect”:

Dec 06 08:40:07 volumio volumio[3526]: info: CoreCommandRouter::executeOnPlugin: network , saveWirelessNetworkSettings Dec 06 08:40:07 volumio volumio[3526]: info: Saving new wireless network Dec 06 08:40:08 volumio sudo[4059]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl restart wireless.service Dec 06 08:40:08 volumio sudo[4059]: pam_unix(sudo:session): session opened for user root by (uid=0) Dec 06 08:40:08 volumio systemd[1]: Starting Wireless Services... Dec 06 08:40:08 volumio wireless.js[4061]: start Dec 06 08:40:08 volumio wireless.js[4061]: Cleaning previous... Dec 06 08:40:08 volumio systemd[1]: Stopped hotspot.service. Dec 06 08:40:08 volumio wireless.js[4061]: stophotspotchild process exited with code 0 Dec 06 08:40:08 volumio sudo[4070]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ip addr flush dev wlan0 Dec 06 08:40:08 volumio sudo[4070]: pam_unix(sudo:session): session opened for user root by (uid=0) Dec 06 08:40:08 volumio sudo[4070]: pam_unix(sudo:session): session closed for user root Dec 06 08:40:08 volumio sudo[4072]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig wlan0 down Dec 06 08:40:08 volumio sudo[4072]: pam_unix(sudo:session): session opened for user root by (uid=0) Dec 06 08:40:08 volumio netplugd[3511]: wlan0: state INACTIVE flags 0x00001003 UP,BROADCAST,MULTICAST -> 0x00001002 BROADCAST,MULTICAST Dec 06 08:40:08 volumio sudo[4072]: pam_unix(sudo:session): session closed for user root Dec 06 08:40:08 volumio netplugd[4074]: /etc/netplug/netplug wlan0 probe -> pid 4074 Dec 06 08:40:08 volumio wireless.js[4061]: killing: kill `pgrep -f "^/usr/bin/sudo"` || true Dec 06 08:40:08 volumio netplugd[3511]: wlan0: state PROBING pid 4074 exited status 0 Dec 06 08:40:08 volumio wireless.js[4061]: ifdeconfigchild process exited with code 0 Dec 06 08:40:08 volumio wireless.js[4061]: killing: kill `pgrep -f "^wpa_supplicant"` || true Dec 06 08:40:08 volumio wireless.js[4061]: Stopped aP Dec 06 08:40:08 volumio wireless.js[4061]: Start wireless flow Dec 06 08:40:08 volumio wireless.js[4061]: Stopped hotspot (if there).. Dec 06 08:40:08 volumio sudo[4080]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ip addr flush dev wlan0 Dec 06 08:40:08 volumio sudo[4080]: pam_unix(sudo:session): session opened for user root by (uid=0) Dec 06 08:40:08 volumio sudo[4080]: pam_unix(sudo:session): session closed for user root Dec 06 08:40:09 volumio sudo[4082]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig wlan0 down Dec 06 08:40:09 volumio sudo[4082]: pam_unix(sudo:session): session opened for user root by (uid=0) Dec 06 08:40:09 volumio sudo[4082]: pam_unix(sudo:session): session closed for user root Dec 06 08:40:09 volumio wireless.js[4061]: Conf sudo ip addr flush dev wlan0 && sudo ifconfig wlan0 down Dec 06 08:40:09 volumio wireless.js[4061]: launching wpa_supplicant args: Dec 06 08:40:09 volumio wireless.js[4061]: [ '-d', Dec 06 08:40:09 volumio wireless.js[4061]: '-B', Dec 06 08:40:09 volumio wireless.js[4061]: '-Dwext', Dec 06 08:40:09 volumio wireless.js[4061]: '-c/etc/wpa_supplicant/wpa_supplicant.conf', Dec 06 08:40:09 volumio wireless.js[4061]: '-iwlan0' ] Dec 06 08:40:09 volumio wireless.js[4061]: wpasupp undefined Dec 06 08:40:09 volumio wireless.js[4061]: DHCP IP Dec 06 08:40:09 volumio wireless.js[4061]: launching /usr/bin/sudo args: Dec 06 08:40:09 volumio wireless.js[4061]: [ '/sbin/dhcpcd' ] Dec 06 08:40:09 volumio wireless.js[4061]: Start ap Dec 06 08:40:09 volumio wireless.js[4061]: ifdeconfigchild process exited with code 0 Dec 06 08:40:09 volumio sudo[4085]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/dhcpcd Dec 06 08:40:09 volumio sudo[4085]: pam_unix(sudo:session): session opened for user root by (uid=0) Dec 06 08:40:09 volumio dhcpcd[4086]: version 6.0.5 starting Dec 06 08:40:09 volumio wireless.js[4061]: dhclientstderr: dhcpcd[4086]: version 6.0.5 starting Dec 06 08:40:09 volumio kernel: rtl8192cu: MAC auto ON okay! Dec 06 08:40:09 volumio kernel: rtl8192cu: Tx queue select: 0x05 Dec 06 08:40:09 volumio netplugd[3511]: wlan0: state DOWN flags 0x00001002 BROADCAST,MULTICAST -> 0x00001003 UP,BROADCAST,MULTICAST Dec 06 08:40:09 volumio wireless.js[4061]: wpa supplicantstderr: ioctl[SIOCSIWMODE]: Operation not supported Dec 06 08:40:09 volumio wireless.js[4061]: ioctl[SIOCGIWRANGE]: Operation not supported Dec 06 08:40:09 volumio wireless.js[4061]: wpa supplicantstderr: ioctl[SIOCGIWMODE]: Operation not supported Dec 06 08:40:09 volumio wireless.js[4061]: ioctl[SIOCSIWAP]: Operation not supported Dec 06 08:40:09 volumio wireless.js[4061]: ioctl[SIOCSIWESSID]: Operation not supported Dec 06 08:40:09 volumio wireless.js[4061]: wpa supplicantstderr: ioctl[SIOCSIWENCODEEXT]: Operation not supported Dec 06 08:40:09 volumio wireless.js[4061]: ioctl[SIOCSIWENCODE]: Operation not supported Dec 06 08:40:09 volumio wireless.js[4061]: wpa supplicantstderr: ioctl[SIOCSIWENCODEEXT]: Operation not supported Dec 06 08:40:09 volumio wireless.js[4061]: ioctl[SIOCSIWENCODE]: Operation not supported Dec 06 08:40:09 volumio wireless.js[4061]: ioctl[SIOCSIWENCODEEXT]: Operation not supported Dec 06 08:40:09 volumio wireless.js[4061]: ioctl[SIOCSIWENCODE]: Operation not supported Dec 06 08:40:09 volumio wireless.js[4061]: ioctl[SIOCSIWENCODEEXT]: Operation not supported Dec 06 08:40:09 volumio wireless.js[4061]: ioctl[SIOCSIWENCODE]: Operation not supported Dec 06 08:40:09 volumio wireless.js[4061]: ioctl[SIOCSIWENCODEEXT]: Operation not supported Dec 06 08:40:09 volumio wireless.js[4061]: ioctl[SIOCSIWENCODE]: Operation not supported Dec 06 08:40:09 volumio wireless.js[4061]: ioctl[SIOCSIWENCODEEXT]: Operation not supported Dec 06 08:40:09 volumio wireless.js[4061]: wpa supplicantstderr: ioctl[SIOCSIWENCODE]: Operation not supported Dec 06 08:40:09 volumio wireless.js[4061]: wpa supplicantchild process exited with code 0 Dec 06 08:40:09 volumio dhcpcd[4086]: wlan0: waiting for carrier Dec 06 08:40:09 volumio dhcpcd[4086]: eth0: soliciting an IPv6 router Dec 06 08:40:09 volumio wireless.js[4061]: dhclientstderr: dhcpcd[4086]: wlan0: waiting for carrier Dec 06 08:40:09 volumio wireless.js[4061]: dhcpcd[4086]: eth0: soliciting an IPv6 router Dec 06 08:40:09 volumio dhcpcd[4086]: eth0: rebinding lease of 192.168.0.60 Dec 06 08:40:09 volumio wireless.js[4061]: dhclientstderr: dhcpcd[4086]: eth0: rebinding lease of 192.168.0.60 Dec 06 08:40:09 volumio dhcpcd[4086]: eth0: leased 192.168.0.60 for 86400 seconds Dec 06 08:40:09 volumio dhcpcd[4086]: eth0: adding host route to 192.168.0.60 via 127.0.0.1 Dec 06 08:40:09 volumio dhcpcd[4086]: eth0: adding route to 192.168.0.0/24 Dec 06 08:40:09 volumio dhcpcd[4086]: eth0: adding default route via 192.168.0.254 Dec 06 08:40:09 volumio wireless.js[4061]: dhclientstderr: dhcpcd[4086]: eth0: leased 192.168.0.60 for 86400 seconds Dec 06 08:40:09 volumio wireless.js[4061]: dhclientstderr: dhcpcd[4086]: eth0: adding host route to 192.168.0.60 via 127.0.0.1 Dec 06 08:40:09 volumio wireless.js[4061]: dhcpcd[4086]: eth0: adding route to 192.168.0.0/24 Dec 06 08:40:09 volumio wireless.js[4061]: dhclientstderr: dhcpcd[4086]: eth0: adding default route via 192.168.0.254 Dec 06 08:40:10 volumio dhcpcd[4086]: forked to background, child pid 4147 Dec 06 08:40:10 volumio wireless.js[4061]: dhclientstderr: dhcpcd[4086]: forked to background, child pid 4147 Dec 06 08:40:10 volumio sudo[4085]: pam_unix(sudo:session): session closed for user root Dec 06 08:40:10 volumio wireless.js[4061]: dhclientchild process exited with code 0 Dec 06 08:40:10 volumio dhcpcd[4147]: eth0: removing route to 192.168.0.0/24 Dec 06 08:40:10 volumio dhcpcd[4147]: eth0: removing default route via 192.168.0.254 Dec 06 08:40:10 volumio wireless.js[4061]: trying... Dec 06 08:40:10 volumio wireless.js[4061]: /volumio/app/plugins/system_controller/network/wireless.js:175 Dec 06 08:40:10 volumio wireless.js[4061]: if (status.ssid != undefined) { Dec 06 08:40:10 volumio wireless.js[4061]: ^ Dec 06 08:40:10 volumio wireless.js[4061]: TypeError: Cannot read property 'ssid' of undefined Dec 06 08:40:10 volumio wireless.js[4061]: at /volumio/app/plugins/system_controller/network/wireless.js:175:16 Dec 06 08:40:10 volumio wireless.js[4061]: at /volumio/node_modules/wireless-tools/iwconfig.js:129:16 Dec 06 08:40:10 volumio wireless.js[4061]: at ChildProcess.exithandler (child_process.js:213:5) Dec 06 08:40:10 volumio wireless.js[4061]: at emitTwo (events.js:106:13) Dec 06 08:40:10 volumio wireless.js[4061]: at ChildProcess.emit (events.js:191:7) Dec 06 08:40:10 volumio wireless.js[4061]: at maybeClose (internal/child_process.js:877:16) Dec 06 08:40:10 volumio wireless.js[4061]: at Socket.<anonymous> (internal/child_process.js:334:11) Dec 06 08:40:10 volumio wireless.js[4061]: at emitOne (events.js:96:13) Dec 06 08:40:10 volumio wireless.js[4061]: at Socket.emit (events.js:188:7) Dec 06 08:40:10 volumio wireless.js[4061]: at Pipe._handle.close [as _onclose] (net.js:498:12) Dec 06 08:40:10 volumio systemd[1]: wireless.service: control process exited, code=exited status=1 Dec 06 08:40:10 volumio systemd[1]: Failed to start Wireless Services. Dec 06 08:40:10 volumio systemd[1]: Unit wireless.service entered failed state. Dec 06 08:40:10 volumio sudo[4059]: pam_unix(sudo:session): session closed for user root Dec 06 08:40:20 volumio volumio[3526]: info: CoreCommandRouter::executeOnPlugin: upnp , onRestart Dec 06 08:40:20 volumio sudo[4152]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/killall upmpdcli Dec 06 08:40:20 volumio sudo[4152]: pam_unix(sudo:session): session opened for user root by (uid=0) Dec 06 08:40:20 volumio sudo[4152]: pam_unix(sudo:session): session closed for user root Dec 06 08:40:20 volumio volumio[3526]: error: Cannot kill upmpdcli Error: Command failed: /usr/bin/sudo /usr/bin/killall upmpdcli Dec 06 08:40:20 volumio volumio[3526]: upmpdcli: no process found Dec 06 08:40:20 volumio sudo[4157]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl start upmpdcli.service Dec 06 08:40:20 volumio sudo[4157]: pam_unix(sudo:session): session opened for user root by (uid=0) Dec 06 08:40:20 volumio systemd[1]: Starting UPnP Renderer front-end to MPD... Dec 06 08:40:20 volumio systemd[1]: Started UPnP Renderer front-end to MPD. Dec 06 08:40:20 volumio sudo[4157]: pam_unix(sudo:session): session closed for user root Dec 06 08:40:20 volumio volumio[3526]: info: Upmpdcli Daemon Started Dec 06 08:40:20 volumio mpd[3258]: client: [3] opened from ::ffff:127.0.0.1:45088
BUT, even having posted this for you, I wouldn’t go futzing around trying to sort out this unsupported image. I’ve seen enough for me to go and pick up one of the fully supported board/DAC combinations. Probably the Odroid, as I’m already used to working with those.

Thanks for giving me the opportunity to try this with my XU4.

Cheers.

gkkpch · December 6, 2016, 8:53am

hey, you’re not getting off with it that easy
Testing now with the XU4 to see if it is an image issue or a general problem with wifi.
I’m more and more convinced that we’re missing something, to many devices with issues.

gkkpch · December 6, 2016, 9:16am

this is what I get with an rtl8192cu when I hit Connect, which seems a 1:1 copy from EddieA’s:

Dec 06 09:09:31 volumio volumio[3616]: info: CoreCommandRouter::executeOnPlugin: network , saveWirelessNetworkSettings Dec 06 09:09:31 volumio volumio[3616]: info: Saving new wireless network Dec 06 09:09:31 volumio sudo[4825]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl restart wireless.service Dec 06 09:09:31 volumio sudo[4825]: pam_unix(sudo:session): session opened for user root by (uid=0) Dec 06 09:09:31 volumio systemd[1]: Starting Wireless Services... Dec 06 09:09:32 volumio wireless.js[4827]: start Dec 06 09:09:32 volumio wireless.js[4827]: Cleaning previous... Dec 06 09:09:32 volumio systemd[1]: Stopped hotspot.service. Dec 06 09:09:32 volumio wireless.js[4827]: stophotspotchild process exited with code 0 Dec 06 09:09:32 volumio sudo[4836]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ip addr flush dev wlan0 Dec 06 09:09:32 volumio sudo[4836]: pam_unix(sudo:session): session opened for user root by (uid=0) Dec 06 09:09:32 volumio sudo[4836]: pam_unix(sudo:session): session closed for user root Dec 06 09:09:32 volumio sudo[4838]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig wlan0 down Dec 06 09:09:32 volumio sudo[4838]: pam_unix(sudo:session): session opened for user root by (uid=0) Dec 06 09:09:32 volumio netplugd[3614]: wlan0: state INACTIVE flags 0x00001003 UP,BROADCAST,MULTICAST -> 0x00001002 BROADCAST,MULTICAST Dec 06 09:09:32 volumio netplugd[4840]: /etc/netplug/netplug wlan0 probe -> pid 4840 Dec 06 09:09:32 volumio sudo[4838]: pam_unix(sudo:session): session closed for user root Dec 06 09:09:32 volumio wireless.js[4827]: killing: kill `pgrep -f "^/usr/bin/sudo"` || true Dec 06 09:09:32 volumio netplugd[3614]: wlan0: state PROBING pid 4840 exited status 0 Dec 06 09:09:32 volumio wireless.js[4827]: ifdeconfigchild process exited with code 0 Dec 06 09:09:32 volumio wireless.js[4827]: killing: kill `pgrep -f "^wpa_supplicant"` || true Dec 06 09:09:32 volumio wireless.js[4827]: Stopped aP Dec 06 09:09:32 volumio wireless.js[4827]: Start wireless flow Dec 06 09:09:32 volumio wireless.js[4827]: Stopped hotspot (if there).. Dec 06 09:09:32 volumio sudo[4846]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ip addr flush dev wlan0 Dec 06 09:09:32 volumio sudo[4846]: pam_unix(sudo:session): session opened for user root by (uid=0) Dec 06 09:09:32 volumio sudo[4846]: pam_unix(sudo:session): session closed for user root Dec 06 09:09:32 volumio sudo[4848]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig wlan0 down Dec 06 09:09:32 volumio sudo[4848]: pam_unix(sudo:session): session opened for user root by (uid=0) Dec 06 09:09:32 volumio sudo[4848]: pam_unix(sudo:session): session closed for user root Dec 06 09:09:32 volumio wireless.js[4827]: Conf sudo ip addr flush dev wlan0 && sudo ifconfig wlan0 down Dec 06 09:09:32 volumio wireless.js[4827]: launching wpa_supplicant args: Dec 06 09:09:32 volumio wireless.js[4827]: [ '-d', Dec 06 09:09:32 volumio wireless.js[4827]: '-B', Dec 06 09:09:32 volumio wireless.js[4827]: '-Dwext', Dec 06 09:09:32 volumio wireless.js[4827]: '-c/etc/wpa_supplicant/wpa_supplicant.conf', Dec 06 09:09:32 volumio wireless.js[4827]: '-iwlan0' ] Dec 06 09:09:32 volumio wireless.js[4827]: wpasupp undefined Dec 06 09:09:32 volumio wireless.js[4827]: DHCP IP Dec 06 09:09:32 volumio wireless.js[4827]: launching /usr/bin/sudo args: Dec 06 09:09:32 volumio wireless.js[4827]: [ '/sbin/dhcpcd' ] Dec 06 09:09:32 volumio wireless.js[4827]: Start ap Dec 06 09:09:32 volumio wireless.js[4827]: ifdeconfigchild process exited with code 0 Dec 06 09:09:32 volumio sudo[4851]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/dhcpcd Dec 06 09:09:32 volumio sudo[4851]: pam_unix(sudo:session): session opened for user root by (uid=0) Dec 06 09:09:32 volumio dhcpcd[4852]: version 6.0.5 starting Dec 06 09:09:32 volumio wireless.js[4827]: dhclientstderr: dhcpcd[4852]: version 6.0.5 starting Dec 06 09:09:32 volumio kernel: rtl8192cu: MAC auto ON okay! Dec 06 09:09:32 volumio kernel: rtl8192cu: Tx queue select: 0x05 Dec 06 09:09:33 volumio netplugd[3614]: wlan0: state DOWN flags 0x00001002 BROADCAST,MULTICAST -> 0x00001003 UP,BROADCAST,MULTICAST Dec 06 09:09:33 volumio wireless.js[4827]: wpa supplicantstderr: ioctl[SIOCSIWMODE]: Operation not supported Dec 06 09:09:33 volumio wireless.js[4827]: wpa supplicantstderr: ioctl[SIOCGIWRANGE]: Operation not supported Dec 06 09:09:33 volumio wireless.js[4827]: ioctl[SIOCGIWMODE]: Operation not supported Dec 06 09:09:33 volumio wireless.js[4827]: ioctl[SIOCSIWAP]: Operation not supported Dec 06 09:09:33 volumio wireless.js[4827]: ioctl[SIOCSIWESSID]: Operation not supported Dec 06 09:09:33 volumio wireless.js[4827]: wpa supplicantstderr: ioctl[SIOCSIWENCODEEXT]: Operation not supported Dec 06 09:09:33 volumio wireless.js[4827]: wpa supplicantstderr: ioctl[SIOCSIWENCODE]: Operation not supported Dec 06 09:09:33 volumio wireless.js[4827]: ioctl[SIOCSIWENCODEEXT]: Operation not supported Dec 06 09:09:33 volumio wireless.js[4827]: ioctl[SIOCSIWENCODE]: Operation not supported Dec 06 09:09:33 volumio wireless.js[4827]: ioctl[SIOCSIWENCODEEXT]: Operation not supported Dec 06 09:09:33 volumio wireless.js[4827]: ioctl[SIOCSIWENCODE]: Operation not supported Dec 06 09:09:33 volumio wireless.js[4827]: wpa supplicantstderr: ioctl[SIOCSIWENCODEEXT]: Operation not supported Dec 06 09:09:33 volumio wireless.js[4827]: ioctl[SIOCSIWENCODE]: Operation not supported Dec 06 09:09:33 volumio wireless.js[4827]: ioctl[SIOCSIWENCODEEXT]: Operation not supported Dec 06 09:09:33 volumio wireless.js[4827]: wpa supplicantstderr: ioctl[SIOCSIWENCODE]: Operation not supported Dec 06 09:09:33 volumio wireless.js[4827]: ioctl[SIOCSIWENCODEEXT]: Operation not supported Dec 06 09:09:33 volumio wireless.js[4827]: ioctl[SIOCSIWENCODE]: Operation not supported Dec 06 09:09:33 volumio wireless.js[4827]: wpa supplicantchild process exited with code 0 Dec 06 09:09:33 volumio dhcpcd[4852]: wlan0: waiting for carrier Dec 06 09:09:33 volumio dhcpcd[4852]: eth0: soliciting an IPv6 router Dec 06 09:09:33 volumio wireless.js[4827]: dhclientstderr: dhcpcd[4852]: wlan0: waiting for carrier Dec 06 09:09:33 volumio wireless.js[4827]: dhclientstderr: dhcpcd[4852]: eth0: soliciting an IPv6 router Dec 06 09:09:33 volumio dhcpcd[4852]: eth0: rebinding lease of 192.168.0.189 Dec 06 09:09:33 volumio wireless.js[4827]: dhclientstderr: dhcpcd[4852]: eth0: rebinding lease of 192.168.0.189 Dec 06 09:09:33 volumio dhcpcd[4852]: eth0: leased 192.168.0.189 for 604800 seconds Dec 06 09:09:33 volumio dhcpcd[4852]: eth0: adding host route to 192.168.0.189 via 127.0.0.1 Dec 06 09:09:33 volumio dhcpcd[4852]: eth0: adding route to 192.168.0.0/24 Dec 06 09:09:33 volumio dhcpcd[4852]: eth0: adding default route via 192.168.0.1 Dec 06 09:09:33 volumio wireless.js[4827]: dhclientstderr: dhcpcd[4852]: eth0: leased 192.168.0.189 for 604800 seconds Dec 06 09:09:33 volumio wireless.js[4827]: dhclientstderr: dhcpcd[4852]: eth0: adding host route to 192.168.0.189 via 127.0.0.1 Dec 06 09:09:33 volumio wireless.js[4827]: dhclientstderr: dhcpcd[4852]: eth0: adding route to 192.168.0.0/24 Dec 06 09:09:33 volumio wireless.js[4827]: dhclientstderr: dhcpcd[4852]: eth0: adding default route via 192.168.0.1 Dec 06 09:09:33 volumio dhcpcd[4852]: forked to background, child pid 4913 Dec 06 09:09:33 volumio wireless.js[4827]: dhclientstderr: dhcpcd[4852]: forked to background, child pid 4913 Dec 06 09:09:33 volumio sudo[4851]: pam_unix(sudo:session): session closed for user root Dec 06 09:09:33 volumio wireless.js[4827]: dhclientchild process exited with code 0 Dec 06 09:09:33 volumio dhcpcd[4913]: eth0: removing route to 192.168.0.0/24 Dec 06 09:09:33 volumio dhcpcd[4913]: eth0: removing default route via 192.168.0.1 Dec 06 09:09:33 volumio wireless.js[4827]: trying... Dec 06 09:09:33 volumio wireless.js[4827]: /volumio/app/plugins/system_controller/network/wireless.js:175 Dec 06 09:09:33 volumio wireless.js[4827]: if (status.ssid != undefined) { Dec 06 09:09:33 volumio wireless.js[4827]: ^ Dec 06 09:09:33 volumio wireless.js[4827]: TypeError: Cannot read property 'ssid' of undefined Dec 06 09:09:33 volumio wireless.js[4827]: at /volumio/app/plugins/system_controller/network/wireless.js:175:16 Dec 06 09:09:33 volumio wireless.js[4827]: at /volumio/node_modules/wireless-tools/iwconfig.js:129:16 Dec 06 09:09:33 volumio wireless.js[4827]: at ChildProcess.exithandler (child_process.js:213:5) Dec 06 09:09:33 volumio wireless.js[4827]: at emitTwo (events.js:106:13) Dec 06 09:09:33 volumio wireless.js[4827]: at ChildProcess.emit (events.js:191:7) Dec 06 09:09:33 volumio wireless.js[4827]: at maybeClose (internal/child_process.js:877:16) Dec 06 09:09:33 volumio wireless.js[4827]: at Socket.<anonymous> (internal/child_process.js:334:11) Dec 06 09:09:33 volumio wireless.js[4827]: at emitOne (events.js:96:13) Dec 06 09:09:33 volumio wireless.js[4827]: at Socket.emit (events.js:188:7) Dec 06 09:09:33 volumio wireless.js[4827]: at Pipe._handle.close [as _onclose] (net.js:498:12) Dec 06 09:09:33 volumio systemd[1]: wireless.service: control process exited, code=exited status=1 Dec 06 09:09:33 volumio systemd[1]: Failed to start Wireless Services. Dec 06 09:09:33 volumio systemd[1]: Unit wireless.service entered failed state. Dec 06 09:09:33 volumio sudo[4825]: pam_unix(sudo:session): session closed for user root

gkkpch · December 6, 2016, 9:37am

Then I added “wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf” to /etc/network/interfaces:

[code]auto wlan0
auto lo
iface lo inet loopback

allow-hotplug eth0
iface eth0 inet dhcp

allow-hotplug wlan0
iface wlan0 inet manual
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf[/code]

when I bring up the network with

sudo ifdown wlan0 sudo ifup -v wlan0

I get this

Dec 06 09:20:23 volumio sudo[5153]: pam_unix(sudo:session): session opened for user root by volumio(uid=0) Dec 06 09:20:23 volumio systemd[1]: Reloading OpenBSD Secure Shell server. Dec 06 09:20:23 volumio sshd[3351]: Received SIGHUP; restarting. Dec 06 09:20:23 volumio systemd[1]: Reloaded OpenBSD Secure Shell server. Dec 06 09:20:24 volumio sudo[5153]: pam_unix(sudo:session): session closed for user root Dec 06 09:20:24 volumio sshd[3351]: Server listening on 0.0.0.0 port 22. Dec 06 09:20:24 volumio sshd[3351]: Server listening on :: port 22. Dec 06 09:20:35 volumio sudo[5249]: volumio : TTY=pts/1 ; PWD=/etc/network ; USER=root ; COMMAND=/usr/bin/nano interfaces Dec 06 09:20:35 volumio sudo[5249]: pam_unix(sudo:session): session opened for user root by volumio(uid=0) Dec 06 09:21:43 volumio sudo[5249]: pam_unix(sudo:session): session closed for user root Dec 06 09:21:46 volumio sudo[5257]: volumio : TTY=pts/1 ; PWD=/etc/network ; USER=root ; COMMAND=/sbin/ifdown wlan0 Dec 06 09:21:46 volumio sudo[5257]: pam_unix(sudo:session): session opened for user root by volumio(uid=0) Dec 06 09:21:46 volumio sudo[5257]: pam_unix(sudo:session): session closed for user root Dec 06 09:21:48 volumio sudo[5290]: volumio : TTY=pts/1 ; PWD=/etc/network ; USER=root ; COMMAND=/sbin/ifup -v wlan0 Dec 06 09:21:48 volumio sudo[5290]: pam_unix(sudo:session): session opened for user root by volumio(uid=0) Dec 06 09:21:48 volumio wpa_supplicant[5306]: Successfully initialized wpa_supplicant Dec 06 09:21:48 volumio wpa_supplicant[5306]: Line 12: Invalid WEP key length 12 - this network block will be ignored Dec 06 09:21:48 volumio wpa_supplicant[5306]: rfkill: Cannot open RFKILL control device Dec 06 09:21:48 volumio systemd[1]: Reloading OpenBSD Secure Shell server. Dec 06 09:21:48 volumio sshd[3351]: Received SIGHUP; restarting. Dec 06 09:21:48 volumio systemd[1]: Reloaded OpenBSD Secure Shell server. Dec 06 09:21:48 volumio sshd[3351]: Server listening on 0.0.0.0 port 22. Dec 06 09:21:48 volumio sshd[3351]: Server listening on :: port 22. Dec 06 09:21:49 volumio sudo[5290]: pam_unix(sudo:session): session closed for user root Dec 06 09:21:49 volumio wpa_supplicant[5307]: wlan0: SME: Trying to authenticate with 90:5c:44:0a:01:3a (SSID='UPC419E94D' freq=2462 MHz) Dec 06 09:21:49 volumio kernel: wlan0: authenticate with 90:5c:44:0a:01:3a Dec 06 09:21:49 volumio kernel: wlan0: send auth to 90:5c:44:0a:01:3a (try 1/3) Dec 06 09:21:49 volumio wpa_supplicant[5307]: wlan0: Trying to associate with 90:5c:44:0a:01:3a (SSID='UPC419E94D' freq=2462 MHz) Dec 06 09:21:49 volumio kernel: wlan0: authenticated Dec 06 09:21:49 volumio kernel: wlan0: associating with AP with corrupt probe response Dec 06 09:21:49 volumio kernel: wlan0: associate with 90:5c:44:0a:01:3a (try 1/3) Dec 06 09:21:49 volumio kernel: wlan0: RX AssocResp from 90:5c:44:0a:01:3a (capab=0x411 status=0 aid=1) Dec 06 09:21:49 volumio wpa_supplicant[5307]: wlan0: Associated with 90:5c:44:0a:01:3a Dec 06 09:21:49 volumio kernel: wlan0: associated Dec 06 09:21:49 volumio wpa_supplicant[5307]: wlan0: WPA: Key negotiation completed with 90:5c:44:0a:01:3a [PTK=CCMP GTK=TKIP] Dec 06 09:21:49 volumio wpa_supplicant[5307]: wlan0: CTRL-EVENT-CONNECTED - Connection to 90:5c:44:0a:01:3a completed [id=0 id_str=] Dec 06 09:21:49 volumio netplugd[3614]: wlan0: state INACTIVE flags 0x00011003 UP,BROADCAST,MULTICAST,10000 -> 0x00011043 UP,BROADCAST,RUNNING,MULTICAST,10000 Dec 06 09:21:49 volumio netplugd[5419]: /etc/netplug/netplug wlan0 in -> pid 5419 Dec 06 09:21:49 volumio netplugd[3614]: wlan0: state INNING pid 5419 exited status 0 Dec 06 09:21:52 volumio kernel: cfg80211: World regulatory domain updated: Dec 06 09:21:52 volumio kernel: cfg80211: DFS Master region: unset Dec 06 09:21:52 volumio kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Dec 06 09:21:52 volumio kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) Dec 06 09:21:52 volumio kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) Dec 06 09:21:52 volumio kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) Dec 06 09:21:52 volumio kernel: cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A) Dec 06 09:21:52 volumio kernel: cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s) Dec 06 09:21:52 volumio kernel: cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) Dec 06 09:21:52 volumio kernel: cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) Dec 06 09:21:52 volumio kernel: cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) Dec 06 09:21:52 volumio wpa_supplicant[5307]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD

It gets wlan0 associated with my AP, but still no IP

gkkpch · December 6, 2016, 9:52am

Finally changed /etc/network/interfaces to use dhcp on wlan0:

[code]auto wlan0
auto lo
iface lo inet loopback

allow-hotplug eth0
iface eth0 inet dhcp

allow-hotplug wlan0
iface wlan0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
[/code]

Brought wlan0 up with

sudo ifdown wlan0 sudo ifup -v wlan
and success:

Dec 06 09:47:33 volumio sudo[7072]: volumio : TTY=pts/1 ; PWD=/etc/network ; USER=root ; COMMAND=/sbin/ifup -v wlan0 Dec 06 09:47:33 volumio sudo[7072]: pam_unix(sudo:session): session opened for user root by volumio(uid=0) Dec 06 09:47:33 volumio wpa_supplicant[7091]: Successfully initialized wpa_supplicant Dec 06 09:47:33 volumio wpa_supplicant[7091]: Line 13: Invalid WEP key length 12 - this network block will be ignored Dec 06 09:47:33 volumio wpa_supplicant[7091]: rfkill: Cannot open RFKILL control device Dec 06 09:47:33 volumio kernel: rtl8192cu: MAC auto ON okay! Dec 06 09:47:33 volumio kernel: rtl8192cu: Tx queue select: 0x05 Dec 06 09:47:34 volumio dhcpcd[7113]: control_open: Connection refused Dec 06 09:47:34 volumio dhcpcd[7113]: version 6.0.5 starting Dec 06 09:47:34 volumio dhcpcd[7113]: wlan0: waiting for carrier Dec 06 09:47:35 volumio wpa_supplicant[7109]: wlan0: SME: Trying to authenticate with 90:5c:44:0a:01:3a (SSID='UPC419E94D' freq=2462 MHz) Dec 06 09:47:35 volumio kernel: wlan0: authenticate with 90:5c:44:0a:01:3a Dec 06 09:47:35 volumio kernel: wlan0: send auth to 90:5c:44:0a:01:3a (try 1/3) Dec 06 09:47:35 volumio wpa_supplicant[7109]: wlan0: Trying to associate with 90:5c:44:0a:01:3a (SSID='UPC419E94D' freq=2462 MHz) Dec 06 09:47:35 volumio kernel: wlan0: authenticated Dec 06 09:47:35 volumio kernel: wlan0: associating with AP with corrupt probe response Dec 06 09:47:35 volumio kernel: wlan0: associate with 90:5c:44:0a:01:3a (try 1/3) Dec 06 09:47:35 volumio kernel: wlan0: RX AssocResp from 90:5c:44:0a:01:3a (capab=0x411 status=0 aid=1) Dec 06 09:47:35 volumio kernel: wlan0: associated Dec 06 09:47:35 volumio wpa_supplicant[7109]: wlan0: Associated with 90:5c:44:0a:01:3a Dec 06 09:47:35 volumio wpa_supplicant[7109]: wlan0: WPA: Key negotiation completed with 90:5c:44:0a:01:3a [PTK=CCMP GTK=TKIP] Dec 06 09:47:35 volumio wpa_supplicant[7109]: wlan0: CTRL-EVENT-CONNECTED - Connection to 90:5c:44:0a:01:3a completed [id=0 id_str=] Dec 06 09:47:35 volumio dhcpcd[7113]: wlan0: carrier acquired Dec 06 09:47:35 volumio dhcpcd[7113]: wlan0: soliciting an IPv6 router Dec 06 09:47:35 volumio dhcpcd[7113]: wlan0: soliciting a DHCP lease Dec 06 09:47:35 volumio dhcpcd[7113]: wlan0: offered 192.168.0.152 from 192.168.0.1 Dec 06 09:47:38 volumio kernel: cfg80211: World regulatory domain updated: Dec 06 09:47:38 volumio kernel: cfg80211: DFS Master region: unset Dec 06 09:47:38 volumio kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Dec 06 09:47:38 volumio kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) Dec 06 09:47:38 volumio kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) Dec 06 09:47:38 volumio kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) Dec 06 09:47:38 volumio kernel: cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A) Dec 06 09:47:38 volumio kernel: cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s) Dec 06 09:47:38 volumio kernel: cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) Dec 06 09:47:38 volumio kernel: cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) Dec 06 09:47:38 volumio kernel: cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) Dec 06 09:47:38 volumio wpa_supplicant[7109]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Dec 06 09:47:40 volumio dhcpcd[7113]: wlan0: leased 192.168.0.152 for 604800 seconds Dec 06 09:47:40 volumio avahi-daemon[3378]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.152. Dec 06 09:47:40 volumio avahi-daemon[3378]: New relevant interface wlan0.IPv4 for mDNS. Dec 06 09:47:40 volumio dhcpcd[7113]: wlan0: adding host route to 192.168.0.152 via 127.0.0.1 Dec 06 09:47:40 volumio dhcpcd[7113]: wlan0: adding route to 192.168.0.0/24 Dec 06 09:47:40 volumio avahi-daemon[3378]: Registering new address record for 192.168.0.152 on wlan0.IPv4. Dec 06 09:47:40 volumio dhcpcd[7113]: wlan0: adding default route via 192.168.0.1 Dec 06 09:47:40 volumio dhcpcd[7113]: forked to background, child pid 7185 Dec 06 09:47:41 volumio volumio[3616]: Discovery: this is already registered, 17a4497d-a5d8-4705-ac07-2ce9ce418a7a Dec 06 09:47:41 volumio volumio[3616]: info: mDNS: Found device Volumio Dec 06 09:47:41 volumio systemd[1]: Reloading OpenBSD Secure Shell server. Dec 06 09:47:41 volumio sshd[3351]: Received SIGHUP; restarting. Dec 06 09:47:41 volumio systemd[1]: Reloaded OpenBSD Secure Shell server. Dec 06 09:47:41 volumio sshd[3351]: Server listening on 0.0.0.0 port 22. Dec 06 09:47:41 volumio sshd[3351]: Server listening on :: port 22. Dec 06 09:47:41 volumio sudo[7072]: pam_unix(sudo:session): session closed for user root Dec 06 09:47:42 volumio ntpd[3409]: Listen normally on 6 wlan0 192.168.0.152 UDP 123 Dec 06 09:47:42 volumio ntpd[3409]: 192.33.214.47 interface 192.168.0.189 -> 192.168.0.152 Dec 06 09:47:42 volumio ntpd[3409]: 192.33.96.102 interface 192.168.0.189 -> 192.168.0.152 Dec 06 09:47:42 volumio ntpd[3409]: 195.186.1.100 interface 192.168.0.189 -> 192.168.0.152 Dec 06 09:47:42 volumio ntpd[3409]: 82.220.2.2 interface 192.168.0.189 -> 192.168.0.152 Dec 06 09:47:42 volumio ntpd[3409]: peers refreshed

EDIT This sequence of events is an exact copy of what I experience with pine64 (checked it just before) and it also looks like what people have reported for cubox-i (after the driver fix).
This proves it is not a driver or a wpasupplicant problem, more like a dhcp problem I don’t understand yet.

gkkpch · December 6, 2016, 5:13pm

No change in interfaces left wlan0 manual, instead started the dhcpcd service which seems to exit during boot
Now I can bring wlan0 up and down via the command line as long as the wpa-conf line is in interfaces.
Next thing to find out: why does the dhcpcd service exit during boot???

EddieA · December 6, 2016, 7:03pm

LOL. I’m still willing to help, if I can.

Looking at the logs I pasted, I’m not so sure my dongle is getting associated to the AP:

Dec 06 08:40:10 volumio wireless.js[4061]: trying...
Dec 06 08:40:10 volumio wireless.js[4061]: /volumio/app/plugins/system_controller/network/wireless.js:175
Dec 06 08:40:10 volumio wireless.js[4061]: if (status.ssid != undefined) {
Dec 06 08:40:10 volumio wireless.js[4061]: ^
Dec 06 08:40:10 volumio wireless.js[4061]: TypeError: Cannot read property 'ssid' of undefined
Dec 06 08:40:10 volumio wireless.js[4061]: at /volumio/app/plugins/system_controller/network/wireless.js:175:16
Dec 06 08:40:10 volumio wireless.js[4061]: at /volumio/node_modules/wireless-tools/iwconfig.js:129:16
Dec 06 08:40:10 volumio wireless.js[4061]: at ChildProcess.exithandler (child_process.js:213:5)
Dec 06 08:40:10 volumio wireless.js[4061]: at emitTwo (events.js:106:13)
Dec 06 08:40:10 volumio wireless.js[4061]: at ChildProcess.emit (events.js:191:7)
Dec 06 08:40:10 volumio wireless.js[4061]: at maybeClose (internal/child_process.js:877:16)
Dec 06 08:40:10 volumio wireless.js[4061]: at Socket.<anonymous> (internal/child_process.js:334:11)
Dec 06 08:40:10 volumio wireless.js[4061]: at emitOne (events.js:96:13)
Dec 06 08:40:10 volumio wireless.js[4061]: at Socket.emit (events.js:188:7)
Dec 06 08:40:10 volumio wireless.js[4061]: at Pipe._handle.close [as _onclose] (net.js:498:12)
Dec 06 08:40:10 volumio systemd[1]: wireless.service: control process exited, code=exited status=1
Dec 06 08:40:10 volumio systemd[1]: Failed to start Wireless Services.
Dec 06 08:40:10 volumio systemd[1]: Unit wireless.service entered failed state.

So without that, it shouldn’t even be trying to contact the DHCP server.

Cheers.

gkkpch · December 6, 2016, 7:14pm

Both our first logs are identical, I used the commandline to try and find where the problem was, my second attempt showed, that authentication and association worked, but I was still not getting an IP. That again is the dhcpcd daemon (the dhcp client) problem, it is not running…

gkkpch · March 18, 2017, 10:24pm

As the first version has been released I’m locking this thread.
Should issues arise, please open a thread in the Help section.