Bugzilla – Bug 3194
Resetting the router caused SB3 to lock up
Last modified: 2006-04-06 09:50:32 UTC
After switching to the 6.23.2006 nightly to fix the FLAC/cue issues with v6.2.x, I noticed that after several hours the network would stop responding. This forces me to restart the Linksys WRT54Gv5 router. After the router negotiates with the DSL modem, the SB3 (using wireless connection) will lock up and the display will stick at whatever was on screen at the time.
chris to reproduce
I haven't been able to reproduce this bug, I'm afraid. Linksys does have some updated (from what came on my WRT54Gv5) firmware, version 1.00.6: http://www.linksys.com/servlet/Satellite?c=L_Download_C2&childpagename=US%2FLayout&cid=1115417109974&packedargs=sku%3D1127782957298&pagename=Linksys%2FCommon%2FVisitorWrapper Have you tried it? Also Richard Titmuss has been working furiously to fix various router connectivity issues. His latest sb3 firmware (37) should be in the nightly builds tonight, available for download tomorrow. If those don't work, could you describe your home network to me in a bit more detail? You have a DSL modem (what brand/model? We have several in house I could try) with a WRT54G attached to it. Is your slimserver machine (running XP, it looks like from the bug) connected to the router with a cable or does it also connect wirelessly? Are there other wired or wireless devices connected? Please edit the bug with any new information. If you reply to this automated notification email message, I will not receive it.
I updated to the 4/3/06 nightly and the problem is gone. The only problem I encountered was once while playing a song, the display became garbled, and I had to reset the SB3.
Excellent. If you notice any more problems with the display becoming corrupted, feel free to let us know. There's a bug dealing with display corruption already that might be a good place to add any information you can: https://bugs-archive.lyrion.org/show_bug.cgi?id=3156 I think we're fixing enough big connectivity bugs that we may have time to fix some of the less-critical ones like display corruption soon. We've even had someone here in the office report it, but it seems difficult to reproduce. I'm going to go ahead and mark this bug as "Closed". If you have additional problems, you can always reopen it.