[sane-devel] canon_pp does not work
Frank DiPrete
fdiprete@comcast.net
Tue, 7 Sep 2004 13:32:00 -0400
HW = Dell Dimension 2400
Using FreeBSD 5.2.1,
Libieee1284 0.2.8 (compiled from source)
I've tried no port, ppi0, lpt0, 0x378, etc.
Taken the printer off the chain, etc.
tried force-nibble.
nada - no click no beep no lamp, nada
output from boot in messages:
ep 7 08:44:10 thurston kernel: ppc0 port 0x778-0x77f,0x378-0x37f irq 7
drq 1 on acpi0
Sep 7 08:44:10 thurston kernel: ppc0: SMC-like chipset (ECP/EPP/PS2/
NIBBLE) in COMPATIBLE mode
Sep 7 08:44:10 thurston kernel: ppc0: FIFO with 16/16/8 bytes
threshold
Sep 7 08:44:10 thurston kernel: ppbus0: <Parallel port bus> on ppc0
Sep 7 08:44:10 thurston kernel: lpt0: <Printer> on ppbus0
Sep 7 08:44:10 thurston kernel: lpt0: Interrupt-driven port
Sep 7 08:44:10 thurston kernel: ppi0: <Parallel I/O> on ppbus0
output of scan image:
[canon_pp] detect_mode: Opening port 0x378
[canon_pp] detect_mode: Claiming port.
[canon_pp] detect_mode: Port supports ECP-S.
[canon_pp] detect_mode: Using ECP-S Mode
[canon_pp] sane_init: >> initialise
[canon_pp] Scanner not ready (0xf). Attempting to reset...
[canon_pp] Timeout: Reset 2 response 1 (0x07 in 0x1f) - Status = 0x0f
[canon_pp] Timeout: Scanner wakeup reply 1 (0x03 in 0x1f) - Status =
0x0f
[canon_pp] Timeout: Scanner wakeup reply 2 (0x03 in 0x1f) - Status =
0x0f
[canon_pp] Timeout: Scanner wakeup reply 1 (0x03 in 0x1f) - Status =
0x0f
[canon_pp] Timeout: Scanner wakeup reply 2 (0x03 in 0x1f) - Status =
0x0f
[canon_pp] Timeout: Scanner wakeup reply 1 (0x03 in 0x1f) - Status =
0x0f
[canon_pp] Timeout: Scanner wakeup reply 2 (0x03 in 0x1f) - Status =
0x0f
[canon_pp] Timeout: Scanner wakeup reply 1 (0x03 in 0x1f) - Status =
0x0f
[canon_pp] Timeout: Scanner wakeup reply 2 (0x03 in 0x1f) - Status =
0x0f
[canon_pp] Timeout: Scanner wakeup reply 1 (0x03 in 0x1f) - Status =
0x0f
[canon_pp] Timeout: Reply 2 (0x0c in 0x1f) - Status = 0x0f
[canon_pp] initialise: could not wake scanner
[canon_pp] sane_init: << 1 initialise
[canon_pp] sane_init: Couldn't contact scanner on port 0x378. Probably
no scanner there?