[H-GEN] ppp problems under debian (slink)

[James C. McPherson]

[ Humbug *General* list - semi-serious discussions about Humbug and
Unix-related topics. ]


Patrick Nichols writes:
 > Byron Ellacott writes:
 > > apart, which means writing to /dev/modem has failed.  This could be a
 > > broken lock, a faulty DSR/DCD line (as mentioned earlier), the earlier
 > > pppd somehow not fully exiting yet removing its lockfile..
 > > I can't think why, specifically, but the problem is with writing (or
 > > possibly opening - check permissions?) to /dev/modem, or the appropriate
 > > device.
 > 
 > -After dialing in the first time, there are no stale locks in /var/lock.
 > -pppd isn't running after the first dialin ie. it exits properly (checked
 > with ps)
 > -I've changed modem cables to a spare I had here, this made no difference.
 > The computer hasn't been moved or tripped over.
 > -I've tried starting minicom to do some AT commands (after the first
 > dialin), but it crashed and spat garbage on the terminal when trying to
 > initalise the modem, requiring a "cat /bin/ls" to fix it.
 > -I tried using minicom to recreate the problem, but I can dial in and hang
 > up as many times as I like if I just use a terminal
 > 
 > It seems that Byron is correct.  It isn't permissions because I run both
 > minicom, and "pon uq" as root with sudo.  So it would seem that the problem
 > is with /dev/ttyS0, and opening or writing, or pppd does something funky
 > when it closes the port.
 > 
 > Any more suggestions.  Next thing I can think of it changing the port to
 > /dev/ttyS1, maybe the actual com port has gone in the computer (P100).
 > However if this were the case, why would it work perfectly on the first use
 > after boot?

if the actual circuit that controls the port has physically flaky hardware
(like a transistor going open collector or something more recent) then you may 
find that your reliability goes down the longer that your machine is turned
on. If your motherboard has a crack somewhere along a trace that's needed for
the port, you'll keep getting these problems because as the motherboard heats
up the cracks will tend to widen.

 > Could it be a corrupt file (a binary)?


doubtful. I'd suggest getting a new motherboard


James
--
Principal Software Architect	Phone: +61.2.9850.6280
APAF, Building F7B level 4	  Fax: +61.2.9850.6200
Macquarie University NSW 2109
AUSTRALIA

--
This is list (humbug) general handled by majordomo at lists.humbug.org.au .
Postings only from subscribed addresses of lists general or general-post.