From: "Pintér Tibor" <tibyke@tibyke.hu>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] GDM kbd/mouse lockup after emerge --update on a stable amd64 platform - need hints to cure
Date: Thu, 22 Dec 2011 08:00:10 +0100 [thread overview]
Message-ID: <kdaot1356jny9l7ywh0fmnca.1324537210645@email.android.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2915 bytes --]
Reemerge all xf86* packages
Quite obvious as the log clearly gives the clue (new xorg server version, driver version mismatch)
t
"G.Wolfe Woodbury" <redwolfe@gmail.com> wrote:
I did:
emerge -va --update --deep --newuse @world
on a stable gentoo amd64 (multilib) system after switching the profile
from "desktop/gnome" to "desktop" and adding
qt4 and kde flags to make.conf. [I wan to add a few kde apps to the
mix, but not everything.]
Since then, I get a keyboard and mouse lockup when gdm starts. and can't
login graphically or switch to a text console.
I'd rather not do a complete re-install on that instance, so some clue
as to where to look for problems beyond the obvious dmesg
and boot info.
I do get a "dmeventd" failure to start, so lvm-monitoring fails to start
(even after a re-emerge of lvm2) but don't think that as anything to do
with the X lockup. Startx from single user mode also causes a kbd/mouse
lockup.
I've verified that the kernel has the proper event configuration.
Perusing the Xorg.0.log reveals evdev failing to load:
> [ 410.507] (II) LoadModule: "evdev"
> [ 410.507] (II) Loading /usr/lib64/xorg/modules/input/evdev_drv.so
> [ 410.513] (II) Module evdev: vendor="X.Org Foundation"
> [ 410.513] compiled for 1.10.4, module version = 2.6.0
> [ 410.513] Module class: X.Org XInput Driver
> [ 410.513] ABI class: X.Org XInput driver, version 12.2
> [ 410.513] (EE) module ABI major version (12) doesn't match the
> server's version (13)
> [ 410.513] (II) UnloadModule: "evdev"
> [ 410.513] (II) Unloading evdev
> [ 410.513] (EE) Failed to load module "evdev" (module requirement
> mismatch, 0)
> [ 410.513] (EE) No input driver matching `evdev'
> [ 410.513] (II) config/udev: Adding input device Power Button
> (/dev/input/event1)
> [ 410.513] (**) Power Button: Applying InputClass "evdev keyboard
> catchall"
> [ 410.513] (II) LoadModule: "evdev"
> [ 410.513] (II) Loading /usr/lib64/xorg/modules/input/evdev_drv.so
> [ 410.513] (II) Module evdev: vendor="X.Org Foundation"
> [ 410.513] compiled for 1.10.4, module version = 2.6.0
> [ 410.513] Module class: X.Org XInput Driver
> [ 410.513] ABI class: X.Org XInput driver, version 12.2
> [ 410.513] (EE) module ABI major version (12) doesn't match the
> server's version (13)
> [ 410.513] (II) UnloadModule: "evdev"
> [ 410.513] (II) Unloading evdev
> [ 410.513] (EE) Failed to load module "evdev" (module requirement
> mismatch, 0)
> [ 410.513] (EE) No input driver matching `evdev'
> [ 410.514] (II) config/udev: Adding input device Sleep Button
> (/dev/input/event0)
which tell me something went wrong in the re-emerge of xorg something,
but I'd like to get a clue as to just what to do to fix it.
Thanks in advance for any help.
--
G.Wolfe Woodbury
aka redwolfe@gmail.com
[-- Attachment #2: Type: text/html, Size: 3660 bytes --]
next reply other threads:[~2011-12-22 7:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-22 7:00 Pintér Tibor [this message]
2011-12-22 8:02 ` [gentoo-user] GDM kbd/mouse lockup after emerge --update on a stable amd64 platform - need hints to cure G.Wolfe Woodbury
2011-12-22 12:58 ` Alex Schuster
2011-12-23 5:12 ` Michael Mol
2011-12-23 5:46 ` Dale
2011-12-23 12:55 ` Michael Mol
2011-12-23 14:02 ` Dale
2011-12-23 10:38 ` Mick
2011-12-23 12:57 ` Michael Mol
2011-12-23 14:05 ` Dale
2011-12-23 14:38 ` Michael Mol
2011-12-23 23:17 ` Dale
2011-12-23 23:47 ` Neil Bothwick
2011-12-25 2:56 ` Stroller
-- strict thread matches above, loose matches on Subject: below --
2011-12-22 6:16 G.Wolfe Woodbury
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=kdaot1356jny9l7ywh0fmnca.1324537210645@email.android.com \
--to=tibyke@tibyke.hu \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox