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

Getting setup for NUC testing.  I have the NUC7i7DNBE  board on order from SimplyNUC (I hope) and the Asaka X7D is also ordered. I have the license for AL... I wanted to ask about RAM for Headless endpoint. I have not ordered it yet. I have seen a couple of references to 4GB and some that say 16Gb.  I am slightly confused.  I also need some USB sticks just to be safe.  32gb overkill?

 

The plan is to test A/B with my UltraRendu.  I will be using my JS-2 Power supply and if I need I have an LPS-1.2.  

 

This feels like we need an AL/NUC Wiki???  I can try to host one if we need.

Link to comment
1 hour ago, austinpop said:

 

Bob,

 

Here's the rationale about RAM:

  • More memory consumes more power
    • more noise
    • more demand from PSU
  • Roon Bridge seems to run fine on just 4GB RAM, even with AL booted into RAM
  • I use 8GB, because it enables me to experiment with up to 4GB of buffer space for squeezelite
  • I see no reason to go beyond 8GB for an endpoint for now.

As for USB sticks, yes definitely get a few spares. I have had good luck with these: https://www.amazon.com/SanDisk-Ultra-Flair-Flash-Drive/dp/B015CH1JIW

 

I look forward to your findings! Please post your listening impressions comparing with the UR over on the novel thread.

 

Rajiv,

Thanks for the info.  I am finishing up my Amazon order now. 

 

I will report over on the SQ thread.  I am excited about this.  

 

Bob

Link to comment

I have a NUC7i7BNH that was a ROON ROCK server at one point it is now on Windows 10.  I am going to use it to build up my AL setup and test the basics.  Should help me fill the space while waiting for my NUC/Endpoint hardware to arrive.

 

I will also use it as a AL ROON server testBED.

 

Updating BIOS and Windows now....

Link to comment

In this crazy update mode, we are in personal version control is hard.  I have only made a couple of small changes and I am keeping a "log" in an Apple Note.  I was thinking about moving to Evernote to share stuff with others.  When I get my new NUC I will have to add BIOS change log to that.

 

I am still thinking of a WIKI.  I will go over to my A2 hosting panel and see what I can install quickly.

 

 

 

Link to comment
  • 2 weeks later...
1 hour ago, austinpop said:

I was helping out @bobfa to get his Roon Server to boot off of an Optane NVMe SSD. Since he was able to get it done succesdfully, the side benefit are my notes, which resulted in a HOW-TO Guide, included below.

I am looking into having two NUC machines running Audio Linux in my system, server, and a network bridge.  Both are running Roon software.

 

Rajiv sent me his document to kick off my idea of taking my NUC network bridge and turning it into a Music server.  It did not sound like it would be hard just challenging as I am not fluent in Linux.    First I had to upgrade the NUC with an Optane Stick.

 

 

IMG_0845.thumb.jpeg.704a4066b8218e5d33f48eb312c2da4d.jpeg

 

I purchased a 32Gb stick to install in the Akasa NUC

 

IMG_0846.thumb.jpeg.2052f3937fc23da3a154d8e798f3e9fd.jpeg

 

As I showed in the initial build, there are four screws to take the top off of the case.  The NUC7i7DNBE has two M.2 slots.  The one closest to the board is for the Intel WiFi/Bluetooth radio card.  The slot that is further away is the 80mm long slot for PCIE NVME SSD, and it is Optane ready.  There is a small screw that holds down the end of the card.  Make sure to use proper anti-static precautions here.  Remove that little screw.

 

IMG_0848.thumb.jpeg.ca6a3102cce23472ad54059ad6cf7866.jpeg

 

The plug the card into the M.2 slot and replace the screw holding down the M.2 card.

 

IMG_0849.thumb.jpeg.0f483fcfb4f0aed9f0fbf63380a37019.jpeg

 

Here is the overall picture of the inside of the case with the Optane card installed.

 

IMG_0850.thumb.jpeg.d079aecc7c5ffec98d6da92853ccab52.jpeg

 

I the BIOS I had to turn that M.2 slot back on.

IMG_0851.thumb.jpeg.c8442dedcbc913abdeffc62cabba8672.jpeg

 

Notice that the BIOS shows that there is a card in the slot.  Just check the box shown and save the BIOS and exit.

 

 

It took me some time to work through the process that @austinpop provided.  I had to relearn some stuff and LEARN some more stuff.  The drive and partition ID scheme is Linux is a bit different that MacOS and Windows.  I made a couple of typing mistakes and had to redo a couple of steps!  I had a couple of stumbling blocks, but we worked those out.  Oh and one email to @hifi25nl when I got desperate, but Rajiv had already solved it!

 

The NUC is setup on my test bench and connected to the network along with a keyboard and display.  I did most of the work on my 27in screen iMac so that I could have the document and a shell into the NUC side by side.  I found that the nano editor works fine for me but it was not working right in Termius so I just opened the Unix Terminal on the Mac and SSHed into the NUC.  

 

I have my music library stored in three places for "safety." My Sonic Transporter has it stored internally, and it is on my QNAP NAS.   I setup Roon on the NUC server to access the library from the NAS.  Roon is still crunching in the background fingerprinting the music.

 

I have one more step on the bench to complete.  I am setting up a network bridge on AL so that I isolate the main stereo endpoint.

 

The NUC server will be on my basement equipment rack with the NAS.  Both will be powered by the HDPLEX 200.  I will be testing with a couple of network bridge endpoints shortly.

 

MANY MANY thanks to @austinpop

 

 

 

 

Link to comment
42 minutes ago, bobfa said:

I am looking into having two NUC machines running Audio Linux in my system, server, and a network bridge.  Both are running Roon software.

 

Rajiv sent me his document to kick off my idea of taking my NUC network bridge and turning it into a Music server.  It did not sound like it would be hard just challenging as I am not fluent in Linux.    First I had to upgrade the NUC with an Optane Stick.

 

 

IMG_0845.thumb.jpeg.704a4066b8218e5d33f48eb312c2da4d.jpeg

 

I purchased a 32Gb stick to install in the Akasa NUC

 

IMG_0846.thumb.jpeg.2052f3937fc23da3a154d8e798f3e9fd.jpeg

 

As I showed in the initial build, there are four screws to take the top off of the case.  The NUC7i7DNBE has two M.2 slots.  The one closest to the board is for the Intel WiFi/Bluetooth radio card.  The slot that is further away is the 80mm long slot for PCIE NVME SSD, and it is Optane ready.  There is a small screw that holds down the end of the card.  Make sure to use proper anti-static precautions here.  Remove that little screw.

 

IMG_0848.thumb.jpeg.ca6a3102cce23472ad54059ad6cf7866.jpeg

 

The plug the card into the M.2 slot and replace the screw holding down the M.2 card.

 

IMG_0849.thumb.jpeg.0f483fcfb4f0aed9f0fbf63380a37019.jpeg

 

Here is the overall picture of the inside of the case with the Optane card installed.

 

IMG_0850.thumb.jpeg.d079aecc7c5ffec98d6da92853ccab52.jpeg

 

I the BIOS I had to turn that M.2 slot back on.

IMG_0851.thumb.jpeg.c8442dedcbc913abdeffc62cabba8672.jpeg

 

Notice that the BIOS shows that there is a card in the slot.  Just check the box shown and save the BIOS and exit.

 

 

It took me some time to work through the process that @austinpop provided.  I had to relearn some stuff and LEARN some more stuff.  The drive and partition ID scheme is Linux is a bit different that MacOS and Windows.  I made a couple of typing mistakes and had to redo a couple of steps!  I had a couple of stumbling blocks, but we worked those out.  Oh and one email to @hifi25nl when I got desperate, but Rajiv had already solved it!

 

The NUC is setup on my test bench and connected to the network along with a keyboard and display.  I did most of the work on my 27in screen iMac so that I could have the document and a shell into the NUC side by side.  I found that the nano editor works fine for me but it was not working right in Termius so I just opened the Unix Terminal on the Mac and SSHed into the NUC.  

 

I have my music library stored in three places for "safety." My Sonic Transporter has it stored internally, and it is on my QNAP NAS.   I setup Roon on the NUC server to access the library from the NAS.  Roon is still crunching in the background fingerprinting the music.

 

I have one more step on the bench to complete.  I am setting up a network bridge on AL so that I isolate the main stereo endpoint.

 

The NUC server will be on my basement equipment rack with the NAS.  Both will be powered by the HDPLEX 200.  I will be testing with a couple of network bridge endpoints shortly.

 

MANY MANY thanks to @austinpop

 

IMG_0855.thumb.jpeg.3ba46d42da841d642b7c36259fdf2716.jpeg

3

The

42 minutes ago, bobfa said:

 

 

 

Folks I forgot to add the heatsink to the Optane SSD!!  Using the pad attach the heatsink to the SSD!

 

IMG_0855.thumb.jpeg.3ba46d42da841d642b7c36259fdf2716.jpegIMG_0857.thumb.jpeg.6ad3e6458349fedc0cc4ec9c0b2b499b.jpegIMG_0856.thumb.jpeg.27cebb890817c5b0e6b66213d05eb52b.jpeg

 

 

Link to comment

Roon audio device issue with two AL machines in the same network. @hifi25nl any ideas?  Anyone else? @austinpop 

 

I have one AL NUC machine running Roon Core. 

I have a Sonic Transporter running  Roon Core 

I have a second AL NUC  running RoonBridge

 

  • When the Sonic Transporter is the Roon Core the NUC running roonbridge shows the DAC hooked to the USB port in Roon Audio Settings
  • When the NUC AL machine is the Roon Core the same NUC endpoint does not show the DAC hooked up to the USB port in Roon  Audio Settings.
  • ALSO when the two NUCs are running the devices "Connected to CORE" do not show up at all.  If I shut down the NUC running roonbridge the "connected to Core" devices appear.

 

This is weird to me.  Of note that both of the AL machines are built from the same download of AL and have been updated online.  (I should be properly licensed to run two)

 

NOTE: I built a new USB stick today for the roonbridge machine just to test. 

 

 

Link to comment
1 hour ago, austinpop said:

On the 2 AL machines:

  • stop Roon Server or Bridge as the case may be. You can use the menu option to STOP and disable all running audio services
  • (as root) rm -f /var/roon/RAATServer/Settings
  • Now start Roon Server or Bridge as the case may be. 

I deleted the file unique_id in that settings folder on the bridge and everything is working.  I did not change it on the server yet. 

 

If someone else has this problem remember to fix it on real media if you are running in RAM

 

Link to comment
9 hours ago, ray-dude said:

 

 

The ArchLinux site (linked from the audiolinux site) has lots of good info on how to setup wireless networking, but it took a long time to wade through.  I distilled down my findings into a simple recipe that I use, that may be useful to others that want to play with WLANs on their NUC (I've used this on both my NUC7i7DNKE and NUC7CJYH)

 

 

 

* Make sure WiFi on in bios

 

* Install WPA supplicant

 

pacman -S wpa_supplicant

 

 

* Find out name of wireless interface:

 

ip link

 

(mine is wlo2)

 

 

* Quick setup of WPA supplicant config file

 

wpa_passphrase MYSSID MYpassphrase > /etc/wpa_supplicant/wpa_supplicant-wlo2.conf

 

(use your interface name where I used wlo2, and your WiFi SSID and passphrase in plain text

 

 

* Test wpa_supplicant

 

wpa_supplicant -i wlo2 -c /etc/wpa_supplicant/wpa_supplicant-wlo2.conf

 

(again, use your interface name where I used wlo2)

 

If it connects cleanly, control C to kill.  If not, you have some digging to do to figure out why: 

https://wiki.archlinux.org/index.php/WPA_supplicant

 

 

* Setup to start at boot, start it up, and check that it is running

 

systemctl daemon-reload

systemctl enable wpa_supplicant@wlo2

systemctl start wpa_supplicant@wlo2

systemctl status wpa_supplicant@wlo2

 

(use your wireless interface name after the @ sign)

 

 

* Create /etc/systemd/network/wl.network for your wireless interface

 

[Match]

Name=wlo2

 

[Network]

DHCP=yes

 

[DHCP]

RouteMetric=20

 

 

* If you're going to run wired ethernet at same time modify /etc/systemd/network/en.network

 

[Match]

Name=en*

 

[Network]

DHCP=yes

 

[DHCP]

RouteMetric=10

 

 

 

* Restart networkd and check:

 

systemctl restart systemd-networkd

networkctl status

 

 

* Get IP address(es) and check

 

ip a

 

You should have a different one on each network interface you set up (wired, wireless, etc)

 

ping the IP address(es) from another computer on your network

 

 

Thanks for the formula it helps. I will have to adjust  and put in the route metric. I had used what Piero put up the other day on his website.  I am going to try an experiment where I have both network interfaces active and switch playback in Roon.  This will leave the wireless radio on.  I will then disable the  m.2 slot in the BIOS and see what happens to the sound from Ethernet.    Note I will post about adding the wireless card to the hardware shortly.

 

 

 

 

Link to comment
1 minute ago, User471 said:

Also can anyone point me to a post with the optimised BIOS settings in it?

I have some of it in my post here:

 

The basic BIOS changes for the NUC I am using are there.  Now some of the setting will change due to hardware, adding wifi or optane, etc.  I am not sure that they are fully optimal.

I will be updating it shortly for adding an internal wifi card.

Link to comment
3 hours ago, tapatrick said:

had similar issues @bobfa (did you get yours working?) but after a few days back and forth with Piero, I got the network bridge working. It's worth the effort for the improvement in SQ. I did follow the instructions carefully but kept getting issues but eventually succeeded. When working it looks like this:

I have not had time to get back to testing this.  I see that the bridging scripts have been updated in the latest menu.  I will test with the and see what happens.  My current server (Sonic Transporter) is bridged and that helps.  I think we will get to a point where the setup menu system will make this accessible to everyone.

 

I left off at a point where the endpoint was not accessible and could not get an IP address when rebooted when talking to AL server in a bridge.  

 

Keep us informed as to your progress.

Link to comment
8 minutes ago, amolan said:

Hi,

 

Where did you get this unique_id ?

 

Thanks,

 

Alexandre.

This is a problem when the Roon folders are copied and you try to run two devices on the same network. Roon gets VERY confused!

 

Search for it on the forums. You shut down Roon and delete some stuff.  I would not do this on the server so you do not lose the database or anything by accident

 

Link to comment

I started playing with processor core dedication today.  I ran the scripts while in RAMBOOT and they threw errors saying /etc folders were full.  So I rebooted into USB and the audio status menu does not display data properly it ends up blank.  So I broke something running that menu item while booted into RAM. 

 

To that end audio-Linux 1.0 with menu 100 is up on the website so I am going to reflash and start over.  Takes about 15 min to get up and running.  OH, and menu 101 appears to be up also.

 

I will see where the listening takes me after I get the USB rebuilt.

Link to comment
6 hours ago, bobfa said:

I started playing with processor core dedication today.  I ran the scripts while in RAMBOOT and they threw errors saying /etc folders were full.  So I rebooted into USB and the audio status menu does not display data properly it ends up blank.  So I broke something running that menu item while booted into RAM. 

 

To that end audio-Linux 1.0 with menu 100 is up on the website so I am going to reflash and start over.  Takes about 15 min to get up and running.  OH, and menu 101 appears to be up also.

 

I will see where the listening takes me after I get the USB rebuilt.

I just build a new USB stick and play.  Of course, I break stuff all the time.  OH well

Link to comment
  • 2 weeks later...

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...