Hi Peter,
Thanks for replying to my email. I really cannot find what I'm doing
wrong. I've added an extract from the /var/log/messages file. These
messages appear directly after the start of xscanimage (with or without
any options specified, it does not matter), just before it segfaults.
Mar 31 21:31:49 Drizzt kernel: sym53c876-0-<3,*>: target did not report
SYNC.
Mar 31 21:31:52 Drizzt kernel: sym53c876-0-<6,*>: asynchronous.
I've also added the /proc/scsi/scsi file, so you can see what's where :
Attached devices:
Host: scsi0 Channel: 00 Id: 03 Lun: 00
Vendor: HP Model: C5110A Rev: 3701
Type: Processor ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 04 Lun: 00
Vendor: IOMEGA Model: ZIP 100 Rev: J.03
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 06 Lun: 00
Vendor: HP Model: C1533A Rev: 9608
Type: Sequential-Access ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 04 Lun: 00
Vendor: PLEXTOR Model: CD-ROM PX-40TS Rev: 1.10
Type: CD-ROM ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 05 Lun: 00
Vendor: PHILIPS Model: CDD3600 CD-R/RW Rev: 2.00
Type: CD-ROM ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 06 Lun: 00
Vendor: IBM Model: DDRS-39130D Rev: DC1G
Type: Direct-Access ANSI SCSI revision: 02
You can find the output generated by hpinq in the attached file
(hpinq.out). It seems to work normally, that's the odd thing.
The output from the find-scanner tool also suggests that the scanner can
be found by sane....
find-scanner: found processor "HP C5110A 3701" at device /dev/scanner
find-scanner: found processor "HP C5110A 3701" at device /dev/sg0
find-scanner: found processor "HP C5110A 3701" at device /dev/sga
Another odd thing I found (I don't know if it's related), is when I run
the scsi_info tool on /dev/sga. The result is the following :
SCSI_ID="0,3,0"
MODEL="Direct-A "
FW_REV="SCSI"
That should say something like what can be found in the /proc/scsi/scsi
file as far as I know, which would make me expect that model would be
C5110A instead of Direct-A .....
Thanks so far.
Rogier
Peter Kirchgessner wrote:
>
> Hi Rogier,
>
> dou you get any other messages before the segmentation fault ? At what
> action do you get it ? Start of xscanimage, start of preview scan ?
> If you can run the hpinq-tool, the communication with the scanner should
> be ok.
>
> Rogier Stam wrote:
> >
> > Hi,
> >
> > Has anybody seen this problem before ? I have been trying to get the
> > Symbios Logic 22801 Dual channel controller with the HP Scanjet 5P on
> > channel 0 to work. All I get when I start xscanimage or scanimage is
> > that I got a Segmentation Fault. When I look during boot time I can see
> > that the kernel can find the Scanner, as can the find-scanner tool and
> > the hpinq tool. I also get a target did not report SYNC message in my
> > /var/log/messages file.
> >
> > I'm using kernel 2.2.13, but the problem also occurs on 2.2.14, 2.2.3,
> > 2.2.5 and 2.2.9 so I don't think that's the problem. Should it help, the
> > linux distribution I'm using is Slackware 7.0. I'm currently using sane
> > v1.02, but the problem also occurs on sane v1.01. I'm currently using
> > the Symbios SCSI driver, but the problem also occurs when using the
> > NCR8XX SCSI driver in the kernel.
> >
> > I've checked cable lengths and termination, and it should not cause any
> > problems.....
> >
> > I hope you can help me.
> >
> > Regards,
> >
> > Rogier Stam
> >
> > --
> > Source code, list archive, and docs: http://www.mostang.com/sane/
> > To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
>
> --
> Peter Kirchgessner
> WWW: http://www.kirchgessner.net
> e-mail: peter@kirchgessner.net
>
> --
> Source code, list archive, and docs: http://www.mostang.com/sane/
> To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
This archive was generated by hypermail 2b29 : Fri Mar 31 2000 - 12:48:44 PST