From owner-freebsd-bugs Fri Nov 7 10:56:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA16515 for bugs-outgoing; Fri, 7 Nov 1997 10:56:57 -0800 (PST) (envelope-from owner-freebsd-bugs) Received: from george.arc.nasa.gov (george.arc.nasa.gov [128.102.194.142]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA16510 for ; Fri, 7 Nov 1997 10:56:55 -0800 (PST) (envelope-from lamaster@george.arc.nasa.gov) From: lamaster@george.arc.nasa.gov Received: (from lamaster@localhost) by george.arc.nasa.gov (8.8.7/8.8.7) id KAA23714 for freebsd-bugs@FreeBSD.ORG; Fri, 7 Nov 1997 10:54:44 -0800 (PST) Date: Fri, 7 Nov 1997 10:54:44 -0800 (PST) Message-Id: <199711071854.KAA23714@george.arc.nasa.gov> To: freebsd-bugs@FreeBSD.ORG Subject: Re: i386/4948: SCSI don't boot. Sender: owner-freebsd-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk |> J> Even Adaptec? That's stupid of them. People, send bug reports to |> J> your BIOS vendors. By now, i've only seen it on HP systems |> J> (Netserver and Vectra), but they ship with a hacked BIOS anyway. I have to say, with all the BIOS-related irritations I have seen people report, I'm happy that the two systems I use at the moment have Award BIOSes. I'm sure they have their problems, too, but, I haven't noticed it. |> 6-8 months ago, I came across a 2940UW that wouldn't boot |> BSD/OS because of this problem. According to BSDI, this was known to |> be the new standard for 2940's. Sounds like a good reason to use an NCR/Symbios controller. I've used an old 53c810-based ASUS for some time off and on with no problems. Do the newer controllers (e.g. 875-based) seem to work well out there? Is tagged queueing working (totally) on the 53c8xx-based controllers?