Hello guys! It has become quiet here so I decided to speak up...
I have a good news and a bad news...
The bad news is that I have found strange glitch with my new Mac mini. Everything works perfectly except Xbench that locks up when it tries to do vecLib FFT part of the CPU test. Reliably crashes at exactly the same place every time... As I said before everything else works fine.
The good news is that my Mac mini is in fact 1.25GHz Mac mini that runs at 1.5GHz. I can step down to 1.42GHz where Xbench works just perfect as everything else! So I am inclined to think that it is not an instability but some strange glitch.
Even more the mini starts up at 1.58GHz as well but "About this Mac" shows 750MHz (?) frequency and Xbench locks up at exactly same place on vecLib FFT. Everything else is fine... Very strange... Could this be either overclock protection or some glitch from OF or Mac OS not expecting this frequency?
What do you think is going on and should I just leave it at 1.5GHz and try to find what happens or get "back" to 1.42GHz?
Well, at least we can get away with 1.25 -> 1.42 which is quite good anyway...
I have just took it apart so have not had a chance to discuss it anywhere else...
Details are available here:
http://www.lbodnar.dsl.pipex.com/macmini/
Leo
I have a good news and a bad news...
The bad news is that I have found strange glitch with my new Mac mini. Everything works perfectly except Xbench that locks up when it tries to do vecLib FFT part of the CPU test. Reliably crashes at exactly the same place every time... As I said before everything else works fine.
The good news is that my Mac mini is in fact 1.25GHz Mac mini that runs at 1.5GHz. I can step down to 1.42GHz where Xbench works just perfect as everything else! So I am inclined to think that it is not an instability but some strange glitch.
Even more the mini starts up at 1.58GHz as well but "About this Mac" shows 750MHz (?) frequency and Xbench locks up at exactly same place on vecLib FFT. Everything else is fine... Very strange... Could this be either overclock protection or some glitch from OF or Mac OS not expecting this frequency?
What do you think is going on and should I just leave it at 1.5GHz and try to find what happens or get "back" to 1.42GHz?
Well, at least we can get away with 1.25 -> 1.42 which is quite good anyway...
I have just took it apart so have not had a chance to discuss it anywhere else...
Details are available here:
http://www.lbodnar.dsl.pipex.com/macmini/
Leo