Date: Sat, 31 Jan 2009 15:48:16 +0300 (MSK) From: Dmitry Morozovsky <marck@rinet.ru> To: Dominic Fandrey <kamikaze@bsdforen.de> Cc: stable@freebsd.org Subject: Re: Xorg hangs on first boot Message-ID: <alpine.BSF.2.00.0901311545350.95497@woozle.rinet.ru> In-Reply-To: <49844712.6060105@bsdforen.de> References: <alpine.BSF.2.00.0901311144050.91263@woozle.rinet.ru> <49842FDA.1040101@bsdforen.de> <alpine.BSF.2.00.0901311414480.91263@woozle.rinet.ru> <49844712.6060105@bsdforen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 31 Jan 2009, Dominic Fandrey wrote: DF> > DF> You are facing the same problem as Oliver. Your X starts before the connection DF> > DF> between hald und dbus is established and hence X does not find hald. DF> > DF> > Well, but gdm rc.d script contains DF> > DF> > # REQUIRE: LOGIN cleanvar moused syscons dbus hald DF> > DF> > and console log shows correct order: ...> DF> > Rather strange for me. DF> > DF> DF> Yes, they start in the correct order, but the connection between them is not done DF> in time. This is a conceptual problem that can only be fixed properly upstream in DF> Xorg (the problem also exists with Linux distributions). The only workaround that DF> comes to mind is to operate X without hald or delay the start of gdm. Ah, I see detached cycle that waits not more than 60 seconds and does not probe hald. -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0901311545350.95497>