SB5101 not working - Printable Version +- Haxorware Forums (http://www.haxorware.com/forums) +-- Forum: General (http://www.haxorware.com/forums/forumdisplay.php?fid=6) +--- Forum: Modems (http://www.haxorware.com/forums/forumdisplay.php?fid=7) +--- Thread: SB5101 not working (/showthread.php?tid=364) Pages:
1
2
|
SB5101 not working - laythy - 07-01-2010 hi there im new to all this so i might not know much but i kinda know a bit about what im doing a friend of mine gave me his modem that worked fine at his house but its not working at mine i tried another one that worked at his house too but still not working on mine we live in the same area but might not be the same range so this might be the problem we both have comcast and using DNS 208.67.222.222, 208.67.220.220 i am using a mac but i can get access to a pc if i need to the modem is flashed with Haxorware Version 1.1 Revision 38 checked boxes in setting are Disable Firmware Upgrades Force Network Access DHCP Server Frequency settings 597000000 549000000 339000000 chan 4 using d11_m_sb5101_showcase_c05.cm file BPI+DOCSIS1.1 tried to bypass still didnt work here is a log file 2010-01-07 17:02:35 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2010-01-07 17:02:34 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2010-01-07 17:02:32 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2010-01-07 17:02:31 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2010-01-07 17:02:31 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2010-01-07 17:02:31 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2010-01-07 17:02:30 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2010-01-07 17:02:26 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2010-01-07 17:02:26 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2010-01-07 17:02:20 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2010-01-07 17:02:19 Notice M572.0 Ds Pulse Failed - Reinitialize MAC... 2010-01-07 17:02:17 Notice M572.0 Neg Or Bad Reg Rsp - Reinitialize MAC... 2010-01-07 17:02:13 Critical D003.0 DHCP WARNING - Non-critical field invalid in response. 2010-01-07 17:02:08 Critical R002.0 No Ranging Response received - T3 time-out (US 1) 2010-01-07 17:01:39 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2010-01-07 17:01:39 Notice M572.0 T1 No Ucd Timeout - Reinitialize MAC... 2010-01-07 17:01:39 Critical U001.0 No UCD's Received - Timeout 2010-01-07 17:01:27 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2010-01-07 17:01:27 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2010-01-07 17:01:23 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2010-01-07 17:01:22 Notice M572.0 Ds Pulse Failed - Reinitialize MAC... 2010-01-07 17:01:21 Notice M572.0 Neg Or Bad Reg Rsp - Reinitialize MAC... 2010-01-07 17:01:15 Critical D003.0 DHCP WARNING - Non-critical field invalid in response. 2010-01-07 17:01:06 Notice M572.0 Neg Or Bad Reg Rsp - Reinitialize MAC... 1970-01-01 00:00:19 Critical D003.0 DHCP WARNING - Non-critical field invalid in response. 1970-01-01 00:00:12 Critical R002.0 No Ranging Response received - T3 time-out (US 1) 1970-01-01 00:00:04 Notice M571.1 Ethernet link up - ready to pass packets RE: SB5101 not working - drewmerc - 07-01-2010 try using a docsis 1.0 config and see if it connects then RE: SB5101 not working - laythy - 07-01-2010 i assume that will be in the force config file field? if im right then i get this log 2010-01-07 17:46:44 Critical D006.0 TFTP failed - configuration file NOT FOUND 2010-01-07 17:46:43 Critical D003.0 DHCP WARNING - Non-critical field invalid in response. 2010-01-07 17:46:39 Critical R002.0 No Ranging Response received - T3 time-out (US 1) 2010-01-07 17:46:30 Notice M572.0 Tftp Init Failed - Reinitialize MAC... 2010-01-07 17:45:30 Critical D006.0 TFTP failed - configuration file NOT FOUND 1970-01-01 00:00:19 Critical D003.0 DHCP WARNING - Non-critical field invalid in response. 1970-01-01 00:00:13 Critical R002.0 No Ranging Response received - T3 time-out (US 1) 1970-01-01 00:00:05 Notice M571.1 Ethernet link up - ready to pass packets it lockes up but stays at Retrieve Time of Day RE: SB5101 not working - drewmerc - 08-01-2010 the 1.0 config your trying to use is not valid try a differant one RE: SB5101 not working - laythy - 09-01-2010 actually i checked my previous post and 2010-01-07 17:46:44 Critical D006.0 TFTP failed - configuration file NOT FOUND lol i guess im doing somthing wrong? how and where do i exactly find the configuration file? RE: SB5101 not working - drewmerc - 09-01-2010 for me i run dhcpforce and look for new configs names that way and download them with haxors webgui RE: SB5101 not working - laythy - 10-01-2010 im on a mac so i cant really run exe files what im trying to understand is why its working at my friends house but not in mine? if i can find out why ill know how to fix it RE: SB5101 not working - drewmerc - 10-01-2010 my guess is that his node has not implemented docsis 1.1 yet RE: SB5101 not working - laythy - 10-01-2010 ok i was checking mac addresses and they both use the same exact macs on all 3 counts does that make difference or not and how can i find other macs that may work? RE: SB5101 not working - drewmerc - 11-01-2010 your on a mac so no idea but i did see this http://lifehacker.com/5440703/winebottler-turns-windows-programs-into-standalone-os-x-applications (off topic kind of) but try that with dhcpforce or solsters sniffer |