On Tue 21 Jul 16:59 2009 eial@xxxxxxxxxxxx wrote:
>
> On Tue 21 Jul 16:43 2009 Matthias Schwarzott wrote:
> > On Dienstag, 21. Juli 2009, eial@xxxxxxxxxxxx wrote:
> > > On Tue 21 Jul 16:17 2009 Matthias Schwarzott wrote:
> > > > On Dienstag, 21. Juli 2009, eial@xxxxxxxxxxxx wrote:
> > > > > hello.
> > > > > I'm running gentoo with kernel tuxonice 2.6.29, hal 0.5.12_rc1, dbus
> > > > > 1.2.12, xorg-server 1.6.2 and udev 140. I have these following three
> > > > > rules: ACTION=="add", SUBSYSTEM=="input", ENV{ID_CLASS}=="mouse",
> > > > > RUN+="/usr/bin/synclient TouchpadOff=1"
> > > > > ACTION=="remove",
> > > > > SUBSYSTEM=="input", ENV{ID_CLASS}=="mouse", RUN+="/usr/bin/synclient
> > > > > TouchpadOff=0" SUBSYSTEM=="bluetooth", KERNEL=="hci[0-9]*",
> > > > > RUN+="bluetooth.sh"
> > > >
> > > > What is the name of the file these rules are in?
> > > > It must be lexically after the file setting ID_CLASS.
> > > > For remove event it is possible not all properties can be checked, but
> > > > you may use REMOVE_CMD for it.
> > > > REMOVE_CMD is set in ACTION=="add" to the value you want to pass to RUN
> > > > in remove case.
> > > >
> > > > If that does not help, please run "udevadmin monitor --udev --env" while
> > > > plugging the mouse in and post the results.
> > > >
> > > > Regards
> > > > Matthias
> > > > --
> > > > To unsubscribe from this list: send the line "unsubscribe linux-hotplug"
> > > > in the body of a message to majordomo@xxxxxxxxxxxxxxx
> > > > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > >
> > > for some reason I can't seem to find the bluetooth file, I'll focus on the
> > > mouse, the file is /etc/udev/rules.d/01-touchpad.rules lexically?
> >
>
> ok, 01 is before 60 so I need to call it 61-touchpad.rules?
>
> > The rule files are sorted in alphabetic order.
> > So the file where ID_CLASS is set must be before your own file, and it is set
> > in 60-persistent-input.rules
> > So when your rules are executed ID_CLASS simply is not yet set and they can
> > never match.
> >
> > Why do you write your own bluetooth rules? net-wireless/bluez already provides
> > the rule you quoted above.
> >
>
> well, that script was there in my distribution, what I want to do is the following, when I run on the bt+wireless adapter on, udev will load the bt and wl modules and run the kbluetooth program, and when I turn in off, it will kill the program and remove them from the memory
>
> > > not sure I've understood the REMOVE_CMD
>
> thanks for the tip.
>
> > If you have a rule to match on remove and the properties you want to test are
> > not available at that point the rule need to match on add. The match is then
> > stored into udev database to know what to do on remove.
> >
> > ACTION=="add", SUBSYSTEM=="input", ENV{ID_CLASS}=="mouse", \
> > RUN+="/usr/bin/synclient TouchpadOff=1", \
> > ENV{REMOVE_CMD}="/usr/bin/synclient TouchpadOff=0"
> >
>
> will try it,
>
> > >
> > > here is the output:
> > > ul 21 16:27:36 NCC-5001-D usb 6-2: new low speed USB device using uhci_hcd
> > > and address 7 Jul 21 16:27:36 NCC-5001-D usb 6-2: configuration #1 chosen
> > > from 1 choice Jul 21 16:27:36 NCC-5001-D input: USB_PS2 Optical Mouse as
> > at least this is not the output of udevadmin monitor, looks more like dmesg.
> >
> > Regards
> > Matthias
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
> > the body of a message to majordomo@xxxxxxxxxxxxxxx
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
>
>
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
any hints on the issue?
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
