On 9/20/05, John Brahy <[EMAIL PROTECTED]> wrote: > I've got two poweredge 2650's w/ PERC 3/di raid cards and I've tried OpenBSD > 3.7, 3.6 and 3.5. I've found that the aac in 3.7 is completely unstable, the > aac in 3.6 would have problems after an hour or so of heavy use. BUT, 3.5 > seems to be stable but now I'm stuck on a version of an os that is about to > become unsupported.
aac support in 3.8 seems to be much better than 3.7 in my experience, however I still suggest better hardware if possible. > > I think the only long term solution is to change hardware. I have been > considering Sun's trade in offer. I haven't found it on Sun's site but it is > mentioned here (http://www.theinquirer.net/?article=26143) > I have a friend that's a Sun dealer www.acsacs.com and they said they honor > it. I don't believe they sell online. Does anyone know if OpenBSD likes this > hardware? > > It's really Adaptec's fault. Those fuckers won't give up the source so the > OpenBSD developers can't provide a good driver for their hardware. My > company will not purchase any more servers from Dell as long as they > continue to use Adaptec cards. > First off, we never asked for "source" from adaptec, we were only asking for documentation to make the driver more stable, and write management utilities. However they only provide documentation if you sign an NDA, which is unacceptable for any free software. Second, all the PERC4 cards Dell uses are no longer Adaptec, but LSI Logic (unless they've changed again reciently), which is fully supported in OpenBSD, including completely open management utilities. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of > Jan Johansson > Sent: Tuesday, September 20, 2005 8:14 AM > To: Ryan Rothert > Cc: [email protected] > Subject: Re: Dell PowerEdge 2650 > > Ryan Rothert <[EMAIL PROTECTED]> wrote: > > 3.6 will install on it. I believe the aac driver still exists > > but is disabled by default. You could install 3.6, recompile > > the kernel with aac support enabled then upgrade. > > This is a bad advice. > > The aac driver was disabled because it was broken and could not > be fixed because there was no documentation. > > Using aac is like playing Russian Roulette with your data.
