Roon 3.0 ROCK access

Early Access
1

I just noticed this.

Does that mean if I have a MOCK ROCK, for example using a newer gen Intel chip, that it won’t ever update to 3.0. Or, if I am using ROCK on a NUC with an AMD chip?

2

I think it just means that it must be an UEFI installation, as has been the case for all RoonOS updates since 2.1 (and the final 1.0 update as well)

3

Maybe, but, it would be good to know officially.

4

I wouldn’t expect this to have changed, but I don’t think it ever excluded MOCK. Surely someone with a MOCK would have said something by now?

5

UEFI devices will continue to get update notifications regardless of the processor type. Machines outside of the list of supported devices are supported best effort.

6

RoonOS 3.0 early access works fine as a MOCK installation on a GMKTec G3plus (intel N150) device.

In fact, while RoonOS 2.0 doesn’t support the GMKTecs USB ports properly, this works fine in RoonOS 3.0, supposedly thanks to the updated Linux kernel supporting newer hardware.

7

I have no success on virtualized ROCK. The production release has been working like a charm, but when I put the .bin-file in the reinstall map, and I click install, it just reboots RoonOS 2.1 (build 271) production instead.

EDIT: Nevermind, there’s a wrong link in this article:

===========================

(…)
Roon Early Access download links

macOS

Roon

Windows

Roon

RoonOS

Instruction File ← this points to the wrong file
(…)

8

Hey @Leroy_la_Fontaine curious why virtualize as a ROCK vm? I have Roon running on a Debian lxc. Just wondering, thanks.

10

No Roon/music-related reason at all.

I have a home server running various VMs and other services. I don’t see any reason to dedicate a separate device to Roon if I can simply spin up a VM for ROCK. :slightly_smiling_face:

And as a benefit, I can back up the VM itself and the library to a second server.

EDIT: In hindsight, you probably meant something else.

ROCK was one of the first things I tried running on Proxmox, and PVE was my first experience with virtualization. VMs were simply the first thing I looked into, before I even considered containers. Once it worked, I never looked back. :sweat_smile: