d/freebsd-skq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update the current state of affairs with the AMI and Mylex drivers;

Browse Source 
they're usable but booting is not supported at this time.

Approved-by:	jkh
This commit is contained in:
msmith 2000-02-10 21:41:54 +00:00
parent e515e856f2
commit 6606faa5d7
2 changed files with 19 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
release/texts/HARDWARE.TXT
View File

@ -370,10 +370,13 @@ SmartRAID IV SCSI/RAID controllers are supported. The DPT SmartRAID/CACHE V
is not yet supported.
AMI MegaRAID Express and Enterprise family controllers (all models).
Booting from these controllers is not supported.
Mylex DAC960 controllers with 3.x and 4.x firmware, including the
P, PL, PJ, PG and PTL (AcceleRAID 250). Other AcceleRAID models may
function but have not been tested.
Mylex DAC960 and DAC1164 controllers with 3.x and 4.x firmware,
including the P, PL, PJ, PG and PTL (AcceleRAID 250). Other
AcceleRAID models may function but have not been tested. Booting from
these controllers is not supported, and enabling the controller BIOS may
cause the FreeBSD bootstrap to fail.
SymBios (formerly NCR) 53C810, 53C810a, 53C815, 53C820, 53C825a, 53C860,
53C875, 53C875e, 53C875j, 53C885, 53C895 and 53C896 PCI SCSI controllers:

13
release/texts/TROUBLE.TXT
View File

@ -384,5 +384,18 @@ A: There is a problem with the onboard Ethernet in the Netfinity 3500
will have to install another Ethernet adapter and avoid attempting
to configure the onboard adapter at any time.
Q: When I install to my Mylex RAID controller and reboot, I get a register
dump, or the system is extremely slow in booting.
A: Due to incompatibilities between the Mylex BIOS and the FreeBSD
bootloader, the Mylex BIOS must be disabled. This means that you
cannot boot from a RAID array at this time.
Q: When I install to my AMI RAID controller and reboot, the kernel
cannot mount root, even though the AMI controller was detected.
A: On some systems, the AMI controller doesn't work as the driver expects
when it has been booted from. This results in the array being
unreadable. The only current workaround is to boot from another disk.
[ Please send hardware tips for this Q&A section to jkh@freebsd.org ]