Colleagues, yes, I'm the next person to report Xorg upgrade problems ;) After thorough upgrade (ugh!!!) almost all work as expected, except one thing: on initial machine boot, X starts, gdm executes -- and then this console is not responded to either keyboard or mouse; however, I can switch to text console, log in and kill X server. After that, everything works correctly. Any hints? Thank you in advance. -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Dmitry! Dmitry Morozovsky wrote: | Colleagues, | | yes, I'm the next person to report Xorg upgrade problems ;) | | After thorough upgrade (ugh!!!) almost all work as expected, except one thing: | | on initial machine boot, X starts, gdm executes -- and then this console is not | responded to either keyboard or mouse; however, I can switch to text console, | log in and kill X server. After that, everything works correctly. | | Any hints? Thank you in advance. Just an idea: I saw excactly this behaviour with my keyboard and mouse (both USB, is this the case for you?) Setting Option "AllowEmptyInput" "off" in xorg.conf as described in UPDATING solved it for me (despite that it should not be needed anymore at all and especially not for keyboards.. :-) ) Hope it helps, Johannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJJhBgjAAoJEAtIjACLBioQ6hoP/2QiRi+43xI70pFSuq8FOzAr z+M84mdyM+04kEMtHVxTlRutSWS8aKRkfInl1B3++7qfxobyav0mIhHZBlEyQbUN xFWCms9sXdE7HSDRq3RNzFgeSuKrAxbapE6y46SJ2zSmaWQsNsxiZQR4gPwH7quh VFVemKxRk0Lmhk2wk81eW+sqfuT8v/nMgly3ShtFVPSFR5THmMTNcp23HChC2vyF +0yWuGsrQkittbHtoYuNo9Va8RUlpwLM85vB2nJtIe4VFZWK0C0EJrCjfSANV+lr /7K5XAZFqJBUtPubKLvE2hU1EyrKxf0fG22FTRwPf9A/q5n2OElZaN4ATPmC6eVy q/BZZkfJE+idt+864RCaQLsyaeYXWIW9bG011xsoR5oVNenOL9L5CLM3CDvUCxz9 5ORoAH7W1yQHtjsaqRQ9QD02kS6AEqON6APs/fu6wAuVw/w+WDDCikMOOeFczVZS lQ+dx64SejRbmsqNIqEXaLJPfAeTsQutSmioXrXjJynkO60ZglTiqyUjzv8+7G/6 7QjyixcExFrd0qOae4rxTkIis/+j1fPa+ClLBmy5gFir3LNdv0PxbUAgZqRUHGnd HZiewEjc0NaeTMzX3szBpjUS1o4uRPfhXpaC6Pcr0A5wxqhinJyQD6de5ZB78pKf eSHzmF7A9Dbd3cpEDQzR =G+Mu -----END PGP SIGNATURE-----
Dmitry Morozovsky wrote:> Colleagues, > > yes, I'm the next person to report Xorg upgrade problems ;) > > After thorough upgrade (ugh!!!) almost all work as expected, except one thing: > > on initial machine boot, X starts, gdm executes -- and then this console is not > responded to either keyboard or mouse; however, I can switch to text console, > log in and kill X server. After that, everything works correctly. > > Any hints? Thank you in advance. >You are facing the same problem as Oliver. Your X starts before the connection between hald und dbus is established and hence X does not find hald.
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: Jan 31 13:53:49 <console.info> revamp kernel: Starting dbus. Jan 31 13:53:50 <console.info> revamp kernel: Starting hald. Jan 31 13:53:50 <console.info> revamp kernel: Configuring syscons: Jan 31 13:53:50 <console.info> revamp kernel: blanktime Jan 31 13:53:50 <console.info> revamp kernel: . Jan 31 13:53:50 <console.info> revamp kernel: Starting gdm. Rather strange for me. -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------
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.
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 *** ------------------------------------------------------------------------