Motorola sb5101 firmware update

Log in or register to post comments. Last post. Thanks in advance Sincerely, W. David Taylor. There's a few different ways. Heres a couple of suggestions Method 1 Put the commands into the modem config file. Haha yes I know what you mean. I know what you mean. Unfortunately the Moto's do not have a similar feature.

Free YouTube Downloader. IObit Uninstaller. Internet Download Manager. Advanced SystemCare Free. VLC Media Player. MacX YouTube Downloader. Microsoft Office YTD Video Downloader. Adobe Photoshop CC. VirtualDJ Avast Free Security. WhatsApp Messenger.

Talking Tom Cat. Clash of Clans. Subway Surfers. TubeMate 3. I would not, however, suggest switching from Ethernet to USB as a troubleshooting step. If you try all those things, and the problem still exists, then the next step would be to get a new modem.

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. I have Software Version: SB Does your modem log show any significant errors?

Have you pushed the Reset button on the modem at the problem times? Yes I've got errors in the modem's log file: 3-Critical D I haven't pressed the reset button, just power cycled. 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. I'm ready to try it. Comcast is clueless as to why it's happening. 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. See the dates that are ? Those are the times I had to power-cycle. Here's the full log:.

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! No, that's not a booting log at all and the 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. When you replaced the modem, you did call Comcast and give them the new MAC address 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 RG 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. 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? 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.

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. 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: 3-Critical D 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 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 SB this time. 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. Guess I'll have to try to get it from Motorola. 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. 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. That one is obviously failing.

It should have been served the rime and retained it so that subsequenet log entries would be stamped etc. 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. What to you mean by "same"? A lot of problems look the same on the surface. More than one person has explained that you that you have zero control over the firmware. It does resemble your situation, but he had no control over firmware either.

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 SB uses a different chipset which could make a subtle difference in regard to hangs.

And even that version is newer than mine. Gee, so much for the theory that Comcast pushes out the same firmware to everyone. 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.