|
Wow the new miner is so fast! it's crunching at more than 20 Gh/s per card LoL!
Anyone with the same problem?
|
|
|
|
Hi, I am trying to compile on Mac, but I receive this error when I 'make' make[3]: Nothing to be done for `all-am'.
gcc -DHAVE_CONFIG_H -I. -pthread -Qunused-arguments -falign-loops=16 -falign-functions=16 -falign-jumps=16 -falign-labels=16 -Ofast -flto -fuse-linker-plugin -funroll-loops -fvariable-expansion-in-unroller -ftree-loop-if-convert-stores -fmerge-all-constants -fbranch-target-load-optimize2 -fsched2-use-superblocks -maes -MT minerd-cpu-miner.o -MD -MP -MF .deps/minerd-cpu-miner.Tpo -c -o minerd-cpu-miner.o `test -f 'cpu-miner.c' || echo './'`cpu-miner.c
clang: error: unknown argument: '-falign-loops=16' [-Wunused-command-line-argument-hard-error-in-future]
clang: note: this will be a hard error (cannot be downgraded to a warning) in the future
clang: error: unknown argument: '-falign-jumps=16' [-Wunused-command-line-argument-hard-error-in-future]
clang: note: this will be a hard error (cannot be downgraded to a warning) in the future
clang: error: unknown argument: '-falign-labels=16' [-Wunused-command-line-argument-hard-error-in-future]
clang: note: this will be a hard error (cannot be downgraded to a warning) in the future
clang: error: unknown argument: '-fuse-linker-plugin' [-Wunused-command-line-argument-hard-error-in-future]
clang: note: this will be a hard error (cannot be downgraded to a warning) in the future
clang: error: unknown argument: '-fvariable-expansion-in-unroller' [-Wunused-command-line-argument-hard-error-in-future]
clang: note: this will be a hard error (cannot be downgraded to a warning) in the future
clang: error: unknown argument: '-ftree-loop-if-convert-stores' [-Wunused-command-line-argument-hard-error-in-future]
clang: note: this will be a hard error (cannot be downgraded to a warning) in the future
clang: error: unknown argument: '-fbranch-target-load-optimize2' [-Wunused-command-line-argument-hard-error-in-future]
clang: note: this will be a hard error (cannot be downgraded to a warning) in the future
clang: error: unknown argument: '-fsched2-use-superblocks' [-Wunused-command-line-argument-hard-error-in-future]
clang: note: this will be a hard error (cannot be downgraded to a warning) in the future
make[2]: *** [minerd-cpu-miner.o] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
I have the dependencies installed. 'autogen.sh' and 'configure' run without errors. I am having the same issue as this person but I see no one has suggested a solution. Could someone help me out with this. I was told to use a makefile from cpuminer-multi and thought all I would need to do is copy it from there and paste into wolfs-m7m folder but when I attempted to configure/make it it only hit me with errors. It's not meant for clang - use GCC, or remove the arguments clang takes issue with. BTW I compiled it with clang on linux some months ago and it was slower. |
|
|
|
So now they pay double. Poloniex doing a code review on how single confirm tx's can work securely on VNL didn't even bump the price decently, the altscene has gone terribly low in investors and in people who have eyes for quality coding.
Just look at the VTC pump: did it come when they booted lyra2re? none..... it came when there was nothing new for months. Imho VTC was nothing more than a pointless chinese pump, the coin has almost nothing to offer. I doubt VNLs rise has anything to do with them or their market, we had low volume pumps which is basically more people buying than selling instead of volume manipulation and botplay. Else you may also be right that the market reacts later to the announcements, but the example is wrong imho. I was just citing an example of a big price rise which wasn't related to any improvement in the coin, to enforce your "the altscene has gone terribly low in investors and in people who have eyes for quality coding". |
|
|
|
So now they pay double. Poloniex doing a code review on how single confirm tx's can work securely on VNL didn't even bump the price decently, the altscene has gone terribly low in investors and in people who have eyes for quality coding.
Just look at the VTC pump: did it come when they booted lyra2re? none..... it came when there was nothing new for months. |
|
|
|
|
The miner has been developed on omega drivers (14.12) but it is reported to be working fine and as fast on newer ones - BUT - some users have reported half hashrate on the first card and fixed it by installing catalyst version 14.9.
|
|
|
|
This coin looks great, it just lacks a good community. I wonder how we can get peoples attention.
I really like the pure POW on X11. POS is bad because the coins are generated for free, using hardly any electricity like mining on POW.
Coins in POS are not generated for free, one pc use 100W-150W of power. Btw provides peer for connection. small reward for that is pos award. true to a degree: I've been minting a PoS coin for months on my nas which consumes 5/10W, and the first coins with minting smartphone wallets are becoming common. there are problems with PoS, but not power consumption ;-) |
|
|
|
|
@pcste
There has been various reports of people having similar issues to yours.
First of all, it looks like there is some sort of issue with the first card of the setup under certain conditions. I noticed this as well: my card 0 hashed but never returned a share, on multiple algos, including x11... but not all :-)
Another issue is that of half hashrate for the first card. I could never reproduce this problem. It seems to depend on the driver version, though.
What I can tell you is try with the precompiled binaries, also try 4 threads which seem to give better results on 280x (and slightly worse on 290x, at least in my case).
You can also try making your binaries with different driver version without reinstalling them, just by copying the opencl.dll file into the sgminer folder.
About hardware errors, are you sure the ram of your card can run reliably at 1500? Not all 290s can. Unfortunately such high ram clock is needed for lyra2re to go fast.
Finally I see you remove bin files in your 280x bat file, but not in the 290's, are you sure you removed the bins after installing the new drivers?
And superfinally I'm not sure 100% that two running sgminer instances are good: there is some bug about device selection on sgminer, so I wouldn't do it if possible.
Hope that helps
|
|
|
|
Hi,
No CPU miner available ?
I won't do it. Unless you are extremely lucky, you're not going to mine a single block for days, with the current difficultly levels. |
|
|
|
My impulse reactions for updating caused this but I also noticed that the wallet has an auto-update feature built in... So technically if I just opened my Sia wallet it would of updated the wallet for me and I wouldn't of had to try and manually update the wallet, also might I say the wallet.dat is traditionally stored in your roaming folder but in Sia's case it is located wherever you install and run the program folder from.
This is not the norm so I overlooked it.
We're sorry about this, you're not the only one who has had problems with this setup. We are going to be changing it in the next major release so that the primarly wallet.dat is in your home folder, and the backup is in the executable directory. If the backup is automatic, it should be near the primary wallet i.e. same directory (if run manually, the folder can be changed by the user). That's because one would expect it to be there, and he might not put enough attention to it, and leave unattended. And because the executable directory is not, in general, writable by the user! |
|
|
|
|
The wallet should be in the home folder, as with all the other coins.
The program folder is another thing altogether.
This is true for most windows and Linux programs in general, and how all the OSes I know are structured.
|
|
|
|
This is the second time someone posts exactly the same thing I did some days before. Clearly they are new users trying to get some trust by posting. Makes me think they are scammers or trolls so beware. |
|
|
|
|
This is childish, come on!
There are FPGA farms with algo ready before coin launch!
|
|
|
|
-.... (Merkle Trees)
The Greek finance minister will not allow CC in Greece ... With that name of a tree  Sorry, couldn't resist ... hehe but merkle trees are in all coins, including bitcoin ;-) Didn't I say that same thing some time ago? |
|
|
|
|
I don't understand why people get mad at wolf0.
He has always developed opensource projects, along with some private. I do as well. There is nothing wrong with it. Just envious people who want to take advantage of the other people's work for free.
And mining is not for everybody for a long time now... Wake up and realise it :-)
|
|
|
|
Can someone please check if it's a false positive (happens often with miners)? I didn't compile it myself but the source should be reliable. |
|
|
|
What should be hashrate of 280x/7970 and 290 in Lyra2RE?
With my miner (see SIG) about 1100 and about 1700, depending on ram type. |
|
|
|
I have 270x's with elpida and I get 780kh/s/card I use worksize 64 with 2 threads 1000/1400 eng/mem and intensity 18 however I believe intensity could be set to 14 with similar results. I'm not sure if it makes a difference with Lyra2RE but I'm using the AMD Catalyst 15.5 drivers.
bin might need to be compiled with 14.6-14.7 dlls, at least this is imperative with stock kernel then you remove dlls and run it on 15.xx without problem on 280x i use 750/1500 clocks, any higher core clock gives nothing alas the latest pallas's sgminer gives nothing for 280x as well, just the same as stock kernel I only get 660kh/s with 14.6 drivers and 780kh/s with 15.5 My miner has been developed on omega drivers (14.12) but should lead to similar results on newer drivers. |
|
|
|
|
Show Posts
