hello, i apologize for previous threading. the problem is that the FreeBSD boot images (kern, mfsroot) do not see da0 and da1. this results in a 'disks not found' error in sysinstall. some background: the machine is a newly delivered Dell Precision 620. the scsi controller is an Adaptec AIC-7899, and there are two Quantum 10k RPM 17.4GB disks (specifically, Quantum model ATLAS10K2-TY184L) on it, as well as a tape backup drive (ARCHIVE Python 06240-XXX, Revision 8071). i had thought before that the issue may have something to do with RAID, so i've deleted the arrays that the machine shipped with and am just using the disks as standalone devices. i have also done a low-level format on each disk, as suggested in a previous message to freebsd-hardware. all this results in the same thing: the boot kernel detects the controller as ahc0, but fails to detect any disks. i decided to try booting a slackware 7 cdrom to see if it had similar problems (kernel version 2.2.13), and it sees everything without issue (tape, scsi controller, scsi disks). this also works when the disks are part of a RAID0 array, as defined in the utility shipped with the machine... for these reasons i've narrowed it down to the boot images. previous posts to freebsd-current have suggested that these controllers work fine under 4.0-STABLE, and at reduced capacity under 4.0-RELEASE. as another test, i booted the latest floppy images from the 20000626 5.0-STABLE branch, with the same result: controller found, disks not. does anyone else have this problem with the boot images, or is it just me? i am thinking that since linux 2.2.13 sees everything, the hardware configuration is ok... unless it has to be configured a specific way to jive with FreeBSD? i'm stumped... any insight is very very greatly appreciated. thank you. adam To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
