On Tue, 07 May 2002, Douglas Gilbert wrote:
> Carsten Neumann wrote:
> > On Mon, 06 May 2002, Douglas Gilbert wrote:
> >
> >>Johan,
> >>In your kernel config (assuming you have built that kernel)
> >>turn off CONFIG_SCSI_MULTI_LUN . Some SCSI scanners don't
> >>react properly to being probed for l
A big thanks to both Ray Curtis and Carsten Neumann.
I recompiled the kernel with the MULTI_LUN off and that has done the trick.
The scanner now works beautifully, and is about 20% faster than under windows
using the Microtek Twain Driver, no lockups and the colour output is fine
despite readin
Sorry, did forget to say what the problem is with this setup.
Currently whenever I try to scan , whether from the comand line or from
xscanimage or using the KDE3 scan utility I hear the scanner move for a
couple of seconds then I get a total system freeze , no coredump or any other
messages , j
Carsten Neumann wrote:
> On Mon, 06 May 2002, Douglas Gilbert wrote:
>
>>Johan,
>>In your kernel config (assuming you have built that kernel)
>>turn off CONFIG_SCSI_MULTI_LUN . Some SCSI scanners don't
>>react properly to being probed for logical unit numbers (luns).
>>They should only respond to
On Monday 06 May 2002 10:45 am, Carsten Neumann wrote:
>On Mon, 06 May 2002, Douglas Gilbert wrote:
>> Johan,
>> In your kernel config (assuming you have built that kernel)
>> turn off CONFIG_SCSI_MULTI_LUN . Some SCSI scanners don't
>> react properly to being probed for logical unit numbers
>> (lu
> I think from looking at the listing below it is pretty obvious that
> the scsi card is detecting muliple scanners, at ID 1 Lun 00-07.
agreed
> Not being familiar with this scsi card I can't really help much
> except the suggest moving the ID from 1 to maybe 4 or 5. The lower
This won't do much
On Mon, 06 May 2002, Johan Wehtje wrote:
> Sorry, did forget to say what the problem is with this setup.
> Currently whenever I try to scan , whether from the comand line or from
> xscanimage or using the KDE3 scan utility I hear the scanner move for a
> couple of seconds then I get a total syste
On Mon, 06 May 2002, Douglas Gilbert wrote:
> Johan,
> In your kernel config (assuming you have built that kernel)
> turn off CONFIG_SCSI_MULTI_LUN . Some SCSI scanners don't
> react properly to being probed for logical unit numbers (luns).
> They should only respond to lun==0 but they respond to a
On Mon, May 06, 2002 at 10:05:29PM +1200, V K wrote:
> > I think from looking at the listing below it is pretty obvious that
> > the scsi card is detecting muliple scanners, at ID 1 Lun 00-07.
>
> agreed
>
> > Not being familiar with this scsi card I can't really help much
> > except the suggest
have read the docs as well as the SCSI 2.4 how to but am still none the
wiser as to why I get the following output from sane-find-scanner
===
sane-find-scanner: found SCSI scanner " Scanner 1.40" at device /dev/scanner
sane-find-scanner: found SCSI scanner
> "jw" == Johan Wehtje writes:
jw> Sorry, did forget to say what the problem is with this setup.
jw> Currently whenever I try to scan , whether from the comand line or from
jw> xscanimage or using the KDE3 scan utility I hear the scanner move for a
jw> couple of seconds then
Johan Wehtje wrote:
> have read the docs as well as the SCSI 2.4 how to but am still none the
> wiser as to why I get the following output from sane-find-scanner
> ===
> sane-find-scanner: found SCSI scanner " Scanner 1.40" at device /dev/scanner
> sane-fin
Hi, Johan,
you've missed to tell what your problems actually are!
I don't see any problem why you can't use your scanner.
But you haven't told that you cannot use it.
What are the errors you get, if there are any?
Carsten
On Mon, 06 May 2002, Johan Wehtje wrote:
> have read the docs as
> "cn" == Carsten Neumann writes:
cn> Hi, Johan,
cn> you've missed to tell what your problems actually are!
cn> I don't see any problem why you can't use your scanner.
cn> But you haven't told that you cannot use it.
cn> What are the errors you get, if there are any?
14 matches
Mail list logo
