Search content
Sort by
Showing 20 of 422 results by kenshirothefist
Re: NVIDIA is cutting the 3060's Hash Rate in Half & NEW Mining specific GPU's
Yup, as shown in the past, mining is only a temporary spike. They need to take care of the core market.
Unfortunatelly Nvidia is (once again) trying to put out the fire with quick and bad solution. They were unprepared for the third time in the row with the current crypto hype and still they do not have a strategy, a proper solution to the issue. Now they are trying to sell old hardware to miners which is "specialized for mining" and at the same time disabling home users by bricking future gaming gpus which is essentially a kick in the ass for the much needed decentralized mining. This is very very bad solution and will not solve the issues addressed. Fist of all - if profitability will be good then miners will buy ANYTHING that is capable of mining (gaming/specialized) and will try to override the driver/bios obstacles that Nvidia puts in new products. And secondly - miner will ALWAYS buy best price/performance product and not some fancy-named "specialized" products.
Re: NVIDIA is cutting the 3060's Hash Rate in Half & NEW Mining specific GPU's
that means about 370,000 3080.s. were added in 7 weeks. so 7.1 x that = 2.62 million gpus a year. Just for mining.
could that be correct?
could that be correct?
Due to the fact that every single computer-related community, even large sites like anandtech, tomshardware, etc. are talking about mining this means that every single 3xxx 68xx that is sold it is actually used for mining, let it be professional miners or gamers. Due to the hype and media cover, everybody knows about mining and everybody is mining. So yes, the vast majority of new hashrate is from 3xxx 68xx ... ASIC can't just come ouf of the blue ...
It looks like Nvidia is trying desperate measures to fight GPU shortages. What do you thing about this?
https://blogs.nvidia.com/blog/2021/02/18/geforce-cmp/
https://blogs.nvidia.com/blog/2021/02/18/geforce-cmp/
Here is my working room heater 
I have a wooden custom build case under my desk with big ATX chassis in it, and one undeclocked Avalon4 connected to my Linux workstation which is always powered on anyway
Avalon4 is connected directly to my PC's power supply
My PC is an good old Intel quad-core, custom water cooled with water cooled GPU (an old AMD, doesn't even support OpenCL, so I can't mine with it )
But my undeclocked Avalon4 at only 30% fan speed is almost totally silent and at 45C it makes a great foot heater for cold days
That makes a nice heater that actually makes Bitcoins ... the miner itself draws about 380W which makes lesst hen 0.55 W/GH at wall ... considering the heating effect the electricity is basically free.
I have a wooden custom build case under my desk with big ATX chassis in it, and one undeclocked Avalon4 connected to my Linux workstation which is always powered on anyway
Avalon4 is connected directly to my PC's power supply
My PC is an good old Intel quad-core, custom water cooled with water cooled GPU (an old AMD, doesn't even support OpenCL, so I can't mine with it
)But my undeclocked Avalon4 at only 30% fan speed is almost totally silent and at 45C it makes a great foot heater for cold days
That makes a nice heater that actually makes Bitcoins ... the miner itself draws about 380W which makes lesst hen 0.55 W/GH at wall ... considering the heating effect the electricity is basically free.
Re: [ANN] Signatum - New Algorithm - Fair Launch - No Premine - Cryptopia
Support for Skunk algorithm
NiceHash is introducing the immediate availability for buying and selling hashing power with Skunk algorithm. The Signatum coin can be mined by buying the Skunk algorithm hashing power. You can place orders and point them to any of your preferred Signatum pools.
Take a look here for more information: https://new.nicehash.com/news/204
Best regards,
kenshirothefist.
NiceHash is introducing the immediate availability for buying and selling hashing power with Skunk algorithm. The Signatum coin can be mined by buying the Skunk algorithm hashing power. You can place orders and point them to any of your preferred Signatum pools.
Take a look here for more information: https://new.nicehash.com/news/204
Best regards,
kenshirothefist.
Anyone else noticed the bug in ethminer generating DAG files? When trying to generate DAG file for any block larger than 3870000, it will only produce a 0-size file.
Try this:
It will run just of a few seconds, generate 0-bytes file "full-R23-3868abc5dcee2334" and exit.
Try this:
Code:
ethminer.exe -D 3870000
It will run just of a few seconds, generate 0-bytes file "full-R23-3868abc5dcee2334" and exit.
This has now been fixed by Ethereum core devs. @Genoil or whoever is still maintaining various ethminer forks: make sure to include this patch, or else ethminers will simply "die" after block block 3870000.
Hi,
Anyone else noticed the bug in ethminer generating DAG files? When trying to generate DAG file for any block larger than 3870000, it will only produce a 0-size file.
Try this:
It will run just of a few seconds, generate 0-bytes file "full-R23-3868abc5dcee2334" and exit.
Anyone else noticed the bug in ethminer generating DAG files? When trying to generate DAG file for any block larger than 3870000, it will only produce a 0-size file.
Try this:
Code:
ethminer.exe -D 3870000
It will run just of a few seconds, generate 0-bytes file "full-R23-3868abc5dcee2334" and exit.
Re: Gateless Gate: zawawa's open-source cross-platform OpenCL Zcash miner
sgminer-gm seems to be working fine with an old SA kernel both with RX 480 and with GTX 1060.
(Obviously, it's really slow and hardware monitoring is not available for the latter.)
Porting GG's kernel to sgminer-gm should not be that difficult if SA's kernel is already working.
Let's see if I can quickly hack up a new version...
(Obviously, it's really slow and hardware monitoring is not available for the latter.)
Porting GG's kernel to sgminer-gm should not be that difficult if SA's kernel is already working.
Let's see if I can quickly hack up a new version...
Please, make yourself a favour and don't dig into sgminer. Even though it is a great multi-algorithm miner and also we at NiceHash support it for long time, it has too much legacy and is too bloated. It goes back to original minerd, through cgminer, into sgminer, with lots "ifs" inside. Modern algorithms and modern gpus need lightweight miners, and nhqminer is one of them, you're really welcome to try working on nheqminer (it can be easily extended with support for other algorithms, besides equihash).
There are serious issues with this miner on Win10 when mining on multiple AMD GPUs (more than 2) ... CPU is overloaded and shares not validated on the pool. Anyone has a solution for this?
@Genoil, if I understand correctly I can not generate DAG file locally (saved on my drive) with 1.1.x version of ethminer? I noticed that if I use latest 1.0.x windows build, I can only generate DAGs up to block 3840000 (-D,--create-dag ) ... if I specify any larger block, ethminer crashes. Is this an issue with Ethereum generally, or an issue with ethminer?
Re: SILENTARMY v4: Zcash miner, now with Nvidia support (Linux only)
mrb, you still haven't pulled these two?
https://github.com/mbevand/silentarmy/pull/17
https://github.com/mbevand/silentarmy/pull/39
There are many miners, trying to use your miner on NiceHash, but are having issues because of these two issues (and on some others pools as well, because of missing client.reconnect method).
Anyway, if anyone of you would like to mine on NiceHash with silentarmy you can build from our fork https://github.com/nicehash/silentarmy where these two issues are already solved.
Thanks!
https://github.com/mbevand/silentarmy/pull/17
https://github.com/mbevand/silentarmy/pull/39
There are many miners, trying to use your miner on NiceHash, but are having issues because of these two issues (and on some others pools as well, because of missing client.reconnect method).
Anyway, if anyone of you would like to mine on NiceHash with silentarmy you can build from our fork https://github.com/nicehash/silentarmy where these two issues are already solved.
Thanks!
Re: SILENTARMY v4: Zcash miner, now with Nvidia support (Linux only)
Really it is a shame, that there is no opensource miner for nvidia, only with devfee one, which makes 53-54 s/s on one 1070, and low cpu usage.
As far as I know there is no NVIDIA closed-source miner with devfee that makes 53-54 S/s (hopefully you are not referring to this scam https://github.com/zcminer-dev/zcminer).
So for now Tromp-based miners are the only one available for NVIDIA (for example, https://github.com/nicehash/nheqminer).
Re: SILENTARMY v3: now a full miner! multi-GPU, Stratum support (Linux only)
mrb, I also would love to support the request to pool
into the mainstream. Would it be possible to implement it?
Code:
extranonce.subscribe #39
https://github.com/mbevand/silentarmy/pull/39
https://github.com/mbevand/silentarmy/pull/39
into the mainstream. Would it be possible to implement it?
Until @mbr doesn't pulls this you can build from our repository (just forked with patches for NiceHash extranonce.subscription):
https://github.com/nicehash/silentarmy
Re: SILENTARMY v3: now a full miner! multi-GPU, Stratum support (Linux only)
Anyway, I pushed a nicehash-compatibilty update to tolerate stratum servers fixing 17 bytes of the nonce: https://github.com/mbevand/silentarmy/commit/0d371a9582159627b11941c14ca6cbc3da359cb1
Perhaps I will eventually permanently address the issue by allowing the last 12 bytes of the nonce to be non-zero...
Perhaps I will eventually permanently address the issue by allowing the last 12 bytes of the nonce to be non-zero...
Cool. I've also made a pull for extranonce.subscribe
https://github.com/mbevand/silentarmy/pull/39
btw: I also believe that you should pull this one https://github.com/mbevand/silentarmy/pull/17 per stratum specs
Re: Open Source ZEC (ZCash) GPU Miner AMD & NVidia (up to 45 sol/s on RX480)
So, what's up with this bug under Linux:
I see several reports of this issue, but no solution?
Code:
terminate called after throwing an instance of 'config4cpp::ConfigurationException'
Aborted (core dumped)
Aborted (core dumped)
I see several reports of this issue, but no solution?
joblo, you're probably already aware of the Tromp's Equihash solvers, which were released under open-source. Are you considering implementing them into your cpuminer-opt, thus adding support for equihash algortihm (for z.cash)?
That's a cuda miner, still looking for a CPU miner.
Not true. It has fastest to-date known public CPU implementation as well as CUDA implementation.
joblo, you're probably already aware of the Tromp's Equihash solvers, which were released under open-source. Are you considering implementing them into your cpuminer-opt, thus adding support for equihash algortihm (for z.cash)?
Please, make sure to read wattage numbers at the Wall. ADL on new AMD cards is foobar, so the only number that you can count on is power meter at the wall. So, @tytanick, repeat your comparison with a watt meter at the wall and see if there are really these kind of differences between Linux/Windows.
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v7.1 (Windows/Linux)
Claymore, you could fix the issue when using NVIDIA GPUs without fans (watercooling, server-grade GPUs, etc.):
Code:
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
GPU0 t=48C fan=0%, GPU1 t=76C fan=0%, GPU2 t=44C fan=0%, GPU3 t=71C fan=0%, GPU4 t=63C fan=0%, GPU5 t=52C fan=0%, GPU6 t=61C fan=0%, GPU7 t=50C fan=0%
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
GPU0 t=48C fan=0%, GPU1 t=76C fan=0%, GPU2 t=44C fan=0%, GPU3 t=71C fan=0%, GPU4 t=63C fan=0%, GPU5 t=52C fan=0%, GPU6 t=61C fan=0%, GPU7 t=50C fan=0%
Code:
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 367.48 Driver Version: 367.48 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 Tesla M60 Off | 0000:05:00.0 Off | 0 |
| N/A 50C P0 111W / 150W | 1766MiB / 7613MiB | 100% Default |
+-------------------------------+----------------------+----------------------+
| 1 Tesla M60 Off | 0000:06:00.0 Off | 0 |
| N/A 81C P0 118W / 150W | 1768MiB / 7613MiB | 100% Default |
+-------------------------------+----------------------+----------------------+
| NVIDIA-SMI 367.48 Driver Version: 367.48 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 Tesla M60 Off | 0000:05:00.0 Off | 0 |
| N/A 50C P0 111W / 150W | 1766MiB / 7613MiB | 100% Default |
+-------------------------------+----------------------+----------------------+
| 1 Tesla M60 Off | 0000:06:00.0 Off | 0 |
| N/A 81C P0 118W / 150W | 1768MiB / 7613MiB | 100% Default |
+-------------------------------+----------------------+----------------------+
Hi,
First of all, I don't have any issues like lost coins, etc, I'm just looking for some detailed information:
1. Where exactly are private keys and other application files stored (Android 4.3)? There is no /data/data/de.schildbach.wallet/ folder on the device (looked for ../data in device storage and sd card).
2. When this app is uninstalled from a device, does it make complete cleanup, deletes all private keys, etc?
Thanks for answers.
First of all, I don't have any issues like lost coins, etc, I'm just looking for some detailed information:
1. Where exactly are private keys and other application files stored (Android 4.3)? There is no /data/data/de.schildbach.wallet/ folder on the device (looked for ../data in device storage and sd card).
2. When this app is uninstalled from a device, does it make complete cleanup, deletes all private keys, etc?
Thanks for answers.