From owner-freebsd-hardware Wed Oct 1 07:39:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA17103 for hardware-outgoing; Wed, 1 Oct 1997 07:39:57 -0700 (PDT) Received: from rfd1.oit.umass.edu (mailhub.oit.umass.edu [128.119.175.4]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA17096; Wed, 1 Oct 1997 07:39:52 -0700 (PDT) Received: from wilde.oit.umass.edu by rfd1.oit.umass.edu (PMDF V5.1-10 #20973) with ESMTP id <0EHD005O7NEAQM@rfd1.oit.umass.edu>; Wed, 1 Oct 1997 10:39:46 -0400 (EDT) Received: from localhost (gp@localhost) by wilde.oit.umass.edu (8.8.3/8.8.6) with SMTP id KAA06757; Wed, 01 Oct 1997 10:39:45 -0400 (EDT) Date: Wed, 01 Oct 1997 10:39:45 -0400 (EDT) From: Greg Pavelcak Subject: Re: ppbus problem In-reply-to: <199710011255.IAA00667@tower.my.domain> To: hardware@FreeBSD.ORG Cc: questions@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > From: User Gp > > > > > > I 'm trying to install the ppbus stuff for my parallel port > > > zip drive. The kernel compiled OK, and it has a lot to say > > > about the drive, but fdisk and mount produce no results. > > > Here's dmesg. Any ideas. > > > > Can you be more specific about "no results"? Error messages? System > > lockup? > > No error messages, it just sits doing nothing, i.e. no indication (sound or > lights of disk activity in the zip. I bring my prompt back with ^C. > > > > > > ppc0 at 0x278 irq 7 on isa > > > ppc0: Generic chipset in PS/2 mode > > > plip0: on ppbus 0 > > > ppi0: on ppbus 0 > > > vpo0: on ppbus 0 > > > scbus0 at vpo0 bus 0 > > > sd0 at scbus0 target 6 lun 0 > > > sd0: type 0 removable SCSI 2 > > > sd0: Direct-Access > > > sd0: UNIT ATTENTION asc:28,0 > > > sd0: Not ready to ready transition, medium may have changed > > > 862MB (196608 4592 byte sectors) > > > vpo0: on ppbus 0 > > > scbus1 at vpo0 bus 0 > > > sd1 at scbus1 target 6 lun 0 > > > sd1: type 0 removable SCSI 2 > > > sd1: Direct-Access > > > sd1: ILLEGAL REQUEST asc:24,0 Invalid field in CDB > > > sd1 could not mode sense (4). Using ficticious geometry > > > 96MB (196608 512 byte sectors) > > > > Actually, this looks pretty ugly; you appear to have detected the vpo0 > > device twice. Do you have one Zip or two connected? > > > > mike > > To follow up, I have one zip, but I had vpo.c in both /sys/conf/files and /sys/i386/conf/files.i386 and their related directories (DOn't ask me how.). Now I only have vpo.c in /sys/i386/conf/files.i386, and there's some improvement. Now I only get the probe results for the 96MB Zip. fdisk still hangs though. Should I be using some of those flags in my kernel? I don't quite understand those. Thanks. Greg