ethminer-0.9.41-genoil-1.1 - page 44.

davembg

sr. member

Activity: 340

Merit: 251

Smell the glove.

Quote from: Genoil on June 13, 2016, 10:42:31 AM

Quote from: carlo_0000 on June 13, 2016, 09:32:43 AM

Quote

1.1.3

i m a bit confuse what s the last version? is it not the 0.9.41?

0.9.41 was the version of ethminer when I forked it. 1.1.3 is the release number of the fork.

Is the stratum code working in the OpenCL build of 1.1.4?
It builds fine, and runs great using network - but, I'm getting a missing symbol when using a -S (stratum) config with Ubuntu 15.10.

Does it need a link to boost? or is that built-in?

Anyone else running stratum with 1.1.4?
If so, would you please share your config line.

thanks!

jdc4429

newbie

Activity: 13

Merit: 0

I don't know where Claymore gets his additional 5-ish percent performance increase from, but I really can't keep up with the features he keeps adding to his miner. But mine is free Grin

I don't think Claymore's miner is faster, I think he gets the increase because his stratum protocol works allowing a direct connection to Dwarf. Supposedly this makes a big difference going direct rather then over eth-proxy... If you got stratum working with dwarf I think you would be just as fast. Great miner. Thank you for your work. Good way to verify would be testing solo mode with each as solo mode must use HTTP.

bensam1231

legendary

Activity: 1750

Merit: 1024

SO I've figured out what's been causing some weird crashing on my rigs. Some rigs have smaller SSDs (32GB). With the DAG files from Ethash this is bumping right up against the disk space limit (1.0. Cool

.

It seems as though ethminer does not gracefully handle running out of diskspace. When it does, some weird things start happening. The miner just hard locks with no output or sometimes the whole OS will lock. Since there is a small pagefile on the disk, this could be a combination of pagefile access, new dag file generation, and/or the OS trying to add to the pagefile when there is literally no diskspace left. Since when a new dag file is generated it essentially uses 3x one dag file, this can consume a lot of space.

I originally thought this was a bad OC, but it doesn't appear to be the case. I have since fixed it by removing the pagefile on the disk, but since 1.1.3 isn't stable and has slightly lower hashrate I'm still running the older version.

Genoil consider adding the streaming dag as a option or original dag file generation back in as a option in the newer versions till streaming dags get ironed out.

merc84

hero member

Activity: 799

Merit: 1000

Quote from: Genoil on June 13, 2016, 03:31:01 AM

Quote from: feriq2 on June 12, 2016, 07:23:52 PM

I've got some rigs running at Win8 with 14.4 whql drivers. Miner 1.0.8 is working just fine (-S -G --farm-recheck 400). However, miner 1.1.3 does not accept/reject any shares.. it just shows [A0+0:R0:F0] all the time. It does show mining speed (pretty similar to 1.0.8 ) in the mining window.. Just not accepting shares. Huh

That's odd, haven't seen that before. What videocards are you using?

I have seen this exact behavior with 280x and 14.4 drivers using stock etherminer, it is a problem with the drivers I suggest using 15.12 cl files. You can get the cl files from my dropbox for simplicity sake if u need too https://www.dropbox.com/s/7h19jw7xezpa2i7/Amd%2015.12%20dll.rar?dl=0 just extract them to the same folder as the miner.

FFI2013

hero member

Activity: 906

Merit: 507

genoil I have two questions first I've been using your miner on ethermine.org and works great but I recently started renting on miningrigrentals and the last few rentals got nothing but rejects so I found out one was on dwarfpool is your miner supported there cause MRR support told me it is and was heavily tested and the last where can I find a list of commands for your miner Thank You

Bokelka

sr. member

Activity: 242

Merit: 250

Quote from: uncaer9 on June 14, 2016, 01:03:07 AM

Im use 2x R9 390
my OC :
power limit +10%
core clock 1100mhs
memory 1700mhs
fan speed auto (usage device)
Gpu temperatur stable at 74

i get black scren(blank) after 2hours then i reduce the OC of memory to 1600mhz but i get blank screen again after 1hours.

anyone can help me ?
im use genoil too.

just information, this is my first problem, before it im runing in 24hours without any problem like this

For the R9 390, When you run the core at 1100 MHz, the memory freqeuncy can be 1500 or 1250. 1600 MHz is too high.

uncaer9

sr. member

Activity: 413

Merit: 250

Im use 2x R9 390
my OC :
power limit +10%
core clock 1100mhs
memory 1700mhs
fan speed auto (usage device)
Gpu temperatur stable at 74

i get black scren(blank) after 2hours then i reduce the OC of memory to 1600mhz but i get blank screen again after 1hours.

anyone can help me ?
im use genoil too.

just information, this is my first problem, before it im runing in 24hours without any problem like this

Genoil

sr. member

Activity: 438

Merit: 250

Quote from: carlo_0000 on June 13, 2016, 09:32:43 AM

Quote

1.1.3

i m a bit confuse what s the last version? is it not the 0.9.41?

0.9.41 was the version of ethminer when I forked it. 1.1.3 is the release number of the fork.

carlo_0000

legendary

Activity: 1281

Merit: 1003

Quote

1.1.3

i m a bit confuse what s the last version? is it not the 0.9.41?

restless

legendary

Activity: 1151

Merit: 1001

Or simply copy opencl files from 14.4 into miner directory Cheesy

Genoil

sr. member

Activity: 438

Merit: 250

Quote from: feriq2 on June 13, 2016, 05:18:16 AM

Quote from: Genoil on June 13, 2016, 03:31:01 AM

Quote from: feriq2 on June 12, 2016, 07:23:52 PM

I've got some rigs running at Win8 with 14.4 whql drivers. Miner 1.0.8 is working just fine (-S -G --farm-recheck 400). However, miner 1.1.3 does not accept/reject any shares.. it just shows [A0+0:R0:F0] all the time. It does show mining speed (pretty similar to 1.0.8 ) in the mining window.. Just not accepting shares. Huh

That's odd, haven't seen that before. What videocards are you using?

These rigs have 5x R9 280X each

Try adding -L sequential to the command line, or alternatively, try using a single GPU to see if that works (--opencl-devices 0). Not sure if it helps, but you could always try. I have 1 7950 (same arch) that works fine with 1.1.3.

feriq2

newbie

Activity: 53

Merit: 0

Quote from: Genoil on June 13, 2016, 03:31:01 AM

Quote from: feriq2 on June 12, 2016, 07:23:52 PM

I've got some rigs running at Win8 with 14.4 whql drivers. Miner 1.0.8 is working just fine (-S -G --farm-recheck 400). However, miner 1.1.3 does not accept/reject any shares.. it just shows [A0+0:R0:F0] all the time. It does show mining speed (pretty similar to 1.0.8 ) in the mining window.. Just not accepting shares. Huh

That's odd, haven't seen that before. What videocards are you using?

These rigs have 5x R9 280X each

Genoil

sr. member

Activity: 438

Merit: 250

Quote from: feriq2 on June 12, 2016, 07:23:52 PM

I've got some rigs running at Win8 with 14.4 whql drivers. Miner 1.0.8 is working just fine (-S -G --farm-recheck 400). However, miner 1.1.3 does not accept/reject any shares.. it just shows [A0+0:R0:F0] all the time. It does show mining speed (pretty similar to 1.0.8 ) in the mining window.. Just not accepting shares. Huh

That's odd, haven't seen that before. What videocards are you using?

Wolf0

member

Activity: 81

Merit: 1002

It was only the wind.

Quote from: davembg on June 09, 2016, 06:47:09 PM

Quote from: Genoil on June 09, 2016, 03:37:39 PM

No it's not part of the stratum spec.

Note that there are currently two stratum clients; async and sync (V2). The latter is much more straightforward and works just as good.

Will you add it if I code it?

Pools need to support it.

feriq2

newbie

Activity: 53

Merit: 0

I've got some rigs running at Win8 with 14.4 whql drivers. Miner 1.0.8 is working just fine (-S -G --farm-recheck 400). However, miner 1.1.3 does not accept/reject any shares.. it just shows [A0+0:R0:F0] all the time. It does show mining speed (pretty similar to 1.0.8 ) in the mining window.. Just not accepting shares. Huh

bensam1231

legendary

Activity: 1750

Merit: 1024

Quote from: Genoil on June 12, 2016, 05:03:05 AM

Quote from: bensam1231 on June 11, 2016, 10:29:33 PM

Curious bit here... I overclock my memory on my cards. I wonder if the stability issues and the random hangs when generating the DAG files relate to it becoming corrupt while entering memory and being in memory.

The cards hash fine, but I could see a large chunk of memory becoming corrupted possible causing this to happen. Perhaps some sort of error checking to prevent this from happening? I'm sure I'm not the only one that OCs memory.

Perhaps a separate intensity setting for the dag gen would work.

Yeah, not sure if I conveyed that right. My memory OCs are fine when mining, it seems like it might be causing slight corruption somewhere which throws off the files in memory or when they're being generated. OCs are always stable till they throw a error. The tolerance of a OS and the hardware to handle the errors changes with the severity of the OC. Something like DAG generation or the DAGs that are generated might not remotely tolerate errors or be extremely sensitive to them.

I'm running 1.0.8 again and having no issues, so best guess.

carlo_0000

legendary

Activity: 1281

Merit: 1003

for the "-L sequential" on version ethminer-opencl-0.9.41 it s not recognize

overclock the memory does it really increase performance?

i tryied on r9 380 asus, xfx, sapphire, they don't have same stock memory speed

but i see no difference when increasing memory speed, and 1500mhz is not stable of some of them
so i put them all at 1400 (asus default is 1375, even with 1375 make no difference)

i have only 2gigas's
asus 380's are the fastest 20.8mh for the best one (20.1 for the worst) best setting --cl-global-work 8192 --cl-local-work 128

sapphire the best 19.3mh ,the worst one 17.6 best setting --cl-global-work 16384 --cl-local-work 64

xfx did not test yet but it s less than 19mh current setting --cl-global-work 16384 --cl-local-work 64

for the gpu clock speed asus run at 1010 (default 970), all the other at 1033 (default 1000)

Genoil

sr. member

Activity: 438

Merit: 250

Quote from: bensam1231 on June 11, 2016, 10:29:33 PM

Curious bit here... I overclock my memory on my cards. I wonder if the stability issues and the random hangs when generating the DAG files relate to it becoming corrupt while entering memory and being in memory.

The cards hash fine, but I could see a large chunk of memory becoming corrupted possible causing this to happen. Perhaps some sort of error checking to prevent this from happening? I'm sure I'm not the only one that OCs memory.

Perhaps a separate intensity setting for the dag gen would work.

bensam1231

legendary

Activity: 1750

Merit: 1024

Curious bit here... I overclock my memory on my cards. I wonder if the stability issues and the random hangs when generating the DAG files relate to it becoming corrupt while entering memory and being in memory.

The cards hash fine, but I could see a large chunk of memory becoming corrupted possible causing this to happen. Perhaps some sort of error checking to prevent this from happening? I'm sure I'm not the only one that OCs memory.

vaulter

full member

Activity: 174

Merit: 100

Quote from: lethax on June 11, 2016, 02:56:50 PM

I'm having issues getting ethminer to work on Windows 7 with GTX 1080 card. I'm using version 1.1.3 It crashes with CUDA error in func 'ethash_cuda_miner::search' at line 303: unknown error. In open cl it crashes with clEnqueueMapBuffer(-5). Both crash right after the DAG loads before mining starts. the windows nvidia driver crashes and the screen flashes when either of these happen. Any help would be greatly appreciated.

Its crashing because currently its super low speed - without the new driver (i cant tell when or if it is coming for win 7/8.1) its pointless to mine on win 7/8.1
For win 10 there will be an update in July and you will be able to mine at ~23mhs
Currently you can set the following parameter for CUDA mode (-U) so it will stop crashing but the speed will be super slow
--cuda-grid-size 2048 --cuda-block-size 128

Topic: ethminer-0.9.41-genoil-1.1 - page 44. (Read 397363 times)