Sorry for the repost...
I don't think the first one posted..
posted to freebsd.stable, freebsd-current, Freebsd-hardware
I checked the hardware in the online documentation manual/hardware
It only lists the bits and peices of the machine say the hard drive
controller and so forth. but doesn't give you a particular system to
look at as a working machine with FreeBSD 6.2
does anybody know if a Dell PowerEdge 1950
? Quad-Core Intel Xeon Processors 5400 series 3.16GHz
? 4GB Ram
I am looking to attach 2 machines to a SAN to make a constantly up
system. Is there a Dell San and San Switch that will work with this
version of BSD?
Thank you for your help
Hi Richard, I run freeBSD 6.2 on a 1950 and the only i had issue i had was with the on board broadcom ethernet, my workaround is detailed here http://www.ifdnrg.com/freebsd_broadcom_dell_1950.htm hope that helps Paul. <http://www.ifdnrg.com> *web and video services* *Paul Macdonald* Director paul@ifdnrg.com <mailto:paul@ifdnrg.com> www.ifdnrg.com <http://www.ifdnrg.com> *IFDNRG* *Please note new address!* 127 Rose St South Lane, Edinburgh, EH2 4BB +44.131.2257470
On 1/8/08, Richard Bates <rtbates@patmedia.net> wrote:> Sorry for the repost... > I don't think the first one posted.. > > posted to freebsd.stable, freebsd-current, Freebsd-hardware > > I checked the hardware in the online documentation manual/hardware > > It only lists the bits and peices of the machine say the hard drive > controller and so forth. but doesn't give you a particular system to > look at as a working machine with FreeBSD 6.2 > > does anybody know if a Dell PowerEdge 1950 > ? Quad-Core Intel Xeon Processors 5400 series 3.16GHz > ? 4GB Ram > > I am looking to attach 2 machines to a SAN to make a constantly up > system. Is there a Dell San and San Switch that will work with this > version of BSD?I'm using a newer version of the PE2950, which has the PERC 6/i controller. Older ones use the PERC 5/i, which is supported by 6.2. Dell machines are pretty well supported.> > Thank you for your help > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >-- Mahnahmahnah!
Richard Bates wrote:> Sorry for the repost... > I don't think the first one posted.. > > posted to freebsd.stable, freebsd-current, Freebsd-hardware > > I checked the hardware in the online documentation manual/hardware > > It only lists the bits and peices of the machine say the hard drive > controller and so forth. but doesn't give you a particular system to > look at as a working machine with FreeBSD 6.2 > > does anybody know if a Dell PowerEdge 1950 > ? Quad-Core Intel Xeon Processors 5400 series 3.16GHz > ? 4GB Ram >We have ~20 PE [12]950 systems here all running 6/2 with a back ported bce driver from RELENG_6. Tom> I am looking to attach 2 machines to a SAN to make a constantly up > system. Is there a Dell San and San Switch that will work with this > version of BSD? > > Thank you for your help > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Richard Bates wrote:> Sorry for the repost... > I don't think the first one posted.. > > posted to freebsd.stable, freebsd-current, Freebsd-hardware > > I checked the hardware in the online documentation manual/hardware > > It only lists the bits and peices of the machine say the hard drive > controller and so forth. but doesn't give you a particular system to > look at as a working machine with FreeBSD 6.2 > > does anybody know if a Dell PowerEdge 1950 > ? Quad-Core Intel Xeon Processors 5400 series 3.16GHz > ? 4GB Ram > > I am looking to attach 2 machines to a SAN to make a constantly up > system. Is there a Dell San and San Switch that will work with this > version of BSD? > > Thank you for your helpIt has been observed that there is some interrupt related issue with certain models of Dell PowerEdge 1950/2950 on 6.2-RELEASE, to be more specific, those which are configured without a RAID controller. The symptom is that server will hang on boot after detected acd0, but this is not reliably reproducible. At our company (we deploy hundreds of 1950/2950 online during last year), our important local changes that is made for these boxes include: - backport my bce(4) changes from RELENG_6. - backport MSI support, and enable by default. (*) *: This is the default behavior for 7.0, I have not encountered the problem mentioned above on any 1950/2950 boxes so far I have tested. That's said, I would recommend that you deploy 6.3-RELEASE (with proper loader.conf configuration to enable MSI) or 7.0-RELEASE once they are out of the door. I do not have much experience with SAN devices you have mentioned, though, so perhaps it's better to listen someone else's suggestions. Cheers, - -- Xin LI <delphij@delphij.net> http://www.delphij.net/ FreeBSD - The Power to Serve! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD4DBQFHhWFpi+vbBBjt66ARAhaLAJdYQHtgCsXYYdgPvWOh0QiLARWmAKCU2sH5 9PLlYsSESqvoMHCekHtJfw==xIhB -----END PGP SIGNATURE-----
Vivek Khera wrote:> > On Jan 15, 2008, at 1:40 PM, John Baldwin wrote: > >>> Where can one go to read up on what MSI is and how it helps us? >>> >>> Is enabling it just setting a sysctl? Does that have to be done in >>> loader.conf or can it happen later? >> >> loader.conf (though it is now default on in RELENG_6). >> >> hw.pci.msi_enable=1 >> hw.pci.msix_enable=1 > > > Thanks for the info. But can anyone point me to some documentation on > why MSI is good for me? >When implemented and used correctly in the hardware and driver, it a lower overhead interrupt mechanism. It also expands the number of interrupt vectors available, making interrupt sharing non-existent (for right now, at least). Scott
Vivek Khera wrote:> > On Jan 15, 2008, at 1:40 PM, John Baldwin wrote: > >>> Where can one go to read up on what MSI is and how it helps us? >>> >>> Is enabling it just setting a sysctl? Does that have to be done in >>> loader.conf or can it happen later? >> >> loader.conf (though it is now default on in RELENG_6). >> >> hw.pci.msi_enable=1 >> hw.pci.msix_enable=1 > > > Thanks for the info. But can anyone point me to some documentation on > why MSI is good for me? >When implemented and used correctly in the hardware and driver, it a lower overhead interrupt mechanism. It also expands the number of interrupt vectors available, making interrupt sharing non-existent (for right now, at least). Thirdly, it vastly simplifies interrupt routing and makes a lot of problems with missing interrupts at the OS/driver level go away. Scott