Search content
Sort by
Showing 10 of 10 results by Nacsiar
Hey guys,
I've posted about this problem at https://bitcointalk.org/index.php?topic=227918. This fix is mostly limited to CGMiner/BFGMiner but the problem is the same, so the solution should be similar.
Good luck, and let me know if you need more help!
Note: my 'fix' removes a switch and as such may break mining with other cards (or reduce performance!!)
I've posted about this problem at https://bitcointalk.org/index.php?topic=227918. This fix is mostly limited to CGMiner/BFGMiner but the problem is the same, so the solution should be similar.
Good luck, and let me know if you need more help!
Note: my 'fix' removes a switch and as such may break mining with other cards (or reduce performance!!)
Re: [Group Buy] AVALON CHIPs 4142 left @0.082BTC + K16 Miner Assembly from 60EUR
; <64>; < 5.248 >; < 4 >; <1HjQnqHuUoGdAeWvLXDq4asaovF5nN2PgK>
So Nacsiar, 64 chips, 5.248BTC, 4 miner assemblies, and 1HjQnqHuUoGdAeWvLXDq4asaovF5nN2PgK for the address.
Tx: https://blockchain.info/en/tx/f78c0724c0fb32ed2908ffe5e0b4c236938805bcb7bf5f3abb4c4e84cd0316f2
Please confirm!
So Nacsiar, 64 chips, 5.248BTC, 4 miner assemblies, and 1HjQnqHuUoGdAeWvLXDq4asaovF5nN2PgK for the address.
Tx: https://blockchain.info/en/tx/f78c0724c0fb32ed2908ffe5e0b4c236938805bcb7bf5f3abb4c4e84cd0316f2
Please confirm!
How are you planning on mining? With a pool? in that case you'll be better off with say CGMiner or BFGMiner.
That said... you probably won't get much more MHash out of that card, regardless of your miner. The hardware comparison guide reckons that you'll get 27 MHash/sec even if you overclocked it; not really worth it at today's difficulty (and certainly not for the future!)
That said... you probably won't get much more MHash out of that card, regardless of your miner. The hardware comparison guide reckons that you'll get 27 MHash/sec even if you overclocked it; not really worth it at today's difficulty (and certainly not for the future!)
Re: Can't get bitcoind to accept RPC connections from other machines
Code:
user@server:~$ netstat -lp | grep bitcoind
tcp 0 0 localhost:8332 *:* LISTEN 32153/bitcoind
tcp 0 0 *:8333 *:* LISTEN 32153/bitcoind
tcp6 0 0 localhost:8332 [::]:* LISTEN 32153/bitcoind
tcp6 0 0 [::]:8333 [::]:* LISTEN 32153/bitcoind
As you can see, the RPC port (8332) is only listening for local connections, as expected. tcp 0 0 localhost:8332 *:* LISTEN 32153/bitcoind
tcp 0 0 *:8333 *:* LISTEN 32153/bitcoind
tcp6 0 0 localhost:8332 [::]:* LISTEN 32153/bitcoind
tcp6 0 0 [::]:8333 [::]:* LISTEN 32153/bitcoind
What firewall are you using? do you have iptables enabled (I assume not since you say others are connecting fine)? It sounds more like your gateway not forwarding ports from your external IP.
Hi,
Please whitelist me.
I have an understanding of BTC (I have had my own wallet using the bitcoin-qt client for over a year now), have knowledge of how miners work and have already offered help here for those experiencing issues with 5800 cards, 13.4 cats and cgminer/bfgminer (https://bitcointalk.org/index.php?topic=227918.0).
Thanks!
Please whitelist me.
I have an understanding of BTC (I have had my own wallet using the bitcoin-qt client for over a year now), have knowledge of how miners work and have already offered help here for those experiencing issues with 5800 cards, 13.4 cats and cgminer/bfgminer (https://bitcointalk.org/index.php?topic=227918.0).
Thanks!
Hi!
I posted about this earlier on this very same forum. Please read https://bitcointalk.org/index.php?topic=227918.0 for a solution!
I posted about this earlier on this very same forum. Please read https://bitcointalk.org/index.php?topic=227918.0 for a solution!
Don't have that card so I can't test if it helps, but you could provide a patch to make it even easier to implement.
I'd be glad to, however it's not worth implementing in it's current form; I removed some of the checks that might need to be there for other card series!
Code snippet of the diff:
Code:
--- phatk121016.cl 2013-06-07 09:38:40.000000000 +0100
+++ phatk121016-modified.cl 2013-06-07 10:41:05.000000000 +0100
@@ -57,27 +57,12 @@
// SHA-256 Ch function, but provides it in exactly one instruction. If
// detected, use it for Ch. Otherwise, construct Ch out of simpler logical
// primitives.
-
- #ifdef BFI_INT
- // Well, slight problem... It turns out BFI_INT isn't actually exposed to
- // OpenCL (or CAL IL for that matter) in any way. However, there is
- // a similar instruction, BYTE_ALIGN_INT, which is exposed to OpenCL via
- // amd_bytealign, takes the same inputs, and provides the same output.
- // We can use that as a placeholder for BFI_INT and have the application
- // patch it after compilation.
- // This is the BFI_INT function
- #define Ch(x, y, z) amd_bytealign(x,y,z)
- // Ma can also be implemented in terms of BFI_INT...
- #define Ma(z, x, y) amd_bytealign(z^x,y,x)
- #else // BFI_INT
- // Later SDKs optimise this to BFI INT without patching and GCN
- // actually fails if manually patched with BFI_INT
-
- #define Ch(x, y, z) bitselect((u)z, (u)y, (u)x)
+ //We have an SDK which automatically optimizes to BFI INT, so lets do this
+ #define Ch(x, y, z) bitselect(z, y, x)
#define Ma(x, y, z) bitselect((u)x, (u)y, (u)z ^ (u)x)
#define rotr(x, y) amd_bitalign((u)x, (u)x, (u)y)
- #endif
+
#else // BITALIGN
#define Ch(x, y, z) (z ^ (x & (y ^ z)))
#define Ma(x, y, z) ((x & z) | (y & (x | z)))
+++ phatk121016-modified.cl 2013-06-07 10:41:05.000000000 +0100
@@ -57,27 +57,12 @@
// SHA-256 Ch function, but provides it in exactly one instruction. If
// detected, use it for Ch. Otherwise, construct Ch out of simpler logical
// primitives.
-
- #ifdef BFI_INT
- // Well, slight problem... It turns out BFI_INT isn't actually exposed to
- // OpenCL (or CAL IL for that matter) in any way. However, there is
- // a similar instruction, BYTE_ALIGN_INT, which is exposed to OpenCL via
- // amd_bytealign, takes the same inputs, and provides the same output.
- // We can use that as a placeholder for BFI_INT and have the application
- // patch it after compilation.
- // This is the BFI_INT function
- #define Ch(x, y, z) amd_bytealign(x,y,z)
- // Ma can also be implemented in terms of BFI_INT...
- #define Ma(z, x, y) amd_bytealign(z^x,y,x)
- #else // BFI_INT
- // Later SDKs optimise this to BFI INT without patching and GCN
- // actually fails if manually patched with BFI_INT
-
- #define Ch(x, y, z) bitselect((u)z, (u)y, (u)x)
+ //We have an SDK which automatically optimizes to BFI INT, so lets do this
+ #define Ch(x, y, z) bitselect(z, y, x)
#define Ma(x, y, z) bitselect((u)x, (u)y, (u)z ^ (u)x)
#define rotr(x, y) amd_bitalign((u)x, (u)x, (u)y)
- #endif
+
#else // BITALIGN
#define Ch(x, y, z) (z ^ (x & (y ^ z)))
#define Ma(x, y, z) ((x & z) | (y & (x | z)))
...and a pastebin for those that prefer it:
http://pastebin.com/tZ7DeV2c
Hey guys, figured I'd make my first post useful.
So if you have a 58xx series card (could be more) and upgraded your catalyst drivers to latest, you may have noticed that you are getting nothing but this:
Of course, this is no good! You won't be sending any blocks that are deemed invalid, and contributing nothing to whatever pool you might be on!
The reason for this seems to be that amd_bytealign is either working differently or no longer usable in the 13.4 drivers (and probably a few before it). that phatk kernel that cgminer and bfgminer uses was upgraded to harness this optimization, however with the newer drivers "bitselect" is automatically optimized to BFI INT without us having to do it!
So, how do you fix it? simple!
1. To start, navigate to your miner's folder and look for a file that begins with "phatk" and ends with ".cl". this is the OpenCL code that makes up the kernel, but as it's a script it can be opened in any text document viewer (I highly recommend Notepad++!)
2. Inside this file may be a bit daunting, but don't worry, there's only a few small changes needed! You'll notice around line 61 (depending on your version of miner) you'll see the following (or very similar):
Some of this block is the problematic code for the 13.4 Catalysts, and as such we need to change it!
3. Delete the above block of code (aprrox line 49 to 86 inclusive), and replace it with the following:
This avoids any of the logic that should cause you problems.
4. if your miner is running, shut it down. if you have any leftover files starting in "phatk" and ending in ".bin", it's probably best to delete those.
5. Start up your miner. it should now start accepting blocks!
Hope this has helped. Note that this is modified from the following post regarding a similar problem on poclbm: https://bitcointalk.org/index.php?topic=221041.0.
Happy mining!
So if you have a 58xx series card (could be more) and upgraded your catalyst drivers to latest, you may have noticed that you are getting nothing but this:
Quote
GPU0: invalid nonce - HW error
Of course, this is no good! You won't be sending any blocks that are deemed invalid, and contributing nothing to whatever pool you might be on!
The reason for this seems to be that amd_bytealign is either working differently or no longer usable in the 13.4 drivers (and probably a few before it). that phatk kernel that cgminer and bfgminer uses was upgraded to harness this optimization, however with the newer drivers "bitselect" is automatically optimized to BFI INT without us having to do it!
So, how do you fix it? simple!
1. To start, navigate to your miner's folder and look for a file that begins with "phatk" and ends with ".cl". this is the OpenCL code that makes up the kernel, but as it's a script it can be opened in any text document viewer (I highly recommend Notepad++!)
2. Inside this file may be a bit daunting, but don't worry, there's only a few small changes needed! You'll notice around line 61 (depending on your version of miner) you'll see the following (or very similar):
Code:
#ifdef BITALIGN
#pragma OPENCL EXTENSION cl_amd_media_ops : enable
#define rot(x, y) amd_bitalign(x, x, (uint)(32 - y))
// This part is not from the stock poclbm kernel. It's part of an optimization
// added in the Phoenix Miner.
// Some AMD devices have Vals[0] BFI_INT opcode, which behaves exactly like the
// SHA-256 Ch function, but provides it in exactly one instruction. If
// detected, use it for Ch. Otherwise, construct Ch out of simpler logical
// primitives.
#ifdef BFI_INT
// Well, slight problem... It turns out BFI_INT isn't actually exposed to
// OpenCL (or CAL IL for that matter) in any way. However, there is
// a similar instruction, BYTE_ALIGN_INT, which is exposed to OpenCL via
// amd_bytealign, takes the same inputs, and provides the same output.
// We can use that as a placeholder for BFI_INT and have the application
// patch it after compilation.
// This is the BFI_INT function
#define Ch(x, y, z) amd_bytealign(x,y,z)
// Ma can also be implemented in terms of BFI_INT...
#define Ma(z, x, y) amd_bytealign(z^x,y,x)
#else // BFI_INT
// Later SDKs optimise this to BFI INT without patching and GCN
// actually fails if manually patched with BFI_INT
#define Ch(x, y, z) bitselect((u)z, (u)y, (u)x)
#define Ma(x, y, z) bitselect((u)x, (u)y, (u)z ^ (u)x)
#define rotr(x, y) amd_bitalign((u)x, (u)x, (u)y)
#endif
#else // BITALIGN
#define Ch(x, y, z) (z ^ (x & (y ^ z)))
#define Ma(x, y, z) ((x & z) | (y & (x | z)))
#define rot(x, y) rotate((u)x, (u)y)
#define rotr(x, y) rotate((u)x, (u)(32-y))
#endif
#pragma OPENCL EXTENSION cl_amd_media_ops : enable
#define rot(x, y) amd_bitalign(x, x, (uint)(32 - y))
// This part is not from the stock poclbm kernel. It's part of an optimization
// added in the Phoenix Miner.
// Some AMD devices have Vals[0] BFI_INT opcode, which behaves exactly like the
// SHA-256 Ch function, but provides it in exactly one instruction. If
// detected, use it for Ch. Otherwise, construct Ch out of simpler logical
// primitives.
#ifdef BFI_INT
// Well, slight problem... It turns out BFI_INT isn't actually exposed to
// OpenCL (or CAL IL for that matter) in any way. However, there is
// a similar instruction, BYTE_ALIGN_INT, which is exposed to OpenCL via
// amd_bytealign, takes the same inputs, and provides the same output.
// We can use that as a placeholder for BFI_INT and have the application
// patch it after compilation.
// This is the BFI_INT function
#define Ch(x, y, z) amd_bytealign(x,y,z)
// Ma can also be implemented in terms of BFI_INT...
#define Ma(z, x, y) amd_bytealign(z^x,y,x)
#else // BFI_INT
// Later SDKs optimise this to BFI INT without patching and GCN
// actually fails if manually patched with BFI_INT
#define Ch(x, y, z) bitselect((u)z, (u)y, (u)x)
#define Ma(x, y, z) bitselect((u)x, (u)y, (u)z ^ (u)x)
#define rotr(x, y) amd_bitalign((u)x, (u)x, (u)y)
#endif
#else // BITALIGN
#define Ch(x, y, z) (z ^ (x & (y ^ z)))
#define Ma(x, y, z) ((x & z) | (y & (x | z)))
#define rot(x, y) rotate((u)x, (u)y)
#define rotr(x, y) rotate((u)x, (u)(32-y))
#endif
Some of this block is the problematic code for the 13.4 Catalysts, and as such we need to change it!
3. Delete the above block of code (aprrox line 49 to 86 inclusive), and replace it with the following:
Code:
#ifdef BITALIGN
#pragma OPENCL EXTENSION cl_amd_media_ops : enable
#define rot(x, y) amd_bitalign(x, x, (uint)(32 - y))
// This part is not from the stock poclbm kernel. It's part of an optimization
// added in the Phoenix Miner.
// Some AMD devices have Vals[0] BFI_INT opcode, which behaves exactly like the
// SHA-256 Ch function, but provides it in exactly one instruction. If
// detected, use it for Ch. Otherwise, construct Ch out of simpler logical
// primitives.
//We have an SDK which automatically optimizes to BFI INT, so lets do this
#define Ch(x, y, z) bitselect(z, y, x)
#define Ma(x, y, z) bitselect((u)x, (u)y, (u)z ^ (u)x)
#define rotr(x, y) amd_bitalign((u)x, (u)x, (u)y)
#else // BITALIGN
#define Ch(x, y, z) (z ^ (x & (y ^ z)))
#define Ma(x, y, z) ((x & z) | (y & (x | z)))
#define rot(x, y) rotate((u)x, (u)y)
#define rotr(x, y) rotate((u)x, (u)(32-y))
#endif
#pragma OPENCL EXTENSION cl_amd_media_ops : enable
#define rot(x, y) amd_bitalign(x, x, (uint)(32 - y))
// This part is not from the stock poclbm kernel. It's part of an optimization
// added in the Phoenix Miner.
// Some AMD devices have Vals[0] BFI_INT opcode, which behaves exactly like the
// SHA-256 Ch function, but provides it in exactly one instruction. If
// detected, use it for Ch. Otherwise, construct Ch out of simpler logical
// primitives.
//We have an SDK which automatically optimizes to BFI INT, so lets do this
#define Ch(x, y, z) bitselect(z, y, x)
#define Ma(x, y, z) bitselect((u)x, (u)y, (u)z ^ (u)x)
#define rotr(x, y) amd_bitalign((u)x, (u)x, (u)y)
#else // BITALIGN
#define Ch(x, y, z) (z ^ (x & (y ^ z)))
#define Ma(x, y, z) ((x & z) | (y & (x | z)))
#define rot(x, y) rotate((u)x, (u)y)
#define rotr(x, y) rotate((u)x, (u)(32-y))
#endif
This avoids any of the logic that should cause you problems.
4. if your miner is running, shut it down. if you have any leftover files starting in "phatk" and ending in ".bin", it's probably best to delete those.
5. Start up your miner. it should now start accepting blocks!
Hope this has helped. Note that this is modified from the following post regarding a similar problem on poclbm: https://bitcointalk.org/index.php?topic=221041.0.
Happy mining!