From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: evdev broken?
Date: Wed, 20 Jul 2011 07:05:10 +0100 [thread overview]
Message-ID: <201107200705.20857.michaelkintzios@gmail.com> (raw)
In-Reply-To: <CAHH9eM65vrHmEdhfyoO-8mEfn92oupJcQp8VqiiDvcqDy+fZkw@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 1625 bytes --]
On Wednesday 20 Jul 2011 04:38:37 Francisco Ares wrote:
> On Wed, Jul 20, 2011 at 12:10 AM, Francisco Ares <frares@gmail.com> wrote:
> > On Wed, Jul 20, 2011 at 12:05 AM, Grant Edwards
> > <grant.b.edwards@gmail.com
> >
> > > wrote:
> >> On 2011-07-20, Francisco Ares <frares@gmail.com> wrote:
> >> > Hi, All
> >> >
> >> > Recently, after blindingly emerging world, X11/Xorg stopped to accept
> >>
> >> mouse
> >>
> >> > and keyboard events. After some ways to figure out what was going on,
> >> > I found that it seems related to "evdev".
> >> >
> >> > Anybody noticed something like that? The xorg-server package (or
> >> > xorg-drivers, can't remember nor check now, because I had to use
> >> > Windows
> >> >
> >> >:-( ) is being built with "evdev" flag, but there is an error in the
> >> >:log
> >> >:
> >> > file about evdev could not be found, as long as "dri" and "dri2". I am
> >>
> >> using
> >>
> >> > nvidia proprietary video driver.
> >>
> >> You probably just need to re-emerge the xf86-input packages that you
> >> have installed. That happens after every update to the Xorg server,
> >> and there are probably messages in the portage log to that effect.
> >>
> >> --
> >> Grant
> >
> > Thank you, gonna try it
> >
> > --
> > Francisco
>
> It worked. Thanks a lot!! Back to Gentoo / X11 again ;-)
Every time after you emerge xorg you're meant to remerge its drivers (evdev
being one of them). Usually there is some elog message telling you to run
qfile to find what is need to be reinstalled:
qlist -I -C x11-drivers/
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-07-20 6:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 2:50 [gentoo-user] evdev broken? Francisco Ares
2011-07-20 3:05 ` [gentoo-user] " Grant Edwards
2011-07-20 3:10 ` Francisco Ares
2011-07-20 3:38 ` Francisco Ares
2011-07-20 6:05 ` Mick [this message]
2011-07-20 6:20 ` Dale
2011-07-20 11:27 ` Francisco Ares
2011-07-20 12:03 ` Alex Schuster
2011-07-20 11:23 ` Francisco Ares
2011-07-20 14:16 ` Grant Edwards
2011-07-20 14:36 ` Mick
2011-07-20 16:36 ` Alan McKinnon
2011-07-20 19:01 ` Grant Edwards
2011-07-20 16:37 ` Neil Bothwick
2011-07-20 22:34 ` Michael Orlitzky
2011-07-21 8:57 ` Neil Bothwick
2011-07-21 16:13 ` Michael Orlitzky
2011-07-21 16:44 ` Neil Bothwick
2011-07-20 3:05 ` [gentoo-user] " Arthur Barlow
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=201107200705.20857.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.com \
--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