HEAD UP: non-MPSAFE network drivers to be disabled
Gary Jennejohn
gary.jennejohn at freenet.de
Mon May 26 18:58:02 UTC 2008
On Mon, 26 May 2008 19:21:24 +0200
Willem Jan Withagen <wjw at digiware.nl> wrote:
> Steve Kargl wrote:
> > On Mon, May 26, 2008 at 05:34:09AM -0700, Ade Lovett wrote:
> >> idiosyncratic situations (yes, ahc(4), I'm looking at you) for 5+
> >
> > What's the problem with ahc(4)? My ahc controller is one of
> > the most reliable pieces of hardware that I've purchased.
> > It's also the only interface available to my external DLT
> > tape drive.
>
> Not to forget the large amount of embedded ahc's that got implemented on
> all kinds of serverbords. I still have quite a large set of customers
> with such ASUS boards I sold to them over the years. Up 'till now I've
> been able to keep 'm running with the pace of FreeBSD.
> Removing this driver would "leave them behind".
>
> I can force them to upgrade, but thus far there has been little reason
> for that (hardware wise).
>
[pruned the over-zealous CCs]
Well, one problem with ahc is that it doesn't play nicely with >= 4GB
of memory on AMD64.
I have ahc and 4GB of memory and have to set hw.physmem="3500m" in
/boot/loader.conf to keep it from dumping its cookies at boot time.
Otherwise I'm more than happy with my 29160N.
---
Gary Jennejohn
More information about the freebsd-arch
mailing list