crash with a 1.6. 1.5 works fine. Could you post the information from this post? It would make troubleshooting a lot easier.
|
|
|
I've updated my GPU miner for MTS! It's now 15-20% faster than before! (I went from 11,150 kHash/s to 13,500 kHash/s) Download the latest version from the beginning of this thread. Enjoy!
|
|
|
I've updated my GPU miner for MTS! It's now 15-20% faster than before! (I went from 11,150 kHash/s to 13,500 kHash/s) You can follow the updates at the MTS GPU miner thread or download the latest version from below: Source code:https://github.com/llamasoft/xptMiner-gpuWindows binaries (32 and 64-bit):Mega.co.nzDropbox mirrorLinux users: download the source from github and compile. git clone https://github.com/llamasoft/xptMiner-gpu.git cd xptMiner make
|
|
|
still error: g++ -Wall -Wextra -O2 -fomit-frame-pointer -march=native -L/usr/local/lib -L/usr/lib -I/usr/local/include -I/usr/include -IxptMiner/includes/ -o xptminer xptMiner/ticker.o xptMiner/main.o xptMiner/sha2.o xptMiner/xptClient.o xptMiner/protosharesMiner.o xptMiner/primecoinMiner.o xptMiner/keccak.o xptMiner/metis.o xptMiner/shavite.o xptMiner/metiscoinMiner.o xptMiner/scrypt.o xptMiner/scryptMinerCPU.o xptMiner/xptClientPacketHandler.o xptMiner/xptPacketbuffer.o xptMiner/xptServer.o xptMiner/xptServerPacketHandler.o xptMiner/transaction.o xptMiner/OpenCLObjects.o xptMiner/jhlib.o -lrt -lOpenCL -flto /usr/bin/ld: xptMiner/main.o: undefined reference to symbol 'pthread_create@@GLIBC_2.2.5' /usr/lib/libpthread.so.0: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status Makefile:102: recipe for target 'xptminer' failed make: *** [xptminer] Error 1
Try it again. Somehow I forgot to include "-lpthread" in the compile options.
|
|
|
The debug information has been bundled into the 1.5 build. I should have made that a bit more clear, sorry about that. If you could post the log information up until the crash, it would be very appreciated.
|
|
|
compile error in Archlinux. cpu : AMD Athlon(tm) II X3 440 Processor display card: microstar hd7850 driver: catalyst 14.1 g++ -c -static -Wall -Wextra -std=c++0x -O2 -fomit-frame-pointer -march=native -I/usr/local/include -I/usr/include -IxptMiner/includes/ xptMiner/main.cpp -o xptMiner/main.o In file included from xptMiner/global.h:77:0, from xptMiner/main.cpp:1: xptMiner/OpenCLObjects.h:77:9: error: extra qualification 'OpenCLKernel::' on member 'getPreferredWorkGroupSize' [-fpermissive] size_t OpenCLKernel::getPreferredWorkGroupSize(OpenCLDevice* device); ^ Makefile:93: recipe for target 'xptMiner/main.o' failed make: *** [xptMiner/main.o] Error 1
Whoops, looks like one of my tweaks broke something. I pushed a fix to github, you should be good to go.
|
|
|
Dude you just made my day. You just fixed my problem. Thank you very much and as I earn some coins for sure I am going to donate to you. NVIDIA GEFORCE GT 540M - 2GB Core: 672 MHz Shaders: 1344MHz Memory: 900MHz https://i.imgur.com/2tp8lGC.png?1Btw what does -s -2 means? You just don't know how happy I am. Again thank you very much ! The -s flag... normally the miner does 512,000 hashes on the GPU before taking a quick break to check the results. The -s flag lets you adjust the number of hashes before taking a break. The exact amount is HEX(0x80000) * 2^N. When you set -s to "-2", it means the work load is only HEX(0x80000)/4 so it takes breaks more often. The end result in your case is that Windows no longer thinks the GPU crashed from being unresponsive.
|
|
|
win7 x64 radeon hd770 edit: just sth happened, windows freezes and after a driver crash, miner started working on 200kh [changing driver and will update post] edit2: driver updated, miner started to work at 6mh speed for few seconds, and boooooom windows crashed =)) [ brb ) ] edit3: seems everything is working f9 now, miner works at 100% but when i feel some decrease in vga performance while im working with autocad (of course when miner is not running :-" ) which might be driver issues :-? anyway, 6mh more added to my power hash rate thnx gigawatt Glad the driver update fixed the problem. I've had Windows freeze once or twice during testing, but a reboot usually fixes it. What's your overall hash rate now? (So I can add it to the benchmarks?)
|
|
|
With my R9 290 i cannot seem to get any higher rate than around 7000 to 8000 Khash. Seems kind of low to me . 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 Screenshot with info:http://postimg.org/image/8lud2ngpx/Any help will be appreciated !! Thanks. That looks fairly decent. Do you happen to know your card's clock speeds? Check GPUz while the miner is running: http://www.techpowerup.com/gpuz/I found out the hard way that cgminer never reset my clock speeds so the memory was badly un-derclocked. It ended up cutting my hash speed in half.
|
|
|
Thanks for the info! I'll start looking into it. Is that the 32 or 64-bit build?
|
|
|
Like this...
Wow, that's... not good. If you could get me this information I might be able to help out some.
|
|
|
x86 and x64 get a lot of invalid shares... Define "a lot"? I'd normally expect 2-4% invalid.
|
|
|
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.
|
|
|
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://bitcointalk.org/index.php?topic=447298.msg5056624#msg5056624I 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.
|
|
|
It would be very nice to have a i686 (32bit) compability for all old good BAMT users...
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).
|
|
|
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.
|
|
|
A10-5600K APU video 2600~2900 BUT use hd 4890 getting a compile error!
The Radeon HD 4000 series doesn't fully support OpenCL, so the miner will not work on it no matter what. Sorry mate.
|
|
|
|