On Saturday 21 June 2003 14:52, Henning Meier-Geinitz wrote:
> If I try to use the "ncr" driver instead of "sym", FreeBSD doesn't
> even boot. With a Tekram 315 controller the results are the same as
> above.
ncr driver is old, you should not use it. As far as I know, sym should
support everythi
On Friday 20 June 2003 20:51, abel deuring wrote:
> Great. I've already sent a patch to Martin, and it seems to fix the
> problems with the Microtek Scanamker II. Attached is the proposed new
> version (with Martin's fixes of my typos) of sanei_scsi_cmd2 for
> FreeBSD/CAM. It should replace the fu
On Wednesday 18 June 2003 19:30, you wrote:
> 0) None of this generation of Microtek scanners supports SCSI
> disconnect. Disconnect needs to be disabled for the scanner device
> (if not the whole bus), and you should expect the scanner to
> monopolize the entire bus during a scan.
I really don't
On Tuesday 17 June 2003 23:30, abel deuring wrote:
> First a disclaimer for the following stuff: I don't have FreeBSD
> installed, I used it only rarely, and I never wrote software
> specifically for FreeBSD. So I am writing as a "backseat driver" ;)
Try it :)
> I assume that you are using Fre
--Boundary-00=_ELz7+hd1IAGKfsJ
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On Tuesday 17 June 2003 00:16, abel deuring wrote:
> What I meant, was a combination of the log output of the Sane SCVSI
> library and of the Microtek backen
--Boundary-00=_bUj7+3jA47kNUKn
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On Monday 16 June 2003 21:16, abel deuring wrote:
> The first error occurs immediately after a "read", and this at least
> does not contradict my suspicions
--Boundary-00=_9TQ7++/s4/fNiZr
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On Sunday 15 June 2003 22:20, abel deuring wrote:
> IIRC, the delay between two scan passes is really long.
I don't think so. It always was working fast. Us
On Thursday 12 June 2003 12:10, abel deuring wrote:
> A long shot: IIRC, these Microtek scanners may freeze, if you access
> them with another LUN than 0 -- but they show up with all LUN values
> from 0 to 7. So, if any backend tries to access the scanner with a
> non-zero LUN, you'll have an unac
On Wednesday 11 June 2003 11:27, Henning Meier-Geinitz wrote:
> Looks like a SCSI problem (either hardware or kernel driver). My
> Mustek SCSI scanners work fine with FreeBSD/386 so I don't think there
> is a general bug in the SCSI code of SANE.
You might be right. I will check the cables and th
--Boundary-00=_Gsk5+USHsb9suHM
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Well, how to say... it doesn't work.
I compiled xsane-0.90 from ports. I tried to set 'norealcal' and/or
'noprecal'. The scanner always causes a timeout (s
10 matches
Mail list logo
