|
Stuck again, 0 balance and 0 payments for 3 hours.
|
|
|
|
|
"Confirmed, but still not on the balance" is growing, DDOS ongoing? :-/
|
|
|
|
At this stage with only two coins in the Keccak multipool I won't be adding a Keccak TomCoin just yet. I'd like the coins to all be available on major exchanges before making the move as TomCoin makes use of the Cryptsy API for trading, at the moment only MAX is on Cryptsy.
I understand. Today I found another two new keccak coins (galleon and sloth), they are popping up like mushrooms, lets hope we can take advantage of them soon! |
|
|
|
I've been looking at 365 coin but haven't found any exchanges yet, where is it listed? The exchange needs to have an API so I can get the latest trade data.
You are right, there is no good exchange for 365, but let's keep an eye on it ;-) What about tomcoin for keccak? I'm ready to give my sha3 hashes but I have no way to auto-exchange helix or possibly other coins you might add in the future. |
|
|
|
So, if you aren't specifying --worksize, it defaults to 256, and I wouldn't use -R 1856 (try -R 6144,1792 or throw a --worksize 256,64).
I really can't answer questions about linux - you'll have to google it, or, as I said, run it with -T -D and look through the output, it does get output somewhere in there.
So, the AMD supplied linux drivers don't work for mining? That really surprises me. I know Ubuntu is Debian based, and a colleague is running numerous machines on debian using YACMiner, and has been quite successful, even while still learning what he was doing.
I'm not using the amd supplied ones (which cause trouble when upgrading, I avoid them as much as I can) but the ones supplied by the standard ubuntu distribution (do not work as well as xedger's). |
|
|
|
Thanks for the extensive explanation!
I mistyped, I'm using raw intensity and I'm on 13.12.
The same values, if set on the command line, work fine.
It hangs only when set live.
Currently I'm getting 3.350 Kh from a 7950 and 3.730 from an r9 290.
Can you post your exact command line, and then examples of what fails? also, how much memory your cards and system have as well as the number of shaders being reported by HWInfo or GPU-z (alternatively, you could launch yacminer with -D and -T and comb through the output, but that's messy - it will eventually get added to pretty output somewhere, sometime.) rI has a similar limitation to xI - multiples of worksize are known to work, in-between values are questionable. I haven't been able to nail down what is affected and what is not - there are just too many variables. I thought it was just R7/R9 that was exempt, then thought it was driver - I know my R7 240, and R7 250 aren't limited, both on 13.12. My 7850M (unknown driver version) is not, but my 7850 desktop on 12.10 (I think) is limited. Also, no clue about what values can be valid under what driver version of linux... However, in none of the cases has the computer or software hung (I compile and run for Windows only though). For me, if it finds a value it doesn't like, and can't enqueue it onto the openCL kernel, it disables the GPU. Setting rI back to a valid value and then re-enabling the GPU always gets it back to work for me. here is the command line: -R 6144,1856 --lookup-gap 3 --buffer-size 3264,2496 --gpu-engine 1100,1100 --gpu-memclock 1250,1250 what fails is changing -R "on the fly". the first card is an r9 290 with 4GB and the second is a 7950 with 3GB (both failing), system has 8GB ram. how can I see the number of shaders on linux? when a card fails that way, if I try restarting, it goes "sick" and I need to reboot. at this point, I believe it might be a driver issue (I'm using xedgers repository, which usually has beta drivers, but with ubuntu default ones it was much worse). |
|
|
|
|
I'd like to try the keccak multipool, is tomcoin support for this algo in the works?
Also could you please add 365coin?
Thank you!
|
|
|
|
|
Thanks for the extensive explanation!
I mistyped, I'm using raw intensity and I'm on 13.12.
The same values, if set on the command line, work fine.
It hangs only when set live.
Currently I'm getting 3.350 Kh from a 7950 and 3.730 from an r9 290.
|
|
|
|
You're fast - I updated my analysis when I looked at the code you forgot --enable-scrypt in your configure statement you could just run autogen.sh too (unless you don't like things easy  ) thanks! it's working now, about the same hashrate than 3.4 but I need to tweak a little bit to see if I can get better. the problem I'm having now is that every time I change the xintensity the corresponding gpu halts and I must reboot. changing the legacy intensity value doesn't seem to suffer the same issue, though. |
|
|
|
Disclaimer - update to yacminer 3.5.0 is required to follow this advice...
You need to allocate more memory. 760 MB is not enough - Double it and go higher if you can. Use "--buffer-size 1664" instead of your thread concurrency setting. That will let you use more shaders without running out of memory. If you do that, you can push -R to ~3300 without any other changes to your config
tried compiling it now: yacminer.c: In function ‘GetNfactor’: yacminer.c:1090:11: error: ‘opt_n_scrypt’ undeclared (first use in this function) else if (opt_n_scrypt) ^ yacminer.c:1090:11: note: each undeclared identifier is reported only once for each function it appears in yacminer.c: In function ‘curses_print_status’: yacminer.c:2297:27: error: ‘opt_n_scrypt’ undeclared (first use in this function) if (opt_scrypt_chacha || opt_n_scrypt) ^ yacminer.c: In function ‘main’: yacminer.c:7807:16: error: lvalue required as unary ‘&’ operand opt_set_bool(&opt_scrypt); ^ yacminer.c:7808:20: error: ‘opt_n_scrypt’ undeclared (first use in this function) opt_set_invbool(&opt_n_scrypt); ^ yacminer.c:7813:16: error: lvalue required as unary ‘&’ operand opt_set_bool(&opt_scrypt); ^ yacminer.c:7814:19: error: lvalue required as unary ‘&’ operand opt_set_invbool(&opt_scrypt_chacha); ^ you need to have the automake tools and dependancies and then run the autogen.sh before running make. It looks like it's going off an old config. I run it on a new folder like this: ./autogen.sh CFLAGS="-march=native -O3" ./configure make tried also running "make clean" but same problem. other cgminer variants and yacminer 3.4 do compile fine. EDIT: if I don't run configure after autogen.sh, it works :-) |
|
|
|
Disclaimer - update to yacminer 3.5.0 is required to follow this advice...
You need to allocate more memory. 760 MB is not enough - Double it and go higher if you can. Use "--buffer-size 1664" instead of your thread concurrency setting. That will let you use more shaders without running out of memory. If you do that, you can push -R to ~3300 without any other changes to your config
tried compiling it now: yacminer.c: In function ‘GetNfactor’: yacminer.c:1090:11: error: ‘opt_n_scrypt’ undeclared (first use in this function) else if (opt_n_scrypt) ^ yacminer.c:1090:11: note: each undeclared identifier is reported only once for each function it appears in yacminer.c: In function ‘curses_print_status’: yacminer.c:2297:27: error: ‘opt_n_scrypt’ undeclared (first use in this function) if (opt_scrypt_chacha || opt_n_scrypt) ^ yacminer.c: In function ‘main’: yacminer.c:7807:16: error: lvalue required as unary ‘&’ operand opt_set_bool(&opt_scrypt); ^ yacminer.c:7808:20: error: ‘opt_n_scrypt’ undeclared (first use in this function) opt_set_invbool(&opt_n_scrypt); ^ yacminer.c:7813:16: error: lvalue required as unary ‘&’ operand opt_set_bool(&opt_scrypt); ^ yacminer.c:7814:19: error: lvalue required as unary ‘&’ operand opt_set_invbool(&opt_scrypt_chacha); ^ |
|
|
|
All the talk about power costs is one of the reasons im switching to GS5s. The other is air-conditioning. I live in the Arizona desert, and it's already getting hot enough that I have to dial-back my GPU rigs to between 8-13 intensity from noon to 9pm because of the heat. The GPU's ran fine all winter in my garage, but now it's getting ridiculous to try and maintain them in that environment. Moving inside isn't going to be acceptable from a noise perspective.
I suppose I could go out and buy rack-space at some co-lo, but that would eat into the revenue stream.
For me, I pretty much have to move to ASIC because I won't be able to run the GPUs effectively during the summer months.
and if you move it inside, you will double your electricity use, because of the added air conditioning needed ;-) |
|
|
|
|
Hello, just wanted to know if the miners of the current shipping batch still have the "hang after one hour" problem I've seen discussed on some threads.
|
|
|
|
Max pool stuck?
Please, MAX is going up and I didn't get any payout last night! :-( |
|
|
|
Here's what I got after 24 hours mining with 3.750Mhash rig at CoinShift
It's about 0.00729BTC/MHash !!! Just WOW !! so this is wrong: http://poolpicker.eu/ |
|
|
|
what happend with diff? just shot up from around the 40k to 100k
*edit just some flaw in the network i gues it's already back to normal
KGW? |
|
|
|
|
Max pool stuck at 6 hours ago but still accepting shares = 6 hours of waisted work???
|
|
|
|
My BEST settings for minig Maxcoin (MAX) with mining rig with 3x Sapphire R9 290X 4GB DDR5 (5000MHz)
I've just started mining max using the dwarfpool pools but after 2 hours i've receive no MaxCoins, how long do you normally to have to wait for a payout? With exactly the same configuration I get payments from 1gh every 20 minutes. 1GH has much higher hashrate than dwarf, so the payments are more stable. but in the long run it doesn't matter: what matters is a lower fee, instead  |
|
|
|
|
Show Posts
