nucleon...
Here's hoping you see this

Update
 

[QUOTE=flashjh;282486]Good reading and hopefully good news for Bulldozer CPUs... now I just need to get my power supply in so I can test everything!

[URL]http://support.microsoft.com/kb/2592546[/URL][/QUOTE]

The KB download is gone... MS & AMD said it's not ready and many people were getting BSOD with this update. Oh well, at least they're working on it. Looks like AMD and MS need to release two updates to fix the problem and it won't be until 1st Qtr '12.

[URL]http://www.brightsideofnews.com/news/2011/12/16/microsoft-releases-amd-bulldozer-patch-by-mistake2c-incomplete-download.aspx[/URL]

How can I put this politely...I can't recommend bulldozer at all atm. I can't go past a 2500k for value for money. The bulldozer I have, I'm pretty much keen on throwing it out or give it to some poor uni student who needs a pc.

The other thing hurting bulldozers is 16Kb L1 cache. Every other platform seems to be 32k - and hence everything is optimized for that.

I'm working on getting all the info to do a doco post of my setup - stay tuned.

-- Craig

...on the comment of Windows scheduler. The patch is still coming.

It was due to come out then pulled due to issues in testing apparently.

-- Craig

Anyone have mkakto working on one of the newer amd APUs?

I have an E350 here and I had no luck. Tried 11.9 drivers - GPU usage was only <5%. So I think something is up. Tried 11.12 drivers - no luck there either; exe drops out with errors.

-- Craig

[QUOTE=nucleon;282670]Anyone have mkakto working on one of the newer amd APUs?

I have an E350 here and I had no luck. Tried 11.9 drivers - GPU usage was only <5%. So I think something is up. Tried 11.12 drivers - no luck there either; exe drops out with errors.

-- Craig[/QUOTE]
Drivers 11.10 and above will work only with mfakto 0.10 (to be released next week).

In the last week of this year I may have the chance to test an E350 as well. I had hoped it would work right away, but maybe more work is needed. Can you give a few details - did it not find the GPU (and therefore failed to use it, just running on the CPU)? Maybe you could post the output of when it starts, and also the output of clinfo. But I guess it's easier to wait for 0.10 than downgrade the drivers again ...

If you pm me you email address I can send you the RC of 0.10.

I think it did found the GPU - using GPUz it did show a slight increase (say 2% to 6%) and it dropped back down after I closed it.

Sorry, but I'm not going to get much time with it to do further testing. I gotta hand it back.

This was a win7 home premium install.

-- Craig

Version 0.10 release
 

mfakto version 0.10 is ready, with the following changes:

[LIST][*]workaround for compatibility with Catalyst 11.10 and above (tested up to 11.12)[*]Checkpoints now keep a backup (.bu) that is automatically read if the .cpt file is corrupt[*]mfakto now allows reading checkpoints from any version of mfaktc and mfakto as long as the other parameters match and the checksum is OK[*]split mul24 kernel in two bitranges 0-64 and 61-72 allowing for some optimizations: 10-20% performance improvement for 70-bit assignments using the mul24 kernel:
[I]Please check for your GPU if barrett is still faster or if it makes sense to switch to the mul24 kernel.
On HD5770 and HD 6870 barrett is still a bit ahead ...
[/I][*]merged mfaktc 0.18 features:[*][LIST][*]inifile parameter CheckpointDelay (see below)[*]extended selftest (-st2)[*]Changes to the factor found result line as discussed in the mersenne forum[/LIST] [*]Writing checkpoints can now be limited:[*][LIST][*]set CheckpointDelay <s> to write a checkpoint only if at least s seconds have passed since the last checkpoint[*]set Checkpoint <n>, n>1 to write a checkpoint only after n classes have been tested (set to n=1 to enable CheckpointDelay)[/LIST] [*]added commandline parameter -i|--inifile <file>
to load <file> as inifile (default: mfakto.ini), allowing multiple instances of mfakto in the same directory[*]added ResultsFile parameter to inifile (same reason)[*]... and a few less important things (see README)[/LIST][I]Attention: If you use Catalyst 11.10 or above with this version, there is an incompatibility with AMD APP SDK 2.4 leading to BSODs (Win) or mfakto/X-Server hangs (Linux).[/I] Make sure to uninstall APP SDK - it is no longer needed since 11.9 (Win) or 11.11 (Linux). If you need the APP SDK, install version 2.5.

Source package follows en suite, Linux version tomorrow.

mfakto 0.10 sources
 

mfakto 0.10 sources

If anyone feels like creating a Makefile.win for the sources, I'd be happy to move away from VS10 ...

6950 Results
 

What is the MUL24 Kernal?

In .09 I was using the mfakto_cl_71 for my 6950s with the shaders unlocked (so basically 6970s). I was getting around 140 M/s

With mfakto_cl_barrett79 I was getting around 120 M/s, so barrett was around 15-20% slower.

With .10 I seem to be getting around 120 M/s with both, so the mfakto_cl_71 seems to have gotten slower for me. The barrett kernel still runs at the same speed.

I am installing something ATM, but I can check again when I am done if you would like. Let me know if there are any screenshots or output files I can send you if that would help.

Edit: I just confirmed that at the same load, I now run around 20% slower with the new version.

I'm running both mfakto win 0.09 and 0.10 on different PCs. I've noticed that mfakto 0.10 (x64) seems to crash fairly regularly. I'm using cat 11.12 with 2x5870s. Since I'm running remote, I haven't been able to monitor the circumstance of the crashes. Event viewer doesn't have anything helpful to add at the moment. I'll update if I can find a set of circumstances that cause the crash.