From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 15 10:40:02 2013 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 9476844F for ; Mon, 15 Apr 2013 10:40:02 +0000 (UTC) (envelope-from hps@bitfrost.no) Received: from mta.bitpro.no (mta.bitpro.no [92.42.64.202]) by mx1.freebsd.org (Postfix) with ESMTP id 5B489297 for ; Mon, 15 Apr 2013 10:40:02 +0000 (UTC) Received: from mail.bitfrost.no (mail.bitfrost.no [46.29.221.36]) by mta.bitpro.no (Postfix) with ESMTP id D50607A0FA; Mon, 15 Apr 2013 12:39:54 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at bitfrost.no Received: from laptop015.hselasky.homeunix.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: hanspetter) by mail.bitfrost.no (Postfix) with ESMTPSA id BCC0D2057B; Mon, 15 Apr 2013 12:39:49 +0200 (CEST) Message-ID: <516BD94F.7030507@bitfrost.no> Date: Mon, 15 Apr 2013 12:41:19 +0200 From: Hans Petter Selasky Organization: Bitfrost A/S MIME-Version: 1.0 To: Joshua Isom Subject: Re: USB Printer quirks References: <5169DFFB.4030101@gmail.com> In-Reply-To: <5169DFFB.4030101@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@FreeBSD.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Apr 2013 10:40:02 -0000 On 04/14/13 00:45, Joshua Isom wrote: > I've got my printer to finally work, now that I got around to hooking it > up again and trying. It's a Kodak AiO, and there's a driver that's been > around for a few years and works under Linux. It doesn't work properly > under FreeBSD, or a Debian/kFreeBSD jail, but does work under a Linux > jail. With FreeBSD, the best I'd get is one document and then need to > power cycle the printer to get it to do anything. From what I remember > of the logs, the communication wasn't coming back properly. Cups is > reporting it's not getting bidirectional communication, but it is mostly > printing properly. > > Since it works under the Linux jail, and not the Debian jail, I'm > assuming it has to be a FreeBSD kernel issue that's masked by the Linux > overhead. But where would I begin to troubleshoot the underlying issue? > Right now I'm running a -CURRENT kernel: > > FreeBSD jri.homeunix.com 10.0-CURRENT FreeBSD 10.0-CURRENT #15 r249169M: > Fri Apr 5 16:12:04 CDT 2013 > root@jri.homeunix.com:/usr/obj/root/ATH/head/sys/ATH amd64 > > Any help would be appreciated. Hi, What does dmesg say about your printer. Is cups hooked up the correct /dev/uxxx device ? --HPS