• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

did not recognize the processor?!?

S

Skaven

Senior member
I just got my trusty old Asus P55T2P4 mainboard out to install a CHEAP K6-III+ that I just got (Hot Deals forum). One of the first proggys I put on it?? Dnet client of course!!! 🙂

Anyway, check this out:

[Oct 11 18:43:22 UTC] Automatic processor type detection did not
recognize the processor (tag: "7541:05D0&quot😉
[Oct 11 18:43:22 UTC] RC5: Running micro-bench to select fastest core...
[Oct 11 18:43:54 UTC] RC5: using core #5 (RG RISC-rotate II).

Have you guys seen this before? I was hoping that since the K6-III+ had the Athlon 3DNow enhancements, it would run better! Should I worry about which core it selected? I'm sure it ran all the benches and then decided on the fastest... I just never ran into this before... <shrug>

Anywho, its running at 450mhz right now (going to try for 500mhz later) and here are the scores:

RC5 short block: 770,639 k/s
RC5 long block: 768,341 k/s

For ~$50 its not so bad! 🙂 Besides I am FINALLY using that old AT case and Asus mainboard! 🙂

Add another 450mhz to my herd!

-Skaven
 


<< using core #5 (RG RISC-rotate II). >>


is alright. Running on K-6III myself that's what the client detects on my machine. 500 Mhz works here and 800+ should be no prob. Nice ass lamination BTW. 😀
We love you man !
 
Skaven,

If you aren't sure that the core chosen is the best you can go to the command line and run &quot;dnetc.exe -bench&quot;. This will run long benchmarks for all the processor cores and you can tell which one is really the best.

After you have deterimined the optimum core, you should tell the client to use that core instead of the auto detect.

The reason that the client doesn't detect the processor automatically is that the K6-3+ just came out and has a different &quot;tag&quot; than the K6-3 even though they should run the client with exactly the same keyrate.
 
Skaven, sciencewhiz is right on the detection reason, though I'd also like to note that the RC5 client has no use for 3dNow! instructions, so it's not something for you to worry about.🙂

PS If your wondering about how the Athlon got a boost, it was related to it's architecture, not 3dNow!
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top