Bug 26277
| Summary: | ppc driver doesn't work with port 0x3BC printer port | ||
|---|---|---|---|
| Product: | Base System | Reporter: | aa8vb <aa8vb> |
| Component: | kern | Assignee: | freebsd-bugs (Nobody) <bugs> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | CC: | aa8vb |
| Priority: | Normal | ||
| Version: | 4.2-RELEASE | ||
| Hardware: | Any | ||
| OS: | Any | ||
State Changed From-To: open->feedback Does this still occur with more recent releases? It does sound like a hardware conflict or misconfiguration rather than a driver bug though. State Changed From-To: feedback->closed Mail to submitter bounces. |
ppc driver works if parallel port is configured on: port 0x378, interrupt 7, ECP+EPP mode Does not work if configured as port 0x3BC, interrupt 7, ECP+EPP mode Fix: Fix not known. Can't use a 0x3BC printer port. Workaround is reconfigure hardware (if possible) to move the printer port to another port range. How-To-Repeat: Set printer to port 0x3BC, interrupt 7, ECP+EPP mode in BIOS, and configure kernel as: device ppc0 at isa? port 0x3BC irq 7 device ppbus device lpt Boot probes yield: ppc0: <Parallel port> at port 0x3bc-0x3bf irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode lpt0: <Printer> on ppbus0 lpt0: Interrupt-driven port even with the printer on. Booting FreeBSD results in a spurious page ejected from the printer, and all attempts to print result in "/dev/lpt0: Device busy". However, move the BIOS printer port to 0x378 and reconfig the kernel with 0x378: device ppc0 at isa? port 0x378 irq 7 device ppbus device lpt and the boot probes and printing tests show that the parallel port works fine: ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppbus0: IEEE1284 device found /NIBBLE Probing for PnP devices on ppbus0: ppbus0: <Hewlett-Packard HP LaserJet 4P> HP ENHANCED PCL5,PJL lpt0: <Printer> on ppbus0 lpt0: Interrupt-driven port I'm reasonably sure this is not a port conflict because 3.4-RELEASE (what I just upgraded from) works fine with the printer port on 0x3BC with the same interrupt and printer capability configuration.