| [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. |
|
| No still on 1066 in MI |
|
 telcodad
join:2011-09-16
Lincroft, NJ
kudos:1 | 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 |
|
|
|
| Would be nice to see the release notes. I checked on the Moto web site but couldn't find any. |
|
 ScreeIn 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). |
|
 jasqidFiber 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) |
|
| 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? |
|
| 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? |
|
| reply to travelguy
just checked my 6121, still same firmware |
|
| SB 6141 still has the same. |
|
| 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) |
|
andyrossPremium,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. |
|
| reply to travelguy
No update here. |
|
| 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. |
|
 koitsuPremium,MVM
join:2002-07-16
Mountain View, CA
kudos:18
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  '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. |
|
 DrDrewSo that others may surf.
join:2009-01-28
SoCal
kudos:8 | 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. |
|
| 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 |
|
| reply to travelguy
Issues such as these? »forums.comcast.com/t5/Connectivi···U1365553 |
|
koitsuPremium,MVM
join:2002-07-16
Mountain View, CA
kudos:18 | 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. |
|
