I must have clicked Reply instead of Reply All accidentally, sorry.
I did not notice the obvious error in my first post where I kept mentioning
/proc/bus/usb when in fact the JNI tracing error was mentioning /dev/bus/usb
until your last post.
I have also managed to get things working by making a "usbusers" group and
then added group definition to the rules for creating usb devices:
b...@kronos:~$ grep usbusers /etc/group
usbusers:x:501:ben
b...@kronos:~$ grep usb /etc/udev/rules.d/40-basic-permissions.rules
# USB devices (usbfs replacement)
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", MODE="0664", GROUP="usbusers"
SUBSYSTEM=="usb_device", MODE="0664", GROUP="usbusers"
Thanks again for the help.
Ben.
On Sat, Dec 13, 2008 at 7:40 AM, Dan Streetman <[email protected]> wrote:
> Do not reply only to me. Please keep the discussion on the list.
>
> You don't need anything in /proc/bus/usb anymore. The device nodes
> are now at /dev/bus/usb for recent distributions.
>
> On Fri, Dec 12, 2008 at 3:49 PM, Ben Hall <[email protected]> wrote:
> > Hi Dan, thanks for the quick reply.
> >
> > Without usbfs mounted, the contents of my /proc/bus/usb directory are
> empty,
> > even though I have udev mounted.
> >
> > b...@kronos:~$ mount | grep udev
> > udev on /dev type tmpfs (rw,mode=0755)
> > b...@kronos:~$ ls -l /proc/bus/usb
> > total 0
> >
> > I checked the /etc/udev rules folder and according to the
> > 40-basic-permissions.rules file:
> >
> > # USB devices (usbfs replacement)
> > SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", MODE="0664"
> > SUBSYSTEM=="usb_device", MODE="0664"
> >
> > Then I checked the 40-permissions.rules file:
> >
> > SUBSYSTEMS=="usb", GROUP="plugdev"
> >
> > I then checked to make sure I was a member of group plugdev so 664
> > permission would give me group rw access:
> >
> > b...@kronos:/etc/udev/rules.d$ grep plugdev /etc/group
> > plugdev:x:46:ben
> >
> > It all looks good but the original error is still there and /proc/bus/usb
> is
> > empty.
> >
> > If I run lsusb I can see my devices listed.
> >
> > Thanks,
> > Ben.
> >
> > On Sat, Dec 13, 2008 at 3:07 AM, Dan Streetman <[email protected]>
> wrote:
> >>
> >> you don't need usbfs mounted anymore - udev now creates the nodes at
> >> /dev/bus/usb. Change the permissions of those nodes instead of
> >> mounting usbfs. You can create a simple udev rule, or manually chmod
> >> the node(s) you are accessing (the udev rule with work over
> >> hotplugs/reboots while a simple chmod is temporary).
> >>
> >> On Fri, Dec 12, 2008 at 9:00 AM, Ben Hall <[email protected]> wrote:
> >> > I am having some issues accessing devices using
> >> > javax-usb-ri-linux-1.0.2. I
> >> > believe I have set it up correctly as I do not have any errors when
> >> > running
> >> > the example applications.
> >> >
> >> > I was not able to see any devices with the Show Topology example,
> except
> >> > for
> >> > the virtual hub so I turned on the JNI tracing which revealed this:
> >> >
> >> > [hotplug](3) JavaxUsbTopologyUpdater.c.build_device[117] Building
> device
> >> > /dev/bus/usb/001/001
> >> > [default](1) JavaxUsbTopologyUpdater.c.build_device[121] Could not
> >> > access
> >> > /dev/bus/usb/001/001
> >> > [hotplug](3) JavaxUsbTopologyUpdater.c.build_device[117] Building
> device
> >> > /dev/bus/usb/002/001
> >> > [default](1) JavaxUsbTopologyUpdater.c.build_device[121] Could not
> >> > access
> >> > /dev/bus/usb/002/001
> >> >
> >> > The lines go on to list the other device combinations but the error
> >> > messages
> >> > are essentially the same.
> >> >
> >> > I believe the USB access should be correct, but the error message
> >> > indicates
> >> > otherwise.
> >> >
> >> > Here is how I have mounted the usbfs (insecurely, but it should do the
> >> > trick):
> >> >
> >> > b...@kronos:~$ mount | grep usbfs
> >> > usbfs on /proc/bus/usb type usbfs (rw,devmode=0666)
> >> > b...@kronos:~$ ls -l /proc/bus/usb/007/003
> >> > -rw-rw-rw- 1 root root 77 2008-12-12 10:33 /proc/bus/usb/007/003
> >> > b...@kronos:~$ uname -a
> >> > Linux kronos 2.6.27-9-generic #1 SMP Thu Nov 20 22:15:32 UTC 2008
> x86_64
> >> > GNU/Linux
> >> >
> >> > I suspect it is something trivial I have forgotten to do but I can not
> >> > seem
> >> > to spot it at this stage.
> >> >
> >> > Has anyone seen this issue before and if you have, any hints on how I
> >> > can
> >> > fix it?
> >> >
> >> > Cheers,
> >> > Ben.
> >> >
> >> >
> >> >
> ------------------------------------------------------------------------------
> >> > SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas,
> >> > Nevada.
> >> > The future of the web can't happen without you. Join us at MIX09 to
> >> > help
> >> > pave the way to the Next Web now. Learn more and register at
> >> >
> >> >
> http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
> >> > _______________________________________________
> >> > javax-usb-devel mailing list
> >> > [email protected]
> >> > https://lists.sourceforge.net/lists/listinfo/javax-usb-devel
> >> >
> >> >
> >
> >
>
------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
javax-usb-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/javax-usb-devel
