public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] New install, a few problems (or not?)
Date: Sat, 10 Sep 2016 08:06:03 +0000	[thread overview]
Message-ID: <493EC760-09F7-4F81-B348-B3E7C5AF190F@antarean.org> (raw)
In-Reply-To: <20160910071159.GA3024@waltdnes.org>

On September 10, 2016 9:11:59 AM GMT+02:00, waltdnes@waltdnes.org wrote:
>On Sat, Sep 10, 2016 at 12:18:51PM +1000, Adam Carter wrote
>
>> I just tried uninstalling xf86-video-vesa and xf86-video-fbdev to see
>if
>> they were required, and X still runs, so you can ignore those
>messages.
>> 
>> FWIW i'm kernel 4.7.2 with ~amd64 on a skylake i3.
>> 
>> You dont appear to have evdev setup;
>>      -> Device Drivers
>>          -> Input device support
>>             -> Generic input layer (needed for keyboard, mouse, ...)
>> 
>> and emerge xf86-input-evdev
>
>  ?!?! I've never had evdev installed.  Why now?  Mouse and keyboard
>work OK.

Evdev helps with swapping mice and keyboards. IOW, when using laptops.

And I think it's the 'preferred' way of doing things these days?

Then again, if you're not having problems with mice and keyboards, I don't see how evdev will 'solve' a non existent problem.

--
Joost
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.


  parent reply	other threads:[~2016-09-10  8:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-09  4:50 [gentoo-user] New install, a few problems (or not?) waltdnes
2016-09-09 15:17 ` Daniel Frey
2016-09-09 15:25   ` Daniel Frey
2016-09-10  5:45     ` J. Roeleveld
2016-09-10  1:20   ` waltdnes
2016-09-10  2:18     ` Adam Carter
2016-09-10  7:11       ` waltdnes
2016-09-10  8:03         ` Adam Carter
2016-09-10  8:06         ` J. Roeleveld [this message]
2016-09-12  2:49 ` [gentoo-user] [SOLVED] " waltdnes

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=493EC760-09F7-4F81-B348-B3E7C5AF190F@antarean.org \
    --to=joost@antarean.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