Jump to content

Anyone use(d) following scanners with MD9.0?


finlay
 Share

Recommended Posts

I have run sane-find-scanner - nothing. I've run scan --list-devices and got the usual " no scanners were found on your system". I tried deleting the entries in dll.conf and mustek_ub.conf, pulling outthe usb cable, rebooting, and sticking the usb back in once I was back to my desktop. Nothing. harddrake reports the Trust scanner on /dev/usb/scanner0 and invites me to configure it manually. Apart from picking scanners at random from the database, I'm at a loss. :(

Can you tell me please which driver your scanner is using? Also, Steve you mentioned that yours works "but with a little tweaking". Can you tell me what that consisted of?

 

Finlay

Link to comment
Share on other sites

I can try

 

Here is my /etc/sane.d/dll.conf file:

# enable the next line if you want to allow access through the network:

net

mustek_usb

 

/etc/sane.d/mustek_usb.conf:

# mustek_usb.conf: Configuration file for Mustek USB scanner

# Read man sane-mustek_usb for documentation



# If USB errors occur, using this option may help

#option max_block_size 1024



# Autodetect 1200 UB and Trust Compact Scan USB 19200

usb 0x055f 0x0006



# Autodetect 1200 USB (not supported)

# usb 0x055f 0x0003



# Autodetect 1200 CU

usb 0x055f 0x0001



# Autodetect 1200 CU Plus

usb 0x055f 0x0008



# Autodetect 600 CU

usb 0x055f 0x0002



# Autodetect 600 USB (not supported)

usb 0x055f 0x0873



# If autodetection doesn't work uncomment or add your device file and one

# suitable option (1200ub is also for Trust Compact Scan USB 19200).



#/dev/usb/scanner0

option 1200ub

#option 1200cu

#option 1200cu_plus

#option 600cu



#/dev/usbscanner0

#option 1200ub

#option 1200cu

#option 1200cu_plus

#option 600cu

 

(Hmmmmm...I notice this interesting line in there):

1200ub is also for Trust Compact Scan USB 19200

 

And do you have these two files?

/usr/lib/sane/libsane-mustek_usb.so.1

/usr/lib/sane/libsane-mustek_usb.so.1.0.8

Link to comment
Share on other sites

[root@omar omar]# man sane-mustek_usb

sane-mustek(5)                                     sane-mustek(5)



NAME

      sane-mustek_usb  -  SANE  backend  for  Mustek USB flatbed

      scanners



DESCRIPTION

      The sane-mustek_usb library  implements  a  SANE  (Scanner

      Access  Now  Easy)  backend that provides access to Mustek

      (and some relabeled Trust) USB flatbed scanners.  At  pre­

      sent,  the  following  scanners  are known to work more or

      less with this backend:



             Mustek 600 CU

             Mustek 1200 UB

             Mustek 1200 CU

             Mustek 1200 CU Plus

             Trust Compact Scan USB 19200



      More details can be found on the Mustek  backend  homepage

      http://www.meier-geinitz.de/sane/.



      The Mustek BearPaw 1200 and 2400 scanners are supported by

the plustek backend. See sane-plustek(5) for details.



      This backend is based on the 1200ub  backend  provided  by

      Mustek. It was modified to fit into the SANE distribution,

      some bugs were fixed, support for the 600  CU  was  added,

      and some features added.



      This  is  BETA  software. It currently only works on Linux

      and FreeBSD. Other systems are untested. See BUGS for more

      information.



      This  backend can only work with scanners that are already

      detected by the operating system. For  Linux,  it  may  be

      necessary  to load the scanner module with additional ven­

      dor/product  parameters   /see   /usr/src/linux/Documenta­

      tion/usb/scanner.txt  for  details). With FreeBSD upto 4.4

      only the 1200 CU will work out-of-the box. For other scan­

      ners,  their  ids  must be added to the FreeBSD uscanner.c

      file and a new kernel must be compiled.



      If you own a Mustek (or Trust) scanner other than the ones

      listed  above  that works with this backend, please let me

      know this by sending the scanner's exact  model  name  and

the    USB    vendor    and    device   ids   (e.g.   from

      /proc/bus/usb/devices or syslog) to me.



DEVICE NAMES

      This backend expects device names of the form:



             special



      Where special is a path-name for the special  device  that

      corresponds  to  a USB scanner.  With Linux, such a device

      name could be /dev/usb/scanner0 or  /dev/usbscanner1,  for

      example.



      For FreeBSD use /dev/uscanner0.



CONFIGURATION

      The  contents  of  the  mustek_usb.conf  file is a list of

      options and device names that  correspond  to  Mustek  USB

      scanners.  Empty lines and lines starting with a hash mark

      (#)  are  ignored.  If  a  device  name   is   placed   in

      mustek_usb.conf,  it must be followed by a line containing

      the keyword option and an option  specifying  the  scanner

      type.  The  following  options can be used: 600cu, 1200cu,

1200cu_plus, 1200ub.  For the Trust Compact Scan USB 19200

      use `option 1200ub'.



      Instead  of  using  the  device  name,  the scanner can be

      autodetected by usb vendor_id product_id statements  which

      are  already  included into mustek_usb.conf.  This is only

      supported with Linux 2.4.8  and  higher.  "vendor_id"  and

      "product_id"  are  hexadecimal  numbers  that  identfy the

      scanner. If this doesn't  work,  a  device  name  and  the

      option  specifying  the  scanner  type  must  be placed in

      mustek_usb.conf.



      The global option max_block_size can be used to limit  the

      amount  of  data acquired in one turn from the USB system.

      It may be woth trying, if USB errors occur.



      A sample configuration file is shown below:



             # Comment

             option max_block_size 1024

             usb 0x055f 0x0001

             /dev/usb/scanner0

             option 600cu

The first line is ignored. The second line sets the buffer

      size  to a maximum of 1024 bytes.  The third line tries to

      autodetect a scanner with vendor id 0x055f and product  id

      0x0001 (Mustek 1200 CU). The fourth line tells the backend

      to attach to /dev/usb/scanner0 and the fifth  line  speci­

      fies that /dev/usb/scanner0 is a Mustek 600 CU.



FILES

      /etc/sane.d/mustek_usb.conf

             The  backend  configuration file (see also descrip­

             tion of SANE_CONFIG_DIR below).



      /usr/lib/sane/libsane-mustek_usb.a

             The static library implementing this backend.



      /usr/lib/sane/libsane-mustek_usb.so

             The shared library implementing this backend  (pre­

             sent on systems that support dynamic loading).

ENVIRONMENT

      SANE_CONFIG_DIR

             This  environment  variable  specifies  the list of

             directories  that  may  contain  the  configuration

             file.  Under UNIX, the directories are separated by

             a colon (`:'), under OS/2, they are separated by  a

             semi-colon (`;').  If this variable is not set, the

             configuration  file  is  searched  in  two  default

             directories:  first,  the current working directory

             (".") and then in /etc/sane.d.  If the value of the

             environment  variable ends with the directory sepa­

             rator character, then the default  directories  are

             searched  after  the  explicitly specified directo­

             ries.   For  example,  setting  SANE_CONFIG_DIR  to

             "/tmp/config:"    would   result   in   directories

             "tmp/config", ".", and "/etc/sane.d" being searched

             (in this order).

SANE_DEBUG_MUSTEK_USB

             If  the  library  was  compiled  with debug support

             enabled, this  environment  variable  controls  the

             debug  level for this backend.  Higher debug levels

             increase the verbosity of the output.



             Value  Descsription

             0      no output

             1      print fatal errors

             2      print important messages

             3      print non-fatal errors and less important messages

             4      print all but debugging messages

             5      print high level debugging messages

             6      print medium level debugging messages

             7      print low level debugging messages



             Example:

             export SANE_DEBUG_MUSTEK_USB=4

 

I hope this helps.

Link to comment
Share on other sites

Also, I have these files:

/home/omar/.sane/xsane

/home/omar/.sane/xsane/xsane.rc

/home/omar/.sane/xsane/Mustek:1200UB.drc

/root/.sane/xsane

/root/.sane/xsane/xsane.rc

/root/.sane/xsane/Mustek:1200UB.drc

 

I think the Mustek:1200UB.drc is the important one:

"XSANE_DEVICE_RC"

"Mustek:1200 UB"

"xsane-version"

"0.87"

"mode"

"Gray"

"resolution"

13369344

"preview"

0

"tl-x"

600286

"tl-y"

1200572

"br-x"

12039092

"br-y"

18842352

"custom-gamma"

0

"xsane-main-window-x-position"

7

"xsane-main-window-y-position"

188

"xsane-main-window-width"

306

"xsane-main-window-height"

387

"xsane-standard-options-window-x-position"

24

"xsane-standard-options-window-y-position"

438

"xsane-advanced-options-window-x-position"

280

"xsane-advanced-options-window-y-position"

420

"xsane-histogram-window-x-position"

280

"xsane-histogram-window-y-position"

50

"xsane-gamma-window-x-position"

0

"xsane-gamma-window-y-position"

0



[bunch more configuration options]

Link to comment
Share on other sites

many many thanks for all this , Steve. I'll sit down with the links you've mentioned and get downloading. A quick look tells me one thing: The model I have is the 1200 UB Plus and the Plus makes all the difference. It needs a completely different driver. I haven't the time at the moment but will get to it as soon as pos.

Thanks again

Finlay

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...