Well that's another problem - the DRAC stuff doesn't work once FreeBSD finishes booting (or, rather, the virtual keyboard doesn't work). Dermot On Wed, 2006-10-04 at 06:30 -0500, Eric Anderson wrote: > Scott, > > I have a new 1950 sitting here ready for any hacking you want. It has > remote console access (DRAC), etc, so I could install whatever you want > and give you full access to it. Any other resources you need to work on > this, I can provide also. Email me directly if you are interested. > > Eric > > > On 10/04/06 03:19, Scott Long wrote: > > A quick tour of the bce driver leaves a lot of concerns in my mind > > about how interrupts are handled as well as how work is segmented. > > I only have very limited access to a 1950 with this chip in it, > > though, so if anyone can provide better access (or maybe a shiny > > new 1950 for my lab!) I can look at it over the next week or so. > > > > Scott > > > > > > Dermot Williams wrote: > >> Frederik, > >> > >> Dunno if it helps, but we're running 6.1-STABLE on 1950s and the mfi > >> driver detects the SAS with no problems. > >> > >> With regard to the bce driver, I've been having the exact same issue on > >> this hardware - NFS triggers it every time in our case. I've upgraded > >> one of the machines in question to one of the 7- releases and the > >> problem is still there, unfortunately. > >> > >> I've actually ordered Intel PRO cards for these 1950s because we're in > >> the same boat as you in that we don't really want to migrate away from > >> FreeBSD. > >> > >> Sorry I don't have more or better info for you. > >> > >> Regards, > >> > >> Dermot > >> > >> On Wed, 2006-10-04 at 00:33 +0200, Fredrik Widlund wrote: > >>> Hi, > >>> > >>> I'm trying to get FreeBSD working on Dell 1950 (and 2950), which is > >>> vital since it's no longer possible to buy 1850/2850 units here. > >>> > >>> Hardware: > >>> PE1950 Xeon 5130, 2GB 667MHz > >>> SAS 5I > >>> PERC5E > >>> > >>> 6.1-RELEASE: not possible since SAS drives aren't found. > >>> 6.2-BETA2: bce interfaces does not work at all, "watchdog timeout > >>> occured" every other second, and _no_ connectivity. > >>> > >>> We are also having problems with some PE1850 failing from time to time > >>> with "watchdog timeout" hangs, and have had to debug.mpsafenet=0 these. > >>> > >>> How can we help solve this issue? It would really be a pity to be forced > >>> to leave FreeBSD but we really can't afford to replace our choice of > >>> hardware platform. > >>> > >>> Kind regards, > >>> Fredrik Widlund > >>> > > _______________________________________________ > > freebsd-current_at_freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org" > >Received on Wed Oct 04 2006 - 09:38:22 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:01 UTC