Bug 16303 - Cannot set up Duet receiver with 7.5.1 r8837 controller firmware
: Cannot set up Duet receiver with 7.5.1 r8837 controller firmware
Status: RESOLVED FIXED
Product: SB Controller
Classification: Unclassified
Component: Setup
: unspecified
: PC Fedora
: P1 critical with 10 votes (vote)
: 7.5.1
Assigned To: Ben Klaas
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-06-16 19:24 UTC by Ron Olsen
Modified: 2010-06-22 09:37 UTC (History)
10 users (show)

See Also:
Category: ---


Attachments
don't send a playerCurrent notification for a nil object (372 bytes, application/octet-stream)
2010-06-17 20:35 UTC, Ben Klaas
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ron Olsen 2010-06-16 19:24:30 UTC
Setup of a Duet receiver fails when running SBS 7.5.1 with the r8837 firmware on the Duet Controller. The setup proceeds to the step where you have to select the receiver you want to set up. Selecting the receiver causes the controller to "bump" and does not allow the receiver to be selected. Selecting "skip this step" also causes a "bump" and the setup process stays stuck at this point.

Downgrading to SBS 7.5.0 and the r8673 controller firmware cures the problem.

A number of users have reported this problem in the forums.

My platform: VortexBox running Fedora 11.
Comment 1 Ron Olsen 2010-06-16 19:27:45 UTC
See http://forums.slimdevices.com/showthread.php?p=555438 for reports from other users about this problem.
Comment 2 Ron Olsen 2010-06-16 19:31:01 UTC
Seehttp://forums.slimdevices.com/showthread.php?t=79532 for reports from other users about this problem.
Comment 3 Philip Rodokanakis 2010-06-16 20:01:51 UTC
Same problem here. Since the Controller forced me to upgrade this morning, I have been unable to connect to my two Receivers. Makes no difference whether I'm on mysqueezebox.com or my squeezebox server. 

I've tried everything to force the upgrade on the receivers, but I cannot connect to them. I've reset the controller to factory specs, I've rebooted the router repeatedly, all to no avail. When I turn on either Receiver (I have two of them), the red light flashes slowly and turning it on and off or resetting it by holding the button until I get rapid red flashing, makes no difference. The Receivers register as I can see them on the Controller, but I cannot access them and when I try to connect to the mysqueezebox.com network, I get a connection error (although the Diagnostics tell me that I can ping the MySB.com server at 66.150.114.115 and that the two port connections are OK -- I can also "tracert" to that IP address, so it's not a question of not being able to reach the server). 

I've also tried connecting to the squeezebox server but cannot get the players connected.
Comment 4 Ron Olsen 2010-06-17 07:13:03 UTC
Also see http://forums.slimdevices.com/showthread.php?t=79756 for more user reports of this problem.
Comment 5 jj.womack 2010-06-17 08:53:53 UTC
*** This bug has been confirmed by popular vote. ***
Comment 6 Michael Newman 2010-06-17 08:57:42 UTC
Same problem here since the 7.5.1 upgrade. Problem only relates to Duet receiver. Touch works fine.
Comment 7 Chris Owens 2010-06-17 09:18:50 UTC
We will plan push out an updated controller firmware for 7.5.1 for this problem.

Julius Dauz can reproduce this internally and has said he will add more detailed repro instructions.
Comment 8 Michael Newman 2010-06-17 10:13:18 UTC
This does not seem like a controller issue. Shouldn't I be able to do a reset on the receiver and get it connected to the server irrespective of anything to do with the controller?
Comment 9 Julius Dauz 2010-06-17 10:43:14 UTC
Steps to reproduce

Starting FW/SW Versions
Jive - r8673

Update to: r8837

Restore both Jive and Ray to factory defaults.

If you attempt setup, you'll only get as far as attempting to setup Ray. When you select the Ray to setup, the screen just bumps.

As the OP states, if you downgrade to 7.5.0 FW and attempt the setup, it fixes it and you can update to the latest FW. 

I don't thing the issue presents itself any other way. I doubt this issue presents itself to users that update and don't need to facotry reset for, but this is based on preliminary reports of the issue.
Comment 10 Ron Olsen 2010-06-17 11:06:10 UTC
A suggestion: add Duet Receiver setup as a QA regression test when the Duet Controller firmware or Duet Receiver firmware is changed. Such a test would have caught this bug before 7.5.1 was released.
Comment 11 Ben Klaas 2010-06-17 11:21:34 UTC
FWIW, it is already a qualification test for software release, so there is some question as to how this got through. After assessing and fixing this bug, we will look to see if there is a particular aspect of this bug that the test case failed to cover. The QA qualification tests/process will be updated as needed.
Comment 12 Chris Owens 2010-06-17 11:55:11 UTC
For completeness, I can reproduce this reliably.

1) Factory reset SBC using menus
2) Factory Reset SB Receiver by holding button until fast red flash
3) Follow SBC setup process
a) Select English
b) Select Continue
c) Select North America
d) Select networkname
e) Enter password
f) Squeezebox Account screen, select 'Continue'
g) Choose player, select 'Squeezebox MACADX' depending on the last digits of your MAC address
h) Note selecting that player 'bumps' that is, the screen moves slightly but the UI does not proceed to the next screen.

NOTE the other ways of setting up the player (selecting 'Set Up Receiver' from that menu, selecting 'Choose Player' from the Home menu, etc) also fail.  I have found no workaround.
Comment 13 Ben Klaas 2010-06-17 20:35:22 UTC
Created attachment 6884 [details]
don't send a playerCurrent notification for a nil object

This is a proposed patch that has been tested to fix receiver setup.

playerCurrent notification is going out erroneously with a nil object and it's causing squeezeplay to barf. this patch checks to make sure the player object is not nil before pushing out the notification.

I've tested this on three receivers before and after the change. Reproduced the problem every time before the change, setup worked every time after the change.

I'm actually wary of the fix because it seems too easy. I've contacted an ex-squeezebox developer that has more intimate knowledge of this code to see if I'm missing why that nil check has never been there (though I should say I have some idea why the bug just showed itself in 7.5.1).

I'll have QA do some further testing tomorrow on this and if it passes their tests we may have a new 7.5.1 controller firmware yet late Friday.
Comment 14 SVN Bot 2010-06-18 08:23:08 UTC
 == Auto-comment from SVN commit #8882 to the jive repo by bklaas ==
 == http://svn.slimdevices.com/jive?view=revision&revision=8882 ==

Bug: 16303
Description: never send out nil object in playerCurrent notifications
Comment 15 SVN Bot 2010-06-18 12:34:59 UTC
 == Auto-comment from SVN commit #8883 to the jive repo by bklaas ==
 == http://svn.slimdevices.com/jive?view=revision&revision=8883 ==

Bug: 16303
Description: back off earlier change as sending nil as a player object is valid (SlimMenus expects this when press-hold of back arrow is done to force a player disconnect). Adding a check for player object in AlarmSnooze to fix the issue.
Comment 16 chrija 2010-06-18 15:03:22 UTC
I have the same problem.

How can I downgrade the firmware on the controller and the receiver?
Comment 17 Doug Pacas 2010-06-18 22:15:50 UTC
If reverting back to 7.5.0 is the solution, can someone direct me to a URL that will allow me to lownload this aoftware? Logitech only points to 7.5.1 - thanks!
Comment 18 Ben Klaas 2010-06-19 05:36:02 UTC
We'll be pushing out a working 7.5.1 controller firmware out, probably Monday.

If that's too long, grab this
http://benklaas.com/jive_7.5.1._r8885.bin
and put it on an SD card. Remove the battery from your controller and slot in the SD card behind it. Boot up the controller, then go to Settings->Advanced->Software Update, and selected "Update to r8885". After this updates, you should be able to setup your receiver.

I believe this firmware to be safe, but recognize this hasn't gone through the full QA process yet. It's safer (and easier) to wait until QA qualifies this firmware and pushes it out to users via the network.
Comment 19 Ben Klaas 2010-06-19 05:36:41 UTC
one more try on that URL

http://benklaas.com/jive_7.5.1_r8885.bin
Comment 20 bjbwood 2010-06-20 16:55:49 UTC
Downgraded all elements and still not working...help it driving me mad!

FYI tried 7.5.0 on both server and controller and have tried this lates firmware on controller plus 7.5.0 - to no avail...can not connect to Squeezeserver at all and can only seem to see on controlloer which is claims it is connected to but Server cant see it...btw no music.

Gonna give up and wait till monday...oh it already is...hey ho!
Comment 21 drshiva 2010-06-22 03:50:15 UTC
(In reply to comment #20)
> Downgraded all elements and still not working...help it driving me mad!
> 
> FYI tried 7.5.0 on both server and controller and have tried this lates
> firmware on controller plus 7.5.0 - to no avail...can not connect to
> Squeezeserver at all and can only seem to see on controlloer which is claims it
> is connected to but Server cant see it...btw no music.
> 
> Gonna give up and wait till monday...oh it already is...hey ho!
Comment 22 drshiva 2010-06-22 03:51:21 UTC
Did anybody receive the new update with out bug
Comment 23 Doug Pacas 2010-06-22 04:51:29 UTC
Please provide an update on when QA will finish testing this firmware upgrade. I downloaded 7.5.0 and still could not get my controller to select my receiver.
Comment 24 Ben Klaas 2010-06-22 05:19:53 UTC
Just to be clear, the fix is in 7.5.1 not 7.5.0. If you are running SBS 7.5.0, I'd recommend updating to 7.5.1:
http://downloads.slimdevices.com/SqueezeboxServer_v7.5.1/

New controller firmware (r8885) was made available Monday, and anyone running 7.5.1 SBS or connected directly to MySB.com should have seen the update by now.

If for some reason a message hasn't been pushed to screen saying an update is available, on the controller go to Settings->Advanced->Software Update and choose to update to 7.5.1 r8885
Comment 25 Ben Klaas 2010-06-22 09:26:25 UTC
this is resolved in 7.5.1 r8885 controller firmware
Comment 26 Michael Newman 2010-06-22 09:37:33 UTC
(In reply to comment #25)
> this is resolved in 7.5.1 r8885 controller firmware

That fixed the issue for me. Thanks.