I am really no USB expert but I guess that after "rmmod usblp"
even the "io/hpmud/musb.c 594: invalid usb_open: Permission denied"
error messages do no longer happen?
It might happen that an automated "modprobe usblp"
is done every time when the device is connected
to the USB via whatever udev magic - search all
udev rules files in /etc/udev/rules.d/ and
/lib/udev/rules.d/ and /dev/.udev/rules.d/
see "man udev":
----------------------------------------------------------
The udev rules are read from the files located
in the default rules directory /lib/udev/rules.d/,
the custom rules directory /etc/udev/rules.d/
and the temporary rules directory
/dev/.udev/rules.d/
----------------------------------------------------------
When "rmmod usblp" helps, it looks like a new effect /bugzilla. novell. com/show_ bug.cgi? id=184825
of the old usblp <-> usbfs/libusb kernel driver conflict, see
https:/
I am really no USB expert but I guess that after "rmmod usblp"
even the "io/hpmud/musb.c 594: invalid usb_open: Permission denied"
error messages do no longer happen?
It might happen that an automated "modprobe usblp" ------- ------- ------- ------- ------- ------- ------- -- ------- ------- ------- ------- ------- ------- ------- --
is done every time when the device is connected
to the USB via whatever udev magic - search all
udev rules files in /etc/udev/rules.d/ and
/lib/udev/rules.d/ and /dev/.udev/rules.d/
see "man udev":
-------
The udev rules are read from the files located
in the default rules directory /lib/udev/rules.d/,
the custom rules directory /etc/udev/rules.d/
and the temporary rules directory
/dev/.udev/rules.d/
-------