From: Alex Schuster <wonko@wonkology.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: evdev broken?
Date: Wed, 20 Jul 2011 14:03:48 +0200 [thread overview]
Message-ID: <3142440.jWue4OGtAY@weird> (raw)
In-Reply-To: <CAHH9eM6+HwyWCpPJa2Z=h-tsiCNZzG2fKus1qtcOin2j4z1EMA@mail.gmail.com>
Francisco Ares writes:
> On Wed, Jul 20, 2011 at 3:20 AM, Dale <rdalek1967@gmail.com> wrote:
> > Mick wrote:
> >> 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/
> >
> > I think this works too:
> >
> > emerge -1av @x11-module-rebuild
> >
> > Correct me if I am wrong here.
> Thanks for replying, but emerge tells me there are no sets to satisfy
> 'x11-module-rebuild' . Where would it come from? As far as I could tell,
> those sets are manually set, isn't it?
No, you just need a newer portage, probably a version >= 2.2. This seems to
be safe and is often suggested here on this list. Although there are
frequent updates and I wonder if some big bug might slide into portage one
day.
If you want to do so, put
<sys-apps/portage-9999 **
in /etc/portage/package.accept_keywords. Or something like
=sys-apps/portage-2.2.0_alpha45
to install this version only, but I guess when it moves out of the portage
tree it will be downgraded, so you'd need to put the ebuild into your local
overlay then.
> And by the way, what is the use of 'xorg-drivers' package ?
I think it's just some sort of meta package pulling in the real drivers. At
least the output of equery files xorg-drivers is empty.
Wonko
next prev parent reply other threads:[~2011-07-20 12:05 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
2011-07-20 6:20 ` Dale
2011-07-20 11:27 ` Francisco Ares
2011-07-20 12:03 ` Alex Schuster [this message]
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=3142440.jWue4OGtAY@weird \
--to=wonko@wonkology.org \
--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