Very Computer

by **Michael Sec** » Thu, 14 Oct 1999 04:00:00

I am running Red Hat 6.0 i386. I set up my ISP account/connection using
Kppp. My modem is on COM2 and /dev/ttyS1. On my first attempt to connect I
had a couple of errors: "Sorry, can't create modem lock file" and
"/etc/resolv.con is missing". These last two errors I have fixed by giving
kppp setuid root permissions and creating the /etc/resolv.conf file with the
proper domain name and server address.

Now when I connect I get a "Sorry, modem busy".

Modem is a Boca 56i.

I also tried this command but no go:

setserial /dev/ttyS1 irq 10 My modem is on com2 and the irq is 10. Still
get the modem busy.

So I tried changing the modem to /dev/ttyS2 at the device tab in kppp and
then setserial /dev/ttyS2 irq 10 Still get a modem busy. Any suggestions?

--
Michael Seck

by **Eugene Gro** » Fri, 15 Oct 1999 04:00:00

Hi
I've fiddled around a similar problem during more than a week ... I got
that modem busy msg just after updating to kde 1.1.2 .. finally, that's
Murphy's law, I found a broken com3 /dev/cua3 port .... . This story
makes me biting through many howto's and man pages.

now, first are you sure that irq10 is not used by other devices ?
then , try to chmode -c 666 /dev/ttySx or /dev/cuax
(I've read somewhere that ttySx is for dialing in mode and cuax for
dial-out mode, so it's better to set cuax (x=your port))
If it still not working try this : setserial -a /dev/cuax (information
about all the settings) with a 56k modem run setserial spd_vhi, maybe
change the UART according to your chip ..
That's the way i got working my modem ..
hope it helps
Eugene

> I am running Red Hat 6.0 i386. I set up my ISP account/connection using
> Kppp. My modem is on COM2 and /dev/ttyS1. On my first attempt to connect I
> had a couple of errors: "Sorry, can't create modem lock file" and
> "/etc/resolv.con is missing". These last two errors I have fixed by giving
> kppp setuid root permissions and creating the /etc/resolv.conf file with the
> proper domain name and server address.

> Now when I connect I get a "Sorry, modem busy".

> Modem is a Boca 56i.

> I also tried this command but no go:

> setserial /dev/ttyS1 irq 10 My modem is on com2 and the irq is 10. Still
> get the modem busy.

> So I tried changing the modem to /dev/ttyS2 at the device tab in kppp and
> then setserial /dev/ttyS2 irq 10 Still get a modem busy. Any suggestions?

> --
> Michael Seck

by **Frank Stefan** » Fri, 15 Oct 1999 04:00:00

Hi Michael,

if you use kppp, the file /etc/ppp/options MUST exist and MUST
be empty (in particular NO lock option).

In addition, you should /dev/ttyS? and not /dev/cua? because
the latter is deprecated due to documentation. It won't be
supported in future Linux versions.

HTH,
Frank.

Michael Seck schrieb: