From owner-freebsd-current Sun Jun 21 22:43:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA20187 for freebsd-current-outgoing; Sun, 21 Jun 1998 22:43:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles314.castles.com [208.214.167.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA20181 for ; Sun, 21 Jun 1998 22:43:35 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id VAA03590; Sun, 21 Jun 1998 21:38:34 -0700 (PDT) Message-Id: <199806220438.VAA03590@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Matthew D. Fuller" cc: current@FreeBSD.ORG Subject: Re: ZIP drive, just for a change In-reply-to: Your message of "Thu, 18 Jun 1998 23:12:26 CDT." <19980618231226.63579@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 21 Jun 1998 21:38:33 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Any idea what these messages on bootup mean? -current from a few days > ago, but I've seen them before, too: > ppc0 at 0x378 irq 7 on isa > ppc0: SMC FDC37C665GT chipset in ECP mode > ppi0: on ppbus 0 > vpo0: on ppbus 0 > scbus0 at vpo0 bus 0 > vpoio_outstr(): unknown transfer mode (6)! > vpoio_outstr(): unknown transfer mode (6)! > vpoio_outstr(): unknown transfer mode (6)! Is the Zip working? It looks like the vpo driver isn't grokking some of the transfer modes that are offered by the ppbus. There are updates coming in this area soon, so unless you're hurting, you might just want to ignore this. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message