1 recommendation |
to Meatball
Re: SB6141 Firmware Update?said by Meatball:...but then they shouldn't be allowed to sell it directly to end users without some sort of auto updating feature built in. They're happy to take your $70-$100 for the modem, but if it won't work b/c the firmware is too old, oh well.
I agree!! Motorola's consumer-targeted modems should have to be sold with a prominent disclaimer, like with cigarettes. For example: " WARNING: The firmware in consumer-owned cable modems will never be updated. Neither consumers nor manufacturers are allowed to do it (per the DOCSIS standard), and cable internet providers refuse to update the firmware of a modem they do not own. So if there's a bug in the current version, it will never be fixed. Nor can future compatibility issues be addressed." |
|
 NetFixerFrom My Cold Dead Hands
Premium Member
join:2004-06-24
The Boro
Pace 5268AC
TRENDnet TEW-829DRU
1 recommendation |
NetFixer
Premium Member
2013-Mar-4 6:41 pm
said by permutations:said by Meatball:...but then they shouldn't be allowed to sell it directly to end users without some sort of auto updating feature built in. They're happy to take your $70-$100 for the modem, but if it won't work b/c the firmware is too old, oh well.
I agree!! Motorola's consumer-targeted modems should have to be sold with a prominent disclaimer, like with cigarettes. For example: " WARNING: The firmware in consumer-owned cable modems will never be updated. Neither consumers nor manufacturers are allowed to do it (per the DOCSIS standard), and cable internet providers refuse to update the firmware of a modem they do not own. So if there's a bug in the current version, it will never be fixed. Nor can future compatibility issues be addressed." That would not be correct. Not all ISPs punish their customers (and indirectly their own tech support staff) just because the customer owns the modem. Comcast updates the firmware on customer owned modems the same as it does for its leased modems. In fact, they are currently starting to push the latest 1.0.6.10 firmware for the SB612x and SB6141 modems to those modems that are attached to their network. They don't care who owns it, they only want all modems of the same class to have the same firmware for performance and support purposes. Your problem is with your ISP, not with the modem or the modem's manufacturer. DOCSIS standards require that the ISP do the firmware updating and configuration for security reasons; if your ISP is not honoring its commitment to the DOCSIS standards, then place the blame where it belongs. |
|
| |
to Meatball
Pretty incredible that the T3 timeout issue is still going on and both sides are too full of bureaucracy to get anything fixed.
I had trouble with this in July of last year. As it stands now the only way to ensure you get a properly working DOCSIS 3.0 modem on Time Warner Cable's network is to ditch Motorola altogether. I've had issues with SB6141s and SBG6850s.
Want to know what fixed it? I sent the SB6141 back to Amazon and bought a Ubee DDW3611 off eBay and stuck it in bridge mode. Never again would I see a T3 timeout error. It's been rock solid these past 9 months.
Motorola used to be known as a reliable modem manufacturer. They really dropped the ball on this one. It may indeed be fixed in a recent firmware but imo Motorola doesn't deserve our support. I don't appreciate being treated like a criminal and told I can't update my own hardware because they're too incompetent to find a way to stop pirates that doesn't involve punishing the legitimate customer.
With no way to update them, every modem that Motorola has sold to a customer up until this update is essentially a $100 brick. I'm surprised no one has filed a lawsuit yet.
The Ubees have worked from day one and for that reason Ubee gets my support. |
|
| |
I think you guys changed my mind, this isn't Motorolla's fault. They're just following the DOCSIS 3 standard. The blame for all this lies squarely in the lap of Time Warner Cable. Time Warner has 7 modems that you can 'buy' that they say are compatible with the DOCSIS 3.0 service. Vendor ModelMotorola SBG6580 Motorola SB6141 Netgear CMD31T Motorola SB6121 Zoom 5341J Zoom 5350 ZyXEL CDA-30360 I checked every one of of them and none of them offer firmware upgrades for end users, they all say the ISP is supposed to do it. Heck, the ZyXEL modem is discontinued. Man, every day I think I can't dislike the support and business practices of Time Warner Cable any more, and yet every day I'm amazed that I find a new reason. |
|
1 recommendation |
to NetFixer
said by NetFixer:Not all ISPs punish their customers (and indirectly their own tech support staff) just because the customer owns the modem. Comcast updates the firmware on customer owned modems the same as it does for its leased modems. In fact, they are currently starting to push the latest 1.0.6.10 firmware for the SB612x and SB6141 modems to those modems that are attached to their network. They don't care who owns it, they only want all modems of the same class to have the same firmware for performance and support purposes. That's heartwarming. I'm glad to hear it. It certainly does sound like TWC deserves the blame. Their business practices are moronic in so many ways, why should I be surprised at one more dumb policy? Murica - this isn't Motorola's choice. Like Meatball said, it's the DOCSIS 3 standard. Motorola can't do it. It's the responsibility of the cable internet provider. |
|
1 recommendation |
to Meatball
said by Meatball:I think you guys changed my mind, this isn't Motorolla's fault. They're just following the DOCSIS 3 standard. The blame for all this lies squarely in the lap of Time Warner Cable.
It is Motorola's fault for having this bug in their firmware in the first place. Motorola should be replacing their faulty modems with replacements that have the latest firmware if the ISP won't do it. They sold a product which does not function as advertised. It should be their responsibility to fix it. As a prominent member of CableLabs, the developer of the DOCSIS standards, Motorola also deserves some blame for not trying to use their leverage to block this moronic restriction on what the customer can do with their own hardware when the DOCSIS 3.0 standards were being developed. Time Warner also deserves a share of the blame for not being willing to flash customer owned modems. There's plenty of blame to go around here, but unfortunately playing the blame game won't fix this problem. Purchasing a modem which does not have this bug in its firmware is your only option. |
|
1 recommendation |
to Meatball
I just read that someones SB6141 purchased modem was downgraded to 1.0.6.3. So TWC won't update your firmware but they will downgrade to a buggy firmware on a purchased modem.
I have a white retail SB6141 that I exchanged because it comes with 1.0.6.8. If TWC downgrades the firmware to 1.0.6.3 I am going to be really ticked off. They won't update your firmware but they will downgrade it which is proof that they can push firmware to purchased modems. |
|
| |
to Meatball
Re: SB6141 Reset and bore on ......I don't know if it's an old post but the reset on the SB 6141 is under the plastic gummed to the front. Take it off and it's at the bottom. The plastic cover goes back on well. You could put a pin hole in the plastic but with all the problems I've had I wouldn't dare.
TWC/RR has provisioned my modem. They stated they have the proper code from Motorola. That from level three.
I have been told, in this area, we have 25 up, 50 down, doesn't exist. I was on EarthLink for a time. I wish I could get my rock solid 30 meg, 1 1/2 up back. Received a commercial modem sitting on my porch. Have complained every day I have not gotten 80 % of 50 down since I lost my g father plan.
A tech saw everything was as I described, the modem is capable of 320 down, the apple 2nd gen Airport Express was grabbing 79 meg down from the modem on a, b, g, and n.
Everything from the pole in was replaced, an old timer made the best connect I ever saw, from the pole to the modem no boxes. Past level 3 and past two appeals to get the speed to 50 have failed. I've already seen it. I am paying 64.99 for the Ultimate. I woke up to today to 6 down .1 up.
I have kept a record all day and night and early morning since 3-4-13, I am not getting the required advertised 50 meg down 80% of the time. Roughly, 20 to 30% or less. I believe that is federal law today, April first.
I am so tired of this but I will keep at it. I forgot the name of the department I was in and graduated from, ah, retention, there it is, it's when they try to keep a customer. I am at the last appeal. Lost them both. there is a third. A separate department listens to every phone call I've made to them and then decides. Since I believe in and tell the absolute truth, they will find no discrepencies but they will think I scripted it, no winners.
It's a losing battle. The line tech said today that he hates speed issues. He said worse than the last call, where an older lady was getting half a picture, he moved the other console TV for her in it's place. Really nice guy.
It's my reponsibility for messing with the original grandfathered plan. It was somehow programmed right and never deviated from 28.6 to 30 down and 1 and a half up. It probably happened when I got an Eathlink agent, (they use TWC here), got a promo, talked for a while, got along, and he set it up with permanent turbo, who knows.
Sorry for the bore on, but I thought maybe if I wrote it, my obsession with speed would go away, just like the additional 35 bucks.
I forgot one thing. I had to edit this. Of all things, my modem has never restarted itself. Sorry, I really deserve that part too or I won't feel proper. |
|
 Le RoySkillz
Premium Member
join:2002-05-03
Ocean Springs, MS |
Le Roy
Premium Member
2013-Apr-21 4:25 am
I too am having issues with my SB6141 on my Cable Company, but I'm not sure if it really is the Cable Modem or the Cable Company... My cable company is Cable One. I've had a tech come out twice already to look over everything. So far they've replaced the line directly from my outside box to my modem, all the splitters in between and redone all the ends. This last time they replaced the main line from their hub to my house under ground. (I don't think they've sent anyone out to bury it yet, it's been rainy/muddy the past couple of days still)
My connection has gone from dropping 2 - 3 times per hour to only once every few hours now.
Their has to be a way for consumers to do our own firmware update on these. |
|
 swintec
Premium Member
join:2003-12-19
Alfred, ME |
swintec
Premium Member
2013-Apr-21 11:27 am
said by Le Roy:My connection has gone from dropping 2 - 3 times per hour to only once every few hours now.
What is the errors in your modem log? t4 timeouts and such? |
|
Le RoySkillz
Premium Member
join:2002-05-03
Ocean Springs, MS |
Le Roy
Premium Member
2013-Apr-22 2:42 am
Ill check when i get home, but if i remember correctly it is t4 or t3 errors. |
|
| Le Roy |
Le Roy
Premium Member
2013-Apr-22 10:27 pm
Apr 22 2013 19:21:18 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 22 2013 18:52:57 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 22 2013 18:52:57 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Apr 22 2013 18:52:13 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 22 2013 18:51:43 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 22 2013 18:51:17 5-Warning T202.0 Lost MDD Timeout;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 22 2013 18:51:12 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 22 2013 18:50:58 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 22 2013 17:57:18 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 22 2013 17:57:05 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 22 2013 17:57:02 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 22 2013 17:56:52 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 22 2013 17:56:52 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 22 2013 17:54:23 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 22 2013 17:53:44 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 22 2013 17:53:20 5-Warning T202.0 Lost MDD Timeout;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 22 2013 17:53:00 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 22 2013 17:51:36 5-Warning T202.0 Lost MDD Timeout;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
|
|
Le Roy
2 edits |
Le Roy
Premium Member
2013-Apr-23 1:17 pm
Apr 23 2013 11:11:11 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 23 2013 11:11:11 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:08:49 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:08:47 5-Warning R09.0 B-INIT-RNG Failure - Retries exceeded;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:08:43 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:08:01 3-Critical D01.0 DHCP FAILED - Discover sent, no offer received;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:07:27 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:54 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:42 5-Warning T203.0 MDD message timeout;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Apr 23 2013 11:00:01 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 23 2013 03:05:35 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 23 2013 02:54:25 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 23 2013 02:54:25 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Apr 23 2013 02:53:41 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 23 2013 02:52:56 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 23 2013 02:41:40 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 23 2013 02:41:40 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
This time the connection went down for a while. Like 15 - 20 minutes before the modem would connect again, power cycling seemed to have no effect. I was on the phone with the CO when it was down and when it came back online, he told me over the phone that he didn't see the modem online, despite it being online on my end. Weird. They are sending another tech out, right now he's talking to one of the techs in the call center apparently. edit He said they had an outage on their end, which is the reason why he wasn't able to see the modem come back online and the reason why it was off for so long. He said he still seen prior connection drops on my line and he's going to send a tech out anyway, so one will be here tomorrow between 3 - 5P. |
|
| Le Roy |
Le Roy
Premium Member
2013-Apr-24 5:39 pm
Well now I will find out if it's the cable modem or something on their end. They left an SB6180 here on the same line as my SB6141, both are connected to the same 3 way splitter and online. So in theory, if it's a problem on their end, both modems should go down; but if it's the SB6141 modem, then only it will go down. |
|
swintec
Premium Member
join:2003-12-19
Alfred, ME |
swintec
Premium Member
2013-Apr-24 5:49 pm
said by Le Roy:Well now I will find out if it's the cable modem or something on their end. They left an SB6180 here on the same line as my SB6141, both are connected to the same 3 way splitter and online. So in theory, if it's a problem on their end, both modems should go down; but if it's the SB6141 modem, then only it will go down.
The problem is the T4 timeouts you are having. Granted, you arent supposed to get them but if they do happen the firmware that your (and many others) 6141's run on will cause the modem to drop like you see. My 6141 runs great with the same firmware that yours has...but I do not have cable plant issues so i do not get T4 errors. I think in this case, it is hard to pin blame. One side would say the modem should handle the T4 errors more gracefully. The opposite side would say the cable plant should be addressed so T4 errors should not happen to begin with. At any rate, firmware revisions put out by Motorola address this. Maybe your cable company is small enough where you can get them to apply a more recent version for you and others on the network. I see it as a bandaid fix though for the bigger issue but I guess it is the easiest thing to do rather than have them track down why the T4 issue is happening to begin with. |
|
Le RoySkillz
Premium Member
join:2002-05-03
Ocean Springs, MS |
Le Roy
Premium Member
2013-Apr-24 5:59 pm
So what you are saying is what I am fearing. They are going to come back and say it's a problem with my Cable Modem since the 6180 wont be getting dropped when the 6141 will? If I tell the line tech who is coming back to my house tomorrow that the reason why the 6141 is dropping it's connection is because of T4 errors. The problem is, the 6141 is not "officially" supported by my Cable Company (Cable One) so they will most likely just tell me to get a new cable modem.
Worst case scenario, I do have to get a new one. Which one would be recommended? |
|
swintec
Premium Member
join:2003-12-19
Alfred, ME |
swintec
Premium Member
2013-Apr-24 6:07 pm
said by Le Roy:The problem is, the 6141 is not "officially" supported by my Cable Company (Cable One) so they will most likely just tell me to get a new cable modem.
What modems are supported by your cable company? The 6141 uses the same firmware as the 6121 and I believe the 6120. This was by design by Motorola in order to make things a bit easier on ISPs. If they utilize either of those modems as supported they should have no problem supporting the 6141, or at least upgrading you to a newer firmware (although i realize this would be an uphill battle for you on that front). There is a white 6141 available now through regular retail channels (Newegg, etc) that ships with a newer firmware. This should take care of your issue. My experience on this front simply comes from discussions in the Time Warner forum and users posting about it. YMMV on a different cable company but your symptoms are all the same. |
|
Le RoySkillz
Premium Member
join:2002-05-03
Ocean Springs, MS |
Le Roy
Premium Member
2013-Apr-24 6:11 pm
Oh wow, I just looked up the latest support list and the 6141 has been added!! When I bought the modem back in January, it wasn't listed. » support.cableone.net/app ··· m-modelsThat's good to know, so the 6180 uses the same firmware as well? If not, then I am afraid they are still going to tell me it's my modems problem when the 6180 they left here wont be getting dropped. On the other hand, if it does have the same firmware and it does get dropped, that should make it a lot easier to tell them they need to update their firmware to solve the problem. Do you happen to have some more documentation/links that I can read more into this so I can be better educated on the issue for when the tech comes back out tomorrow? |
|
swintec
Premium Member
join:2003-12-19
Alfred, ME |
swintec
Premium Member
2013-Apr-24 6:33 pm
said by Le Roy:That's good to know, so the 6180 uses the same firmware as well? If not, then I am afraid they are still going to tell me it's my modems problem when the 6180 they left here wont be getting dropped.
No, the 6180 does not share the same firmware image. Just the 6141, 6121 and 6120. Key part from the manual linked to below: "Easily add the SB6141 to a deployed family of SB6120s and SB6121s, all three models utilize the same firmware image. This reduces qualification time for an Operator and eliminates configuration management headaches." » moto.arrisi.com/staticfi ··· S-EN.pdf |
|
Le RoySkillz
Premium Member
join:2002-05-03
Ocean Springs, MS |
Le Roy
Premium Member
2013-May-1 11:23 pm
Well so far I haven't had any connection issues with the modem. |
|
Le Roy
1 edit |
to Meatball
Re: SB6141 Firmware Update?Spoke too soon. Seems as long as I don't upload anything heavily and/or download constantly I am fine. Once I start using the connection I pay for, I get those errors and the modem reboots itself.
Maybe this will be of some help.
Model Name: SB6141
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.10-SCM00-NOSH
Boot Version: PSPU-Boot(25CLK) 1.0.12.18m3
Hardware Version: 7.0
Serial Number: xxxxxxxxxxx
Firmware Build Time: Oct 29 2012 18:07:13 |
|
| |
to permutations
"Meatball", and friends,
I Shudder here in Charlotte, NC. Switching to TWC from ATT Uverse to gain control of my home network (silly me for wanting to manage VoIP & NOT pay $35/mo to ATT).
ANYWAY, looking to you as I prepare to buy my own modem and router. After reading about Meatball's experience with Motorola's still-approved, purchased router since December, I wanted to cry (for us both, I promise!)
My eagerly-awaited departure (think "Argo" hostage) from AT&T ("I can transfer you to the Fee-based customer service area that can assist you with your issue"... ON A RENTED ROUTER? UGH!) Dear, dear Meatball: do you have any newer experiences? I see that one respondant suggested s/he had switched to a router not specifically "supported" by TWC. I find that move terrifying ... which is probably silly on my part.
I initially switched to ATT 2 years ago since it was easier to get them to initiate a simple reboot by calling an automated attendant: Can TWC do that now? I even chose their $6/mo (ironically, Motorola!) modem (they provide one already capable of wifi to addict the user and those pesky Phone ports mean they control your access to VoIP). They've taking the "User's Manual" off the FCC's website, but hey? It's not like I'm paying them rent to ... oh, wait, I am. Although you can access the router's [2Wire] web interface and change settings on the Ethernet ports, you can't really. I esp loved being taunted with the bright green "Contratulations! Successfully changed!" page they forgot to disable. Yes, even the interface lies to me.
Because TWC allows me to go month to month, I still prefer them. Would you suggest that I [suck it up and] rent the modem to get the access into my home with their alleged support and just purchase a router for wifi, VoIP and ethernet?
Peace and condolences as I Shudder in Charlotte. |
|
boe_d
join:2003-10-12
Los Angeles, CA |
boe_d
Member
2013-Jun-3 11:13 pm
I just switched out my TW rental unit for the Sb16141. I went from 26mbit down x 2mbit up to 3mbit down x2mbit up. I certainly am hoping this is fixed quickly.
Model Name: SB6141
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.3-SCM03-NOSH
Boot Version: PSPU-Boot(25CLK) 1.0.12.
Hardware Version: 7.0
Firmware Build Time: Aug 18 2011 10:27:53 |
|
| boe_d |
boe_d
Member
2013-Jun-4 12:36 am
I've spent 2 hours working with TW. My old modem gets 26mbit down the best they can do for me is 15mbit. |
|
Le RoySkillz
Premium Member
join:2002-05-03
Ocean Springs, MS |
to Meatball
Still having issues with T4 timeouts, but either I'm not using my Internet as much as I was before or it just doesn't happen as frequently.
Last night between 930PM and 1130PM, my modem rebooted due to T4 errors 4 times. |
|
| |
Just want to say, I've been using the SB6121 (Firmware SB612X-1.0.5.1-SCM00-NOSH from Dec 2010) for months without a single issue. I know they fixed something in my neighborhood, but I also wonder if the 6141 just has issues with TWC's network. |
|
| |
Well I've been having this T4 timeout problem since last summer and have spent at least 20 hours arguing with TWC to get things fixed. It's hilarious that when I purchased my SB6141, I specifically asked TWC if I will receive full support for the modem since it is on their approved list, which they said they would.
Now they're telling me that they cannot even give me level 3 tech support because they don't support customer modems and that the problem is not on their end, but they'd like to send a tech out.... again.
They also told me that any firmware updates must be obtained from Motorola since this is a customer owned device.... so much for support.
Has anyone been able to get firmware from Motorola?
here is my current software:
Model Name: SB6141
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.3-SCM03-NOSH
Boot Version: PSPU-Boot(25CLK) 1.0.12.
Hardware Version: 7.0
Firmware Build Time: Aug 18 2011 10:27:53 |
|
swintec
Premium Member
join:2003-12-19
Alfred, ME |
swintec
Premium Member
2013-Jun-15 4:55 pm
How arte you approaching the problem with TW? T4 errors shouldnt happen under ideal circumstances so maybe it would be better to pursue that route? Obviously a modem shouldnt restart because of it but they do not seem willing to address that with a simple firmware update. FWIW, I have the same firmware but do not see the problem at all.
Maybe start a topic in the direct forum here and get the ball rolling for a widespread rollout of the newest firmware, which HAS been issued in some divisions according to some topics here. Or maybe they can at least get the T4 problems fixed. |
|
|
| |
Bob 3965 to Meatball
Anon
2013-Jun-26 9:28 am
to Meatball
Does anyone from Motorola and TWC read these posts and try to fix these problems? After 6 pages of complaints it doesn't appear they care at all about their customers. I say class action lawsuit about false advertising and fraud for claiming everything is available on demand. |
|
| |
DOCSIS Modem
Anon
2013-Jun-26 1:32 pm
said by Bob 3965 :Does anyone from Motorola and TWC read these posts and try to fix these problems? After 6 pages of complaints it doesn't appear they care at all about their customers. I say class action lawsuit about false advertising and fraud for claiming everything is available on demand.
Actually, only TWC can do anything about the problem. Motorola can not supply the end user with the firmware because only allowing the ISP to install firmware is part of the DOCSIS standard. The assumption is that an ISP will want to keep the firmware up to date on their customers' equipment, but apparently TWC just doesn't give a damn. |
|
