Date: Thu, 2 Oct 1997 13:34:32 +0000 From: Nicolas Souchu <Nicolas.Souchu@prism.uvsq.fr> To: hardware@FreeBSD.ORG Subject: Re: ppbus problem Message-ID: <19971002133432.18047@coreff.prism.uvsq.fr> In-Reply-To: <Pine.OSF.3.96.971001103317.13007A-100000@wilde.oit.umass.edu>; from Greg Pavelcak on Wed, Oct 01, 1997 at 10:39:45AM -0400 References: <199710011255.IAA00667@tower.my.domain> <Pine.OSF.3.96.971001103317.13007A-100000@wilde.oit.umass.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Oct 01, 1997 at 10:39:45AM -0400, Greg Pavelcak wrote: >> > > From: User Gp <gp@tower.my.domain> >> > > >> > > 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. Then, you do not have the message "device not configured" from sd0 driver? >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. > Ok, is there a way for you to get the name of your parallel port chipset? Which release of ppbus-dist did you get? September's? You may try to set boot flags to 0x1 to get NIBBLE operating mode. -- Nicolas.Souchu@prism.uvsq.fr FreeBSD - Turning PC's into workstations - http://www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19971002133432.18047>