[
FaqProblemFr ] [
In English ] [
FaqProblemEs ] [
Deutsch? ]
[500] [19]
I cannot LOAD the DSP code
Check your modem is correctly plugged in and that the firmware has been successfully loaded. The DSP code cannot be loaded untill
the firmware has been.
Check also that the virtual filesystem /proc/bus/usb is mounted.
adictrl uses this filesystem to talk to the driver.
Check also adictrl and module have been compiled using the same gcc version as the kernel.
Be carefull if you have /usr in a separate partition!!!
After the firmware is uploaded to the modem, hotplug is calling
eaglectrl with the
-d option to upload the DSP code, but this is done very early during the boot sequence while only the root partition is mounted.
If
/usr is in a separate partition, hotplug cannot find
eaglectrl that is installed in
/usr/sbin (Mdk / RH / Fedora) or
/usr/local/sbin (by default).
You should wait for for the modem synchronization a very long time!...
A simple solution is to install
eaglectrl in
/sbin.
[501] [20]
I do not find the driver network interface
The driver network interface is created on demand, when the command
eaglectrl -i
is issued. This command also prints the interface name used by the driver to let you write your connection scripts.
[502] [21]
The modem uses the name of one of my network card !
Network interface names are allocated in sequence at their creation.
If the modem driver uses the name of one of your network card, it's because the initialization sequence of your system is wrong. In other words, you call the
eaglectrl -i sooner than the module load for the drivers of your other network cards.
Start the DSL connection later, that is after the other drivers initialization to solve this problem.
You can also force the name of the interface to use by setting the variable if_name at load time:
e.g.:
insmod eagle-usb.o if_name="eth9"
You may put it in
/etc/modules.conf to keep those parameters at boot time (in
/etc/modprobe.conf with kernel 2.6.x and perhaps
eagle_usb) :
options eagle-usb if_name="eth9"
[503] [22]
pppd dies prematurely
pppd quits when it lose the connection.
There are many good reasons to lose the connection. The most probable are certainly the following ones: the modem driver is not loaded, the modem hasn't yet synchronized with the DSL line, or the options specified for the connection are wrong.
If the connection is lost after a correct initialization, it is a true connection lost. In this case, you can force pppd to keep and try to reconnect with the persist option.
[504] [28]
The modem finds the DSL line, but I cannot connect
If the modem finds the DSL line but you still cannot connect, you may use either the wrong protocol or the wrong VPI/VCI numbers.
You can fix these options in the option file stored in
/etc/eagle-usb/.
VPI/VCI numbers are often specific to a countrey, however, this may change if several phone companies are present in your country. The default options shipped with the driver are for use in France only, you should therefore adapt these numbers to your local phone company.
[505] [29]
I can connect, but the connection is not usable
The French ISP Free has some problems with their equipments these days (the so-called "LNS"). These buggy equipments can accept
connections, but cannot make the bridge between your computer and their network. The connection is therefore unusable.
The best thing to do to solve this problem is to find another LNS.
To do this, the simplest thing is to disconnect with stopadsl and reconnect with startadsl.
These problems seem to be specific to the Free ISP in France. I do not known if other ISP have the same problems in other countries or with other ISPs. If this is the case, there may be a bug in the driver that prevents the LSN to route paquets.
I would like to have reports of such failures.
[506] [31]
I'm disconnected as soon as the upstream traffic becomes too high
It the upstream comes to prevent the LCP echo request of pppd from going out, pppd may lose the connection with the LNS.
To solve this problem, you can define a quality of service, increase the LCP echo request count before connection lost, and use the persist option of pppd to make it reconnect automatically in case the problem persists.
You may lose your connection as well when heavy disk access is made, if your DMA is not enabled. You can verify it with
hdparm -d /dev/hdx for hdx. To enable DMA :
hdparm -d1 /dev/hdx (if it does not work, verify that your motherboard chipset is supported and that DMA support is compiled in your kernel).
[507] [32]
I'm disconnected regularly but at random times
You can be disconnected often but at random times if you do not have a filtering plug on each phone socket where another device
is plugged in. These plug separate the DSL stream FROM the other stream and if you do not use them, some interference will occur and this can disturb the connection and even break it.
The solution is therefore to use these plugs on each phone socket for your DSL line.
[508] [33]
pppoa crashes with a signal 11 (SIGSEGV)
Former pppoa versions used to crash when they received packets that were not for them. These packets should certainly not occur, but some software (such as Samba or Cups) broadcast such packets on every network interface, even the modem network inteface (which
of course should not be receive them).
Upgrade the driver and fix the configuration of those softwares to not send packets on the driver Ethernet interface.
[509] [34]
The driver eats all my system memory !
Former versions of the driver (before 1.0.3) used to have a memory leak that ate all the system memory after a while, when the pppoa protocol was used.
Upgrade the driver as soon as possible.
[510] [35]
My computer sometimes freezes for 2 seconds
Former version (pre-1.0.3) used to actively wait during initilization/boot process, which leads to 2s freeze (per modem).
Version 1.0.3 should fix this problem using a desynchronization of the boot process.
The modem is reinitialized only when it crashes or when it lose the DSL line. If these freeze occur often, you should check your DSL line and check every phone socket has a filter on it.
[511] [36]
My computer freezes definitively and I have to reboot it
Former versions of the driver used to have a race condition that caused a kernel panic when the modem was reinitialized while packets were sent.
Upgrade the driver as soon as possible.
[512] [37]
The module does not LOAD at boot
Check the module is installed in the following directory:
/lib/modules/version/kernel/driver/usb
Check hotplug is installed and that the kernel is configured to use it.
Check that the module dependencies are up to date. CHECK the file
/lib/modules/version/usb.usermap to see if it contains references to
the eagle-usb.o module. Check you have a recent version of modutils.
[513] [38]
The module is loaded at boot, bug hotplug do not load the firmware or the DSP code
Hotplug should LOAD the firmware and the DSP code thanks to the script
/etc/hotplug/usb/eu_dsp
It is called whenever the modem declares itself on the USB bus with the USB identifiers that are specified in the file
/etc/hotplug/usb.usermap. Check these files are correct, and that the file
eu_dsp have execute permission.
[514] new
Web accesses are slow
If loading a web page takes a long time or if there's a "latency" before loading, it may be :
- either IPv6 support that causes the slowdown (see FaqDiagUs to disable it)
- or bad DNS : check file /etc/resolv.conf
Have a look at what displays
tail -f /var/log/messages in a terminal window, you may be too often disconnected because of line problems ?
[515] new
My PC becomes very slow
If you feel that X is freezing when connection is established add the following lines :
- to /etc/sysconfig/network (for Red Hat, Fedora & Mandrakelinux)
HOSTNAME=your_server_name
- to /etc/hostname (for Debian and derived)
your_server_name
127.0.0.1 your_server_name
It will be cool to have a name for your server ;-) and it will solve your slowness problems that are caused by X using your server name to access the DISPLAY (+ all gethostbyname that are around...)
