Date: Fri, 7 Nov 1997 10:20:36 -0500 (EST) From: David Gilbert <dgilbert@jaywon.pci.on.ca> To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: dgilbert@jaywon.pci.on.ca (David Gilbert), fbugs@jraynard.demon.co.uk (James Raynard), freebsd-bugs@FreeBSD.ORG Subject: Re: i386/4948: SCSI don't boot. Message-ID: <199711071520.KAA03502@repeat.pci.on.ca> In-Reply-To: <19971107085533.AG15207@uriah.heep.sax.de> References: <199711052330.PAA18225@hub.freebsd.org> <19971106231933.54562@jraynard.demon.co.uk> <199711070220.VAA12412@repeat.pci.on.ca> <19971107085533.AG15207@uriah.heep.sax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> "J" == J Wunsch <j@uriah.heep.sax.de> writes: J> As David Gilbert wrote: >> Since there are a number of devices that require fdisk partitions >> (a number of BIOS's require them as do newer 2940's), it would seem >> that this is really an area that should be addressed. 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. J> Btw., BSD/OS must suffer the same problems, they also know a mode J> that's comparable to our DD mode (and i was planning to make our J> kernel recognize their drives). 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. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199711071520.KAA03502>