Date: Mon, 06 Apr 2009 20:51:25 -0700 From: Tim Kientzle <kientzle@freebsd.org> To: Robert Noland <rnoland@freebsd.org> Cc: current@freebsd.org Subject: Re: KDE4 and input events stalled Message-ID: <49DACDBD.3030809@freebsd.org> In-Reply-To: <1239075455.1908.36.camel@balrog.2hip.net> References: <49DA752B.5030805@freebsd.org> <934e1d760904061438k7d70d683re5c9d9a29e311942@mail.gmail.com> <934e1d760904061455o4736d643o1d07e3292192d94c@mail.gmail.com> <1239057809.1908.2.camel@balrog.2hip.net> <49DAC742.8090507@freebsd.org> <1239075455.1908.36.camel@balrog.2hip.net>
next in thread | previous in thread | raw e-mail | index | archive | help
>> Now, I have two other problems I'm trying to >> track down, either of which could be related to >> using Intel graphics: >> * On logout, screen dies (garbage all over). >> /var/log/messages reports that the Xorg server >> died with a segfault... > > This is definately broken on at least some Intel chips at the moment... > I'm working on it... I find that if I kill X by stopping gdm, things > seem to be ok... Using the logout or reset options in the gnome menus > does bad things... I'll play with a few things. For the record: agp0: <Intel 82945G (945G GMCH) SVGA controller> on vgapci0 I do have an Xorg.core here if a backtrace would help at all. >> * If I start kdm from /etc/ttys, I get a blank >> screen on startup. If I start it from a root >> login, it works okay for the first login. > > This sounds more like it is waiting on hal/dbus to start up than > anything. You might try using Option "AutoAddDevices" "off" in place of > or in addition to AllowEmptyInput. Startup messages claim that dbus and hal are both running at that point. Maybe I should try adding a sleep to the hal/dbus startups and see if that changes anything? Cheers, Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49DACDBD.3030809>