From owner-freebsd-current Fri Jan 1 11:16:34 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12524 for freebsd-current-outgoing; Fri, 1 Jan 1999 11:16:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA12519 for ; Fri, 1 Jan 1999 11:16:32 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.221]) by smtp02.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA6781; Fri, 1 Jan 1999 20:16:08 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19981229003351.05206@breizh.prism.uvsq.fr> Date: Fri, 01 Jan 1999 20:23:04 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Nicolas Souchu Subject: Re: ZIP driver Cc: FreeBSD Current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry for the late reply, HD died, new year's eve, etc... On 29-Dec-98 Nicolas Souchu wrote: > On Mon, Dec 28, 1998 at 10:20:46PM +0100, Jeroen Ruigrok/Asmodai wrote: >> >>while we're on the subject, whatever did happen with the ZIP(+) driver? >> >>Somewhere along the line of commits did it break and unfortunately I only >>noticed >>this when I needed it... >> >>The boot reports all the devices getting probed alright, except for da2 which >>was >>normally my ZIP drive (and yes, it's on and has a disk in it ;) >> > > ZIP is detected, then no da? You have generic chipset? Aye, think so... ppc: parallel port found at 0x378 ppc0 at 0x378 irq 7 on isa ppc0: W83877F chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode nlpt0: on ppbus 0 nlpt0: Interrupt-driven port ppi0: on ppbus 0 The parallel port is set to EPP. controller pnp0 controller isa0 controller pci0 controller ahc0 controller scbus0 controller ppbus0 controller vpo0 at ppbus? device nlpt0 at ppbus? device ppi0 at ppbus? device ppc0 at isa? port ? tty irq 7 vector ppcintr > Try 0x40 as 'ppc' boot flags. This avoids specific detection code that may > break your hardware. Hmmm, it appears that more people have problems, see SCSI list mails last couple of days... --- Jeroen Ruigrok van der Werven Life is the only Pain asmodai(at)wxs.nl we endeavour... Network/Security Specialist BSD & picoBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message