Motorola SB5101 firmware update?
-DC-
on me. When this happens, all the lights are on steady including the
activity light which blinks occasionally (but not rapidly like normal.)
The modem does not respond to pings or on its internal web interface
at 192.168.100.1 and there is no Internet connection. Only a
power-cycle fixes the issue, temporarily. All the signal strength
readings appear to be good, at least at the time I'm checking them.
I've rewired the coax in my house so that there is only one splitter in
the path to the modem. This seems to have helped some, but has not
solved the problem.
Doing some research on the Internet I've found I'm not the only one with
this problem. One site mentioned a firmware update from my current
SB5101-2.4.1.1-SCM14-NOSH to SB5101-2.4.2.0-SCM00-NOSH that supposedly
solves this issue. But Motorola doesn't provide this update on their
site and when I asked Comcast they said they have no update available!
How does one go about getting this new firmware?
Warren H
Which firmware version is used is chosen by the owner of the network
that the cablemodem is on; in this case, Comcast. When you unplug the
modem long enough that the CMTS can see the modem is off-line, when you
repower the modem, it will download a new config file, and if new
firmware is available, it will download it at that time.
But you're only guessing that there's a problem with the firmware you're
using. You almost certainly have the most current firmware that is being
used with your CMTS, so your guess that you have the wrong firmware, and
that's what's causing your problems is going to do nothing but distract
you from discovering what the real solution is.
The problem you describe could be as simple as a bad Ethernet cable
coming off the cablemodem. If you have a router, your router could be
having problems communicating with the modem. Or if you're connected
directly to the cablemodem, your NIC may be having problems. Or you just
may have a messed-up modem. The problem you describe is unlikely to be
on the coax side of the cablemodem.
Methodic troubleshooting to isolate the issue is the route to go at this
time. Swap-out each suspect part. Try a new cable. If you're using a
router, try connecting to the cablemodem directly with the current
cable, and then with a different, known-good cable. If you're not using
a router, borrow a router, or use a different computer. Do it with the
current cable, and a different known-good cable. If you're using a USB
connection to the cablemodem, get a NIC, and use Ethernet instead. (I
would not, however, suggest switching from Ethernet to USB as a
troubleshooting step. Going from USB to Ethernet eliminates a number of
points of failure, while going from Ethernet to USB introduces new
failure points.)
If you try all those things, and the problem still exists, then the next
step would be to get a new modem.
--
Warren H.
==========
Disclaimer: My views reflect those of myself, and not my
employer, my friends, nor (as she often tells me) my wife.
Any resemblance to the views of anybody living or dead is
coincidental. No animals were hurt in the writing of this
response -- unless you count my dog who desperately wants
to go outside now.
Maintain your landscape with Black & Decker:
http://www.holzemville.com/mall/blackanddecker
Dr Feelgood WA
"Warren H" <who...@hotmail.com> wrote in message
news:GqGdnd9a4d3FhJPb...@comcast.com...
How about router firmware? Any possibility that could cause such a
problem?
Rick Merrill
I have Software Version: SB5100-2.3.2.5-SCM01-NOSH in MA.
Does your modem log show any significant errors?
Have you pushed the Reset button on the modem at the problem times?
-DC-
Yes I've got errors in the modem's log file:
1970-01-01 00:00:11 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
1970-01-01 00:03:37 3-Critical D002.0 DHCP FAILED - Request sent, No
response
1970-01-01 00:03:30 3-Critical D001.0 DHCP FAILED - Discover sent, no
offer received
1970-01-01 00:02:38 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
1970-01-01 00:02:14 3-Critical D001.0 DHCP FAILED - Discover sent, no
offer received
2007-03-05 06:05:03 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2007-03-04 13:32:50 5-Warning D103.0 DHCP RENEW WARNING - Field invalid
in response
2007-03-03 16:44:51 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2007-03-01 01:32:50 5-Warning D103.0 DHCP RENEW WARNING - Field invalid
in response
..etc..
I haven't pressed the reset button, just power cycled.
-DC-
And you're assuming I haven't done any of these troubleshooting steps.
You're wrong.
The modem has been replaced, the cables have been replaced, my
computer's NIC works just fine, the router works, etc. There is no
obvious reason for the cable modem to just decide to lock up as stated
unless it's having issues communicating with Comcast (see log file I
posted in another msg.) Even then, it shouldn't require a power cycle
to reset.
Trust me, I've researched this thoroughly and have even had Comcast
techs out twice. Other people who have described this EXACT same
problem have said a firmware update fixed it. I'm ready to try it.
Comcast is clueless as to why it's happening.
Robert Heiling
>
> <snip>
>
> Yes I've got errors in the modem's log file:
>
> 1970-01-01 00:00:11 3-Critical D003.0 DHCP WARNING - Non-critical field
> invalid in response.
> 1970-01-01 00:03:37 3-Critical D002.0 DHCP FAILED - Request sent, No
> response
> 1970-01-01 00:03:30 3-Critical D001.0 DHCP FAILED - Discover sent, no
> offer received
> 1970-01-01 00:02:38 3-Critical R005.0 Started Unicast Maintenance
> Ranging - No Response received - T3 time-out
> 1970-01-01 00:02:14 3-Critical D001.0 DHCP FAILED - Discover sent, no
> offer received
> 2007-03-05 06:05:03 3-Critical R005.0 Started Unicast Maintenance
> Ranging - No Response received - T3 time-out
> 2007-03-04 13:32:50 5-Warning D103.0 DHCP RENEW WARNING - Field invalid
> in response
> 2007-03-03 16:44:51 3-Critical R005.0 Started Unicast Maintenance
> Ranging - No Response received - T3 time-out
> 2007-03-01 01:32:50 5-Warning D103.0 DHCP RENEW WARNING - Field invalid
> in response
>
> ..etc..
>
> I haven't pressed the reset button, just power cycled.
It might also be helpful to see the log record immediately after a fresh
power-up and before the boot information has rolled off the end of the log.
Bob
-DC-
See the dates that are 1970-01-01? Those are the times I had to
power-cycle. Here's the full log:
1970-01-01 00:00:11 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
1970-01-01 00:03:37 3-Critical D002.0 DHCP FAILED - Request sent, No
response
1970-01-01 00:03:30 3-Critical D001.0 DHCP FAILED - Discover sent, no
offer received
1970-01-01 00:02:38 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
1970-01-01 00:02:14 3-Critical D001.0 DHCP FAILED - Discover sent, no
offer received
2007-03-05 06:05:03 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2007-03-04 13:32:50 5-Warning D103.0 DHCP RENEW WARNING - Field invalid
in response
2007-03-03 16:44:51 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2007-03-01 01:32:50 5-Warning D103.0 DHCP RENEW WARNING - Field invalid
in response
2007-02-28 05:44:21 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
1970-01-01 00:00:15 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
1970-01-01 00:00:06 3-Critical R002.0 No Ranging Response received - T3
time-out
1970-01-01 00:00:11 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2007-02-24 15:47:19 3-Critical D001.0 DHCP FAILED - Discover sent, no
offer received
2007-02-24 15:47:04 3-Critical T001.0 SYNC Timing Synchronization
failure - Failed to acquire QAM/QPSK symbol timing
2007-02-24 15:43:23 3-Critical T002.0 SYNC Timing Synchronization
failure - Failed to acquire FEC framing
2007-02-24 15:43:22 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance o
2007-02-24 15:43:22 3-Critical T002.0 SYNC Timing Synchronization
failure - Failed to acquire FEC framing
1970-01-01 00:00:14 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2007-02-21 16:09:20 3-Critical R002.0 No Ranging Response received - T3
time-out
2007-02-21 16:08:29 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance o
2007-02-21 16:07:56 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2007-02-20 19:50:08 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2007-02-20 19:49:58 3-Critical R002.0 No Ranging Response received - T3
time-out
2007-02-20 19:48:08 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance o
2007-02-20 19:47:35 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2007-02-20 18:07:49 5-Warning D103.0 DHCP RENEW WARNING - Field invalid
in response
2007-02-20 17:45:52 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2007-02-20 17:44:31 3-Critical I002.0 REG RSP not received
1970-01-01 00:00:31 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
1970-01-01 00:00:30 3-Critical D002.0 DHCP FAILED - Request sent, No
response
1970-01-01 00:00:23 3-Critical D001.0 DHCP FAILED - Discover sent, no
offer received
1970-01-01 00:00:14 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2007-02-20 17:24:45 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2007-02-17 10:10:08 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2007-02-17 10:09:58 3-Critical T001.0 SYNC Timing Synchronization
failure - Failed to acquire QAM/QPSK symbol timing
2007-02-17 10:09:27 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance o
2007-02-17 10:09:27 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.
2007-02-15 20:57:58 3-Critical T001.0 SYNC Timing Synchronization
failure - Failed to acquire QAM/QPSK symbol timing
2007-02-15 20:57:05 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance o
2007-02-15 20:57:05 3-Critical T002.0 SYNC Timing Synchronization
failure - Failed to acquire FEC framing
2007-02-14 19:36:25 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2007-02-12 18:17:35 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2007-02-12 18:17:24 3-Critical T001.0 SYNC Timing Synchronization
failure - Failed to acquire QAM/QPSK symbol timing
2007-02-12 18:10:06 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance o
2007-02-12 18:10:06 3-Critical T002.0 SYNC Timing Synchronization
failure - Failed to acquire FEC framing
1970-01-01 00:00:18 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
1970-01-01 00:00:07 3-Critical R002.0 No Ranging Response received - T3
time-out
1970-01-01 00:00:16 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2007-02-09 03:08:03 3-Critical R002.0 No Ranging Response received - T3
time-out
2007-02-09 03:06:46 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance o
2007-02-09 03:06:14 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2007-02-09 02:24:09 5-Warning D103.0 DHCP RENEW WARNING - Field invalid
in response
2007-02-08 11:03:29 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2007-02-08 10:55:19 3-Critical T002.0 SYNC Timing Synchronization
failure - Failed to acquire FEC framing
2007-02-08 10:53:46 3-Critical T001.0 SYNC Timing Synchronization
failure - Failed to acquire QAM/QPSK symbol timing
2007-02-08 10:53:46 3-Critical T002.0 SYNC Timing Synchronization
failure - Failed to acquire FEC framing
2007-02-08 02:59:11 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
1970-01-01 00:00:12 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2007-02-04 11:34:18 3-Critical T002.0 SYNC Timing Synchronization
failure - Failed to acquire FEC framing
2007-02-04 11:34:06 3-Critical T001.0 SYNC Timing Synchronization
failure - Failed to acquire QAM/QPSK symbol timing
2007-02-04 11:32:01 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance o
2007-02-04 11:32:01 3-Critical T002.0 SYNC Timing Synchronization
failure - Failed to acquire FEC framing
2007-02-04 11:20:40 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2007-02-04 11:20:28 3-Critical T001.0 SYNC Timing Synchronization
failure - Failed to acquire QAM/QPSK symbol timing
2007-02-04 11:20:04 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance o
2007-02-04 11:20:04 3-Critical T002.0 SYNC Timing Synchronization
failure - Failed to acquire FEC framing
2007-02-04 05:56:39 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
1970-01-01 00:00:10 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
1970-01-01 00:06:10 3-Critical D002.0 DHCP FAILED - Request sent, No
response
1970-01-01 00:05:46 3-Critical D001.0 DHCP FAILED - Discover sent, no
offer received
2007-02-02 06:44:32 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2007-02-02 06:44:02 3-Critical R002.0 No Ranging Response received - T3
time-out
2007-02-02 06:43:08 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance o
2007-02-02 06:42:36 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2007-02-02 06:39:23 3-Critical I002.0 REG RSP not received
2007-02-02 06:39:16 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2007-02-02 06:38:58 3-Critical R002.0 No Ranging Response received - T3
time-out
2007-02-02 06:38:40 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance o
2007-02-02 06:38:07 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2007-02-02 06:12:45 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2007-02-02 06:12:36 3-Critical R002.0 No Ranging Response received - T3
time-out
2007-02-02 06:12:31 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance o
2007-02-02 06:11:59 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2007-02-02 06:07:14 3-Critical I002.0 REG RSP not received
2007-02-02 06:07:08 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2007-02-02 06:06:58 3-Critical R002.0 No Ranging Response received - T3
time-out
2007-02-02 06:06:53 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance o
2007-02-02 06:06:20 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2007-02-02 06:03:09 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2007-02-02 06:02:50 3-Critical R002.0
Rick Merrill
Have the cables to the pole been replaced? Do you split off TV with
filter? Are your in house cables up to date? Are you in an apartment or
a single family house?
To get my wires to pole replaced I had to subscribe to Com cast Phone!
Robert Heiling
>
> Robert Heiling wrote:
> > -DC- wrote:
> >> <snip>
> >>
> >> Yes I've got errors in the modem's log file:
> >>
> >> 1970-01-01 00:00:11 3-Critical D003.0 DHCP WARNING - Non-critical field
> >> invalid in response.
> >> 1970-01-01 00:03:37 3-Critical D002.0 DHCP FAILED - Request sent, No
> >> Ranging - No Response received - T3 time-out
> >> 2007-03-01 01:32:50 5-Warning D103.0 DHCP RENEW WARNING - Field invalid
> >> in response
> >>
> >> ..etc..
> >>
> >> I haven't pressed the reset button, just power cycled.
> >
> > It might also be helpful to see the log record immediately after a fresh
> > power-up and before the boot information has rolled off the end of the log.
> >
> > Bob
>
> See the dates that are 1970-01-01? Those are the times I had to
> power-cycle. Here's the full log:
>
> 1970-01-01 00:00:11 3-Critical D003.0 DHCP WARNING - Non-critical field
> invalid in response.
No, that's not a booting log at all and the 1970-01-01 is simply the empty time
counter before the time is gotten from the timeserver. You have to be willing to
powercycle and post that log. Also post your Signals: Downstream signal to noise
rate and Power level and Upstream Power Level.
Bob
Bob F.
>>
>> The modem has been replaced, the cables have been replaced, my computer's
>> NIC works just fine, the router works, etc. There is no obvious reason
>> for the cable modem to just decide to lock up as stated unless it's
>> having issues communicating with Comcast (see log file I posted in
>> another msg.) Even then, it shouldn't require a power cycle to reset.
When you replaced the modem, you did call Comcast and give them the new MAC
address...didn't you?
-DC-
Comcast replaced the modem, so yes.
-DC-
Cables to the pole have not been replaced. Actually, there is no pole
as it's all underground cable. The splitter in use is a typical
high-quality cable TV splitter. The wiring going from outside the house
to the first splitter and to the modem is RG6. The rest of the house is
RG59. It's a single family house.
Rewiring with RG6 cable to the first splitter and to the modem helped
reduce the frequency of this problem. But there are several other
splitters in the house and I have no way to replace them all as many are
in the walls.
-DC-
Those log entries stay even when the modem is power cycled, so the boot
information is not rolling off the end of the log. You have some other
way to show the boot log?
Signal info:
Downstream Value
Frequency 711000000 Hz
Signal To Noise Ratio 39.1 dB
Power Level 4.5 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 6
Frequency 27800000 Hz
Power 41.8 dBmV
Robert Heiling
It should be clearing the log and starting completely over. If you've already
been keeping the power off for up to a minute before plugging power back in at
the modem, then a reset would seem to be in order. That's on the Configuration
Page and called Reset All Defaults. You're looking for a full boot so that you
can see such things as what Config file was loaded. That will also insure that
the proper firmware gets loaded if it isn't up to date.
> Signal info:
>
> Downstream Value
> Frequency 711000000 Hz
> Signal To Noise Ratio 39.1 dB
> Power Level 4.5 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 6
> Frequency 27800000 Hz
> Power 41.8 dBmV
Those all look just fine.
Bob
-DC-
Ok I selected Restore Defaults and then immediately rebooted the modem.
It took a minute for it to come back up but once it did this was the
log file:
1970-01-01 00:01:32 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
1970-01-01 00:01:25 3-Critical R002.0 No Ranging Response received - T3
time-out
1970-01-01 00:01:18 3-Critical T001.0 SYNC Timing Synchronization
failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:04 3-Critical T002.0 SYNC Timing Synchronization
failure - Failed to acquire FEC framing
1970-01-01 00:01:03 3-Critical T001.0 SYNC Timing Synchronization
failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:26 3-Critical T002.0 SYNC Timing Synchronization
failure - Failed to acquire FEC framing
1970-01-01 00:00:25 3-Critical T001.0 SYNC Timing Synchronization
failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:19 3-Critical T002.0 SYNC Timing Synchronization
failure - Failed to acquire FEC framing
1970-01-01 00:00:19 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:08 3-Critical T002.0 SYNC Timing Synchronization
failure - Failed to acquire FEC framing
1970-01-01 00:00:08 3-Critical T001.0 SYNC Timing Synchronization
Robert Heiling
I suppose it's always possible that the portions of the log at the beginning
from boot onwards are being quickly overwritten by an excessive number of
messages like those above. What argues against that thought is that the modem
should have been served with the time by then(even though Comcast has been an
hour off since DST). That would mean that the above log entries should have a
reasonable date/time value and they have reverted to the default instead. That
doesn't seem right.
My vote is that you have a faulty modem and need to replace it. I think you said
earlier that it was a Comcast rental, so you can simply go to their local office
and swap it over the counter if that's convenient for you. Perhaps you should
try an SB5120 this time.
Bob
-DC-
I don't think these "boot log" entries that you speak of exist for this
modem. If you'll notice, the log file is considerably shorter than the
previous one I posted indicating that it has been cleared.
Why should I replace my modem a third time? It's unlikely I've had two
bad ones. Plus my original was a different model altogether (but had
the same problem.)
My vote is for trying a firmware update. Fixing bugs/improving
performance is exactly what firmware updates do! Guess I'll have to try
to get it from Motorola.
Here's a related thread that describes my problem and claims a firmware
update will fix it (see page 2):
http://hardware.mcse.ms/showthread.php?s=604e90c11a9af4d51495492e376de42e&threadid=264831&perpage=10&pagenumber=1
Dr Feelgood WA
"-DC-" <ha...@yeah.right> wrote in message
news:asydnVuvNowLvJLb...@comcast.com...
So you believe some idiot you don't know because he posted bad
information in another forum? Take your damn complaint to that forum if
they are so damn great.
You need to get it in your head that Comcast sets which firmware your
modem runs on their network. If everyone else with that same model modem
is not having problems with the Comcast supplied firmware what makes you
so special they should load a different one for you? Just because a
service tech changed out your modem doesn't mean he didn't give you
another bad modem. They remove them from one house and put them in
another. Unless he installed a brand new modem your chances of getting a
bad one off their trucks is the same as everyone else's chances. Even
new modems can be bad. Some service techs are downright physical with
modems tossing them instead of placing them neatly on truck shelves.
Someone in a warehouse may have dropped some modems off of a forklift or
cart while shelving them. The fact is you just have no way of knowing.
Warren H
> Why should I replace my modem a third time? It's unlikely I've had
> two bad ones. Plus my original was a different model altogether (but
> had the same problem.)
>
> My vote is for trying a firmware update. Fixing bugs/improving
> performance is exactly what firmware updates do! Guess I'll have to
> try to get it from Motorola.
If your original modem was a different model, and had the same problem,
then why do you still think it's a firmware issue?
The firmware is only made available to licensed system operators. You
are not Comcast, so you will not be able to get the firmware. Even if
you did get it, you would need to set-up a tftp server on an HFC network
to load it onto your cablemodem. And then once you reconnect to Comcast,
your modem will simply re-download the correct firmware -- the one
you're already using -- and reinstall it. The firmware is chosen by the
system operator, not the end user.
The problem is *not* your modem's firmware, and even if it was, you
cannot change it.
--
Warren H.
==========
Disclaimer: My views reflect those of myself, and not my
employer, my friends, nor (as she often tells me) my wife.
Any resemblance to the views of anybody living or dead is
coincidental. No animals were hurt in the writing of this
response -- unless you count my dog who desperately wants
to go outside now.
Maintain your landscape with Black & Decker:
http://www.holzemville.com/mall/blackanddecker
Robert Heiling
*All* modems go through a certain sequence of steps during the bootup process,
if they are functioning properly. That one is obviously failing. It should have
been served the rime and retained it so that subsequenet log entries would be
stamped 2007-03-31 etc.
> Why should I replace my modem a third time?
Don't if you don't want to. If it's bad, it needs to be replaced, but that's
your problem and your decision.
> It's unlikely I've had two bad ones.
From the same physical source and the same batch possibly?
> Plus my original was a different model altogether (but had
> the same problem.)
What to you mean by "same"? A lot of problems look the same on the surface.
> My vote is for trying a firmware update. Fixing bugs/improving
> performance is exactly what firmware updates do! Guess I'll have to try
> to get it from Motorola.
More than one person has explained that you that you have zero control over the
firmware.
> Here's a related thread that describes my problem and claims a firmware
> update will fix it (see page 2):
> http://hardware.mcse.ms/showthread.php?s=604e90c11a9af4d51495492e376de42e&threadid=264831&perpage=10&pagenumber=1
It does resemble your situation, but he had no control over firmware either. so
be careful what you believe. It looks as his was failing also and that might be
a common failure mode although I honestly don't know that for a fact.
In any case, the SB5120 uses a different chipset which could make a subtle
difference in regard to hangs.
Bob
-DC-
> On Sat, 31 Mar 2007 09:22:32 -0700, -DC- <ha...@yeah.right>, you wrote:
>
>>>> Doing some research on the Internet I've found I'm not the only one
>>>> with this problem. One site mentioned a firmware update from my
>>>> current SB5101-2.4.1.1-SCM14-NOSH to SB5101-2.4.2.0-SCM00-NOSH that
>>>> supposedly solves this issue. But Motorola doesn't provide this
>>>> update on their site and when I asked Comcast they said they have no
>>>> update available!
>>>>
>>>> How does one go about getting this new firmware?
>
> Software Version: SB5101-2.4.1.5-SCM01-NOSH
> Hardware Version: 1
> MIB Version: II
> GUI Version: 1.0
And even that version is newer than mine. Gee, so much for the theory
that Comcast pushes out the same firmware to everyone.
-DC-
How is it "obviously failing?"
>> Why should I replace my modem a third time?
>
> Don't if you don't want to. If it's bad, it needs to be replaced, but that's
> your problem and your decision.
>
>> It's unlikely I've had two bad ones.
>
> From the same physical source and the same batch possibly?
They weren't even the same brand.
>> Plus my original was a different model altogether (but had
>> the same problem.)
>
> What to you mean by "same"? A lot of problems look the same on the surface.
"Same" as in modem occasionally locks up and has to be power-cycled.
>> My vote is for trying a firmware update. Fixing bugs/improving
>> performance is exactly what firmware updates do! Guess I'll have to try
>> to get it from Motorola.
>
> More than one person has explained that you that you have zero control over the
> firmware.
Perhaps.
>> Here's a related thread that describes my problem and claims a firmware
>> update will fix it (see page 2):
>> http://hardware.mcse.ms/showthread.php?s=604e90c11a9af4d51495492e376de42e&threadid=264831&perpage=10&pagenumber=1
>
> It does resemble your situation, but he had no control over firmware either. so
> be careful what you believe. It looks as his was failing also and that might be
> a common failure mode although I honestly don't know that for a fact.
>
> In any case, the SB5120 uses a different chipset which could make a subtle
> difference in regard to hangs.
I don't think the modem is failing. As I stated in my original post,
upgrading the wiring (RG6) and removing splitters helped the situation
considerably. All my signal readings from the modem are normal. But
the problem still persists, just less frequently now.
Robert Heiling
I'm not willing to sit here and argue with you and will bow out now. My own
projects are calling.
Bob
Dr Feelgood WA
"-DC-" <ha...@yeah.right> wrote in message
Hey stupid! Comcast has bought out many different cable franchises in
many areas and in some cases they use what the physical system supports.
This is a big country in case you are to stupid to know that already.
Firmware that works on one system won't on another.
So much for the idea anyone could get new information into that closed
retarded brain of yours.
-DC-
Do you feel better now? Is your ego boosted on your otherwise boring
weekend?
I'm really in awe of smart people like you. You know so much. That
must be why you don't have a solution to this issue.
-DC-
Good luck with them!
Dr Feelgood WA
"-DC-" <ha...@yeah.right> wrote in message
You have been given a solution by myself and several others here. This
being your special day I do apologize for pointing out you mental
defects. There are two possible causes for the problem you are
experiencing.
1 - bad modem
2 - faulty cable somewhere between your modem and where it connects to
the distribution point.
What the problem is NOT is your firmware. Stamp that fact onto a sledge
hammer and beat it into that fat but not to bright head of yours and you
will be on the way to a solution.
The readings you posted were in the good range. That would make the
modem highly suspect. Especially because it totally locks up and your
logs indicate a problem with it accepting the correct information as
displayed by it's inability to even accept the correct date and hold it.
There is a possibility of an intermittent cable problem caused by wind,
rain, or other acts of God or some mythical imp. The only other
possibility I see would be a cable amplifier going bad and there is no
indication you are running an amplifier. If a Comcast system cable
amplifier is involved it would be at the distribution point and everyone
else with a connection off of that point would have the same problem so
Comcast would know about it already.
Enjoy your special day. :)
Warren H
> AuldPhart wrote:
>> -DC- wrote:
>>
>>>>> Doing some research on the Internet I've found I'm not the only
>>>>> one with this problem. One site mentioned a firmware update from
>>>>> my current SB5101-2.4.1.1-SCM14-NOSH to SB5101-2.4.2.0-SCM00-NOSH
>>>>> that supposedly solves this issue. But Motorola doesn't provide
>>>>> this update on their site and when I asked Comcast they said they
>>>>> have no update available!
>>>>>
>>>>> How does one go about getting this new firmware?
>> This is what I get with my SB5101.
>>
>> Software Version: SB5101-2.4.1.5-SCM01-NOSH
>> Hardware Version: 1
>> MIB Version: II
>> GUI Version: 1.0
>
> And even that version is newer than mine. Gee, so much for the theory
> that Comcast pushes out the same firmware to everyone.
>
No one said anything like that.
However, everyone connected to your CMTS with the same modem as you have
will have the same firmware pushed to them. You don't get to pick what
firmware is pushed. Whoever loads the CMTS gets to decide. And even if
you did manage to install a different firmware on your modem, it won't
take long before the CMTS simply re-pushes what it believes is the
correct firmware to your modem.
If the firmware that is being TFPT'd to your modem is incorrect, then
everyone in your area with the same modem is getting the same firmware,
and many, if not all of them, will be having problems similar to what
you're having.
But you've stated that you had the same problem even with a different
modem. If we assume that you're right about it being a firmware issue,
then was the same problem a firmware issue, too? If so, what do you
think the odds are that two different modems types have the wrong
firmware in your area? That would mean even more people having the same
problem, and would be even more obvious to the network admins.
You don't have a firmware problem. For how long do you want to waste
your time continuing down this incorrect path? You're not going to ever
reach a resolution to your problem if you continue with the erroneous
belief that you have a firmware issue. But if you want to dig in, and
insist that we're all wrong, you're welcome to waste all the time of
yours that you want.
Just don't expect to get a different answer in this forum. Your
incorrect assumption is not going to get affirmation here. We tried to
help you with your problem, but you're more interested in affirmation
than in assistance. And as long as you continue to take this position,
you're just wasting your time, and the problem is not getting fixed.
-DC-
The point is, I've done nearly everything I can do myself. I've had
Comcast out twice. Replaced the modem. Signals are all good. Replaced
splitters & upgraded wiring which helped (and leads me to believe this
is an issue between the ISP and cable modem, NOT my router/LAN.) Yet
the problem still persists. The fact that it's intermittent makes it
very difficult to troubleshoot, especially when it's not happening at
the time the tech decides to show up. Then I see a message in a forum
that claims my firmware version is known to lock up, which is exactly
what I'm experiencing. And I know firmware updates are free and easy, I
figure it's worth a shot. Apparently it's not that simple. Comcast
should be using the latest firmware available from the manufacturer, but
that's my belief and obviously not theirs. I never claimed it WOULD
solve the problem, only that it's an easy step to try in the
troubleshooting process. For that I get flamed (whatever!)
I'm not the only one with this problem. This post describes exactly
what I'm experiencing:
http://groups.google.com/group/alt.online-service.comcast/browse_thread/thread/95c8ed64e215a4a1/a63411b67cb1919e?lnk=st&q=sb5101+locks+up&rnum=3&hl=en#a63411b67cb1919e
This forum has definitely shown me one thing: nobody here knows why it's
happening either. And the online disinhibition effect reigns supreme!
Dr Feelgood WA
"-DC-" <ha...@yeah.right> wrote in message
<snip>
> I'm not the only one with this problem. This post describes exactly
> what I'm experiencing:
> http://groups.google.com/group/alt.online-service.comcast/browse_thread/thread/95c8ed64e215a4a1/a63411b67cb1919e?lnk=st&q=sb5101+locks+up&rnum=3&hl=en#a63411b67cb1919e
>
> This forum has definitely shown me one thing: nobody here knows why
> it's happening either. And the online disinhibition effect reigns
> supreme!
What is the one thing everyone reporting this problem have in common?
A- They are all you?
B- They are all over 10 years of age?
C- They all are under 10 years of age?
D- They are all using Motorola 5101 modems?
If the answer is D you need to try another modem that is not a Motorola
5101.
The fact your activity light isn't blinking should clue you to a problem
with the modem or the modem is not getting a signal from the system. The
stats you posted show you have a good signal. The fact everyone else
reporting this problem is using the same modem is a major clue.
You might want to ask Comcast if there are several Larry's on your node
also.
Warren H
> Comcast should be using the latest firmware available from the
> manufacturer, but that's my belief and obviously not theirs.
Your belief is wrong.
There aren't people at Motorola working in a vacuum writing new firmware
for products they thought were finished when they went out the door. The
engineers at Motorola are working in conjunction with the engineers at
the various cable companies identifying problems that are specific to
each network. The firmware that came out last week may resolve a problem
with a specific system, but for another system that wasn't being looked
at when the firmware was developed, it could cause a huge problem.
This isn't a political issue. Starting a campaign to direct Comcast to
use a specific firmware based on what some end user thinks solved a
problem that is almost like the one you're having isn't going to resolve
your problem.
There have been numerous suggestions on things you can do to better your
chances of a resolution to your problem, but you're so hung-up on this
one guy's uninformed opinion that a different firmware version is the
Holy Grail that those suggestions have fallen on deaf ears.
Continue believing whatever you want, but those beliefs aren't going to
fix your problem. And complaining that people in this group aren't smart
enough to just affirm your beliefs, and agree with you isn't helping,
either.
In the link you provided, the person having a problem mentions that it
happens sometimes overnight. That calls to mind one other very important
thing to check: Your PC's power management settings. Go into the System
control panel, choose your network adapter, and check it's properties.
If there is a Power Management tab, make sure that the box that allows
the device to be turned off to save power is not checked. From the OS's
view point, data flowing will not stop power management from shutting
things down for inactivity. Inactivity is defined by a lack of keyboard
or mouse movements.
Is this the problem you're having? We don't know. You didn't provide
enough information. The guy in the post you linked to didn't provide
enough information, either. But his description of a similar problem to
the one you're having suggests another place to look. But his specific
problem is unlikely to be the same as the specific problem you're
having. (And I didn't see anything at that link that even suggested that
a firmware update solved anything.)
The problem you originally described strongly suggests that the problem
is between the modem and your PC, and not in the HFC network. But the
devil is in the details, and while you've provided more details than
most people provide, the only thing certain is that further
troubleshooting is required. I'll say that again. Further
troubleshooting is required.
You've been given more than enough ideas in this forum as to things you
can observe while doing that troubleshooting. Stomping your feet, and
saying that you've already done enough troubleshooting, and that you
believe that you need a magic bullet of some random firmware update has
caused you to waste a lot of time.
Go back and re-read all the good advice you were given. Continuing to be
hung-up on this firmware idea has already cost you time and energy.
Don't let it continue to waste your time and energy. And if you can't be
bothered to go back and do the troubleshooting that people suggested,
just go away. Of course we don't have a magic answer for you. You
haven't done your part by following-up on our suggestions, and that's
your biggest problem right now.
Dr Feelgood WA
If I disconnect my Ethernet cable from my modem the WAN activity light
still blinks. If I understand the OP correctly he has no indication of
WAN activity when experiencing his problem. I believe that would
indicate either a bad chip in the modem or a loss of signal from the
Comcast side of the modem. Am I missing something here?
"Warren H" <who...@hotmail.com> wrote in message
news:FfWdnSb03t0cJ4zb...@comcast.com...
-DC-
Warren: You're beating a dead horse. Apparently you didn't read my last
post where I said I never claimed a firmware update would solve the
problem. Yet you keep bringing it up as if I had. Pointless.
Furthermore, you apparently have no idea what different versions of each
firmware have fixed, so how would you know? You don't.
And this isn't a PC power management issue, I can assure you of that.
Do you even know for a fact that this would be a problem or are you just
guessing?
It looks like I've exhausted all the supposed knowledge here. Maybe
I'll get yet another new modem just so I can come back and say "hey, it
didn't work! Nice guess!"
Dr Feelgood WA
"-DC-" <ha...@yeah.right> wrote in message
> It looks like I've exhausted all the supposed knowledge here. Maybe
> I'll get yet another new modem just so I can come back and say "hey,
> it didn't work! Nice guess!"
>
You are correct. No one here seems to be a specialist in teaching those
unwilling to learn and we are not magical so we can't diagnose and fix
your problems without the proper information that you seem to stupid to
provide. Several of us have actually tried to help you but you are STUCK
ON STUPID!
With that attitude I'm sure you will get the replies you deserve KID!
Dr Feelgood WA
news:0ie5135no4hr9p2r7...@4ax.com...
> In my area, between 7pm and 10:30 pm, my download speed drops to
> 120kB/sec. Most of the other times I average around 800kB/sec, with
> hit over 1mB/sec. I tried to ask CC chat and their only answer was
> network overload.
The time frame tells you there are Larry's* on your node so when you hit
peak hours the node just can't handle the load.
*Larry's
1-download hogs**, thieves, welfare rats, cheaters, selfish antisocial
uneducated momma's boys or daddy's girls.
2- Larry's respect nothing and no one but demand everything they can get
their grubby paws on as long as it's free or heavily discounted.. These
are the people you see eating the free handouts in grocery stores in
volumes equal to full meals, cheating on their taxes, driving as if the
road is their private raceway & sending the majority of spam.
3- Larry's of the world are that group known to bypass utility meters,
siphon gas from the cars in their neighborhoods & steal anything not
securely bolted down.
Larry's will never admit they have ever done anything wrong as anything
they do, take or acquire is their just due because they grace the world
with their existence.
**download hogs
1- Idiots that feel they must use maximum bandwidth because " they" are
paying for it. Being a responsible citizen is the last thing these
idiots would ever consider. Usually someone else is paying their bills
as they feel they are too good to work for a living.
-DC-
Someone who resorts to flaming is going to lecture about attitude? LOL.
Your ego and immaturity never ends.
-DC-
> 120kB/sec. Most of the other times I average around 800kB/sec, with
> hit over 1mB/sec. I tried to ask CC chat and their only answer was
> my router, my computer, everything was my fault. When I pointed out
> it never happen until CC took over for RR 3 months ago, then they said
> I would have to call tech support when it happen.
>
> Another friend kept having problems staying connected. He finally had
> to complain to the city after 4 request to CC produced no results.
> After he called the city, 4 trucks showed up in his neighborhood and
> CC finally found a major equipment problem in one of the main routers
> in his area. After they fix that, his problems went away. Again, they
> kept trying to blame his software and equipment.
>
> If your city has a complaint depart that overseas the CC service, you
> might try that route.
Welcome to "customer service" in the 21st century. As long as the
customer keeps paying, that's what they'll keep getting.
Dr. Feelgood Tommy Lee wannabe probably works for them.
Dr Feelgood WA
"-DC-" <ha...@yeah.right> wrote in message
You started the flaming when no one would support your stupid claim that
firmware was the cure all of all internet connection problems. I'm
simply replying in kind asshole!
Actually my reply to you was being kind as you have demonstrated you are
well beyond stupid in the ignorance category. Come back if you ever
graduate from pre-school.
You may now continue your tantrum.
Dr Feelgood WA
"-DC-" <ha...@yeah.right> wrote in message
And this asshole "-DC-" that is stuck on stupid will ensure you never
solve your problem if he has his way.
Pat Cook
"-DC-" <ha...@yeah.right> wrote in message
> Dr Feelgood WA wrote:
>> "-DC-" <ha...@yeah.right> wrote in message
>> news:CMOdnUegYveFSozb...@comcast.com...
>
> Someone who resorts to flaming is going to lecture about attitude? LOL.
> Your ego and immaturity never ends.
Apparently neither does your stupidity and UNWILLINGNESS TO LEARN BY
LISTENING to what others - WITH FAR MORE EXPERIENCE THAN YOU I might add -
are trying to tell you so you can PROPERLY troubleshoot your problem and
take the proper steps to correct it.
I'd HATE to hear what you've told the Comcast techies when they were at your
home.
Don't get me wrong. I'm no fan of Dr. Feelgood WA either as he and I have
been known to disagree and on occasion have a few go-rounds. But YOU OTOH
DC TAKE THE CAKE.
Just when I was beginning to think people were incapable of getting any more
stupider....
JMHO....
Cheers :D
Pat Cook
Denver, Colorado
Pat Cook
"Dr Feelgood WA" <drfeel...@comcast.net> wrote in message > Actually my
> well beyond stupid in the ignorance category. Come back if you ever
> graduate from pre-school.
Hey Doc....Have you any idea what you're asking of him to do?
Remember this is someone who has yet to PROVE his so-called "claims" AND
back that up by trying a DIFFERENT brand of modem (Scientific Atlantis comes
to mind here as that's what I've got) and its firmware.
And this is to say NOTHING about demonstrating some knowledge of proper
troubleshooting.
> You may now continue your tantrum.
Throwing tantrums is apparently all he's good at.
JMO...
Pat Cook
> 120kB/sec. Most of the other times I average around 800kB/sec, with
> hit over 1mB/sec. I tried to ask CC chat and their only answer was
> network overload. They tried to tell me it was my software, spyware,
> my router, my computer, everything was my fault. When I pointed out
> it never happen until CC took over for RR 3 months ago, then they said
> I would have to call tech support when it happen.
Well the above could be caused by any number of things INCLUDING software,
spyware, even malware (Especially when it's badly coded) so that assumption
by the chat person is fairly easy to make.
But that's NOT what we're talking about in this thread. *Hint....Hint* :D
> Another friend kept having problems staying connected. He finally had
> to complain to the city after 4 request to CC produced no results.
> After he called the city, 4 trucks showed up in his neighborhood and
> CC finally found a major equipment problem in one of the main routers
> in his area. After they fix that, his problems went away. Again, they
> kept trying to blame his software and equipment.
Things break. But it costs them more $$$ to dig up the ground if they only
get ONE trouble call. Now if an entire neighborhood called....
> If your city has a complaint depart that overseas the CC service, you
> might try that route.
See above.