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
Subject: Re: [gentoo-user] Re: xorg-server 1.7.6 without mouse and keyboard  (solved)
Date: Tue, 13 Jul 2010 11:12:28 -0700	[thread overview]
Message-ID: <AANLkTimGEuUIIiMpGY-lobRepu2wx7FwiX4dtRsfLDPS@mail.gmail.com> (raw)
In-Reply-To: <i1i95r$brf$1@dough.gmane.org>

On Tue, Jul 13, 2010 at 10:53 AM, Nikos Chantziaras <realnc@arcor.de> wrote:
> On 07/13/2010 08:14 PM, Mark Knecht wrote:
>>
>> On Tue, Jul 13, 2010 at 10:01 AM, Tamer Higazi<th982a@googlemail.com>
>>  wrote:
>>>
>>> Hi Mark!
>>> you were entirely right, the problem were the input drivers.
>>>
>>> There three packages I remerged:
>>>
>>> xf86-input-mouse
>>> xf86-input-keyboard
>>> xf86-input-evdev
>>>
>>> and the problem was gone.
>>>
>>>
>>> Tamer
>>
>> Glad it worked. Investigate modules-rebuild as it keeps track of these
>> things and does it for you pretty easily. Here's what's in my list:
>>
>> c2stable ~ # module-rebuild list
>> ** Packages which I will emerge are:
>>         =x11-base/xorg-drivers-1.7
>>         =x11-drivers/xf86-input-evdev-2.3.2
>>         =x11-drivers/xf86-video-ati-6.13.0
>>         =x11-drivers/xf86-video-fbdev-0.4.2
>>         =x11-drivers/xf86-input-keyboard-1.4.0
>>         =x11-drivers/xf86-input-mouse-1.5.0
>>         =x11-drivers/xf86-video-vmware-11.0.1
>>         =media-libs/mesa-7.8.1
>
> All of the above are not kernel modules. Kernel updates don't affect them,
> only xorg-server updates do.
>
>
>>         =app-emulation/vmware-modules-1.0.0.26
>
> Only this is affected by kernel updates.
>

No disagreement on that, but frankly it doesn't matter to me. It
works. Takes about 1 minute to rebuild these files. I don't care (as a
user type) why I have to do it. I do it and my machine works. It
covers kernel and xorg updates. That's OK with me.

Or maybe you're just pointing this out to the OP?

I suspect I might have failed with the same problem as the OP myself
this morning had I used not it. There was an xorg-driver update that
didn't update all the input devices in my make.conf file. (evdev
specifically) This command did. Maybe I didn't need to rebuild evdev
after an sorg-driver update but I suspect you'd agree it's safer if I
do.

Sometimes the tools take care of things that are just oversights.
Matters not that I shouldn't have to do it. Matters more that the
machine works.

Cheers,
Mark



  reply	other threads:[~2010-07-13 18:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-13 15:57 [gentoo-user] xorg-server 1.7.6 without mouse and keyboard Tamer Higazi
2010-07-13 16:45 ` Mark Knecht
2010-07-13 17:01   ` [gentoo-user] xorg-server 1.7.6 without mouse and keyboard (solved) Tamer Higazi
2010-07-13 17:14     ` Mark Knecht
2010-07-13 17:53       ` [gentoo-user] " Nikos Chantziaras
2010-07-13 18:12         ` Mark Knecht [this message]
2010-07-13 17:55     ` Nikos Chantziaras
2010-07-13 18:31       ` Dale
2010-07-14  8:45     ` [gentoo-user] " Rod
2010-07-13 16:45 ` [gentoo-user] xorg-server 1.7.6 without mouse and keyboard Willie Wong
2010-07-13 16:57   ` Hung Dang
2010-07-13 16:59 ` Neil Bothwick

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=AANLkTimGEuUIIiMpGY-lobRepu2wx7FwiX4dtRsfLDPS@mail.gmail.com \
    --to=markknecht@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