Search content
Sort by
Showing 18 of 18 results by frozen80
Re: [ANN] cpuminer-opt v3.19.4, open source optimized multi-algo CPU miner
It worked perfectly on a fresh installation of MSYS2(latest build on their website).
I think users should be also informed to follow the instructions on the msys2 website to update the base packages and install some tools for compiling(just in case they overlook these three steps):
I think users should be also informed to follow the instructions on the msys2 website to update the base packages and install some tools for compiling(just in case they overlook these three steps):
Code:
pacman -Syu
pacman -Su
pacman -S --needed base-devel mingw-w64-x86_64-toolchain
pacman -Su
pacman -S --needed base-devel mingw-w64-x86_64-toolchain
Re: [ANN] cpuminer-opt v3.19.4, open source optimized multi-algo CPU miner
⭐ Merited by JayDDee (1)
You were right, it is a compiler bug!
The problem is a flag in -O2 level that is -ftree-vrp and the default values of its parameters.
We can keep -O3 and add --param=evrp-mode=legacy. From my understanding this param will instruct how the flag -ftree-vrp will perform. The default value for this param is ranger:
Aside from this, you are right about the resulting binary. It's working only in msys2 environment. It might work outside msys2 too, if we provide the path to the DLLs files.
It's just another way of doing it, and if it's possible, why not!
The problem is a flag in -O2 level that is -ftree-vrp and the default values of its parameters.
We can keep -O3 and add --param=evrp-mode=legacy. From my understanding this param will instruct how the flag -ftree-vrp will perform. The default value for this param is ranger:
Code:
--param=evrp-mode=[legacy|ranger|legacy-first|ranger-first] default is "ranger"
It works fine with:Code:
CFLAGS="-O3 --param=evrp-mode=legacy -march=native -maes -Wall"
I found some info related to this issue here: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103603Aside from this, you are right about the resulting binary. It's working only in msys2 environment. It might work outside msys2 too, if we provide the path to the DLLs files.
It's just another way of doing it, and if it's possible, why not!
Re: [ANN] cpuminer-opt v3.19.4, open source optimized multi-algo CPU miner
I tried to compile in Windows 10(MinGW64) with [gcc version 11.2.0 (Rev5, Built by MSYS2 project)].
Using the default
Changing optimization level to -O1 solved the problem and it compiled successfully.
Using the default
Code:
CFLAGS="-O3 -march=native -maes -Wall"
I get the following error on file algo/jh/sph_jh.c. Code:
gcc -DHAVE_CONFIG_H -I. -Iyes/include -fno-strict-aliasing -I. -Iyes/include -Wno-pointer-sign -Wno-pointer-to-int-cast -Wl,--stack,10485760 -Icompat/pthreads -O3 -march=native -maes -Wall -Iyes/include -MT algo/jh/cpuminer-sph_jh.o -MD -MP -MF algo/jh/.deps/cpuminer-sph_jh.Tpo -c -o algo/jh/cpuminer-sph_jh.o `test -f 'algo/jh/sph_jh.c' || echo './'`algo/jh/sph_jh.c
make[2]: *** [Makefile:3963: algo/jh/cpuminer-sph_jh.o] Error 1
Same error occurs with -O2.make[2]: *** [Makefile:3963: algo/jh/cpuminer-sph_jh.o] Error 1
Changing optimization level to -O1 solved the problem and it compiled successfully.
Code:
$ ./cpuminer.exe --version
********** cpuminer-opt 3.19.4 ***********
A CPU miner with multi algo support and optimized for CPUs
with AVX512, SHA and VAES extensions by JayDDee.
BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
CPU: AMD Ryzen 5 1600 Six-Core Processor
SW built on Jan 13 2022 with GCC 11.2.0
CPU features: AVX2 AES SHA
SW features: AVX2 AES SHA
********** cpuminer-opt 3.19.4 ***********
A CPU miner with multi algo support and optimized for CPUs
with AVX512, SHA and VAES extensions by JayDDee.
BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
CPU: AMD Ryzen 5 1600 Six-Core Processor
SW built on Jan 13 2022 with GCC 11.2.0
CPU features: AVX2 AES SHA
SW features: AVX2 AES SHA
Re: [ANN] TeamRedMiner 0.5.2 - Cryptonight Thread - High hashrate, Low Power
@kerney666
What does it mean to have the "hw" code triggered for a GPU? My Radeon VII GPU is having almost a 40% "hw" triggering even though the pool is still accepting its share. However, the poolside hashrate for the card is very low. I am using TRM 0.5.2 and running my GPU @1575cclk/975mclk/855mV.
Any ideas what is happening and how to fix this?
What does it mean to have the "hw" code triggered for a GPU? My Radeon VII GPU is having almost a 40% "hw" triggering even though the pool is still accepting its share. However, the poolside hashrate for the card is very low. I am using TRM 0.5.2 and running my GPU @1575cclk/975mclk/855mV.
Any ideas what is happening and how to fix this?
Can you share your hashrate,power draw and stable settings. Did you manage to solve your "hw" errors problem? I'm also interested to buy one and I'm curious with the power draw and the temperatures. Also does it come with Samsung memory?
Re: [ANN] TeamRedMiner 0.4.5 - Cryptonight Thread - High hashrate, Low Power
Hi guys,
Sometimes one of my Vega56 gets in trouble with only one of the two threads. I tried to use the --watchdog_script parameter but unfortunately it works only for a dead GPU.
Do you know any settings I can use for the "half dead" GPU?
@todxx Is it possible to implement an internal watchdog for the threads(just in case only one thread will die the watchdog would restart only that thread)?
Tnx to the devs for this awesome miner!
Sometimes one of my Vega56 gets in trouble with only one of the two threads. I tried to use the --watchdog_script parameter but unfortunately it works only for a dead GPU.
Do you know any settings I can use for the "half dead" GPU?
@todxx Is it possible to implement an internal watchdog for the threads(just in case only one thread will die the watchdog would restart only that thread)?
Tnx to the devs for this awesome miner!
@kerney666 An internal watchdog, is it possible?
Re: [ANN] TeamRedMiner 0.4.5 - Cryptonight Thread - High hashrate, Low Power
Hi guys,
Sometimes one of my Vega56 gets in trouble with only one of the two threads. I tried to use the --watchdog_script parameter but unfortunately it works only for a dead GPU.
Do you know any settings I can use for the "half dead" GPU?
@todxx Is it possible to implement an internal watchdog for the threads(just in case only one thread will die the watchdog would restart only that thread)?
Tnx to the devs for this awesome miner!
Sometimes one of my Vega56 gets in trouble with only one of the two threads. I tried to use the --watchdog_script parameter but unfortunately it works only for a dead GPU.
Do you know any settings I can use for the "half dead" GPU?
@todxx Is it possible to implement an internal watchdog for the threads(just in case only one thread will die the watchdog would restart only that thread)?
Tnx to the devs for this awesome miner!
Re: AMD Mem Tweak - Read/modify mem timings on the fly - [Vega Friendly] [Win/Linux]
Hi guys,
I have a Sapphire Nitro+ Vega56 with default bios and Hynix memory with the defaults:
I'm using TR4.4 with L22+22 and driver 18.6.1.
Unfortunately with other values posted here i had no luck
What values do you think i could try to change based on my defaults?
I have a Sapphire Nitro+ Vega56 with default bios and Hynix memory with the defaults:
Code:
GPU 0: Vega 10 XL/XT [Radeon RX Vega 56/64] Memory state: 0x118 (800MHz)
Timing 1 CL: 18 RAS: 24 RCDRD: 22 RCDWR: 10
Timing 2 RCAb (RC): 37 RCPb (RC): 37 RPAb (RP): 13 RPPb (RP): 13
Timing 3 RRDS: 3 RRDL: 3 RTP: 6
Timing 4 FAW: 13
Timing 5 CWL: 6 WTRS: 4 WTRL: 4
Timing 6 WR: 12
Timing 7 RREFD: 7
Timing 8 RDRDDD: 3 RDRDSD: 2 RDRDSC: 1 RDRDSCL: 3
Timing 9 WRWRDD: 3 WRWRSD: 2 WRWRSC: 1 WRWRSCL: 3
Timing 10 WRRD: 1 RDWR: 18
Timing 12 REF: 3200
Timing 13 MRD: 4 MOD: 12
Timing 14 XS: 216
Timing 16 XSMRS: 216
Timing 17 PD: 7 CKSRE: 8 CKSRX: 8
Timing 20 RFCPB: 96 STAG: 7
Timing 21 XP: 7 CPDED: 2 CKE: 7
Timing 22 RDDATA: 17 WRLAT: 4 RDLAT: 14 WRDATA: 1
Timing 23 CKESTAG: 2
RFC Timing RFC: 176
Until now the only value i could change was --ref 12800 which increased the hashrate from 18.5 to 19.5 kh on cn-turtle.Timing 1 CL: 18 RAS: 24 RCDRD: 22 RCDWR: 10
Timing 2 RCAb (RC): 37 RCPb (RC): 37 RPAb (RP): 13 RPPb (RP): 13
Timing 3 RRDS: 3 RRDL: 3 RTP: 6
Timing 4 FAW: 13
Timing 5 CWL: 6 WTRS: 4 WTRL: 4
Timing 6 WR: 12
Timing 7 RREFD: 7
Timing 8 RDRDDD: 3 RDRDSD: 2 RDRDSC: 1 RDRDSCL: 3
Timing 9 WRWRDD: 3 WRWRSD: 2 WRWRSC: 1 WRWRSCL: 3
Timing 10 WRRD: 1 RDWR: 18
Timing 12 REF: 3200
Timing 13 MRD: 4 MOD: 12
Timing 14 XS: 216
Timing 16 XSMRS: 216
Timing 17 PD: 7 CKSRE: 8 CKSRX: 8
Timing 20 RFCPB: 96 STAG: 7
Timing 21 XP: 7 CPDED: 2 CKE: 7
Timing 22 RDDATA: 17 WRLAT: 4 RDLAT: 14 WRDATA: 1
Timing 23 CKESTAG: 2
RFC Timing RFC: 176
I'm using TR4.4 with L22+22 and driver 18.6.1.
Unfortunately with other values posted here i had no luck
What values do you think i could try to change based on my defaults?
Re: [JCE] Ultrafast CN-Heavy/Tube/HVX miner, low power, Vega56 1750+ h/s
I am trying out JCE for the first time.
Getting 1660h/s per card.
What would be the best config for Vega 56's on BittubeV2?
This is my config.
"gpu_threads_conf" :
[
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 0, "multi_hash":464 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 0, "multi_hash":464 },
],
Thanks
Alpha 128, multi_hash as high as possible.Getting 1660h/s per card.
What would be the best config for Vega 56's on BittubeV2?
This is my config.
"gpu_threads_conf" :
[
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 0, "multi_hash":464 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 0, "multi_hash":464 },
],
Thanks
I use alpha:64 and multi_hash:896 on Vega56 and i have 1700 h/s which is a 21% increase than previous version where i had around 1400 h/s.
Great work DEV!
Tnx for this great miner!
Whats the recommended driver? im using 18.9.3 and my rig freezes.
i have mix gpu in my system, 3 x 580, 2 x 570, 1 x 470, 1 x r9 Fury and 2 x Nvidia 1070.
Using win 1709, any one can help me with freeze problem.
i have mix gpu in my system, 3 x 580, 2 x 570, 1 x 470, 1 x r9 Fury and 2 x Nvidia 1070.
Using win 1709, any one can help me with freeze problem.
You should try 18.6.1
Hello JCE,
Can you add support for https://webchain.network/?
Their algo it's a modified version of CryptoNightV7.
They have official miner for CPU here: https://github.com/webchain-network and unofficial for GPU here: https://github.com/monkins1010.
Tnx and keep up the good work!
Can you add support for https://webchain.network/?
Their algo it's a modified version of CryptoNightV7.
They have official miner for CPU here: https://github.com/webchain-network and unofficial for GPU here: https://github.com/monkins1010.
Tnx and keep up the good work!
Hi Dev,
I'm still using version 0.31c of the miner on a Vega56(Driver: 18.6.1) to mine CryptoLight V7(set FORK=4).
This is my conf:
With the same conf i've try to mine with version 0.32a, 0.32t but no luck.
My first problem is the hashrate drop from 4300 to 3700 and the second, i get a lot of invalid shares.
The only improvement is the compilation speed of the kernels.
JCE 0.32t results: https://imgur.com/Tao8Y7Q
I have also good news for the Cryptonight V7(set FORK=3). The hashrate is the same with all versions, around 1950 h/s.
Because of that i will continue to use version 0.31c until you get a Vega so you can test your code properly.
Until then keep up the good work!
It's a great miner!!!
I'm still using version 0.31c of the miner on a Vega56(Driver: 18.6.1) to mine CryptoLight V7(set FORK=4).
This is my conf:
Code:
"gpu_threads_conf" :
[
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 0, "multi_hash" : 3552 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 0, "multi_hash" : 3552 },
]
JCE 0.31c results: https://imgur.com/TSkGb7h[
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 0, "multi_hash" : 3552 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 0, "multi_hash" : 3552 },
]
With the same conf i've try to mine with version 0.32a, 0.32t but no luck.
My first problem is the hashrate drop from 4300 to 3700 and the second, i get a lot of invalid shares.
The only improvement is the compilation speed of the kernels.
JCE 0.32t results: https://imgur.com/Tao8Y7Q
I have also good news for the Cryptonight V7(set FORK=3). The hashrate is the same with all versions, around 1950 h/s.
Because of that i will continue to use version 0.31c until you get a Vega so you can test your code properly.
Until then keep up the good work!
It's a great miner!!!
Quote
@JCE-Miner
Is it possible that the config generated by the --auto option can also be written in a text file or at least showed in the output?
I have good results for the Vega on the auto config and it would be nice to know the parameters of the config just in case i want to use the -c option later on.
Tnx dev.
Keep up the good work!
Is it possible that the config generated by the --auto option can also be written in a text file or at least showed in the output?
I have good results for the Vega on the auto config and it would be nice to know the parameters of the config just in case i want to use the -c option later on.
Tnx dev.
Keep up the good work!
Lol ... It is already in the output ... i didn't notice.
The desktop wallet is here: https://stardustcoin.org/docs/stardustwalletwin64.zip
Hi!
I'm trying to run JCE-Gpu for CN Lite V7 (Bitsum) - the Fork parameter is 0, the pool writes an error. Somebody digs Lite V7, what should be the option in the settings?
I'm trying to run JCE-Gpu for CN Lite V7 (Bitsum) - the Fork parameter is 0, the pool writes an error. Somebody digs Lite V7, what should be the option in the settings?
set FORK=4
Hi guys,
How can i insert the config for my ryzen 3 2200g .
Im tryed :
jce_cn_cpu_miner%BITS%.exe -c CONFIG==config.bittube --any --forever --variation %FORK% --low -o %POOL%:%PORT% -u %WALLET% -p %PASSWORD% %SSL% %*
But no sucess open my config for the cpu
How can i insert the config for my ryzen 3 2200g .
Im tryed :
jce_cn_cpu_miner%BITS%.exe -c CONFIG==config.bittube --any --forever --variation %FORK% --low -o %POOL%:%PORT% -u %WALLET% -p %PASSWORD% %SSL% %*
But no sucess open my config for the cpu
Hi zeef,
I think your config.bittube file should look like this:
Code:
"cpu_threads_conf" :
[
{ "cpu_architecture" : "auto", "affine_to_cpu" : 0, "use_cache" : true },
{ "cpu_architecture" : "auto", "affine_to_cpu" : 1, "use_cache" : true },
{ "cpu_architecture" : "auto", "affine_to_cpu" : 2, "use_cache" : true },
{ "cpu_architecture" : "auto", "affine_to_cpu" : 3, "use_cache" : true },
]
You have additional "," after 'true' on thread 2 and thread 4. Try to remove the extra ",".[
{ "cpu_architecture" : "auto", "affine_to_cpu" : 0, "use_cache" : true },
{ "cpu_architecture" : "auto", "affine_to_cpu" : 1, "use_cache" : true },
{ "cpu_architecture" : "auto", "affine_to_cpu" : 2, "use_cache" : true },
{ "cpu_architecture" : "auto", "affine_to_cpu" : 3, "use_cache" : true },
]
And "-c config.bittube" on the params in the .bat file.
Good luck!
Hello miners,
I'm using the last version of JCEMiner(31c) on CNLite V7(set FORK=4 in the .bat), mining Turtlecoin.
I mine with CPU+GPU(Threadripper 1950x & Sapphire Nitro+ Vega56).
Config: https://imgur.com/JCFukAv
Hashrates on the miner:https://imgur.com/aPMszui
Hashrates on the pool: https://imgur.com/dqVebcX
The CPU is OC 10% from 3.4Ghz to 3.75Ghz.
For the Vega i'm using(1500Mhz/950mV on the gpu and 925Mhz/925mV on the memory). The Vega is serving also a fullhd display.
The full output wattage reported on the system in stand-by is 85W and when mining 330W.
The CPU itself is showing 10W in standby and around 100W when mining.
The temp of the CPU is around 60 degrees with air cooling(Noctua U12S with 2 fans).
The Vega is around 50 degrees at 2000 rpm for the fans.
I think the hashrates are good but unfortunately not a lot of coins are using this CNLite V7 fork.
Happy mining!
I'm using the last version of JCEMiner(31c) on CNLite V7(set FORK=4 in the .bat), mining Turtlecoin.
I mine with CPU+GPU(Threadripper 1950x & Sapphire Nitro+ Vega56).
Config: https://imgur.com/JCFukAv
Hashrates on the miner:https://imgur.com/aPMszui
Hashrates on the pool: https://imgur.com/dqVebcX
The CPU is OC 10% from 3.4Ghz to 3.75Ghz.
For the Vega i'm using(1500Mhz/950mV on the gpu and 925Mhz/925mV on the memory). The Vega is serving also a fullhd display.
The full output wattage reported on the system in stand-by is 85W and when mining 330W.
The CPU itself is showing 10W in standby and around 100W when mining.
The temp of the CPU is around 60 degrees with air cooling(Noctua U12S with 2 fans).
The Vega is around 50 degrees at 2000 rpm for the fans.
I think the hashrates are good but unfortunately not a lot of coins are using this CNLite V7 fork.
Happy mining!
Hello @doktor83,
I'm trying to use my CPU(Threadripper 1950x) also with SRBMiner v1.6.0 but i got an OpenCL error. I used the default config from the readme file and the --usecpuopencl arg on the command line. I've tried different parameters inside "cpu_conf" but it doesn't want to compile the kernel.
The error is like this:
https://i.imgur.com/NASYeio.png
Thank you.
I'm trying to use my CPU(Threadripper 1950x) also with SRBMiner v1.6.0 but i got an OpenCL error. I used the default config from the readme file and the --usecpuopencl arg on the command line. I've tried different parameters inside "cpu_conf" but it doesn't want to compile the kernel.
Code:
"cpu_conf" :
[
{ "intensity" : 1, "worksize" : 1, "threads" : 1}
]
[
{ "intensity" : 1, "worksize" : 1, "threads" : 1}
]
The error is like this:
https://i.imgur.com/NASYeio.png
Thank you.