From owner-freebsd-stable Sat Dec 18 12:55:45 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.eclipse.net (mail.eclipse.net [207.207.192.13]) by hub.freebsd.org (Postfix) with ESMTP id BEE7A14FB8; Sat, 18 Dec 1999 12:55:41 -0800 (PST) (envelope-from spiffer@eclipse.net) Received: from phil1-02-175.eclipse.net (phil1-02-175.eclipse.net [207.207.238.175]) by mail.eclipse.net (8.9.1a/8.9.1) with ESMTP id PAA23150; Sat, 18 Dec 1999 15:55:39 -0500 (EST) Date: Sat, 18 Dec 1999 15:39:26 -0500 (EST) From: "Roger W." X-Sender: spiffer@deepthought.invalid To: Mike Smith Cc: freebsd-stable@FreeBSD.org Subject: Re: printer problems using 3.4RC kernel In-Reply-To: <199912130135.RAA04626@mass.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry I wasn't able to respond sooner to this Mike, I was called away on business suddenly and couldn't get my emails. After hacking with this for a number of hours today, I was able to determine what was causing the problem with my kernel configuration file. The line: pseudo-device tun 1 #Packet Filtering I had #'d out this line, and it was the cause of all my problems, so the problem, was as usual, PEBKAC. I had a feeling it was in my configuration and not the kernel, but was centering my attention in parallel port area. Thank you for the help, Roger On Sun, 12 Dec 1999, Mike Smith wrote: > > You're not clear about what you're printing, where you're printing it to, > or what the actual output looks like, but these symptoms are entirely > consistent with you trying to print plain text or some other encoding to > the printer. You need to ensure that you're actually printing to the > correct printer device. > > > > Hello everyone, > > > > I've just finished cvsup'ing 3.3-stable, to bring my 3.3-Release system up > > to date. Everything went fine and seems to be working except for my laser > > jet printer. Its a NEC SuperScript 870 which emulates to a HPLJ IIP. The > > printer gets recognized fine during bootup and everthing appears to be OK > > until I try to send roughly more than 1 page of data to it. The page can > > be sent by cat 'filename' | lpr, using a2ps, or just dumping from a > > webpage with html, it doesn't seem to matter. What happens is I only get > > a small amout of data on each page, and then the next page is sucked into > > the printer and again only a small amount of data is placed on it. I am > > using apsfilter as the printers textfilter. > > > > I compared my boot logs with the new kernel to the GENERIC 3.3R kernel I > > was using previously, and there isn't a bit of difference in them. All I > > did was eliminate devices that weren't getting found anyways. I'm sure it > > has to do with the kernel, or its config, as if I boot off my old GENERIC > > kernel my printer functions properly. > > > > The one thing I've noticed is when the printer is working correctly, there > > is significantly more delay from when I send the printjob to the printer, > > and when it starts printing. Booting off of the kernel I compiled, there > > is almost no delay between when I tell the system to print, and when the > > printer starts to suck in the paper and print out small portions of what > > it should be printing spread out over many pages. > > > > If anyone else is seeing this problem and has any ideas, I would love to > > hear them. > > > > thank you, > > > > Roger > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message