Hi Loki ...
>NONE of the commands is sent to the modem until I move
>a mouse !!!
>
>When I keep moving - all the initialization, dialing and
>handshaking go OK, but then, when dialup programm expects
>login prompt, everything stopps.
Amazed as I am that this works at all, you undoubtedly are experiencing an
IRQ conflict between your mouse (or, if it's a serial mouse, the com port to
which it is connected) and the com port to which your modem is connected (or
set, if it's an internal modem)
In the PC, COM1 and COM3 (/dev/ttyS0 and /dev/ttyS2 in Linux lingo) share
the same IRQ line (IRQ4) as do COM2 and COM4 (IRQ3), meaning that for most
purposes you can't use COM1 and COM3 (or COM2 and COM4) simultaneously. That
is, assuming you have your mouse connected to COM1, get your modem to use
COM2 (or 4) rather than COM3.
If it's an external modem, this simply means plugging it into the COM2
connector.
If it's an internal modem, you'll have to change some jumpers on the card.
Your modem manual will provide the necessary details. Also note that you'll
have to disable any onboard or otherwise present COM2, or configure it to
use COM3/COM4 (if it's onboard, you'll be able to do this from your BIOS,
otherwise jumpers again).
If it's a plug and play modem, it shouldn't really happen to begin with, so
your best best is, if your modem provides this capability, to disable the
PNP functionality alltogether (again a jumper), and proceed as above. Other
options might include using the Linux isapnptools to set the modem to the
correct settings, but I can't help you there.
[ does work in Windows ]
Looks as though the last options, a PNP modem, could be the case? If so, it
seems your modem boots up in a conflicting state, and Windows reprograms it
to a good state. Linux doesn't "do PNP" (out of the box) leaving things in
the conflicting state...
Hope this helps...
Best regards,
Rene
