On Mon, 8 Feb 1999, Ray Olszewski wrote:
> 1. Make sure it isn't a Winmodem. (I know you said it isn't, but, to put it
> plainly, how sure are you?) Best way is to check it against the list at URL
> http://www.o2.net/~gromitkc/winmodem.html . Note that some Rockwell-based
> modems aren't quite "winmodems" but will work only if error correction is
> disabled; the Web page already cited has the details.
Well, in the box nothing looks like "Designed For Win95" or "Winmodem" or
something like that.
I'll se the webpage right now.
> 2. Figure out what port PnP is assigning it to. (COM1=/dev/ttyS0,
> COM2=/dev/ttyS1, COM3=/dev/ttyS2, COM4=/dev/ttyS3 .) See the PnP HowTo (at
> http://metalab.unc.edu/LDP/HOWTO/Plug-and-Play-HOWTO.html) for details --
> there are too many different ways to do this for me to guide you here.
I also have an ISA modem, it works fine but I have to change it for the
PCI one, my ISA modem works on ttyS3
> 3. Make sure there isn't an interrupt conflict. If the modem is on S0 or S2,
> check for anything else using IRQ 4. If on S1 or S3, check IRQ 3. To check,
> enter "more /proc/interrupts" and look for an entry for the appropriate IRQ.
> Possible conflicts can be your mouse or, in some cases, your NIC (Ethernet
> card).
my ISA modem work with IRQ 7, /proc/pci says that the new modem is IRQ 10,
and doesn't has conflicts with other devices.
> 4. Symlink /dev/modem to the appropriate actual dev. E.g., "ln -s /dev/ttyS0
> /dev/modem".
>
ok, it's done
> 5. Use setserial to probe /dev/modem ("setserial /dev/modem"). See if it
> returns a UART type. If it does, its' found a modem (more exactly, it's
> found a serial port, but if you have the right dev, that means it's found
> the modem).
it says that UART is unknown for PCI modem:
/dev/modem, UART: unknown,
the ISA says: /dev/modem, UART: 16550A, Port: 0x02e8, IRQ: 7, Flags: spd_vhi
by the way, I'm running Kernel 2.2.1 on a RedHat 5.2 box.
> If this gets you to a working system, then great. If not, a follow-up
> posting with the details of how far you got in this sequence before
> encountering trouble may let me or someone else on the list offer a specific
> suggestion.
well, I'm waiting for more suggestions ;-)
Thanks
David
