Jump to content
IGNORED

AudioLinux and NUC Troubleshooting and Tuning


rickca
Message added by austinpop

Summary of useful findings and recommendations

 

This section will be a living repository of useful info from this thread. It's very similar to a wiki and will be maintained by a small group of thread moderators.

 

Before you get started please refer to the Audio-Linux website to ensure you have the latest info and the proper versions of the OS. Audio-Linux.com  

 

**** Updated for AL 1.30 menu 118 or later.

 

  "First Run" setup for headless.  

 

Setup your NUC with a keyboard, mouse, and monitor to the NUC BIOS settings.  From the menu note the IP address of the machine to SSH into.  From a MAC the macOS terminal program supports SSH:

324537708_ScreenShot2019-01-28at3_02_19PM.thumb.png.739dc7f9cdb05e04da806c7c66877332.png

 

Then it is simpler to cut and paste into the terminal session. After entering the password for the audiolinuxuser you will be presented with the AL headless menu:

 

1518375894_ScreenShot2019-01-28at3_04_18PM.thumb.png.a7b2867a163f8f014e56e52ff69f94b4.png

 

Option 8 takes you to the command line for the following basic setup.  You will need to be the Root user for this setup and the su command first:

 

su

 

Fix the time zone:  (this is my timezone - look in directory /usr/share/zoneinfo)

 

timedatectl set-timezone America/Chicago
 

Setup and Start NTP daemon (to keep the system time in sync)

 

*** the config file is now properly filled in.

 

Now Start the daemon

 

timedatectl set-ntp true

 

 

NOTE: Sometimes the system takes a little while to get synced up.
 

Set hostname  (this provides a unique name for the machine on your network.  Replace <NAME> with your chosen name)

 

hostnamectl set-hostname <NAME> 
 

Once the above items are set up your machine is ready to be configured for say a Roon bridge/endpoint. That is done using the AL menu.  To return to the menu do the following commands.

 

exit

menu

 

----------------------------------

 

For most of us, the following basic settings are key.

From the configuration menu:

6. START and enable Roonbridge

15. SET Realtime Priority to extreme

16. ENABLE ramroot (reboot after)

 

Return to the main menu and reboot the NUC using 

 

11 Reboot

 

------------------

Roon Server setup is a bit more complex and we will cover it completely a bit later.  The key is where you are booting from and where the Roon database is stored.  In general; say a 32gb OPTANE "SSD".

 

  • You have to partition the SSD into a boot drive and a storage drive.  
  • The transfer the USB stick install to the boot partition.  
  • Reboot from the boot partition.  
  • Do the basic setup. Timezone and name
  • Transfer the Roon Database to the storage drive
  • Start the Roon Server
  • .....

 

----------------- 

The machine will reboot and from the display attached to the NUC you can watch it boot up and load into RAM.  Once the AudioLinux menu is showing the endpoint should be available in Roon.    This completes the basic startup sequence.  The system is ready to start testing.    

 

 

Recommended Posts

3 hours ago, Dutch said:

@hifi25nl,

 

Some questions after reading: http://www.audio-linux.com/html/realtime.html

 

I’m running just Roon Bridge on my AL headless (0.6) NUC (it’s the endpoint) and I’m seeing these related processes :

 

root       544     1  0 17:41 ?        00:00:00 /bin/sh /opt/RoonBridge/start.sh

root       549   544  0 17:41 ?        00:00:01 RoonBridge --debug --gc=sgen --server RoonBridge.exe

root       590   549  0 17:41 ?        00:00:10 RoonBridgeHelper --debug --gc=sgen --server RoonBridgeHelper.exe

root       595   549  0 17:41 ?        00:00:00 /opt/RoonBridge/Bridge/processreaper 590

root       601   549  0 17:41 ?        00:00:39 RAATServer --debug --gc=sgen --server RAATServer.exe

 

In the rtapp.conf file (below) I see RoonBridge is listed but not RoonBridgeHelper or RAATServer. Since these have used more CPU time, would it be beneficial if I/we added those processes to the applications list?

 

Also I see —debug in the process list? Is that necessary or better said would it be ‘leaner and meaner’ to not use those switches?

 

Thanks in advance. If you’d like me to email you instead please tell me. It’s just that I though this might be beneficial to other users as well. :)

audiolinux@audiolinux ~]$ more /etc/rtapp/rtapp.conf

APPLICATIONS="jackd mpd hqplayer hqplayerd RoonAppliance RoonBridge mediacenter24 networkaudiod deadbeef a2jmidid ardour-5.12.0 rosegarden audacity"

 

MAX_PRIORITY="93"

 

MODE="autodec"

 

For closed source application with multiple threads is sometime difficult to understand what thread must have higher priority of another thread.

 

With "autodec" mode a running  application will have an higher priority than the one following it in the list. 

You can experiment with this, I am curious if you can find differences. The configuration file is there to be tweaked for the better sound.

 

Remember that MAX_PRIORITY must be lower than dac irq priority in /etc/rtirq.conf

AudioLinux --> https://www.audio-linux.com

developer of AudioLinux realtime OS

Link to comment

 

 

If you want to format a drive in headless, you must use parted.

I understand that this can be challenging for most people.

---> I suggest to make a USB stick with audiolinux and use gparted (an application with GUI). Very easy to use.

 

Please don't format in NTFS, if you can. Ext4 is a lot better for many reasons (no defrag, more solid in case of power failures, etc.)

AudioLinux --> https://www.audio-linux.com

developer of AudioLinux realtime OS

Link to comment

The 3 realtime tests (as root. you can use more cycles than 10000 if you want)

 

1) cyclictest -q -l 10000 -m -Sp98 -i100 -d0

 

2) hackbench -l 10000 &>/dev/null && cyclictest -q -l 10000 -m -Sp98 -i100 -d0

 

3) hwlatdetect --duration=60 --threshold=15

 

The first 2 are executed if you type

rttest

 

AudioLinux --> https://www.audio-linux.com

developer of AudioLinux realtime OS

Link to comment

A revision log would take some work... For kernel and packages, you can see the linux kernel release notes and the developer sites.

For manual changes I have made myself, there are the new menus options, time sync at boot and some minor changes.

 

The system is now completely upgradable from inside (menus, kernel, packages).

The sound configuration is the same as the previous versions, so people with a working system don't need to reinstall. Audiolinux is a "rolling release", you can update it continuously.

 

@Middy, for commercial questions, please contact me at the support email address.

AudioLinux --> https://www.audio-linux.com

developer of AudioLinux realtime OS

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...