Date: Sat, 31 Jan 2009 13:41:54 +0100 From: Dominic Fandrey <kamikaze@bsdforen.de> To: Dmitry Morozovsky <marck@rinet.ru> Cc: stable@freebsd.org Subject: Re: Xorg hangs on first boot Message-ID: <49844712.6060105@bsdforen.de> In-Reply-To: <alpine.BSF.2.00.0901311414480.91263@woozle.rinet.ru> References: <alpine.BSF.2.00.0901311144050.91263@woozle.rinet.ru> <49842FDA.1040101@bsdforen.de> <alpine.BSF.2.00.0901311414480.91263@woozle.rinet.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Dmitry Morozovsky wrote: > On Sat, 31 Jan 2009, Dominic Fandrey wrote: > > DF> > After thorough upgrade (ugh!!!) almost all work as expected, except one thing: > DF> > > DF> > on initial machine boot, X starts, gdm executes -- and then this console is not > DF> > responded to either keyboard or mouse; however, I can switch to text console, > DF> > log in and kill X server. After that, everything works correctly. > DF> > > DF> > Any hints? Thank you in advance. > DF> > > DF> > DF> You are facing the same problem as Oliver. Your X starts before the connection > DF> between hald und dbus is established and hence X does not find hald. > > Well, but gdm rc.d script contains > > # REQUIRE: LOGIN cleanvar moused syscons dbus hald > > and console log shows correct order: ...> > Rather strange for me. > Yes, they start in the correct order, but the connection between them is not done in time. This is a conceptual problem that can only be fixed properly upstream in Xorg (the problem also exists with Linux distributions). The only workaround that comes to mind is to operate X without hald or delay the start of gdm.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49844712.6060105>