Using an Adesso Barcode Scanner With Ubuntu

We’re gearing up to test out a new ticketing system at work. We’ll be scanning barcoded tickets using an inexpensive USB Adesso Barcode Scanner. Unfortunately, on my Ubuntu (9.04 jaunty) netbook, the scanner would disable itself immediately after I scanned a barcode. Here’s how I fixed it:

1) Add the following lines to the bottom of your /etc/modprobe.d/blacklist file:

# these drivers are very simple, the HID drivers are usually preferred
#blacklist usbmouse
#blacklist usbkbd
blacklist usbhid

2) Add the following line to the bottom of your /etc/modules file:


3) Reboot.

This will make your system prefer the usbkbd driver over the HID one. Apparently the scanner likes the older usbkbd driver better.

4 thoughts on “Using an Adesso Barcode Scanner With Ubuntu

  1. Hallo… i’m ewyn from indonesia.. sorry for my bad english :)
    your posting very usefull for me.. coz my USB Barcode scanner (maxima) won’t working properly on my ubuntu desktop 9.04 until i’m follow your easy step.

    now my barcode reader has working but now my mouse can’t working properly. mo mouse can move right and left only. any suggestion ?

    Thank you before… keep writing..

    • Yeah, it affects the input devices when you tinker with those settings. You may have to revert the settings to get your mouse working properly again. You can probably set in exceptions for different devices, but I’m not sure how to do that. The idea would be to run only the barcode scanner off of USBKD and everything else off of HID. Sorry I couldn’t be of more help!

  2. What are the vendor/product ID’s? See the output with lsusb -v command.
    I’ve had similar problems with the Acan FG-8100 barcode reader (Vendor ID: 0x04b4, device ID: 0xbca1). It has the vendor ID of cypress and requires the same MIN/MAX swap descriptor quirk as other barcode readers from cypress.
    That info has been passed to the usbhid kernel maintainer and a patch is currently in the linux kernel patchqueue. Once it’s in the kernel, the scanner is supported out-of-the-box. Your scanner can be possibly added easily if the problem is similar.

  3. Hi,

    It seems that I have the same problem here. I’m not exactly sure, though, as I get this in my kernel messages whenever I plug my scanner:
    generic-usb: probe of 0003:04B4:BCA1.000C failed with error -22

    Anyway, I’d like to give a go to this “MIN / MAX swap descriptor quirk,” but can’t find any reference to it anywhere in the Linux kernel bugtracker. Where has it been queued?

Comments are closed.