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

Wanted to share a phenomenon powering the i7 NUC (DNBE) with the LPS1.2. I've noticed a "warm up" effect in terms of how tolerant the LPS1.2 is with power hungry options.

 

I had the NUC running on AL ramroot, extreme 2, 4 cores active, low power mode which was stable and going for days (perhaps 1.5 weeks). Then we had a power outage so the NUC was off for a few days (including after power outage). When I restarted the NUC it would not boot despite trying 10+ times to boot, with the exact same settings.

 

The only way I could get it going was by going 1 core active, AL normal BFQ (no extreme). Gradually after the LPS1.2 warmed up, I added back the other options one by one until I was back to where I was before the power outage.

 

@Superdad is there any documented increase in LPS1.2 current output as it warms up?

 

Yeang

Link to comment
  • 5 months later...

@hifi25nl Piero,

 

Wondering if you could help with this. I've been enjoying Audiolinux on my NUC7i7DNBE greatly, and have been using Roon Bridge which always connects without any issues, 100% reliable.

 

I used to love using HQplayer before I moved to Audiolinux. With audiolinux, switching to the NAA service, I keep getting dropped connections with my HQplayer computer which is connected to the same Brocade ICX6650 switch. It takes a while before the HQPlayer desktop program can recognize the AL NAA.

 

I assumed this was a problem with HQP, so I posted in the HQP forum, and Jussi suggested using his NAA image to boot. Using that, it's 100% reliable with the same exact hardware, so I think in my case it is some Audiolinux setting which is off.

 

Any suggestions? I have 4GB RAM on my NUC which should be enough for NAA. Not sure why the connection is so flaky.

 

Thanks!

Yeang

Link to comment

Could well be the blacklisting. @luisma @AnotherSpin @hifi25nl thanks so much for the tips.

 

I'll go back to a vanilla install and see if it works.

 

How much RAM do you guys have on the NAA machine? I have only 4GB, wonder if enough for NAA (it is enough for roonbridge for sure).

 

I use HQP desktop 3.25 not the embedded version.

 

@luisma I had a multihomed setup for a while, Miska yelled at me for that. It was too much trouble so i quit using that and went back to waiting for EtherRegen lol.

Link to comment
4 minutes ago, AnotherSpin said:

 

It is stated on AL site that you need 16GB RAM for entire system and 8GB for headless.

 

True, but Piero had OK'd 4GB of ram for headless Roonbridge with Ramroot... this could be an issue with NAA i guess.

 

@hifi25nl Piero, do you know if 4GB ram is enough for NAA, with ramroot, using AL headless? 

 

Link to comment

tried updating to newest kernel, no luck. @luisma here's the output you requested:

 


[root@audiolinux ~]# networkctl
IDX LINK             TYPE               OPERATIONAL SETUP
  1 lo               loopback           carrier     unmanaged
  2 eno1             ether              routable    configured

2 links listed.
[root@audiolinux ~]# ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 54:b2:03:14:f7:14 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.20/24 brd 192.168.1.255 scope global dynamic eno1
       valid_lft 5012sec preferred_lft 5012sec
    inet6 fe80::56b2:3ff:fe14:f714/64 scope link
       valid_lft forever preferred_lft forever
 

Link to comment
1 hour ago, luisma said:

Looks about right. It is configured as DHCP right?

IPv6 and multicast enabled

 

Just for testing would you like to configure it as static?

 

edit as root the file

nano /etc/systemd/network/eno1.network

 

[Match]
Name=eno1

[Network]
Address=192.168.1.20/24
Gateway=192.168.1.1

 

You can select a different IP that doesn't conflict with your dHCP pool and configure the gateway which I'm assuming is 1.1

MAybe you did this already

 

 

@luisma

Thanks for your suggestions. I will try this! 

 

I also updated the AL menu and all other components as well as the kernel. HQP still not seeing NAA reliably at all.

 

Yeang

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