Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
root@deedee mirrorball # sane-find-scanner
# No SCSI scanners found. If you expected something different, make sure that
# you have loaded a SCSI driver for your SCSI adapter.
found USB scanner (vendor=0x0458, product=0x2004) at /dev/usb/scanner0
# Your USB scanner was detected. It may or may not be supported by
# SANE. Try scanimage -L and read the backend's manpage.
# Scanners connected to the parallel port or other proprietary ports can't be
# detected by this program.
Code:
root@deedee mirrorball # scanimage -L
No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).
Code:
root@deedee mirrorball # cat /etc/sane.d/plustek.conf
# Plustek-SANE Backend configuration file
# For use with Plustek parallel-port scanners and
# LM9831/2/3 based USB scanners
#
# For parport devices use the parport section
#
[parport]
device /dev/pt_drv
#
# leave the default values as specified in /etc/modules.conf
#
option warmup -1
option lOffOnEnd -1
option lampOff -1
#
# The USB section:
# each device needs at least two lines:
# - [usb] vendor-ID and product-ID
# - device devicename
# i.e. for Plustek (0x07B3) UT12/16/24 (0x0017)
# [usb] 0x07B3 0x0017
# device /dev/usbscanner
# or
# device libusb:bbb:ddd
# where bbb is the busnumber and ddd the device number
# make sure that your user has access to /proc/bus/usb/bbb/ddd
#
# additionally you can specify some options
# warmup, lOffOnEnd, lampOff
#
# For autodetection use
# [usb]
# device /dev/usbscanner
#
# or simply
# [usb]
#
# or if you want a specific device but you have no idea about
# the device node or you use libusb, simply set vendor- and product-ID
# [usb] 0x07B3 0x0017
# device auto
#
# NOTE: autodetection is safe, as it uses the info it got
# from the USB subsystem. If you're not using the
# autodetection, you MUST have attached that device
# at your USB-port, that you have specified...
#
[usb] 0x458 0x2004
#
# options for the previous USB entry
#
# switch lamp off after xxx secs, 0 disables the feature
option lampOff 300
# warmup period in seconds, 0 means no warmup
option warmup 15
# 0 means leave lamp-status untouched, not 0 means switch off
# on sane_close
option lOffOnEnd 1
#
# options to tweak the image start-position
# (WARNING: there's no internal range check!!!)
#
# for the normal scan area
#
option posOffX 0
option posOffY 0
# for transparencies
option tpaOffX 0
option tpaOffY 0
# for negatives
option negOffX 0
option negOffY 0
#
# for setting the calibration strip position
# (WARNING: there's no internal range check!!!)
# -1 means use built in
#
option posShadingY -1
option tpaShadingY -1
option negShadingY -1
#
# to invert the negatives, 0 disables the feature
#
option invertNegatives 0
# for skipping whole calibration step
option skipCalibration 0
# for skipping entire fine calibration step
# coarse calibration is done
option skipFine 0
# discard the result of the fine white calibration
option skipFineWhite 0
# for replacing the gain values found during
# calibration
option red_gain -1
option green_gain -1
option blue_gain -1
#
# for adjusting the default gamma values
#
option redGamma 1.0
option greenGamma 1.0
option blueGamma 1.0
option grayGamma 1.0
#
# to enable TPA (non Plustek devices only)
# 0 means default behaviour as specified in the internal tables
# 1 means enable
#
option enableTPA 0
#
# and of course the device-name
#
# device /dev/usbscanner
device /dev/usb/scanner0
#
# to define a new device, start with a new section:
# [usb] or [parport]
#
Does anyone know what's wrong? Maybe my scanner isn't really supported by sane.
I'm running Gentoo Linux.
You need to comment out the parport section (put a # at the start of each line like in the usb section) of your plustek.conf, and complete the usb section according to the instructions in it.
It still doesn't work. I changed plustek.conf, please tell me if I did it right.
Code:
root@deedee mirrorball # cat /etc/sane.d/plustek.conf
# Plustek-SANE Backend configuration file
# For use with Plustek parallel-port scanners and
# LM9831/2/3 based USB scanners
#
# For parport devices use the parport section
#
#[parport]
#device /dev/pt_drv
#
# leave the default values as specified in /etc/modules.conf
#
#option warmup -1
#option lOffOnEnd -1
#option lampOff -1
#
# The USB section:
# each device needs at least two lines:
# - [usb] vendor-ID and product-ID
# - device devicename
# i.e. for Plustek (0x07B3) UT12/16/24 (0x0017)
# [usb] 0x07B3 0x0017
# device /dev/usbscanner
# or
# device libusb:bbb:ddd
# where bbb is the busnumber and ddd the device number
# make sure that your user has access to /proc/bus/usb/bbb/ddd
#
# additionally you can specify some options
# warmup, lOffOnEnd, lampOff
#
# For autodetection use
# [usb]
# device /dev/usbscanner
#
# or simply
# [usb]
#
# or if you want a specific device but you have no idea about
# the device node or you use libusb, simply set vendor- and product-ID
# [usb] 0x07B3 0x0017
# device auto
#
# NOTE: autodetection is safe, as it uses the info it got
# from the USB subsystem. If you're not using the
# autodetection, you MUST have attached that device
# at your USB-port, that you have specified...
#
[usb] 0x458 0x2004
#
# options for the previous USB entry
#
# switch lamp off after xxx secs, 0 disables the feature
option lampOff 300
# warmup period in seconds, 0 means no warmup
option warmup 15
# 0 means leave lamp-status untouched, not 0 means switch off
# on sane_close
option lOffOnEnd 1
#
# options to tweak the image start-position
# (WARNING: there's no internal range check!!!)
#
# for the normal scan area
#
option posOffX 0
option posOffY 0
# for transparencies
option tpaOffX 0
option tpaOffY 0
# for negatives
option negOffX 0
option negOffY 0
#
# for setting the calibration strip position
# (WARNING: there's no internal range check!!!)
# -1 means use built in
#
option posShadingY -1
option tpaShadingY -1
option negShadingY -1
#
# to invert the negatives, 0 disables the feature
#
option invertNegatives 0
# for skipping whole calibration step
option skipCalibration 0
# for skipping entire fine calibration step
# coarse calibration is done
option skipFine 0
# discard the result of the fine white calibration
option skipFineWhite 0
# for replacing the gain values found during
# calibration
option red_gain -1
option green_gain -1
option blue_gain -1
#
# for adjusting the default gamma values
#
option redGamma 1.0
option greenGamma 1.0
option blueGamma 1.0
option grayGamma 1.0
#
# to enable TPA (non Plustek devices only)
# 0 means default behaviour as specified in the internal tables
# 1 means enable
#
option enableTPA 0
#
# and of course the device-name
#
# device /dev/usbscanner
device /dev/usb/scanner0
#
# to define a new device, start with a new section:
# [usb] or [parport]
#
Ok, now we need to ckeck that you have the correct kernel modules loaded. Have a look at the linux USB-Guide for instructions and check them against your set up.
Right, now check the permissions and ownership on /dev/usb/scanner0.
I use /dev/usbscanner and these are mine,
Code:
bern@aptiva:~$ ls -l /dev/usbscanner
lrwxrwxrwx 1 root saned 16 Dec 29 11:38 /dev/usbscanner -> /dev/usbscanner0
I run my scanner from my network server with saned - any other computers on the network have access to it.
Another potential fix could be with the uhci module - there are two modules for the uhci type of usb controller - uhci and usb-uhci, the "lsmod" command will show you what one is loaded now, try the other and see if that helps.
OK, thank you Aussie. I'm going to contact the plustek developers. I hope I can get this scanner to work on Linux but I don't think it's really supported by sane despite what's written on the Genius website.
I FINALLY GOT IT! I dont believe it took so long considering I cant be called a anymore. Its about the permissions of the file /proc/bus/usb/001/002 or whatever is your scanners device id. If a normal user needs to access the scanner then this file should be writable to that user.
Just chmod the file to 666 and it should work.
With libusb around its useless to change the permissons of /dev/scanner or /dev/usbscanner cos they are not being used anymore.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.