You need an 'engineer' to fix yours like mine (3 years ago), boost the signal tremendously (by moving the cable connection in the green box), then fit an attenuator that you can take out. If the downstream was reduced to 0dB then the upstream would be saturated @ +58 and I get a lot of disconnects. As you can see it works fine like this...
Code:
jview /cp docsdiag.jar docsdiag -cmip 10.150.67.57 -cmmac 0xxxx -v
DocsDiag v030720 Copyright 2001-3 Robin Walker rdhw@cam.ac.uk
Terayon DOCSIS Cable Modem: <<HW_REV: 6.62; VENDOR: Terayon; BOOTR: NONE; SW_REV
: 1.7.14; MODEL: >>
System up time = 8 days 21h 40m 19.89s
Ethernet single-collision errs.1 = 987
Ethernet multiple-collision errs.1 = 945
Downstream channel ID = 0
Downstream channel frequency = 402750000 Hz
Downstream received signal power = 13.5 dBmV
Upstream channel ID = 1
Upstream channel frequency = 33584000 Hz
Upstream timing offset = 13149 units of (6.25/64) microseconds
QoS max upstream bandwidth = 64000 bps
QoS max downstream bandwidth = 150000 bps
SigQu: received without error = 1512992529 codewords
SigQu: correctable errors = 1137 codewords
SigQu: uncorrectable errors = 4 codewords
SigQu: Signal to Noise Ratio = 34.1 dB
SigQu: microreflections = 24 dBc
Cable modem status = Operational
Upstream transmit signal power = 48.2 dBmV
Number of interface resets = 0
Downstream sync losses = 0
Invalid MAP msgs received = 0
Invalid UCD msgs received = 0
Invalid Ranging Responses rcvd = 0
Invalid Registration Resps rcvd = 0
T1 timer expiries = 0
T2 timer expiries = 0
T3 timer expiries = 8
T4 timer expiries = 0
Ranging Aborts = 0
Tx mini-slots used (contended).2733 = 0
Tx mini-slots used (dedicated).2733 = 195503078
Tx data re-tries.2733 = 0
Tx data retry limit exceeded.2733 = 0
Tx bandwidth req retries.2733 = 1508816
Tx bw req retry lim exceeded.2733 = 78732
Date and Time = 2004-07-02,18:08:38.0+00:00
Configuration filename = tera210x-bronze.cm