On Sat, Nov 13, 1999 at 06:28:24PM +0100, Christoph wrote:
> Hi again!
>
> >Does the scanhead at least move a little bit? If so, then it might be
> >that the SCSI setup is wrong. In most cases the settings for
> >disconnect/reconnect cause this problem.
>
> Yes it does, but it seems like it moves the wrong direction.
> So what does it mean? Is it the aha152x driver?
This is normal behaviour. The device starts a color calibration scan
below the normal scan area.
> Meantime it I took the advice from Douglas and patched the kernel down to
> 2.2.5 but that didn't help ether.
> It seems like it takes longer to crash but it still crashes :-(
>
> >
> >If not, can you provide a trace with SANE_DEBUG_MICROTEK2 and
> >SANE_DEBUG_SANEI_SCSI set to 30 (although I fear that the last lines
> >of trace will be missing, if the system freezes).
>
> Just in case it is useful here are the last few lines before the crash:
>
> [microtek2] set_exposure: ms=0x8056f00
> [microtek2] scsi_send_gamma: pos=0x8067de8, size=8192, word=1, color=3
> [sanei_scsi] scsi_req_enter: entered 0x804eeb8
> [sanei_scsi] sanei_scsi_req_wait: waiting for 0x804eeb8
> [sanei_scsi] sanei_scsi.issue: 0x804eeb8
> [sanei_scsi] sanei_scsi_req_wait: read 36 bytes
> [microtek2] scsi_set_window: ms=0x8056f00, wnd=1
> [sanei_scsi] scsi_req_enter: entered 0x804eeb8
> [sanei_scsi] sanei_scsi_req_wait: waiting for 0x804eeb8
> [sanei_scsi] sanei_scsi.issue: 0x804eeb8
> [sanei_scsi] sanei_scsi_req_wait: read 36 bytes
> [microtek2] scsi_read_image_info: ms=0x8056f00
> [sanei_scsi] scsi_req_enter: entered 0x804eeb8
> [sanei_scsi] sanei_scsi_req_wait: waiting for 0x804eeb8
> [sanei_scsi] sanei_scsi.issue: 0x804eeb8
> [sanei_scsi] sanei_scsi_req_wait: read 52 bytes
> [microtek2] scsi_read_image_info: ppl=612, bpl=1842, lines=842, remain=1550964
> [microtek2] scsi_wait_for_image: ms=0x8056f00
> [microtek2] scsi_read_image_status: ms=0x8056f00
> [sanei_scsi] scsi_req_enter: entered 0x804eeb8
> [sanei_scsi] sanei_scsi_req_wait: waiting for 0x804eeb8
> [sanei_scsi] sanei_scsi.issue: 0x804eeb8
This means, that the host does not get an answer from the device. Did
you try to load the aha152x module with the parameters aha152x=0x140,10,7,1,1 ?
IRQ and IO port might vary on your system.
Bernd
-- Bernd Schroeder Email: mailto:bernd@aquila.muc.de PGP public key available: mailto:pgp@aquila.muc.de | Subject: send key
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com