From owner-freebsd-scsi Sun Dec 10 11:05:10 1995 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA00394 for freebsd-scsi-outgoing; Sun, 10 Dec 1995 11:05:10 -0800 (PST) Received: from wiley.csusb.edu (wiley.csusb.edu [139.182.2.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA00388 for ; Sun, 10 Dec 1995 11:05:04 -0800 (PST) Received: (from rmallory@localhost) by wiley.csusb.edu (8.6.11/8.6.11) id LAA25763; Sun, 10 Dec 1995 11:07:59 -0800 From: Rob Mallory Message-Id: <199512101907.LAA25763@wiley.csusb.edu> Subject: Re: ncr[01] conflicts..? To: se@zpr.uni-koeln.de (Stefan Esser) Date: Sun, 10 Dec 1995 11:07:58 -0800 (PST) Cc: scsi@freebsd.org In-Reply-To: <199512092332.AA17178@Sysiphos> from "Stefan Esser" at Dec 10, 95 00:32:55 am X-Mailer: ELM [version 2.4 PL22] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk > > On Dec 8, 23:18, Rob Mallory wrote: > } Subject: ncr[01] conflicts..? > > } OK, I took the "easy" way out,,throw more hardware at it apporach:) > } > } I finaly found (through a tech at symbios) how to successfully get > } both a ncr825 and 810 in my asus p55tp4xe with 3.07 ncr bios. > } > } the tyan 825 had a 3.04 rom, complete with geometry bugs which > } prevented me from installing slowaris-2.5 and freebsd on the same disk. > } the tech suggested that the 810 be installed in a lower slot than the > } 825 so it booted first. the 825, now romless, would 'use' the 3.07 > } bios which was incarnated by the 810 from the asus bios. it follows > } that the 810 would have to contain the boot drive. > > Why can't you update both SDMS ROMs to the same > software release level ? I dont have an EEPROM on the 825. It's just more conveinent to u/g to the latest SDMS rev with a new MB bios upgrade. also, the 3.04 PROM I have won't drive the 810. (the tech seemed to know about this) > > I'd be surprised if the slot numbers would make > any difference with respect to which ROM is choosen. yup. they do. notice by me, and verified by a tech at symbios. I have to remove the rom, and put the 825 in slot2 (closer to the mediabus slot) and the 810 in slot1. no other way will work. the bios' step on each other.. the only thing to 'play' with at this point is the "2nd" jumper and the IRQ's in the asus pci bios setup. > > But I guess you made sure it works as advertised ? > (I.e.: Did the SDMS line show that the new BIOS > was in fact the one being used ?) yep. 3.07. if I leave the 3.04 rom in, with the 810 in slot1, I get a 'DISK BOOT FAILURE' as *no* SDMS bios is found. (they step all over each other) > > > There was a message with regard to a mixed 810/825 > system recently, and it claimed, that the BIOS did > always prefer the 810 as the "MAIN" controller, i.e. > no matter which slots the 810 and 825 are put into, > the 810 should always get the DOS drive C: ... > > This is different from what the BSD init code does: > The PCI bus is scanned from low to high bus numbers > and from low to high slot numbers, and controllers > are assigned to drivers in the order they are found. is there a hack that can be dropped in for 'reverse scan' of the pci-bus for FreeBSD? > > } well, this is where it gets fun. the 810 has a 2 way jumper on it that > } says '2nd'. it does what it implies, and moves its mem-base(?) somewhere > } else(i guess). see the following boot messages: > } > } (chopped up for readability) > } [conflicting with the 825] > } Dec 8 21:58:16 kickme /kernel: Probing for devices on the PCI bus: > } Dec 8 21:58:16 kickme /kernel: chip0 rev 1 on pci0:0 > } Dec 8 21:58:16 kickme /kernel: ncr0 rev 1 int a irq ?? on pci > } 0:6 > } Dec 8 21:58:16 kickme /kernel: pci_map_mem failed: device's memrange 0xff00-0xf > } fff is incompatible with its bridge's memrange 0x4000000-0xffffffff > > There is something wrong ... !!! > > The NCR seems to have been mapped into the memory range > of the last 256 bytes just below 64KB. > > This would be the fault of the BIOS. The FreeBSD PCI code > does currently respect these values, even if it considers > them badly choosen (and complains) ... My guess is that the '2nd' jumper tells the chip where to advertise itself.? one way it setps on the 825's memrange(above), and the other way works(below). > > * Could you please send **verbose** boot messages (obtained > * by booting with "-v" entered at the "Boot: " prompt). > * I need all lines starting at "pcibus_setup()" and until > * the final PCI ressource report. I'll send it in another message as not to clutter -scsi..:-) Let me build a newly sup'd current-kernel first... > > > } Dec 8 21:58:16 kickme /kernel: CACHE TEST FAILED: reg dstat-sstat2 readback fff > } fffff. > > This is a sign, that the NCR does not see the same data > as the CPU. That's not surprising, if the memory region > 0xff00 to 0xffff in fact has been assigned to the NCR's > registers. That region most likely is covered by a WB > secondary cache, and the NCR doesn't see the data written > before the corresponding cache lines get flushed to RAM. > > } Dec 8 21:58:16 kickme /kernel: CACHE INCORRECTLY CONFIGURED. > } Dec 8 21:58:16 kickme /kernel: chip1 rev 2 on pci0:7 > } Dec 8 21:58:16 kickme /kernel: vga0 rev 0 int a > } Dec 8 08:45:56 kickme /kernel: ncr1 rev 2 int a irq 11 o > } n pci0:11 > } Dec 8 08:45:56 kickme /kernel: (ncr1:0:0): "TOSHIBA MK537FB 6261" type 0 fixed > } Dec 8 08:45:57 kickme /kernel: sd0(ncr1:0:0): Direct-Access > } Dec 8 08:45:57 kickme /kernel: sd0(ncr1:0:0): FAST SCSI-2 100ns (10 Mb/sec) off > } > } ...boots off ncr(1), the 825, sd0. > > Does it in fact work, even though the cache test warned > about the lack of coherency ? ??? only the 825 works, even the bootblocks are read off the 825. I guess I could make a dos floppy with sdms and scsidisk.com on it and put my (only:) dos drive on the 810 and see what happens.. > > } [not conflicting boots off ncr1, but of course, the kernel says root on sd0] > } Dec 8 08:50:37 kickme /kernel: Probing for devices on the PCI bus: > } Dec 8 08:50:37 kickme /kernel: chip0 rev 1 on pci0:0 > } Dec 8 08:50:37 kickme /kernel: chip1 rev 2 on pci0:7 > } Dec 8 08:50:38 kickme /kernel: ncr0 rev 2 int a irq 11 o > } Dec 8 08:50:38 kickme /kernel: (ncr0:0:0): "TOSHIBA MK537FB 6261" type 0 fixed > } Dec 8 08:50:38 kickme /kernel: sd0(ncr0:0:0): Direct-Access > } ... > } Dec 8 08:50:40 kickme /kernel: ncr1 rev 1 int a irq 14 on pci > } 0:12 > } Dec 8 08:50:40 kickme /kernel: ncr1 waiting for scsi devices to settle > } Dec 8 08:50:40 kickme /kernel: (ncr1:0:0): "CONNER CFA540S 13B0" type 0 fixed S > } Dec 8 08:50:40 kickme /kernel: sd4(ncr1:0:0): Direct-Access > } Dec 8 08:50:40 kickme /kernel: sd4(ncr1:0:0): FAST SCSI-2 100ns (10 Mb/sec) off > } > } sd4 is a 2.1R disk which was probed by sdms at boot, and the bootblocks > } were read, a kernel read, and then tried to switch root to sd0. > > As I wrote above, the SDMS code will prefer the 810 as > the boot controller. FreeBSD doesn't, it sees the 825 on > PCI bus 0 slot 11 and the 810 on bus 0 slot 12 ... > > } i noticed how they switch posisions when i jumper the '2nd' jumper.. > > Do you know, what this "2nd" jumper is supposed to do ? > Does it just disable accesses to the cards BIOS ROM ? see my guess above. > > } my question is,, Why does the ncr probe look backwards to me? > } if the 810 is hooked first and booted, and the sd4 kernel is read that > } device, why does the kernel call the 810 ncr1? > > That's because FreeBSD finds it in the higher numbered > slot. the symbios tech said the SDMS will only look from low to high. and I would have to put my boot drives on the 810. I left his name/number at work, but I think his name was Gary something.. > > } ...has anyone else run into this? is there a valid reason for this > } being default? ...give me a 'FLIP_NCR_PROBE' option flag! :-) > > Hmmm, well, have you tried flipping the cards ? yup. only one combo works. see above. -- Rob Mallory From owner-freebsd-scsi Wed Dec 13 05:50:31 1995 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA09948 for freebsd-scsi-outgoing; Wed, 13 Dec 1995 05:50:31 -0800 (PST) Received: from motgate.mot.com (motgate.mot.com [129.188.136.100]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id FAA09943 for ; Wed, 13 Dec 1995 05:50:28 -0800 (PST) Received: from pobox.mot.com (pobox.mot.com [129.188.137.100]) by motgate.mot.com (8.7.1/8.6.10/MOT-3.8) with ESMTP id HAA16333 for ; Wed, 13 Dec 1995 07:49:56 -0600 (CST) Received: from shemp.ftw.paging.mot.com (shemp.ftw.paging.mot.com [180.18.128.201]) by pobox.mot.com (8.7.1/8.6.10/MOT-3.8) with ESMTP id HAA01002 for ; Wed, 13 Dec 1995 07:49:55 -0600 (CST) Received: from wmg13 by shemp.ftw.paging.mot.com (8.6.12/8.6.12) with ESMTP id HAA08324 for ; Wed, 13 Dec 1995 07:49:54 -0600 From: Jeff Kreska Received: by wmg13 (8.6.12/8.6.12) id HAA16356; Wed, 13 Dec 1995 07:49:54 -0600 Date: Wed, 13 Dec 1995 07:49:54 -0600 Message-Id: <199512131349.HAA16356@wmg13> To: freebsd-scsi@freebsd.org Subject: PD Disk and SCSI question Reply-To: jeff_kreska@pts.mot.com Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk For those of you who don't know what a PD disk is, it is a combination 4x CD-ROM and PD writer. You can format, re-format, and use it as a normal disk read/write disk drive. The drive itself uses 2 LUN, LUN 0 is PD LUN 1 is CD. The latest version of FreeBSD (2.1) recognizezs both LUN's. (Way to go) I have posted the question to the NetBSD camp about PD disk support, and one person responded by saying that in netbsd there were no changes neccessary to enable the PD disk. > There should be no patches required to the NetBSD > sd driver to recognise the PD drive. The sd driver recognises the following > inquiry patterns > > T_DIRECT, T_FIXED > T_DIRECT, T_REMOV > T_OPTICAL, T_FIXED > T_OPTICAL, T_REMOV > > (Taken from sys/scsi/sd.c) Does the FreeBSD driver have the same functionality in it??? -- Thanks, Jeff Kreska email: jeff_kreska@pts.mot.com X.400: FJK008@email.mot.com pager: 214 836-7416, 0578 internal phone: x52572 From owner-freebsd-scsi Fri Dec 15 05:58:31 1995 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA23726 for freebsd-scsi-outgoing; Fri, 15 Dec 1995 05:58:31 -0800 (PST) Received: from ncc-1701-d.starfleet.gov (root@ix-sb1-04.ix.netcom.com [204.32.201.36]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA23720 Fri, 15 Dec 1995 05:58:24 -0800 (PST) Received: (from d_burr@localhost) by ncc-1701-d.starfleet.gov (8.6.11/8.6.9) id GAA00989; Fri, 15 Dec 1995 06:00:10 -0800 Date: Fri, 15 Dec 1995 06:00:09 -0800 (PST) From: Donald Burr X-Sender: d_burr@ncc-1701-d To: FreeBSD Questions cc: FreeBSD SCSI Subject: question about Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk I'm running FreeBSD 2.1 on a 486/66 with VLB video board and ISA everything else, including a Adaptec 1542CP SCSI card with IBM 0662 hard drive (the main drive at ID 0) and Toshiba CD-ROM drive at ID 2. My SCSI devices are all setup properly, my bus is terminated at both ends, and everything is otherwise happy. System works great in DOS/Windows, OS/2, and Linux. Why does FreeBSD print "not ready", etc. for my CD-ROM, as evidenced by the following extract from dmesg: aha0 at 0x330-0x333 irq 11 drq 5 on isa (aha0:0:0): "IBM 0662S12 !O 2 23" type 0 fixed SCSI 2 sd0(aha0:0:0): Direct-Access 1003MB (2055035 512 byte sectors) sd0(aha0:0:0): with 4119 cyls, 5 heads, and an average 99 sectors/track (aha0:1:0): "SyQuest SQ3105S 2_10" type 0 removable SCSI 2 sd1(aha0:1:0): Direct-Access 105MB (215440 512 byte sectors) sd1(aha0:1:0): with 2060 cyls, 2 heads, and an average 52 sectors/track (aha0:2:0): "TOSHIBA CD-ROM XM-3501TA 2694" type 5 removable SCSI 2 cd0(aha0:2:0): CD-ROM cd0(aha0:2:0): NOT READY asc:4,1 cd0(aha0:2:0): Logical unit is in process of becoming ready can't get the size Despite these messages, though, the system works perfectly (including the CD-ROM). I always boot up with a CD-ROM stuck in the drive, if that makes a difference. I'm just curious why these messages are displayed, if they are an indication of something about to break, or if it's just one of those little quirks that people live with. Donald Burr [d_burr@ix.netcom.com], PO Box 91212, Santa Barbara CA 93190-1212 TEL (805)564-1871 / FAX 564-2315 / WWW http://www.geopages.com/WallStreet/2072 PGP Public Key available by request (send e-mail) or on Public Key Servers. ** Uphold your right to privacy - Use PGP. ** From owner-freebsd-scsi Fri Dec 15 10:35:40 1995 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA09850 for freebsd-scsi-outgoing; Fri, 15 Dec 1995 10:35:40 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA09837 Fri, 15 Dec 1995 10:35:35 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id FAA25465; Sat, 16 Dec 1995 05:31:03 +1100 Date: Sat, 16 Dec 1995 05:31:03 +1100 From: Bruce Evans Message-Id: <199512151831.FAA25465@godzilla.zeta.org.au> To: d_burr@ix.netcom.com, freebsd-questions@FreeBSD.ORG Subject: Re: question about Cc: freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk >Why does FreeBSD print "not ready", etc. for my CD-ROM, as evidenced by >the following extract from dmesg: Because the CD-ROM drive isn't ready :-). >... >(aha0:2:0): "TOSHIBA CD-ROM XM-3501TA 2694" type 5 removable SCSI 2 >cd0(aha0:2:0): CD-ROM >cd0(aha0:2:0): NOT READY asc:4,1 >cd0(aha0:2:0): Logical unit is in process of becoming ready >can't get the size >I'm just curious why these messages are displayed, if they are an >indication of something about to break, or if it's just one of those >little quirks that people live with. The driver resets the device (and/or the SCSI bus?) and some devices take a looong time to become ready. The device driver only waits a long time for SCSI devices to become ready. This is controlled by options SCSI_DELAY=nnn # nnn is 15 for GENERIC in the kernel config file. I use 8, which is this smallest value that avoids the above error message here. The drive LED indicator showed reliably when the drive was ready. Bruce From owner-freebsd-scsi Fri Dec 15 19:48:19 1995 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA12010 for freebsd-scsi-outgoing; Fri, 15 Dec 1995 19:48:19 -0800 (PST) Received: from io.org (io.org [142.77.70.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id TAA11991 Fri, 15 Dec 1995 19:48:14 -0800 (PST) Received: from mail.io.org (dyna-10.net8b.io.org [205.233.78.10]) by io.org (8.6.12/8.6.12) with SMTP id WAA08458; Fri, 15 Dec 1995 22:47:51 -0500 Date: Fri, 15 Dec 1995 22:47:51 -0500 Message-Id: <199512160347.WAA08458@io.org> X-Sender: scouch@io.org X-Mailer: Windows Eudora Light Version 1.5.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: freebsd-scsi@freebsd.org, freebsd-hardware@freebsd.org From: Stephen Couchman Subject: SCSI disk not being recognized Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk I am trying to install FreeBSD 2.0.5 from a Walnut Cove CD. When I try to partition my hard disk, I am told that the system cannot find it. I am using an Adaptec 2940 SCSI controller with a Fujitsu SCSI disk drive attached. This drive is found without a problem by MS-DOS, but not by BSD. Do I have to modify the kernel using boot: -c? How do I get BSD to recognize my SCSI hard disk (it is the only disk in my PCI system). Thanks -- Stephen ______________________________ Stephen Couchman | scouch@io.org From owner-freebsd-scsi Fri Dec 15 21:29:40 1995 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA18262 for freebsd-scsi-outgoing; Fri, 15 Dec 1995 21:29:40 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id VAA18235 Fri, 15 Dec 1995 21:29:34 -0800 (PST) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id QAA02480; Sun, 17 Dec 1995 16:01:36 +1030 From: Michael Smith Message-Id: <199512170531.QAA02480@genesis.atrad.adelaide.edu.au> Subject: Re: SCSI disk not being recognized To: scouch@io.org (Stephen Couchman) Date: Sun, 17 Dec 1995 16:01:36 +1030 (CST) Cc: freebsd-scsi@freebsd.org, freebsd-hardware@freebsd.org In-Reply-To: <199512160347.WAA08458@io.org> from "Stephen Couchman" at Dec 15, 95 10:47:51 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk Stephen Couchman stands accused of saying: > > I am trying to install FreeBSD 2.0.5 from a Walnut Cove CD. When I try to > partition my hard disk, I am told that the system cannot find it. Erosion is a wonderful thing, is it not? > I am using an Adaptec 2940 SCSI controller with a Fujitsu SCSI disk drive > attached. This drive is found without a problem by MS-DOS, but not by BSD. You are using an Adaptec 2940 "Ultra" which has a different PCI signature to the original 2940, and which is _not_ supported by FreeBSD 2.0.5. You will need to use WC's NQA exchange policy to get a copy of 2.1. > Stephen Couchman | scouch@io.org -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 041-122-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] "Who does BSD?" "We do Chucky, we do." [[ From owner-freebsd-scsi Fri Dec 15 21:31:24 1995 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA18349 for freebsd-scsi-outgoing; Fri, 15 Dec 1995 21:31:24 -0800 (PST) Received: from io.org (io.org [142.77.70.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA18338 for ; Fri, 15 Dec 1995 21:31:17 -0800 (PST) Received: from mail.io.org (dyna-20.net7e.io.org [204.92.52.20]) by io.org (8.6.12/8.6.12) with SMTP id AAA17463 for ; Sat, 16 Dec 1995 00:12:05 -0500 Date: Sat, 16 Dec 1995 00:12:05 -0500 Message-Id: <199512160512.AAA17463@io.org> X-Sender: scouch@io.org X-Mailer: Windows Eudora Light Version 1.5.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: freebsd-scsi@freebsd.org From: Stephen Couchman Subject: SCSI disk not being recognized Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk I have checked further and I suspect that my PCI Adaptec 2940 is not being found. The 'hardware' doc on the CD lists this controller as device type 'ahc0', but the system does not seem to check for that when it boots. Any help would be most appreciated. Thanks -- Stephen >Date: Fri, 15 Dec 1995 22:24:54 >To: questions@freebsd.org >From: Stephen Couchman >Subject: SCSI disk not being recognized > >I am trying to install FreeBSD 2.0.5 from a Walnut Cove CD. When I try to partition my hard disk, I am told that the system cannot find it. > >I am using an Adaptec 2940 SCSI controller with a Fujitsu SCSI disk drive attached. This drive is found without a problem by MS-DOS, but not by BSD. Do I have to modify the kernel using boot: -c? How do I get BSD to recognize my SCSI hard disk (it is the only disk in my PCI system). > >Thanks -- Stephen > ______________________________ Stephen Couchman | scouch@io.org From owner-freebsd-scsi Sat Dec 16 13:49:02 1995 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA03842 for freebsd-scsi-outgoing; Sat, 16 Dec 1995 13:49:02 -0800 (PST) Received: from io.org (io.org [142.77.70.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA03780 Sat, 16 Dec 1995 13:48:39 -0800 (PST) Received: from mail.io.org (dyna-19.net7e.io.org [204.92.52.19]) by io.org (8.6.12/8.6.12) with SMTP id QAA00525; Sat, 16 Dec 1995 16:48:13 -0500 Date: Sat, 16 Dec 1995 16:48:13 -0500 Message-Id: <199512162148.QAA00525@io.org> X-Sender: scouch@io.org X-Mailer: Windows Eudora Light Version 1.5.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Michael Smith From: Stephen Couchman Subject: Problem partitioning SCSI disk and creating filesystems Cc: freebsd-scsi@freebsd.org, freebsd-hardware@freebsd.org Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk Thanks for your help so far! While I am waiting for Walnut Cove to send me FreeBSD 2.1.0, I have downloaded the 2.1.0 install disk from www.freebsd.org to make sure that my hardware is recognized. After partitioning the hard disk (a small MS-DOS partition, and the rest for FreeBSD) and writing the info to disk, I ran into a problem labelling the partitions within the FreeBSD partition. After requesting that the install program allocate the space for the filesystems using defaults, I tried to write the info to my hard disk. The following errors came up: 1. Unable to swap to /dev/sd0s2b (this is/will be the swap filesystem) 2. Unable to make new root filesystem on /dev/rds0a Should I be attempting to write the filesystems at this point? Should I be waiting until a later point, i.e. after I have selected the installation media)? I can't reproceed past setting up the disks in any case, but I would like to be ready with working hardware once the CD ROM arrives. Thanks -- Stephen At 04:01 PM 12/17/95 +1030, Michael Smith wrote: >Stephen Couchman stands accused of saying: >> >> I am trying to install FreeBSD 2.0.5 from a Walnut Cove CD. When I try to >> partition my hard disk, I am told that the system cannot find it. > >Erosion is a wonderful thing, is it not? > >> I am using an Adaptec 2940 SCSI controller with a Fujitsu SCSI disk drive >> attached. This drive is found without a problem by MS-DOS, but not by BSD. > >You are using an Adaptec 2940 "Ultra" which has a different PCI signature to >the original 2940, and which is _not_ supported by FreeBSD 2.0.5. You will >need to use WC's NQA exchange policy to get a copy of 2.1. > >> Stephen Couchman | scouch@io.org > >-- >]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ >]] Genesis Software genesis@atrad.adelaide.edu.au [[ >]] High-speed data acquisition and (GSM mobile) 041-122-496 [[ >]] realtime instrument control (ph/fax) +61-8-267-3039 [[ >]] "Who does BSD?" "We do Chucky, we do." [[ > ______________________________ Stephen Couchman | scouch@io.org