Here are old and cheap USB2 and USB3 sticks on board as well - and they all are working well. Speed performance does vary a lot of course. The first boot sequence of a freshly flashed image is always taking a long time because volumio resizes the file system according to the size of the stick. Larger sticks take longer time. You have to be very patient though. This process can take several minutes!
If you already have an existing, running volumio system you can use it to log into it via puTTY (a terminal tool for M$) and perform the “dd” command I mentioned above. On M$ systems I recently hade better results in using “Rufus” rather than "BalenaEtcher ". May be this is worth an attempt?
True, an electron based app (400+ MB) for simple stuff is the classic “get stuff done, the hardware is powerful enough anyway”.
But in my books they killed it when they added non optional telemetry + sponsored content
@Robert.Hecht I bought a known brand Sandisk 32GB drive, and it worked immediately, and was really quick, so shonky flash drives may be a problem to watch out for, or I may have caused a problem trying to flash them on my other PC. I bought 2 of the Sandisks, so I will now try flashing this on my other PC.
I will now see how well Volumio v3 works on X86!
Got to the bottom of not being able to flash on my main PC - Windows Security (defender as was) I was getting Protected Memory Access Blocked messages. I had these messages:
So I clicked on the Actions button, then Allow on Device.
Also, clicking the Controlled Folder Access Settings link takes you to where the blockage can be unblocked by clicking on Allow an app through controlled folder access:
I’m running the Volumio 3.139 on a Z86 box (atom) and everything is running ok, except the analog audio input. I’d like to connect my turntable to the analog port.
It appears on the web interface as bytcr-rt5651 and I’m able to select the input but do not have any audio input.
Sorry for the confusion, I only read analog, not the “in” part
Audio in is only supported with a select group of devices.
bytcr-rt5651 should not have been shown, that is still a bug.
Same for usb audio in, this is not supported either.
Are you sure we are talking about the same thing? You want to use an M-Audio Fasttrack to feed a Volumio setup with audio?
Can you repeat the log for the M-Audio? Edit
Did you use mic-in on your intel atom box? If so, did you use amixer to enable and raise volume levels?
Hi
I have just installed Volumio 3 on my intel Nuc.
I cannot find spotify plug-in.
I only find spotify connect.
If I active it I can control my volumio device via spotify connect but I cannot edit the queue.
Can someone help me?
I made a few tests today. In the same box, I installed the Volumio 2.9 with a generic USB audio card and worked fine. Here is the logs: http://logs.volumio.org/volumio/XA5l7Om.html
I have a thumbdrive I was able to use to get volumio working on a Dell Wyse 5010 and it was great. I then ordered a 3040 in order to get lower power consumption (5W vs 15W). The v2 thumbdrive doesn’t work in the 3040 at all (doesn’t recognize any soundcard) so I downloaded the 3 beta and put it on a thumbdrive as well.
The GUI gives me the choice between cht-bsw-rt5672, HDMI0, HDMI1, HDMI2. So I selected the cht-bsw-rt5672 and when I try and play anything I see an error message like:
Failed to open "alsa" (alsa): Error opening ASLA device "volumio": snd_pcm_hw_params() failed: Invalid argument
I tried to upload the results of alsa-info but I guess I’m too new to be allowed to upload.
I’ve read the whole thread and found the volumio_hda_intel_tweak.sh and I was thinking about attempting that just to see if it would help but I’m not entirely sure what string I should include. It seems like a realtek 5672 but I’m not entirely sure. It’s not obvious to me how to map whatever strings are showing up in these various aplay/amixer commands to what you put in the tweak script.
sorry, we can’t help you without more info. No idea how a Dell 3040 is configurated. Please post the necessary information after reading the opening post.
Thanks for the info, you are the first one to report use of the realtek rt5670/ rt5672 codec which is obviously not fully supported yet. The amixer commands to setup routing are missing. I will try to fix that this week but need your help to test it.
This would not be the right place, it is a cherrytrail audio device, cherrytrail and baytrail audio devices are a bit special as they use Alsa UCM, which is still a bit WIP for Volumio. But we’re working on it, rt5670/72 are just 2 new puzzle pieces to put in place.
Edit
Please edit the cherrytrail/baytrail init script
sudo nano /usr/local/bin/bytcr_init.sh
replace string
bytcr-rt5640)
by
bytcr-rt5640 | cht-bsw-rt5672)
In case the above works, you could play with both speaker and headphone output, using the following commands
/usr/bin/alsaucm -c cht-bsw-rt5672 set _verb HiFi set _enadev Speaker
/usr/bin/alsaucm -c cht-bsw-rt5672 set _verb HiFi set _enadev Headphones
This fix in bytcr_init.sh is not complete for rt5672, but it should at least give you first output over speaker/headphone.
Automatic switching between headphones and speaker (=lineout) will be done in a next step
It needs additional changes in another script which currently works for rt5640, but needs an extension for rt5672.
I just gave that a try, with what might be called less than success:
volumio@shop:~$ /usr/bin/alsaucm -c cht-bsw-rt5672 set _verb HiFi set _enadev Headphones
ALSA lib utils.c:63:(uc_mgr_config_load) could not open configuration file /usr/share/alsa/ucm/cht-bsw-rt5672/cht-bsw-rt5672.conf
ALSA lib parser.c:1425:(load_master_config) error: could not parse configuration for card cht-bsw-rt5672
ALSA lib utils.c:63:(uc_mgr_config_load) could not open configuration file /usr/share/alsa/ucm/cht-bsw-rt5672/cht-bsw-rt5672.conf
ALSA lib parser.c:1425:(load_master_config) error: could not parse configuration for card cht-bsw-rt5672
ALSA lib main.c:946:(snd_use_case_mgr_open) error: failed to import cht-bsw-rt5672 use case configuration -2
/usr/bin/alsaucm: error failed to open sound card cht-bsw-rt5672: No such file or directory
volumio@shop:~$
Looking at your advice above I thought “hey maybe I can figure this out” and tried to make a few changes to bring that about. I don’t think it worked.
volumio@shop:/usr/share/alsa/ucm$ sudo cp -R chtrt5650 cht-bsw-rt5672
[sudo] password for volumio:
volumio@shop:/usr/share/alsa/ucm$ ls
ASUSTeKCOMPUTERINC.-T100HAN-1.0-T100HAN bytcr-rt5640-mono-spk-in1-mic bytcr-rt5651-stereo-spk-in12-mic DAISY-I2S PandaBoardES
broadwell-rt286 bytcr-rt5640-mono-spk-in3-mic bytcr-rt5651-stereo-spk-in1-mic DB410c PAZ00
broxton-rt298 bytcr-rt5640-stereo-spk-dmic1-mic bytcr-rt5651-stereo-spk-in2-mic Dell-WD15-Dock PIPO-W2S-Defaultstring-CherryTrailCR
bytcht-es8316 bytcr-rt5640-stereo-spk-in1-mic cht-bsw-rt5672 GoogleNyan platforms
bytcht-es8316-mono-spk-in1-mic bytcr-rt5640-stereo-spk-in3-mic chtnau8824 gpd-win-pocket-rt5645 SDP4430
bytcht-es8316-mono-spk-in2-mic bytcr-rt5651 chtrt5645 HDAudio-Gigabyte-ALC1220DualCodecs skylake-rt286
bytcht-es8316-stereo-spk-in1-mic bytcr-rt5651-mono-spk-in1-mic chtrt5645-mono-speaker-analog-mic HDAudio-Lenovo-DualCodecs TECLAST-X80Pro-Defaultstring-CherryTrailCR
bytcht-es8316-stereo-spk-in2-mic bytcr-rt5651-mono-spk-in2-mic chtrt5650 kblrt5660 tegraalc5632
bytcr-rt5640 bytcr-rt5651-mono-spk-in2-mic-hp-swapped codecs LENOVO-80XF-LenovoMIIX320_10ICR-LNVNB161216 VEYRON-I2S
bytcr-rt5640-mono-spk-dmic1-mic bytcr-rt5651-stereo-spk-dmic-mic cube-i1_TF-Defaultstring-CherryTrailCR PandaBoard
volumio@shop:/usr/share/alsa/ucm$ cd cht-bsw-rt5672/
volumio@shop:/usr/share/alsa/ucm/cht-bsw-rt5672$ ls
chtrt5650.conf HiFi.conf
volumio@shop:/usr/share/alsa/ucm/cht-bsw-rt5672$ sudo cp chtrt5650.conf cht-bsw-rt5672.conf
volumio@shop:/usr/share/alsa/ucm/cht-bsw-rt5672$ /usr/bin/alsaucm -c cht-bsw-rt5672 set _verb HiFi set _enadev Headphones
ALSA lib main.c:432:(execute_sequence) unable to open ctl device 'hw:chtrt5650'
ALSA lib main.c:1712:(set_verb_user) error: failed to initialize new use case: HiFi
/usr/bin/alsaucm: error failed to set _verb=HiFi: No such device
volumio@shop:/usr/share/alsa/ucm/cht-bsw-rt5672$ sudo vim cht-bsw-rt5672.conf
volumio@shop:/usr/share/alsa/ucm/cht-bsw-rt5672$ /usr/bin/alsaucm -c cht-bsw-rt5672 set _verb HiFi set _enadev Headphones
ALSA lib main.c:432:(execute_sequence) unable to open ctl device 'hw:chtrt5650'
ALSA lib main.c:1712:(set_verb_user) error: failed to initialize new use case: HiFi
/usr/bin/alsaucm: error failed to set _verb=HiFi: No such device
volumio@shop:/usr/share/alsa/ucm/cht-bsw-rt5672$ sed -i 's/hw:chtrt5650/hw:cht-bsw-rt5672/g' HiFi.conf
sed: couldn't open temporary file ./sedqK4IvC: Permission denied
volumio@shop:/usr/share/alsa/ucm/cht-bsw-rt5672$ sudo sed -i 's/hw:chtrt5650/hw:cht-bsw-rt5672/g' HiFi.conf
volumio@shop:/usr/share/alsa/ucm/cht-bsw-rt5672$ /usr/bin/alsaucm -c cht-bsw-rt5672 set _verb HiFi set _enadev Headphones
ALSA lib main.c:432:(execute_sequence) unable to open ctl device 'hw:cht-bsw-rt5672'
ALSA lib main.c:1712:(set_verb_user) error: failed to initialize new use case: HiFi
/usr/bin/alsaucm: error failed to set _verb=HiFi: No such device
volumio@shop:/usr/share/alsa/ucm/cht-bsw-rt5672$
I didn’t really expect that whole approach would necessarily work but I’m also not seeing anything that looks like a clue that I can tune in to. I feel like I’ve hit a brick wall of not understanding.
Then I went looking for what the hardware might be more properly called, and also struck out:
volumio@shop:/dev/snd/by-path$ ls -l
total 0
lrwxrwxrwx 1 root root 12 Nov 22 21:03 pci-0000:00:02.0-platform-hdmi-lpe-audio -> ../controlC1
lrwxrwxrwx 1 root root 12 Nov 22 21:03 platform-cht-bsw-rt5672 -> ../controlC0
volumio@shop:/dev/snd/by-path$ sudo sed -i 's/hw:cht-bsw-rt5672/hw:platform-cht-bsw-rt5672/g' /usr/share/alsa/ucm/cht-bsw-rt5672/HiFi.conf
volumio@shop:/dev/snd/by-path$ /usr/bin/alsaucm -c cht-bsw-rt5672 set _verb HiFi set _enadev Headphones
ALSA lib main.c:432:(execute_sequence) unable to open ctl device 'hw:platform-cht-bsw-rt5672'
ALSA lib main.c:1712:(set_verb_user) error: failed to initialize new use case: HiFi
/usr/bin/alsaucm: error failed to set _verb=HiFi: No such device
volumio@shop:/dev/snd/by-path$