Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.eng.convex.com!newshost.convex.com!bcm.tmc.edu!pendragon!ames!elroy.jpl.nasa.gov!usc!news.cerf.net!gde.GDEsystems.COM!gde.GDEsystems.COM!not-for-mail
From: sparkstp@gde.GDEsystems.COM (Timothy P. Sparks)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Need help with AHA-2940
Date: 10 Jul 1996 12:20:15 -0700
Organization: GDESystems Inc.
Lines: 46
Message-ID: <4s0vpf$snh@gde.GDEsystems.COM>
References: <31DD3662.41C67EA6@nap.net> <4rjt2s$53r@hamilton.maths.tcd.ie> <Du4pu4.HuH@alisa.org> <31E3D64E.41C67EA6@nap.net>
NNTP-Posting-Host: gde
In article <31E3D64E.41C67EA6@nap.net>, Joseph T. Klein <jtk@nap.net> wrote:
>John J. Rushford wrote:
>>
>> David Malone (dwmalone@maths.tcd.ie) wrote:
>> : "Joseph T. Klein" <jtk@nap.net> writes:
>>
>> : >If anyone has gotten an AHA-2940 working with FreeBSD please
>> : >tell me how.
>>
>> Mine, AHA-2940, worked fine right out of the box. Never had DOS on any of
>
>It looks like some chipsets do not work well. I took the problemic cards out
>of a system with an ALI chipset w/Award BIOS and put them in a Triton chipset
>board >w/Award BIOS and it worked like a champ.
Well I have a generic motherboard with the Triton II chipset, Genuine Intel,
and Award BIOS and I still can't get the dang thing(AHA-2940UW) to load the
system....even with the 2.2 snap. Oh sure, it boots the boot floppy and lets
me go through the entire install menu. But do a "commit" and the system gives
an error message or Panics and then rolls over and dies. Is there some
specific configuration that I need to set up on the SCSI card? Something I
need to disable or enable?
I've seen a few comments here about "disabling the cache". Is this referring
to the cache on the motherboard? Do I need to try this? I've also seen
comments about the memory or chipset being defective. The memory is a pair
of 72 pin 8M simms w/o parity. Is this a problem? I don't have access to
any other memory chips at the moment and I'd rather not spend any more money
on additional parts until I find out why the current stuff isn't working. I
bought the hardware that I have based on the "supported hardware" listed in
HARDWARE.TXT. I can't even take the stuff back now because I've been trying
to get it to work for the past month exceeding even the 30 day return policy.
I would greatly appreciate some more specific things to try besides "It may
be your chipset or memory..." Are there more detailed troubleshooting
procedures besides what's in the "Install.TXT". That basically says re-read
Install.Txt.
Please forgive my rant.....I've been working on this thing every night after
work into the wee hours for over a month now and I'm a little frustrated.
:-/
--
Tim Sparks * Logical And Uncle Sam
sparkstp@gdesystems.com * Intelligent doesn't want to hear
* Efficient about any LIES!!!!
* Supportable