I had this behavior when I first started up, and it turned out that I had
the modem tty port jumpered to irq 5, but setserial -g showed it at irq 4.
I had to, (and currently still have to), execute a:
setserial /dev/ttyS2 irq 5
command to utilize the modem. Strangely, I actually got it to accept one
command after several attempts with the wrong IRQ!
just my $0.02,
At 05:47 PM 12/21/99, you wrote:
>I'm sorry Chris. Richard mentioned this process before. I was referring to
>something more along the lines of installation problems, bugs, etc. though.
>
>I did minicom-s and checked to see that serial port was /dev/ttyS1
>
>As far as I can tell that is the port it is on as per:
>
>[root@ /root]# setserial -g /dev/ttyS[0-9]
>/dev/ttyS0, UART: unknown, Port: 0x03f8, IRQ: 4
>/dev/ttyS1, UART: 16550A, Port: 0x02f8, IRQ: 3
>/dev/ttyS2, UART: unknown Port: 0x03e8, IRQ: 4
>/dev/ttyS3, UART: unknown Port: 0x02e8, IRQ: 3
>
>So I enter minicom and get the string:
>
>AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0
>
>Then when I type AT, I get no response.
>
>And that's the end of story.
>
>I have to kill it after waiting 15 minutes. And I'm back where I started. BTW,
>I don't have the manual.
>
>
>
>
>
>Chris Bennett wrote:
>
> > the only thing that can cause Minicon to work incorectly is a incorectly
> > configured serial port
> > to verify that the serial port is set up properly:
> > #ln -sf /dev/ttyS0 /dev/modem (for com1)
> > once in minicom Press Control + A Then S this will take you to minicom's
> > setup.
> > Verify that the port is set to either /dev/modem (if the above symlink
> is in
> > place) or the propper ttySx port here they are
> >
> > /dev/ttyS0 (com1)
> > /dev/ttyS1 (com2)
> > /dev/ttyS2 (com3)
> > /dev/ttyS3 (com4)
> >
> > If this is all corect then that is the only thing that would be screwed up
> > in Minicom
> >
> > Regards,
> > Chris Bennett
> >
> > > -----Original Message-----
> > > From: John Starkey [SMTP:[EMAIL PROTECTED]]
> > > Sent: Tuesday, December 21, 1999 7:14 PM
> > > To: Ray Olszewski
> > > Cc: Linux
> > > Subject: Re: The Newbie and the Modem....... something's changed.
> > >
> > > Ok. Lawson mentioned that a couple days ago, sorry. I'm in Minicom and I
> > > type
> > > AT and nothing happens. But I'm still not convinced minicom is working
> > > correctly.
> > >
> > > How do I know if minicom is working correctly. This may be a stupid
> > > question.
> > > But I am migrating from Windows. I spent an hour today helping my
> > > girlfriend
> > > troubleshoot a problem on her HP w/ Windows 98. I've heard of no less
> than
> > > 5
> > > problems with windows every week this year (+- a few). So I am used to
> > > things
> > > not working correctly. From what I can gather that isn't very common in
> > > Linux.
> > > Thank god.
> > >
> > >
> > >
> > > Ray Olszewski wrote:
> > >
> > > > Yes (at least usually yes - modem do vary). Try just sending "AT"
> > > followed
> > > > by a return - the modem should respond with "OK". But for the exact
> > > details
> > > > of how to communicate with your modem, you really have to look at its
> > > manual
> > > > -- there is a core of standard AT commands, but also many that vary
> from
> > > > modem to modem.
> > > >
> > > > At 04:50 PM 12/21/99 -0700, John Starkey wrote:
> > > > >So is there anyway to send a command to the modem and have it confirm
> > > it's
> > > > >existence?
> > > >
> > > > ------------------------------------"Never tell me the odds!"---
> > > > Ray Olszewski -- Han Solo
> > > > Palo Alto, CA [EMAIL PROTECTED]
> > > > ----------------------------------------------------------------
Rod Flancher
[EMAIL PROTECTED]
"The more I see, the more I see there is to see" - John Sebastion
