 koitsuPremium,MVM
join:2002-07-16
Mountain View, CA
kudos:18 | reply to swalker
Re: [Connectivity] New SB6120/6121 Firmware Released said by swalker:https://secure.dslreports.com/forum/r27387539-Connectivity-Bonded-upstream-and-modem-sync-T4-issues 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  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 ); 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. |
|
| 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. |
|
|
|
koitsuPremium,MVM
join:2002-07-16
Mountain View, CA
kudos:18 | 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. |
|
andyrossPremium,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. |
|
 ScreeIn 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 |
|
| reply to travelguy
Any word from anyone else seeing the new firmware? |
|
| Nothing so far. |
|
| 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. |
|
| 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:1 | 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) |
|
 pokesphIt Is Almost FastPremium
join:2001-06-25
Sacramento, CA
kudos:1 | reply to travelguy
nothing over here either..
still on Firmware Name: SB612X-1.0.3.3-SCM00-NOSH |
|
| reply to DisturbedDan
said by DisturbedDan:Is 1.0.6.6 the new firmware for sb6121? As has been posted 1068 is currently being tested by a limited number of subscribers. It addresses some of the channel bonding issues introduced in 1066, which was widely deployed a few months ago. |
|
| reply to travelguy
Ah.... my fault. I didn't read something fully. |
|
koitsuPremium,MVM
join:2002-07-16
Mountain View, CA
kudos:18 | reply to Mike Wolf
I'm currently helping Comcast test 1.0.6.8. I imagine it may be deployed in the field to very, very small/specific areas, otherwise if outside those areas it has to be done manually/on a per-customer basis.
--
Making life hard for others since 1977.
I speak for myself and not my employer/affiliates of my employer. |
|
| What makes you think that ?
--
»www.VAJeeps.com |
|
koitsuPremium,MVM
join:2002-07-16
Mountain View, CA
kudos:18 | Because the user mentioned here is not in the same area I am, and it's fairly likely this user did not go to Comcast and ask to test a new firmware version. So there must be small "test regions" in the field.
--
Making life hard for others since 1977.
I speak for myself and not my employer/affiliates of my employer. |
|
andyrossPremium,MVM
join:2003-05-04
Schaumburg, IL | reply to pokesph
said by pokesph:nothing over here either..
still on Firmware Name: SB612X-1.0.3.3-SCM00-NOSH
Have you rebooted your modem recently? |
|
| If you are currently on 1033, I wouldn't do anything to try to get 1066. For that matter, Comcast may have suspended deployment of 1066, but I still wouldn't force a reboot. |
|
andyrossPremium,MVM
join:2003-05-04
Schaumburg, IL | There is no proof that the firmware update actually caused problems. I still wonder how many started having problems because they didn't start bonding upstream until after the firmware update and the reboot that requires. Just because Comcast started offering upstream bonding doesn't mean the modem will automatically start using it. You have to reboot it to get enable it. |
|
| True. However, I know in my case I was seeing 50/5 with bonded down/up channels on 1033. When 1066 was pushed, I dropped to 20/1.5. Still seeing bonded down channels, but only a single uplink channel. 1088 restored the downlink speed back to 50, and I'm seeing 2 functional uplink channels, but uplink speed is stuck on 1.5. |
|
