From owner-freebsd-hackers Mon Jan 16 19:30:35 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id TAA26407 for hackers-outgoing; Mon, 16 Jan 1995 19:30:35 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id TAA26398 for ; Mon, 16 Jan 1995 19:30:23 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id OAA23004; Tue, 17 Jan 1995 14:29:37 +1100 Date: Tue, 17 Jan 1995 14:29:37 +1100 From: Bruce Evans Message-Id: <199501170329.OAA23004@godzilla.zeta.org.au> To: freebsd-hackers@FreeBSD.org, j@uriah.sax.de Subject: Re: Colorado 250 Tape Drive Sender: hackers-owner@FreeBSD.org Precedence: bulk >| Next, make sure the device is configured into your kernel. By default >| it is disabled because it apparently causes problems with some peoples' >| systems. You will need to build a new kernel. Your config should have: >| >| disk fd0 at fdc0 drive 0 >| disk fd1 at fdc0 drive 1 >| tape ft0 at fdc0 drive 2 >| >| make sure this last line isn't commented out. >As far as i know, the fdc line in the config file does also need a >``flags 0x1'' clause (right after the `bio' keyword), otherwise the ft >probe will be skipped. History: ft0 was added to generic in case someone wants to install from ft0. This broke some systems without ft0. The correct way to fix this is to disable ft0 at (static) config time. However, there is no way to statically configure the device enable flag (it isn't in `flags' and config always sets it to 1). The 0x1 flag was hacked on instead. Bruce