From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1C4s6a-0005AM-LY for qemu-devel@nongnu.org; Tue, 07 Sep 2004 22:22:40 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1C4s6Y-0005AA-Qo for qemu-devel@nongnu.org; Tue, 07 Sep 2004 22:22:40 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1C4s6Y-0005A7-Nl for qemu-devel@nongnu.org; Tue, 07 Sep 2004 22:22:38 -0400 Received: from [81.209.184.159] (helo=dd2718.kasserver.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1C4s0l-0007Rt-Bg for qemu-devel@nongnu.org; Tue, 07 Sep 2004 22:16:39 -0400 Received: from [192.168.0.7] (dsl-082-082-143-108.arcor-ip.net [82.82.143.108]) by dd2718.kasserver.com (Postfix) with ESMTP id 97A171C897 for ; Wed, 8 Sep 2004 04:16:37 +0200 (CEST) Message-ID: <413E6B95.4010406@fabianowski.de> Date: Wed, 08 Sep 2004 04:16:53 +0200 From: Bartosz Fabianowski MIME-Version: 1.0 Subject: Re: [Qemu-devel] Running Linux on Mac OS X References: <33ECF18C-010C-11D9-99AC-00039347B912@mac.com> <413E2145.5090607@dblab.ece.ntua.gr> <1686FFAF-0133-11D9-9549-00039346A7A8@mac.com> <8A83D328-013B-11D9-9549-00039346A7A8@mac.com> In-Reply-To: <8A83D328-013B-11D9-9549-00039346A7A8@mac.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org > XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" > after 0 requests (0 known processed) with 0 events remaining. I don't know what is wrong, I just have a few ideas of where to look. First of all, what does X's log file say? It should be located at "/var/log/XFree86.0.log". Second, if kdm or xdm is starting X in the background, you might want to disable that and be sure that the X you are starting manually is the only X running on the system. This way, you should get the stuff that goes into the log file dumped into your console as well. Maybe those X logs will say what's going wrong or at least where something odd happens. - Bartosz