• Willkommen im Linux Club - dem deutschsprachigen Supportforum für GNU/Linux. Registriere dich kostenlos, um alle Inhalte zu sehen und Fragen zu stellen.

Parallelport-Scanner Plustek OpticPro4800 / Suse 9.1

mp2

Newbie
Hallo!

Auch nach dem Durchlesen verschiedener Themen, die das Einrichten von Parallelport-Scannern unter sane behandelten, komme ich leider nicht weiter mit meinem problem... ;-(

Ich versuche einen alten Scanner mit Sane zum Laufen zu bringen.

Suse's sane 1.0.13 habe ich rausgeschmissen und die aktuelle Version sane-1.0.14 (als rpm) geladen und installiert; davor wurde noch libieee1284-0.2.8-0.pm.0 installiert.

Die /etc/sane.d/dll.conf sowie /etc/sane.d/plustek_pp.conf
Code:
[direct]
device parport0
wurden entsprechend modifiziert.

LPT Mode ist in BIOS auf EPP 1.9 eingestellt.

Code:
export SANE_DEBUG_PLUSTEK_PP=20 ; scanimage -L

liefert folgendes:

Code:
[plustek_pp] PlustekPP backend V0.01-8, part of sane-backends 1.0.14
[plustek_pp] ># Plustek-PP SANE Backend configuration file<
[plustek_pp] ># For use with Plustek parallel-port scanners<
[plustek_pp] >#<
[plustek_pp] ><
[plustek_pp] >#<
[plustek_pp] ># user either [direct] or [kernel] to access the scanner<
[plustek_pp] ># when using [kernel], device specifies the device-node, which is created<
[plustek_pp] ># by the kernel-module loader (applies only to Linux)<
[plustek_pp] ># when using [direct], device is used to set the parallel-port base address<
[plustek_pp] ># or a device-name suitable for libieee1284, i.e. parport0<
[plustek_pp] >#<
[plustek_pp] >#[direct]<
[plustek_pp] >#device 0x378<
[plustek_pp] ><
[plustek_pp] >#<
[plustek_pp] ># leave the default values as specified in /etc/modules.conf<
[plustek_pp] >#<
[plustek_pp] >option warmup    -1<
[plustek_pp] Decoding option >warmup<
[plustek_pp] >option lOffOnEnd -1<
[plustek_pp] Decoding option >lOffOnEnd<
[plustek_pp] >option lampOff   -1<
[plustek_pp] Decoding option >lampOff<
[plustek_pp] ><
[plustek_pp] ># model override switch, mostly for cosmetic changes, if the autodetection<
[plustek_pp] ># does not work or could not work correctly<
[plustek_pp] >#option mov 7<
[plustek_pp] ><
[plustek_pp] >#<
[plustek_pp] ># example for accessing the scanner via libieee1284<
[plustek_pp] >#<
[plustek_pp] >[direct]<
[plustek_pp] >device parport0<
[plustek_pp] Decoding device name >parport0<
[plustek_pp] ><
[plustek_pp] >#<
[plustek_pp] ># example for accessing the scanner via the kernel module<
[plustek_pp] >#<
[plustek_pp] >#[kernel]<
[plustek_pp] >#device /dev/pt_drv<
[plustek_pp] >#<
[plustek_pp] >#option warmup    -1<
[plustek_pp] >#option lOffOnEnd -1<
[plustek_pp] >#option lampOff   -1<
[plustek_pp] attach (parport0, 0xbfff43d0, (nil))
[plustek_pp] Device configuration:
[plustek_pp] device name   : >parport0<
[plustek_pp] direct I/O    : yes
[plustek_pp] warmup        : -1s
[plustek_pp] lampOff       : -1
[plustek_pp] lampOffOnEnd  : yes
[plustek_pp] model override: 0
[plustek_pp] ---------------------
[plustek_pp] drvopen()
[plustek_pp] ptdrvInit(0)
[plustek_pp] Init settings done
[plustek_pp] ScanData = 0x08051a20
[plustek_pp] Assigning port handle 0
[plustek_pp] ptdrvOpen(port=0x0)
[plustek_pp] Try to claim the parport
[plustek_pp] Setting SPP-mode
[plustek_pp] Setting PS/2-mode
[plustek_pp] Setting EPP-mode
[plustek_pp] We're using libIEEE1284 I/O
[plustek_pp] Starting Scanner-Autodetection
[plustek_pp] ************ DETECTP48xx ************
[plustek_pp] ModelSet4800()
[plustek_pp] modelInitPageSettings()
[plustek_pp] A4 set
[plustek_pp] ModelSet4800() done.
[plustek_pp] P48xxInitAsic()
[plustek_pp] DacInitialize()
[plustek_pp] ImageInitialize()
[plustek_pp] IOFuncInitialize()
[plustek_pp] IOInitialize()
[plustek_pp] * using readfunction >fnEPPRead<
[plustek_pp] MotorInitialize()
[plustek_pp] ResetPort()
[plustek_pp] Test 0x55
[plustek_pp] Test 0xAA
[plustek_pp] Compare data=0xc8 and status=0x8, port=0x0
[plustek_pp] p48xxReadWriteTest()
[plustek_pp] Found a 96001 ASIC at Reg 0x13
[plustek_pp] ModelSet4800()
[plustek_pp] modelInitPageSettings()
[plustek_pp] A4 set
[plustek_pp] ModelSet4800() done.
[plustek_pp] p48xxCheck4800Memory()

Hier bleibt das Programm stehen, bis man's mit Strg-C abbricht.

Wird in BIOS als LPT-Mode ECP+EPP 1.9 eingestellt, ändert sich das Verhalten:

Code:
export SANE_DEBUG_PLUSTEK_PP=20 ; scanimage -L

Code:
[sanei_debug] Setting debug level of plustek_pp to 20.
[plustek_pp] PlustekPP backend V0.01-8, part of sane-backends 1.0.14
[plustek_pp] ># Plustek-PP SANE Backend configuration file<
[plustek_pp] ># For use with Plustek parallel-port scanners<
[plustek_pp] >#<
[plustek_pp] ><
[plustek_pp] >#<
[plustek_pp] ># user either [direct] or [kernel] to access the scanner<
[plustek_pp] ># when using [kernel], device specifies the device-node, which is created<
[plustek_pp] ># by the kernel-module loader (applies only to Linux)<
[plustek_pp] ># when using [direct], device is used to set the parallel-port base address<
[plustek_pp] ># or a device-name suitable for libieee1284, i.e. parport0<
[plustek_pp] >#<
[plustek_pp] >#[direct]<
[plustek_pp] >#device 0x378<
[plustek_pp] ><
[plustek_pp] >#<
[plustek_pp] ># leave the default values as specified in /etc/modules.conf<
[plustek_pp] >#<
[plustek_pp] >option warmup    -1<
[plustek_pp] Decoding option >warmup<
[plustek_pp] >option lOffOnEnd -1<
[plustek_pp] Decoding option >lOffOnEnd<
[plustek_pp] >option lampOff   -1<
[plustek_pp] Decoding option >lampOff<
[plustek_pp] ><
[plustek_pp] ># model override switch, mostly for cosmetic changes, if the autodetection<
[plustek_pp] ># does not work or could not work correctly<
[plustek_pp] >#option mov 7<
[plustek_pp] ><
[plustek_pp] >#<
[plustek_pp] ># example for accessing the scanner via libieee1284<
[plustek_pp] >#<
[plustek_pp] >[direct]<
[plustek_pp] >device parport0<
[plustek_pp] Decoding device name >parport0<
[plustek_pp] ><
[plustek_pp] >#<
[plustek_pp] ># example for accessing the scanner via the kernel module<
[plustek_pp] >#<
[plustek_pp] >#[kernel]<
[plustek_pp] >#device /dev/pt_drv<
[plustek_pp] >#<
[plustek_pp] >#option warmup    -1<
[plustek_pp] >#option lOffOnEnd -1<
[plustek_pp] >#option lampOff   -1<
[plustek_pp] attach (parport0, 0xbfff43e0, (nil))
[plustek_pp] Device configuration:
[plustek_pp] device name   : >parport0<
[plustek_pp] direct I/O    : yes
[plustek_pp] warmup        : -1s
[plustek_pp] lampOff       : -1
[plustek_pp] lampOffOnEnd  : yes
[plustek_pp] model override: 0
[plustek_pp] ---------------------
[plustek_pp] drvopen()
[plustek_pp] ptdrvInit(0)
[plustek_pp] Init settings done
[plustek_pp] ScanData = 0x08051a20
[plustek_pp] Assigning port handle 0
[plustek_pp] ptdrvOpen(port=0x0)
[plustek_pp] Try to claim the parport
[plustek_pp] Setting SPP-mode
[plustek_pp] Setting PS/2-mode
[plustek_pp] We're using libIEEE1284 I/O
[plustek_pp] Starting Scanner-Autodetection
[plustek_pp] ************ DETECTP48xx ************
[plustek_pp] ModelSet4800()
[plustek_pp] modelInitPageSettings()
[plustek_pp] A4 set
[plustek_pp] ModelSet4800() done.
[plustek_pp] P48xxInitAsic()
[plustek_pp] DacInitialize()
[plustek_pp] ImageInitialize()
[plustek_pp] IOFuncInitialize()
[plustek_pp] IOInitialize()
[plustek_pp] * using readfunction >fnBiDirRead<
[plustek_pp] MotorInitialize()
[plustek_pp] ResetPort()
[plustek_pp] Test 0x55
[plustek_pp] Test 0xAA
[plustek_pp] Compare data=0xc8 and status=0x8, port=0x0
[plustek_pp] p48xxReadWriteTest()
[plustek_pp] Found a 96001 ASIC at Reg 0x13
[plustek_pp] ModelSet4800()
[plustek_pp] modelInitPageSettings()
[plustek_pp] A4 set
[plustek_pp] ModelSet4800() done.
[plustek_pp] p48xxCheck4800Memory()
[plustek_pp] Error in memory test at pos 0 (0 != 255)
[plustek_pp] p48xxReadWriteTest()
[plustek_pp] Found a 96001 ASIC at Reg 0x13
[plustek_pp] ModelSet4800()
[plustek_pp] modelInitPageSettings()
[plustek_pp] A4 set
[plustek_pp] ModelSet4800() done.
[plustek_pp] p48xxCheck4800Memory()
[plustek_pp] Error in memory test at pos 0 (0 != 255)
[plustek_pp] p48xxReadWriteTest()
[plustek_pp] Found a 96001 ASIC at Reg 0x13
[plustek_pp] ModelSet4800()
[plustek_pp] modelInitPageSettings()
[plustek_pp] A4 set
[plustek_pp] ModelSet4800() done.
[plustek_pp] p48xxCheck4800Memory()
[plustek_pp] Error in memory test at pos 0 (0 != 255)
[plustek_pp] p48xxReadWriteTest()
[plustek_pp] Found a 96001 ASIC at Reg 0x13
[plustek_pp] ModelSet4800()
[plustek_pp] modelInitPageSettings()
[plustek_pp] A4 set
[plustek_pp] ModelSet4800() done.
[plustek_pp] p48xxCheck4800Memory()
[plustek_pp] Error in memory test at pos 0 (0 != 255)
[plustek_pp] p48xxReadWriteTest()
[plustek_pp] Found a 96001 ASIC at Reg 0x13
[plustek_pp] ModelSet4800()
[plustek_pp] modelInitPageSettings()
[plustek_pp] A4 set
[plustek_pp] ModelSet4800() done.
[plustek_pp] p48xxCheck4800Memory()
[plustek_pp] Error in memory test at pos 0 (0 != 255)
[plustek_pp] detectScannerConnection() returns -9020.
[plustek_pp] ************* ASIC9800x *************
[plustek_pp] ResetPort()
[plustek_pp] IOInitialize()
[plustek_pp] * using readfunction >fnBiDirRead<
[plustek_pp] ASIC = 0xF0
[plustek_pp] Unknown ASIC-ID
[plustek_pp] *** DETECTION DONE, result: -9020 ***
[plustek_pp] ptdrvClose()
[plustek_pp] MiscRestorePort()
[plustek_pp] Releasing parport
[plustek_pp] ptdrvShutdown()
[plustek_pp] cleanup device 0
[plustek_pp] open: PtDrvInit failed: -9020
[plustek_pp] open failed: -1
[plustek_pp] sane_get_devices (0xbfff6498, 0)

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).
[plustek_pp] sane_exit

Was mache ich nun falsch?

Für jede Hilfe dankbar,

Michael
 
OP
M

mp2

Newbie
Ich versuche gerade, sane neu zu kompilieren. Dabei habe ich die neueste sane-backends 1.0.14 runtergeladen und erstmal versucht, das kernel modul pt_drv zu kompilieren. Hat auch prima geklappt. Bloss laden kann ich ihn nicht:

Code:
vano:~ # modprobe pt_drv
FATAL: Error inserting pt_drv (/lib/modules/2.6.5-7.104-default/kernel/drivers/parport/pt_drv.ko): Unknown symbol in module, or unknown parameter (see dmesg)

dmesg liefert:

Code:
pt_drv: no version for "struct_module" found: kernel tainted.
pt_drv: unsupported module, tainting kernel.
pt_drv: Unknown symbol __floatdidf
pt_drv: Unknown symbol __gtdf2
pt_drv: Unknown symbol __floatsidf
pt_drv: Unknown symbol __ltdf2
pt_drv: Unknown symbol __fixunsdfsi
pt_drv: Unknown symbol __adddf3
pt_drv: Unknown symbol __fixdfsi
pt_drv: Unknown symbol __divdf3
pt_drv: Unknown symbol __muldf3
pt_drv: Unknown symbol __nedf2
pt_drv: Unknown symbol __fixdfdi
pt_drv: Unknown symbol __subdf3

Ich komme nicht weiter... ;-(

Michael
 
Hol Dir mal die aktuellste Version (daily snapshots):
http://www.sane-project.org/snapshots/

Da sollte das Problem behoben sein. Ich hab leider keinen
OP4800 mit nem 96001 ASIC hier und deshalb kann es schon
sein, dass die Userspace Variante versagt - sorry.
Aber als Kernelmodul sollte es gehen.

Viel Erfolg,
Gerhard
 
OP
M

mp2

Newbie
Habe das snapshot (2004-08-19) runtergeladen und versucht, das Modul zu kompilieren:

Code:
vano:~/sane-backends/doc/plustek # MakeModule.sh
This script will try and build a suitable kernel-module for your system.
If you'd like to make the module WITH debug output, restart this script
with as follows:
./MakeModule.sh DEBUG=y
Press <ENTER> to continue or <CTRL><C> to cancel.

Check for root - done.

Check for kernelversion:
Using makefile for kernel 2.6.x
Build-directory:
/root/sane-backends/doc/plustek/build
Removing build-directory - done.
Creating build-directory - done.

Linking source files - done.
Copying Makefile to build-directory - done.
Making the module...
make: Entering directory `/usr/src/linux-2.6.5-7.104-obj/i386/default'
make -C ../../../linux-2.6.5-7.104 O=../linux-2.6.5-7.104-obj/i386/default modules

WARNING: Symbol version dump /usr/src/linux-2.6.5-7.104-obj/i386/default/Module.symvers is  missing, modules will have CONFIG_MODVERSIONS disabled.

grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
  CC [M]  /root/sane-backends/doc/plustek/build/plustek-pp_dac.o
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
  CC [M]  /root/sane-backends/doc/plustek/build/plustek-pp_detect.o
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
  CC [M]  /root/sane-backends/doc/plustek/build/plustek-pp_genericio.o
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
  CC [M]  /root/sane-backends/doc/plustek/build/plustek-pp_image.o
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
  CC [M]  /root/sane-backends/doc/plustek/build/plustek-pp_map.o
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
  CC [M]  /root/sane-backends/doc/plustek/build/plustek-pp_misc.o
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
  CC [M]  /root/sane-backends/doc/plustek/build/plustek-pp_models.o
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
  CC [M]  /root/sane-backends/doc/plustek/build/plustek-pp_io.o
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
  CC [M]  /root/sane-backends/doc/plustek/build/plustek-pp_procfs.o
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
  CC [M]  /root/sane-backends/doc/plustek/build/plustek-pp_motor.o
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
  CC [M]  /root/sane-backends/doc/plustek/build/plustek-pp_p9636.o
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
  CC [M]  /root/sane-backends/doc/plustek/build/plustek-pp_ptdrv.o
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
  CC [M]  /root/sane-backends/doc/plustek/build/plustek-pp_scale.o
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
  CC [M]  /root/sane-backends/doc/plustek/build/plustek-pp_tpa.o
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
  CC [M]  /root/sane-backends/doc/plustek/build/plustek-pp_p48xx.o
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
  CC [M]  /root/sane-backends/doc/plustek/build/plustek-pp_p12.o
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
  CC [M]  /root/sane-backends/doc/plustek/build/plustek-pp_p12ccd.o
  LD [M]  /root/sane-backends/doc/plustek/build/pt_drv.o
  Building modules, stage 2.
  MODPOST
  CC      /root/sane-backends/doc/plustek/build/pt_drv.mod.o
  LD [M]  /root/sane-backends/doc/plustek/build/pt_drv.ko
make: Leaving directory `/usr/src/linux-2.6.5-7.104-obj/i386/default'
done.
Should I install the module?
Press <ENTER> to continue or <CTRL><C> to cancel.

Er hat also etwas rumgeschimpft, jedoch wurde das Modul erzeugt und installiert. Aber starten laden lässt es sich nicht, diesmal mit einer anderen Fehlermeldung:

Code:
vano:~/sane-backends/doc/plustek # modprobe pt_drv
FATAL: Error inserting pt_drv (/lib/modules/2.6.5-7.104-default/kernel/drivers/parport/pt_drv.ko): Kernel does not have module support

Nach dreimaligem "Ladeversuch" liefert dmesg folgendes:

Code:
pt_drv: unsupported module, tainting kernel.
pt_drv: Unknown symbol __floatdidf
pt_drv: Unknown symbol __gtdf2
pt_drv: Unknown symbol __floatsidf
pt_drv: Unknown symbol __ltdf2
pt_drv: Unknown symbol __fixunsdfsi
pt_drv: Unknown symbol __adddf3
pt_drv: Unknown symbol __fixdfsi
pt_drv: Unknown symbol __divdf3
pt_drv: Unknown symbol __muldf3
pt_drv: Unknown symbol __nedf2
pt_drv: Unknown symbol __fixdfdi
pt_drv: Unknown symbol __subdf3
pt_drv: unsupported module, tainting kernel.
pt_drv : driver version
pt_drv : no device(s) detected, (-9020)
pt_drv: unsupported module, tainting kernel.
pt_drv : driver version
pt_drv : no device(s) detected, (-9020)

Ich bin wohl zu blöd dafür... ;-(
 
mp2 schrieb:
...
Code:
Linking source files - done.
Copying Makefile to build-directory - done.
Making the module...
make: Entering directory `/usr/src/linux-2.6.5-7.104-obj/i386/default'
make -C ../../../linux-2.6.5-7.104 O=../linux-2.6.5-7.104-obj/i386/default modules

WARNING: Symbol version dump /usr/src/linux-2.6.5-7.104-obj/i386/default/Module.symvers is  missing, modules will have CONFIG_MODVERSIONS disabled.

grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
grep: /usr/src/linux-2.6.5-7.104/plustek_pp.c: No such file or directory
  CC [M]  /root/sane-backends/doc/plustek/build/plustek-pp_dac.o
.
.
.

Er hat also etwas rumgeschimpft, jedoch wurde das Modul erzeugt und installiert. Aber starten laden lässt es sich nicht, diesmal mit einer anderen Fehlermeldung:

Code:
vano:~/sane-backends/doc/plustek # modprobe pt_drv
FATAL: Error inserting pt_drv (/lib/modules/2.6.5-7.104-default/kernel/drivers/parport/pt_drv.ko): Kernel does not have module support

Nach dreimaligem "Ladeversuch" liefert dmesg folgendes:

Code:
pt_drv: unsupported module, tainting kernel.
pt_drv: Unknown symbol __floatdidf
pt_drv: Unknown symbol __gtdf2
pt_drv: Unknown symbol __floatsidf
pt_drv: Unknown symbol __ltdf2
pt_drv: Unknown symbol __fixunsdfsi
pt_drv: Unknown symbol __adddf3
pt_drv: Unknown symbol __fixdfsi
pt_drv: Unknown symbol __divdf3
pt_drv: Unknown symbol __muldf3
pt_drv: Unknown symbol __nedf2
pt_drv: Unknown symbol __fixdfdi
pt_drv: Unknown symbol __subdf3
pt_drv: unsupported module, tainting kernel.
pt_drv : driver version
pt_drv : no device(s) detected, (-9020)
pt_drv: unsupported module, tainting kernel.
pt_drv : driver version
pt_drv : no device(s) detected, (-9020)

Ich bin wohl zu blöd dafür... ;-(

das mit dem blöd lassen wir mal...
Ich glaube eher, dass Deine Kernelquellen nicht richtig konfiguriert sind.
Übrigens bringt er die seltsame Fehlermeldung, dass der Kernel keinen
Modulsupport beinhaltet, wenn der Treiber sich nicht laden lässt, also auch
dann, wenn er kein Device erkennt.

Also bitte mal den Kernel richtig konfigurieren und dann der Treiber mit
Debugmeldungen übersetzen und laden.

Grüsse,
Gerhard
 
OP
M

mp2

Newbie
Die Kernel-Quellen sind in Ordnung, habe gerade mal probeweise einen Kernel samt Modulen kompiliert.

Das Packet kernel-syms war (dummerweise) nicht installiert. Nach der Installation verschwindet erwartungsgemäß diese Fehlermeldung:

Code:
WARNING: Symbol version dump /usr/src/linux-2.6.5-7.104-obj/i386/default/Module.symvers is  missing, modules will have CONFIG_MODVERSIONS disabled.

Aber sonst bleibt alles beim alten. Das Laden ist nicht möglich bzw nicht erfolgreich.

Nach der Übersetzung des Moduls mit der DEBUG-Option findet man ähnliche Fehlermeldungen, wie beim Startversuch über libIEEE1284 bzw. direkten Paralelport-Zugriff:

dmesg:

Code:
pt_drv: unsupported module, tainting kernel.
*********************************************
pt_drv: init_module()
pt_drv : driver version
ProcFsInitialize()
ptdrvInit(0)
Init settings done
ScanData = 0xc366c000
Using fast I/O
Requested port at 0x378
misc_attach
Requested port (0x378) found
Port mode reported: (0x0047)
Port for device 0 registered
ptdrvOpen(port=0x378)
Try to claim the parport
parport-modi: SPP PS/2 EPP EPP(ECP) PS/2(ECP)
Using EPP-mode
Starting Scanner-Autodetection
************ DETECTP48xx ************
ModelSet4800()
modelInitPageSettings()
A4 set
ModelSet4800() done.
P48xxInitAsic()
DacInitialize()
ImageInitialize()
IOFuncInitialize()
IOInitialize()
* using readfunction >fnEPPRead<
MotorInitialize()
Dataport = 0x0378
Ctrlport = 0x037a
ResetPort()
Test 0x55
Test 0xAA
Compare data=0xd8 and status=0x8, port=0x378
p48xxReadWriteTest()
Found a 96001 ASIC at Reg 0x13
ModelSet4800()
modelInitPageSettings()
A4 set
ModelSet4800() done.
p48xxCheck4800Memory()
Error in memory test at pos 0 (0 != 255)
p48xxReadWriteTest()
Found a 96001 ASIC at Reg 0x13
ModelSet4800()
modelInitPageSettings()
A4 set
ModelSet4800() done.
p48xxCheck4800Memory()
Error in memory test at pos 0 (0 != 255)
p48xxReadWriteTest()
Found a 96001 ASIC at Reg 0x13
ModelSet4800()
modelInitPageSettings()
A4 set
ModelSet4800() done.
p48xxCheck4800Memory()
Error in memory test at pos 0 (0 != 255)
p48xxReadWriteTest()
Found a 96001 ASIC at Reg 0x13
ModelSet4800()
modelInitPageSettings()
A4 set
ModelSet4800() done.
p48xxCheck4800Memory()
Error in memory test at pos 0 (0 != 255)
p48xxReadWriteTest()
Found a 96001 ASIC at Reg 0x13
ModelSet4800()
modelInitPageSettings()
A4 set
ModelSet4800() done.
p48xxCheck4800Memory()
Error in memory test at pos 0 (0 != 255)
detectScannerConnection() returns -9020.
************* ASIC9800x *************
ResetPort()
IOInitialize()
* using readfunction >fnEPPRead<
ASIC = 0xF0
Unknown ASIC-ID
*** DETECTION DONE, result: -9020 ***
ptdrvClose()
MiscRestorePort()
- no need to restore portmode !
Releasing parport
ptdrvShutdown()
cleanup device 0
Port unregistered
misc_detach
ProcFsShutdown()
pt_drv: proc del 'info' root='pt_drv'
pt_drv: proc del 'pt_drv' root='/proc'
pt_drv : no device(s) detected, (-9020)
---------------------------------------------


Langsam glaube ich, dass der Scanner irgendwie eine Macke hat, obwohl er unter Win noch einigermassen funktioniert...

Gruß, Michael
 
Hi Michael,

das ganze Ärgernis sind die Parallelport-Einstellungen, bitte
unbedingt ECP abschalten:
Code:
parport-modi: SPP PS/2 EPP EPP(ECP) PS/2(ECP)

Desweiteren, solltest Du mal überprüfen, wie die Optionen
des parport Moduls sind, check mal /etc/modprobe.conf.
Evtl. solltest Du die Optionen mal setzen:
Code:
options parport_pc io=0x378 irq=none

Ich weiss jetzt nicht, welches MoBo du hast, aber gerade bei
VIA Chipsätzen gibt es immer wieder Ärger. Evtl. spielst Du auch
mal mit den Optionen des pt_drv herum, z.B.:
forceMode=1 oder 2
slowIO=1
Für eine genauere Beschreibung, siehe: man sane-plustek_pp

Wenn Du das Modul irgendwie dann geladen bekommts, kannst Du
auch mal wieder das Userspacebackend probieren.

Grüsse,
Gerhard
 
Oben