Topic: [ANN]: cpuminer-opt v3.8.8.1, open source optimized multi-algo CPU miner - page 153. (Read 444067 times)
July 21, 2016, 06:54:54 PM
Good.. I'm running CPU-Miner at i7 6700K 8M on windows 7 64x and didn't have any problem...
July 21, 2016, 06:50:17 PM
hey joblo, i run a windows 32 bit machine, considering the sw is for 64 bit i can't use it, is there a possible workaround ?
thanks
thanks
July 21, 2016, 05:45:52 PM
is there a way to statically build/link the miner (linux) ?
i wasn't able to get it running
i wasn't able to get it running
A native build is always prefereable to ensure you're taking advantage of all the optimizations supported
by your CPU.
Describe the problem you're having. Does it fail to compile, or fail to run after compiling? Post any error
messages.
July 21, 2016, 05:38:41 PM
is there a way to statically build/link the miner (linux) ?
i wasn't able to get it running
i wasn't able to get it running
July 20, 2016, 11:26:58 AM
i stumbled upon this as i was running some benchmark with nicehash for my cpu autoswitching miner control software (which uses cpuminer-opt)
July 20, 2016, 11:20:38 AM
thanks for looking into it, yes its a low prio issue, maybe its fixed in some future release 
July 19, 2016, 04:28:02 PM
i heard skein2 too 
Yup, I broke that in 3.3.7. I knew that one of my optimizations would break it but forgot to follow up.
I had removed the automatic ctx init in the close function of all sph algos because it was unnecessary
in most cases. But it is needed in algos like skein2 that run the same algo multiple times. I simply forgot
to add an explicit init before the second skein round.
July 19, 2016, 03:59:36 PM
i heard skein2 too
July 19, 2016, 03:50:46 PM
I can confirm that mining decred at nicehash is broken yet it works at zpool. I have also found some of the
other blake based algos are broken at nicehash.
I will have to do some more investigation.
other blake based algos are broken at nicehash.
I will have to do some more investigation.
July 19, 2016, 09:58:04 AM
hi joblo,
it seems decred (and maybe other algos?) generate 100% rejected on nicehash with the following error:
"reject reason: Invalid extranonce2 size."
is this a bug?
br
it seems decred (and maybe other algos?) generate 100% rejected on nicehash with the following error:
"reject reason: Invalid extranonce2 size."
is this a bug?
br
Thanks for reporting this. It appears to be specific to decred and nicehash. I will look into this and do a round of testing
on nicehash to confirm only decred is broken. I'm not very motivated to implement a workaround if it only applies to one
algo in one pool.
I should also point out that decred, and other blake algos, are the worst performing algos for CPU mining.
In summary this is a very low priority issue.
July 19, 2016, 04:44:19 AM
nicehash is using its own protocol. Even if it looks correct, i think its not better and might create problems on future blockchain votes.
My implementation was accepted/reviewed by the decred team, they have seen the vote problem (the last bit of the vote field should never be changed by the miner, and blocks will not be accepted by "proper" pools)
First i thought it was always 1 but it can be 0 too. its a small thing but could be important later.
Nicehash made a different one without contacting decred team
Else for multi gpus, my initial protocol seems better/easier to handle
My implementation was accepted/reviewed by the decred team, they have seen the vote problem (the last bit of the vote field should never be changed by the miner, and blocks will not be accepted by "proper" pools)
First i thought it was always 1 but it can be 0 too. its a small thing but could be important later.
Nicehash made a different one without contacting decred team
Else for multi gpus, my initial protocol seems better/easier to handle
July 18, 2016, 11:23:16 PM
hi joblo,
it seems decred (and maybe other algos?) generate 100% rejected on nicehash with the following error:
"reject reason: Invalid extranonce2 size."
is this a bug?
br
it seems decred (and maybe other algos?) generate 100% rejected on nicehash with the following error:
"reject reason: Invalid extranonce2 size."
is this a bug?
br
July 14, 2016, 11:49:55 AM
cpuminer-opt v3.3.7 released.
https://drive.google.com/file/d/0B0lVSGQYLJIZc0x3V2JPUXhPLWs/view?usp=sharing
- lyra2 AES optimized +7%
- small increase, ~1%, in most chained algos (x11, quark, lyra2v2, etc)
- lyra2v2 now reported as AES optimized
- added a decimal place to the accepted rate percentage if less than 100%
Windows binaries:
http://cryptomining-blog.com/wp-content/download/cpuminer-opt-3-3-7-windows.zip
https://drive.google.com/file/d/0B0lVSGQYLJIZc0x3V2JPUXhPLWs/view?usp=sharing
- lyra2 AES optimized +7%
- small increase, ~1%, in most chained algos (x11, quark, lyra2v2, etc)
- lyra2v2 now reported as AES optimized
- added a decimal place to the accepted rate percentage if less than 100%
Windows binaries:
http://cryptomining-blog.com/wp-content/download/cpuminer-opt-3-3-7-windows.zip
June 24, 2016, 03:22:51 PM
yep the only reliable way found was dmidecode | grep MHz
found no way on windows to get the freq and the temperature :/ it seems to require some low level drivers to access some protected asm
found no way on windows to get the freq and the temperature :/ it seems to require some low level drivers to access some protected asm
June 24, 2016, 12:30:24 PM
Superb work. Some algo's on my ageing CPU are almost half an ageing GPU.
Don't know whether it's possible to report the actual CPU frequency rather than the default CPU frequency in the stats. Some people are probably wondering how I get so much hash out of my CPU! (It's OC'd to 4.6 GHz).
Thanks for the tips.Don't know whether it's possible to report the actual CPU frequency rather than the default CPU frequency in the stats. Some people are probably wondering how I get so much hash out of my CPU! (It's OC'd to 4.6 GHz).
I agree with CPU freq. Simply displaying the default freq is of no use, it just happens to be part of the brand string.
I'm sure the actual freq can be found, the code may already exist.
CPU freq is not so simple. It can be read diectly from the /sys/ or /proc/ file systems on Linux but I don't know of an API
for Windows.
Using /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq would be preferred because it returns a simple numeric string.
But it is root access only.
/proc/cpuinfo is accessible and also includes the CPU freq but it needs to be filtered from two pages of output.
This will require more thought and more work.
June 23, 2016, 10:53:03 AM
Superb work. Some algo's on my ageing CPU are almost half an ageing GPU.
Don't know whether it's possible to report the actual CPU frequency rather than the default CPU frequency in the stats. Some people are probably wondering how I get so much hash out of my CPU! (It's OC'd to 4.6 GHz).
You really should look at getting this onto github. It's quite simple to use. I'd suggest the following:
Create a github account and install git (sudo apt-get install git).
Fork the original source code using the web front end
Clone the fork into a new directory. (git clone)
Copy your code over the cloned fork code.
Submit the changes. (git commit -n "comment", I think)
Push the changes to github. (git push with a couple of parameters)
It's also easy to track changes made to the original and integrate them after that.
Expect a star from me!
Don't know whether it's possible to report the actual CPU frequency rather than the default CPU frequency in the stats. Some people are probably wondering how I get so much hash out of my CPU! (It's OC'd to 4.6 GHz).
You really should look at getting this onto github. It's quite simple to use. I'd suggest the following:
Create a github account and install git (sudo apt-get install git).
Fork the original source code using the web front end
Clone the fork into a new directory. (git clone
Copy your code over the cloned fork code.
Submit the changes. (git commit -n "comment", I think)
Push the changes to github. (git push with a couple of parameters)
It's also easy to track changes made to the original and integrate them after that.
Expect a star from me!
Thanks for the tips.
I agree with CPU freq. Simply displaying the default freq is of no use, it just happens to be part of the brand string.
I'm sure the actual freq can be found, the code may already exist.
About github, I presume your suggestion to fork the original cpuminer-multi is to maintain its history, this is a good thing.
I wanted to wait until the development slowed down so I wouldn't be trying to learn github while trying to fix bugs in cpuminer.
Now may be a good time to dig into it. I need to play in a sandbox for a while before I comit to it.
github not to hard to learn, at its basics. Original developer might be terse and not open for discussion. Which is not good for a serial forker.
June 23, 2016, 08:34:41 AM
Superb work. Some algo's on my ageing CPU are almost half an ageing GPU.
Don't know whether it's possible to report the actual CPU frequency rather than the default CPU frequency in the stats. Some people are probably wondering how I get so much hash out of my CPU! (It's OC'd to 4.6 GHz).
You really should look at getting this onto github. It's quite simple to use. I'd suggest the following:
Create a github account and install git (sudo apt-get install git).
Fork the original source code using the web front end
Clone the fork into a new directory. (git clone)
Copy your code over the cloned fork code.
Submit the changes. (git commit -n "comment", I think)
Push the changes to github. (git push with a couple of parameters)
It's also easy to track changes made to the original and integrate them after that.
Expect a star from me!
Don't know whether it's possible to report the actual CPU frequency rather than the default CPU frequency in the stats. Some people are probably wondering how I get so much hash out of my CPU! (It's OC'd to 4.6 GHz).
You really should look at getting this onto github. It's quite simple to use. I'd suggest the following:
Create a github account and install git (sudo apt-get install git).
Fork the original source code using the web front end
Clone the fork into a new directory. (git clone
Copy your code over the cloned fork code.
Submit the changes. (git commit -n "comment", I think)
Push the changes to github. (git push with a couple of parameters)
It's also easy to track changes made to the original and integrate them after that.
Expect a star from me!
Thanks for the tips.
I agree with CPU freq. Simply displaying the default freq is of no use, it just happens to be part of the brand string.
I'm sure the actual freq can be found, the code may already exist.
About github, I presume your suggestion to fork the original cpuminer-multi is to maintain its history, this is a good thing.
I wanted to wait until the development slowed down so I wouldn't be trying to learn github while trying to fix bugs in cpuminer.
Now may be a good time to dig into it. I need to play in a sandbox for a while before I comit to it.
June 23, 2016, 03:02:03 AM
Superb work. Some algo's on my ageing CPU are almost half an ageing GPU.
Don't know whether it's possible to report the actual CPU frequency rather than the default CPU frequency in the stats. Some people are probably wondering how I get so much hash out of my CPU! (It's OC'd to 4.6 GHz).
You really should look at getting this onto github. It's quite simple to use. I'd suggest the following:
Create a github account and install git (sudo apt-get install git).
Fork the original source code using the web front end
Clone the fork into a new directory. (git clone)
Copy your code over the cloned fork code.
Submit the changes. (git commit -n "comment", I think)
Push the changes to github. (git push with a couple of parameters)
It's also easy to track changes made to the original and integrate them after that.
Expect a star from me!
Don't know whether it's possible to report the actual CPU frequency rather than the default CPU frequency in the stats. Some people are probably wondering how I get so much hash out of my CPU! (It's OC'd to 4.6 GHz).
You really should look at getting this onto github. It's quite simple to use. I'd suggest the following:
Create a github account and install git (sudo apt-get install git).
Fork the original source code using the web front end
Clone the fork into a new directory. (git clone
Copy your code over the cloned fork code.
Submit the changes. (git commit -n "comment", I think)
Push the changes to github. (git push with a couple of parameters)
It's also easy to track changes made to the original and integrate them after that.
Expect a star from me!
June 20, 2016, 11:55:26 PM
I don't understand what you're saying. Please guide more detailed.
You need to explain more about what you are doing.I replied to your message.
Your first post included CPU info that indicated you are using QEMU. Please describe the configuration of your PC
and how you are using QEMU to compile cpuminer-opt.
If you don't understand what I am asking maybe you can find some way to translate to vietnamese.
June 09, 2016, 10:45:59 AM
Jump to: