From owner-freebsd-current Sat Jan 29 20:21:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 7495F14E1F for ; Sat, 29 Jan 2000 20:21:49 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA28556; Sat, 29 Jan 2000 20:21:33 -0800 (PST) (envelope-from dillon) Date: Sat, 29 Jan 2000 20:21:33 -0800 (PST) From: Matthew Dillon Message-Id: <200001300421.UAA28556@apollo.backplane.com> To: David Gilbert Cc: Peter Wemm , freebsd-current@FreeBSD.ORG Subject: Re: Printer fiascos. References: <14483.45082.151986.340011@trooper.velocet.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When the new parallel port stuff was put several months ago, my machine stopped working. I had to set flags to 0x40 to make it work again. Flags of 0x40 force the driver to use the most basic probes possible. It was put in because a number of people's machines stopped working. It looks like Peter removed the flags 0x40 in rev 1.228 of GENERIC on Jan 14. At the time I had an argument with the author who insisted that the correct way to force 'basic' probing of the printer was to set the flags field in GENERIC rather then make the default a basic probe. * Peter, the comment in your log message makes no mention of the reason * for removing the flags. If you did this by accident could you please * set the flags back to 0x40? Now, a huge number of changes have been made since the original problem was reported, so I could be puffing smoke here. I didn't see anything in the CVS logs, though, so I am assuming that the removal of the flags field was a mistake. David, try putting flags 0x40 back in and see if that fixes your problem. -Matt Matthew Dillon :Why is it that a properly functioning printer is such a moving target :in FreeBSD? : :I don't mean to be argumentative, but under 3.x, the magic cookie to :make printers work (it appeared to be a flow control problem) was to :change : :device ppc0 at isa? port? flags 0x40 net irq 7 : :to : :device ppc0 at isa? port? flags 0x40 tty irq 7 : :Now... I've upgraded to -CURRENT, and it has a much more serious :problem. The line now reads : :device ppc0 at isa? port? irq 7 : :... so I havn't tried putting net or tty in it, but I have a printer :with a particular problem --- it will often fail to pick up a sheet of :paper. I suspect that this sets the paper out sense line of the :parallel port (?). : :When this happens, the entire machine freezes until someone feeds the :printer --- the momment it starts printing again, the computer :unfreezes. : :Printer-port related things probe as: : :ppc0: at port 0x378-0x37f irq 7 on isa0 :ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode :ppbus0: IEEE1284 device found /NIBBLE/PS2/ECP :Probing for PnP devices on ppbus0: :ppbus0: PCL,MLC,PML :lpt0: on ppbus0 :lpt0: Interrupt-driven port :plip0: on ppbus0 :ppi0: on ppbus0 : :(I have tried putting the BIOS in different parallel port modes.) : :Dave. : :-- :============================================================================ :|David Gilbert, Velocet Communications. | Two things can only be | :|Mail: dgilbert@velocet.net | equal if and only if they | :|http://www.velocet.net/~dgilbert | are precisely opposite. | :=========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message