r885 - r890, upgrade "cycle"

[Mark Lanctot]

I upgraded from r885 to r890.

Oddly, for the first time ever, when I go to Controller Settings - Advanced Settings - Software Update there's a "new" update waiting which the JHB will happily download and install, but it's r890. When it restarts, the update is still there and I can download and install it again.

It does not seem to recognize that it has the latest firmware.

Thankfully the JHB operates perfectly until I go to the Software Update menu, and it doesn't prompt me automatically on startup (actually mine never has).

[sdonham]

I upgraded from r885 to r890.

Oddly, for the first time ever, when I go to Controller Settings - Advanced Settings - Software Update there's a "new" update waiting which the JHB will happily download and install, but it's r890. When it restarts, the update is still there and I can download and install it again.

It does not seem to recognize that it has the latest firmware.

Thankfully the JHB operates perfectly until I go to the Software Update menu, and it doesn't prompt me automatically on startup (actually mine never has).

I was just browsing the jive forum to see if anyone else had encountered this. For what it's worth, I'm seeing that as well (but I could have caused it myself with all the tinkering I've been doing with jive).
Using r885, I scroll on over to "software update" where it says "updated software is available...." so I download the latest, it reboots and still says "updated software is now available..." (I'm not prompted, it says that only when I scroll to the software update menu).

Personally, I'm just waiting one more day to see if this is a fluke and just goes away. I've been playing around with slimserver and the jive a lot lately, so it's entirely likely I broke something myself. Unlike Mark though, I'm usually prompted to update after a reboot (which is good).

[rtitmuss]

The text changed yesterday, and it's now misleading. If new firmware is available you'll be prompted when you connect to a player. Feel free to file a bug, looks like we'll need to fix this.