From owner-freebsd-questions@FreeBSD.ORG Fri Mar 19 10:56:00 2004 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 131AD16A4CE for ; Fri, 19 Mar 2004 10:56:00 -0800 (PST) Received: from shockwave.systems.pipex.net (shockwave.systems.pipex.net [62.241.160.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3BF7643D4C for ; Fri, 19 Mar 2004 10:55:59 -0800 (PST) (envelope-from mark.cullen@dsl.pipex.com) Received: from ape (81-178-227-136.dsl.pipex.com [81.178.227.136]) by shockwave.systems.pipex.net (Postfix) with SMTP id F0C581C00223 for ; Fri, 19 Mar 2004 18:55:56 +0000 (GMT) Message-ID: <003101c40de3$c8ed7900$f700000a@ape> From: "Markie" To: Date: Fri, 19 Mar 2004 18:55:42 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Subject: lpt0 stopped working after upgrading 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: Fri, 19 Mar 2004 18:56:00 -0000 Hello, I recently upgraded to the latest -CURRENT and afterwards my printer would no longer print over Samba via CUPS. At first I thought it was a CUPS/Samba problem so I deinstalled and recompiled both of those but the problem still remains. CUPS recieves the print jobs ok and tries to print but in the web interface it says something along the lines of "parallel port busy, retrying in 30 seconds..." and indeed trying echo hello > /dev/lpt0 says device busy. I deleted the printer from CUPS yesterday to discover that lpt0 is no longer in the drop down list where you select where the printer is attached (serial 0 and 1, parallel etc). I have unplugged the printer lead and tried too and I get the same device busy, but maybe that's supposed to happen if there's nothing plugged in? Also on boot the printer gets recognised properly with the lead in. I have also tried disabling ACPI in BIOS as I read somewhere that this may solve the problem, but it's the same :o) Can anyone help me? Should I post this to the current list instead? Thanks