Harald Dunkel [EMAIL PROTECTED] writes:
Juergen Kreileder wrote:
,
| ACTION==add, \
| KERNEL==event*, \
| SUBSYSTEM==input, \
| SYSFS{manufacturer}==Logitech, \
| SYSFS{product}==USB Receiver, \
| NAME=input/mx1000
`
for my MX1000.
This looks very good, but ...
Hi Juergen,
Juergen Kreileder wrote:
You probably gave a non-existant sysfs path to the command (see /sys).
Yes, that was a typo. udevinfo should print some
error message, like no such entry in database.
I did not try your suggested udev config change, though.
I am back to the old mouse
Hi Juergen,
Juergen Kreileder wrote:
,
| ACTION==add, \
| KERNEL==event*, \
| SUBSYSTEM==input, \
| SYSFS{manufacturer}==Logitech, \
| SYSFS{product}==USB Receiver, \
| NAME=input/mx1000
`
for my MX1000.
This looks very good, but ...
You can get the necessary
Harald Dunkel [EMAIL PROTECTED] writes:
On the next reboot you might get /dev/input/event(n+1),
Write an udev rule for the device.
I'm using
,
| ACTION==add, \
| KERNEL==event*, \
| SUBSYSTEM==input, \
| SYSFS{manufacturer}==Logitech, \
| SYSFS{product}==USB Receiver, \
|
Daniel Stone wrote:
On Tue, Jan 24, 2006 at 07:40:09AM +0100, Harald Dunkel wrote:
Sorry, but this is not a dup. #347681 talks about typos
in xorg.conf, i.e. something that can be fixed by somebody
with write permission to this file.
This bug (#347681) is about something that can _not_ be
Package: xserver-xorg
Version: 6.9.0.dfsg.1-4
severity: serious
I don't know how to reproduce it, but sometimes after
the next boot my mouse seems to be connected to
/dev/input/event2 instead of the /dev/input/event1
configured in xorg.conf (or vice versa).
If I start X without fixing xorg.conf,
On Mon, 2006-01-23 at 22:25 +0100, Harald Dunkel wrote:
If I start X without fixing xorg.conf, then my machine
gets stuck completely. All I can do is to press the reset
button.
Dupe of #347681, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=347681
--
To UNSUBSCRIBE, email to [EMAIL
Jeremy Nickurak wrote:
On Mon, 2006-01-23 at 22:25 +0100, Harald Dunkel wrote:
If I start X without fixing xorg.conf, then my machine
gets stuck completely. All I can do is to press the reset
button.
Dupe of #347681, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=347681
Sorry, but
On Tue, Jan 24, 2006 at 07:40:09AM +0100, Harald Dunkel wrote:
Sorry, but this is not a dup. #347681 talks about typos
in xorg.conf, i.e. something that can be fixed by somebody
with write permission to this file.
This bug (#347681) is about something that can _not_ be
fixed by editing
9 matches
Mail list logo