Date: Wed, 4 Nov 1998 16:06:23 -0500 From: "Larry S. Marso" <larry@marso.com> To: "Justin T. Gibbs" <gibbs@narnia.plutotech.com> Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: 3.0-Release breaks pt0 (scanner) working under Aug. current Message-ID: <19981104160622.B5920@marso.com> In-Reply-To: <199811041837.LAA24907@narnia.plutotech.com>; from Justin T. Gibbs on Wed, Nov 04, 1998 at 11:37:16AM -0700 References: <19981104130400.A5152@marso.com> <199811041837.LAA24907@narnia.plutotech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>From the manual, configuring xvscan involves the following:
////////
The FreeBSD version of XVScan uses the `pt' (processor type) device
driver in your kernel.
XVScan looks for the scanner on /dev/scanjet. On FreeBSD systems, this
should be a copy of the appropriate /dev/pt[0-9] device:
Note: FreeBSD SYSTEMS ONLY
freebsd# ls -l /dev/pt[0-9]
crw------- 1 root wheel 61, 0 Jan 13 10:48 /dev/pt0
crw------- 2 root wheel 61, 1 Jan 13 10:48 /dev/pt1
crw------- 1 root wheel 61, 2 Jan 13 10:48 /dev/pt2
freebsd# mknod /dev/scanjet c 61 0
freebsd# chmod 666 /dev/scanjet
freebsd# ls -l /dev/scanjet
crw-rw-rw- 1 root wheel 61, 1 Jan 13 10:48 scanjet
Note that the /dev/scanjet device is readable and writable by everyone.
Scanner users will require read and write permissions to this device
file.
///////
this done, pre-CAM, you get the following output from the Install script:
//////
This ScanJet device file already exists... not created
/dev/scanjet: Vendor: 'HP ' Product: 'C2520A' Type: 3 (Scanner)
Successfully opened scanner device '/dev/pt0'
/dev/pt0: Vendor: 'HP ' Product: 'C2520A' Type: 3 (Scanner)
//////
After installing 3.0-release, I get:
//////
Device on '/dev/scanjet' is not an HP.
Found ' |Ø¿ï'.
Scanner device disabled to prevent possible overwrite.
/dev/scanjet: Vendor: '' Product: '|Ø¿ï' Type: 2
*** Device file was NOT created
//////
On Wed, Nov 04, 1998 at 11:37:16AM -0700, Justin T. Gibbs wrote:
> In article <19981104130400.A5152@marso.com> you wrote:
> > I just upgraded from an August 3.0-current (non-CAMed) to 3.0-Release
> > (CAMed).
> >
> > I run xvscan to operate my HP ScanJet 6100C using the /dev/pt0 driver,
> > which works great on the August 3.0-current system.
> >
> > However, on 3.0-Release, the software doesn't recognize the scanner on
> > /dev/pt0.
>
> What does, "doesn't recognize" mean? It can't open the device? I/O
> to the device fails?
>
> The software interface to /dev/pt0 did not change with CAM, but several
> other interfaces of the SCSI subsystem did change and perhaps xvscan
> needs to be taught about these changes.
>
> --
> Justin
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-scsi" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19981104160622.B5920>