All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Aymeric O." <ejisneos@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: 2 kernels, 2 different mice locations
Date: Wed, 17 Feb 2010 18:35:41 +0000	[thread overview]
Message-ID: <4B7C36FD.2010109@mailoo.org> (raw)
In-Reply-To: <4B7BC06B.50004@mailoo.org>

[-- Attachment #1: Type: text/plain, Size: 995 bytes --]

That did the trick!
I will be able to provide a new stable RT kernel, now.

Thank you very much!


(2010年02月17日 14:57), Kay Sievers wrote:
> 2010/2/17 Aymeric O. <ejisneos@gmail.com>:
>   
>> I'm using 2 kernels on my distribution. The "official" one is 2.6.32,
>> and I'm providing a 2.6.29.6-rt24 for those who want to use RealTime.
>> But since we upgraded udev to the latest version, some of /dev files are
>> placed at different locations depending on which kernel is used.
>>
>> With 2.6.32, everything works fine, but now, when I boot with
>> 2.6.29.6-rt24, I cannot move my mouse unless I symlink /dev/mice to
>> /dev/input/mice. And it doesn't completely work, because I'm unable to
>> scroll.
>>     
> New udev versions and old kernels need some old udev rules to name
> device nodes. You should be able to use the Gentoo rules, which seem
> to support this:
>   http://git.kernel.org/?p=linux/hotplug/udev.git;a=blob;f=rules/gentoo/30-kernel-compat.rules;hb=HEAD
>
> Kay
>   


[-- Attachment #2: 0xEF3AF04D.asc --]
[-- Type: application/pgp-keys, Size: 2116 bytes --]

  parent reply	other threads:[~2010-02-17 18:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-17 10:09 2 kernels, 2 different mice locations Aymeric O.
2010-02-17 13:57 ` Kay Sievers
2010-02-17 18:35 ` Aymeric O. [this message]
2010-02-17 21:40 ` Aymeric O.
2010-02-17 21:57 ` Kay Sievers
2010-02-17 22:19 ` Aymeric O.

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=4B7C36FD.2010109@mailoo.org \
    --to=ejisneos@gmail.com \
    --cc=linux-hotplug@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.