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

41 minutes ago, drjimwillie said:

 How do I load the driver for my Holo spring DAC?

 

I have seen a lot of examples showing how to install the software but I have not seen examples of how to work with it. 

 How is the experience different between the headless and the lxqt?  

 With the lxqt  you can attach a monitor to the actual computer and with the headless you have to remote into the computer, but you’re still doing the same tasks. I assume the Lxqt has a few more menus or scripts? 

 Can somebody show us some graphics of  A day in the life of a headless user, please?

 

 

 

“That Depends”

 

Well not really.  Headless does not mean you cannot have a head, you can.  My AL devices all have display ability.  You most likely need a display, keyboard and mouse for BIOS settings.  When I built my NUC endpoint and Xeon server I have the display hardware setup.  When AL headless boots up it will present you with the AL menu as you have seen in these various threads here.  Once you have it running you can grab the IP address of the device and SSH into it from just about anything to get you to that menu!  And of course command line as needed.

 

On Roon you should not need a driver for a DAC.  I do not know yours to be sure. With my NUC endpoint there is no display desired so I SSH into it as needed.  I have found very little for anything more over time.   Take a look at my NUC build thread starter to see if that helps!

 

 

 

Bob

Link to comment
3 minutes ago, tapatrick said:

I'm running Roon on my NUC AL server and it also hangs when I pull out the USB stick.

I leave it in as I have an auto save on the roon database every hour because I add a lot of tracks to playlists in a listening session...

Did you move the Roon database off of the USB stick into optane memory or something?

Link to comment
1 hour ago, tapatrick said:

No I have database on the USB stick - no other drives attached....

Tapatrick

 

I am thinking you may have a couple of problems here.  

 

1.   Trying to run Roon Server out of only 4GB of RAM. 

2.   I have not seen others run  Roon Server off of a USB stick and them loading into RAM.  

 

When I built my server I boot off of an Optane SSD and then load into RAM.  During setup, I moved the Roon Database to a separate partition on the Optane.  The music is on an external drive.

 

 

Link to comment

When I did my server build I said I would publish more of the setup process.  I have not done that.  Here is just the uncleaned up section for building the basic Optane Roon stick.

 

After the hardware is all installed boot from a USB stick with the latest AL headless.  Follow just the section in @austinpoppost below that builds the partitions the Optane stick.  (The rest of what he did here is now automated in Audiolinux menus.)

 

Then return back into the menu system and run #14 to Copy /Backup the current install to another drive.

 

After that is done shut down and remove the USB stick.  Then you can power up from the Optane boot.

 

When you get into the menu, then select #1 configuration  menu and select #5 that will transfer the Roon database to another drive which would be the second partition on the Optane.

 

 

Here is what my server booted into RAM with an external drive for music looks like:

********************************************

              

              Welcome to

         AUDIOLINUX HEADLESS

             version 1.0

             

    https://www.audio-linux.com

 

      [email protected]

      

For configuration menu type "menu"

 

For poweroff type "sudopoweroff"

For reboot type "sudo reboot"

 

********************************************

[audiolinux@FairXeon ~]$ lsblk

NAME        MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT

sda          8:0    0  7.3T  0 disk

└─sda1        8:1    0  7.3T  0 part /media/BobMusic

zram0       254:0    0   15G  0 disk /

nvme0n1     259:0    0 27.3G  0 disk

├─nvme0n1p1 259:1    0  488M  0 part /boot

└─nvme0n1p2 259:2    0 26.8G  0 part

[audiolinux@FairXeon ~]$

 

 

Link to comment
  • 4 weeks later...
1 minute ago, austinpop said:

Hey folks, 

 

I just wanted to give kudos to @hifi25nl for his responsiveness to ideas and suggestions for improvement.

 

Earlier this week I tried to setup a new server using the "Copy/backup to... another drive" and "Transfer Roon database to another drive" options. It didn't quite do what I want. I suggested to Piero that what we really wanted was to clone the boot USB stick to the target drive (in my case, Optane SSD), but use the extra space for a 3rd partition on the target for "data," specifically the Roon DB. I also sent him some script suggestions.

 

Well here it is barely days later, and he's delivered it already in menu version 107! 

 

If you're thinking of setting up a new system with Roon server, booting off an Optane (or other) SSD, and putting the Roon DB on this drive in a separate partition, please test 107. You should be able to do all of this now from within the menu without having to drop into the command line.

 

That is GRRRREATTTTTT!

 

I need to go back and re-do my from 0 to ..... setup stuff.  There are so few steps now to get started.  Hi FIVE to @hifi25nl!

 

 

Link to comment
  • 4 months later...
12 minutes ago, austinpop said:

 

Actually the content in sticky up top was created by @bobfa, so I'd as him to consider the changes you recommend. 

 

(The AS topic owner actions have some quirks, so the sticky shows the owner to be whoever originally created the message, not who last edited it.)

I am on a very poor internet connection.  I will try to figure this out when I am in better cover coverage

Link to comment
  • 3 weeks later...
7 hours ago, AnotherSpin said:

I see. You should put image in the folder and make this folder accessible to Terminal. Honestly I don't remember how I did it, maybe google will help here. As a result, in folder menu you should see "open in Terminal", go from here.

No it is simpler

 

Etcher does it all.  I will create a short screen video.

 

Plug in USB stick, run etcher, select download, select USB, select write....

Link to comment
  • 3 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...