cxacru.txt 2.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100
  1. Firmware is required for this device: http://accessrunner.sourceforge.net/
  2. While it is capable of managing/maintaining the ADSL connection without the
  3. module loaded, the device will sometimes stop responding after unloading the
  4. driver and it is necessary to unplug/remove power to the device to fix this.
  5. Note: support for cxacru-cf.bin has been removed. It was not loaded correctly
  6. so it had no effect on the device configuration. Fixing it could have stopped
  7. existing devices working when an invalid configuration is supplied.
  8. There is a script cxacru-cf.py to convert an existing file to the sysfs form.
  9. Detected devices will appear as ATM devices named "cxacru". In /sys/class/atm/
  10. these are directories named cxacruN where N is the device number. A symlink
  11. named device points to the USB interface device's directory which contains
  12. several sysfs attribute files for retrieving device statistics:
  13. * adsl_controller_version
  14. * adsl_headend
  15. * adsl_headend_environment
  16. Information about the remote headend.
  17. * adsl_config
  18. Configuration writing interface.
  19. Write parameters in hexadecimal format <index>=<value>,
  20. separated by whitespace, e.g.:
  21. "1=0 a=5"
  22. Up to 7 parameters at a time will be sent and the modem will restart
  23. the ADSL connection when any value is set. These are logged for future
  24. reference.
  25. * downstream_attenuation (dB)
  26. * downstream_bits_per_frame
  27. * downstream_rate (kbps)
  28. * downstream_snr_margin (dB)
  29. Downstream stats.
  30. * upstream_attenuation (dB)
  31. * upstream_bits_per_frame
  32. * upstream_rate (kbps)
  33. * upstream_snr_margin (dB)
  34. * transmitter_power (dBm/Hz)
  35. Upstream stats.
  36. * downstream_crc_errors
  37. * downstream_fec_errors
  38. * downstream_hec_errors
  39. * upstream_crc_errors
  40. * upstream_fec_errors
  41. * upstream_hec_errors
  42. Error counts.
  43. * line_startable
  44. Indicates that ADSL support on the device
  45. is/can be enabled, see adsl_start.
  46. * line_status
  47. "initialising"
  48. "down"
  49. "attempting to activate"
  50. "training"
  51. "channel analysis"
  52. "exchange"
  53. "waiting"
  54. "up"
  55. Changes between "down" and "attempting to activate"
  56. if there is no signal.
  57. * link_status
  58. "not connected"
  59. "connected"
  60. "lost"
  61. * mac_address
  62. * modulation
  63. "" (when not connected)
  64. "ANSI T1.413"
  65. "ITU-T G.992.1 (G.DMT)"
  66. "ITU-T G.992.2 (G.LITE)"
  67. * startup_attempts
  68. Count of total attempts to initialise ADSL.
  69. To enable/disable ADSL, the following can be written to the adsl_state file:
  70. "start"
  71. "stop
  72. "restart" (stops, waits 1.5s, then starts)
  73. "poll" (used to resume status polling if it was disabled due to failure)
  74. Changes in adsl/line state are reported via kernel log messages:
  75. [4942145.150704] ATM dev 0: ADSL state: running
  76. [4942243.663766] ATM dev 0: ADSL line: down
  77. [4942249.665075] ATM dev 0: ADSL line: attempting to activate
  78. [4942253.654954] ATM dev 0: ADSL line: training
  79. [4942255.666387] ATM dev 0: ADSL line: channel analysis
  80. [4942259.656262] ATM dev 0: ADSL line: exchange
  81. [2635357.696901] ATM dev 0: ADSL line: up (8128 kb/s down | 832 kb/s up)