public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Cc: Mick <michaelkintzios@gmail.com>
Subject: Re: [gentoo-user] xorg-drivers for mouse and keyboard confusion
Date: Sat, 26 Feb 2011 11:36:50 -0800	[thread overview]
Message-ID: <AANLkTimJe9KwujkcobZH0OfdgcFajT=gKB3bvAi+gAOJ@mail.gmail.com> (raw)
In-Reply-To: <201102261504.13309.michaelkintzios@gmail.com>

On Sat, Feb 26, 2011 at 7:04 AM, Mick <michaelkintzios@gmail.com> wrote:
> On Saturday 26 February 2011 11:26:38 Jesús J. Guerrero Botella wrote:
>> You could always grep for INPUT_DEVICES into /etc/portage, user -R for
>> recursive search.
>>
>> Also, make sure there's no other statement for INPUT_DEVICES in
>> make.conf after the one you posted above.
>
> Thanks, I checked for duplicate entries in make.conf (there aren't any) and
> nothing is shown under /etc/portage ... what now?
> --
> Regards,
> Mick
>

Did you double check /var/lib/portage/world to make sure they aren't
(somehow) still in there?

I don't know if you use modules-rebuild but if so have you removed
them from the list of things that you rebuild when you make a new
kernel?

If you let the system re-emerge them, make sure you're -DuN @world
clean, then emerge -C them, use --depclean to get everything out, I
bet they'll be gone.

Very strange...

Good luck,
Mark



  reply	other threads:[~2011-02-26 20:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-26  8:38 [gentoo-user] xorg-drivers for mouse and keyboard confusion Mick
2011-02-26 11:26 ` Jesús J. Guerrero Botella
2011-02-26 15:04   ` Mick
2011-02-26 19:36     ` Mark Knecht [this message]
2011-02-26 23:21     ` Jesús J. Guerrero Botella
2011-02-27  9:53       ` Mick
2011-02-27 14:33 ` Mark Knecht
2011-02-27 14:58   ` Mick
2011-02-27 17:43     ` Mike Gilbert

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='AANLkTimJe9KwujkcobZH0OfdgcFajT=gKB3bvAi+gAOJ@mail.gmail.com' \
    --to=markknecht@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    --cc=michaelkintzios@gmail.com \
    /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