From owner-freebsd-questions@FreeBSD.ORG Tue Apr 12 10:16:45 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D418A16A4CE for ; Tue, 12 Apr 2005 10:16:45 +0000 (GMT) Received: from smtp-out3.blueyonder.co.uk (smtp-out3.blueyonder.co.uk [195.188.213.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 90B6043D4C for ; Tue, 12 Apr 2005 10:16:44 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [82.41.37.55] ([82.41.37.55]) by smtp-out3.blueyonder.co.uk with Microsoft SMTPSVC(5.0.2195.6713); Tue, 12 Apr 2005 11:17:21 +0100 Message-ID: <425BA00B.3020708@dial.pipex.com> Date: Tue, 12 Apr 2005 11:16:43 +0100 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7) Gecko/20040627 X-Accept-Language: en, en-us MIME-Version: 1.0 To: "Anthony M. Agelastos" References: <3d4917d89fcf710e1ada055cb7bd4de9@asu.edu> <200504102131.10222.mistry.7@osu.edu> <8d0f92b05cef4867d7500aa684121b3a@asu.edu> <867jj9bz0v.fsf@nowhere.org> <20050411065750.GA61757@slackbox.xs4all.nl> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 12 Apr 2005 10:17:21.0889 (UTC) FILETIME=[D08AF510:01C53F48] cc: freebsd-questions@freebsd.org Subject: Re: Very slow printing with stock FreeBSD5.3 + CUPS + Gimp-Print + HPDeskJet612C X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Apr 2005 10:16:45 -0000 Anthony M. Agelastos wrote: > It appears that "0x28" fixed the problem. Thank you to all who have > contributed to this thread. > > Out of curiosity, now that the solution is known, what was the problem > and what is the fix doing to solve it? The "problem" is that your printer port was being driven by interrupts and this was somehow not working -- the interrupts storm message you reported. I can't tell you the why, except that it's happened to me on several PCs. I regularly turn off interrupts on the ppc in the BIOS as well, just be very sure. Why did your fix work? Because you have instructed the port to not use interrupts. Re-read the ppc man page until it makes sense. If you don't know what an interrupt is, then try finding a book on PC hardware or search google. I'm sure there's a wiki or something out there somewhere -- there usually is :) --Alex