The wikis are now using the new authentication system.
If you did not migrate your account yet, visit

SDB:USB Scanner Configured with YaST Does Not Work

Şuraya atla: kullan, ara

Version: 8.2


Your USB scanner has been detected in YaST2's configuration dialog and the driver has been installed. However, conducting a test scan is not possible and the scanner cannot be addressed after the installation.


In the case of USB scanners based on Sane's gt68xx backend, not only the driver but also the scanner's firmware is required.
This particularly affects USB scanners from the manufacturers Medion and Mustek, as well as single scanners from other manufacturers. A detailed list can be found at the gt68xx homepage.


First, you have to obtain the device's firmware.

The firmware of Mustek and Packard Bell scanners is available at the gt68xx homepage.
If you have a different scanner supported by gt68xx, you can try to extract the firmware from the Windows driver CD. In case the firmware is not directly available on the CD, you have to install the driver in Windows first.
The firmware should be located at c:\\windows\system32\drivers\.

Copy the firmware to the directory /usr/share/sane/gt68xx/. If the directory does not exist yet, create it by entering the following in a text console as root user:

	mkdir /usr/share/sane/gt68xx/

Then restart the scanner configuration dialog in YaST2 Control Center. Conducting a test scan should now be possible and the scanner should be available on your system.


If the scanner still does not work after following the instructions above, try to configure the scanner manually.
To do so, open a text console and enter the following command:


If the scanner is found, the output should be similar to:

	found USB scanner (vendor=0x055f, product=0x021e) at /dev/usb/scanner0
	found USB scanner (vendor=0x055f, product=0x021e) at /dev/usbscanner
	found USB scanner (vendor=0x046d, product=0x0870) at libusb:001:002
	found USB scanner (vendor=0x055f, product=0x021e) at libusb:002:002

Enter the following command to identify the scanner:

	scanimage -L

If the scanner has been properly detected, the output should be similar to:

	device `gt68xx:/dev/usb/scanner0' is a Mustek BearPaw 1200 TA flatbed scanner
	device `gt68xx:/dev/usbscanner' is a Mustek BearPaw 1200 TA flatbed scanner

Now try to start the graphical frontend with:


If there are still problems with the scanner's availability, the backend will display an error message accordingly, for example:

	[gt68xx] sane_open: power control failure: check power plug!

Certain scanners may be wrongly detected. If this is the case, an additional option must be activated in the file:


For the following scanner types:

        Mustek Scanexpress 1200 UB Plus
        Medion/Lifetec/Tevion LT 9452
        Trust Compact Scan USB 19200

the option reads:

        override  mustek-scanexpress-1200-ub-plus

For the following scanner types:

        Artec Ultima 2000
        Boeder SmartScan Slim Edition
        Medion/ Lifetec/ Tevion/ Cytron MD/LT 9385
        Medion/ Lifetec/ Tevion MD 9458
        Trust  Flat  Scan  USB  19200

the option reads:

        override artec-ultima-2000

and for the scanner:

        Mustek BearPaw 2400 CU

the option reads:

        override mustek-bearpaw-2400-cu

The override options are already included (disabled) in the file gt68xx.conf. To activate these options, simple remove the lozenge at the beginning of the override line and save the file. <keyword>scanner,USB,Mustek,gt68xx</keyword>