Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2011.11.25 00:00:58 =~=~=~=~=~=~=~=~=~=~=~=
- Haxorware integrated telnet daemon
- Username: root
- Password: ****
- Welcome.
- CM>
- CM> run
- CM>
- CM> run_app
- Running the system...
- Beginning Cable Modem operation...
- 0x0000aee2 [Scan Downstream Thread] BcmVendorCmDownstreamScanThread::ThreadMain: (Scan Downstream Thread) Scanning for a Downstream Channel...
- mot_scanList: Setting override freq @ 0
- Favorite[0].freq = 762000000
- Attempting Downstream FEC lock @ freq= 762000000 Hz, QAM64/256
- CM> Found energy at frequency 762000000Hz! Publishing event kEventEnergyDetected...
- 0x0000b112 [CmDocsisCtlThread] BcmCmDocsisCtlThread::StartUsInit: (CmDocsisCtlThread) Locked on the downstream. Waiting for UCDs...
- ******************************************
- DOWNSTREAM STATUS
- ******************************************
- Tuner Frequency = 762000000 Hz
- Carrier Offset = -18 Hz
- Symbol rate = 6952000 sym/sec
- SNR = 32 dB
- QAM Mode = QAM256
- Tuner AGC = 0xfff00000
- IF AGC = 0x1635874b
- Power Level = -1 dB
- QAM = LOCKED
- FEC = LOCKED
- ******************************************
- CM> Selecting UCD for Us Channel 3
- 0x0000be0a [CmDocsisCtlThread] BcmCmDocsisCtlThread::TestAndLaunchDsTimeSync: (CmDocsisCtlThread) starting ds time sync acquisition...
- 0x0000c09e [CmDocsisCtlThread] BcmCmDocsisCtlThread::SyncDsSyncOk: (CmDocsisCtlThread) downstream time sync acquired...
- 0x0000c09e [CmDocsisCtlThread] BcmCmDocsisCtlThread::DsSyncOkResumeUsInit: (CmDocsisCtlThread) pre-REG upstream target case...starting initial ranging.
- Beginning initial ranging...
- Using stored initial upstream power = 8.0 dBmV
- 0x0000c0a8 [CmDocsisCtlThread] BcmCmDocsisCtlThread::SyncDsSyncOk: (CmDocsisCtlThread) rx unexpected kDsSyncOk indication...
- Not logging event ID 2307948724, control for level 7 is 0.
- CM> Adjusting the initial ranging power to 33.0 dBmV...
- Logging event: No Ranging Response received - T3 time-out (US 3)
- CM> Adjusting the initial ranging power to 46.0 dBmV...
- Logging event: No Ranging Response received - T3 time-out (US 3)
- CM> Adjusting the initial ranging power to 21.0 dBmV...
- Logging event: No Ranging Response received - T3 time-out (US 3)
- CM> Adjusting the initial ranging power to 52.0 dBmV...
- Logging event: No Ranging Response received - T3 time-out (US 3)
- CM> Adjusting the initial ranging power to 39.0 dBmV...
- Logging event: No Ranging Response received - T3 time-out (US 3)
- CM> Adjusting the initial ranging power to 27.0 dBmV...
- Logging event: No Ranging Response received - T3 time-out (US 3)
- CM> Adjusting the initial ranging power to 14.0 dBmV...
- Logging event: No Ranging Response received - T3 time-out (US 3)
- CM> Adjusting the initial ranging power to 55.0 dBmV...
- Logging event: No Ranging Response received - T3 time-out (US 3)
- CM> cd
- CM>
- CM> cd n/bAdjusting the initial ranging power to 49.0 dBmV...
- Logging event: No Ranging Response received - T3 time-out (US 3)
- CM> cd n/b
- CM> cd n/b
- Active Command Table: BFC Application Settings Commands (bfcApp)
- CM -> non-vol -> bfcApp
- CM/NonVol/BfcApp> auto_consoleAdjusting the initial ranging power to 42.0 dBmV...
- Logging event: No Ranging Response received - T3 time-out (US 3)
- CM/NonVol/BfcApp>
- CM/NonVol/BfcApp> auto_console
- CM/NonVol/BfcApp> auto_console Adjusting the initial ranging power to 36.0 dBmV...
- Logging event: No Ranging Response received - T3 time-out (US 3)
- CM/NonVol/BfcApp> auto_console 0
- CM/NonVol/BfcApp> auto_console 0
- Automatically stop at console = 0
- CM/NonVol/BfcApp> write
- CM/NonVol/BfcApp>
- CM/NonVol/BfcApp> write
- Dynamic Non-Vol Settings successfully written to the device.
- Adjusting the initial ranging power to 30.0 dBmV...
- Logging event: No Ranging Response received - T3 time-out (US 3)
- Permanent Non-Vol Settings successfully written to the device.
- CM/NonVol/BfcApp>
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement