Very Computer

Thanks in advance.

Russell E. Smith

http://www.wolsi.com/~homerj/

/sbin/setserial /dev/cua2 auto_irq autoconfigure

That tries to determine the correct IRQ and port to use.  If it works,
then you're set, except that you'll need to do it everytime you boot.
Place the line in the file /etc/rc.d/rc.local so that it will be called
each time to boot.

If it doesn't work, and you know the IRQ, try

/sbin/setserial /dev/cua2 irq 5 autoconfigure

but replace 5 with the correct IRQ.  If that doesn't work, you will need
to specify both the IRQ and the port used by the modem like this:

/sbin/setserial /dev/cua2 irq 5 port 220

but replace the 5 and 220 with the appropriate values.  If you're using
Windows as well, you can get the correct values from the device manager.

If that doesn't work, I don't know what to tell you.

Good luck,

Lyle

   >I seem to be running into problems getting my modem to work under
   >kppp. Whenever I set it to the correct port (/dev/cua2 or
   >/dev/modem).  But whenever I attempt to query the modem, It says
   >the modem is busy. I am running COL 2.2 w/ KDE. A walkthrough would
   >be greatly appreciated, but any help would do.
   >Thanks in advance.
   >Russell E. Smith

   >http://www.wolsi.com/~homerj/
--------------------------------------------------------------------

Russell,

I had the same problem after bringing up COL 1.3 with a new 3Com USR
56K FAX/Modem.

Two things:

   (1.) the port you set up on should probably be /dev/ttyS2
        for COL 2.2 (the old COM4).

and

   (2.) 3Com USR Internal modems are increasingly a problem.
        I won't use another one.  They are being sold out of
        boxes poorly marked with respect to the product
        capability.  A 56K FAX/Modem INT with the same product
        number may have jumpers (Good!), be PnP (not as good),
        or be one of two varieties of erzatz WinModem.  The
        only way you can tell which you have is to open the
        box and look at the trailing two digits on the product
        number and call 3Com USR for the scoop.  If you happen
        to have purchased one of the modems with Windows drivers
        installed in its ROM it will *not* work with LINUX;
        they will tell you it is not a WinModem ('cause the
        software is not on the HD), but effectively it is; and
        they will not take it back (the shop that sold it to
        you has to do that and they have trouble understanding
        the problem).  The solution?  Buy a real internal modem
        with jumpers on it that you can know the configuration
        of with out doubt; worked for me :), bought a Zoom 56K
        dual mode FAX/Modem!

So, that's my two cents; hope it helps/illuminates.

--William

Does the modem have "Sportster" written somewhere on the card?  If it
does and has jumpers, it comes out of the box configured for Plug and
Pray.  Mine did.  I downloaded usrv90v.pdf from somewhere on the 3com
site.  It told me how to set the jumpers for a specific port.  I think I
set it for com2 (/dev/cua1) so as to not conflict with the mouse. You
may need to do a "ln -s /dev/cua1 /dev/modem"

If all that doesn't work, try the modem on a windows machine to see if
you have a hardware problem.

--

Out of my mind                                 back in 5 minutes