If you connect to Volumio hotspot, Volumio UI sits at: 192.168.211.1
volumio.github.io/docs/User_Man … Guide.html
let me know
Didn’t work.
I have configured PC with the static IP 192.168.211.100/24 on WiFi, with or without gw 192.168.211.1.
I can ping 192.168.211.1, but it won’t open web UI (tried both volumio.local and 192.168.211.1).
I did some more tests - tried from different browsers (Firefox/ Chrome/ Edge), nothing helped.
I figured out I can login via SSH, but with non-working sudo, don’t really know what else I could try,
Maybe my changes to the image broke something with sudo, but I’m not sure why.
I could not test the image so I can’t tell: maybe you can redo the change by yourself from a blank image.
What is your wifi dongle? Which chipset specifically? (hostspot may not be supported with all yet. there are some driver dependencies in some cases).
Anyhow, all these are just quick & dirty hacks to circumvent the initial “auto” issue for rpi0.
There are also few other networking issues that may cause problems in certain circumstances (not specific to rpi0 I think).
Having an ethernet dongle for rescue helped me a lot to stabilize and refine my rpi0 setup.
You may have to wait a bit until those are resolved to enjoy Volumo2 on your rpi0: dev team is doing a lot on many things in parallel, so we need to be patient.
My WiFI dongle is WLU6331 (this one https://shop.pimoroni.com/products/official-raspberry-pi-wifi-dongle).
I’ll try to go through image modification myself ass soon as grab some time, I’ll let you know how it went.
I understand there are priorities to to take care of first and really appreciate your will to help.
I could try to send you an image of my pi zero this weekend. But I have to set it on a 4gb card, hence the upload/download will be quite big.
Besides skipping the auto statement I can preconfigure a Wifi to login to. Just give me the right ssid and password (or I chose some default ones and you can open a hotpot with that details on your phone)
Sure, if you can make the image, I’ll give it a try.
Sent you SSID/ pass in PM.
Hi, I’m having the same problem with my Raspberry Pi Zero (and Phat DAC) and the same problems with your image mentioned above appeared as well for me. I could connect to the Volumio wifi but not to the Volumio control page with my browser (192.168.211.1 nor volumio.local worked).
Therefore I would be very happy if you could let me use your other image, too.
Thanks already very much for your help!
There are definitely problems here with wifi and the RPi0. I now have a working setup on a RPi0, but only after changing my network adapter. Currently I am using an Edimax usb dongle. Btw this works without any of the removing of “auto” statements in /etc/network/interfaces.
I think that Raspbian really blew away the “playing field” with their changes (not standard Debian) to dhcp/dhcpd/dhcpcd
Actually hostspot introduction in Volumio has caused significant changes in network management, and it does not seem fully stabilized yet (various dhcpd, dsnmasq & hostapd messages in log illustrate this).
This has created issue on all models, but rpi0 suffers most as network interfaces variability does not help: indeed none are built-in on that model.
Edimax dongle seems well supported indeed, but some others work ok too.
TL-WN725N V2 (and clones) work fine with built-in driver as long as hotspot is NOT enabled, but needs a custom driver for hotspot mode, etc…
As long as you have a chance to boot once, you can do fine-tuning using another interface and/or keyboard.
However, since initial boot is with hotspot ON, user may fall into networking issues right-away and get stucked.
Hopefully dev team will find time soon to fix overall network management.
Yes, networking is our first priority.
However, we recommed to use the EDIMAX NANO DONGLE, because it is the most stable (driver wise) and we simply cannot support every wifi dongle out there. So if someone wants consistent results with wifi, we suggest to use the edimax one
Is it ok to host a version, which runs on the pi0 with a predesigned Wifi-Setup?
I’m new to this, on headless pi zero + Volumio 2.031 + white official Raspberry wifi dongle (raspberrypi.org/products/usb-wifi-dongle/)
/etc/network/interfaces has been modified to this:
[code]#auto wlan0
auto lo
iface lo inet loopback
#auto eth0
allow-hotplug eth0
iface eth0 inet dhcp
allow-hotplug wlan0
iface wlan0 inet manual[/code]
I’m able to connect to AP, but not to GUI. SSH and sudo work. Some commands:
[code]
volumio@volumio:~$ free -h
total used free shared buffers cached
Mem: 482M 382M 100M 8.6M 60M 210M
-/+ buffers/cache: 110M 371M
Swap: 511M 0B 511M
volumio@volumio:~$ top
top - 17:27:17 up 34 min, 2 users, load average: 1.37, 1.17, 1.01
Tasks: 103 total, 2 running, 101 sleeping, 0 stopped, 0 zombie
%Cpu(s): 91.8 us, 7.2 sy, 0.0 ni, 0.9 id, 0.1 wa, 0.0 hi, 0.1 si, 0.0 st
KiB Mem: 493844 total, 402468 used, 91376 free, 61816 buffers
KiB Swap: 524284 total, 0 used, 524284 free. 216056 cached Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
6027 volumio 20 0 84216 32844 16256 R 73.5 6.7 0:04.52 node
6036 volumio 20 0 3464 2084 1688 R 8.6 0.4 0:00.06 top
1 root 20 0 5444 4064 2856 S 0.0 0.8 0:32.16 systemd
2 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kthreadd
3 root 20 0 0 0 0 S 0.0 0.0 0:01.24 ksoftirqd/0
5 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/0:0H
7 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kdevtmpfs
8 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 netns
9 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 perf
10 root 20 0 0 0 0 S 0.0 0.0 0:00.00 khungtaskd
11 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 writeback
12 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 crypto
13 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset
14 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kblockd
16 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 rpciod
19 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kswapd0
20 root 20 0 0 0 0 S 0.0 0.0 0:00.00 fsnotify_mark
21 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 nfsiod
30 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kthrotld
31 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset
32 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset
33 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset
volumio@volumio:~$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mmcblk0p2 2.0G 744M 1.2G 39% /imgpart
/dev/loop0 247M 247M 0 100% /static
overlay 27G 522M 25G 3% /
devtmpfs 233M 0 233M 0% /dev
tmpfs 242M 0 242M 0% /dev/shm
tmpfs 242M 8.7M 233M 4% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 242M 0 242M 0% /sys/fs/cgroup
tmpfs 242M 8.0K 242M 1% /tmp
tmpfs 242M 0 242M 0% /var/spool/cups
tmpfs 242M 4.0K 242M 1% /var/log
tmpfs 242M 0 242M 0% /var/spool/cups/tmp
/dev/mmcblk0p1 61M 29M 33M 47% /boot
tmpfs 49M 0 49M 0% /run/user/1000[/code]
The node process changes PID rapidly and uses a lot of CPU, so maybe it crashes and restarts all the time.
Can I help by providing any debugging info from this system?
Paste here the result of
sudo journalctl -f
volumio@volumio:~$ sudo journalctl -f
– Logs begin at Wed 2016-11-23 17:39:58 UTC. –
Nov 23 17:44:07 volumio volumio[1203]: Enabling Swap
Nov 23 17:44:07 volumio systemd[1]: volumio.service holdoff time over, scheduling restart.
Nov 23 17:44:07 volumio systemd[1]: Stopping Volumio Backend Module…
Nov 23 17:44:07 volumio systemd[1]: Starting Volumio Backend Module…
Nov 23 17:44:07 volumio volumio[1203]: swapon: /data/swapfile: swapon failed: Device or resource busy
Nov 23 17:44:07 volumio systemd[1]: Started Volumio Backend Module.
Nov 23 17:44:07 volumio systemd[1]: dynamicswap.service: main process exited, code=exited, status=255/n/a
Nov 23 17:44:07 volumio systemd[1]: Unit dynamicswap.service entered failed state.
Nov 23 17:44:07 volumio sudo[1211]: volumio : TTY=pts/0 ; PWD=/home/volumio ; USER=root ; COMMAND=/bin/journalctl -f
Nov 23 17:44:07 volumio sudo[1211]: pam_unix(sudo:session): session opened for user root by volumio(uid=0)
Nov 23 17:44:14 volumio volumio[1209]: /volumio/node_modules/fs-extra/lib/mkdirs/mkdirs-sync.js:47
Nov 23 17:44:14 volumio volumio[1209]: throw err0
Nov 23 17:44:14 volumio volumio[1209]: ^
Nov 23 17:44:14 volumio volumio[1209]: Error: EACCES: permission denied, mkdir ‘/data/albumart’
Nov 23 17:44:14 volumio volumio[1209]: at Error (native)
Nov 23 17:44:14 volumio volumio[1209]: at Object.fs.mkdirSync (fs.js:922:18)
Nov 23 17:44:14 volumio volumio[1209]: at mkdirsSync (/volumio/node_modules/fs-extra/lib/mkdirs/mkdirs-sync.js:29:9)
Nov 23 17:44:15 volumio volumio[1209]: at Object.mkdirsSync (/volumio/node_modules/fs-extra/lib/mkdirs/mkdirs-sync.js:35:16)
Nov 23 17:44:15 volumio volumio[1209]: at Object.setFolder (/volumio/app/plugins/miscellanea/albumart/albumart.js:29:8)
Nov 23 17:44:15 volumio volumio[1209]: at Object. (/volumio/index.js:17:10)
Nov 23 17:44:15 volumio volumio[1209]: at Module._compile (module.js:570:32)
Nov 23 17:44:15 volumio volumio[1209]: at Object.Module._extensions…js (module.js:579:10)
Nov 23 17:44:15 volumio volumio[1209]: at Module.load (module.js:487:32)
Nov 23 17:44:15 volumio volumio[1209]: at tryModuleLoad (module.js:446:12)
Nov 23 17:44:14 volumio systemd[1]: volumio.service: main process exited, code=exited, status=1/FAILURE
Nov 23 17:44:14 volumio systemd[1]: Unit volumio.service entered failed state.
Nov 23 17:44:15 volumio systemd[1]: Starting dynamicswap.service…
Nov 23 17:44:15 volumio systemd[1]: Started dynamicswap.service.
Nov 23 17:44:15 volumio volumio[1222]: 512 MB or less RAM Detected, need to enable swap
Nov 23 17:44:15 volumio volumio[1222]: Enabling Swap
Nov 23 17:44:15 volumio volumio[1222]: swapon: /data/swapfile: swapon failed: Device or resource busy
Nov 23 17:44:15 volumio systemd[1]: dynamicswap.service: main process exited, code=exited, status=255/n/a
Nov 23 17:44:15 volumio systemd[1]: Unit dynamicswap.service entered failed state.
Nov 23 17:44:15 volumio systemd[1]: volumio.service holdoff time over, scheduling restart.
Nov 23 17:44:15 volumio systemd[1]: Starting dynamicswap.service…
Nov 23 17:44:15 volumio systemd[1]: Started dynamicswap.service.
Nov 23 17:44:15 volumio systemd[1]: Stopping Volumio Backend Module…
Nov 23 17:44:15 volumio systemd[1]: Starting Volumio Backend Module…
Nov 23 17:44:15 volumio systemd[1]: Started Volumio Backend Module.
Nov 23 17:44:15 volumio volumio[1229]: 512 MB or less RAM Detected, need to enable swap
Nov 23 17:44:15 volumio volumio[1229]: Enabling Swap
Nov 23 17:44:15 volumio volumio[1229]: swapon: /data/swapfile: swapon failed: Device or resource busy
Nov 23 17:44:15 volumio systemd[1]: dynamicswap.service: main process exited, code=exited, status=255/n/a
Nov 23 17:44:15 volumio systemd[1]: Unit dynamicswap.service entered failed state.
Nov 23 17:44:23 volumio volumio[1230]: /volumio/node_modules/fs-extra/lib/mkdirs/mkdirs-sync.js:47
Nov 23 17:44:23 volumio volumio[1230]: throw err0
Nov 23 17:44:23 volumio volumio[1230]: ^
Nov 23 17:44:23 volumio volumio[1230]: Error: EACCES: permission denied, mkdir ‘/data/albumart’
Nov 23 17:44:23 volumio volumio[1230]: at Error (native)
Nov 23 17:44:23 volumio volumio[1230]: at Object.fs.mkdirSync (fs.js:922:18)
Nov 23 17:44:23 volumio volumio[1230]: at mkdirsSync (/volumio/node_modules/fs-extra/lib/mkdirs/mkdirs-sync.js:29:9)
Nov 23 17:44:23 volumio volumio[1230]: at Object.mkdirsSync (/volumio/node_modules/fs-extra/lib/mkdirs/mkdirs-sync.js:35:16)
Nov 23 17:44:23 volumio volumio[1230]: at Object.setFolder (/volumio/app/plugins/miscellanea/albumart/albumart.js:29:8)
Nov 23 17:44:23 volumio volumio[1230]: at Object. (/volumio/index.js:17:10)
Nov 23 17:44:23 volumio volumio[1230]: at Module._compile (module.js:570:32)
Nov 23 17:44:23 volumio volumio[1230]: at Object.Module._extensions…js (module.js:579:10)
Nov 23 17:44:23 volumio volumio[1230]: at Module.load (module.js:487:32)
Nov 23 17:44:23 volumio volumio[1230]: at tryModuleLoad (module.js:446:12)
et cetera…
The issue here is that you probably turned off the device while it was still doing its first boot procedure.
So, as stated in the quick start guide, leave it alone for 10 minutes at first boot
Reflash and do what above
Let me know
mi
caught me there - now it works!
Procedure:
Flash
Boot, waited 15 minutes
Change /etc/network/interfaces in current squashfs as described above
Boot, waited 15 minutes
Thanks for your very fast support, michelangelo
Don’t worry! Glad to help
I am looking at this issue as we speak, thanks to a suggestion I’ve found out how to remove those lines from interfaces file
Here’s a potential fix for boot on PI0:
updates.volumio.org/pi/volumio/2 … pi.img.zip
Please, if someone is willing to test, let me know if that works for pi0
thanks
A quick test: it boots ok and seems to work on my rpi0 1.3 (on a test SD-card) with just a wifi-dongle network.
When I want to put this update on my 32 GB card with the previous Volumio version + all the music - can I avoid erasing it by just replacing the squashfs - or?