[MTC] High Performance GPU Miner for Metiscoin (Updated - 19 Feb 2014) - page 3.

gigawatt

full member

Activity: 168

Merit: 100

Quote from: ~Money~ on February 13, 2014, 05:54:34 AM

here is wot u need:
1)
http://s14.postimg.org/afbilk1pt/Untitled1.jpg

http://s4.postimg.org/k53wlvl8t/Untitled.jpg

2) latest version

3)
start /low xptminer.exe -o ypool.net -u user -p pass

hope u can bring this miner online too, it can increase my mining speed more than 1mh Grin

Thanks for the info! I'll start looking into it.

Is that the 32 or 64-bit build?

aakashkumar

full member

Activity: 157

Merit: 100

Your Miner works Great with 58xx and 59XX ,

Can you do something For PTS ?

Crybaby84

newbie

Activity: 2

Merit: 0

With my R9 290 i cannot seem to get any higher rate than around 7000 to 8000 Khash. Seems kind of low to me Huh

.
Somebody got a clue on how to get a better rate? I tried to play around with the -s parameter, but doesnt realy affect the hashrate.

To be complete:

Intel i5 4670K, 16GB memory, Win 8.1 X64

Startup command
:BEGIN
start /low /wait xptminer.exe -o ypool.net -u Crybaby84.M1 -p X -d 0.5 -s 2
timeout /t 30
GOTO BEGIN
pause

Version
xptMiner (v1.1) + GPU Metiscoin Miner (v0.4gg)
Catalyst 14.1 (13.35.1005-140131a-167669E-ATI)

Screenshot with info:
http://postimg.org/image/8lud2ngpx/

Any help will be appreciated !! Thanks.

~Money~

hero member

Activity: 1132

Merit: 536

Quote from: gigawatt on February 11, 2014, 11:43:52 AM

Quote from: ~Money~ on February 11, 2014, 11:09:55 AM

gigawatt can u help me fix this:

http://s4.postimg.org/r6amus7rx/image.jpg

its stat of less than 1 minutes with a 7770 on win7 x64
and im getting 0000 shares in ypool with this miner, but it works fine on few more PCs

I can do my best to help. I'll need three things from you:

1) When you run the miner, what's the first few lines that pop up on screen? It should look something like this:

Code:

Initing device 0...
Initializing GPU 0

============================================================
Device information for: Cypress
CL_DEVICE_GLOBAL_MEM_SIZE:            1048576 kb
CL_DEVICE_GLOBAL_MEM_CACHE_SIZE:            0 kb
CL_DEVICE_LOCAL_MEM_SIZE:                  32 kb
CL_DEVICE_LOCAL_MEM_TYPE:           CL_LOCAL
CL_DEVICE_MAX_WORK_GROUP_SIZE:            256

2) What's the version number that shows when you run the miner? The newest version should show

Code:

xptMiner (v1.1) + GPU Metiscoin Miner (v0.3gg)

3) What command do you run to launch the miner?

here is wot u need:
1)
http://s14.postimg.org/afbilk1pt/Untitled1.jpg

http://s4.postimg.org/k53wlvl8t/Untitled.jpg

2) latest version

3)
start /low xptminer.exe -o ypool.net -u user -p pass

hope u can bring this miner online too, it can increase my mining speed more than 1mh Grin

jk_14

legendary

Activity: 1292

Merit: 1000

Quote from: gigawatt on February 12, 2014, 05:20:23 PM

Quote from: jk_14 on February 12, 2014, 02:50:33 PM

I did it.

root@bamt-miner:~/xptMiner-master# ./xptminer -o ypool.net -u xxx.w11 -p xxx -d 0 | grep total
kHash/s: 10747.90 Shares total: 300 (Valid: 0, Invalid: 2)
kHash/s: 10846.21 Shares total: 651 (Valid: 0, Invalid: 2)
kHash/s: 10857.13 Shares total: 986 (Valid: 0, Invalid: 4)
^C
root@bamt-miner:~/xptMiner-master#

card: Gigabyte 7950 WF3
OS: BAMT Linux 32bit

https://bitcointalksearch.org/topic/m.5056624

The problem isn't with the *.cl files. It's that (currently) the kHash/s, total shares, and invalid shared are stored as a 64-bit number.
When you compile on a 32-bit system, you end up having data spill over. That's why your shares/invalid count is all over the place. It should still mine properly, but it's just graphically bad.

I'm currently working on a fix and I'll push the changes to github later today.

Now this issue is OK,
but I have two more.

1. miner disconnects from ypool.net after 5-10 minutes
2. no incrementation of "Unconfirmed (MTC) 0.00000000",
worker was connected, active, but no single result of mining at all...

kHash/s: 43515.90 Shares total: 70280 (Valid: 1454, Invalid: 68826)
kHash/s: 43525.80 Shares total: 71626 (Valid: 2713, Invalid: 68913)
root@bamt-miner:~/test/xptMiner-gpu#

no information about exit code....

thiec

hero member

Activity: 854

Merit: 502

Quote from: gigawatt on February 12, 2014, 11:50:19 AM

Never mind, I figured it out. It's a graphical bug specific to the 32-bit build. You're actually getting shares, but it's incrementing the wrong variable. This is happening because the "totalShareCount" and "invalidShareCount" variables are defined as 64-bit numbers which doesn't play well when treated as 32-bit numbers.

I'll have that fixed by the end of the day. In the mean time, continue mining. It's only a graphical bug. You're actually getting shares. You can verify that on yPool if you'd like.

v1.5 x86 work great Grin

gigawatt

full member

Activity: 168

Merit: 100

Quote from: ddkkddkk on February 12, 2014, 10:39:45 PM

Like this...

Wow, that's... not good.

If you could get me this information I might be able to help out some.

ddkkddkk

newbie

Activity: 8

Merit: 0

http://i.imgur.com/2es0LiT.png
Like this...

gigawatt

full member

Activity: 168

Merit: 100

Quote from: ddkkddkk on February 12, 2014, 08:58:52 PM

x86 and x64 get a lot of invalid shares... Sad

Define "a lot"? I'd normally expect 2-4% invalid.

ddkkddkk

newbie

Activity: 8

Merit: 0

x86 and x64 get a lot of invalid shares... Sad

gigawatt

full member

Activity: 168

Merit: 100

The "invalid share" issue has been fixed! Please update your miners.

In addition, you power users might want to check out the "-s" flag. It lets you specify the GPU load per hash pass.
It multiplies the work load by 2^X, so "-s 1" does twice the work, "-s 2" does four times the work, and "-s -1" does half the work, etc.

For more information, run the miner without any parameters. The help screen will tell you more.

gigawatt

full member

Activity: 168

Merit: 100

Quote from: jk_14 on February 12, 2014, 02:50:33 PM

I did it.

root@bamt-miner:~/xptMiner-master# ./xptminer -o ypool.net -u xxx.w11 -p xxx -d 0 | grep total
kHash/s: 10747.90 Shares total: 300 (Valid: 0, Invalid: 2)
kHash/s: 10846.21 Shares total: 651 (Valid: 0, Invalid: 2)
kHash/s: 10857.13 Shares total: 986 (Valid: 0, Invalid: 4)
kHash/s: 10878.98 Shares total: 1294 (Valid: 0, Invalid: 6)
kHash/s: 10865.87 Shares total: 1589 (Valid: 0, Invalid: 5)
kHash/s: 10857.13 Shares total: 1964 (Valid: 0, Invalid: 7)
kHash/s: 10869.61 Shares total: 2322 (Valid: 0, Invalid: 1)
kHash/s: 10878.98 Shares total: 2643 (Valid: 0, Invalid: 3)
kHash/s: 10886.26 Shares total: 2955 (Valid: 0, Invalid: 73)
kHash/s: 10892.08 Shares total: 3281 (Valid: 0, Invalid: 4)
kHash/s: 10896.85 Shares total: 3623 (Valid: 0, Invalid: 115)
^C
root@bamt-miner:~/xptMiner-master#

card: Gigabyte 7950 WF3
OS: BAMT Linux 32bit

https://bitcointalksearch.org/topic/m.5056624

I have even try to replace *.cl from win32 into source tree, and recompile

No success...

The problem isn't with the *.cl files. It's that (currently) the kHash/s, total shares, and invalid shared are stored as a 64-bit number.
When you compile on a 32-bit system, you end up having data spill over. That's why your shares/invalid count is all over the place. It should still mine properly, but it's just graphically bad.

I'm currently working on a fix and I'll push the changes to github later today.

jk_14

legendary

Activity: 1292

Merit: 1000

Quote from: gigawatt on February 12, 2014, 02:16:38 PM

Quote from: jk_14 on February 12, 2014, 12:38:01 PM

Quote from: jk_14 on February 12, 2014, 06:11:14 AM

It would be very nice to have a i686 (32bit) compability for all old good BAMT users...

Quote from: gigawatt on February 12, 2014, 09:07:03 AM

There's already a 32-bit version released. It's the one labeled xptMiner-GPU-x86-v1.X.zip

But it's windows 32bit binaries, BAMT is linux!

Sorry, I wasn't familiar with BAMT. You should be able to compile the program from the source code. It's available in the github repo (see the first post).

I did it.

root@bamt-miner:~/xptMiner-master# ./xptminer -o ypool.net -u xxx.w11 -p xxx -d 0 | grep total
kHash/s: 10747.90 Shares total: 300 (Valid: 0, Invalid: 2)
kHash/s: 10846.21 Shares total: 651 (Valid: 0, Invalid: 2)
kHash/s: 10857.13 Shares total: 986 (Valid: 0, Invalid: 4)
kHash/s: 10878.98 Shares total: 1294 (Valid: 0, Invalid: 6)
kHash/s: 10865.87 Shares total: 1589 (Valid: 0, Invalid: 5)
kHash/s: 10857.13 Shares total: 1964 (Valid: 0, Invalid: 7)
kHash/s: 10869.61 Shares total: 2322 (Valid: 0, Invalid: 1)
kHash/s: 10878.98 Shares total: 2643 (Valid: 0, Invalid: 3)
kHash/s: 10886.26 Shares total: 2955 (Valid: 0, Invalid: 73)
kHash/s: 10892.08 Shares total: 3281 (Valid: 0, Invalid: 4)
kHash/s: 10896.85 Shares total: 3623 (Valid: 0, Invalid: 115)
^C
root@bamt-miner:~/xptMiner-master#

card: Gigabyte 7950 WF3
OS: BAMT Linux 32bit

https://bitcointalksearch.org/topic/m.5056624

I have even try to replace *.cl from win32 into source tree, and recompile

No success...

gigawatt

full member

Activity: 168

Merit: 100

Quote from: jk_14 on February 12, 2014, 12:38:01 PM

Quote from: jk_14 on February 12, 2014, 06:11:14 AM

It would be very nice to have a i686 (32bit) compability for all old good BAMT users...

Quote from: gigawatt on February 12, 2014, 09:07:03 AM

There's already a 32-bit version released. It's the one labeled xptMiner-GPU-x86-v1.X.zip

But it's windows 32bit binaries, BAMT is linux!

Sorry, I wasn't familiar with BAMT. You should be able to compile the program from the source code. It's available in the github repo (see the first post).

fenghush

sr. member

Activity: 658

Merit: 250

Hot damn, with that new update its profitable to mine solo, found 3 blocks on ypool in no time lol.

jk_14

legendary

Activity: 1292

Merit: 1000

Quote from: jk_14 on February 12, 2014, 06:11:14 AM

It would be very nice to have a i686 (32bit) compability for all old good BAMT users...

Quote from: gigawatt on February 12, 2014, 09:07:03 AM

There's already a 32-bit version released. It's the one labeled xptMiner-GPU-x86-v1.X.zip

But it's windows 32bit binaries, BAMT is linux!

Meizirkki

hero member

Activity: 616

Merit: 500

Quote from: gigawatt on February 09, 2014, 11:40:48 PM

I wish I had an Intel chip to test on. It would probably make thing easier than guess and check.

What happens if you add the #pragma line to the top of each of the .cl files?

I tested you new versionon my Intel. Wink

Same looking output even with #pragma everywhere:

Code:

Initing device 0...
Initializing GPU 1

======================================================================
Device information for: Iris Pro
CL_DEVICE_GLOBAL_MEM_SIZE:            1048576 kb
CL_DEVICE_GLOBAL_MEM_CACHE_SIZE:            0 kb
CL_DEVICE_LOCAL_MEM_SIZE:                  64 kb
CL_DEVICE_LOCAL_MEM_TYPE:            CL_LOCAL
CL_DEVICE_MAX_WORK_GROUP_SIZE:            512
CL_DEVICE_ENDIAN_LITTLE:                    1
CL_DEVICE_ADDRESS_BITS:                    64
CL_DEVICE_OPENCL_C_VERSION:         OpenCL C 1.2 
======================================================================

Compiling OpenCL code... this may take 3-5 minutes
ERROR: -11, CL_BUILD_PROGRAM_FAILURE, if there is a failure to build the program executable. This error will be returned if clBuildProgram does not return until the build has completed.
--- Build log ---
Cannot select: 0x7fbe7ba49910: i64 = rotl 0x7fbe7bdac710, 0x7fbe7b95fe10 [ID=16912]
  0x7fbe7bdac710: i64 = bitcast 0x7fbe7b9a3110 [ID=16891]
    0x7fbe7b9a3110: v2i32 = IGILISD::MOVSWZ 0x7fbe7b9a2710, 0x7fbe7b9a2810, 0x7fbe7ba5f310, 0x7fbe7ba5f310 [ID=16857]
      0x7fbe7b9a2710: i32 = xor 0x7fbe7b906910, 0x7fbe7ba47b10 [ID=16816]
        0x7fbe7b906910: i32 = IGILISD::LO_COPY 0x7fbe7bdab410 [ID=16782]
          0x7fbe7bdab410: i64 = bitcast 0x7fbe7b9be410 [ID=16760]
            0x7fbe7b9be410: v2i32 = IGILISD::MOVSWZ 0x7fbe7b9bd710, 0x7fbe7b9bd910, 0x7fbe7ba5f310, 0x7fbe7ba5f310 [ID=16739]
              0x7fbe7b9bd710: i32 = xor 0x7fbe7ba49410, 0x7fbe7b9bd410 [ID=16703]
                0x7fbe7ba49410: i32 = IGILISD::LO_COPY 0x7fbe7bdaab10 [ID=16685]
                  0x7fbe7bdaab10: i64 = bitcast 0x7fbe7b9c9910 [ID=16678]

                0x7fbe7b9bd410: i32 = IGILISD::LO_COPY 0x7fbe7bda9810 [ID=16572]
                  0x7fbe7bda9810: i64 = bitcast 0x7fbe7b9d7110 [ID=16561]

              0x7fbe7b9bd910: i32 = xor 0x7fbe7b9bd310, 0x7fbe7b9bd610 [ID=16702]
                0x7fbe7b9bd310: i32 = IGILISD::HI_COPY 0x7fbe7bdaab10 [ID=16684]
                  0x7fbe7bdaab10: i64 = bitcast 0x7fbe7b9c9910 [ID=16678]

                0x7fbe7b9bd610: i32 = IGILISD::HI_COPY 0x7fbe7bda9810 [ID=16571]
                  0x7fbe7bda9810: i64 = bitcast 0x7fbe7b9d7110 [ID=16561]

              0x7fbe7ba5f310: i32 = Constant<0> [ORD=5975] [ID=42]
              0x7fbe7ba5f310: i32 = Constant<0> [ORD=5975] [ID=42]
        0x7fbe7ba47b10: i32 = IGILISD::LO_COPY 0x7fbe7bda8f10 [ID=16520]
          0x7fbe7bda8f10: i64 = bitcast 0x7fbe7b9e2810 [ID=16495]
            0x7fbe7b9e2810: v2i32 = IGILISD::MOVSWZ 0x7fbe7b9e0010, 0x7fbe7b9e1c10, 0x7fbe7ba5f310, 0x7fbe7ba5f310 [ID=16479]
              0x7fbe7b9e0010: i32 = xor 0x7fbe7ba42710, 0x7fbe7b9dfc10 [ID=16457]
                0x7fbe7ba42710: i32 = IGILISD::LO_COPY 0x7fbe7bda7610 [ID=16407]
                  0x7fbe7bda7610: i64 = bitcast 0x7fbe7b954010 [ID=16373]

                0x7fbe7b9dfc10: i32 = IGILISD::LO_COPY 0x7fbe7ba3fe10 [ID=16159]
                  0x7fbe7ba3fe10: i64 = rotl 0x7fbe7bda5310, 0x7fbe7b961210 [ID=16114]


              0x7fbe7b9e1c10: i32 = xor 0x7fbe7b9dfa10, 0x7fbe7b9dfe10 [ID=16456]
                0x7fbe7b9dfa10: i32 = IGILISD::HI_COPY 0x7fbe7bda7610 [ID=16406]
                  0x7fbe7bda7610: i64 = bitcast 0x7fbe7b954010 [ID=16373]

                0x7fbe7b9dfe10: i32 = IGILISD::HI_COPY 0x7fbe7ba3fe10 [ID=16158]
                  0x7fbe7ba3fe10: i64 = rotl 0x7fbe7bda5310, 0x7fbe7b961210 [ID=16114]


              0x7fbe7ba5f310: i32 = Constant<0> [ORD=5975] [ID=42]
              0x7fbe7ba5f310: i32 = Constant<0> [ORD=5975] [ID=42]
      0x7fbe7b9a2810: i32 = xor 0x7fbe7b9a1b10, 0x7fbe7b9a2510 [ID=16811]
        0x7fbe7b9a1b10: i32 = IGILISD::HI_COPY 0x7fbe7bdab410 [ID=16781]
          0x7fbe7bdab410: i64 = bitcast 0x7fbe7b9be410 [ID=16760]
            0x7fbe7b9be410: v2i32 = IGILISD::MOVSWZ 0x7fbe7b9bd710, 0x7fbe7b9bd910, 0x7fbe7ba5f310, 0x7fbe7ba5f310 [ID=16739]
              0x7fbe7b9bd710: i32 = xor 0x7fbe7ba49410, 0x7fbe7b9bd410 [ID=16703]
                0x7fbe7ba49410: i32 = IGILISD::LO_COPY 0x7fbe7bdaab10 [ID=16685]
                  0x7fbe7bdaab10: i64 = bitcast 0x7fbe7b9c9910 [ID=16678]

                0x7fbe7b9bd410: i32 = IGILISD::LO_COPY 0x7fbe7bda9810 [ID=16572]
                  0x7fbe7bda9810: i64 = bitcast 0x7fbe7b9d7110 [ID=16561]

              0x7fbe7b9bd910: i32 = xor 0x7fbe7b9bd310, 0x7fbe7b9bd610 [ID=16702]
                0x7fbe7b9bd310: i32 = IGILISD::HI_COPY 0x7fbe7bdaab10 [ID=16684]
                  0x7fbe7bdaab10: i64 = bitcast 0x7fbe7b9c9910 [ID=16678]

                0x7fbe7b9bd610: i32 = IGILISD::HI_COPY 0x7fbe7bda9810 [ID=16571]
                  0x7fbe7bda9810: i64 = bitcast 0x7fbe7b9d7110 [ID=16561]

              0x7fbe7ba5f310: i32 = Constant<0> [ORD=5975] [ID=42]
              0x7fbe7ba5f310: i32 = Constant<0> [ORD=5975] [ID=42]
        0x7fbe7b9a2510: i32 = IGILISD::HI_COPY 0x7fbe7bda8f10 [ID=16519]
          0x7fbe7bda8f10: i64 = bitcast 0x7fbe7b9e2810 [ID=16495]
            0x7fbe7b9e2810: v2i32 = IGILISD::MOVSWZ 0x7fbe7b9e0010, 0x7fbe7b9e1c10, 0x7fbe7ba5f310, 0x7fbe7ba5f310 [ID=16479]
              0x7fbe7b9e0010: i32 = xor 0x7fbe7ba42710, 0x7fbe7b9dfc10 [ID=16457]
                0x7fbe7ba42710: i32 = IGILISD::LO_COPY 0x7fbe7bda7610 [ID=16407]
                  0x7fbe7bda7610: i64 = bitcast 0x7fbe7b954010 [ID=16373]

                0x7fbe7b9dfc10: i32 = IGILISD::LO_COPY 0x7fbe7ba3fe10 [ID=16159]
                  0x7fbe7ba3fe10: i64 = rotl 0x7fbe7bda5310, 0x7fbe7b961210 [ID=16114]


              0x7fbe7b9e1c10: i32 = xor 0x7fbe7b9dfa10, 0x7fbe7b9dfe10 [ID=16456]
                0x7fbe7b9dfa10: i32 = IGILISD::HI_COPY 0x7fbe7bda7610 [ID=16406]
                  0x7fbe7bda7610: i64 = bitcast 0x7fbe7b954010 [ID=16373]

                0x7fbe7b9dfe10: i32 = IGILISD::HI_COPY 0x7fbe7ba3fe10 [ID=16158]
                  0x7fbe7ba3fe10: i64 = rotl 0x7fbe7bda5310, 0x7fbe7b961210 [ID=16114]


              0x7fbe7ba5f310: i32 = Constant<0> [ORD=5975] [ID=42]
              0x7fbe7ba5f310: i32 = Constant<0> [ORD=5975] [ID=42]
      0x7fbe7ba5f310: i32 = Constant<0> [ORD=5975] [ID=42]
      0x7fbe7ba5f310: i32 = Constant<0> [ORD=5975] [ID=42]
  0x7fbe7b95fe10: i64 = bitcast 0x7fbe7ba41f10 [ID=373]
    0x7fbe7ba41f10: v2i32 = IGILISD::MOVSWZ 0x7fbe7ba4f910, 0x7fbe7ba5f310, 0x7fbe7ba5f310, 0x7fbe7ba5f310 [ID=238]
      0x7fbe7ba4f910: i32 = Constant<36> [ID=83]
      0x7fbe7ba5f310: i32 = Constant<0> [ORD=5975] [ID=42]
      0x7fbe7ba5f310: i32 = Constant<0> [ORD=5975] [ID=42]
      0x7fbe7ba5f310: i32 = Constant<0> [ORD=5975] [ID=42]
In function: metiscoin_process
---  End log  ---
Assertion failed: (!error), function loadProgramFromStrings, file xptMiner/OpenCLObjects.cpp, line 362.
Abort trap: 6

CPU performace is excellent tho. Hasrate almost doubled from last release.

gigawatt

full member

Activity: 168

Merit: 100

Quote from: gigawatt on February 12, 2014, 10:07:31 AM

Quote from: thiec on February 12, 2014, 09:53:20 AM

I hope this will help

So close. I need the stuff at the very start of the program run. It should look like this: https://bitcointalksearch.org/topic/m.4986799

Do you happen to get shares on yPool? Normally if you get an invalid share it will actually say "Invalid Share" followed by a reason.

Never mind, I figured it out. It's a graphical bug specific to the 32-bit build. You're actually getting shares, but it's incrementing the wrong variable. This is happening because the "totalShareCount" and "invalidShareCount" variables are defined as 64-bit numbers which doesn't play well when treated as 32-bit numbers.

I'll have that fixed by the end of the day. In the mean time, continue mining. It's only a graphical bug. You're actually getting shares. You can verify that on yPool if you'd like.

gigawatt

full member

Activity: 168

Merit: 100

Quote from: thiec on February 12, 2014, 10:20:10 AM

I dont have the screen like you refer to.
I mean there is no information for my CPU, only GPU

Here the screen pop up from the start

That's the correct screen, but the wrong version. Download the debug build and send the screenshot from that.
You can get the debug build from here: https://www.dropbox.com/sh/tan8yprhoaq6o1q/pqgHVLVkCT/xptMiner-GPU-v1.4-debug.zip

thiec

hero member

Activity: 854

Merit: 502

Quote from: gigawatt on February 12, 2014, 10:07:31 AM

Quote from: thiec on February 12, 2014, 09:53:20 AM

I hope this will help

So close. I need the stuff at the very start of the program run. It should look like this: https://bitcointalksearch.org/topic/m.4986799

Do you happen to get shares on yPool? Normally if you get an invalid share it will actually say "Invalid Share" followed by a reason.

I dont have the screen like you refer to.
I mean there is no information for my CPU, only GPU

Here the screen pop up from the start

Topic: [MTC] High Performance GPU Miner for Metiscoin (Updated - 19 Feb 2014) - page 3. (Read 19667 times)