I've got a Motorola SB5100 here that's been working fine for months. However, the past few days, I've had some issues with internet connectivity seeming to drop out until I powercycled the Linksys WRT54G v5 (1.06 firmware, just upgraded that to 1.10 last night). All day today, the SB5100 has been going thru its normal startup cycle when I unplug it (sometimes >15 minutes). I see the following cycle of lights:
1: Power: Solid (5-10 seconds) 2: Power: S, Receive Blinky (5-20 seconds) 3: Power: S, Receive S, Send: Blinky (5-20 seconds) 4: Power: S, Receive S, Send: S, Online blinky (5-10 seconds) 5: Power: S, Receive & Send lights blink at same time. [Permanent]It stays in state #5 forever (at least 2-3 hours). I have rebooted it many times today, sometimeswith the WRT54G connected to it, sometimes with only the cable & power cords connected to the SB5100. Doing some scouring online, I could not find a single FAQ or guide that explains what a double-blink means.
An older netgear CG814WGv2 (Comcast-supplied, though TimeWarner recently took them over) cable box that I used to have *could* connect to the cable line here, which is how I was able to do some research & post this. [Netgear box got the boot because it was (1) not able to support more than 4 DHCP clients at once (2) connections seemed flaky, (3) unable to find new firmware to try and update that thing to see if that would fix issues 1 & 2 (4) WRT54G supports dyndns.org. Replacing the CG814WG with the SB5100 and WRT54G made things great for months]
Connecting my computer to the SB5100 while it was connected, I got the following info. Note that it thinks everything is "done" while the double-blink was happening. I don't know how to read the frequency, signal/noise, or power level items, so please advise. The logs (scroll down) are the most interesting-- it seems like it can't lock on to the signals.
Sorry for the exceptionall long post, but I'd rather err on the side of too much info. Is this a problem with my TW Cable? Does the SB5100 need a firmware update? (Didn't see any items on the webpages when connected to it). Is the SB5100 dead and needing replacement? Thanks to all who can reply.
Nathan Mates
--- Logs from SB5100's webpages
Acquire Downstream Channel Done Obtain Upstream Parameters Done Upstream Ranging Done Establish IP Connectivity using DHCP Done Establish Time Of Day Done Transfer Operational Parameters through TFTP Done Register Connection Done Cable Modem Status Operational Initialize Baseline Privacy Skipped
Frequency 739786900 Hz Locked Signal to Noise Ratio 35 dB Power Level -4 dBmV The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading
Upstream Value Channel ID 2 Frequency 25344000 Hz Ranged
Power Level 42 dBmV
[Logs page]1970-01-01 00:00:10 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:16 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:00:02 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 1970-01-01 00:00:13 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response. 2006-10-21 19:30:40 3-Critical D006.0 TFTP failed - configuration file NOT FOUND 2006-10-21 19:30:18 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response. 2006-10-21 19:30:06 3-Critical D006.0 TFTP failed - configuration file NOT FOUND 1970-01-01 00:00:13 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response. 2006-10-21 18:56:17 3-Critical D006.0 TFTP failed - configuration file NOT FOUND 1970-01-01 00:00:12 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response. 2006-10-21 18:16:24 3-Critical D006.0 TFTP failed - configuration file NOT FOUND 1970-01-01 00:00:13 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response. 2006-10-21 17:31:21 3-Critical D006.0 TFTP failed - configuration file NOT FOUND 1970-01-01 00:00:12 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response. 2006-10-21 16:44:59 3-Critical D006.0 TFTP failed - configuration file NOT FOUND 1970-01-01 00:00:14 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response. 2006-10-21 16:18:58 3-Critical D006.0 TFTP failed - configuration file NOT FOUND 1970-01-01 00:00:13 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response. 2006-10-21 16:15:21 3-Critical D006.0 TFTP failed - configuration file NOT FOUND 1970-01-01 00:00:10 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response. 2006-10-21 14:17:07 3-Critical D006.0 TFTP failed - configuration file NOT FOUND 1970-01-01 00:00:11 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response. 2006-10-20 22:19:07 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2006-10-20 22:19:06 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing-- Nathan Mates - personal webpage