snip...
snip, snip...
> >kurt,
> >I had the same problem. Loaded 2.1.6 from ftp.freebsd.org and all is OK.
> Here's what I've found with an AHA2940AU.
> On cold boot, devices are scanned correctly.
> On warm boot or reset, devices are not found.
> Just what is the difference between the 2940U and 2940AU anyway? This
> cold boot versus warm boot thing isn't so bad but it will make it a
> pain to remotely reboot a server.
> --
> I have seen this problem many times over the years. Some pieces of iron
> need a hardware reset signal to be *truly* reset. Soft reset does not cut it.
> I therefore never trust anything but a hard reset from the front of the machine.
> --
snip, snip...
Well now here is some more funny stuff (and I'm laughing). I've attached
an Iomega Jaz SCSI drive. The AHA2940AU has term=autoterm, 2 IBM drives
scsi ids 0 and 1 on the internal chain, id 1 is the last and has
term=on.
Jaz is on the external chain, term=auto and Windows NT3.51 boots just
fine,
happy as a pig in.
BUT, FreeBSD gets SCSISIGI errors. So to boot FreeBSD, set AHA2940AU to
term=disabled, set JAZ term=OFF and FreeBSD boots OK and so does NT.
I've made a filesystem on the Jaz and have used it for backups, not bad.
NOW, power the whole lot off, wait a few minutes, power up and all is
still OK.
BUT power down and wait 'till the next morning (or a few hours)
and now the AHA2049AU can't boot from any devices but it can see them
because
I can verify media. So we play the "power up/down disconnect/connect the
Jaz
combination" shuffle until something works. Its never the same
combination.
Is there a capacitor in there that takes a few hours to discharge ?
--
regards, taras
==========================================
Taras M. Dowhaluk
VisionDB Pty Ltd
Sydney, Australia
http://www.visiondb.com.au
==========================================
by