US Cable Support > Comcast HSI > SB6120 Firmware Updated (7/19/12)

reply to GmDude66

Re: SB6120 Firmware Updated (7/19/12)

reply to GmDude66
Got it here in Glenview, Illinois, too.

reply to SteveTeow

reply to GmDude66
I did a reset to defaults and reboot and got the new firmware. No performance difference, but I am happy to see a firmware that is only a few months old as opposed to 2 years old. My Blast internet is still as fast as it was before.
--
My domain - Nightfall.net

reply to GmDude66
1. People are attributing all kinds of completely unrelated issues/changes to firmware.
2. Why are people so excited about updating firmware that probably does nothing for them? It may be that it does nothing but add the open source credits. Regardless, if it was THAT important, Comcast wouldn't require you to find out about it on broadbandreports.com and then manually reset the modem.

reply to johnnn
Reply to johnnn and SteveTeow -
I have a newly purchased SB6121 with 1.0.6.6 and am seeing exactly the same: Sporadic T4 timeouts and reboots throughout the day. Tech visited, all looks solid. When it's up, no complaints, but periodic reboots are starting to become very troublesome.

Are there known solutions to this issue? Or suggestions?

quatrix's comments aside (it's obvious the firmware fixes known issues between Arris CMTSes and Motorola D3 devices), I have noticed stabilization after a few power cycles. No T4 timeouts since the first two intervals between power cycles, and no sporadic reboots. Did you have T4 timeouts prior to this firmware build, or did your 6121 come preloaded with it?

This is a 2 week old 6121 and came preloaded. I was on an old SB5120 before.

reply to SteveTeow
I noted the firmware change after seeing it mentioned here. I did see that the modem was in IPV6 Modem IP Mode. I rebooted because of the speed-bump news on the internet and it moved back to IPV4 IP Mode.

Either way I saw no change in performance that I could discern. I ran a shaper probe after and my upstream shaping rate is halved but speed test show no change. I have 4 upstream and 3 downstream as before. On Ultra here.

I see some type of CMTS errors that are new:

Code: I401.0 Notice: TLV-11 - unrecognized OID

Code: Z00.0 Warning: MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;

reply to arw4f
The 5120 was really solid; I used one prior to my 6120. Hopefully things stabilize for you soon...I'd recommend DMing ComcastSteve if there's no improvement!

reply to quatrix

That is the kind of advice that almost any tech or engineer would agree with. If it ain't broke, don't fix it!

(I just wish that I would always follow that same advice that I often give to others, and not be tempted by curiosity)

Still, you know the risks and you're ready to deal with them.

reply to sortofageek
I take a similar approach but more willing to experiment. For example my new wireless router I am running beta firmware put out by the manufacturer's developers. Completely new interface, and offers a lot more control.

Besides assuring the open source community is getting it's due credit (shame on Motorola if they didn't before), aren't there a number of credible fixes in the new firmware? In fact we should have been running it a long time ago. Other ISPs pushed out the firmware more than a year ago. So they were more than cautious with Comcast.

Some of those may be security related etc. So in some cases the old engineering approach of "if it ain't broke don't fix it" may no longer apply when it comes to security or at least I evaluate if those issues impact me as part of the decision, some level of caution that others are reporting no issues.

In this case, you had no choice but to wait. If I had a choice to update my modem firmware I would have last year. If I fried it, then I accepted the risk by installing in the first place.

reply to SuperNet9
Got it in Joliet

reply to johnnn
That might be exactly what happened. They probably pushed an update to the CMTS first and that starting causing any of the modems that weren't updated to go crazy. I was informed that the internet went down again around noon today and it took a while to come back up. Didn't get a chance to see if I already had the firmware but I definitely have it now. One of my upstreams is reporting T4 timeout at the moment, so it might require a reboot tonight to get all 3 of them back online.

EDIT: Well it already rebooted itself again... It did fix the one upstream that was down... The one interesting thing though is now the upstream channels are listed in reverse from before. I used to have the 16QAM as the first one, then 2 64QAMs. Now the 2 64QAMs are listed as 1 & 2, and the 16 QAM is last. Not sure if that makes any difference or not.

reply to GmDude66
Received the firmware update in Aurora, IL. I was setup for IPv6 with the updated firmaware but it has reverted to IPv4 after a reboot a day later.

reply to GmDude66
Can anyone confirm that this firmware update fixes an issue where the 6120 reboots itself. Mine was doing that for four weeks now. It has been okay since the firmware upgrade, but still wonder if that was/is the issue.

reply to GmDude66
Got it in Lancaster, PA on 7-25. Don't see any difference and never had a reboot problem.
--
Best Team.