Bug 7713 - PPP can't initialize modem after first connect.
Summary: PPP can't initialize modem after first connect.
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: ppp
Version: 6.1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 1999-12-09 23:10 UTC by dedwards
Modified: 2008-05-01 15:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2002-12-14 01:49:32 UTC

Attachments (Terms of Use)

Description dedwards 1999-12-09 23:10:46 UTC
I am running PPP on two different linux boxes. One is a 400 Mhz Celeron
256 MB ram, 9 Gb Scsi HD,and an ext. Sporster 56K fax/modem. The other
macine is a 133 Mhz Pent with one 3 Gb IDE HD, one 10 GB IDE HD, 192 MB
ram, and an internal 56K Sportster fax/modem. I have loaded the latest PPP
patch. Both modems dialed and connected with no problem, but after using
the modems from 1.5 to 2 hours and then rebooting the machines ppp stops
working. I was able to configure the modems after installing the rp3
patch. But the machine just sits there when I try to dial with rp3 or the
control-panel or wvdial after the first time.  'ifup ppp0' doesn't work
either. The same thing has happened on both machines. I get either a GTK+
error about setting or comparing some var to NULL or I get an error 6. I
may also get modem is busy or unavailable. I have tried reinstalling the
connections, running 'ifdown ppp0' then 'ifup ppp0' and even rebooting the
machines. Nothing seems to reset the modem or allow ppp to start

Comment 1 Nalin Dahyabhai 2000-01-31 13:30:59 UTC
If you're getting errors from GTK+, please update rp3 to the latest errata or
the version from Raw Hide, which has had several of these bugs fixed.

Error 6, according to the pppd man page, is an inability to lock the serial
port.  This means that you either still have an errant pppd process running
(which can be killed with "killall -9 pppd"), or you have a stale lock file
(/var/lock/LCK..<modemdevice>) which can probably be removed safely.  I
suspect the latter if the problem continues across reboots.

Please let me know if this solves the problem.

Comment 2 Alan Cox 2002-12-14 01:49:32 UTC
No reply in two years

Note You need to log in before you can comment on or make changes to this bug.