Bugzilla – Bug 13231
Baby offers upgrade even after it's been upgraded when connecting to hidden SSID network r6895 MP
Last modified: 2009-09-08 09:28:18 UTC
When I connect a 6895MP baby to an SSID-non-broadcasted network the firmware upgrade process is bad. Half the time it successfully upgrades, reboots, and then prompts for begin update and shows no version number. The other half the time it looks like it upgrades, reboots, prompts to update again also showing no version number. Reproduced with Linksys WRT310N and Dlink DIR655.
Created attachment 5564 [details] tail -f log
I tested here with hidden / non hidden SSID and I cannot reproduce what Ross is seeing. I loaded r6895 on Baby, did a factory reset, connected to the AP, got a update offered (r6896) from SN and after downloading, installing and rebooting I am now at the Squeezebox Account screen. No second update is offered. I have no local SC running. The fact that something gets offered in your case tells me that the wireless connection is fine. Which leads me to believe it has nothing to do with hidden / non hidden SSID. In fact I don't see how that could make a difference. Also your log shows at least that Baby has reconnected to the AP just fine: AR6000 connected event on freq 2462 with bssid 00:23:69:41:b4:14 listenInterval=100, beaconInterval = 100, beaconIeLen = 0 assocReqLen=38 assocRespLen =59 Network: Infrastructure Are you sure the second update, for whatever reason isn't offered from a local SC? I am going to include Tom and Richard. They know more about the upgrade process than I do.
(In reply to comment #2) > Are you sure the second update, for whatever reason isn't offered from a local > SC? > > I am going to include Tom and Richard. They know more about the upgrade process > than I do. I agree baby is definitely connected, and I'm _not_ sure the update isn't being offered from a local SC. I have a local SC running, and using custom.baby.version it is pushing 6985MP, this should not prompt as it is lower than 6986.
We should confirm whether this is really an MP issue or not (seems like it's not), since after upgrade, you will have a non MP fw. The "no version" shown FW upgrade screen I believe only happens now when you have a custom fw on an SC. The file custom.baby.version actually is what's used for the fw version comparison, not the bin file, so Ross, can you you check the contents of "custom.baby.version" to see what version it shows?
This is a symptom of bug 13256.