Dear chsims1, dear gkkpch,
with regards to my mini PC with ALC5651 audio chip I sent extra email.
My machine: Mini PC AZW Z83 II 2GB RAM, 32GB eMMC HD, Quad-Core Atom x5-Z8350, Realtek ALC5651 audio chip, OS on eMMC.
My other, new, topics seems to be also x86-related:
Yesterday I updated my machine from 3.083 beta to 3.114 beta: Sound is ok, similar to what I already experienced with 3.083: sound only via headphone Jack and after the fresh installation the sound stops after a few seconds but after a shutdown from within Volumio and a restart with the PC knob, the audio output is fine!
WLAN doesnāt work (no change), but LAN does the job.
However, now, there seems to be a problem with my 1 TB SSD FAT32 (with about 500 GB of MP3 music) attached via external USB 3.0.
I tested in the evening and heard perhaps a dozens songs and everything seemed to be fine. Next day: music database broken, only few of the music subfolders left.
Re-reading of the database didnāt succeeded, after less then 1,000 artists, process ends with a non-reacting PC and I had to force restart.
That means for the moment: back to 3.083 beta (that worked quite good to me), I fear. Or to you think the changes from 3.111 to 3.114 made the problems?
Good, because the profile is there, but the log shows, the ALC898 is not initialised like we do for other ALC codecs. Simple fix to test, when OK, Iāll add it to the build.
Will post instructons here the next few days
Added to the todo list, not sure about audio though. Had reports that headphone/lineout was ok.
Your initial WiFi error (missing firmware) disappeared, have not checked whether WLAN hotspot was enabled
Iām wondering, could it be that the hyphen in [HD-Audio Generic] name is erroneously recognized as a special regex or jolly char and breaks the process of audio devices identification? Just a stupid ideaā¦
no, it is more likely that the āHDA-Audio Genericā was only configured once based on one particular configuration request.
With x86 it is not like a PI or Tinkerboard, there are soooo many different configurations we would need to take care off.
There will never be a guarantee from us, that we can take care of all of them.
Hi, I think I switched off WLAN ā¦
With regards to the USB HD/library problem: I switched back from 3.114 to 3.111 and, so far, it seems to work again ā¦ Setting up the library (=import of the mp3ās on the FAT32 1 TB SSD) wasnāt a problem at all. Apart from that, as written earlier, I needed to restart after the initial start of Volumio to avoid stuttering of sound. In this case, with 3.111, the sound stuttered, and even when I pressed āPauseā, playing went on after a small interruption ā¦ as with earlier versions, a restart helped.
Device: ThinkPad T430 - volumio PC version
Version: 3.114
Issue: I try to install volumio pc version on 320 GB hard-drive but it is going on error, on 160 GB hard-drive no problem, all ok.
Debug log link:
are there any limits on hard-drive capability ?
thanks nico
I will probably find a working solution, both cards will then show the same subdevices, as the cards have the same card name.
The first card only has HDMI support (probably on HDMI 0), Analog and SPDIF will be shown but wonāt work.
Similar story for the second one, it will have Analog out and SPDIF support, HDMI 0-3 will also be shown but wonāt work.
This is not ideal, but given the fact we have not seen such a rare config for the last 6 years, a complete redesign of soundcard parsing is not justified for one single user, hope you understand.
Once I have the output of the above commands I will make a suggestion for editing and testing.
When it is OK, it will be implemented in one of the next releases.
Thanks to you for taking care of such a rare issue. It is enough to have all the options available, duplicates donāt matter.
The first command returned an error, the second one never returned until I pressed Ctrl+C. Shall I wait longer?
volumio@volumioss:~$ aplay -c 0
aplay: main:608: value 0 for channels is invalid volumio@volumioss:~$ aplay -c 1
^CAborted by signal Interruptā¦
^C
volumio@volumioss:~$
Difficult to answer, it should not make any difference.
What I would need is a log from the failing 320GB trial.
I have seen an issue recently, not due to size, but due to failing to remove partitions (see Index at the top of this thread). A log would make that clear.
That would not stop the firmware being loaded properly and this seems to work ok.
The Z83 is a low performance mini pc, donāt expect miracles
During indexing of the library, stutter can occur while playing music in parallel.
Also, we know that after connecting an external drive, indexing sometime needs to be started manually by the update button in the āSourceā menu.
After all is finished (and a reboot), a Z83 should be OK though.
Iāll close this report unless something fails consistently, which I did not read from your text.
In case you open another one, please add a log, otherwise it is just guesswork, Iām not very good at that.
Also, one issue per report makes it a lot easier to handle.