X86 Hardware issues (Graphics, WiFi, Onboard Sound, external DACs, Disks, BIOS/UEFI Boot problems etc.)

No idea what a “DQ55” mainboard is, can you please be a little more precise.
Who is the manufacturer, how old is it, which hw components does it have.
Without more information no one will be able to help you.

Dear members! I would like to ask if the latest Volumio3 and plug-ins work on the ATOMIC PI sbc card? Maybe Peppymeter too? If so, I might try this card too, with my 1280x800 HDMI Touch display. If there is a problem, what is it typically? Thanks!

Peppy will not work as plugin, only as full manual install. See:

The processor is supported: Atom™ x5-Z8350
WiFi chip is supported: RT5572

But according to Atomic Pi “Eats RPi for dessert” seems a bit too positive, only valid for < rPi4

1 Like

@zoli76 With cherrytrail and baytrail devices, onboard audio it can be a hit or miss, you will have to try.
The ones with RT5640 and RT5672 audio codecs should be OK out-of-the-box, with RT5651 and ES8316 you may have to fiddle a bit as I have never been able to test them myself (lack of hw on my side). You may need forum help on that case, but no guarantee.

Edit: It seem the codec stuff does not apply to your board, you need to test it yourself.

1 Like

The thing is, it would be possible to buy an Atomic Pi for $26. What I would have tried out of curiosity: 1280x800 hdmi+usb waveshare touch monitor, Volumio3 and Peppymeter plugin, with themes. USB output directly to external DAC. In fact, it is the same as what now finally works on rpi4. I wouldn’t be interested in a motherboard analog audio output.

where you can get it for 26 bucks?

1 Like

It was offered by a friend. Only the sbc, original, new. The power supply is not included in the price, only the virgin panel. But I would only dare to buy it if I could turn it into a Volumio3 streamer with Peppymeter and my 1280x800 touch monitor. I would also use a USB output to the DAC. Maybe the ATOMIC PI would be more suitable for watching 4k video than the rpi4, so a KODI or something like that would also run better on it.

1 Like

you get them for a special offer at Ameridroid
click here for the Ameridroid offer
No idea what they charge for shipping

1 Like

i do, it made me cry…


I would also buy this 26 usd (+ 4 usd sshipping).offer if I knew I could make a working Volumio3 out of it…let’s say they write problems. 2 GB of RAM is not enough, Windows 10 does not work well, the wifi of the sbc is crap, it needs an antenna and a power supply. And only 1 usb3 port (of course you can solder in the 1 usb2 as well).

Don’t laugh at me, but I’m sorry that Atomic PI is not widespread. Then there could be a clear tutorial with which you can easily install what you need.
Or find someone using it with Volumio3…

2GB RAM is sufficient for Volumio.
Don’t use Windows as a reference, it uses WAY more resources than Linux does. It would most likely work, I have no big doubts about that, but it is an atom pc.
Somewhat snappier than a Pi (as @Wheaten mentioned, below a PI4), but known to be very stable on usb, not like the PIs in that range.

Look for a 2nd hand Dell Wyse 3040 on ebay, when you can score one below 40-50 dollars, you would be better off.
And that one has a case, your atomic pc is just a bare board.

1 Like

Hello friends!
Can you ask me a question? How to connect volumio (PC) to the TV screen and display the interface window like on mobile!
I connected via HDMI cable to the TV, but only the command interface (Dos) is displayed.
Thanks a lot!
Please see: Volumio 3 issues: hints and solutions before posting a new issue.
(You’ll need to cut and paste the link)

----------------------------- Delete here & above before posting below -----------------

What hardware are you using?

If a rPi, install the “touch display” plugin

I am using volumio on x86 computer

Then all you need to do is, go to:
System => Video Output Options =>

1 Like

@phungmac I know this is all a bit confusing, but the x86 image has HDMI enabled by default.
You can switch it, that is what the previous post is about.
In your case it looks more like a hw compatibility issue, the current version of Volumio for x86 is known to have issues with newer hardware, when not yet supported graphics cards are used.
Could you please submit a log to verify this?
This article shows how to do it

The other option is to install this version, it is brand new with the latest hw support and therefore not officially supported yet: Volumio-3.576-2023-11-10-x86
An official version should be released soon.

1 Like

Thank you for responding!

it is possible to add new entries to the Windows Bootmanager for example with the easybcd-tool. It was no problem to add an entry for the kde-neon-installation. It was just important to install the bootloader of that installation into the root-directory.

Why i want to use the Windows-Bootmanager is because i use two WIN 10 Installations on that System. One for a normal Windows with Fidelizer and another with Audiophile-Optimizer. When i use the Bootloader of KDE-Neon (GRUB i think) it will always detect the two Windows as One or in other words it detects the Windows Bootmanager. So after choosing WIN i have another Boot into that Bootloader and choose again and then sometimes one or two more Boots until i finally arrive.

This is why i tried to include the Linux into the WIN-Bootloader although i think the NEON-Loader looks better. And this works very fine for this first disk. Could i add Volumio into this Menu it would be the AUDIO-Machine of my dreams.

Is there anybody who ever tried to add Volumio to the Windows 10 Bootmanager?


Probably me to answer this one, this is a very tempting feature which went through my head many times.
It did not get done, not because we wouldn’t want to, but the problem is that the current Volumio install is based on an image flash and we miss the specialist ressources and skills Microsoft and Debian can make use of to create an installer.
In case someone has the skills and time to support us, please let us know.
Manual additions to the Windows bootmanager, Linux grub2 or Syslinux won’t survive a Volumio update.

1 Like

Thanks for your interesting answer. I am not much of a programmer and have to admit although i am fiddeling with linux-installations since 1998 i still do not really understand what i am doing when i copy and paste those terminal-commands that do the jobs.

I am totally convinced of Volumio after comparing it with other solutions. The sound is amazing.

When i understand the Windows-bootmanager correctly it works like this: in easybcd i add an entry to the menu and give the additional information to which kind of bootloader this entry leads. In the case of the kde-Neon it is a GRUB2-link.

When i saw a Syslinux-information in the volumio-bootup i thought ‘that’s it’ and added that in easybcd and directed the bootmanager to the bootpartition of the volumio-drive. But that didn’t work. Why? Isn’t there a bootloader installed in that 171mb-Partition? One that could be linked with my boot-manager?

When i reinstall Volumio on that second drive the bootmanger in the first drive is not affected. I tried that. So maybe it is possible to get Volumio integrated without too much fuss?

1 Like

You can experiment as much as you wish, google chainloading bootloaders, windows BCD and also refer to the syslinux wiki, there is some information which may help.
I prefer not to get involved in this as it has no real value for Volumio.
Just a warning: even when you get this working, there is a big chance that the system breaks as soon as you do your next Volumio update.
So you’re on your own with this, sorry.