INTERACT FORUM

Devices => JRiver Id -- Hardware by JRiver => Topic started by: d_pert on September 02, 2023, 06:59:30 am

Title: Id Pi software upgrade
Post by: d_pert on September 02, 2023, 06:59:30 am

I have three Id Pis (purchased on mSD card). All are Raspberry Pi version 4B. The latest mSD I received from JRiver shipped with MC ver. 31. The other two are still on ver. 30, despite option 12 upgrade attempts.

When should I expect option 12 to bring the two, slightly older Id Pis up to the same version as the newest one?

Thanks.

Title: Re: Id Pi software upgrade cadence
Post by: JimH on September 02, 2023, 07:02:30 am

There's a hidden option:  https://yabb.jriver.com/interact/index.php/topic,135355.0.html

Title: Re: Id Pi software upgrade cadence
Post by: d_pert on September 02, 2023, 07:41:04 am

I just ran option 32.

No upgrade.

Ideas?

Title: Re: Id Pi software upgrade cadence
Post by: d_pert on September 04, 2023, 07:55:30 am

Tried option 32 again. No upgrade.

Questions:

1. Without using option 32 -- should the Id Pis upgrade via option 12 eventually?
2. If so, when when will the 12 work?

Thanks.

Title: Re: Id Pi software upgrade cadence
Post by: JimH on September 04, 2023, 09:17:28 am

How old is it?

Title: Re: Id Pi software upgrade cadence
Post by: d_pert on September 05, 2023, 01:22:31 pm

They're both less than two years old. Both are Raspberry Pi 4B w/ 2GB RAM.

Id 25.0.18   MC 30.0.96   Engen 1.0.69

Thanks.

Title: Re: Id Pi software upgrade cadence
Post by: d_pert on September 06, 2023, 06:04:47 pm

Tried again just now. No change.

Title: Re: Id Pi software upgrade cadence
Post by: bob on September 07, 2023, 07:43:48 am

The IdPI version (25.0.18) endpoint is MC30 which you have.
We needed to upgrade the entire OS for MC31 which can't be done by option 12.
You can send them in to be upgraded. Send an email to deanna (at) jriver (dot) com for instructions and cost.

Title: Re: Id Pi software upgrade cadence
Post by: d_pert on September 07, 2023, 08:36:04 am

Hi bob,

Thanks for this.

They're 100% stable and I only use them as customized DLNA renderers, so I'm unlikely to want/need to have then 'down' for the whole period of physical mailing, etc.

Question, though...

Could I:

1) image the more recent MC31/31.0.2 mSD I received (Id 31.0.2   MC 31.0.33   Engen 1.0.70),
2) make note of the two unique license numbers on the older MC30/25.0.18 ones,
3) 'burn' the MC31/31.0.2 image to those older two mSD cards
4) re-use Option 18 to 're-license' the burned mSDs with those noted license codes

??

P.S. -- I've been able to image all three mSD cards (with 100% verification) using 'Win32 Disk Imager'. I did this as a 'lifeline' in case of mSD corruption caused during, e.g., a power outage. I've never attempted to 'burn back' to the same mSDs though, out of fear that there may be some hidden 'gotya'. ;)

Thanks.