Here it is:
open("/proc/bus/usb/002/002", O_RDWR) = -1 EACCES (Permission denied)
open("/proc/bus/usb/002/002", O_RDONLY) = 3
ioctl(3, USBDEVFS_CONTROL, 0xfef9e390) = -1 EPERM (Operation not permitted)
dup(2) = 4
fcntl64(4, F_GETFL) = 0x2 (flags O_RDWR)
fstat64(4, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 0), ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0xf6ffb000
_llseek(4, 0, 0xfef9de48, SEEK_CUR) = -1 ESPIPE (Illegal seek)
Indeed, this file is not writeable:
$ ls -l /proc/bus/usb/002/002
-rw-r--r-- 1 root root 52 Nov 28 20:48 /proc/bus/usb/002/002
Can I make it writeable somehow?
Sergey
On Sun, 28 Nov 2004 22:44:55 +0100, Oliver Neukum <[EMAIL PROTECTED]> wrote:
> Am Sonntag, 28. November 2004 20:04 schrieb Sergey Udaltsov:
>
>
> > > Looking at the code it seems like libusb is used.
> > > Which error exactly does it fail? How is usbfs mounted?
> > $ mount | grep usb
> > usbfs on /proc/bus/usb type usbfs (rw)
> > $ lmctl -i
> > 003.003: 046d:c50e Receiver for MX1000 Laser (C-BN34) Caps: CSR SMS
> > Writing to USB device: Operation not permitted
>
> Please use strace to find out the actual failing syscall.
>
> Regards
> Oliver
>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
