Re: udev-> libusb issue, already posted to libusb group

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



gentlemen, thank you both, all is working perfectly now.

thx also for pointing out the /lib/udev/rules.d/*, i had only been looking in /etc/udev/rules.d for details.

new fishing technique Greatly appreciated, jackc...


Alan Stern wrote:
On Fri, 26 Jun 2009, Greg KH wrote:

And again, what exactly is this device node, or link?  What does:
	ls -l /dev/obdii
show?
crw-rw-rw- 1 root root 251, 29 2009-06-26 07:02 /dev/obdii

and the node that libusb is using ...
251:29?  What is major 251?  What does /proc/devices/ show?

crw-rw-r-- 1 root root 189, 257 2009-06-26 07:02 /dev/bus/usb/003/002
Yup, that's the device you need to be modifying.

and lsusb's view of the world, ...

Bus 001 Device 004: ID 058f:6335 Alcor Micro Corp. SD/MMC Card Reader
Bus 001 Device 003: ID 13fe:1f00 Kingston Technology Company Inc. DataTraveler 2.0 4GB Flash Drive
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 0b05:b700 ASUSTek Computer, Inc.
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 1808:5555 Multiplex Engineering OBDII to USB Interface
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 046d:c526 Logitech, Inc.
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

the rule i am trying to make work, ...

BUS=="usb", ATTRS{idVendor}=="1808", ATTRS{idProduct}=="5555", NAME="obdii", MODE="0666"

note i removed the SYMLINK bit as that was a shot in the dark on my part thinking well,
maybe if i added the SYMLINK, it would link /dev/obdii to /dev/bus/usb/003/002, but that didnt work.

It sounds like Jack is looking for the proper udev rule to force /dev/bus/usb/003/002 to be created with 0666 permissions. It's not clear whether he wants /dev/obdii to be a separate device node, to be a symlink to the original node, or not to exist at all.

Based on the existing libusb rule in /lib/udev/rules.d/50-udev-default.rules, it looks like this should do the trick:

SUBSYSTEM=="usb", ACTION=="add", ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="1808", ATTRS{idProduct}=="5555", MODE="0666"

(all on one line, of course).  And it should be in a file within
/etc/udev/rules.d numbered higher than 50, so that it applies _after_
the default rule.

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
_________________________________
This email has been ClamScanned !
     www.LinuxLightHouse.com

--
   jack craig
      jackc@xxxxxxxxxxxxxxxxxxx
         831-684-1375 (Office)
            831-596-6924 (cell)
               IM: jackcraigaptos (AIM)
_________________________________
This email has been ClamScanned !
    www.LinuxLightHouse.com
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux