dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
33148
share rss forum feed

travelguy

join:1999-09-03
Santa Fe, NM

[Connectivity] New SB6120/6121 Firmware Released

A user over on the Comcast user forum has reported receiving firmware version 1068 (1066 was the latest). Anyone see this yet?

Wondering if it will address some upstream speed/channel bonding issues I had starting having with 1066.


jford951

join:2009-02-10
Westland, MI

No still on 1066 in MI



telcodad

join:2011-09-16
Lincroft, NJ
kudos:5
reply to travelguy

The link to that post: »forums.comcast.com/t5/Connectivi···#M160976

And the firmware version info that was listed:

Model Name: SB6120
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.8-SCM01-NOSH
Boot Version: PSPU-Boot 1.0.0.4m1
Hardware Version: 3.0
Firmware Build Time: Aug 30 2012 15:35:46


travelguy

join:1999-09-03
Santa Fe, NM

Would be nice to see the release notes. I checked on the Moto web site but couldn't find any.



Scree
In the pipe 5 by 5

join:2001-04-24
Mount Laurel, NJ
reply to travelguy

Just did a "Reset All Defauts" and "Restart Cable Modem" after reading this, and still have 1.0.6.6 here (6121).



jasqid
Fiber In Your Diet?

join:2002-04-02
East Palestine, OH

I was working with comcast steve in the direct forum about my 6121 rebooting randomly. He said something about getting engineers involved and firmware.


drugrep
--

join:2000-08-10
Woodridge, IL
reply to travelguy

Still on 1.0.6.6 here in Chicago Suburbs. (SB6120)



pd0x33

@comcast.net
reply to travelguy

Just power cyclced my 6120 for kicks, and finally got 1.0.6.6. I had assumed it would have been forced on me by now, but hadn't. I noticed in the upload section, 2 of the 3 channels have "success", but the middle one, has "T4 timeout". Is that such a bad thing? Would power cycling again maybe fix that? If it's that big an issue?


travelguy

join:1999-09-03
Santa Fe, NM

said by pd0x33 :

Just power cyclced my 6120 for kicks, and finally got 1.0.6.6. I had assumed it would have been forced on me by now, but hadn't. I noticed in the upload section, 2 of the 3 channels have "success", but the middle one, has "T4 timeout". Is that such a bad thing? Would power cycling again maybe fix that? If it's that big an issue?

Have you tried speedtest.comcast.com to see what your upload speeds are and how they compared to what they were?

hclarkjr

join:2002-08-09
Hostetter, PA
reply to travelguy

just checked my 6121, still same firmware



Wayne99021
Premium
join:2004-12-28
Mead, WA
kudos:1

SB 6141 still has the same.


bman212121

join:2005-06-09
reply to jasqid

said by jasqid:

I was working with comcast steve in the direct forum about my 6121 rebooting randomly. He said something about getting engineers involved and firmware.

Same here. Having issues with my SB6120 so I have the Aug 30th firmware on my modem. I wouldn't worry about it as it's not really doing anything for me... If I don't have bonded upstreams the modem can stay up for 4 or 5 days (or more). If I have bonded upstreams the modem is currently rebooting 4 times an hour. (Norm is about once every 3 hours)

andyross
Premium,MVM
join:2003-05-04
Schaumburg, IL
reply to pd0x33

said by pd0x33 :

Just power cyclced my 6120 for kicks, and finally got 1.0.6.6. I had assumed it would have been forced on me by now, but hadn't. I noticed in the upload section, 2 of the 3 channels have "success", but the middle one, has "T4 timeout". Is that such a bad thing? Would power cycling again maybe fix that? If it's that big an issue?

What are you upstream levels? The middle channel having T4 timeout means it didn't successfully bond all 3. You will also have a message in your log updated every minute or so. It will work well otherwise.

Basically, for upstream bonding, the limits are 51 dB for 3+ channels, 54dB for 2 channels, and 57dB for one.

1066 is the firmware released in July.

ExoticFish

join:2008-08-31
Stuarts Draft, VA
reply to travelguy

No update here.


travelguy

join:1999-09-03
Santa Fe, NM

1 recommendation

I suspect they are selectively targeting the update to see if it addresses at least some of the issues people reported with 1066. Can't blame them for being extra careful.



koitsu
Premium,MVM
join:2002-07-16
Mountain View, CA
kudos:23

1 edit
reply to andyross

The T4 timeout oddity, as well as the "Offline" modem status being shown when the connection is fully 100% working, are known 1.0.6.6 firmware bugs. It's been discussed pretty heavily over on the official Comcast forums. Possibly 1.0.6.8 fixes these -- I need release notes before I can say.

I'd like to know where you got the power level "guideline" numbers for upstream channel bonding from. This is the first I have ever seen this mentioned (specifically that multiple bonded upstream channels have more strict power levels). Even the FAQ doesn't jibe with those numbers. So where did you get them? To my knowledge based on service techs I've spoken with in the past, anything above 52dB is considered "volatile", meaning "not acceptable" and Comcast will do something about it, regardless of channel bonding in use or not (this is also supported by the FAQ). I've also been told that 54 dB is permitted on rare occasion (when the environment/cabling/topology is analysed and determined to be as good as it'll get).

To pd0x33 -- reboot your modem (do not do factory reset, just reboot it) and you'll find the anomaly disappears (until you either lose sync, lose a channel, or have some kind of other issue that results in problems).

travelguy See Profile's comment is spot on here, folks. Comcast is almost certainly testing 1.0.6.8 in very small (read: limited) areas first. This model is nothing new; it's how they've done it for a long time now.
--
Making life hard for others since 1977.
I speak for myself and not my employer/affiliates of my employer.



DrDrew
That others may surf
Premium
join:2009-01-28
SoCal
kudos:15

3 recommendations

said by koitsu:

The T4 timeout oddity, as well as the "Offline" modem status being shown when the connection is fully 100% working, are known 1.0.6.6 firmware bugs. It's been discussed pretty heavily over on the official Comcast forums. Possibly 1.0.6.8 fixes these -- I need release notes before I can say.



--
If it's important, back it up... twice. Even 99.999% availability isn't enough sometimes.

swalker

join:2006-03-24
reply to koitsu

said by koitsu:

I'd like to know where you got the power level "guideline" numbers for upstream channel bonding from. This is the first I have ever seen this mentioned (specifically that multiple bonded upstream channels have more strict power levels). Even the FAQ doesn't jibe with those numbers. So where did you get them? To my knowledge based on service techs I've spoken with in the past, anything above 52dB is considered "volatile", meaning "not acceptable" and Comcast will do something about it, regardless of channel bonding in use or not (this is also supported by the FAQ). I've also been told that 54 dB is permitted on rare occasion (when the environment/cabling/topology is analysed and determined to be as good as it'll get).

»[Connectivity] Bonded upstream and modem sync/T4 issues


Debi Lee

@comcast.net
reply to travelguy

Issues such as these? »forums.comcast.com/t5/Connectivi···U1365553



koitsu
Premium,MVM
join:2002-07-16
Mountain View, CA
kudos:23
reply to DrDrew

Thank you. I don't see the specific bugs mentioned, but it may be possible that in the 2nd bulletpoint of section 8.1.2 they re-worked the logic surrounding that code thus fixed the underlying bugs. I'll let folks know if/when the time comes.
--
Making life hard for others since 1977.
I speak for myself and not my employer/affiliates of my employer.



koitsu
Premium,MVM
join:2002-07-16
Mountain View, CA
kudos:23
reply to swalker

Interesting! I reviewed my modem logs for the past 30 days, and I can confirm that I've ONLY seen a power level higher than 52dB on upstream channels using QAM16 modulation. Those using QAM64 appear to top out at about 51dB for me. So thanks for pointing me to that information -- I appreciate being corrected and learning something! (Looks like the DSLR/BBR FAQ should be updated to reflect this too, at least as far as when bonding on DS3.0 is in use).

The bug/issue andyross See Profile was experiencing in that thread looks like it should be fixed in 1.0.6.8 (2nd bulletpoint of section 8.1.2 of the release notes posted by DrDrew See Profile); meaning the modem shouldn't continually reboot in that situation any longer.
--
Making life hard for others since 1977.
I speak for myself and not my employer/affiliates of my employer.

bman212121

join:2005-06-09

That's interesting koitsu. That would definitely explain why it T4's faster than I thought it should. (Was thinking 52db max because the QAM16 would show that)

The one thing I'm not sure if it was addressed or not was when I had even better signal levels than I do now my modem would "runaway" and T4. I would start at 44dBmV on all of the channels and it would creep up to 48dBmV. From there it would either go up to 51dBmV and time out or come back down to normal levels. 7dBmV is a lot of swing and might have indicated another issue they were having.



koitsu
Premium,MVM
join:2002-07-16
Mountain View, CA
kudos:23

Agreed -- 7dB is a very big delta. I imagine some of the techs here on the forum might have some ideas as to how things could start at 44 then eventually "settle" at 51. I personally haven't ever seen that, but I totally believe you, and would love to know how that kind of thing manifests itself (or if it's normal at that). Always interested to learn more about cable tech!
--
Making life hard for others since 1977.
I speak for myself and not my employer/affiliates of my employer.


andyross
Premium,MVM
join:2003-05-04
Schaumburg, IL

My rough theory is that the modem may not be cleanly transmitting and some noise could be leaking between channels, causing issues at the CMTS.



Scree
In the pipe 5 by 5

join:2001-04-24
Mount Laurel, NJ
reply to koitsu

Perhaps this 6121 datasheet helps... »www.motorola.com/web/Business/Pr···heet.pdf



Mike Wolf

join:2009-05-24
Beachwood, NJ
kudos:3
reply to travelguy

Any word from anyone else seeing the new firmware?



Oregonian
Premium
join:2000-12-21
West Linn, OR

Nothing so far.



DisturbedDan

join:2005-10-19
Oak Lawn, IL
reply to travelguy

Is 1.0.6.6 the new firmware for sb6121? I'm pretty sure I didn't have that version a week ago, since I never had the open source tab on my modem page. Connection was out for 2 hours last night and went down earlier this morning for a minute or two.


ExoticFish

join:2008-08-31
Stuarts Draft, VA

1.0.6.6 was released a while ago. 1.0.6.8 is what this thread is about.
--
»www.VAJeeps.com



telcodad

join:2011-09-16
Lincroft, NJ
kudos:5
reply to DisturbedDan

said by DisturbedDan:

Is 1.0.6.6 the new firmware for sb6121? I'm pretty sure I didn't have that version a week ago, since I never had the open source tab on my modem page. Connection was out for 2 hours last night and went down earlier this morning for a minute or two.

The 1.0.6.6 version of firmware was released by Comcast starting back in July: »SB6120 Firmware Updated (7/19/12)