- Digital TV
- Computer
- Mobiles
- Internet
- Apple
- Gaming
Haxorware stuck at Ranging!
Cable Modems Gotta start somewhere and here's the place to start :)
LinkBack Thread Tools 
21-09-09, 05:50 PM
#1 (permalink) Junior Member
Join Date: Dec 2008Posts: 4Thanks: 1Thanked 0 Times in 0 Posts
Haxorware stuck at Ranging!
Hi Everyone.
I'm really hoping that someone can shed some light on this problem as it's been plaguing me for a week already!
I have a scientific atlanta 2100 with Haxorware 1.1 rev 32 running. I've read loads of really helpful threads on here with different suggestions of configuration, but I still can't get the thing past 'ranging'
The wierd thing is, I've got another scientific atlanta 2100 (running infinite) and a virmin ambit 256 which both connect fine on the same coax cable.
I've taken a telnet log of whats happening with haxorware...
please helpCode:CM> Favorite[0].freq = 339000000 Attempting Downstream FEC lock @ freq= 339000000 Hz, QAM64/256 0x0004f998 [CmDocsisCtlThread] BcmCmDocsisCtlThread::StartUsInit: (CmDocsisCtlThread) Locked on the downstream. Waiting for UCDs... ****************************************** DOWNSTREAM STATUS ****************************************** Tuner Frequency = 339000000 Hz Carrier Offset = -3 Hz Symbol rate = 5360537 sym/sec SNR = 37 dB QAM Mode = QAM256 Tuner AGC = 0xfff00000 IF AGC = 0x16e60e14 Power Level = -5 dB QAM = LOCKED FEC = LOCKED ****************************************** CM> Selecting UCD for Us Channel 2 0x00051004 [CmDocsisCtlThread] BcmCmDocsisCtlThread::TestAndLaunchDsTimeSync: (CmDocsisCtlThread) starting ds time sync acquisition... 0x0005127a [CmDocsisCtlThread] BcmCmDocsisCtlThread::SyncDsSyncOk: (CmDocsisCtlThread) downstream time sync acquired... 0x0005127a [CmDocsisCtlThread] BcmCmDocsisCtlThread::DsSyncOkResumeUsInit: (CmDocsisCtlThread) pre-REG upstream target case...starting initial ranging. Beginning initial ranging... Using default (wacky stored value) initial upstream power = 8.0 dBmV 0x00051284 [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 2) CM> Adjusting the initial ranging power to 46.0 dBmV... Logging event: No Ranging Response received - T3 time-out (US 2) CM> RNG-RSP Adj: tim=2527 power=70 freq=0 Stat=Continue CM> RNG-RSP Adj: tim=0 power=30 freq=0 Stat=Continue CM> RNG-RSP Adj: tim=0 power=30 freq=0 Stat=Continue CM> RNG-RSP Adj: tim=0 power=30 freq=0 Stat=Continue CM> RNG-RSP Adj: tim=0 power=30 freq=0 Stat=Continue CM> RNG-RSP Adj: tim=0 power=30 freq=0 Stat=Continue CM> RNG-RSP Adj: tim=0 power=30 freq=0 Stat=Continue CM> RNG-RSP Adj: tim=0 power=30 freq=0 Stat=Continue CM> RNG-RSP Adj: tim=0 power=30 freq=0 Stat=Continue CM> RNG-RSP Adj: tim=0 power=30 freq=0 Stat=Continue CM> RNG-RSP Adj: tim=0 power=30 freq=0 Stat=Continue CM> RNG-RSP Adj: tim=0 power=30 freq=0 Stat=Continue CM> RNG-RSP Adj: tim=0 power=30 freq=0 Stat=Continue CM> RNG-RSP Adj: tim=0 power=30 freq=0 Stat=Continue CM> RNG-RSP Adj: tim=0 power=30 freq=0 Stat=Continue CM> RNG-RSP Adj: tim=0 power=30 freq=0 Stat=Continue CM> RNG-RSP Adj: tim=0 power=30 freq=0 Stat=Continue CM> RNG-RSP Adj: tim=0 power=30 freq=0 Stat=Abort 0x00056630 [CmDocsisCtlThread] BcmCmDocsisCtlThread::RngRspMsgEvent: (CmDocsisCtlThread) Received a RNG-RSP with ABORT! Going elsewhere... 0x00056630 [CmDocsisCtlThread] BcmCmDocsisCtlThread::CommonRngErrorHandler: (CmDocsisCtlThread) reason: 7 (kRngRspAbortStatus) 0x0005663a [CmDocsisCtlThread] BcmCmDocsisCtlThread::TargetNextUsChan: (CmDocsisCtlThread) 0x0005663a [CmDocsisCtlThread] BcmCmDocsisCtlThread::ResetRngState: (CmDocsisCtlThread) @@@@@ In ResetRngState, fRemainingInitRngPowerSteps 17 Logging event: Unicast Ranging Received Abort Response - Re- initializing MAC CM> Selecting UCD for Us Channel 4 0x00057d1e [CmDocsisCtlThread] BcmCmDocsisCtlThread::DsSyncOkResumeUsInit: (CmDocsisCtlThread) pre-REG upstream target case...starting initial ranging. Beginning initial ranging... Using default (wacky stored value) initial upstream power = 8.0 dBmV Not logging event ID 2307948724, control for level 7 is 0. Adjusting the initial ranging power to 33.0 dBmV... Logging event: No Ranging Response received - T3 time-out (US 4) CM> Adjusting the initial ranging power to 46.0 dBmV... Logging event: No Ranging Response received - T3 time-out (US 4) CM> Adjusting the initial ranging power to 21.0 dBmV... Logging event: No Ranging Response received - T3 time-out (US 4) CM> NonVolDeviceDriver::NonVolDriverWrite: WARNING - Current segment size < buffer size! Increasing the segment size! Adjusting the initial ranging power to 52.0 dBmV... Logging event: No Ranging Response received - T3 time-out (US 4) CM> RNG-RSP Adj: tim=2528 power=60 freq=0 Stat=Continue CM> RNG-RSP Adj: tim=0 power=44 freq=0 Stat=Continue CM> RNG-RSP Adj: tim=0 power=44 freq=0 Stat=Continue CM> RNG-RSP Adj: tim=0 power=44 freq=0 Stat=Continue CM> RNG-RSP Adj: tim=0 power=44 freq=0 Stat=Continue CM> RNG-RSP Adj: tim=0 power=44 freq=0 Stat=Continue CM> RNG-RSP Adj: tim=0 power=44 freq=0 Stat=Continue CM> RNG-RSP Adj: tim=0 power=44 freq=0 Stat=Continue CM> RNG-RSP Adj: tim=0 power=44 freq=0 Stat=Continue CM> RNG-RSP Adj: tim=0 power=44 freq=0 Stat=Continue CM> RNG-RSP Adj: tim=0 power=44 freq=0 Stat=Continue CM> RNG-RSP Adj: tim=0 power=44 freq=0 Stat=Continue CM> RNG-RSP Adj: tim=0 power=44 freq=0 Stat=Continue CM> RNG-RSP Adj: tim=0 power=44 freq=0 Stat=Continue CM> RNG-RSP Adj: tim=0 power=44 freq=0 Stat=Continue CM> RNG-RSP Adj: tim=0 power=44 freq=0 Stat=Continue CM> RNG-RSP Adj: tim=0 power=44 freq=0 Stat=Continue CM> RNG-RSP Adj: tim=1 power=44 freq=0 Stat=Abort 0x00061274 [CmDocsisCtlThread] BcmCmDocsisCtlThread::RngRspMsgEvent: (CmDocsisCtlThread) Received a RNG-RSP with ABORT! Going elsewhere... 0x0006127e [CmDocsisCtlThread] BcmCmDocsisCtlThread::CommonRngErrorHandler: (CmDocsisCtlThread) reason: 7 (kRngRspAbortStatus) 0x0006127e [CmDocsisCtlThread] BcmCmDocsisCtlThread::TargetNextUsChan: (CmDocsisCtlThread) 0x0006127e [CmDocsisCtlThread] BcmCmDocsisCtlThread::TargetNextUsChan: (CmDocsisCtlThread) All usable upstream chans tried. Target next ds. 0x0006127e [CmDocsisCtlThread] BcmCmDocsisCtlThread::TargetNextDsChan: (CmDocsisCtlThread) Logging event: Unicast Ranging Received Abort Response - Re- initializing MAC Deleting DOCSIS 1.0 CoS Settings for SID 0 0x00061346 [CmDocsisCtlThread] BcmDocsisCmHalIf::DeleteAllServiceFlows: (DOCSIS CableModem HalIf) Deleting all Upstream and Downstream Service Flows, along with associated Classifiers and PHS rules... Stopping DHCP/ToD/TFTP (client requested)... DefaultSnmpAgentClass::RestartPendingEvent for SB5102 CM Agent w/ BRCM Factory Support SB5102 CM Agent w/ BRCM Factory Support resetting to default state. SB5102 CM Agent w/ BRCM Factory Support destroying users... Pausing trap thread SB5102 CM Agent w/ BRCM Factory Support destroying notifies... Resuming trap thread SB5102 CM Agent w/ BRCM Factory Support sending deferred traps... Done w/ deferred traps. SB5102 CM Event Log w/ BRCM Factory Support sending deferred async messages... Done w/ deferred msgs SB5102 CM Agent w/ BRCM Factory Support defering traps. SB5102 CM Agent w/ BRCM Factory Support setting V1/V2 view to unrestricted SB5102 CPE Agent w/ BRCM Factory Support setting V1/V2 view to docsisCpeView Non-Vol Settings successfully written to the device. 0x00061350 [CmDocsisCtlThread] BcmCmDocsisCtlThread::ResetRngState: (CmDocsisCtlThread) @@@@@ In ResetRngState, fRemainingInitRngPowerSteps 17 0x0006135a [Scan Downstream Thread] BcmVendorCmDownstreamScanThread::ThreadMain: (Scan Downstream Thread) Downstream Channel scan stopped! 0x0006136e [Scan Downstream Thread] BcmVendorCmDownstreamScanThread::ThreadMain: (Scan Downstream Thread) Scanning for a Downstream Channel... mot_scanList: Setting override freq @ 0 Go back to 1st favorite Attempting Downstream FEC lock @ freq= 826000000 Hz, QAM256 Attempting Downstream FEC lock @ freq= 834000000 Hz, QAM256 CM> Attempting Downstream FEC lock @ freq= 842000000 Hz, QAM256 Attempting Downstream FEC lock @ freq= 850000000 Hz, QAM256 Attempting Downstream FEC lock @ freq= 858000000 Hz, QAM256 Attempting Downstream FEC lock @ freq= 90750000 Hz, QAM64/256 Attempting Downstream FEC lock @ freq= 98750000 Hz, QAM64/256 Attempting Downstream FEC lock @ freq= 106750000 Hz, QAM64/256 Attempting Downstream FEC lock @ freq= 114750000 Hz, QAM64/256 Attempting Downstream FEC lock @ freq= 122750000 Hz, QAM64/256 Attempting Downstream FEC lock @ freq= 130750000 Hz, QAM64/256 Attempting Downstream FEC lock @ freq= 138750000 Hz, QAM64/256 Attempting Downstream FEC lock @ freq= 146750000 Hz, QAM64/256 Attempting Downstream FEC lock @ freq= 154750000 Hz, QAM64/256 Attempting Downstream FEC lock @ freq= 162750000 Hz, QAM64/256 Attempting Downstream FEC lock @ freq= 170750000 Hz, QAM64/256 Attempting Downstream FEC lock @ freq= 178750000 Hz, QAM64/256
21-09-09, 10:00 PM
#2 (permalink) Senior Member
Join Date: Mar 2009Location: East LondonPosts: 1,208Thanks: 751Thanked 275 Times in 217 Posts
Re: Haxorware stuck at Ranging!
Hi have you tried trying another mac address.__________________
"They say the wisest person in the room is usually the one that has made the most mistakes"
22-09-09, 06:44 PM
#4 (permalink) Senior Member
Join Date: Mar 2009Location: East LondonPosts: 1,208Thanks: 751Thanked 275 Times in 217 Posts
Re: Haxorware stuck at Ranging!
hi whats your frequency currently set on
here are the main 3 although there are more but these are the most frequently used ones.
586750000 for ex C+W area
402750000 for NTL area
331000000 for Telewest area__________________
"They say the wisest person in the room is usually the one that has made the most mistakes"
22-09-09, 10:26 PM
#7 (permalink) Senior Member
Join Date: Apr 2009Posts: 108Thanks: 10Thanked 26 Times in 24 Posts
Re: Haxorware stuck at Ranging!
Looks to me like you're using the wrong upstream channel, it seems 2 & 4 don't work.
Try changing it to 0,1 or 3.
Last edited by djbones; 22-09-09 at 10:29 PM.
26-09-09, 10:19 AM
#8 (permalink) Junior Member
Join Date: Dec 2008Posts: 4Thanks: 1Thanked 0 Times in 0 Posts
Re: Haxorware stuck at Ranging!
thanks for the replies sheeks and djbones
my downstream is locking to 339000000 consistantly but i've tried 0, 1 and 3 in the upstream channel field but it takes no notice and keeps trying to lock on to 2 and 4
having said that, it sometimes locks to DS 331000000 / US 18000000 Channel 1 for about 3 seconds and then starts ranging again! *doh*
i'm starting to think that it might be something with the cabling. but as i said i've got a legit vermin modem that works fine lol.
27-09-09, 03:45 PM
#9 (permalink) Technology Forums
Join Date: Nov 2008Posts: 1,331Thanks: 78Thanked 332 Times in 183 Posts
Re: Haxorware stuck at Ranging!
The best test you can do here is what I myself would do.
Take a backup of the nonvol of one of your working modems, and then restore it to the one that you are having problems with, and then see what happens.
It's probably a setting somewhere thats screwed. Sometimes I've had it where all the settings *look* like they are OK and identical to the working settings but it just don't work! And then I use a nonvol backup from a working modem and hey presto! Operational!
Bookmarks
Thread Tools
Posting Rules
Similar Threads
Thread Thread Starter Forum Replies Last Post SA EPC2100R2 - SB5100i + Haxorware R32 rabby Cable Modems 4 28-08-09 08:53 PM Upstream ranging SB5101E antk43 Cable Modems 6 31-07-09 03:38 PM haxorware setup help geordie-james2k7 Cable Modems 7 05-07-09 01:18 PM Both my 250's just went down at the same time!! cheesyboofs Cable Modems 11 21-03-09 11:00 AM Haxorware Tutorial abaaba Cable Modems 12 14-02-09 09:13 AM
All times are GMT +1. The time now is 10:59 AM.
- Mobiles
