libieee1284 problems on FBSD 5.2.1 (was [sane-devel] canon_pp does not work)

Matthew Duggan stauff@guarana.org
Wed, 8 Sep 2004 09:05:30 +1000


On Tue, Sep 07, 2004 at 01:32:00PM -0400, Frank DiPrete wrote:
> 
> 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
> 
<scanimage output no response>

Hi,

Since there's been two independant reports of problems with parport
stuff on FreeBSD 5.2.1, it seems like there may be a problem with
FBSD 5.2.1 and the libieee1284 port.  I checked up the changelog to
see what might have caused it, and this line makes me suspicious:

---
The puc(4) PCI Universal Communications driver now supports connecting
parallel ports to the ppc(4) driver.
---
(http://www.freebsd.org/releases/5.2.1R/relnotes-i386.html)

It's quite possible that something to do with that is breaking the
direct access to the parallel port through /dev/io which libieee1284
performs.  Unfortunately I don't have a FBSD machine handy to test this
theory.. has anyone out there had any success in getting libieee1284
access on FBSD 5.2.1 working?

Cheers,

- Matthew Duggan