On Fri, Mar 20, 1998 at 11:30:27AM -0400, [EMAIL PROTECTED] wrote:
>
> Yep, I lied. I thought I had posted my last message of the day, but there
> has been an outpouring of requests for the loggin surrounding my PPP
> problem. I concede that I should have included it in my original posting.
>
> There have also been requests for my config files. As I've explained to
> several individual respondents, the "box in question" is at home and I'm at
> work, so I don't have access to those files. One respondent did mention
> that I might check the permissions on those files (a good idea, and one
> that I'm ashamed to have not come up with on my own), so I'll do that when
> I get home (or maybe have my wife look for me -- no, probably not. :)
>
> Anyway, here are the highlights of the logging generated by a vanilla
> unsuccessful request:
>
> chat[5737]SIGHUP
> chat[5737]Can't restore terminal parameters: I/O error
> pppd[5747]: pppd 2.2.0 started by root, uid 0
> pppd[5747]: Removed stale lock on ttyS2 (pid 5729(
> chat[5748]: abort on (BUSY)
> chat[5748]: abort on (NO CARRIER)
> chat[5748]: abort on (VOICE)
> chat[5748]: abort on (NO DIALTONE)
> chat[5748]: send (ATDT4042873038^^M)
> chat[5748]: expect (ogin)
> kernel: PPP: ppp line discipline successfully unregistered
> chat[5748]: ATDT4042873038^^M^^M
> chat[5748]: alarm
> chat[5748]: Failed
> pppd[5747]: Connect script failed
I used to have this, but havn't for some time. It seems like the magic step
was to stop sharing IRQs (although this does seem a little odd). I used to
have:
/dev/ttyS0 4
/dev/ttyS1 3
/dev/ttyS2 4
now I have
/dev/ttyS0 4
/dev/ttyS1 3
/dev/ttyS2 2 (NB: IRQ2 = IRQ9)
by adding this to /etc/rc.boot/0setserial:
${SETSERIAL} -b /dev/ttyS2 uart 16550A port 0x3E8 irq 2 ${STD_FLAGS}
(and changing the jumpers on the modem!)
Before you go through all this, I'd suggest extending the timeout - by
putting this at the top of the chatscript:
TIMEOUT 60
It seems very odd that there is *no* reponse from the other side. I don't
know how PAP works, but it might be that the ISP is using this - I believe
you need to have "auth" in the /etc/ppp/options file.
> By the way, I'm very impressed and pleased by the vast and rapid response.
> At the same time, it's troubling to see the negative thoughts floating
> around about the future of Debian. Of course, the two threads contradict
> each other, don't they? The success of any product is directly
> proportional to the support of it's users. That's my initial impression,
> anyway.
Don't worry too much about it, I'm sure everything will look up when hamm is
released in just over a month (probably).
> While I'm not an application developer and cannot help on that side of
> things, I am a rather experienced web developer. If my services could be
> used for the further advancement of Debian's mission, I'm sure you'll let
> me know.
You're more than welcome to look around the web site and see what you think
needs improving. Have a chat with the webmaster - Sue Campbell
<[EMAIL PROTECTED]>.
My only request is not to turn it into a site where you need java just to
click on a button and a T1 connection to download lots of full-screen videos
and MP3 (unless I'm viewing it at work :-)
Maybe looking at the bugs database will help - there are a few suggestions
in there. I think a few of those involve more advanced options for the bugs
database, so depending on what kind of web development you do, you may or
may not be able to fix them!
Packaging programs isn't too difficult, just start off with something simple
before trying to package X-windows or the various emacs parts :-)
Adrian
email: [EMAIL PROTECTED] | Debian Linux - www.debian.org
http://www.poboxes.com/adrian.bridgett | Because bloated, unstable
PGP key available on public key servers | operating systems are from MS
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
