From owner-freebsd-questions@FreeBSD.ORG Tue Nov 11 11:40:18 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D2A371065687 for ; Tue, 11 Nov 2008 11:40:18 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from mail.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id 94FB48FC21 for ; Tue, 11 Nov 2008 11:40:18 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from localhost (mail.rachie.is-a-geek.net [192.168.2.101]) by mail.rachie.is-a-geek.net (Postfix) with ESMTP id BB44EAFCF54; Tue, 11 Nov 2008 02:40:17 -0900 (AKST) From: Mel To: freebsd-questions@freebsd.org Date: Tue, 11 Nov 2008 12:40:14 +0100 User-Agent: KMail/1.9.7 References: <49184372.7010209@a1poweruser.com> <200811111147.03303.fbsd.questions@rachie.is-a-geek.net> <491967CD.3050606@a1poweruser.com> In-Reply-To: <491967CD.3050606@a1poweruser.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200811111240.15930.fbsd.questions@rachie.is-a-geek.net> Cc: Polytropon , Fbsd1 Subject: Re: trouble getting x11 xdm to work X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Nov 2008 11:40:18 -0000 On Tuesday 11 November 2008 12:09:01 Fbsd1 wrote: > Mel wrote: > > On Tuesday 11 November 2008 11:35:41 Fbsd1 wrote: > >>>> Still getting error msg > >>>> init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 > >>>> second > > > > You first need to get rid of that. xdm can't open /dev/ttyv8 while getty > > is hammering at it. > > I turned that off all ready before running xdm from root command line. What does xdm -debug 1 turn up? You said nothing related to xdm in /var/log/Xorg.0.log, but it would still be helpful to see the last lines of the file, so we know why X quit. And since Xorg.0.log isn't timestamped, check if the last modification time of the file corresponds with the last time you ran the command. This will determine if xdm actually gets to the stage of starting the X server or gives up sooner. You may also want to set the -error option (see man xdm) and check if anything useful is written there. With current information, the possible causes range from errors in a configuration file xdm reads on start up to X display problems. -- Mel Problem with today's modular software: they start with the modules and never get to the software part.