Roon OS 1.0 Build 253 Observations

[AMP (Andrew P)]

@mikeb

Instructions for the Reinstall directory are here: https://help.roonlabs.com/portal/en/kb/articles/roonos-reinstall-directory-instructions#Using_the_Reinstall_Directory

You will need to use this file: roonos-production.bin

(above download link edited to be the correct one for RoonOS)

Short version is:

• Download the file linked above to your computer
• Mount the Data folder from your RoonOS device on your computer and navigate to the Reinstall folder
• Copy the downloaded file to the Reinstall folder
• Hit the reinstall button on the admin page

[AMP (Andrew P)]

@Tim_Rhodes

I assume this is something to do with the reauth that I had to do, but this audio device is spurious, any idea how to get rid of it?

This string is cached on the Roon side and isn’t refreshed often. Restart your remote and it should be correct.

[mikeb]

Thanks Andrew … I’ve tried a couple of times. followed the instructions, but it’s stubbornly staying on 253. earlyaccess. Any other ideas?

[Tim_Rhodes]

Yeah it has disappeared now, thanks!

[Tim_Rhodes]

@AMP

I am having the same issue as @mikeb, with the os-production.bin file in place and hitting Reinstall does not move the RoonOS from 253 to 254. Although the .bin file is removed.

[Tim_Rhodes]

In fact all this has done is move my Core version from earlyaccess 1149 to produciton 1148

[AMP (Andrew P)]

@mikeb

Any other ideas?

Yeah, it would have really, really helped if I had given you the correct file to download. That one was for Roon, not RoonOS. This is what I get for jumping in before that second cup of coffee…

Here’s the correct file:

roonos-production.bin

The one you downloaded moved your Roon install back to production if you want to be on Roon earlyaccess then you need to use this one: roon-earlyaccess.bin

[Tim_Rhodes]

Nope that hasnt worked either. Still on RoonOS 253 earlyaccess.

[AMP (Andrew P)]

@Tim_Rhodes … download the file again and copy it over then reinstall. I noted an error which I’ve now corrected.

[Tim_Rhodes]

Yeah I used the correct file from your last message, it didn’t work, although the file was deleted after the reinstall.

[AMP (Andrew P)]

no, there’s been another correction since the post I made. download it again.

[danny (Danny Dulai)]

@ivan @simon_pepper

I see details about Intel HDMI audio vs Intel HD audio here…

I think this is a feature of the new Linux kernel. The old one seems to have depended on Intel HD to make the HDMI work. You were able to disable HD audio in the past, which broke HDMI support. They seem to have eliminated that requirement now. I don’t think you can actually disable HDMI audio in the BIOS, just “HD Audio”

We should move this conversation about HDMI and Intel HD audio here:

Booting via UEFI - Intel NUC 11/12 - HDMI audio

Look here: That is the unit I have. NO “Intel HD Audio Technology”. [image] Torben PS: But it is nice that it is working now Roon HDMI Output

[simon_pepper]

No jumper settings.
This additional audio options seem to be ALSA driver based, rather a hardware based option.
Can the inclusion of ALSA drivers in RoonOS be made optional?

[Tim_Rhodes]

Ah sorry I misunderstood. Yes that one has worked now RoonOS 254, thanks

[mikeb]

That worked better, thanks… RoonOS is now at 254, though OS version is still “earlyaccess” - how can I get that back to “production” for a clean house?

[Suedkiez]

@mikeb

OS version is still “earlyaccess” - how can I get that back to “production” for a clean house?

This should happen automatically by a prompt in Roon (if this works for you) as per here:

FYI: RoonOS 253 earlyaccess will move to 254 production automatically

I just wanted to let you all know that since RoonOS isn’t something that’s under constant revision like Roon and ARC it’s not going to go through the same ongoing test → release cycle as those products. We don’t want to have you end up orphaned on the earlyaccess branch of RoonOS so we’re going to setup the update server to migrate ROCK and Nucleus devices which were updated with RoonOS 253 earlyaccess to 254 production. This rule isn’t in place yet, but at some point in the next day you’ll see…

(Not happening for me yet, though)

[mikeb]

Yes, all good after Remote was quit and re-opened.
@AMP all good here now, thanks for your assistance.

@danny

i was able to reproduce the mismatch, but it was fixed on restart of remote.

[CrystalGipsy (Resisting the flow!)]

On my non nuc core my disabled HDMI don’t show up on this build so it must be a combination of bios on the NuCs as well.

[BlackJack]

@simon_pepper

Can the inclusion of ALSA drivers in RoonOS be made optional?

I don’t think that @danny feels the wish to make a product designed to be simple more complicated for just that? I think most users see outputs/potential listening zones they never use when looking into Settings|Audio. It’s seems to be easy for most to just leave them alone and disabled.

[ged_hickman1]

I think the volume of “what are these and why are they enabled” is quite low. The support volume from users disabling the extra ports, forgetting they have done so or forgetting how to re-enable them would be much higher.