I have a USR Courier internal. It would not work under Linux if jumpered for
PnP. To have it properly installed, I:
1) logged in Windows, checked under "System Settings" which COM and IRQ Win98
was using through PnP;
2) jumpered the modem for the proper COM and IRQ, disabling PnP.
3) under linux, I used setserial and modemtool to properly finish my setup.
Hope it helps,
/Gustavo.
On dom, 19 set 1999, you wrote:
> Jeremy Kersenbrock wrote:
> >
> > OK, I am now down to one piece of hardware to configure. It's a USRobotics
> > Sportster internal modem. It is PnP with jumpers, although I currently have
> > it jumpered for PnP. I have isapnp running at startup, but I must need to
> > do something else. By the way, I have read the Modem HOW-TO and the
> > isapnptools documentation and both are highly technical and unclear. Both
> > explain very thoroughly what is happening, but neither explain how to make
> > the modem work!
> >
> > It appears that isapnp has it configured as ttys3 with a IO of 03f8-03ff.
> > But when I select /dev/modem in the setup for kppp, I get the message
> > "Sorry, can't open modem." So I select /dev/ttyS3 and get the message
> > "Sorry, modem is busy."
> >
>
> That might be true. But have you ran "setserial"?
>
> Linux seems to be defaulted to com 1, com 2.
> If this is indeed ttyS3 ( com 4 ) you need to run setserial.
>
> At a terminal type " man setserial " and read it.
> Then fix it. :)
> ALan
>
> ===============================================
> [EMAIL PROTECTED] ( [EMAIL PROTECTED] )
> Coming to you with Linux-Mandrake 6.0
