linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olh@suse.de>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: ibook ttyS0 (modem), and pppd problem, linux-2.2.17pre20ben2
Date: Sun, 8 Oct 2000 20:17:59 +0200	[thread overview]
Message-ID: <20001008201759.A16105@suse.de> (raw)
In-Reply-To: <Pine.SOL.4.10.10010080013120.22269-100000@joust.gpcc.itd.umich.edu>; from cziesler@umich.edu on Sun, Oct 08, 2000 at 01:58:01PM -0400


On Sun, Oct 08, Conrad H Ziesler wrote:

>
> The first time i run pppd after reboot, everything works great.
>
> however, if the remote host abruptly hangs up, then all future pppd
> instances yield the following trace in syslog:
>
> Oct  7 18:35:15 mwatt pppd[7318]: pppd 2.3.11 started by root, uid 0
> Oct  7 18:35:19 mwatt pppd[7318]: Hangup (SIGHUP)
> Oct  7 18:35:19 mwatt pppd[7318]: Connect script failed
>
> that is, pppd aborts without ever running chat.
> nothing i seem to do fixes this except reboot.
>
> note: if pppd exits cleanly from a session, then the next time it runs has
> no problem, however if the link gets disrupted, then the next (and all
> future) times it fails to work.
>
> i'm guessing there is some state in the serial driver that
> doesn't get cleared in all cases, or some such...

How looks the init string for the modem and does it work in MacOS?
If yes, what modem script do you use in MacOS?



Gruss Olaf

--
 $ man clone

BUGS
       Main feature not yet implemented...

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-10-08 18:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-08 17:58 ibook ttyS0 (modem), and pppd problem, linux-2.2.17pre20ben2 Conrad H Ziesler
2000-10-08 18:17 ` Olaf Hering [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-10-09 10:45 Halfmann, Klaus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20001008201759.A16105@suse.de \
    --to=olh@suse.de \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).