Follow-up: A small patch (thanks to Andrew Gallatin) to mptable.c, plus booting without ACPI (which to my knowledge isn't going to hurt me in my particular setup - feel free to correct me if I'm wrong here), makes FreeBSD enable the second CPU and use it. Running a make -j 10 buildworld now for a (very) rudimentary test, in a loop. Will see if the box is still alive tomorrow morning, but it's already been through one build and started the second without errors. So yes, quite possibly I've been very lucky :) Thanks, /Eirik David O'Brien wrote: > On Wed, May 05, 2004 at 10:04:31AM +0200, Eirik Oeverby wrote: > >>I've recently changed from an Asus A7M266-D board to a MSI K7D Master-L >>board, due to the Asus dying on me. I'm running with dual Athlon 1.4ghz >>CPUs (non-MP, just plain old Athlon CPUs), and with the Asus this was no >>problem at all. Performance was fine, both CPUs were utilized well, and >>all was good. >>Now with the MSI board, the BIOS complains on bootup that the CPUs I'm >>using aren't MP-capable, and that it has disabled one and is running in >>UNIprocessor mode. > > > You were very, very lucky this worked at all. You say "plain old > Athlon", not "Athlon XP". This implies Thunderbird, which really didn't > support SMP and I'm very surprised it worked at all in the Asus board. > Are you sure you don't mean "Athlon XP" (Palomino or newer)? > > The reason your BIOS is complaining is that non-MP Athlon's aren't > guaranteed to work in an SMP configuration. If you sampled 10 Athlon > XP's of them, I guaranteed some of them wouldn't work in SMP mode. Athlon > MP CPU's are fully tested, QA'ed, and certified to run *reliably* in SMP > mode and configurations. If AMD didn't have these checks put into the > BIOS, and you used two XP's that wouldn't work together you'd call AMD > CPU's "crap" and be all pissed.Received on Wed May 05 2004 - 14:38:52 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:53 UTC