Date: Wed, 31 Jan 1996 10:10:16 +0100 (MET) From: J Wunsch <j@uriah.heep.sax.de> To: shad@iastate.edu Cc: freebsd-scsi@freebsd.org Subject: Re: 2.1.0 find Adaptec 1740, but not my drives Message-ID: <199601310910.KAA19915@uriah.heep.sax.de> In-Reply-To: <8E193B3023@CCELAB.IASTATE.EDU> from "Marcus I. Ryan" at Jan 30, 96 09:25:15 pm
next in thread | previous in thread | raw e-mail | index | archive | help
As Marcus I. Ryan wrote: > > ahb0: reading board settings, int=11 > ahb0 at 0x6000-0x60ff irq 11 on eisa slot 6 > ahb0 waiting for scsi devices to settle [ahb driver fails to find any devices] Ah, yup, sorry, i have been confusing this... > BIOS Geometries: > 0:019e3f20 0xx414=415 cylinders, 0..63=64 heads, 1..32=32 sectors > 1:019e3f20 0xx414=415 cylinders, 0..63=64 heads, 1..32=32 sectors > 2:03e23f20 0xx994=995 cylinders, 0..63=64 heads, 1..32=32 sectors The above is really the BIOS geometry, i.e. it lists the drives as reported by the BIOS vectors. Alas, the ahb driver failed to probe the devices... ok, now i'm also remembering the real problem. Ok, i've widened the scope of this reply to freebsd-scsi, i ran out of ideas. The only question is, i know that several things have been changing on the EISA front meanwhile. There should be an (unofficial) 2.2-SNAP available somewhere on freefall. Perhaps you could give its boot floppy try and see whether the driver there would see your drives? Anybody else here? Julian? Do you have an idea why the AHA17xx driver sees the adapter, but fails to find the drives? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199601310910.KAA19915>