Compatible x86 machines

Please give us a short feedback on which x86 machine you are successfully running Volumio 2, supply at least:

  • Brand (of your Notebook/Macbook, PC/ Mac or motherboard)
  • Model
  • Chipset
  • Running from local hdd or bootable usb device?
  • Confirmed image version
    and any other info you might think useful.

Brand: Asus
Model: Notebook N550J
Booting from: hdd and usb
Confirmed image version: 2.129

Booting UEFI and Legacy BIOS

Brand: Intel
Model: NUC D34010WYK
Booting from: ssd and usb
Confirmed image version: 2.129

Booting UEFI and Legacy BIOS

Brand: HP
Model: Notebook Pavilion dv6
Booting from: hdd and usb
Intel Pentium B940 TJ85 2.00-GHz processor (2.0-MB
L3 cache, dual core, 35 W
Confirmed image version: 2.129

Booting Legacy BIOS only

1 Like

Brand: Zotac
Model: Nanobox AD10
Booting from: USB stick.

Brand: Medion
Model: Akoya 1210e
Booting from: usb
Intel Atom N270
1Go ram

Brand: HP
Model: Pavilion dm1
Booting from: usb
AMD E-350
3Go ram

  • ASUS
  • EeePC 1005HA (Seashell)
  • Intel Atom N270 1.6GHz, 1GB RAM, 160GB HDD
  • bootable usb device
  • Confirmed image version: Volumio 2.129

Brand: my own building machine
Motherboard Model: GA-Z68XP-UD4
CPU: Intel® Core™ i7-2600K CPU @ 3.40GHz
Booting from: hdd and usb
Confirmed image version: 2.129

Booting Legacy BIOS only

1 Like

Brand: VirtualBox 5.1.18
Motherboard Model: GA-Z68XP-UD4
CPU: Intel® Core™ i7-2600K CPU @ 3.40GHz
Booting from: locally built X86 image .vmdk
Confirmed image version: newer than 2.129

1 Like
  • VirtualBox 5.1.28
  • Debian 64 bit default VM settings
  • Confirmed image version: Volumio 2.285 (converted into .vdi as per below, and attached as virtual drive)

Note: release .img file converted with: VBoxManage convertfromraw --format VDI [filename].img [filename].vdi

  • Apple
  • MacBook Pro 13" Mid-2010 (MacBookPro7,1)
  • Intel Core 2 Duo (Penryn P8600) @ 2,4GHz, NVIDIA GeForce 320M, wifi BCM4322 rev 01 (14e4:432b)
  • bootable usb device
  • Confirmed image version: Volumio 2.129 (Ethernet only for now)

Note: tried to install missing bcm firmware package with firmware-b43-installer, but was not sufficient to get wifi operation. Actually this chipset would require Broadcom wl driver instead (from bcmwl-kernel-source or through broadcom-sta-dkms or broadcom-sta-source) which I could not build on used kernel.

I have Volumio installed and working on a USB flash drive pluggged into a Dell laptop.

Latitude D530
Intel Core 2 Duo

Biggest problem was getting Volumio to access the internet through my laptop’s wireless card. From a terminal I entered lspci -vnn -d 14e4: The results are below.

0c:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] (rev 01)
Subsystem: Dell Wireless 1395 WLAN Mini-Card [1028:000b]
Flags: bus master, fast devsel, latency 0, IRQ 17
Memory at fe8fc000 (64-bit, non-prefetchable) [size=16K]
Kernel driver in use: b43-pci-bridge

The two files I downloaded are b43-fwcutter_018-2_i386.deb and broadcom-wl-5.100.138.tar.bz2. Put them in a folder named offline_firmware-b43-installer. From my working Linux distro on my HDD put that folder into /volumio_data/dyn/home in Volumio on the flash drive. Then booted into Volumio and brought up a command line. Then the following.

cd into offline_firmware-b43-installer
sudo dpkg -i b43-fwcutter_018-2_i386.deb
tar xvjf broadcom-wl-5.100.138.tar.bz2
cd offline_firmware-b43-installer/broadcom-wl-5.100.138/linux
sudo b43-fwcutter -w /lib/firmware wl_apsta.o
sudo chmod 755 /lib/firmware/b43

Reboot Volumio. Volumio should start wireless internet. I went into Network on the Volumio menu and there was a list of available networks. Chose mine, entered my password and was connected. I’m not an expert on this, obviously, so I hope my instructions make sense.

Hi, thanks for sharing this info!

Brand: PC Engines
Model: ALIX APU.1D4
Running from: local M.2 SSD
Confirmed image version: some 2.x up to at least “volumio-2.201-2017-06-14-x86.img”
LAN: 3x Ethernet 10/100/1000
WLAN: mini-PCI addon card / Atheros AR9280 chipset

Tech Details:

Works perfectly as headless streamer, also in combination with compatible wireless LAN mini-PCI adapter. Console output (RS232) only. Flash Volumio image to SSD in another device (i.e. Laptop) or use distribution with output to serial console.

Playback from USB device / HDD is also possible & stable.

Prebuilt bundles in aluminum casing and including SSD are available through ebay.

Thread index like in the USB DAC thread maybe? At least for the pre-built machines with model number?

Thanks for your details in your post @macmpi !
I converted the current X86 Image (VERSION: 2.368) with

VBoxManage convertfromraw --format VDI volumio-2.368-2018-02-18-x86.img volumio-2.368-2018-02-18-x86.vdi

Using VirtualBox 5.2.8, created a Debian 64 bit VM without changes, chose the VDI as disc and just booted.
Afterwards stopped the VM and changed the network to “bridged mode” so i can reach volumio.local in my local webbrowser.

  • Brand ASUS
  • Model EB1007 (2011)
  • Chipset RAM 2 GB, HD 160 GB, Intel® Atom™ D410, Chipset Intel® NM10
  • Running both from local hdd and bootable usb device
  • Confirmed image version 2.368
  • Booting from Legacy BIOS
  • Brand: IDOT
  • Model: IDOT ID-PCM7E PC2500 V1.0C
  • Chipset: VIA C7-D Esther 1.5GHz / VIA CN700 / VIA VT8237R Plus
  • Running from: bootable USB flash drive
  • Confirmed image version: 2.284 (3.18.25 kernel); 2.411 (4.16.0 kernel)
  • Brand: PaceBlade
  • Model: SlimBook 110
  • Chipset:
  • Running from: hdd
  • Confirmed image version: 2.387; 2.411

The touchscreen does’nt work :frowning:


- Brand Panasonic
- Model CF-U1 Mk1+ docking
- Chipset atom processor
- Running from local 16Gb SDD or bootable usb device
- image version 2.411
- sound system USB DAC Xmos (or internal sound “HDA intel MID” card that sound correct) + DIY class D amp + vintage FOCAL speaker

i use a lubuntu USB stick made with linux live usb creator + persistence mode + etcher, to write the image on CF-U1 SSD.
go to the BIOS and choose the device to boot

compatibility issue :
touch screen is not working near the border