From owner-freebsd-questions Mon Sep 22 12:52:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA13840 for questions-outgoing; Mon, 22 Sep 1997 12:52:57 -0700 (PDT) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA13832 for ; Mon, 22 Sep 1997 12:52:46 -0700 (PDT) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id TAA18117; Mon, 22 Sep 1997 19:49:48 +0100 (BST) Message-Id: <199709221849.TAA18117@awfulhak.demon.co.uk> X-Mailer: exmh version 2.0zeta 7/24/97 To: Patrick Gardella cc: questions@FreeBSD.ORG, brian@awfulhak.com Subject: Re: PPP and X ?!? In-reply-to: Your message of "Mon, 22 Sep 1997 13:12:17 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 22 Sep 1997 19:49:48 +0100 From: Brian Somers Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Here is a strange error... > > I am running 2.2.1 on a P-133. I have a US Robotics X2 56K modem. The monitor > card is a STB Horizon 64V (PCI). PPP is Brian's 970921 source and X is 3.3.1. > ppp is ppp -auto -alias isp > > Now on to the problem. > > I cannot start X (startx) when PPP is connected to the ISP. The entire system > freezes just as the card switches to graphics mode. I am forced to reboot using > the Reset button on the front of my machine. > > If I go the other way around, starting ppp (dialing out) as I startx, I freeze > up ppp (which I can then kill and restart). > > If I startx, and then start ppp no problem. > > Nothing shows up in /var/log/ppp.log, by the way besides the normal messages ] > (LCP IPCP CCP). > > This happened with the standard 2.2.1 release of X and PPP as well. I upgraded > to the latest to see if that would work. > > I'm not sure how they are related. Any other pertinent info needed? Can you try moving your modem port ? If it's currently on sio2 or sio3, it may be conflicting in some way with your graphics card. I've seen this problem reported before.... the only thing I can guess is that there's a hardware conflict. > Patrick > > P.S. This is very easy to prevent, so I am able to work around it. It's just > annoying when I forget ;) > -- Brian , , Don't _EVER_ lose your sense of humour....