Trevin Beattie wrote:
> 
> I've recently installed NetBSD 1.4Beta on a new computer, and tried to
> configure it as closely as possible to my original system runnig NetBSD
> 1.3.2.  For some reason, I can't get pppd to communicate with the modem
> on tty00.  When I run pppd, it starts the chat program which is supposed
> to dial out, but chat exits without doing anything, and then pppd just
> sits idle.  What's worse, if I try to kill pppd, NetBSD somehow loses
> the ability to exec any new process, so I'm forced to reset the
> computer.

I'm not sure how, but after I ran the 1.3 version of pppd and chat, I'm
suddenly able to get *.debug logs!  So here's what is reported:

May 14 19:08:40 clay pppd[427]: pppd 2.3.1 started by trevin, uid 0
May 14 19:08:41 clay chat[429]: abort on (BUSY) 
May 14 19:08:41 clay chat[429]: abort on (NO CARRIER) 
May 14 19:08:41 clay chat[429]: report (CONNECT) 
May 14 19:08:41 clay chat[429]: send (atz0^M) 
May 14 19:08:42 clay chat[429]: expect (OK) 
May 14 19:09:27 clay chat[429]: alarm
May 14 19:09:27 clay chat[429]: Failed
May 14 19:09:27 clay pppd[427]: Connect script failed
May 14 19:09:55 clay pppd[427]: Terminating on signal 15.
May 14 19:09:55 clay pppd[427]: tcsetattr: Interrupted system call

(19:09:55 is where I explicitly killed pppd.)  After this point, I was
still able to run commands until I tried to "ls -l /dev/tty00".  At that
point, the kernel locked up and I was forced to reset the CPU.

-----------------------

Since I can't connect to the 'net with NetBSD, I won't be able to
retrieve any email.  Please post any replies to the newsgroup
comp.unix.bsd.netbsd.misc.
-- Trevin