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: 148 Punkte bei 38 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: 194 Punkte bei 41 Stimmen.
Den Beitrag bewerten: Gut / Schlecht

Ähnliche Artikel

Aktuelle Fragen

Brother Drucker DCP-J4120
Achim Zerrer, 09.12.2016 18:08, 0 Antworten
Hallo, ich wollte unter Leap 42.1 den Brother Drucker installieren und dazu das PPD- Datei vom do...
Drucker Epson XP-332 unter ubuntu 14.04 einrichten
Andrea Wagenblast, 30.11.2016 22:07, 2 Antworten
Hallo, habe vergeblich versucht mein Multifunktionsgerät Epson XP-332 als neuen Drucker unter...
Apricity Gnome unter Win 10 via VirtualBox
André Driesel, 30.11.2016 06:28, 2 Antworten
Halo Leute, ich versuche hier schon seit mehreren Tagen Apricity OS Gnome via VirtualBox zum l...
EYE of Gnome
FRank Schubert, 15.11.2016 20:06, 2 Antworten
Hallo, EOG öffnet Fotos nur in der Größenordnung 4000 × 3000 Pixel. Größere Fotos werden nic...
Kamera mit Notebook koppeln
Karl Spiegel, 12.11.2016 15:02, 2 Antworten
Hi, Fotografen ich werde eine SONY alpha 77ii bekommen, und möchte die LifeView-Möglichkeit nu...

Jetzt auf den Mailinglisten

Re: [EasyLinux-Ubuntu] Ubuntu Nachrichtensammlung, Band 129, Eintrag 4
Hans, 08.12.2016 13:30
Hallo Scharam, einmal Tante Guurgel und da habe ich Pooka Email Client gefunden. Gruß Jörg Am 8. Dezem...
[EasyLinux-Ubuntu] Ein Mailprogramm in Java
Schahram Sanawi Garrousi, 07.12.2016 23:02
Hallo Liste Gibt es ein Mailprogramm in Java? Gruß Schahram -- 4.4.0-53-generic x86_64 * Kubuntu 16.04...
Re: [EasyLinux-Ubuntu] WLAN Adressenbereich
"Michael R. Moschner", 02.12.2016 17:54
Am Samstag, 26. November 2016, 00:54:07 schrieb Richard Kraut: Hallo Richard und alle anderen Danke für die...
Re: [EasyLinux-Ubuntu] [erledigt?] xubuntu 16.04: unvollständige_Aktualisierung
Hartmut Haase, 30.11.2016 18:16
Hallo Liste, > 0% [Verbindung mit security.ubuntu.com (2001:67c:1560:8001::11)] wenn man das Ganze lang...
Re: [EasyLinux-Ubuntu] xubuntu_16.04:_unvollständige_Aktualisierung
Hartmut Haase, 30.11.2016 16:28
Hallo Frank, > Habe ich auch gerade? > Root hat noch 3GB frei. ich habe noch knapp 10GB frei. Dara...