LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 12-17-2005, 11:17 AM   #1
yuchai
Member
 
Registered: Jan 2005
Location: New York, NY
Distribution: Slackware 13.0
Posts: 56

Rep: Reputation: 15
Memorex MEM 48U scanner


I am trying to get this scanner to work. According to this link my scanner should be supported in SANE

http://www.sane-project.org/sane-mfgs.html#Z-MEMOREX

I have SANE installed and it seems to be detecting the scanner properly. Here's the output of a couple of commands:

Code:
yuchai@livingroom:~$ sane-find-scanner

  # sane-find-scanner will now attempt to detect your scanner. If the
  # result is different from what you expected, first make sure your
  # scanner is powered up and properly connected to your computer.

  # No SCSI scanners found. If you expected something different, make sure that
  # you have loaded a SCSI driver for your SCSI adapter.
  # Also you need support for SCSI Generic (sg) in your operating system.
  # If using Linux, try "modprobe sg".

found USB scanner (vendor=0x05d8, product=0x4005, chip=GT-6816) at libusb:002:004
  # Your USB scanner was (probably) detected. It may or may not be supported by
  # SANE. Try scanimage -L and read the backend's manpage.

  # Not checking for parallel port scanners.

  # Most Scanners connected to the parallel port or other proprietary ports
  # can't be detected by this program.

  # You may want to run this program as root to find all devices. Once you
  # found the scanner devices, be sure to adjust access permissions as
  # necessary.
yuchai@livingroom:~$ scanimage -L
device `artec_eplus48u:libusb:002:004' is a Memorex MEM 48U USB flatbed scanner
In my mind this means the device was set up properly in SANE.

When I launch xsane, however, I get an error message:

Failed to open device 'artec_eplus48u:libusb:002:004': Invalid argument

What am I missing here? Thanks in advance for any help you can provide.
 
Old 12-17-2005, 12:52 PM   #2
tobyl
Member
 
Registered: Apr 2003
Location: uk
Distribution: slackware current
Posts: 743

Rep: Reputation: 51
I am no expert on scanners or sane, and I had some difficulty getting my scanner to work (an epson). However I looked at your model, and it seems the product (product=0x4005) is not listed in /etc/hotplug/usb/libsane.usermap which I think is necessary. There is a close match, at least in my version of the file, as follows:

# Artec|E+ 48U
libusbscanner 0x0003 0x05d8 0x4003 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x00000000


The 0x05d8 entry is the vendor, which is correct, but the product is 0x4003 (not 0x4005 as in your case).
Its only a guess really, but it may be worth editing this file to reflect your product entry.

The other thing is that you need to make sure your artec_eplus48u.conf file is correct and contains the path to the firmware file which you need from your installation disc. Read carefully FIRMWARE FILE and CONFIGURATION from here:
http://www.sane-project.org/man/sane...plus48u.5.html

Memorex is not really mentioned, so I guess your scanner is a 'rebadged' Artec

I hope this helps,
tobyl
 
Old 12-17-2005, 02:31 PM   #3
yuchai
Member
 
Registered: Jan 2005
Location: New York, NY
Distribution: Slackware 13.0
Posts: 56

Original Poster
Rep: Reputation: 15
Thanks tobyl for your help. I was able to get it working. For reference purposes this is what I had to do:

1. Get the firmware file from the Windows installation disk - Artec48.usb
2. Edit /etc/sane.d/artec_eplus48u.conf. Find the Memorex section (usb 0x05d8 0x4005). Change the filepath for the firmware file (option artecFirmwareFile <pathname>/Artec48.usb), and also make sure to add this line:

option ePlusPro 0

Without this line the scanned images look corrupted.

That's it. Here's a link that shows you how to do it as well.

http://www.mepis.org/node/4154?PHPSE...2b0812d88e6053
 
Old 12-17-2005, 02:38 PM   #4
tobyl
Member
 
Registered: Apr 2003
Location: uk
Distribution: slackware current
Posts: 743

Rep: Reputation: 51
cool!

tobyl
 
Old 01-12-2007, 08:39 PM   #5
matchstich
LQ Newbie
 
Registered: Dec 2006
Posts: 8

Rep: Reputation: 0
hi, i followed the steps and did it right, i think.
cept when i go to applications>graphics>xsane image scanner,
i get no devices available
but sane-find-scanner shows this

# sane-find-scanner will now attempt to detect your scanner. If the
# result is different from what you expected, first make sure your
# scanner is powered up and properly connected to your computer.

# No SCSI scanners found. If you expected something different, make sure that
# you have loaded a kernel SCSI driver for your SCSI adapter.
# Also you need support for SCSI Generic (sg) in your operating system.
# If using Linux, try "modprobe sg".

found USB scanner (vendor=0x05d8, product=0x4005, chip=GT-6816?) at libusb:004:006
# Your USB scanner was (probably) detected. It may or may not be supported by
# SANE. Try scanimage -L and read the backend's manpage.

# Not checking for parallel port scanners.

# Most Scanners connected to the parallel port or other proprietary ports
# can't be detected by this program.

# You may want to run this program as root to find all devices. Once you
# found the scanner devices, be sure to adjust access permissions as
# necessary.
device manager shows it as a unknown

but scanimage -L shows this
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).
thanks

i did as noted on here
https://help.ubuntu.com/community/ArtecEplus48uConf

Last edited by matchstich; 01-12-2007 at 08:45 PM.
 
Old 01-13-2007, 05:46 AM   #6
tobyl
Member
 
Registered: Apr 2003
Location: uk
Distribution: slackware current
Posts: 743

Rep: Reputation: 51
Hi matchstich, could you give some more info,

which distibution and version are you using? (you might like to edit your lq profile)
which kernel? (uname -r)
what is the exact model of your scanner?

Also, did you modify the product id and path to the firmware file (that you copied to your sane.d directory) in the conf file?
Do you get any further running the commands as root?
Can you post the output of lsmod?

tobyl
 
Old 01-13-2007, 08:59 PM   #7
matchstich
LQ Newbie
 
Registered: Dec 2006
Posts: 8

Rep: Reputation: 0
hi, ubuntu 6.06 LTs.
kernal= uname -r
2.6.15-27-386

memorex mem48u--usb connected and powered

output of artec_eplus48u.conf

# artec_eplus48u - SANE Backend configuration file
# For use with the Artec E+ 48U scanner
# This scanner is also sold as
# Tevion MD 9693, Medion MD 9705, Medion MD 9693,
# Trust Easy Webscan 19200, Memorex Mem 48U or Umax AstraSlim SE.
#
# The USB section:
# each device needs at least the following line:
# usb vendor-ID and product-ID
# Every device configuration in this file must begin with an usb entry.
usb 0x05d8 0x4003

#
# Path to the firmware file
# This file comes with the Windows driver
# The scanner won't work without it
#

option artecFirmwareFile /usr/share/sane.d/art3c_eplus48u/Artec48.usb
option ePlusPro 0

#
# for adjusting the default gamma values
#

option redGamma 1.0
option greenGamma 1.0
option blueGamma 1.0
option masterGamma 1.9

#Use this options to set the default offset and exposure time values.

option redOffset 0x28
option greenOffset 0x2f
option blueOffset 0x2f
option redExposure 0xa7
option greenExposure 0x116
option blueExposure 0xdc

# The vendor and model string
# This string is displayed by the frontends. If you do not want to get your
# scanner reported as "Artec E+ 48U", then change the option accordingly.

option vendorString "Artec"
option modelString "E+ 48U"

#
# device-name
#
# If autodetection does not work, then you can specify the device here
# The device entry must be the last one in this config file (or the last one before a
# new usb entry).

#If you are using libusb, a device looks like this:
#device libusb:001:002

#If you are using the scanner module (kernel driver), a device looks like this:
#device /dev/usbscanner


# Another USB section:
# each device needs at least the following line:
# usb vendor-ID and product-ID
# Every device configuration in this file must begin with an usb entry.
# Since the Trust Easy Webscan 19200 uses a different product id, we add
# another usb section here.

usb 0x05d8 0x4005

#
# Path to the firmware file
# This file comes with the Windows driver
# The scanner won't work without it
#

option artecFirmwareFile /usr/share/sane.d/artec_eplus48uArtec48.usb

#
# for adjusting the default gamma values
#
option ePlusPro 1
option redGamma 1.0
option greenGamma 1.0
option blueGamma 1.0
option masterGamma 1.9

#Use this options to set the default offset and exposure time values.
#If calibrate device is set to 0, this values are used instead of the values
#which were calculated during calibration.

option redOffset 0x28
option greenOffset 0x2f
option blueOffset 0x2f
option redExposure 0xa7
option greenExposure 0x116
option blueExposure 0xdc

# The vendor and model string
# This string is displayed by the frontends. The Trust Easy Webscan 19200
# has a different product id, therefore we can overwrite the vendor and model
# string here.

option vendorString "Trust"
option modelString "Easy Webscan 19200"

#
# device-name
#
# If autodetection does not work, then you can specify the device here
# The device entry must be the last one in this config file (or the last one before a
# new usb entry).

#If you are using libusb, a device looks like this:
#device libusb:001:002

#If you are using the scanner module (kernel driver), a device looks like this:
#device /dev/usbscanner

# Another USB section:
# each device needs at least the following line:
# usb vendor-ID and product-ID
# Every device configuration in this file must begin with an usb entry.
# Since the Memorex Mem48U uses a different product id, we add
# another usb section here.

usb 0x05d8 0x4005

#
# Path to the firmware file
# This file comes with the Windows driver
# The scanner won't work without it
#

option artecFirmwareFile /etc/sane.d/Artec48.usb
option ePluspro 0

#
# for adjusting the default gamma values
#

option redGamma 1.0
option greenGamma 1.0
option blueGamma 1.0
option masterGamma 1.9

#Use this options to set the default offset and exposure time values.
#If calibrate device is set to 0, this values are used instead of the values
#which were calculated during calibration.

option redOffset 0x28
option greenOffset 0x2f
option blueOffset 0x2f
option redExposure 0xa7
option greenExposure 0x116
option blueExposure 0xdc

# The vendor and model string
# This string is displayed by the frontends. The Umax AstraSlim SE
# has a different product id, therefore we can overwrite the vendor and model
# string here.

option vendorString "Memorex"
option modelString "MEM 48U"

#
# device-name
#
# If autodetection does not work, then you can specify the device here
# The device entry must be the last one in this config file (or the last one before a
# new usb entry).

#If you are using libusb, a device looks like this:
device libusb:004:006

#If you are using the scanner module (kernel driver), a device looks like this:
#device /dev/usbscanner

# Another USB section:
# each device needs at least the following line:
# usb vendor-ID and product-ID
# Every device configuration in this file must begin with an usb entry.
# Since the Trust 240H Easy Webscan Gold uses a different product id, we add
# another usb section here.

usb 0x05d8 0x4007

#
# Path to the firmware file
# This file comes with the Windows driver
# The scanner won't work without it
#

option artecFirmwareFile /usr/share/sane/artec_eplus48u/Artec48.usb

#
# for adjusting the default gamma values
#
option ePlusPro 1
option redGamma 1.0
option greenGamma 1.0
option blueGamma 1.0
option masterGamma 1.9

#Use this options to set the default offset and exposure time values.
#If calibrate device is set to 0, this values are used instead of the values
#which were calculated during calibration.

option redOffset 0x28
option greenOffset 0x2f
option blueOffset 0x2f
option redExposure 0xa7
option greenExposure 0x116
option blueExposure 0xdc

# The vendor and model string
# This string is displayed by the frontends. The Trust 240H Easy Webscan Gold
# has a different product id, therefore we can overwrite the vendor and model
# string here.

option vendorString "Trust"
option modelString "240H Easy Webscan Gold"

#
# device-name
#
# If autodetection does not work, then you can specify the device here
# The device entry must be the last one in this config file (or the last one before a
# new usb entry).

#If you are using libusb, a device looks like this:
#device libusb:001:002

#If you are using the scanner module (kernel driver), a device looks like this:
#device /dev/usbscanner

# Another USB section:
# each device needs at least the following line:
# usb vendor-ID and product-ID
# Every device configuration in this file must begin with an usb entry.
# Since the Umax AstraSlim SE uses a different product id, we add
# another usb section here.

usb 0x05d8 0x4009

#
# Path to the firmware file
# This file comes with the Windows driver
# The scanner won't work without it
#

option artecFirmwareFile /usr/share/sane/artec_eplus48u/Artec48.usb

#
# for adjusting the default gamma values
#

option redGamma 1.0
option greenGamma 1.0
option blueGamma 1.0
option masterGamma 1.9

#Use this options to set the default offset and exposure time values.
#If calibrate device is set to 0, this values are used instead of the values
#which were calculated during calibration.

option redOffset 0x28
option greenOffset 0x2f
option blueOffset 0x2f
option redExposure 0xa7
option greenExposure 0x116
option blueExposure 0xdc

# The vendor and model string
# This string is displayed by the frontends. The Umax AstraSlim SE
# has a different product id, therefore we can overwrite the vendor and model
# string here.

option vendorString "Umax"
option modelString "AstraSlim SE"

#
# device-name
#
# If autodetection does not work, then you can specify the device here
# The device entry must be the last one in this config file (or the last one before a
# new usb entry).

#If you are using libusb, a device looks like this:
#device libusb:001:002

#If you are using the scanner module (kernel driver), a device looks like this:
#device /dev/usbscanner

# Another USB section:
# each device needs at least the following line:
# usb vendor-ID and product-ID
# Every device configuration in this file must begin with an usb entry.
# This section is for the Artec E+ Pro
# Note, that the name of the firmware file is called 1200.usb for
# this device

usb 0x05d8 0x4004

#
# Path to the firmware file
# This file comes with the Windows driver
# The scanner won't work without it
#

option artecFirmwareFile /usr/share/sane/artec_eplus48u/1200.usb

#
# Tell the backend that this is an Artec E+ Pro
# by setting the option ePlusPro to 1
#

option ePlusPro 1

#
# for adjusting the default gamma values
#

option redGamma 1.0
option greenGamma 1.0
option blueGamma 1.0
option masterGamma 1.9

#Use this options to set the default offset and exposure time values.
#If calibrate device is set to 0, this values are used instead of the values
#which were calculated during calibration.

option redOffset 0x28
option greenOffset 0x2f
option blueOffset 0x2f
option redExposure 0xa7
option greenExposure 0x116
option blueExposure 0xdc

# The vendor and model string
# This string is displayed by the frontends. The Umax AstraSlim SE
# has a different product id, therefore we can overwrite the vendor and model
# string here.

option vendorString "Artec"
option modelString "E+ Pro"

#
# device-name
#
# If autodetection does not work, then you can specify the device here
# The device entry must be the last one in this config file (or the last one before a
# new usb entry).

#If you are using libusb, a device looks like this:
#device libusb:001:002

#If you are using the scanner module (kernel driver), a device looks like this:
#device /dev/usbscanner

# Another USB section:
# each device needs at least the following line:
# usb vendor-ID and product-ID
# Every device configuration in this file must begin with an usb entry.
# This section is for the UMAX AstraSlim 1200 SE
# Note, that the name of the firmware file is called 1200.usb for
# this device

usb 0x05d8 0x4010

#
# Path to the firmware file
# This file comes with the Windows driver
# The scanner won't work without it
#

option artecFirmwareFile /usr/share/sane/artec_eplus48u/1200.usb

#
# for adjusting the default gamma values
#

option redGamma 1.0
option greenGamma 1.0
option blueGamma 1.0
option masterGamma 1.9

#Use this options to set the default offset and exposure time values.
#If calibrate device is set to 0, this values are used instead of the values
#which were calculated during calibration.

option redOffset 0x28
option greenOffset 0x2f
option blueOffset 0x2f
option redExposure 0xa7
option greenExposure 0x116
option blueExposure 0xdc

# The vendor and model string
# This string is displayed by the frontends. The Umax AstraSlim 1200 SE
# has a different product id, therefore we can overwrite the vendor and model
# string here.

option vendorString "UMAX"
option modelString "AstraSlim 1200 SE"

#
# device-name
#
# If autodetection does not work, then you can specify the device here
# The device entry must be the last one in this config file (or the last one before a
# new usb entry).

#If you are using libusb, a device looks like this:
#device libusb:001:002

#If you are using the scanner module (kernel driver), a device looks like this:
#device /dev/usbscanner

Ismod

freq_table 4740 1 cpufreq_stats
cpufreq_powersave 1920 0
cpufreq_ondemand 6428 0
cpufreq_conservative 7332 0
video 16260 0
tc1100_wmi 6916 0
sony_acpi 5644 0
pcc_acpi 12416 0
hotkey 11556 0
dev_acpi 11140 0
container 4608 0
button 6672 0
acpi_sbs 19980 0
battery 9988 1 acpi_sbs
ac 5252 1 acpi_sbs
i2c_acpi_ec 5120 1 acpi_sbs
ipv6 265856 6
dm_mod 58936 1
md_mod 72532 0
lp 11844 0
af_packet 22920 2
snd_seq_dummy 3844 0
snd_seq_oss 33536 0
snd_seq_midi 9376 0
snd_seq_midi_event 7552 2 snd_seq_oss,snd_seq_midi
snd_seq 51984 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_via82xx 28824 3
gameport 15496 1 snd_via82xx
snd_ac97_codec 93216 1 snd_via82xx
snd_ac97_bus 2304 1 snd_ac97_codec
snd_pcm_oss 53664 0
snd_mixer_oss 18688 1 snd_pcm_oss
floppy 62148 0
pcspkr 2180 0
snd_pcm 89864 4 snd_via82xx,snd_ac97_codec,snd_pcm_oss
psmouse 36100 0
rtc 13492 0
serio_raw 7300 0
snd_timer 25220 3 snd_seq,snd_pcm
snd_page_alloc 10632 2 snd_via82xx,snd_pcm
snd_mpu401_uart 7808 1 snd_via82xx
snd_rawmidi 25504 2 snd_seq_midi,snd_mpu401_uart
snd_seq_device 8716 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq,snd_rawmidi
via686a 17672 0
i2c_isa 4992 1 via686a
i2c_viapro 8980 0
snd 55268 15 snd_seq_oss,snd_seq,snd_via82xx,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer,snd_mpu40 1_uart,snd_rawmidi,snd_seq_device
usblp 13056 0
soundcore 10208 1 snd
8139cp 22528 0
8139too 26880 0
mii 5888 2 8139cp,8139too
shpchp 45632 0
pci_hotplug 29236 1 shpchp
nvidia 4551028 0
i2c_core 21904 5 i2c_acpi_ec,via686a,i2c_isa,i2c_viapro,nvidia
parport_pc 35780 1
parport 36296 3 ppdev,lp,parport_pc
via_agp 9856 1
agpgart 34888 2 nvidia,via_agp
tsdev 8000 0
evdev 9856 1
usbhid 39904 0
ext3 135816 1
jbd 58772 1 ext3
ide_generic 1536 0
ehci_hcd 34184 0
ohci_hcd 21892 0
uhci_hcd 33808 0
usbcore 130820 6 usblp,usbhid,ehci_hcd,ohci_hcd,uhci_hcd
ide_cd 33028 2
cdrom 38560 1 ide_cd
ide_disk 17664 3
via82cxxx 9988 0 [permanent]
generic 5124 0
thermal 13576 0
processor 23360 1 thermal
fan 4868 0
capability 5000 0
commoncap 7296 1 capability
vga16fb 13704 1
vgastate 10368 1 vga16fb
fbcon 42784 72
tileblit 2816 1 fbcon
font 8320 1 fbcon
bitblit 6272 1 fbcon
softcursor 2304 1 bitblit

ok, there is everything that i can think to post here.
thanks for any help you can give me

lsusb
Bus 003 Device 003: ID 047d:101f Kensington PocketMouse Pro
Bus 003 Device 002: ID 03f0:3402 Hewlett-Packard
Bus 003 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 002 Device 002: ID 05d8:4005 Ultima Electronics Corp.
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000

Last edited by matchstich; 01-14-2007 at 03:51 AM.
 
Old 01-14-2007, 04:32 AM   #8
tobyl
Member
 
Registered: Apr 2003
Location: uk
Distribution: slackware current
Posts: 743

Rep: Reputation: 51
Ok, well I am not an Ubuntu user, but I guess if you post in a Slackware forum you must be really stuck, so I will make a couple of suggestions.

First, make sure you know where your sane.d directory is. I guess it is /etc/sane.d as the instructions you followed indicates this

(it also means the artec_eplus48u.conf file on your system is generic, not tailored for Ubuntu, as the default path in the file is given as /usr/share/sane.d/)

You have not edited the file artec_eplus48u.conf correctly.


usb 0x05d8 0x4005 has two entries in this file, and your entry is the second one, so it will probably not get found, so comment out (with #) or remove the first section that refers to this usb 0x05d8 0x4005 string.

Also if it still doesn't work, try the command scanimage -L as root. ( I think you use sudo for that on your distro) - this will test whether there is a permissions problem.

My scanner is different, but I have the sg module loaded, which I noticed you do not. So you may have the support built in to your kernel, otherwise you may wish to try "modprobe sg" as your sane-find-scanner output suggested:

# No SCSI scanners found. If you expected something different, make sure that
# you have loaded a kernel SCSI driver for your SCSI adapter.
# Also you need support for SCSI Generic (sg) in your operating system.
# If using Linux, try "modprobe sg".

This may also require root permissions.

good luck

tobyl

Last edited by tobyl; 01-14-2007 at 04:34 AM.
 
Old 07-13-2007, 10:48 PM   #9
matchstich
LQ Newbie
 
Registered: Dec 2006
Posts: 8

Rep: Reputation: 0
mem48

never could get the scanner to work in 6.06 lts.

upgraded to unbuntu 7.04 followed the directions again.

now it opens but when i click on scan

all i get is a grinding sound like a gear is stuck.

any one have any ideas?

thanks
 
Old 07-14-2007, 04:09 AM   #10
tobyl
Member
 
Registered: Apr 2003
Location: uk
Distribution: slackware current
Posts: 743

Rep: Reputation: 51
Is there a lock switch? I read somewhere that you sometimes have to lock and unlock again.

tobyl
 
Old 07-15-2007, 10:23 AM   #11
matchstich
LQ Newbie
 
Registered: Dec 2006
Posts: 8

Rep: Reputation: 0
ok, i tried that. same problem. grinding sound.
thanks

maybe something is wrong with it. cept it did work before in windows.
 
Old 07-17-2007, 07:52 PM   #12
matchstich
LQ Newbie
 
Registered: Dec 2006
Posts: 8

Rep: Reputation: 0
question: do i need to download any thing for the mem48 to work?

i searched every where but every one is saying they got it working just by following the directions about putting the firmware from the windows install disc in sane.d.
 
Old 07-17-2007, 10:53 PM   #13
yuchai
Member
 
Registered: Jan 2005
Location: New York, NY
Distribution: Slackware 13.0
Posts: 56

Original Poster
Rep: Reputation: 15
Hi there - here's my config. I can currently scan images using my scanner.

The relevant section in /etc/sane.d/artec_eplus48u.conf

Quote:
# Since the Memorex Mem48U uses a different product id, we add
# another usb section here.
usb 0x05d8 0x4005
option artecFirmwareFile /usr/share/sane/artec_eplus48u/Artec48.usb
option vendorString "Memorex"
option modelString "MEM 48U"
Make sure that this is the only section that refers to the scanner. I had previously mentioned that "option ePlusPro 0" is needed, but it seems that this is no longer the case. Perhaps it's due to an upgrade to sane, the version I'm using now is 1.0.18

Also verify that the firmware is in the right place and is the correct file. Here's mine (note the file size):

Quote:
yuchai@livingroom:~$ ls -al /usr/share/sane/artec_eplus48u
total 8
drwxr-xr-x 2 root root 24 2007-05-27 01:13 ./
drwxr-xr-x 6 root root 87 2007-03-13 20:59 ../
-rw-r--r-- 1 root root 8192 2005-12-17 15:20 Artec48.usb
 
Old 07-19-2007, 05:23 AM   #14
matchstich
LQ Newbie
 
Registered: Dec 2006
Posts: 8

Rep: Reputation: 0
ok, i went back to the install link. it said something about installing the sane drivers.
that i didn't do. not sure how to do that.

anyhow, i changed the line in etc/

to

# artec_eplus48u - SANE Backend configuration file

# This section is for use with the Artec E+ 48U scanner
# This scanner is also sold as
# Tevion MD 9693, Medion MD 9705, Medion MD 9693, Medion MD4394
# This sections contains verbose description of each option.
# For other scanners, see below.
#
# The USB section:
# each device needs at least the following line:
# usb vendor-ID and product-ID
# Every device configuration in this file must begin with an usb entry.
usb 0x05d8 0x4003

# Path to the firmware file
# This file comes with the Windows driver
# The scanner won't work without it
option artecFirmwareFile /usr/share/sane/artec_eplus48u/Artec48.usb

# Is the scanner an Artec E Plus Pro (or compatible)? 0 = no, 1 = yes
option ePlusPro 0

# for adjusting the default gamma values
option redGamma 1.0
option greenGamma 1.0
option blueGamma 1.0
option masterGamma 1.9

#Use this options to set the default offset and exposure time values.
option redOffset 0x28
option greenOffset 0x2f
option blueOffset 0x2f
option redExposure 0xa7
option greenExposure 0x116
option blueExposure 0xdc

# The vendor and model string
# This string is displayed by the frontends. If you do not want to get your
# scanner reported as "Artec E+ 48U", then change the option accordingly.
option vendorString "Artec"
option modelString "E+ 48U"

# device-name
#
# If autodetection does not work, then you can specify the device here
# The device entry must be the last one in this config file (or the last one before a
# new usb entry).
#If you are using libusb, a device looks like this:
#device libusb:001:002
#If you are using the scanner module (kernel driver), a device looks like this:
#device /dev/usbscanner

# ----------------------------------------------------------------------------

# Since the Trust Easy Webscan 19200 uses a different product id, we add
# another usb section here.
usb 0x05d8 0x4006
option artecFirmwareFile /usr/share/sane/artec_eplus48u/Artec48.usb
option vendorString "Trust"
option modelString "Easy Webscan 19200"

# ----------------------------------------------------------------------------

# Since the Memorex Mem48U uses a different product id, we add
# another usb section here.
usb 0x05d8 0x4005
option artecFirmwareFile /usr/share/sane/artec_eplus48u/Artec48.usb
option vendorString "Memorex"
option modelString "MEM 48U"

# ----------------------------------------------------------------------------

# Since the Trust 240H Easy Webscan Gold uses a different product id, we add
# another usb section here.
usb 0x05d8 0x4007
option artecFirmwareFile /usr/share/sane/artec_eplus48u/Artec48.usb
option ePlusPro 1
option vendorString "Trust"
option modelString "240H Easy Webscan Gold"

# ----------------------------------------------------------------------------

# Since the UMAX AstraSlim SE uses a different product id, we add
# another usb section here.
usb 0x05d8 0x4009
option artecFirmwareFile /usr/share/sane/artec_eplus48u/Artec48.usb
option vendorString "UMAX"
option modelString "AstraSlim SE"

# ----------------------------------------------------------------------------

# This section is for the Artec E+ Pro
# Note, that the name of the firmware file is called 1200.usb for
# this device
usb 0x05d8 0x4004
option artecFirmwareFile /usr/share/sane/artec_eplus48u/1200.usb
option ePlusPro 1
option vendorString "Artec"
option modelString "E+ Pro"

# ----------------------------------------------------------------------------

# This section is for the UMAX AstraSlim 1200 SE
# Note, that the name of the firmware file is called 1200.usb for
# this device
usb 0x05d8 0x4010
option artecFirmwareFile /usr/share/sane/artec_eplus48u/1200.usb
option vendorString "UMAX"
option modelString "AstraSlim 1200 SE"

# ----------------------------------------------------------------------------

# Since the Yakumo Scan50 uses a different product id, we add
# another usb section here.
usb 0x05d8 0x4011
option artecFirmwareFile /usr/share/sane/artec_eplus48u/Artec48.usb
option vendorString "Yakumo"
option modelString "Scan50"




i am confused by this. because the directions said to have the following

# Since the Memorex Mem48U uses a different product id, we add
# another usb section here.

to look like this:

# Since the Memorex Mem48U uses a different product id, we add
# another usb section here.

usb 0x05d8 0x4005

#
# Path to the firmware file
# This file comes with the Windows driver
# The scanner won't work without it
#

option artecFirmwareFile /etc/sane.d/Artec48.usb
option ePlusPro 0

which i did.at first, but, changed it to what yuchai showed in the last post.
but now, when i do

ls -al /usr/share/sane/artec_eplus48u

i get no such file or directory.

many thanks for y'all helping me.
cept i think i am missing something here.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Mounting USB Memorex 512MB Thumbdrive ckovacs Linux - Hardware 3 12-06-2004 10:33 AM
Memorex MX3300 keyboard mapping Captain Harlock Linux - Hardware 0 07-17-2004 03:53 PM
Can't get linux to recognize Memorex MMP8500 MP3 player Gargonia Linux - Hardware 4 06-13-2004 02:29 PM
Memorex 16x-24x CD-RW tricky_linux Linux - Software 1 11-21-2003 07:50 PM
Memorex Optical Wheel Mouse problem grantm Linux - Newbie 3 07-22-2003 07:50 AM


All times are GMT -5. The time now is 09:24 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration