1. Did you really type "/setserial/ttyS2"? If so, that is at least part of
your problem. To probe with setserial, you'd have to type "setserial
/dev/ttyS2". If you didn't actually type it that way, try it and see if you
get a better result.
2. If you did type it correctly .... then the "UART unknown" message is bad
news. It means that setserial found something on that IRQ but could not
identify what it found. The most likely interpretation of that result is
that your modem is an HSP modem ("Winmodem") that will not work with Linux.
The alternative is that you did the isapnp config wrong.
3. To check the HSP possibility, please check your modem in the database at
http://www.o2.net/~gromitkc/winmodem.html . There are several different USR
internal modems listed there - some work with Linux and others don't. You
MUST figure out which kind you have before you go on wasting your own time
with configuration issues.
PS - Please turn off the "feature" of your mailer that appends html
duplicates of your postings. The custom on this list is to post in ascii.
At 03:33 AM 9/3/99 -0700, you ("Merenda, Frank") wrote:
>
>I couldn't get the internal USR to work. I did the isapnp, and it set up the
>modem correctly. I then did a "/setserial/ttyS2", and the UART was unknown,
>so the subsequent /setserial command may have set the port correctly, but
>didn't get the modem working. I tried every possible combination I could
>think of, but could not get the modem working at all.
>Am I missing something? I run (1) isapnp, (2) setserial (3) minicom to test
>the modem. That should be it, correct? If there is any information I could
>give that would help, please let me know. Thanks again for everyone's help.
[old stuff deleted]
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
Palo Alto, CA 94303-3603 [EMAIL PROTECTED]
----------------------------------------------------------------
