DietPi: creating a lean-and-mean Roon Bridge

Thanks. Everything working flawlessly. The only issue I’m still having is using the Edimax EW-7811UAC. Maybe driver needs to be installed?

Yep, possibly, which device is it?

lsusb
lsmod

ID 7392:a812 ??

1 Like

Does it show up with aplay -l

  1. Tried to use DietPi with Odroid C2. Installation went smooth but I couldn’t upgrade kernel or ALSA for native DSD playback. That’s why I switched to Debian

  2. Now I’m thinking about using my spare Cubox pro for multichannel setup. Maybe someone managed to achieve this?
    My goal is to:
    A) cubox running DietPi
    B) connect Cubox to Marantz NR1607 via HDMI
    C) output my 5.1 FLAC collection thanks to new Roon 1.3

For now I can only output 2.0 sound.
Any thoughts?

Hi,

DietPi currently has one forked Kernel (RPi). With this fork, we can patch and resolve kernel issues for our RPi users.

The Odroid’s use stock Kernel at the moment (they are extremely outdated, but proven stable to a degree, 3.x). Provided by Hardkernel and updated through Meveric’s repository.

A) cubox running DietPi

Unfortunately, we do not offer a Cubox DietPi image at the moment, due to lack of physical device for implementation (cost).

Thanks, thats the puppy :slight_smile:

Lemme take a look, ticket below:

1 Like

@brian

Thanks for your feedback Brian, great to hear :slight_smile:

For Edimax in question you will have to manually install drivers on Debian.

wget https://dl.dropboxusercontent.com/u/80256631/install-wifi.tar.gz
tar xzf install-wifi.tar.gz

To install use: ./install-wifi

Tried, doesn’t seem to work…

root@DietPi:~# wget https://dl.dropboxusercontent.com/u/80256631/install-wifi.tar.gz
–2017-02-12 22:58:48-- https://dl.dropboxusercontent.com/u/80256631/install-wifi.tar.gz
Resolving dl.dropboxusercontent.com (dl.dropboxusercontent.com)… 45.58.70.5
Connecting to dl.dropboxusercontent.com (dl.dropboxusercontent.com)|45.58.70.5|:443… connected.
HTTP request sent, awaiting response… 200 OK
Length: 3656 (3.6K) [application/octet-stream]
Saving to: ‘install-wifi.tar.gz’

install-wifi.tar.gz 100%[=====================>] 3.57K --.-KB/s in 0s

2017-02-12 22:58:48 (9.59 MB/s) - ‘install-wifi.tar.gz’ saved [3656/3656]

root@DietPi:~# tar xzf install-wifi.tar.gz
root@DietPi:~# ./install-wifi

Your current kernel revision = 4.4.30-sc1+
Your current kernel build = #1

Checking for a wifi module to determine the driver to install.

Your wifi module is Bus 001 Device 004: ID 7392:a812 Edimax Technology Co., Ltd

And it uses the 8812au driver.

Checking for a new 8812au wifi driver module for your current kernel.
A driver does not yet exist for this update.
root@DietPi:~#

Hi Dan,

First I just want to Thank You, for Diet-Pi.!!!

Its a fantastic achievement in Computer Audio.

I use it and love it, I want to ask if there is a way to make the Nice and Affinity settings persistent between boots?

1 Like

Linux has many different varieties. And guys over there are trying to include as many as possible.
It is working on my 4.4.38, so maybe update your Kernel first?

pi@Bathroom:~ $ cat /etc/*-release
PRETTY_NAME=“Raspbian GNU/Linux 8 (jessie)”
NAME=“Raspbian GNU/Linux”
VERSION_ID=“8”
VERSION=“8 (jessie)”
ID=raspbian
ID_LIKE=debian
HOME_URL=“http://www.raspbian.org/
SUPPORT_URL=“http://www.raspbian.org/RaspbianForums
BUG_REPORT_URL=“http://www.raspbian.org/RaspbianBugs

pi@Bathroom:~ $ uname -r
4.4.38-v7+

Hi Edward,

If you are using dietpi-process_tool (http://dietpi.com/phpbb/viewtopic.php?f=8&t=5&start=30#p279) to apply those settings, they should be applied automatically during each boot.
If this is not the case, please send me a bug report, this will enable me to check your system setup and help with debugging:
http://dietpi.com/phpbb/viewtopic.php?f=8&t=499#p2184

As well as boot, dietpi-process_tool is also triggered when restarting all services:

dietpi-services restart

I quite fancy dipping my toes into Diet Pi but i don’t know my Linux from my elbow! I have an Audioquest Dragonfly Red USB DAC and plan on getting a RPi3 to stick it in to for this project (I already have a Pi/dac+ pro up and running in Roon with the hifiberry bridge). Am I safe in assuming that Diet Pi will work ok with the Pi/DF combination? Will additional configuration steps be required to get it up and running? Thanks, Rob

@rbm @Dan_Knight Do you folks recommend shutting down a DietPi setup when not actively in use, or do you advocate leaving it powered up 24/7. In my setup I can easily do either. Advantages/disadvantages to either?

I’m loving the DietPi setup running RoonBridge using a Meridian Explorer2 USB DAC. Glad I took the plunge. More stuff coming to build more. Thanks @Dan_Knight for making this easy for an idiot to master. :slight_smile:

1 Like

OK thank you

1 Like

Hi Rob,

You’ll need to select USB DAC as your soundcard. Once plugged in, this can be completed in:
dietpi-config > Audio Options > Sound Card > USB DAC

Aside from that, USB DAC should run fine :slight_smile:

Roon Bridge can be installed via dietpi-software:
http://dietpi.com/phpbb/viewtopic.php?f=8&t=5#p5

Getting started with DietPi guide:
http://dietpi.com/phpbb/viewtopic.php?f=8&t=9#p9

I did this with an Oppo HA-2 portable DAC - great little combo by the way - have yet to test with DSD

I leave my Pi’s on all the time.

Personally, there is no harm or disadvantages in leaving the device powered 24/7. As Roon Bridge uses very little CPU, there is hardly any CPU processing (heat) and power usage.
I have a dedicated RPi 2 setup with Roon Bridge and OMPD, runs 24/7.

RPi’s are extremely stable, minus any power cuts, I doubt you’d ever have to power cycle it.

If we want to dig a little deeper:
Powering down a device, allowing all the components to cool (contract), then powering up again and allowing the components to heat up again (expand). Will probably do more damage, than leaving it on running at a constant temperature.

Thank you Dan, I’ll do the reading and give it a go. I am greatful to you for your assistance.
Cheers, Rob