diff options
Diffstat (limited to 'kernel/xpp/README.Astribank')
| -rw-r--r-- | kernel/xpp/README.Astribank | 60 |
1 files changed, 58 insertions, 2 deletions
diff --git a/kernel/xpp/README.Astribank b/kernel/xpp/README.Astribank index 37af95b..5cf6804 100644 --- a/kernel/xpp/README.Astribank +++ b/kernel/xpp/README.Astribank @@ -588,6 +588,62 @@ Normaly this is not a problem. The driver will re-establish a connection once a new call needs to be made. +Both default and sysconfig Exist +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +.Symptoms: +The firmware fails to load. Manually running xpp_fxloader gives: + + Both '/etc/default/zaptel' and '/etc/sysconfig/zaptel' exist + +Alternatively: an initialization script fails and gives the error + + An '/etc/default/zaptel' collides with 'etc/sysconfig/zaptel' + +.Cause: +/etc/default/<service name> is the place used in Debian-based +systems for initialization scripts. /etc/sysconfig/<service name> is +used in Redhat and similar for the same purpose. For historical reasons +many of our programs read configuration from there: either from +/etc/default/zaptel or from /etc/sysconfig/zaptel . + +The problem is what to do if both of those exist. Selecting an arbitrary +one can lead to unexpected results. Likewise sourcing both of them. +Therefore we prefer to fail in a noisy and expected way. In the future +we will probably me to reading configuration from a file under /etc/zaptel . + +.Fix: +Remove one of those two. There should be no reason to have both on the +same system. + + +Astribank not initialized: Premature packet end +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +.Symptoms: +After upgrading to Zaptel 1.4.12 / 1.2.25 the initialization of the +Astribank times out. In the logs you see: + + kernel: NOTICE-xpp: XBUS-00(00): FIRMWARE: ERROR_CODE CODE = 0x3 (Premature packet end) + +.Cause: +When an Astribank is detected, the driver asks it what is its version +and what components it has. Normally if the version of the firmware and +of the driver does not match the driver gives an ugly message and fails +the initialization. + +However in the change of the protocol between versions 2.9 (29) and 3.0 +(30), the response that the new driver recieves from a device with the +old version is now considered to be an illegal packet and gets +discarded. As a result, the Astribank waits till time-out for the +initilization to end. + +.Fix: +Reset the firmware of the Astribank by either: + + /usr/share/zaptel/xpp_fxloader reset + +or disconnecting it from the power and reconnecting it. + + Reference --------- LEDs Indication @@ -1254,7 +1310,7 @@ rx_tasklet (xpp):: separate tasklets. This should probably help on higher-end systems with multiple Astribanks. -print_dbg (all modules):: +debug (all modules):: It will make the driver to print tons of debugging messages. You can set/unset the parameter at run-time. @@ -1274,7 +1330,7 @@ print_dbg (all modules):: For example, - echo 33 >/sys/modules/xpp/parameters/print_dbg + echo 33 >/sys/modules/xpp/parameters/debug forces module xpp to print general debugging messages (1) and procfs debugging messages (32). |