Volumio Version:2.853 PC (X86/X64)
Hardware: Minix Z64 with Intel Z3735F Processor, Realtek RTL8723BS Wifi and eMMC.
DAC: Dragonfly Red
Hi Team,
Yesterday i tried to use Volumio on my Minix Z64. The USB boot was successful. But i could not get the wifi to work and also could see that the eMMC was also not detected.
I had read through some other posts regarding the RTL8723BS and eMMC, i thought that it was supported now. Maybe i have misunderstood.
Could you please let me know if there is any way I will be able to make the volumio detect the eMMC and install it to the eMMC. Also is there any way to make the wifi working.
It would really help a lot if volumio could boot from my eMMC and work using the wifi.
In the current version these devices are and will not be supported due to an old kernel and corresponding firmware.
My suggestion is to use the x86 buster pre-version as discussed in Volumio Development/ Development talks, that version is fully functional and should cover more newer hardware configurations, incl. support for a wider range of wifi chips, emmc, nvme etc.
An official beta, followed by a release is expected soon.
The latest x86 buster image 2.857 did solve the eMMC install issue. So now i have successfully installed to my disk.
But I am not able to get the wifi up and running. I have been trying for some time on different suggestions in the posts. but no success yet. I get an error on hostapd.service stating
“Could not read interface wlan0 flags: No such device”
I can see that the RTL8723BE drivers are present in the rtlwifi path in libraries. Is it possible to fix this issue.
You would have to run a log from the dev page, this may give us more info.
(http://“your ip”/dev)
Post the url it returns.
Something confuses me, in the OP you mention RTL8723BS.
In the previous post you say RTL8723BE
You have to decide which one it is BE or BS?
They are not the same, BS would be an issue.
sorry, live log does not help (my fault, should have been more clear)
Could you please do the other one instead?
It will show the log since booting the device with a few other things.
On a side note, i have observed that the latest debian buster image does not show any plugins in search screen. I ran the below and got the results successfully.
Also i think there is an issue with the Airplay service. I cannot see the volumio as airplay device. When i run the systemctl status shairport-sync.service i get the below. But the Sharepoint-Sync under the Sources settings is enabled and green. Please let me know if i should report each as individual bugs
Dec 25 21:14:55 volumio systemd[1]: Started Shairport Sync - AirPlay Audio Receiver.
Dec 25 21:14:55 volumio systemd[9170]: shairport-sync.service: Failed to execute command: No such file or directory
Dec 25 21:14:55 volumio systemd[9170]: shairport-sync.service: Failed at step EXEC spawning /usr/local/bin/shairport-sync: No such file or directory
Dec 25 21:14:55 volumio systemd[1]: shairport-sync.service: Main process exited, code=exited, status=203/EXEC
Dec 25 21:14:55 volumio systemd[1]: shairport-sync.service: Failed with result ‘exit-code’.
why can’t you just do a simple readable volumio log instead of your own logs and suggestions.
Please do the log on the dev page and post the url you get.
Thanks.
I do not see, at any point, an attempt to initialize the RTL8723BS hw interface.
No driver load and no attempt to load 8723bs firmware.
Could you run this for me (ctrl-alt F1 will give you a terminal, with volumio/volumio to input for uid/pwd):
Thanks, this shows no onboard rtl8723bs device was detected, meaning there is nothing else I can do to help.
You may have to try a usb dongle to get wifi.
your eth0 connection should work, it is initialized and gets an ip address.
Airplay only works when you have a LAN connection, be it wireless or wired eth0.
interesting, i’ll have another look at the kernel configuration and make sure everything related to sdio is enabled.
As for airplay, yes please post this in the Volumio Development/ Development talks’ X86 buster thread.
We are pushing buster, so it is important not to forget this issue.