Date: Tue, 11 Nov 2008 12:40:14 +0100 From: Mel <fbsd.questions@rachie.is-a-geek.net> To: freebsd-questions@freebsd.org Cc: Polytropon <freebsd@edvax.de>, Fbsd1 <fbsd1@a1poweruser.com> Subject: Re: trouble getting x11 xdm to work Message-ID: <200811111240.15930.fbsd.questions@rachie.is-a-geek.net> In-Reply-To: <491967CD.3050606@a1poweruser.com> References: <49184372.7010209@a1poweruser.com> <200811111147.03303.fbsd.questions@rachie.is-a-geek.net> <491967CD.3050606@a1poweruser.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200811111240.15930.fbsd.questions>