ethminer-0.9.41-genoil-1.1

[yakudza]

1.0.6b2 from the pick-devies branch is not the latest version. It has the -E bug. That should be fixed in 1.0.6 in master branch. If you still experience issues, please send me your full command line, as well as a directory listing from your DAG storage directory.

1.0.6 version is not stable.
Miner work, whereas on the bullet coinotron rate drops to zero.
After restarting the miners, speed pool reappears.

setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100

ethminer.exe -G -S coinotron.com:3344 -O usr.log:pass --cl-local-work 128 --cl-global-work 16384 --farm-recheck 200
https://dropmefiles.com/yZv3J

[Ayers]

is the windows 10 low hashrate for nvidia solved somewhere? the last drivers give me 7 mega which is very bad, and you can not revert to 347.52, it say that the cuda version is too old or something

[Genoil]

is the windows 10 low hashrate for nvidia solved somewhere? the last drivers give me 7 mega which is very bad, and you cna not revert to 347.52, it say that the cuda version is too old or something

You need a CUDA 6.5 build. You can find them in the CUDA miner topic on ETH forums, guy named @Mo35 makes them available. I should put them in my repo sometime.

1.0.6b2 from the pick-devies branch is not the latest version. It has the -E bug. That should be fixed in 1.0.6 in master branch. If you still experience issues, please send me your full command line, as well as a directory listing from your DAG storage directory.

1.0.6 version is not stable.
Miner work, whereas on the bullet coinotron rate drops to zero.
After restarting the miners, speed pool reappears.

setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100

ethminer.exe -G -S coinotron.com:3344 -O usr.log:pass --cl-local-work 128 --cl-global-work 16384 --farm-recheck 200
https://dropmefiles.com/yZv3J

True, it isn't stable. I'm working on creating a timeout clientside. So if the miner is working on the same job for over, let's say 1.5 the blocktime, we can safely assume the connection is botched. Reconect and try again. I know it;s a band-aid for a problem I haven't been able to identify yet, but it's better than what we have now..

[tolazy]

ubuntu 14.04 cuda-7.5 and use cmake -DCOMPUTE=30 -DBUNDLE=cudaminer .. from cpp-ethereum/build
with: installed
apt-get install  build-essential fakeroot dh-make debconf execstack dh-modaliases dkms pkg-config
apt-get install libtool libncurses5-dev libcryptopp-dev libleveldb-dev libjsoncpp-dev libargtable2-dev libjson-rpc-cpp-dev
apt-get install libmicrohttpd-dev libreadline-dev libtool autotools-dev automake pkg-config  libssl-dev libevent-dev bsdmainutils
apt-get install -f libsdl2-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler libgmp-dev cpuid


nvcc fatal   : Unknown option '-std'
CMake Error at ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o.cmake:206 (message):
  Error generating
  /root/cpp-ethereum/build2/libethash-cuda/CMakeFiles/ethash-cuda.dir//./ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o


make[2]: *** [libethash-cuda/CMakeFiles/ethash-cuda.dir/ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o] Error 1
make[2]: Leaving directory `/root/cpp-ethereum/build2'
make[1]: *** [libethash-cuda/CMakeFiles/ethash-cuda.dir/all] Error 2
make[1]: Leaving directory `/root/cpp-ethereum/build2'
make: *** [all] Error 2

edit this file:
/root/cpp-ethereum/build2/libethash-cuda/CMakeFiles/ethash-cuda.dir/ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o.cmake

look for lines that set the nvcc_flags:
set(CUDA_NVCC_FLAGS ..........

-std isn't a valid option for some versions of mvcc - so, remove that option.
My line looks like this:
set(CUDA_NVCC_FLAGS --disable-warnings;--ptxas-options=-v;-use_fast_math;-lineinfo;-gencode;arch=compute_20,code=sm_20;-gencode;arch=compute_30,code=sm_30;-gencode;arch=compute_35,code=sm_35;-gencode;arch=compute_50,code=sm_50 ;; )

Also, stop building as root:)
sudo is your friend, my friend.

didnt help. got
Error limit reached.
100 errors detected in the compilation of "/tmp/tmpxft_000008a0_00000000-6_ethash_cuda_miner_kernel.cpp1.ii".
Compilation terminated.
CMake Error at ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o.cmake:264 (message):
  Error generating file
  /root/cpp-ethereum/build2/libethash-cuda/CMakeFiles/ethash-cuda.dir//./ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o


make[2]: *** [libethash-cuda/CMakeFiles/ethash-cuda.dir/ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o] Error 1
make[1]: *** [libethash-cuda/CMakeFiles/ethash-cuda.dir/all] Error 2

[sorry2xs]

is the windows 10 low hashrate for nvidia solved somewhere? the last drivers give me 7 mega which is very bad, and you cna not revert to 347.52, it say that the cuda version is too old or something

You need a CUDA 6.5 build. You can find them in the CUDA miner topic on ETH forums, guy named @Mo35 makes them available. I should put them in my repo sometime.

1.0.6b2 from the pick-devies branch is not the latest version. It has the -E bug. That should be fixed in 1.0.6 in master branch. If you still experience issues, please send me your full command line, as well as a directory listing from your DAG storage directory.

1.0.6 version is not stable.
Miner work, whereas on the bullet coinotron rate drops to zero.
After restarting the miners, speed pool reappears.

setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100

ethminer.exe -G -S coinotron.com:3344 -O usr.log:pass --cl-local-work 128 --cl-global-work 16384 --farm-recheck 200
https://dropmefiles.com/yZv3J

True, it isn't stable. I'm working on creating a timeout clientside. So if the miner is working on the same job for over, let's say 1.5 the blocktime, we can safely assume the connection is botched. Reconect and try again. I know it;s a band-aid for a problem I haven't been able to identify yet, but it's better than what we have now..

i get an invalid argument -S error

[crazyearner]

Can someone tell me what the -S parameter is used for and also -t 2 option too. Using t-2 works with a number of gpus and some it does not work on. -S I do not know what is for as no documentation I have read so far has this listed.

[virasog]

Can someone tell me what the -S parameter is used for and also -t 2 option too. Using t-2 works with a number of gpus and some it does not work on. -S I do not know what is for as no documentation I have read so far has this listed.

-S is used for the pools which supports stratum protocol. One of the pool is the ethpool.org. You use -s eu1.ethpool.org:3333

[Ayers]

is the windows 10 low hashrate for nvidia solved somewhere? the last drivers give me 7 mega which is very bad, and you cna not revert to 347.52, it say that the cuda version is too old or something

You need a CUDA 6.5 build. You can find them in the CUDA miner topic on ETH forums, guy named @Mo35 makes them available. I should put them in my repo sometime.

1.0.6b2 from the pick-devies branch is not the latest version. It has the -E bug. That should be fixed in 1.0.6 in master branch. If you still experience issues, please send me your full command line, as well as a directory listing from your DAG storage directory.

1.0.6 version is not stable.
Miner work, whereas on the bullet coinotron rate drops to zero.
After restarting the miners, speed pool reappears.

setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100

ethminer.exe -G -S coinotron.com:3344 -O usr.log:pass --cl-local-work 128 --cl-global-work 16384 --farm-recheck 200
https://dropmefiles.com/yZv3J

True, it isn't stable. I'm working on creating a timeout clientside. So if the miner is working on the same job for over, let's say 1.5 the blocktime, we can safely assume the connection is botched. Reconect and try again. I know it;s a band-aid for a problem I haven't been able to identify yet, but it's better than what we have now..

found it https://forum.ethereum.org/discussion/comment/25157#Comment_25157, but the link does not work, unlucky like everything

[davembg]

ubuntu 14.04 cuda-7.5 and use cmake -DCOMPUTE=30 -DBUNDLE=cudaminer .. from cpp-ethereum/build
with: installed
apt-get install  build-essential fakeroot dh-make debconf execstack dh-modaliases dkms pkg-config
apt-get install libtool libncurses5-dev libcryptopp-dev libleveldb-dev libjsoncpp-dev libargtable2-dev libjson-rpc-cpp-dev
apt-get install libmicrohttpd-dev libreadline-dev libtool autotools-dev automake pkg-config  libssl-dev libevent-dev bsdmainutils
apt-get install -f libsdl2-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler libgmp-dev cpuid


nvcc fatal   : Unknown option '-std'
CMake Error at ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o.cmake:206 (message):
  Error generating
  /root/cpp-ethereum/build2/libethash-cuda/CMakeFiles/ethash-cuda.dir//./ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o


make[2]: *** [libethash-cuda/CMakeFiles/ethash-cuda.dir/ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o] Error 1
make[2]: Leaving directory `/root/cpp-ethereum/build2'
make[1]: *** [libethash-cuda/CMakeFiles/ethash-cuda.dir/all] Error 2
make[1]: Leaving directory `/root/cpp-ethereum/build2'
make: *** [all] Error 2

edit this file:
/root/cpp-ethereum/build2/libethash-cuda/CMakeFiles/ethash-cuda.dir/ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o.cmake

look for lines that set the nvcc_flags:
set(CUDA_NVCC_FLAGS ..........

-std isn't a valid option for some versions of mvcc - so, remove that option.
My line looks like this:
set(CUDA_NVCC_FLAGS --disable-warnings;--ptxas-options=-v;-use_fast_math;-lineinfo;-gencode;arch=compute_20,code=sm_20;-gencode;arch=compute_30,code=sm_30;-gencode;arch=compute_35,code=sm_35;-gencode;arch=compute_50,code=sm_50 ;; )

Also, stop building as root:)
sudo is your friend, my friend.

didnt help. got
Error limit reached.
100 errors detected in the compilation of "/tmp/tmpxft_000008a0_00000000-6_ethash_cuda_miner_kernel.cpp1.ii".
Compilation terminated.
CMake Error at ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o.cmake:264 (message):
  Error generating file
  /root/cpp-ethereum/build2/libethash-cuda/CMakeFiles/ethash-cuda.dir//./ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o


make[2]: *** [libethash-cuda/CMakeFiles/ethash-cuda.dir/ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o] Error 1
make[1]: *** [libethash-cuda/CMakeFiles/ethash-cuda.dir/all] Error 2

So, you have more/different errors.

Stop building as root - you're killin' me???

What version of cuda? I use 7.5, I think Genoil is using 6.5.

Here's what I do after failed builds.

From your build directory, working as a NON PRIV user:

rm -rf CMakeCache.txt && cmake -G "Unix Makefiles" -DEVMJIT=0 -DCMAKE_BUILD_TYPE=Release -DBUNDLE=cudaminer
make clean

**make your change (removing --std) to libethash-cuda/CMakeFiles/ethash-cuda.dir/ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o.cmake
set(nvcc_flags -m64;--std;c++11;-DETH_JSONRPC;-DETH_READLINE;-DETH_MINIUPNPC;-DETH_ETHASHCL;-DETH_ETHASHCUDA;-DETH_STRATUM;-DETH_CURL;-DETH_FRONTIER;-DETH_TRUE) # list

make VERBOSE=1

Then, show me the error.

[w0lf0.]

guys is normal this result?  i'am trying to mine with 7950

Code:

setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
ethminer -G -F http://127.0.0.1:8080/rig1 --cl-local-work 128 --cl-global-work 8192

I' am new on ETH, the real hashrate are first or second figure?

Thanks

[d57heinz]

Can someone tell me what the -S parameter is used for and also -t 2 option too. Using t-2 works with a number of gpus and some it does not work on. -S I do not know what is for as no documentation I have read so far has this listed.

I have a rig with only hd 7970's (4 cards) and i dont need the -t 4 option.. but in my 290x rig i have to assign the -t 5 option for the amount of cards i have or it just doesnt pick them all up.. seems this miner behaves differently on different setups.. but its a wip so that can be expected.. To my knowledge the -t is the amount of threads the ethminer is using.  Honestly i dont know. i came across it in my many long nights and that is what made my system work.   I have some 390x 's coming today.. excited to get them up and running..  Also anyone here try these yet.  http://www.ebay.com/itm/141865200790?_trksid=p2057872.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT .. i ordered a few and will give them a go and report back.. will save us a ton in setup costs if these work.. but they take a few weeks to get here.. meantime just have to keep buying up mobo's// 

Best Regards
Doug

[Vaccinus]

guys is normal this result?  i'am trying to mine with 7950

Code:

setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
ethminer -G -F http://127.0.0.1:8080/rig1 --cl-local-work 128 --cl-global-work 8192

I' am new on ETH, the real hashrate are first or second figure?

Thanks

i think you can touch 20mega, try to oc a bit, and why you're mining in solo ethereum lol

[tolazy]

guys is normal this result?  i'am trying to mine with 7950

Code:

setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
ethminer -G -F http://127.0.0.1:8080/rig1 --cl-local-work 128 --cl-global-work 8192

I' am new on ETH, the real hashrate are first or second figure?

Thanks

try with --farm-recheck 300
i have a 390x and i use
ethminer --farm-recheck 300 -G -F http://proxyip:8080/gpu1
i get about 29.3MHs

[d57heinz]

guys is normal this result?  i'am trying to mine with 7950

Code:

setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
ethminer -G -F http://127.0.0.1:8080/rig1 --cl-local-work 128 --cl-global-work 8192

I' am new on ETH, the real hashrate are first or second figure?

Thanks

yes thats really close to right(number on left).. i have 7970's and that is about what i get from them.. i use 1040 gpu and 1375 memclk.. i have been looking at some old threads on flashing these cards to get the timings right.. should make a heck of difference if they arent calibrated right.. i have a lot of the xfx versions and it seems that is a common issue with them.. but i get 19.5 mhs average

Best Regards
Doug

[maxvall]

True, it isn't stable. I'm working on creating a timeout clientside. So if the miner is working on the same job for over, let's say 1.5 the blocktime, we can safely assume the connection is botched. Reconect and try again. I know it;s a band-aid for a problem I haven't been able to identify yet, but it's better than what we have now..

Hi!

I think this hack will not work.
For me the problem appears on reconnetct after connection errors.
As I see the received data was corrupted.

I think this is a race condition problem.
You perform asynchronous reading (based on hooks) but your m_pending counter not protected by mutex/semaphore.

I tried perform fast fix: I remove all m_pending counter logic and readline() call from readResponse() and insert multiple readline() calls into processReponse().
For me it fixes this bug, but this is bull shit code only for test proof of concept.
I think the right desigion - it's to create a separate thread with infinite loop, which will read all responces.

Code:

void EthStratumClient::readline() {

	//if (m_pending == 0) {
		async_read_until(m_socket, m_responseBuffer, "\n",
			boost::bind(&EthStratumClient::readResponse, this,
			boost::asio::placeholders::error, boost::asio::placeholders::bytes_transferred));
	//	m_pending++;
	//}
}

...

void EthStratumClient::readResponse(const boost::system::error_code& ec, std::size_t bytes_transferred)
{
	//m_pending = m_pending > 0 ? m_pending - 1 : 0;

	if (!ec)
	{
		...

		if (response.front() == '{' && response.back() == '}') 
		{...}
		else
		{...}
		//readline();
	}
	else
	{...}
}

void EthStratumClient::processReponse(Json::Value& responseObject)
{
	...
	switch (id)
	{
	...
	case 2:
		...
		cnote << "Authorized worker " << m_user;
		readline();//!!!
		break;
 	...
	default:
		string method = responseObject.get("method", "").asString();
		if (method == "mining.notify")
		{
			...
			readline();//!!!
		}
		else if (method == "mining.set_difficulty")
		{
			readline();//!!!
		}
		...
	}
}

[w0lf0.]

guys is normal this result?  i'am trying to mine with 7950

Code:

setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
ethminer -G -F http://127.0.0.1:8080/rig1 --cl-local-work 128 --cl-global-work 8192

I' am new on ETH, the real hashrate are first or second figure?

Thanks

try with --farm-recheck 300
i have a 390x and i use
ethminer --farm-recheck 300 -G -F http://proxyip:8080/gpu1
i get about 29.3MHs

with farm recheck command i I get this:




Is normal these lines with 0 h/s and these changes between 13 and 27 mH/s every sec?

Thanks guys

[tolazy]

i'm trying to compile on 15.10
but i get error that cuda dont support higher then gcc-4.9
i've tried with
ln -s /usr/bin/g++-4.8 /usr/bin/g++
ln -s /usr/bin/gcc-4.8 /usr/bin/gcc
but it still says:  #error -- unsupported GNU version! gcc versions later than 4.9 are not supported!
when i do gcc/g++ --version it says 4.8.5

[tolazy]

with farm recheck command i I get this:




Is normal these lines with 0 h/s and these changes between 13 and 27 mH/s every sec?

Thanks guys
[/quote]

you can try with --farm-recheck 200 you can try diffrent vaules
i use 300 on my 390x and 200 on my 660ti.
i dont get any 0 on my 390x but sometimes on my 660ti.
i can get 0 when i start ethminer but then the numbers come

[davembg]

i'm trying to compile on 15.10
but i get error that cuda dont support higher then gcc-4.9
i've tried with
ln -s /usr/bin/g++-4.8 /usr/bin/g++
ln -s /usr/bin/gcc-4.8 /usr/bin/gcc
but it still says:  #error -- unsupported GNU version! gcc versions later than 4.9 are not supported!
when i do gcc/g++ --version it says 4.8.5

nvcc doesn't always report errors correctly - are you using cuda 6.5 or 7.5?

[tolazy]

i'm trying to compile on 15.10
but i get error that cuda dont support higher then gcc-4.9
i've tried with
ln -s /usr/bin/g++-4.8 /usr/bin/g++
ln -s /usr/bin/gcc-4.8 /usr/bin/gcc
but it still says:  #error -- unsupported GNU version! gcc versions later than 4.9 are not supported!
when i do gcc/g++ --version it says 4.8.5

nvcc doesn't always report errors correctly - are you using cuda 6.5 or 7.5?

7.5

i'm reinstalling 14.04 on my test machine. will try compile it on that when its done.