plustek: OP9636T memory failure?


Previous by date: 28 Oct 2001 13:55:01 -0000 OP9636T memory failure?, Alexander Runge
Next by date: 28 Oct 2001 13:55:01 -0000 Re: OP9636T memory failure?, Alexander Runge
Previous in thread: 28 Oct 2001 13:55:01 -0000 OP9636T memory failure?, Alexander Runge
Next in thread: 28 Oct 2001 13:55:01 -0000 Re: OP9636T memory failure?, Alexander Runge

Subject: Re: OP9636T memory failure?
From: "Jaeger, Gerhard" ####@####.####
Date: 28 Oct 2001 13:55:01 -0000
Message-Id: <01102815583202.01006@ruebennase>

Hi, 

this has in general nothing to do with the scanner memory. It's simply a 
read/write test to see if the driver can talk to the scanner - here it fails!
You might play around with BIOS settings (set it to plain SPP) or
remove the IEEE1284 stuff form your parport configuration.
If your printer is plugged to the scanner - remove it.

Can you tell me more about your HW config?
Gerhard

On Sunday, 28. October 2001 11:41, Alexander Runge wrote:
> Hi folks,
>
> I'm trying to get my Plustek OpticPro 9636T working under Linux 2.4.13
> (I also tried with 2.4.4).
>
> The sane-binaries and the module all built well as far as I can tell,
> but the module pt_drv won't load correctly :(
> I built the module with debug option and in the messages it reads:
>
> Oct 28 09:17:40 zappa kernel:
> *********************************************
> Oct 28 09:17:40 zappa kernel: pt_drv: init_module()
> Oct 28 09:17:40 zappa kernel: pt_drv : driver version 0.39-8
> Oct 28 09:17:40 zappa kernel: ProcFsInitialize()
> Oct 28 09:17:40 zappa kernel: ptdrvInit(0)
> Oct 28 09:17:40 zappa kernel: Init settings done
> Oct 28 09:17:40 zappa kernel: ScanData = 0xc0d54000
> Oct 28 09:17:40 zappa kernel: Using fast I/O
> Oct 28 09:17:40 zappa kernel: Requested port at 0x378
> Oct 28 09:17:40 zappa kernel: Requested port (0x378) found
> Oct 28 09:17:40 zappa kernel: Port mode reported: (0x0047)
> Oct 28 09:17:40 zappa kernel: Port for device 0 registered
> Oct 28 09:17:40 zappa kernel: ptdrvOpen(port=0x378)
> Oct 28 09:17:40 zappa kernel: Try to claim the parport
> Oct 28 09:17:40 zappa kernel: parport-modi: SPP PS/2 EPP EPP(ECP)
> PS/2(ECP)
> Oct 28 09:17:40 zappa kernel: Using EPP-mode
> Oct 28 09:17:40 zappa kernel: Starting Scanner-Autodetection
> Oct 28 09:17:40 zappa kernel: ************ DETECTP48xx ************
> Oct 28 09:17:40 zappa kernel: ModelSet4800()
> Oct 28 09:17:40 zappa kernel: modelInitPageSettings()
> Oct 28 09:17:40 zappa kernel: A4 set
> Oct 28 09:17:40 zappa kernel: ModelSet4800() done.
> Oct 28 09:17:40 zappa kernel: P48xxInitAsic()
> Oct 28 09:17:40 zappa kernel: DacInitialize()
> Oct 28 09:17:40 zappa kernel: ImageInitialize()
> Oct 28 09:17:40 zappa kernel: IOFuncInitialize()
> Oct 28 09:17:40 zappa kernel: IOInitialize()
> Oct 28 09:17:40 zappa kernel: MotorInitialize()
> Oct 28 09:17:40 zappa kernel: Dataport = 0x0378
> Oct 28 09:17:40 zappa kernel: Ctrlport = 0x037a
> Oct 28 09:17:40 zappa kernel: Test 0x55
> Oct 28 09:17:40 zappa kernel: Test 0xAA
> Oct 28 09:17:40 zappa kernel: Compare data=0x7f and status=0x5f,
> port=0x378
> Oct 28 09:17:40 zappa kernel: p48xxReadWriteTest()
> Oct 28 09:17:40 zappa kernel: Can't find your model, asic = 0x5a
> Oct 28 09:17:40 zappa kernel: detectScannerConnection() returns -9031.
> Oct 28 09:17:40 zappa kernel: ************* ASIC9800x *************
> Oct 28 09:17:40 zappa kernel: IOInitialize()
> Oct 28 09:17:40 zappa kernel: ASIC = 0x81
> Oct 28 09:17:40 zappa kernel: ************* ASIC98001 *************
> Oct 28 09:17:40 zappa kernel: ModelSet9636()
> Oct 28 09:17:40 zappa kernel: ModelSet9360()
> Oct 28 09:17:40 zappa kernel: modelInitPageSettings()
> Oct 28 09:17:40 zappa kernel: A4 set
> Oct 28 09:17:40 zappa kernel: modelInitPageSettings()
> Oct 28 09:17:40 zappa kernel: A4 set
> Oct 28 09:17:40 zappa kernel: ModelSet9630() done.
> Oct 28 09:17:40 zappa kernel: modelInitPageSettings()
> Oct 28 09:17:40 zappa kernel: A4 set
> Oct 28 09:17:40 zappa kernel: ModelSet9636() done.
> Oct 28 09:17:40 zappa kernel: P9636InitAsic()
> Oct 28 09:17:40 zappa kernel: DacInitialize()
> Oct 28 09:17:40 zappa kernel: ImageInitialize()
> Oct 28 09:17:40 zappa kernel: IOFuncInitialize()
> Oct 28 09:17:40 zappa kernel: IOInitialize()
> Oct 28 09:17:40 zappa kernel: MotorInitialize()
> Oct 28 09:17:40 zappa kernel: 0x81
> Oct 28 09:17:40 zappa kernel: CCID = 0x00
> Oct 28 09:17:40 zappa kernel: P9636InitAsic() done.
> Oct 28 09:17:40 zappa kernel: Dataport = 0x0378
> Oct 28 09:17:40 zappa kernel: Ctrlport = 0x037a
> Oct 28 09:17:40 zappa kernel: Test 0x55
> Oct 28 09:17:40 zappa kernel: Test 0xAA
> Oct 28 09:17:40 zappa kernel: Compare data=0x7f and status=0x1f,
> port=0x378
> Oct 28 09:17:40 zappa kernel: ioP98ReadWriteTest()
> Oct 28 09:17:40 zappa kernel: Error in memory test at pos 0 (0 != 255)
> Oct 28 09:17:40 zappa kernel: ioP98ReadWriteTest()
> Oct 28 09:17:40 zappa kernel: Error in memory test at pos 0 (0 != 255)
> Oct 28 09:17:40 zappa kernel: ioP98ReadWriteTest()
> Oct 28 09:17:40 zappa kernel: Error in memory test at pos 0 (0 != 255)
> Oct 28 09:17:40 zappa kernel: ioP98ReadWriteTest()
> Oct 28 09:17:40 zappa kernel: Error in memory test at pos 0 (0 != 255)
> Oct 28 09:17:40 zappa kernel: ioP98ReadWriteTest()
> Oct 28 09:17:40 zappa kernel: Error in memory test at pos 0 (0 != 255)
> Oct 28 09:17:40 zappa kernel: detectScannerConnection() returns -9020.
> Oct 28 09:17:40 zappa kernel: *** DETECTION DONE, result: -9020 ***
> Oct 28 09:17:40 zappa kernel: ptdrvClose()
> Oct 28 09:17:40 zappa kernel: MiscRestorePort()
> Oct 28 09:17:40 zappa kernel: - no need to restore portmode !
> Oct 28 09:17:40 zappa kernel: Releasing parport
> Oct 28 09:17:40 zappa kernel: ptdrvShutdown()
> Oct 28 09:17:40 zappa kernel: cleanup device 0
> Oct 28 09:17:40 zappa kernel: Port unregistered
> Oct 28 09:17:40 zappa kernel: ProcFsShutdown()
> Oct 28 09:17:40 zappa kernel: pt_drv: proc del 'info' root='pt_drv'
> Oct 28 09:17:40 zappa kernel: pt_drv: proc del 'pt_drv' root='/proc'
> Oct 28 09:17:40 zappa kernel: pt_drv : no device(s) detected, (-9020)
> Oct 28 09:17:40 zappa kernel:
> ---------------------------------------------
>
> Obviously the parport is found and setup correctly, and I can drive a
> printer on that port without any problems.
> I guess it has something to do with the memory test error message but
> I don't know what to do with this message.
> The scanner works really fine under Winblows so I would say that
> the scanner memory is OK. Any help appreciated.
>
>
> Regards, Alex!!!
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####

Previous by date: 28 Oct 2001 13:55:01 -0000 OP9636T memory failure?, Alexander Runge
Next by date: 28 Oct 2001 13:55:01 -0000 Re: OP9636T memory failure?, Alexander Runge
Previous in thread: 28 Oct 2001 13:55:01 -0000 OP9636T memory failure?, Alexander Runge
Next in thread: 28 Oct 2001 13:55:01 -0000 Re: OP9636T memory failure?, Alexander Runge


Powered by ezmlm-browse 0.20.