Filewatcher File Search File Search
Content Search
» » » » » libnjb5_2.2.7~dfsg0-3_ia64.deb » Content »
pkg://libnjb5_2.2.7~dfsg0-3_ia64.deb:130878/usr/share/doc/libnjb5/  info  control  downloads

libnjb5 - Creative Labs Nomad Jukebox library…  more info»


Frequently Asked Questions

1. Is there a mailing list for users of libnjb?

   Yes.  See:

2. When I run the sample programs, I get "No NJB devices found", or a
   silent failure (i.e., nothing happens and you get a prompt back)

   If you are on Linux, you need to mount the usbdevfs filesystem,
   and ensure that you have read/write permission to the "files"
   there.  For more information, see

   You should also verify that you have the latest libusb sources
   from SourceForge (you may need to grab them via CVS) if you 
   have libusb v0.1.3b or earlier.

   Under BSD, make sure you have read/write access to the ugen*
   and usb* devices in /dev.  ugen support will need to be built in your
   kernel (not required for BSD 5.x and higher, which builds devices
   on the fly)

3. Every other connection attempt fails with an I/O error.

   When the NJB is "released" by the host software, there is a
   brief cycle time (a few seconds or so) during which you cannot
   reattach to the device.  If you retry the command a few 
   seconds later, it may work.

   Under Linux, there appears to be a problem with the communications
   between libnjb, libusb and the USB stack.  This causes "every other
   connection fails" problems on some systems, and has not been
   root-caused.  Unplugging/replugging the device (physically!) appears 
   to get things working again, and sometimes simply retrying the 
   command works, as well.

4. I am getting bulk data transfer failures under Linux.

   This is also a known issue that appears to be an interaction between
   libnjb and libusb.  Although it has not been root-caused, the current
   suspicion is that libnjb is writing too aggressively to the USB
   stack, and usb_bulk_write may be failing on EINPROGESS.  Again, this
   is just a guess based on some scattered evidence.  There is no solution
   other than to retry. Using more recent kernels and libusb 
   implementations may solve the problem.

5. I am getting shared object/shared library errors (something like 
   " cannot open shared object file").

   See the README file under the "Shared Library Support" section.

6. How do I get USB 2.0 working?

   First assure yourself that your hardware is really USB 2.0
   compatible. This goes for both the motherboard, hub, and the
   device you want to connect.

   Kernel 2.6.x (and newer versions of 2.4.x) have three USB driver
   modules: UHCI, OHCI and EHCI. USB 2.0 use the EHCI driver, leave
   out the others and recompile your kernel. Typical config status:

   # USB support
   # CONFIG_USB_DEBUG is not set
   # Miscellaneous USB options
   # USB Host Controller Drivers
   # CONFIG_USB_UHCI_HCD is not set

   See also:
Results 1 - 1 of 1
Help - FTP Sites List - Software Dir.
Search over 15 billion files
© 1997-2017