> > That would be nice. . . I'd like to know *why* the AIC-7xxx driver
> > was changed in the "stable" kernel series. . . isn't that contrary
> > to the express purpose of the stable series? The AIC-7xxx driver
> > was working just fine for me in 2.0.32, why did it need to be
> > modified? Anybody know?
> For the same reason I'm currently working on the 5.1.0 driver version. It
> had nothing to do with the old driver not working on the cards it was
> intended to work on, it had to do with newer cards on the market.
> Specifically, the 5.0.x driver versions, as are in 2.0.34 and 2.0.35 include
> support for the aic7895 chipset as used on many motherboards and as the
> newer 3940AUW cards use. The 5.1.0 driver is adding support for the
> 7890/1/6/7 chipsets as well (all of the Ultra2 chipsets).
> --
> --------------------------------------
> Opinions expressed are my own, but
> they should be everybody's.
> --------------------------------------
I do agree with John, WHY change it in the STABLE series, you don't want toknow
the harm it already has done to my own system. I test the latest greatest
(in this case stable!!) kernel on my own system (and leave our servers alone
until
I am sure it keeps working), both 2.0.34 and 2.0.35 will hardlock my system
under
any heavy disk usage, so for me 2.0.34/35 is NOT stable and can't be
implemented
on our production systems. A * little detail: Red Hat has gone to
2.0.34/35 for
all releases now, so in effect I am stuck at the current 2.0.33 now if I want
to keep
the production systems RH pure :-((
Will 2.0.36 be a STABLE kernel WRT aic7xxx?
Ron Offerman
IT Staff