Thank you Very Much , i did work now i’m connect
let me tell you you know youre stuff
I Really Apreciate it
1 Like
Hi, I am already installed latest official Volumio 3 to Atom N455 x64 PC, after boot up, only login screen appears without GUI (on previous 2.9 version, it’s working normally), it’s default behavior or something hardware related isn’t supported?
Thank you
i would advice you to use your ip on port 3000 to see the GUI so http://< your ip >:3000
best regards,
dvo
X86 has kiosk mode built-in, so don’t install the touchscreen plugin to avoid messing up the install.
Please supply a log so the we are able to check any graphics issues.
Also refer to post #1 for the information we need.
Please create the log after a fresh reboot.
1 Like
Still lot of problems with Volumio, i tried installing to my bootable 32GB SDCARD with success, but after restart it stop booting with error, why? I am on latest 2.9, very old version 2.3 worked fine.
findfs: unable to resolve ‘UUID=63d002ae-4956-422e-b71f-84385626ceeb’
"findfs: unable to resolve ‘UUID=C3ED-C91F’
and bellow that
“sh: can’t access tty; job control turned off”
you mean that you reverted to Volumio 2.0?
Hello,
Volumio 3 - works great and I’m very happy. But there is one problem - please help …
My computer is ZOTAC ZBOX PRO PI335 pico.
It has a card reader that supports Micro SDHC / SDXC cards.
Memory card (micro SDXC 512Gb) - Lexar Professional 1066x UHS-I U3 V30 A2 + ADP (160/120 MB/s)
Volumio is installed, runs and works well from the built-in internal flash drive. I use the Micro SD card only for recording and playing music files.
Problem:
Volumio always identifies a 512Gb card as a 64Gb card.
I tried different formatting options (ExtFAT, FAT32 and Ext4) and connected this card to Volumio via an external USB card reader - nothing helped … At the same time, Win10 correctly determines the size of this card (during formatting and operation).
Question:
- Is this a limitation of Volumio V3 or is it a bug and can be fixed?
- What can I do for you to investigate (check) this problem and, if possible, fix it …
(sorry i counld not find the x86 section to put this post in. )
Hi,
I am installing Volumio3 on my Intel NUC and I got stuck when starting from usb.
- Intel NUC: NUC5i5RYH
- Volumio-3.175-2021-12-13-x86_amd64.img
I flashed the img on an usb stick (fat32).
Booted the NUC from the usb stick.
Now I get these errors:
findfs: unable to resolve 'UUID=71ab3e29-2f21-412e-94bc-14fca9db74f2
findfs: unable to resolve 'UUID=58D2-553A
findfs: unable to resolve 'UUID=8f37fff1-fda1-4aa4-a1c7-1c29a371b21a
BusyBox v1.30.1 (Debian 1:1.30.1-4) built-in shell (ash)
sh: can’t access tty; job control turned off.
HOW do I fix this ?
1 Like
Your post was moved to a more suitable place.
This is likely an x86 kernel issue, but more info is required to analyze what is happening.
I have not seen this before and I don’t have such a card to test with.
Please refer to the first post in this thread for the information I need.
For the log part, please proceed as follows:
- Reboot Volumio without the card inserted.
- Wait till Volumio has started completely
- Insert the card
- Create a log as described in the documentation.
We have seen this before, also during the beta phase.
See here: Post #106 in this thread
Likely caused by incorrectly flashed usb sticks.
Either using the wrong method or tool.
People were able to correct this.
How did you flash the USB stick? Which tool did you use and on which platform (Windows, PC, Mac)?
And in case you used “dd”, can you tell us exactly how you used it?
Hi,
To format the usb card I use diskpart on my Asus Windows 10 laptop.
Select disk 2
Clean.
Create partition primary size=28000
Select partition 1.
Active
format fs=fat32 quick
and then balenaEtcher to flash the image
Something i can do to improve this process ?
1 Like
yes, forget all of this 
There is no need to partition a disk before you flash.
Flashing means the image is copied sector-by-sector, the whole disk is being overwritten for the size of the .img
If you wish, you can use diskpart once again, but only to remove the partitions, nothing else.
This gives you a clean stick to start with, but because of the sector-by-sector copy process, this should not be necessary.
The problem might be balenaEtcher being unreliable. Other people had the same issues as you and changed to Rufus, which appears to do the job properly.
Flash the stick with Rufus, try it, I think it will solve your issues.
Follow @RichA 's post #106 in this thread (you have the link), he did the same, switched to Rufus and it solved his problems.
thanks, i’ll try tomorrow
Z83II Audio Problem
v3.175
inxi output
System: Host: volumiofrontroom Kernel: 5.10.79 x86_64 bits: 64 compiler: N/A Console: tty 0 dm: N/A
Distro: Debian GNU/Linux 10 (buster)
Machine: Type: Desktop System: AZW product: Z83 II v: N/A serial:
Mobo: AMI model: Cherry Trail CR serial: UEFI: American Megatrends v: YB1007 date: 08/17/2017
CPU: Topology: Quad Core model: Intel Atom x5-Z8350 bits: 64 type: MCP arch: Airmont rev: 4 L2 cache: 1024 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 11520
Speed: 815 MHz min/max: 480/1920 MHz Core speeds (MHz): 1: 1366 2: 1586 3: 1328 4: 1187
Graphics: Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers
driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:22b0
Display: tty server: X.org 1.20.4 driver: modesetting unloaded: fbdev,vesa tty: 124x38
Message: Unable to show advanced data. Required tool glxinfo missing.
Audio: Device-1: bytcr-rt5651 driver: bytcr-rt5651 message: bus/chip ids unavailable
Device-2: Intel HDMI/DP LPE Audio driver: HdmiLpeAudio message: bus/chip ids unavailable
Sound Server: ALSA v: k5.10.79
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 v: kernel port: e000
bus ID: 01:00.0 chip ID: 10ec:8168
IF: eth0 state: up speed: 100 Mbps duplex: full mac:
IF-ID-1: wlan0 state: up mac:
Drives: Local Storage: total: 57.77 GiB used: 1.72 GiB (3.0%)
ID-1: /dev/mmcblk0 model: DF4032 size: 29.12 GiB serial: rev: 0x8 scheme: GPT
ID-2: /dev/sda type: USB vendor: SanDisk model: USB 3.2Gen1 size: 28.65 GiB serial: rev: 1.00
scheme: GPT
Partition: ID-1: / size: 24.34 GiB used: 69.2 MiB (0.3%) fs: overlay source: ERR-102
ID-2: /boot size: 170.8 MiB used: 60.1 MiB (35.2%) fs: vfat dev: /dev/sda1
Sensors: Missing: Required tool sensors not installed. Check --recommends
Info: Processes: 193 Uptime: 2m Memory: 1.88 GiB used: 511.5 MiB (26.6%) Init: systemd v: 241 runlevel: 5
default: 2 Compilers: gcc: N/A Shell: bash v: 5.0.3 running in: tty 0 (SSH) inxi: 3.0.32
aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: bytcrrt5651 [bytcr-rt5651], device 0: Audio () []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: bytcrrt5651 [bytcr-rt5651], device 1: Deep-Buffer Audio ()
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Audio [Intel HDMI/DP LPE Audio], device 0: HdmiLpeAudio [Intel HDMI/DP LPE Audi]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Audio [Intel HDMI/DP LPE Audio], device 1: HdmiLpeAudio [Intel HDMI/DP LPE Audi]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Audio [Intel HDMI/DP LPE Audio], device 2: HdmiLpeAudio [Intel HDMI/DP LPE Audi]
Subdevices: 1/1
Subdevice #0: subdevice #0
system log : see 13:41:30
Worked fine on headphones from jack on pre-release version, but now complains of “Audio Port: ASoC: no backend DAIs enabled for Audio Port” accompanied by a seg fault.
lspci
00:00.0 Host bridge: VIA Technologies, Inc. VX900 Host Bridge: Host Control (rev 80)
00:00.1 Host bridge: VIA Technologies, Inc. VX900 Error Reporting
00:00.2 Host bridge: VIA Technologies, Inc. VX900 CPU Bus Controller
00:00.3 Host bridge: VIA Technologies, Inc. VX900 DRAM Bus Control
00:00.4 Host bridge: VIA Technologies, Inc. VX900 Power Management and Chip Testing Control
00:00.5 Host bridge: VIA Technologies, Inc. VX900 APIC and Central Traffic Control
00:00.6 Host bridge: VIA Technologies, Inc. VX900 Scratch Registers
00:00.7 Host bridge: VIA Technologies, Inc. VX900 North-South Module Interface Control
00:01.0 VGA compatible controller: VIA Technologies, Inc. VX900 Graphics [Chrome9 HD]
00:03.0 PCI bridge: VIA Technologies, Inc. VX900 PCI Express Root Port 0
00:03.1 PCI bridge: VIA Technologies, Inc. VX900 PCI Express Root Port 1
00:03.2 PCI bridge: VIA Technologies, Inc. VX900 PCI Express Root Port 2
00:03.3 PCI bridge: VIA Technologies, Inc. VX900 PCI Express Root Port 3
00:03.4 Host bridge: VIA Technologies, Inc. VX900 PCI Express Physical Layer Electrical Sub-block
00:0f.0 IDE interface: VIA Technologies, Inc. VX900 Serial ATA Controller
00:10.0 USB controller: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller (rev a0)
00:10.1 USB controller: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller (rev a0)
00:10.2 USB controller: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller (rev a0)
00:10.3 USB controller: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller (rev a0)
00:10.4 USB controller: VIA Technologies, Inc. USB 2.0 (rev 90)
00:11.0 ISA bridge: VIA Technologies, Inc. VX900 Bus Control and Power Management
00:11.7 Host bridge: VIA Technologies, Inc. VX8xx South-North Module Interface Control
00:13.0 PCI bridge: VIA Technologies, Inc. VX855/VX875/VX900 PCI to PCI Bridge
00:14.0 Audio device: VIA Technologies, Inc. VT8237A/VT8251 HDA Controller (rev 20)
05:00.0 Ethernet controller: Broadcom Limited NetLink BCM57780 Gigabit Ethernet PCIe (rev 01)
inxi
System:
Host: volumio Kernel: 5.10.79 x86_64 bits: 64 compiler: N/A Console: tty 1
dm: N/A Distro: Debian GNU/Linux 10 (buster)
Machine:
Type: Desktop System: Hewlett-Packard product: HP t510 Thin Client v: N/A
serial: Chassis: type: 3 serial:
Mobo: Hewlett-Packard model: 158Ch serial:
BIOS: American Megatrends v: 786R11 v1.05 date: 06/03/2013
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Touch Keyboard K400
serial: charge: Full status: Discharging
CPU:
Topology: Dual Core model: VIA Eden X2 U4200 1.0+ GHz bits: 64 type: MCP
arch: Isaiah rev: D L2 cache: 2048 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx bogomips: 4000
Speed: 1000 MHz min/max: 800/1000 MHz boost: disabled Core speeds (MHz):
1: 1000 2: 1000
Graphics:
Device-1: VIA VX900 Graphics [Chrome9 HD] driver: viafb v: kernel
bus ID: 00:01.0 chip ID: 1106:7122
Display: tty server: X.org 1.20.4 driver: fbdev unloaded: modesetting,vesa
alternate: openchrome tty: 80x30
Message: Unable to show advanced data. Required tool glxinfo missing.
Audio:
Device-1: VIA VT8237A/VT8251 HDA driver: snd_hda_intel v: kernel
bus ID: 00:14.0 chip ID: 1106:3288
Sound Server: ALSA v: k5.10.79
Network:
Device-1: Broadcom Limited NetLink BCM57780 Gigabit Ethernet PCIe
driver: N/A port: d480 bus ID: 05:00.0 chip ID: 14e4:1692
IF-ID-1: usb0 state: unknown speed: N/A duplex: N/A mac:
Drives:
Local Storage: total: 14.91 GiB used: 924.2 MiB (6.1%)
ID-1: /dev/sda model: 16GB SATA Flash Drive size: 14.91 GiB
speed: serial: rev: A01A scheme: GPT
Partition:
ID-1: / size: 11.02 GiB used: 41.4 MiB (0.4%) fs: overlay source: ERR-102
ID-2: /boot size: 170.8 MiB used: 60.1 MiB (35.2%) fs: vfat dev: /dev/sda1
Sensors:
Missing: Required tool sensors not installed. Check --recommends
Info:
Processes: 113 Uptime: 5m Memory: 3.73 GiB used: 370.5 MiB (9.7%)
Init: systemd v: 241 runlevel: 5 default: 2 Compilers: gcc: N/A
Shell: bash v: 5.0.3 running in: tty 1 inxi: 3.0.32
http://logs.volumio.org/volumio/XoMCXZn.html
Volumio-3.175-2021-12-13-x86_amd64
HP t510 terminal PC
Both audio and ethernet works fine on standard debian image (network with workaround or non-free image). In Volumio onboard ethernet doesnt work (doesnt show in ip link list), neither does audio (shows in alsamixer, but not pacmd list-cards, can’t play audio via aplay)
The Volumio OS is not quite standard Debian, as Volumio has its own way to boot the image.
We’re nowhere near the resources Debian has, so not all possible PC configurations may work But we’re close.
I will have a look at you logs and give my feedback.
Good to have your info.
Btw, what is pacmd supposed to mean for volumio?
Uff, had a look at the log, quite a limited PC with no soundcard we encountered so far. Network not supported either.
Any idea how old this hardware is?
btw. pacmd is not relevant to us, only alsa is.
Note, we support a wide range of PCs and notebooks, young and old.
But for a number of “undefined” thin clients, “undefined” hw versions of mac mini’s and more dedicated products, Volumio can’t guarantee that these will ever work completely.
I would like to, but can’t really help you in this case.
(But answer any questions you may have).
It does have a sound device of sorts though, we use it with mopidy as we speak 
It was launched in 2012 which, fair, is quite some time now… Heres an overview of the device HP Thin Client: t510
We had some of them laying around after hardware upgrades for someone, and theyre capable enough that we keep using them as single-use computers, like for playing music in this case
Ive seen syslinux showing as the image boots, so my first thought was to dig into the image and replace the kernel and modules with standard debian one and see what happens, but Ive seen you have a build system available in repos, but Im unsure if I can build the whole system and software package, or is parts of it only available through existing images?
I’ve tried pacmd because Ive seen you have pulseaudio in the image, but I guess you use ALSA as main audio system, and then PA as auxiliary thing for like, bluetooth output support then, do I get that right?
You said it runs standard Debian, would you be able to give me “dmesg” from it after booting and also it’s /boot/syslinux.cfg?
And perhaps output from “xrandr”?
You may also have to try adding “nomodeset” to Volumio’s kernel parameters (see /boot/syslinux.cfg) though I think we have VIA firmware missing, Broadcom Limited NetLink BCM57780 Gigabit Ethernet PCI we don’t have (yet) either.
Still checking…
You said it runs standard Debian, would you be able to give me “dmesg” from it after booting
Two dmesgs here: one thats on wired network but untested audio, and one thats our jukebox, that have usb wifi adapter
Machine with wired network:
Note this one is based on xanmod kernel, thats for ntfs3 module, but network works regardless of kernel used
Jukebox:
also it’s /boot/syslinux.cfg?
I’m using grub, but heres related part of grub.conf
grub.conf
menuentry ‘Debian GNU/Linux’ --class debian --class gnu-linux --class gnu --class os $menuentry_id_option ‘gnulinux-simple-66ff4370-183e-411e-9cbf-80bd25fb0727’ {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root=‘hd0,msdos1’
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 66ff4370-183e-411e-9cbf-80bd25fb0727
else
search --no-floppy --fs-uuid --set=root 66ff4370-183e-411e-9cbf-80bd25fb0727
fi
echo ‘Loading Linux 5.10.0-8-amd64 …’
linux /boot/vmlinuz-5.10.0-8-amd64 root=UUID=66ff4370-183e-411e-9cbf-80bd25fb0727 ro quiet
echo ‘Loading initial ramdisk …’
initrd /boot/initrd.img-5.10.0-8-amd64
}
And perhaps output from “xrandr”? You may also have to try adding “nomodeset” to Volumio’s kernel parameters (see /boot/syslinux.cfg)
Suprisingly, volumio boots with video output, feat that I had problems running pure debian, but nomodeset does indeed work
though I think we have VIA firmware missing, Broadcom Limited NetLink BCM57780 Gigabit Ethernet PCI we don’t have (yet) either.
Its part of the non-free install media, its probably somewhere in the repos too, I guess? The trick to getting this adapter to work is to load both “broadcom” and “tg3”, in this order.
Sorry I don’t have one of these machines that runs “vanilla” debian handy right now, but I can set up one later if its needed for testing!