Scanner Medion MD9693 unter Suse9.1, fehlende Firmware

Anonymous User - Freitag, 20. August 2004 15:32:19 - 2 Antworten

Bringe weder unter Suse9.0 noch 9.1 meinen Medion-Scanner MD9693 zum laufen. Unter Yast kann ich ihn zwar auswählen, bekomme aber stets eine Meldung, dass dieser Scanner das Einspielen einer "Firmware" erfordert.
Nun habe ich schon so manchen Hinweis in Newsgroups gefunden, hat aber alles nichts gebracht.
Ich vermute, dass die "Firmwaredatei" artec48.usb heisst. Die habe ich unter windows gefunden und in den Ordner /etc/sane.d/ kopiert.

Dort ist auch eine Konfigurationsdatei "artec_eplus48u.conf", in der einige Kommentare stehen, unter anderem dass der Pfad zu der Firmwaredatei zu setzen ist.
Habe ich auch gemacht:
option artecFirmwareFile etc/sane.d/Artec48.usb
Dann gibt's noch das:
#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
Das interessiert YAST aber nicht, egal ob mit oder ohne Pfad, gleich welche devicezeile auskommentiert bleibt.
Kann mir jemand eine klare Hilfe geben, welche Datei (mit Namen) wo zu stehen hat, welche Datei (mit Namen) wo und wie zu editieren ist, dass der Scanner geht.

Antworten
Re: Scanner Medion MD9693 unter Suse9.1, fehlende Firmware
Martin Lehmann, Freitag, 20. August 2004 20:23:10
Ein/Ausklappen

Hallo,
ich hatte vor kurzem ein ähnliches Problem, jedoch benutze ich kein Suse.
Ich habe einfach die Firmware in den richtigen Ordner kopiert und XSANE (ich denke das geht auch mit jedem anderen Scanprogram z.B. Kooka) gestartet.
Mehr musste ich nicht machen. Hast Du es auf diesem Weg schon probiert?
Hier ist meine Konfigurationsdatei:
# 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 /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.

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/usb/scanner0


# 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 0x4006

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

option artecFirmwareFile /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 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/usb/scanner0

# 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 /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 "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:001:002

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

# 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 /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/usb/scanner0

# 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 /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/usb/scanner0

Bei mir liegt die Firmware allerdings in /etc/sane.d das kann aber ändern.



Bewertung: 153 Punkte bei 33 Stimmen.
Den Beitrag bewerten: Gut / Schlecht
-
Re: Scanner Medion MD9693 unter Suse9.1, fehlende Firmware
Christoph , Samstag, 21. August 2004 09:47:00
Ein/Ausklappen

und noch ein paar hilfreiche links:

[1] http://www.linux-community.de/Neues/story?storyid=5309
[2] https://portal.suse.com/PM/...s&m=25&l=de&x=true
[3] https://portal.suse.com/PM/...s&m=25&l=de&x=true



Bewertung: 201 Punkte bei 34 Stimmen.
Den Beitrag bewerten: Gut / Schlecht

Ähnliche Artikel

Aktuelle Fragen

Wie kann man das berichtigen
Udo Muelle, 17.07.2016 20:39, 1 Antworten
Fehlschlag beim Holen von http://extra.linuxmint.com/dists/rosa/main/binary-i386/Packages Hash-S...
Installation Genimotion
Horst Müller, 15.07.2016 17:00, 1 Antworten
Hallo, ich kann Genimotion nicht installieren. Folgende Fehlermeldung habe ich beim Aufruf erh...
Probleme beim Hochfahren der Terastaion 5400 mit Unix-Distrib
Sheldon Cooper, 10.07.2016 09:32, 0 Antworten
Hallo ihr lieben, habe seit zwei Tagen das Problem, das das NAS (Raid5) nicht mehr sauber hoch...
Mit Firewire Videos improtieren?
Werner Hahn, 09.06.2016 11:06, 5 Antworten
Ich besitze den Camcorder Panasonic NV-GS330, bei dem die Videos in guter Qualität nur über den 4...
lidl internetstick für linux mint
rolf meyer, 04.06.2016 14:17, 3 Antworten
hallo zusammen ich benötige eure hilfe habe einen lidl-internetstick möchte ihn auf linux mint i...

Jetzt auf den Mailinglisten

Re: [EasyLinux-Ubuntu] KMail und MDA
Steffen Weyh, 23.07.2016 16:00
Selbst wenn es technisch möglich wäre, die Konfiguration von 15 einzelnen SMTP-Ausgängen wäre in meinen Augen e...
Re: [EasyLinux-Ubuntu] KMail und MDA
heiko, 23.07.2016 15:39
Am Samstag, 23. Juli 2016, 14:50:31 schrieb Richard Kraut: > Am Samstag, den 23.07.2016, 11:09 +0200 schri...
Re: [EasyLinux-Ubuntu] KMail und MDA
Richard Kraut, 23.07.2016 14:50
Am Samstag, den 23.07.2016, 11:09 +0200 schrieb heiko: Das hört sich nach unserem alten Heinz-Stefan an. :-)...
Re: [EasyLinux-Ubuntu] KMail und MDA
heiko, 23.07.2016 13:57
Am Samstag, 23. Juli 2016, 12:11:32 schrieb Steffen Weyh: > Nicht gut! > Welche anderen Möglichkeiten...
Re: [EasyLinux-Ubuntu] KMail und MDA
Wilhelm Boltz, 23.07.2016 13:09
Am Samstag, 23. Juli 2016, 11:09:13 CEST schrieb heiko: > [...] > Greift nicht. Und die neuen Konfigu...