AHA2842 controller doesn't work anymore?

[Mike Isely]

I would be happy to test the driver for you.  Or if there's any
experiments you'd like to try, let me know.  The machine is at home (away
from where I am during the day), however every evening I can try things
out, if it will help you find the problem.

One thing I failed to make clear is that I'm talking about the Linux
variant of the driver, not the *BSD version (forgetting that this list
covers more than just Linux).

  -Mike


On Wed, 5 Apr 2000, Doug Ledford wrote:

> Mike Isely wrote:
> > 
> > Well I've heard precisely zero feedback about this.  So I guess nobody's
> > using the AHA2842 controller anymore.  Is there *anyone* successfully
> > using this controller with a recent (5.1.26 or later) aic7xxx driver
> > version?
> > 
> > For what it's worth, I narrowed down the point where the breakage was
> > introduced.  The last working version of the aic7xxx driver (for aic7770)
> > is 5.1.25.  Starting with 5.1.26 the Linux kernel panics on boot with this
> > driver controlling an AHA2842 controller card.
> > 
> > I did this testing using stock 2.2.14 kernel sources, patching up the
> > driver to the next version after every test.  I used the same kernel
> > configuration each time and compiled each kernel from a clean source tree.
> > 
> > Suggestions anyone?
> 
> I'm going to try and fix this for the 5.1.29 driver version, but I don't have
> a 7770 based card to test any more.
> 
> -- 
> 
>  Doug Ledford <dledford at redhat.com>  http://people.redhat.com/dledford
>       Please check my web site for aic7xxx updates/answers before
>                       e-mailing me about problems
> 
> 

                        |         Mike Isely          |     PGP fingerprint
    POSITIVELY NO       |                             | 03 54 43 4D 75 E5 CC 92
 UNSOLICITED JUNK MAIL! |   isely @ pobox (dot) com   | 71 16 01 E2 B5 F5 C1 E8
                        |   (spam-foiling  address)   |



To Unsubscribe: send mail to majordomo at FreeBSD.org
with "unsubscribe aic7xxx" in the body of the message