Re: dial up

["Darren" <backdoc@netdoor.com>]

Thanks for the suggestions, Larry.

It seems pretty clear to me that OBSD is having problems detecting the modem
at boot.  I tried setting the jumpers alternatively to irq's 2, 5 and 7.  It
was already set to 3.  And, 4 was/is being used by pccom0.  BTW, the modem
is jumpered to COM4.

If you are booting with new hardware (not PnP), and if its settings don't
conflict with existing hardware, shouldn't OBSD find it without special
configuration?  I don't mind doing my homework on this, but I'm not sure
what man page to read next.


Thanks,
Darren

----- Original Message -----
From: "Laurence Moore" <lmoore@starwon.com.au>
To: "Darren Crotchett" <backdoc@netdoor.com>
Cc: <misc@openbsd.org>
Sent: Saturday, November 18, 2000 8:20 PM
Subject: Re: dial up


> Hi Darren.
>
> Darren Crotchett wrote:
> >
> > in dmesg that says:
> >
> > pccom0 at isa0 port 0x3f8/8 irq 4: ns16450, no fifo
> >
>
> I suspect this is your on-board uart as there is no fifo in it.
> Try changing the IRQ of your modem card to 5 and the I/O Addr to 0x3e8.
> I have a Hayes 5760 I think in an old motherboard and it is set to
> irq 5. I don't think the modem is in Plug-N-Play mode as Linux couldn't
> probe and detect it so there it has remained in Jumper configuration
> mode. This modem appears as;
>
> pccom2 at isa0 port 0x3e8/8 irq 5: ns16550a, 16 byte fifo
>
> > I think that if I could know for sure that my modem was accepting
> > commands, I could configure all of my .conf files by reading the man
pages
> > and all.
> >
>
> I use tip to test basic modem functionality. I would suggest you
> configure /etc/remote with a couple of lines like this;
>
> modem1:\
>       :dv=/dev/cua02:/br#115200:el=^C^S^Q^U^D:ie=%$:oe=^D:
>
> > One more thing that I've tried was echoing commands from the command
line
> > directly into the modem.  For example, IIRC I tried ehco > ATDT#######
> > /dev/cuaXX (where # is the phone number and XX is each port).  That
didn't
> > do anything either.
> >
>
> I have observed some difficulty in using the cua device with ppp when
> I'm running mgetty. I have instead used /dev/ttyXX for ppp and mgetty
> which seems to work fine.
>
> Cheers,
>
> Larry.
>