Then whatever is happening on your system is in the differences between yours and
mine I guess, I had no diald problems under 2.0 kernels.
The only useful thing I can say is that if you move to the 2.2 kernels you'll
probably need diald-0.99.
Bill wrote:
> COL 1.2 uses kernel 2.0.33. I'm using Linux/diald with a driver for
> a DirecPC satellite dish for downloading. The company that makes
> the driver (Helius) recommends Caldera Open Linux 1.2 or 1.3, so I
> haven't switched to the newer 2.2 kernel. Perhaps the 1.3 version
> of Caldera will solve the problem?
>
> This is probably an issue I should take up with Helius as well.
>
> > I don't think this problem is tied to the cu driver because the diald-0.16
> > problems I had appeared to be related to chat lockups too, and I was using the
> > ttyS driver.
> >
> > Which kernel is this on, Bill? My problems began when I moved to the 2.2
> > kernels. They;ve been partly ameliorated by switching to diald-0.99.
> >
> > Bill wrote:
> >
> > > I am running diald version .16.5 with COL 1.2 and ip masquerade. I
> > > am running into an occasional problem (about once a week) where
> > > diald (or chat) won't release a lock on the modem between
> > > sessions.
> > >
> > > When this happened last, I tried to debug the modem by going into
> > > minicom. I rec'd the message, "Dev cua2 is locked." The modem
> > > was not dialing out at the time. I tried deleting the lockfile in
> > > /var/lock, but it didn't seem to help.
> > >
> > > The /var/log/messages file said something like:
> > >
> > > ==============
> > > May 26 08:15:50 hh2134007 chat[16261]: send
> > > (ATM0DT83,5551515)
> > >
> > > May 26 08:15:51 hh2134007 chat[16261]: expect (CONNECT)
> > >
> > > May 26 08:16:36 hh2134007 chat[16261]: AT
> > >
> > > May 26 08:16:36 hh2134007 chat[16261]: alarm
> > >
> > > May 26 08:16:36 hh2134007 chat[16261]: Failed
> > >
> > > May 26 08:16:36 hh2134007 diald[88]: Connect script failed.
> > > ===============
> > >
> > > Rebooting fixes the problem. Besides this one problem, diald is
> > > working fine.
> > >
> > > Yes -- I know I should switch to the TTYs convention for serial
> > > ports. However, since cua2 seemed to be otherwise working fine,
> > > I've kept with it. Could this be the problem?
> > >
> > > Any suggestions? Thanks.
> > >
> > > Bill
--
[EMAIL PROTECTED] Ralph Clark, Virgo Solutions Ltd (UK)
__ _
/ / (_)__ __ ____ __ * Powerful * Flexible * Compatible * Reliable *
/ /__/ / _ \/ // /\ \/ / *Well Supported * Thousands of New Users Every Day*
/____/_/_//_/\_,_/ /_/\_\ The Cost Effective Choice - Linux Means Business!
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
