+- 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: 5101 to 5101E (/showthread.php?tid=770)
Pages:
1
2
5101 to 5101E - Firefighter1428 - 20-02-2011
Have a working 5101 and had my buddy flash my 5101E with the latest Haxorware. I am new to this so I have no idea what I am doing. I want to get this second one working but cannot figure it out. I unplug my working one a mirrored it on the 5101E same S/n number and same HFC number but it will not connect. I tried the 3 different security settings and also picked none and I still only get the receive light flashing. What am I doing wrong? HELP?
RE: 5101 to 5101E - drewmerc - 20-02-2011
i'll guess your isp has the new security
only way to know for sure is a telnet log
RE: 5101 to 5101E - Firefighter1428 - 20-02-2011
(20-02-2011, 10:16 PM)drewmerc Wrote: i'll guess your isp has the new security
only way to know for sure is a telnet log
what is a telnet log? This is not my area of expertise.. I am a hardware guy not a software guy.
RE: 5101 to 5101E - drewmerc - 21-02-2011
http://www.haxorware.com/forums/thread-556-post-2956.html#pid2956
RE: 5101 to 5101E - Firefighter1428 - 21-02-2011
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2011.02.21 15:55:35 =~=~=~=~=~=~=~=~=~=~=~=
Haxorware integrated telnet daemon
Username: Matt
Password: *******
Welcome.
CM>
CM> 0x000299aa [DHCP Server Thread] BcmDhcpServerThread::ThreadMain: (DHCP Server Thread) Callback request expired:
timerDuration secs = 1
current time secs = 170
elapsed time secs = 1
CM> rub n
CM>
CM> run_app
Running the system...
Beginning Cable Modem operation...
0x0002bec6 [Scan Downstream Thread] BcmVendorCmDownstreamScanThread::ThreadMain: (Scan Downstream Thread) Scanning for a Downstream Channel...
mot_scanList: Setting override freq @ 0
Favorite[0].freq = 300000000
Attempting Downstream FEC lock @ freq= 300000000 Hz, QAM64/256
CM> Found energy at frequency 300000000Hz! Publishing event kEventEnergyDetected...
Favorite[1].freq = 332000000
Attempting Downstream FEC lock @ freq= 332000000 Hz, QAM64/256
Favorite[2].freq = 334000000
Attempting Downstream FEC lock @ freq= 334000000 Hz, QAM64/256
0x0002c4e8 [DHCP Server Thread] BcmDhcpServerThread::ThreadMain: (DHCP Server Thread) Callback request expired:
timerDuration secs = 1
current time secs = 181
elapsed time secs = 1
Go back to 1st favorite
Attempting Downstream FEC lock @ freq= 501000000 Hz, QAM64
CM> Attempting Downstream FEC lock @ freq= 507000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 513000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 519000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 525000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 531000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 537000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 543000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 549000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 555000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 561000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 567000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 573000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 579000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 585000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 591000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 597000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 603000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 609000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 615000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 621000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 627000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 633000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 639000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 645000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 651000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 657000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 663000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 669000000 Hz, QAM64
0x0002f01c [DHCP Server Thread] BcmDhcpServerThread::ThreadMain: (DHCP Server Thread) Callback request expired:
timerDuration secs = 1
current time secs = 192
elapsed time secs = 1
Attempting Downstream FEC lock @ freq= 675000000 Hz, QAM64
CM> Attempting Downstream FEC lock @ freq= 681000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 687000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 693000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 699000000 Hz, QAM64
RE: 5101 to 5101E - drewmerc - 22-02-2011
the telnet log needs to be a full boot sequence
RE: 5101 to 5101E - Firefighter1428 - 22-02-2011
Thats what it said to do on the link you gave me. How do I do it any differently
RE: 5101 to 5101E - drewmerc - 22-02-2011
Method 2) Using ethernet or USB (USB requires that USB drivers are correctly installed)
Remove power from the modem.
Set manual NIC IP 192.168.100.10.
Open Putty. Click the 'session' section of the settings panel:
Connection type: Telnet
Host Name: 192.168.100.1
Port: 23
Close window on exit: Never
Power up the modem. Wait 15 seconds, then click 'open' in putty.
Enter username and password, press enter.
Ignore any crap coming up in the window, it may look like you can't type but you can. May help if you just don't look at the screen
Type this, pressing enter at the end of each line:
cd doc
up_dis
cd /
cd n/b
auto_console 1
write
Note: The lines above are correct for modems based on the BCM3349 (A250/A255/A256/SB5101/Webstar 2100). If you're using a BCM3348 modem (A200/SB5100) the line 'cd n/b' changes to 'cd n/c'.
This tells the modem to halt at the console. Close putty and reboot modem using power cable.
When you reboot it, it won't try to connect at first, so you have time to set putty to log all console output to txt before connecting.
Open Putty. Click the logging section of the settings panel. Select the following options:
Session logging: All session output
Click 'browse' and browse to your desktop folder.
Filename: putty.txt
'Always overwrite it'
Untick 'flush log file frequently'
Click back onto the 'session' section of the settings panel:
Connection type: Telnet
Host Name: 192.168.100.1
Port: 23
Close window on exit: Never
Click 'open', enter username and password and press enter. Type 'run' and press enter. The modem will try to connect.
Once you've finished you'll need to set auto_console back to 0 in telnet, or you'll have to type 'run' every time you reboot modem.
RE: 5101 to 5101E - Firefighter1428 - 22-02-2011
How much is a full boot sequence? how long do I let it run? and what info are you looking for?
RE: 5101 to 5101E - drewmerc - 22-02-2011
http://www.haxorware.com/forums/attachment.php?aid=109