Topic: lolMiner 1.64: Fastest Kaspa miner in market - page 148. (Read 155881 times)

The Windows version is currently a cross build of the Linux one - I will see if I find a Windows compiler that can compile it to get rid of the cross build runtimes. It seems they cause most of the problems, since the code is (except from 1 line) the same.



What?!?

lolMiner.exe can establish at most 3 connections:
1) The one you use for mining to your pool
2) The one for the dev fee, which currently will likely be (dependent of the coin) minexpool.nl, suprnova.cc or miningpoolhub.com
3) The API connection. When you start the miner with API port given the Windows Firewall will kick in and ask if lolMiner is allowed to do so or not.

There is no more code inside that does any connection or load. Also the only thing that it will do to interact with Windows explorer is searching for the Kernel files in its /kernel directory and load the user_config.json. I guaranty that no more is done, especially it does not connect any cloud service or other 3rd party side.


For some reason on some Windows 10 versions the check for the error code does not wait for the program to be finished. I have no idea why, because usually that /wait indicates it should. I changed that line of the batch script with purpose that on a 0 sol/s bug or a stratum problem the miner just should restart because often that fixes the problem. So I use different error codes on return (concretely the error code 134 indicates that the miner assumes that a plain restart will not fix the problem. That is the reason why the Linux restart script tests for this error code). Never the less thank you for providing a solution that works. I think I will change back to the old restart script.


I read the teams request to add the coin just a few minutes before the release, which was a bit too late.  But it will be added in 0.41, likely within in this week.

@Lolliedieb

Could you explain why in this version you added a connection to a cloud hosting?
The first thing it does is connect to a mining site, it is OK
The second is a personal account in www.linode.com
It is not done directly from lolminer.exe, it is done trough explorer.exe
This looks to me you are doing this way to bypass firewalls
Very suspicious 

Cool, now it is working, thank you very much.

now works with this ":EXIT"  at the end

Thank you, the miner is working on my R9 280. Great work, much appreciated. Looking forward to the updates and improvements.

there is an increase in the productivity of the new miner for the MNX coin?

The problem is in bat file. In my case PC try to restart until it hangs. I changed one thing:
this:
to this:
Now it works fine in my case

I'm using RX 580, it looks to me it is a compilation problem.
With previous version it was working fine.

guys i'm using 7970 and 290x with 2x7950........on win 10 and blockchain drivers......stable

but i increased pagefile to 36gb min and 40gb max

As an difference from preview version, this one starts and works fine without hdd swapping (win 7 x64, 17.4.3 drivers, r9 280x). But performances are awful, 9-13 sol/s but with average of 12, roughly half of 1060 3GB on new EWBF 0.3 which makes it currently totally unprofitable to mine with. Hope for much better performance in next versions (r9 280x was getting 280-300 sols/s vs 300-320 1060 3GB on 200,9 equihash).

Same on my rig. 3x R9 280x, pls can u fix 3GB cards, i'm waiting till 3rd july,thanks

hang freeze on windows version on tahiti card, i've tried on wind 7 64bit and wind 10 64bit.
hoping fixed on new update

Linux version works pretty well and is stable.  10-12 sols/s from each of my RX470s and RX570s.  RX550's 4GB also work fine on linux, 5 sols/sec for each one.

Windows version is another story.  I build a powershell watcher script that restarts the miner if it crashes which it does a lot.  Sometimes it crashes after a few seconds, sometimes it runs for 10 minutes or more.  Sometimes on the restart it gets stuck on "Using Device".  I spawn the miner through powershell and tee it out to a log file so I can watch for this problem and force kill the miner and restart it when it does.  The API is unreliable and still not usable to keep the miner up.

Mining on windows with RX550s seems fairly stable for the most part, get 3-4 sols per 4GB RX550.  I do sometimes get the "Application has stopped working." popup which can't be cleared by script.  Once this happens I have to reboot the box to get the miner to work again. 2GB RX550s do not work at all (no worries though, I get 450hs/sec on cryptonight from them)

My Vegas on windows (on blockchain Aug 12 driver) do not like the miner at all and often get stuck, but I am seeing about 30 sols from each of them when it does work. Version .38 with the gfx900 kernel seemed to be more stable for Vega on Windows.

YUP modified only first example1 to XSG



   "XSG" :
   {
      "COIN" : "XSG",
      "POOLS" : [
         {"POOL" : "us.miningspeed.com",
          "PORT" : "3022",
          "USER" : "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
          "PASS" : "x"}
      ]
   },

Hmm - was not able to test the 144.5 code on many gpus, but I even get 35 sol/s on my 1080 non-ti ... strange that the ti does not scale :/


Oh yes the first ones I just forgot xD Will bring them of cause, most likely even this week ^^
Log file is planned on mid term, temperature on long one. Unfortunately there is no good was to extract temps for all 4 combinations (Nvidia / Amd, Windows / Linux) so thats a lot of detail work.


Right now not, but noted for 0.41 (likely this week).

how u configured the json file? u modify the 3-rd example too? or how

USING 2x 7950 , 1x290x and 7970

running stable ...but low sol/s ,my single 1050ti is doing 14sol but all amd including 290x is less...might give up XSG and just do CMM

still no good for amd. the oldest worked .the 0.38

As was already noted API crashes on windows (after first attempt)
Also would be good if you added a total hashrate on the api

Is there a command line option for devices selection?

at least, I would have appreciated the following options (which were present in v0.34):
-max-connection-Attempts
-set-reconnection-timer
-enable-time-print
some options that I will appreciate:
possibility to generate a log file
set maximum temperature threshold