gnomad2 permissions[SOLVED] again

rayjgu3 · 2006-01-25 03:13:36

after beating my head for bout two weeks reading everything bout this im tired of pulling my hair out so im gonna ask the question
what do i have to do to get a user to be able to use this it used to work great no problems
take away hotplug update udev i no longer can run gnomad2 as a user only root
ive read all i found hear on people with usb permission probs trying diffrent udev rules to no avail even looked at other forums please help
error i get is

Could Not open Jukebox"
usb_set_configuration: Operation not permitted

lsusb
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 002: ID 03eb:3301 Atmel Corp. 4-port Hub
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 012: ID 041e:4110 Creative Technology, Ltd Nomad Jukebox Zen Xtra MP3 player
Bus 001 Device 001: ID 0000:0000

dmesg | tail
sr 2:0:0:0: phase change 2-3 12@36b89f60 resid=2.
sr 2:0:0:0: phase change 2-3 12@37424b60 resid=2.
sr 2:0:0:0: phase change 2-3 12@37424b60 resid=2.
usb 1-1: USB disconnect, address 13
sr 2:0:0:0: phase change 2-3 12@37424b60 resid=2.
sr 2:0:0:0: phase change 2-3 12@36b89f60 resid=2.
sr 2:0:0:0: phase change 2-3 12@36b89f60 resid=2.
usb 1-1: new high speed USB device using ehci_hcd and address 14
sr 2:0:0:0: phase change 2-3 12@37424b60 resid=2.
sr 2:0:0:0: phase change 2-3 12@37424b60 resid=2.

if more info is needed just say so
thanks

Last edited by rayjgu3 (2008-04-29 21:31:09)

rayjgu3 · 2006-01-26 22:26:31

ok so still looking i found this
http://www.reactivated.net/writing_udev_rules.html#tips

which i found this

udevinfo -a -p /sys/devices/pci0000:00/0000:00:10.4/usb1/1-1

udevinfo starts with the device the node belongs to and then walks up the
device chain, to print for every device found, all possibly useful attributes
in the udev key format.
Only attributes within one device section may be used together in one rule,
to match the device for which the node will be created.

  looking at class device '/sys/devices/pci0000:00/0000:00:10.4/usb1/1-1':
    KERNEL=="1-1"
    SUBSYSTEM=="unknown"
    SYSFS{bConfigurationValue}=="1"
    SYSFS{bDeviceClass}=="ff"
    SYSFS{bDeviceProtocol}=="ff"
    SYSFS{bDeviceSubClass}=="ff"
    SYSFS{bMaxPacketSize0}=="64"
    SYSFS{bMaxPower}=="  0mA"
    SYSFS{bNumConfigurations}=="1"
    SYSFS{bNumInterfaces}==" 1"
    SYSFS{bcdDevice}=="0001"
    SYSFS{bmAttributes}=="c0"
    SYSFS{configuration}=="Media"
    SYSFS{devnum}=="4"
    SYSFS{idProduct}=="4110"
    SYSFS{idVendor}=="041e"
    SYSFS{manufacturer}=="Creative Technology"
    SYSFS{maxchild}=="0"
    SYSFS{product}=="NOMAD Jukebox Zen Xtra"
    SYSFS{serial}=="01022551D8039098"
    SYSFS{speed}=="480"
    SYSFS{version}==" 2.00"

im hoping somebody here that understands this can either
A. give me a hint
B. tell me im wasting my time cause of what it says on writing udev rules page

* Remember that unfortunately, the kernel does not export information for all devices into sysfs, meaning that you simply can't write rules for some devices yet. On 20/02/04, the udev author stated that there are 162 drivers left to convert to sysfs.

C. tell me the answer
ill settle for A i doubt its B. cause i can run it as root
although im udev illiterate i do wanting to learn
thanks

Snowman · 2006-01-27 01:41:34

Here's what I suggest. It might not be relevant but it's all I can think of. When you plug in your mp3 player, I assume that udev creates the correct device in /dev but that it has root:root ownership so regular users don't have access. Try to find out the name of the device that udev creates. You could do that by doing a 'ls -R /dev' before and after plugging in the mp3 player. Once you know the name of the device, you could put it in a group (using a regular udev rule) and add your user to that group like it is done for the audio stuff.
HTH.

rayjgu3 · 2006-01-28 12:59:58

ty Snowman

ok i think im getting some where
after changeing my google searches i found this
https://bugzilla.redhat.com/bugzilla/sh … ?id=178543
the /dev thats added is usbdev1.X where X marks the times its been pluged in (usbdev1.1 is 1st plugin 1.2 is unplug replug)
usbdev1.X = /proc/bus/usb/001/00X
if i as root

chown USER:disk /proc/bus/usb/001/00X

i can then use gnomad2 as a user
ive tried all the rules at said link to no avail
i understand i need udev to change the permissions of /proc/bus/usb/001/00X but am unable to figure it out so far
any udev geniuses out there can help please

thanks

rayjgu3 · 2006-01-29 15:34:54

holy crap i figured it out with help
found this here
http://lists.debian.org/debian-devel/20 … 00424.html
just had to change a few things

/etc/udev/rules.d/00.rules

BUS=="usb", SYSFS{idVendor}=="041e", SYSFS{idProduct}=="4110", 
    SYMLINK+="njb%n", GROUP="audio"


ACTION=="add", BUS=="usb", SYSFS{idVendor}=="041e", SYSFS{idProduct}=="4110", 
    RUN+="/etc/hotplug/usb/nomadjukebox"

SUBSYSTEM=="usb_device", SYSFS{idVendor}=="041e", SYSFS{idProduct}=="4110", 
    GROUP="audio"

jfca283 · 2008-04-18 19:56:21

i don't want to create another post
the solution is here, but after upgrading my kernel and gnomad2 through PKGBUILD, i lost the ability to access my creative
the file,
/etc/udev/rules.d/00.rules
doesn't appear on my system
should i create one?
this files are on
/etc/udev/rules.d/
05-udev-early.rules 61-persistent-storage-edd.rules
40-pilot-links.rules 64-device-mapper.rules
45-libnjb.rules 64-md-raid.rules
50-udev-default.rules 75-cd-aliases-generator.rules.optional
50-udev-default.rules~ 75-persistent-net-generator.rules.optional
51-arch.rules 80-drivers.rules
54-gphoto.rules 90-hal.rules
60-cdrom_id.rules 90-libgphoto2.rules
60-pcmcia.rules 95-udev-late.rules
60-persistent-input.rules 99-fuse.rules
60-persistent-storage.rules device-mapper.rules
60-persistent-storage-tape.rules udev.rules.pacsave

rayjgu3 · 2008-04-19 01:30:34

ok i just dusted off this player & mine aint connecting right now either
you dont need another rule the rule for your creative player is in 45-libnjb.rules
ive tried tweaking mine to no avail, YET
it may be the kernel as you pointed out
ill try playing with it some more get back to you later
if you find the fix please post it

rayjgu3 · 2008-04-29 21:30:22

as root

cd /etc/udev/rules.d/
mv udev.rules.pacsave udev.rules
killall udevd
/etc/start_udev

taken from this thread
http://bbs.archlinux.org/viewtopic.php?id=47290

jfca283 · 2008-04-29 23:46:49

i did what you said and i edited my 45.libnlb rules, changing storage for audio and 666 group
now it's working
thanks

Arch Linux

#1 2006-01-25 03:13:36

gnomad2 permissions[SOLVED] again

#2 2006-01-26 22:26:31

Re: gnomad2 permissions[SOLVED] again

#3 2006-01-27 01:41:34

Re: gnomad2 permissions[SOLVED] again

#4 2006-01-28 12:59:58

Re: gnomad2 permissions[SOLVED] again

#5 2006-01-29 15:34:54

Re: gnomad2 permissions[SOLVED] again

#6 2008-04-18 19:56:21

Re: gnomad2 permissions[SOLVED] again

#7 2008-04-19 01:30:34

Re: gnomad2 permissions[SOLVED] again

#8 2008-04-29 21:30:22

Re: gnomad2 permissions[SOLVED] again

#9 2008-04-29 23:46:49

Re: gnomad2 permissions[SOLVED] again

Board footer