> Yes your absolutely correct it can cause conflicts pretty easily.
> you should only need to check other serial devices however. The Biggest
> problem that I could think about is if com1 is enabled on the motherboard.
> (F2 at boot) it is not that linux is not able to handle plug and play
> (that's what isapnp is for but I'm not real good at it so this is what I'd
> recommend. try it now and see if you can get any response from AT in minicom
I removed all ISA cards and now I get
[root@LinuxBox /root]# minicom
Device /dev/ttyS0 is locked.
Obviously I haven't changed the jumpers yet.
Too much typing not enough working :}
>
>
> Regards,
> Chris Bennett
>
> > -----Original Message-----
> > From: John Starkey [SMTP:[EMAIL PROTECTED]]
> > Sent: Tuesday, December 21, 1999 8:54 PM
> > To: Chris Bennett
> > Subject: Re: The Newbie and the Modem....... something's changed.
> >
> > Ahhhh....
> >
> > The jumpers were set for PnP (but I turned that off in the setup (F2 at
> > Boot).
> >
> > I set them to Comm1, which was the easiest. I wasn't sure about the
> > diagram. No
> > jumpers was PnP and all jumpers was Comm1. It was on the back so depending
> > on
> > how you turned the card over you could read the other two options
> > backwards.
> >
> > So now I will switch minicom to ttyS0. But am I going to interfere with
> > anything else? Should I pull the other cards to determine how they are
> > set. I
> > assume you can conflict pretty easily this way.
> >
> > BTW. (off topic) I just saw a fire engine laying face down on it's side in
> > a
> > gully down the street from me. I'm in Denver. Streets are getting pretty
> > bad
> > (snow and ice). Considering they are open in the back of the cab
> > somebody's
> > hurting. Ouch.......
> >
> > Chris Bennett wrote:
> >
> > > On the actual Modem Itself there Will be some pins. There Will be a
> > Little
> > > conector conecting the pins together if there are no conections on the
> > card
> > > then it is either Plug and play or it needs to be set through a software
> > > program.
> > >
> > > > -----Original Message-----
> > > > From: John Starkey [SMTP:[EMAIL PROTECTED]]
> > > > Sent: Tuesday, December 21, 1999 7:55 PM
> > > > To: Chris Bennett
> > > > Subject: Re: The Newbie and the Modem....... something's changed.
> > > >
> > > > How do I find this out???? I've heard of jumpers but I've never seen
> > them?
> > > >
> > > > Chris Bennett wrote:
> > > >
> > > > > ttyS1 so that means that the modem is Jumpered for Com 2 right?
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: John Starkey [SMTP:[EMAIL PROTECTED]]
> > > > > > Sent: Tuesday, December 21, 1999 7:47 PM
> > > > > > To: Chris Bennett
> > > > > > Cc: Ray Olszewski; Linux
> > > > > > Subject: Re: The Newbie and the Modem....... something's
> > changed.
> > > > > >
> > > > > > 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]
> > > > > > > > >
> > ----------------------------------------------------------------
