Reply
Connection Expert
EG
Posts: 43,212
Registered: ‎12-24-2003

Re: Motorola 5101 Firmware problem (update)

This thread is for issues with the 5101.
Visitor
Posts: 2
Registered: ‎04-16-2008

Re: Motorola 5101 Firmware problem (update)

Requesting a push as well. I just replaced my SB5120 to SB5101. Thanks!

Software Version: SB5101-2.4.1.5-SCM01-NOSH
Hardware Version: 1
MIB Version: II
GUI Version: 1.0

Logs:

1970-01-01 00:00:41 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:00:38 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:36 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:15 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:15 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:11 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:11 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing


Recognized Contributor
Posts: 325
Registered: ‎04-07-2008

Re: Motorola 5101 Firmware problem (update)

[ Edited ]
That's the same Software Version that is on my SB5101 that I've had since last friday.
So far, no update has been pushed to the modem.
People in here said there is nothing wrong with using that S/W as long as the cable modem is working correctly.
 
Those "1970" year listings in the Log is when the modem is first turned on, before it knows what the current date and time is.


Message Edited by FAUguy on 04-17-2008 07:34 PM
Security Expert
CajunTek
Posts: 20,976
Registered: ‎10-07-2003

Re: Motorola 5101 Firmware problem (update)



Ultrahawke wrote:
Requesting a push as well. I just replaced my SB5120 to SB5101. Thanks!

Software Version: SB5101-2.4.1.5-SCM01-NOSH
Hardware Version: 1
MIB Version: II
GUI Version: 1.0

Logs:

1970-01-01 00:00:41 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:00:38 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:36 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:15 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:15 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:11 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:11 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing




Your modem is not showing a problem.
TANSTAAFL!!



Visitor
Posts: 1
Registered: ‎04-18-2008

Re: Motorola 5101 Firmware problem (update)

I am having frequent and long disconnects with my 5101 as well. The live chat tech gave me a ticket number of 1000145857482021 and set me up for a truck to come out. Sounds like they can save the trip if its an internet fix...
Visitor
Posts: 1
Registered: ‎04-25-2008

Re: Motorola 5101 Firmware problem (update)

Software Version: SB5101-2.4.1.5-SCM01-NOSH
Hardware Version: 1
MIB Version: II
GUI Version: 1.0

May I have a firmware upgrade push please.
Thank you.
Regular Contributor
Posts: 25
Registered: ‎02-29-2008

Re: Motorola 5101 Firmware problem (update)

[ Edited ]
Could still use that config/firmware push please.
 
<edit>
I called support due to slow speeds and tried to get this taken care of over the phone again, but the tech told me to "call Microsoft"...then "call your local office" and finally "we don't do that here...I've worked here 3 years and we have never done that".  This thread seems to be the only outlet in getting this done.


Message Edited by Suchey on 04-27-2008 08:56 PM
Visitor
Posts: 1
Registered: ‎05-02-2008

Re: Motorola 5101 Firmware problem (update)

I need the config push please. I have been having constant connection problems with the 5101.
Contributor
Posts: 9
Registered: ‎03-23-2008

Re: Motorola 5101 Firmware problem (update)

here is my info on my 5101

Software Version: SB5101-2.4.1.5-SCM01-NOSH
Hardware Version: 1
MIB Version: II
GUI Version: 1.0
-------------------------------------------------------


LOG

1970-01-01 00:42:56    3-Critical    R002.0    No Ranging Response received - T3 time-out
1970-01-01 00:42:52    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:42:32    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:42:31    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:42:28    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:42:27    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:42:17    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:42:17    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:42:17    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:42:16    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:42:11    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:42:10    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:42:09    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:42:02    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:41:59    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:41:58    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:41:57    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:41:57    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:41:55    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:41:51    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:41:47    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:41:46    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:41:38    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:41:38    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:41:34    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:41:33    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:41:32    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:41:31    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:41:21    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:41:21    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:41:06    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:41:06    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:40:58    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:40:58    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:40:57    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:40:56    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:40:49    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:40:49    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:40:47    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:40:46    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:40:43    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:40:42    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:40:40    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:40:39    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:40:35    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:40:35    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:40:28    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:40:28    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:40:19    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:40:19    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:40:14    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:40:11    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:40:11    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:40:05    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:40:04    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:39:51    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:39:50    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:39:48    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:39:39    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:39:38    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:39:14    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:39:14    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:38:52    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:38:51    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:38:51    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:38:50    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:38:50    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:38:49    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:38:49    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:38:48    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:38:42    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:38:41    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:38:29    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:38:28    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:38:28    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:38:20    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:38:17    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:38:16    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:38:13    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:38:10    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:38:05    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:38:04    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:37:56    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:37:55    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:37:53    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:37:52    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:37:50    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:37:50    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:37:43    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:37:42    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:37:24    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:37:24    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:37:18    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:37:17    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:37:16    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:37:16    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:37:14    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:37:14    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:37:08    3-Critical    T002.0    SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:37:07    3-Critical    T001.0    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing



not sure if i need the config pushed anyone know what all these log errors are about nothing bad i hope?
Connection Expert
EG
Posts: 43,212
Registered: ‎12-24-2003

Re: Motorola 5101 Firmware problem (update)

[ Edited ]
Well you do indeed have the correct firmware version for your 5101.
 
That said, as far as your error listings, it shows one event of a loss of sync lasting approximately 6 - 7 minutes.
 
Is that the entire contents of the log ?
 
Was that snapshot taken right after you performed a powercycle of your modem ?
 
If not, it may also be that Comcast was performing some sort of maintenance (usually late at night) that took your modem offline for a while.
 
It's impossible to tell exactly what time it was when this occured because there is no T.O.D. (time of day) information there.
 
Are you having any specific connectivity issues ? 


Message Edited by EG on 05-05-2008 09:37 PM
Contributor
Posts: 9
Registered: ‎03-23-2008

Re: Motorola 5101 Firmware problem (update)

oh ok thanks i was just making sure i had the right firmware and was wondering about those error thanks for the quick reply.
Recognized Contributor
Posts: 325
Registered: ‎04-07-2008

Re: Motorola 5101 Firmware problem (update)

I've now had the SB5101 for almost a month with Software Version: SB5101-2.4.1.5-SCM01-NOSH.
Over the past 2 weeks I've been getting alot of disconnects, with the Log today showing:
 
2008-05-06 11:39:01 3-Critical T005.0 SYNC Timing Synchronization failure - Loss of Sync
2008-05-06 11:26:45 3-Critical R002.0 No Ranging Response received - T3 time-out
2008-05-06 11:25:19 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2008-05-06 11:24:47 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-05-06 11:24:31 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
 
What I don't understand is why no one is getting the new firmware push that has requested it in here recently.
Michael seems to have vanished and has not responded to my PM.
Visitor
Posts: 2
Registered: ‎05-09-2008

Re: Motorola 5101 Firmware problem (update)

Michael,
 
I have a new surfboard 5101 and it does not have the latest firmware.
 
My log shows no attempt to download it either.
 
I have had major up and down speed issues in fact right now I have 3.3mps down and 210 kps up.
 
I have had 3 visits from comcast techs.
 
After the technician visits I was getting 10 mps down and 1.5 up.
 
I powered down my equipment today and when I powered it up....3.3 down, 210 kps up.
 
I have called and called and no one seems to know anything about downloading configuration files or new firmware.
 
Can you please help me to be sure I have the correct config file as well as the latest firmware?
 
Thanks,
Eric
Visitor
Posts: 1
Registered: ‎09-06-2006

Re: Motorola 5101 Firmware problem (update)

Have a 5100 and keep getting the 5101 config file.  Glad to see this thread.  I should have come here LONG ago. 

2008-03-02 12:58:34 4-Error E107.0 SW upgrade Failed after download - Incompatible SW file
2008-03-02 12:58:25 6-Notice E102.0 SW Download INIT - Via Config file d11_m_sb5101_speedtier_c01.cm

Software Version: SB5100-2.3.2.5-SCM01-NOSH
Hardware Version: 3
MIB Version: II
GUI Version: 1.0
VxWorks Version: 5.4

Contributor
Posts: 9
Registered: ‎05-13-2008

Re: Motorola 5101 Firmware problem (update)

I don't think I'm getting the firmware update for my Motorola SB5101 to enable Blast speeds, thanks.
Connection Expert
EG
Posts: 43,212
Registered: ‎12-24-2003

Re: Motorola 5101 Firmware problem (update)



SeanWalsh wrote:
 
I don't think I'm getting the firmware update for my Motorola SB5101 to enable Blast speeds, thanks.

F.W.I.W., that's not a matter of *firmware*.
 
That is determined by the provisioning / configuration file that they are loading into your modem.
Contributor
Posts: 9
Registered: ‎05-13-2008

Re: Motorola 5101 Firmware problem (update)

Well either way I haven't been getting Blast speeds and have been going in circles with Support.
Connection Expert
EG
Posts: 43,212
Registered: ‎12-24-2003

Re: Motorola 5101 Firmware problem (update)

[ Edited ]
First, you need to get a confirmation from them that your modem is indeed being provisioned for the correct speedtier that you are subscribed to.
 
This is some of the stuff that we need to even try to help here:
 
 
Try the self troubleshooting stuff, and then post the requested stuff in a new separate thread of your own in this forum.
 
Also, if you are not using Vista or a Mac, take this *Tweak test* and post the results:
 


Message Edited by EG on 05-13-2008 11:27 PM
Contributor
Posts: 8
Registered: ‎02-24-2007

Re: Motorola 5101 Firmware problem (update)

[ Edited ]
I am trying to understand this issue. It looks like Michael stated back in February a fix would be out by the end of the month. Yet it appears after almost 4 months some people seem to still be getting the wrong configuration file pushed to them making those with non current firmware versions unable to update their modems firmware until the correct configuration file is sent?


Message Edited by JCKelly on 05-23-2008 11:16 PM
Contributor
Posts: 9
Registered: ‎03-01-2008

Re: Motorola 5101 Firmware problem (update)

Since my original post, I've tried getting the correct file pushed to my modem. So far I've had no luck getting it done. Calling support is useless, as they say I have the right file every time I call and can't understand how I come up with the information of the file I need (even after explaining to them about their own forums). I keep getting told by support that the techs they are talking to say I have the correct file.
 
I'm starting another post about my connection problems because I have no clue if this modem file not being downloaded to me is causing other problems, or if its just in my town with something else.
Contributor
Posts: 9
Registered: ‎03-01-2008

Re: Motorola 5101 Firmware problem (update)

I no longer need the file for the modem. I am now using a DHG535 as I just switched to using Comcast for my phone service. (Fairpoint raised our bill by over 25% in the first 2 months after the buyout of Verizon here.)
Connection Expert
EG
Posts: 43,212
Registered: ‎12-24-2003

Re: Motorola 5101 Firmware problem (update)



Stashar wrote:
 
I no longer need the file for the modem. I am now using a DHG535 as I just switched to using Comcast for my phone service. (Fairpoint raised our bill by over 25% in the first 2 months after the buyout of Verizon here.)

I think that their provisioning system may recognize that fact :smileywink:
Recognized Contributor
Posts: 325
Registered: ‎04-07-2008

Re: Motorola 5101 Firmware problem (update)

The disconnection poblems have contunied, and is seems that Michael is M.I.A. as he has not respoded to this thread.
Here is my log file for today:
 
2008-05-30 15:19:28 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2008-05-30 15:19:24 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2008-05-30 15:19:24 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2008-05-30 15:19:15 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2008-05-30 15:19:12 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2008-05-30 15:19:11 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2008-05-30 15:19:10 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2008-05-30 15:19:06 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2008-05-30 15:19:05 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2008-05-30 15:19:03 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2008-05-30 15:19:02 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2008-05-30 15:18:59 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2008-05-30 15:18:59 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2008-05-30 15:17:53 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2008-05-30 15:17:32 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2008-05-30 15:17:32 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2008-05-30 15:17:30 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2008-05-30 15:17:29 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2008-05-30 15:17:29 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2008-05-30 15:17:23 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2008-05-30 15:17:22 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2008-05-30 15:16:25 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2008-05-30 15:15:55 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2008-05-30 15:15:55 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2008-05-30 15:15:55 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
Contributor
Posts: 8
Registered: ‎02-24-2007

Re: Motorola 5101 Firmware problem (update)

I just purchased a new SB5101 and after calling to register it got sent a config file called d10_m_sb5101_speedtierextreme2_c01.cm which appears correct for the modem I have and the service I am paying for. The modem's help page shows SB5101-2.4.1.5-SCM01-NOSH which is what came with it. Two questions:
 
1) Which is the latest firmware that Comcast is using for this modem, I've seen some have got SB5101-2.4.1.6-SCM02-NOSH
 
2) If I want the enhancements in the latest firmware, is there anything I can do (reset modem, restore factory defaults, call, wait, etc.) to get mine updated?
 
 
 
 
Connection Expert
EG
Posts: 43,212
Registered: ‎12-24-2003

Re: Motorola 5101 Firmware problem (update)


JCKelly wrote:
 
2) If I want the enhancements in the latest firmware, is there anything I can do (reset modem, restore factory defaults, call,
 
 
>>Try those first.
 
 
 
wait, etc.) to get mine updated?
 
 
>>That would be your last choice... :smileywink:
 

Visitor
Posts: 3
Registered: ‎05-15-2006

Re: Motorola 5101 Firmware problem (update)

Is this still an active issue?

The past two days my 5101 has had serious connection issues.  The status board shows no outages in my area.  I've been getting frequent disconnects where the lights will hang on either the "send" light or the "receive" light (mostly receive).  I will occasionally get on-line but it is very sporadic.  Last time I looked I believe my power levels were at either -3 or -6 (can't remember specifically).

Thanks,

Neil
Connection Expert
EG
Posts: 43,212
Registered: ‎12-24-2003

Re: Motorola 5101 Firmware problem (update)



salstrom wrote:
Is this still an active issue?

The past two days my 5101 has had serious connection issues.  The status board shows no outages in my area.  I've been getting frequent disconnects where the lights will hang on either the "send" light or the "receive" light (mostly receive).  I will occasionally get on-line but it is very sporadic.  Last time I looked I believe my power levels were at either -3 or -6 (can't remember specifically).

Thanks,

Neil


 
 
Post both the upstream power level and the SNR figures.
 
Post the modem's error log entries as well..
Visitor
Posts: 3
Registered: ‎05-15-2006

Re: Motorola 5101 Firmware problem (update)

D'oh!  Now that I'm home (modem was stuck on the blinking "recieve" until a power cycle) I noticed it was a SB5100 and not the 5101.  I guess this does not pertain to me.

I'll post the info just for posterity sake but feel free to move it to a different thread:

Software Version: SB5100-2.3.2.5-SCM01-NOSH
Hardware Version: 3
MIB Version: II
GUI Version: 1.0
VxWorks Version: 5.4

Downstream     Value
Frequency     567000000 Hz Locked
Signal to Noise Ratio     34 dB
Power Level     -4 dBmV

Upstream     Value
Channel ID     5
Frequency     25000000 Hz Ranged
Power Level     39 dBmV

2008-06-05 16:15:22     3-Critical     R004.0     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2008-06-05 16:14:50     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-06-05 16:14:07     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 16:14:00     3-Critical     T002.0     SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-05 16:14:00     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 16:13:51     3-Critical     T004.0     SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period
2008-06-05 16:13:50     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-06-05 16:13:37     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 16:13:11     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-06-05 16:12:28     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 16:12:21     3-Critical     T002.0     SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-05 16:12:21     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 16:12:21     3-Critical     T002.0     SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-05 16:12:20     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 16:12:18     3-Critical     T002.0     SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-05 16:12:18     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 16:12:16     3-Critical     T002.0     SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-05 16:12:16     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 16:12:15     3-Critical     T002.0     SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-05 16:12:15     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 16:12:10     3-Critical     R004.0     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2008-06-05 16:11:38     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-06-05 16:10:53     3-Critical     R004.0     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2008-06-05 16:10:21     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-06-05 16:09:39     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 16:09:39     3-Critical     T002.0     SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-05 16:09:38     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 16:09:38     3-Critical     T002.0     SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-05 16:09:37     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 16:09:36     3-Critical     T002.0     SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-05 16:09:36     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 16:09:35     3-Critical     T002.0     SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-05 16:09:35     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 16:09:34     3-Critical     T002.0     SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-05 16:09:34     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 16:09:34     3-Critical     T002.0     SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-05 16:09:33     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 16:09:32     3-Critical     T002.0     SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-05 16:09:31     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 16:09:31     3-Critical     T002.0     SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-05 16:09:31     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 16:09:30     3-Critical     T002.0     SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-05 16:09:27     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 16:09:26     3-Critical     T004.0     SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period
2008-06-05 16:09:23     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-06-05 16:09:06     3-Critical     T002.0     SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-05 16:09:01     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 16:08:46     3-Critical     R004.0     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2008-06-05 16:08:14     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-06-05 16:07:32     3-Critical     R004.0     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2008-06-05 16:06:59     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-06-05 16:06:17     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 16:05:56     3-Critical     R004.0     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2008-06-05 16:05:23     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-06-05 16:04:41     3-Critical     R004.0     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2008-06-05 16:04:09     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-06-05 16:03:24     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 16:03:15     3-Critical     T002.0     SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-05 16:03:15     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 16:03:14     3-Critical     T002.0     SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-05 16:03:14     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 16:03:14     3-Critical     T002.0     SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-05 16:03:14     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 16:03:10     3-Critical     T002.0     SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-05 16:03:10     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 16:03:09     3-Critical     T004.0     SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period
2008-06-05 16:02:52     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-06-05 16:02:11     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 16:02:11     3-Critical     T002.0     SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-05 16:02:10     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 16:02:10     3-Critical     T002.0     SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-05 16:02:09     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 16:02:08     3-Critical     T002.0     SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-05 16:02:08     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 16:02:07     3-Critical     T002.0     SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-05 16:02:06     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 16:02:06     3-Critical     T002.0     SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-05 16:02:06     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 16:02:03     3-Critical     T002.0     SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-05 16:02:02     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 16:02:02     3-Critical     T002.0     SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-05 16:02:01     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 16:01:57     3-Critical     T002.0     SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-05 16:01:57     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 16:01:44     3-Critical     R004.0     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2008-06-05 16:01:11     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-06-05 16:00:29     3-Critical     R004.0     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2008-06-05 15:59:57     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-06-05 15:59:15     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 15:59:13     3-Critical     T002.0     SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-05 15:59:12     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 15:59:11     3-Critical     T002.0     SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-05 15:59:10     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 15:59:06     3-Critical     T002.0     SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-05 15:59:06     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 15:59:04     3-Critical     T002.0     SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-05 15:59:03     3-Critical     T001.0     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-05 15:58:59     3-Critical     R005.0     Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-06-05 15:58:46     3-Critical     R002.0     No Ranging Response received - T3 time-out
2008-06-05 15:58:37     3-Critical     R004.0     Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
Connection Expert
EG
Posts: 43,212
Registered: ‎12-24-2003

Re: Motorola 5101 Firmware problem (update)

[ Edited ]
Well at the moment that they were measured, your signal stats were o/k although the SNR was a wee bit low.
 
The errors indicate a single lost sync event lasting approx. 17 minutes. Were those log entries observed right after you performed a manual powercycle of the modem ?


Message Edited by EG on 06-05-2008 10:11 PM
Visitor
Posts: 3
Registered: ‎05-15-2006

Re: Motorola 5101 Firmware problem (update)

Correct, those were just after a manual power cycle.  The modem had lost sync for the entire day however (until the manual sync).

As for the signal to noise, it has been hovering right around 34~35.  There are no splitters on the line...

As of this evening I have not had any disconnects.  I was wondering if it had anything to do with maintenance involvied with the upload speed increase I've read about.
Connection Expert
EG
Posts: 43,212
Registered: ‎12-24-2003

Re: Motorola 5101 Firmware problem (update)

[ Edited ]


salstrom wrote:
As of this evening I have not had any disconnects.  I was wondering if it had anything to do with maintenance involvied with the upload speed increase I've read about.

It's impossible for me to know that as I am a fellow subscriber, and not an employee :smileyhappy:
 
However, I can tell you that it shouldn't take 17 minutes for a modem to achieve block sync after a powercycle operation.


Message Edited by EG on 06-05-2008 10:17 PM
Recognized Contributor
Posts: 325
Registered: ‎04-07-2008

Re: Motorola 5101 Firmware problem (update)

My SB5101 was updated today:
Software Version: SB5101-2.6.2.0-SCM00-NOSH
Hardware Version: 1
MIB Version: II
GUI Version: 1.0
 
The Log shows:
2008-06-11 15:31:35 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out 1970-01-01 00:00:13 3-Critical D001.0 DHCP FAILED - Discover sent, no offer received 1970-01-01 00:00:03 6-Notice M571.1 Ethernet link up - ready to pass packets 2008-06-11 15:26:18 6-Notice E111.0 SW download Successful - Via NMS 2008-06-11 15:25:02 6-Notice E101.0 SW Download INIT - Via NMS 2008-06-10 08:06:42 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
Frequent Visitor
Posts: 2
Registered: ‎06-19-2008

Re: Motorola 5101 Firmware problem (update)

I believe my Motorola SB5101 needs help, as these log messages just appeared today:
 
2008-06-19 12:37:03 4-Error E104.0 SW Upgrade Failed Before Download - Server not Present
2008-06-19 12:35:24 6-Notice E101.0 SW Download INIT - Via NMS
 
Software Version: SB5101-2.4.1.5-SCM01-NOSH
Hardware Version: 1
MIB Version: II
GUI Version: 1.0
 
 
Connection Expert
EG
Posts: 43,212
Registered: ‎12-24-2003

Re: Motorola 5101 Firmware problem (update)

[ Edited ]


posthaste3 wrote:
I believe my Motorola SB5101 needs help, as these log messages just appeared today:
 
2008-06-19 12:37:03 4-Error E104.0 SW Upgrade Failed Before Download - Server not Present
2008-06-19 12:35:24 6-Notice E101.0 SW Download INIT - Via NMS
 
Software Version: SB5101-2.4.1.5-SCM01-NOSH
Hardware Version: 1
MIB Version: II
GUI Version: 1.0
 
 



Are you actually having any noticeable connectivity issues ?


Message Edited by EG on 06-19-2008 10:51 PM
Frequent Visitor
Posts: 2
Registered: ‎06-19-2008

Re: Motorola 5101 Firmware problem (update)

Not presently, but last night my speeds (16/2 Blast! Tier) were inconsistent. If I may ask a question, do you have the ability to push the the proper, and latest, firmware to my SB5101?
Connection Expert
EG
Posts: 43,212
Registered: ‎12-24-2003

Re: Motorola 5101 Firmware problem (update)

Split out to a separate thread as per request. Click above link to view it.

Frequent Visitor
Posts: 1
Registered: ‎05-08-2008

Re: Motorola 5101 Firmware problem (update)

I have a new surfboard 5101 and it does not have the latest firmware.  My log shows no attempt to download it.

It appears that the latest version may be:
  Software Version: SB5101-2.6.2.0-SCM00-NOSH

My modem is showing: 

  Software Version: SB5101-2.4.1.5-SCM01-NOSH
 
Can you please help me to be sure I have the correct config file as well as the latest firmware?

Thanks,
Sheila


Regular Contributor
Posts: 31
Registered: ‎02-22-2004

Re: Motorola 5101 Firmware problem (update)

Where do I go to learn how to check, update my firmware?  (I'm on a Mac).
There is no sticky or instruct  that I can see.  
Connection Expert
EG
Posts: 43,212
Registered: ‎12-24-2003

Re: Motorola 5101 Firmware problem (update)

[ Edited ]
Try this. Go to http://192.168.100.1  << clickable link.
 
Click on *Help*. It should be listed there.
 
You can only observe the current firmware load, you can not update it. Only Comcast can.


Message Edited by EG on 07-23-2008 06:03 PM
Regular Contributor
Posts: 31
Registered: ‎02-22-2004

Re: Motorola 5101 Firmware problem (update)

Thanks.  Ooops - I have an SB5120.  Could've sworn I had 5101.

OK - which is the better modem?  :smileyhappy:
Connection Expert
EG
Posts: 43,212
Registered: ‎12-24-2003

Re: Motorola 5101 Firmware problem (update)

Both are very good modems. The 5101 is more current.
Contributor
Posts: 12
Registered: ‎08-20-2008

Re: Motorola 5101 Firmware problem (update)

I have had a surfboard 5101 modem for about ten days. The firmware says it's at Software Version: SB5101-2.4.1.5-SCM01-NOSH
A tech at comcast said the version is correct and I should be able to get up to 8mbps with power bost but seldom get over 6.4 or so.
Is this version of the firmware correct, if not would an upgrade help with the speed? Here is what's in the modem logs
 
1970-01-01 00:01:39 3-Critical U001.0 No UCD's Received - Timeout
1970-01-01 00:01:29 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:57 3-Critical R004.0 Received Response to Broadcast Maintenance Request,  But no Unicast Maintenance o
1970-01-01 00:00:25 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:08 3-Critical R002.0 No Ranging Response received - T3 time-out
 
thanks
Connection Expert
Joe
Posts: 7,130
Registered: ‎06-30-2003

Re: Motorola 5101 Firmware problem (update)

Look like it
any logs with a time stamp
instead of 1970-01-01
now if you have windows XP and down tweaktry this
if you have vista it will not be needed
power boost is never at  full speed all the time
during heavy use it slow down
so 6.4 is good and may get better
Connection Expert
EG
Posts: 43,212
Registered: ‎12-24-2003

Re: Motorola 5101 Firmware problem (update)

[ Edited ]
Which speedtier are you actually subscribed to ?
 
It's not the version of firmware that is loaded into the modem that determines one's speeds, it's the config file.


Message Edited by EG on 08-20-2008 11:31 PM
Contributor
Posts: 12
Registered: ‎08-20-2008

Re: Motorola 5101 Firmware problem (update)

The rate is 39.95 per month, I believe that has a 6MB limit. However I thought it was actually a higher speed.
My old TW now comcast modem was about 6 to 7 years old (hate to admit it). So I decided that it was
time to get one of my own. I heard that the older modems don't work as well no that there is PB. But it
could be that PB is only available if you upgrade to the 8MB plan.
 
mike
Service Expert
Bartleby
Posts: 5,499
Registered: ‎11-10-2003

Re: Motorola 5101 Firmware problem (update)

mikearc,
 
The price you mentioned isn't high enough for the 8 MB tier--unless it's a promo rate of some sort.
 
FWIW, I'm on the 6 MB tier, and powerboost does apply.  Powerboost can give short bursts even over 8 MB. 
Here's a speedtest.net result showing that powerboost will provide speeds over 8 MB.  But note that powerboost is capacity constrained, and can't always be expected to perform consistently.
 
Contributor
Posts: 12
Registered: ‎08-20-2008

Re: Motorola 5101 Firmware problem (update)

Wow, That's awesome. I have never seen anything close to that speed. Thanks for the info. No, the 39.95 is not a promo rate.
For some reason I thought I was on a higher speed plan. Sounds like the comcast tech was right when he said that I should have
no problem getting up to 8 on occasion. Glad someone is getting it. Maybe I will call them instead of trying to talk via the 'chat' method.
 
mike
Recognized Contributor
Posts: 325
Registered: ‎04-07-2008

Re: Motorola 5101 Firmware problem (update)

[ Edited ]
My SB5101 downloaded new software today:
 
2008-09-12 10:01:18 6-Notice E102.0 SW Download INIT - Via Config file d11_m_sb5101_speedtier_c01.cm
 
Software Version: SB5101N-2.7.2.0-GA-00-NOSH
 
I did a few speed tests from http://speedtest.comcast.net/ and www.speedtest.net
My results have not changed from what they have been (I'm on the 8mbps plan).
 
 
I've only had it for about 20 minutes, but haven't noticed any changes.
I hope it fixes the issue with the modem being reset 2-3 times a day.
 
But it didn't fix the problem with web sites takeing longer than average to load.
That's been going on for about 3 weeks now.


Message Edited by FAUguy on 09-12-2008 10:25 AM
Recognized Contributor
Posts: 22
Registered: ‎09-09-2003

Re: Motorola 5101 Firmware problem (update)

Same problem here:
 
Software Version: SB5101-2.6.2.0-SCM00-NOSH
Hardware Version: 1
MIB Version: II
GUI Version: 1.0
 
2008-09-16 16:43:53 4-Error E107.0 SW upgrade Failed after download - Incompatible SW file
2008-09-16 16:43:51 6-Notice E102.0 SW Download INIT - Via Config file d11_m_sb5100_silver_c01.cm
Regular Contributor
Posts: 62
Registered: ‎02-08-2005

Re: Motorola 5101 Firmware problem (update)

I have the same problem with my SB5100 in Allen Park, MI (Taylor, MI headend):

Currently:
Software Version: SB5100-2.3.2.5-SCM01-NOSH
Hardware Version: 3
MIB Version: II
GUI Version: 1.0
VxWorks Version: 5.4

And the logs say it is trying to get a SB5101 file:

2008-09-16 16:02:17 4-Error E107.0 SW upgrade Failed after download - Incompatible SW file
2008-09-16 16:02:15 6-Notice E102.0 SW Download INIT - Via Config file d11_m_sb5101_speedtierextreme2tb25_c01.cm
1970-01-01 00:00:10 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2008-09-16 02:55:42 6-Notice E102.0 SW Download INIT - Via Config file d11_m_sb5101_speedtierextreme2tb25_c01.cm
1970-01-01 00:00:11 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2008-09-15 16:08:57 4-Error E107.0 SW upgrade Failed after download - Incompatible SW file
2008-09-15 16:08:54 6-Notice E102.0 SW Download INIT - Via Config file d11_m_sb5101_speedtierextreme2_c01.cm

etc etc for like 5 days.

Can anyone help??  Thanks!
JB