Pages:
Author

Topic: [ANN] lolMiner-mnx, Mining MinexCoin(MNX) New version: v0.4 (July 22) - page 35. (Read 30772 times)

jr. member
Activity: 34
Merit: 1
Same problem. When connected through Teamviewer I get full hash. When disconnected hash drops to half. This is with a monitor connected, so that cannot be the problem.
I have the same problem.
Tons of us have the same problem. I ordered some dummy plugs but at the moment I'm losing hash rate.

So I think I was able to keep the hashrate from dropping when I disconnect from Teamviewer by changing the "--set-work-batch" config to 8.
jr. member
Activity: 111
Merit: 1
Same problem. When connected through Teamviewer I get full hash. When disconnected hash drops to half. This is with a monitor connected, so that cannot be the problem.
I have the same problem.
Tons of us have the same problem. I ordered some dummy plugs but at the moment I'm losing hash rate.
And constantly reconnects
member
Activity: 104
Merit: 11
Same problem. When connected through Teamviewer I get full hash. When disconnected hash drops to half. This is with a monitor connected, so that cannot be the problem.
I have the same problem.
Tons of us have the same problem. I ordered some dummy plugs but at the moment I'm losing hash rate.
jr. member
Activity: 111
Merit: 1
Same problem. When connected through Teamviewer I get full hash. When disconnected hash drops to half. This is with a monitor connected, so that cannot be the problem.
I have the same problem.
jr. member
Activity: 146
Merit: 4
Same problem. When connected through Teamviewer I get full hash. When disconnected hash drops to half. This is with a monitor connected, so that cannot be the problem.
newbie
Activity: 39
Merit: 0
I added --enable-time-print to the batch file of 0.22, but the time is not displayed. How can I see it?
newbie
Activity: 16
Merit: 0
droping hash if rig no conected on monitor
jr. member
Activity: 34
Merit: 1
Windows 10 and version .21 now enables me to run 2 x 1070 at the same time which is great but they only do half the speed.

So two kards = half speed or two cards = same speed as with one? What happens with two distinc inszances of the miner vs one instance running both cards?
I can run two cards at full speed with v0.21 but as soon as I log out of teamviewer the hash rate halves straight away. If i log back in it goes back to full speed. Any ideas?

I'm also having the same issue. I do have dummy hdmi plugged in to the integrated video card. I hope this gets fixed soon.
jr. member
Activity: 34
Merit: 1
Does anybody have good afterburner overclock settings for GTX 1070? Currently only getting around 7.5k per GPU.
newbie
Activity: 34
Merit: 0
So I am checking the fixed version now. Speed is a bit better than before, but still about 20% less than v0.13. It appears to be related to the CPU, any change to the CPU affinity in the task manager heavily affects the hashrate. Still, I did not have the problem with v0.13. I'll be sticking with the new version for now and see what it can do over time.

btw. Any chance to include a logfile, to see hashrates and how often the miner had to restart?
newbie
Activity: 16
Merit: 0
thanks for the fix  Smiley
newbie
Activity: 9
Merit: 0
läuft wieder, danke für den schnellen Fix Smiley
member
Activity: 433
Merit: 48
Would you PLEASE stop the miner from reconnecting endlessly?
Or just implement "--retries" argument for how many times you would like it to retry, like I suggested before.
The quickest solution is to not have the miner reconnect at all and just exit so we could do something, where now the miner just stops ALL mining and waits forever for the pool to be up again, and hopefully it does.


Well this is better in 0.2 versions ... they handle this much more graceful! But stratum connection will get a rework next versions. Would like to do fall-back pool and ssl support Smiley

By the way (see two posts above): With that versions it now should work on the pools that are still online!
full member
Activity: 132
Merit: 100
By the way, how are the newer versions of the miner?

I am still using 0.12 as they update cut my hashrate in half when afk.
Also the filesize of the update is about 3 times they size of the previous, 0.12. Dunno about the newest versions though.
full member
Activity: 132
Merit: 100
I have suggested this before. But now with suprnovas mnx pool down it is more important than ever.

Would you PLEASE stop the miner from reconnecting endlessly?
Or just implement "--retries" argument for how many times you would like it to retry, like I suggested before.
The quickest solution is to not have the miner reconnect at all and just exit so we could do something, where now the miner just stops ALL mining and waits forever for the pool to be up again, and hopefully it does.

I really don't want to have a script pinging the pool I am using all day again, just so I can exit the miner if it goes down, to switch pools automatically.
member
Activity: 433
Merit: 48
Hello out there,

This is because somehow suprnova is down and I had a bug in the fallback routine for collecting dev fee ... my fault Sad

This version here will fix it for Linux:
https://drive.google.com/open?id=17Q7vpJUKPRdQHcm9L4cbdupGzW4R0TDl

This version here will fix it for Windows:
https://drive.google.com/open?id=1y1wFzejasSn79KArmESmoUKnE4UaZkVL
jr. member
Activity: 34
Merit: 1
Anybody know what I could be doing wrong? My console just keeps saying "Warnign section 1"

Quote
Connecting to stratum server asia.minexpool.nl:9999
Start Mining...
Connected!
Subscribed to stratum server
New target received: 0000333333333333340000000000000000000000000000000000000000000000
New job received: d1da
Authorized worker: Xxxxxxxxxxxxxxxxxxx.78TVTM
Warnign section 1

Warnign section 1

Warnign section 1

Warnign section 1

My config file is basically the following:
Quote
### Device configuration
--platform 1                          # Insert the index of the platform you want to run on. Run lolMiner-mnx.exe --list-devices
                                      # to see all available platforms and the available devices for each platform
--device 0,1,2,3,4,5                            # Insert your devices to run the miner here. For multiple GPU pass a comma separated list, e.g.: 0,1 for using two GPUs 

--set-work-batch 2                   # Uncommend this line to set the work batch size. Default is 2 which is ideal for Nvidia customer GPUs.
                                      # For AMD GPUs try higher values, e.g. 8 or 12 to optimize performance. Higher values increase GPU memory use of lolMiner-mnx.


### Display log configuration
#--set-short-stats-interval 5         # Uncommend to set the time interval (seconds) between the short term performance output. Set 0 to disable the output.    
#--set-long-stats-interval 10         # Uncommend to set the time interval (seconds) between the long term performance output. Set 0 to disable the output.
                                      # The value will also determine the length of the benchmark mode
--enable-time-print                  # Uncommend to allow lolMiner-mnx to print the system time in HH:MM:SS format before each performance output.



### Expert parameters - handle with care
#--use-alt-mine-thread                # Enables the mine thread handling of lolMiner-mnx 0.13. This will disable multi-GPU support.
                                      # Therefore only the first number in --device is handled. The Nvidia load hotfix is enabled by default.
                  # Currently Intel devices are only working with this switch enabled.

#--set-sleep-duration 1000            # Sets the time span between polling the GPUs for completed work in microseconds. Lower values may stabilize
                                      # the performance, but also increase CPU load for all vendors. Setting the value to 0 will make lolMiner-mnx use one full
                                      # CPU core by 100% for handling all devices. If this is used with "--use-alt-mine-thread" it will disable the Nvidia hotfix.
                                      # Higher values reduce CPU load but may reduce hash speed. Default is 1000 microseconds = 1 millisecond.
newbie
Activity: 16
Merit: 0
same for me here not working anymore
newbie
Activity: 9
Merit: 0
hm grade kurz die 0.22 benutzt, nach 20 Mins kamen error irgendwas mit warning message und seit dem geht auch kein 0.21 mehr
Sobald ich den starte, bricht er ab und startet neu, endlos

edit : 0.22 das gleiche
newbie
Activity: 34
Merit: 0

Enable v0.13 thread model by "--use-alt-mine-thread"
This will enable the work handling of lolMiner-mnx 0.13 but with all the other bug fixes and improvements still enabled. This will deactivate multi-gpu support, so only the first device listed in --device will be used. By default the Nvidia CPU load fix (hotfix) is enabled, see below how to disable this. This option will brings back support for Intel devices.


Thanks, that is awesome!

Worked like charm. For 5 seconds. Then the pool went down.

Will report more once I can run it again. Is it possible to combine the "set sleep duration" with the v0.13 thread model?
Pages:
Jump to: