From: Mark Eaton <meaton@vasco.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev - /dev/input/mice problem
Date: Wed, 20 Oct 2004 04:50:41 +0000 [thread overview]
Message-ID: <200410201450.41425.meaton@vasco.com> (raw)
In-Reply-To: <32895.193.231.188.208.1098236930.squirrel@email.rdsor.ro>
I get this sometimes with my wireless mouse at home. It never seems to occur
with my non wireless mice. I have assumed it is something to do with wireless
(or maybe logitech only) mice.
On Wed, 20 Oct 2004 02:32 pm, Kay Sievers wrote:
> On Wed, Oct 20, 2004 at 04:48:50AM +0300, Adrian Dinita wrote:
> > I installed udev-038-1 and after a reboot the computer 'died' trying to
> > get into X. I did a restart in run-level 3 and /var/log/Xorg.0.log said:
> > Cannot open device /dev/input/mice
> > No such file or directory.
> > ......
> > Fatal server error: failed to initialize core devices
> >
> > I added the line Option "AllowMouseOpenFail" "1" (in the ServerFlags
> > section) in xorg.conf.. and X started with no mouse.
> >
> > I entered the directory and /dev/input/ was empty
> >
> > udevd was running
> >
> > ps aux | grep udevd:
> > root 250 0.0 0.0 3184 452 ? S<s 04:17 0:00 udevd
> >
> >
> > after a: /sbin/udevstart (/sbin/udev) , (or a : MAKEDEV mouse) it created
> > the entries and the mouse start working.
> >
> > Why doesn't udev create the entries for the mouse at startup?
> >
> > My distro is Fedora Core 2 , xorg 6.8.1 , kernel: 2.6.8-1.624
>
> No idea. Everything is working well here with the same setup.
>
> Do you have that problem with every reboot?
>
> Do you have a USB-mouse? If yes, you may try diconnect/reconnect it and
> look in /dev if the nodes are deleted/created.
>
> Kay
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
> Linux-hotplug-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
--
Mark Eaton
Senior Software Engineer
VASCO The Authentication Company
+67 3511 5404
+67 (0) 403 384 886
meaton@vasco.com
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-10-20 4:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 1:48 udev - /dev/input/mice problem Adrian Dinita
2004-10-20 4:32 ` Kay Sievers
2004-10-20 4:50 ` Mark Eaton [this message]
2004-10-20 13:40 ` Adrian Dinita
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=200410201450.41425.meaton@vasco.com \
--to=meaton@vasco.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).