Audiolinux Server configurations, Software, Hardware, and Listening Impressions

[hifi25nl]

I guess that you did try typing N + ENTER, not only N.

 

For people having this problem (I don't have it here) you can disable ramroot this way: go to console and type

sudo ramroot -D

and after

sudo ramsave

After reboot.

 

If the problem persists I would try to enable ramroot a second time with keyboard connected

sudo ramroot -E

sudo ramsave

 

 

[gsquared]

1 hour ago, lpost said:

 

I experience the same though I'm not yet running AL2 rather ALprevious, for what it's worth.  Frustrating.

 

I experienced the same thing. I had to move enabling Ramroot to resize AL partition in RAM to one of the last steps. 

[lmitche]

37 minutes ago, hifi25nl said:

I guess that you did try typing N + ENTER, not only N.

 

For people having this problem (I don't have it here) you can disable ramroot this way: go to console and type

sudo ramroot -D

and after

sudo ramsave

After reboot.

 

If the problem persists I would try to enable ramroot a second time with keyboard connected

sudo ramroot -E

sudo ramsave

 

 

I have this problem all the time. My guess is that a newly downloaded version of the kernel doesn't contain the driver for the wireless Logitech keyboard used daily here. So when this happens, if I subsequently run an "Audiolinux update" from the menu it is fixed.  Likewise if I run "Audiolinux update" from a ssh terminal without the Logitech dongle in place, the same thing happens.

 

This forces me to use the ramroot method described by Piero.

[hifi25nl]

You can take also a look here:

https://wiki.archlinux.org/index.php/Mkinitcpio#Configuration

 

In general, you could add the driver for keyboard to /etc/mkinitcpio.conf

For example 

MODULES=(atkbd)

and re-enable ramroot (...in ramroot) with

sudo ramroot -E

sudo ramsave

 

If keyboard is recognized during audiolinux boot menu but not immediately after, you could also try to select Audiolinux fallback, that will load most of drivers.

 

[luisma]

On 12/3/2019 at 5:50 PM, lmitche said:

AL2.0 real-time, non-BFQ config

Hi Larry, trying to understand, when you say realtime you referring to editing rtirq.conf and rtapp.conf?

non-BFQ config you mean the regular kernel and not the BFQ kernel?

 

[lmitche]

23 minutes ago, luisma said:

Hi Larry, trying to understand, when you say realtime you referring to editing rtirq.conf and rtapp.conf?

non-BFQ config you mean the regular kernel and not the BFQ kernel?

 

Yes, the regular kernel.

[drjimwillie]

Hello Friends,

I am trying to understand the profiles menu and whether I should use the orange (default) or auto.

The AL webpage says to go to the release notes for more information, but I do not understand the “examples” there and how they correspond to the different choices.

I am using a CAPS Pipeline computer without a NUC or NAA. I am only running HQPlayer embedded on this computer. (I am not converting PCM to DSD, so the CPU is running comfortably). (because of this I did not think it is necessary to isolate cores). I have Roon installed on my NAS. 

I use RAMroot, of course. The only setting I do is to enable ACPI scaling.
I have enabled turbo boost, but I believe this only allows HQPE to do it’s thing when it needs the extra power?

Because of the above I have enabled the “auto” profile.  My assumption is that this will allow AL to optimize my settings. Is this correct?

 

Will people please report their adventures with these profiles?

 

also will you please make recommendations for further optimizations I can enable?

 

Thank you 

Bill
 

 

[Dutch]

edit; Oops, didn’s see this last page...

[hifi25nl]

On 12/5/2019 at 5:05 PM, drjimwillie said:

Hello Friends,

I am trying to understand the profiles menu and whether I should use the orange (default) or auto.

The AL webpage says to go to the release notes for more information, but I do not understand the “examples” there and how they correspond to the different choices.

I am using a CAPS Pipeline computer without a NUC or NAA. I am only running HQPlayer embedded on this computer. (I am not converting PCM to DSD, so the CPU is running comfortably). (because of this I did not think it is necessary to isolate cores). I have Roon installed on my NAS. 

I use RAMroot, of course. The only setting I do is to enable ACPI scaling.
I have enabled turbo boost, but I believe this only allows HQPE to do it’s thing when it needs the extra power?

Because of the above I have enabled the “auto” profile.  My assumption is that this will allow AL to optimize my settings. Is this correct?

 

Will people please report their adventures with these profiles?

 

also will you please make recommendations for further optimizations I can enable?

 

Thank you 

Bill
 

 

 

I will try to explain the logic behind auto profile.

 

If you have installed Audiolinux for the first time, the orange profile is the default.

Let's suppose that you have made some modifications using the options given by Audiolinux menus. A new profile will be automatically created with these changes, the auto profile.

If you want to save this new configuration to a profile you can use the option "Copy Auto to Custom". For example, let's assume that you have copied auto to Custom1. After you can switch easily from the default orange profile to custom1 and back.

 

Very useful for testing different configurations.

You can repeat the process with different settings, saving to custom2  or custom3

 

 

[drjimwillie]

Thank you.

what is happening with the orange profile compared to the green or red profiles?

is it setting the CPU to a specific clock speed or percentage of clock speed? Does it allow it to work with turbo or something like that?

[hifi25nl]

For a detailed explanation of the variables used by profiles you can read the release notes:

https://www.audio-linux.com/html/headless.html

 

And look at the files green, orange and red in /opt/scripts/profiles

[cat6man]

anyone have, and want to share, a particularly good sounding set of variable settings in their profile?

[luisma]

Hi everyone, there is a new version of hqplayer-embedded how can I force the update on Audiolinux? trying to update through the menu it will take the previous version, also

yay -S hqplayer-embedded

still brings the older version

 

[hifi25nl]

Just updated. 

[Evo-No-Revo]

I have an AudioLinux computer question....not really audiophile question. 

 

My NUC currently has AudioLinux.  It is from NUCkleheads and was set up by Larry.  I am totally ignorant to Linux.  I don't mind staying that way...as much as possible.

 

I want to turn the NUC into a Windows machine.  I have connected a monitor, keyboard, USB optical drive for my W10 disc.  They are all working.

 

When I start the NUC, it starts booting up and comes to the 4 different selections before it starts loading AL.  I have found my way to the boot manager but before I can hardly read the same options on the  previous screen, it boots into AL. 

 

What do I have to do to get AudioLinux to let me load Windows 10?  I don't care about keeping AudioLinux on the NUC.   I also don't know if Larry's install is encrypted and I need a password. 

[rickca]

@Evo-No-Revo you need to get into the BIOS and change your boot device preference to your USB optical drive.

Do a save and exit from the BIOS and when it reboots it will boot your Windows installation media.

 

Maybe Larry can advise you how to make a backup of your AudioLinux image before you wipe it out.

[Evo-No-Revo]

Thanks for the advice Rick.   I have two different flash drives with OS on them from Larry.  One has AL/Roon and the other is Euphony/Roon.   I assume that has me covered. 

[rickca]

@Evo-No-Revo one other thing just occurred to me.  I assume you have an Optane M.2 drive in your NUC, is that right?  What is the capacity?  The minimum size requirement is 20GB for 64-bit Windows 10, so make sure you have at least a 32GB Optane (rather than a 16GB Optane).

[lmitche]

9 minutes ago, rickca said:

@Evo-No-Revo one other thing just occurred to me.  I assume you have an Optane M.2 drive in your NUC, is that right?  What is the capacity?  The minimum size requirement is 20GB for 64-bit Windows 10, so make sure you have at least a 32GB Optane (rather than a 16GB Optane).

Yes, there is a 32 GB Optane drive in this NUC. The machine needs to be booted from a Windows 10 installation USB stick. From there the Optane can be erased and Windows 10 installed. There may be a need to enter the bios to force boot from the Windows installation USB stick. Once done Windows should take it from there.

[adamthebrave]

I have NoMachine problem on LQXT 4.1.1.

 

I had a notification there's an update to the NoMachine. A ran the update and after it doesn' taccept my old user and/or password.

[hifi25nl]

The nomachine user and password is the same as audiolinux login, that is audiolinux

Try eventually to reinstall it with

yay -Sy nomachine

[hifi25nl]

Note that nomachine cannot be updated following the notification, that will start a nomachine script, but in Audiolinux you should update instead as reported above.

[adamthebrave]

9 minutes ago, hifi25nl said:

The nomachine user and password is the same as audiolinux login, that is audiolinux

Try eventually to reinstall it with

yay -Sy nomachine

 

Thanks, it worked.

 

It is disturbing that the Nomachine pops up windows like this one. Can you eliminate it?

[hifi25nl]

Unfortunately not. This is in the official package

[lmitche]

Having just posted this on the Roonlabs support site, I think it makes sense to post here as well.

 

Today, after the Roon 1.7 build 511 Roonserver update and Roonbridge 1.0 build 171 installation RoonAppliance is core dumping on the server after initiating Qobuz playback at any resolution.

OS is AudioLinux. Server hardware is AMD Ryzen 7 2700 on Asus B450 motheboard.

Time to dump after playback is started varies by track and resolution. The dump could immediate or as long as 7 seconds depending on track resolution. The higher the resolution, the shorter the time to dump.

Playback from local files is normal with resolutions up to PCM384 and DSD256.

This behavior is the same when playback is started on multiple endpoint devices, Audiolinux/Roonbridge and Windows/Rooncore in control mode.