On Mon, 9 Jul 2001, Andrew W. Gaunt wrote:
> If this is the case, I must re-evaluate if I want to persue using
> "Winmodems" which may stop working if a different kernel is installed. I
> wouldn't expect hardware modems to have that problem.

  I highly recommend doing so in any event.  A "Winmodem" is not a modem; it
is a sound card.  They don't work very well under Windows, either.  I strongly
recommend replacing the sound card with a modem.  You can then do something
appropriate with the Winmodem, such as launching it into the Sun.

> The problem occurs when pppd is started (via mgetty's AUTO_PPP
> feature). It starts, then complains about an LCP timeout.
>
> LCP: timeout sending Config-Requests

  That means, quite simply, that pppd never got a response from its expected
peer.  The cause is usually a low-level comm error, i.e., bad modem, no PPP at
the far end, etc.

> There is a bit of a mismatch between the actual kernel rev. and what the
> driver's README implies it was written for/with.

  That might be the problem; kernel modules very often do not work between
revisions.  There are a lot of kernel options that can effect module
compatibility.  Try building the module from source.  (If you can't get
source, that is yet another reason to get a modem instead of the sound card
you currently have.)

> It compiled and installed without complaint and even works with minicom so
> I didn't think much about

  I believe (I am not sure) PPP is somewhat more integrated with the kernel
internals, so that might explain that.

-- 
Ben Scott <[EMAIL PROTECTED]>
| The opinions expressed in this message are those of the author and do not |
| necessarily represent the views or policy of any other person, entity or  |
| organization.  All information is provided without warranty of any kind.  |


**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************

Reply via email to