Hello,
I have a Microtek Phantom 636 scanner, which came with Adaptec AVA-1505AE
SCSI controller. I'm trying to make it work under Linux 2.2.12, using
the aha152x driver, with the following configuration in the Makefile:
-DDEBUG_AHA152X -DSKIP_BIOSTEST -DSETUP0="{ 0x140, 9, 7, 0, 0, 0, 100, 0 }"
(jumper set for I/O address 0x140, IRQ 9 set and ISA PnP disabled using
the Adaptec DOS program 1505acfg.exe).
The SCSI controller and the scanner are detected by the kernel, but when
I try to scan something (using "scanimage" from sane-1.0.1), the scanner
makes some noises, then the machine freezes until power to the scanner
is turned off. Fortunately, the lockup was with interrupts enabled, so
Alt-ScrollLock worked, and the EIP reported is inside the make_acklow()
function in aha152x.c.
Looking through the code, I found a few more places where busy looping is
used without calling schedule() to let other processes run, and without
any timeout to break out of the loop. Now, I'd like to know if it really
has to be done that way - not a good idea in a multitasking OS...
Is this really a cheaply designed Win-SCSI-controller hardware limitation,
and I should better get a real (PCI) SCSI controller? NT 4.0 freezes the
mouse pointer during scanning too (but only for short moments, not whole
duration of scan), but I still hope Linux can do better than that even on
such limited hardware.
Or maybe there is a better/updated driver available outside the standard
kernel? As I can see from the changelog, the driver in the kernel was
last updated in 1996...
(BTW, 1505acfg.exe allows setting DMA disabled/5/6/7 in addition to IRQ.
It is currently set to disabled, but maybe it is possible to make it work
more efficiently in DMA mode?)
Any help would be appreciated. Thanks!
Marek
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
