Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[mr_chris]

Woohoo.. I'm learning - I might take the plunge with your tutorials to hold my hand at some point soon!

[kitz]

Just to be clear, the correct command to type is:

cat /proc/cpuinfo

(although it apparently also works without the leading / in front of proc)

Thanks for the reminder eric - changed the cli commands page for the broadcom chipsets to include the leading /

[lodge]

One thing I didn't really notice before is that you appear to have a highish target noise margin (very possibly 12 dB) which would result in your connection speed being a bit less than it might be.

It's been bouncing around between 7dB and 11.5db today.

[roseway]

Yes, the target noise margin is only used at the time the router syncs with the exchange. After that the noise margin can drift up or down, depending on interference conditions. The range you mention isn't particularly unusual.

[lodge]

IP profile for your line is - 4000 kbps
DSL connection rate: 448 kbps(UP-STREAM)  5024 kbps(DOWN-STREAM)
Actual IP throughput achieved during the test was - 3811 kbps

Does this look okay chaps?

[roseway]

In themselves the figures match up, but the connection speed is less than it might be. If the connection is now stable, what ought to happen is that after some time your target noise margin should be reduced, which would yield a higher connection speed. This process doesn't seem to be well understood (by me at any rate) so I suppose that you cross your fingers for a couple of weeks and see what happens.