I think I tried that one, but it did not work. I still have that flag standing. Now that is a long time ago, and this could be done without rebooting the server. dmesg: ppc0: using extended I/O port range ppc0: ECP SPP ECP+EPP SPP ppc0 port 0x778-0x77b,0x378-0x37b irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: <Parallel port bus> on ppc0 ppbus0: IEEE1284 device found /NIBBLE/ECP/NIBBLE_ID/ECP_ID/Extensibility Link Probing for PnP devices on ppbus0: ppbus0: <Hewlett-Packard HP LaserJet 2100 Series> PJL,MLC,PCL,PCLXL,POSTSCRIPT lpt0: <Printer> on ppbus0 lpt0: Interrupt-driven port I'll give it a shot for the next reboot. Major difference I see is that you've got the device on isa0 whereas mine is on acpi0 --WjW Ian FREISLICH wrote: >Willem Jan Withagen wrote: > > >>I've uped the limit for what the max of interrupts could be.... >>In /etc/sysctl.conf >>hw.intr_storm_threshold=20000 >> >>Bit I've seen my lpt intr go as high as 60.000 >> >> > >Why not force ECP? > >/boot/device.hints: hint.ppc.0.flags="0x8" > >ppc0: <Parallel port> at port 0x378-0x37f irq 7 flags 0x8 on isa0 >ppc0: SMC-like chipset (ECP-only) in ECP mode >ppc0: FIFO with 16/16/16 bytes threshold >ppbus0: <Parallel port bus> on ppc0 >lpt0: <Printer> on ppbus0 >lpt0: Interrupt-driven port > >Ian > >-- >Ian Freislich > > >Received on Fri Sep 10 2004 - 07:25:59 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:11 UTC