[sane-devel] canon_pp on FreeBSD 5-STABLE

[Rob Pollock]

Hi,

I am trying to set up my scanner to work via my old laptop on which I
have installed
FreeBSD 5-STABLE (started with 5.3, then cvsuped source and rebuilt).

I am running sane-backends 1.0.15 and trying to get it to work with a canon 640P
scanner.

This is what I get when I run scanimage (as root btw)

[sanei_debug] Setting debug level of canon_pp to 4.
[canon_pp] >> sane_init(0xbfbf6770, 0x8049200): sane-backends 1.0.15
[canon_pp] sane_init: >> ieee1284_find_ports
[canon_pp] sane_init: 0 << ieee1284_find_ports
[canon_pp] >> init_device
[canon_pp] << init_device
[canon_pp] >> init_device
[canon_pp] << init_device
[canon_pp] >> init_device
[canon_pp] << init_device
[canon_pp] detect_mode: Port supports ECP-S.
[canon_pp] sane_init: >> initialise
[canon_pp] sane_init: << 1 initialise
[canon_pp] detect_mode: Port supports ECP-S.
[canon_pp] sane_init: >> initialise
[canon_pp] sane_init: << 1 initialise
[canon_pp] detect_mode: Port supports ECP-S.
[canon_pp] sane_init: >> initialise
[canon_pp] sane_init: << 1 initialise
[canon_pp] << sane_init
[canon_pp] >> sane_get_devices (0xbfbf67a4, 0)
[canon_pp] << sane_get_devices
scanimage: no SANE devices found
[canon_pp] >> sane_exit
[canon_pp] << sane_exit

This is very strange, it's exactly the same as when the device isn't
plugged in (and
it _is_ plugged in, I checked), or in fact when it isn't even
connected to the parallel port.

The port/scanner itself works fine, under Windows no problemo.  The
settings from Windows' device manager are:
ECP printer port; IRQ 07; I/O 0x0378-0x037B; DMA 0

dmesg under FreeBSD shows:

ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/8 bytes threshold
ppbus0: <Parallel port bus> on ppc0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0

libieee1284 is installed, if you run the test utility you get:

Found 3 ports:
  0x278: 
  0x378: 
  0x3bc: 

0x278: 0x278
  RAW NIBBLE BYTE COMPAT ECPSWE 
0x378: 0x378
  RAW NIBBLE BYTE COMPAT ECPSWE 
0x3bc: 0x3bc
  RAW NIBBLE BYTE COMPAT ECPSWE 

I'm not sure what might be happening, although it >COULD< be a kernel
configuration issue.  Is there some SCSI driver I need to compile into
the kernel or something to make things work??  I also haven't
configured the kernel for PLIP, though I wouldn't expect that would
matter (but perhaps it does??)

Anyway, I am really quite keen to get this working, anyone able to help out??

Thanks heaps,

Rob Pollock.