Created new “static” supported-coins overview page …

I have in the past tried my best to document which coins lukMiner does support – by keeping an up-to-date readme with each version, by having my release scripts automatically post that together with the latest releases, by having the lukMiner binary print example commandlines when launched without parameters, by posting new blog articles every time I added a new coin, etc … but still, with the flurry of new cryptonight coin variants several users asked for some better “overview” of what is supported, how to call it, etc (I guess a new article for every new coin is good and well – but not all too useful if you’re new to lukMiner and have to google through 10 such articles).

In light of those requests, I did spend some time trying to figure out how WordPress really works, and did finally manage to create a new “static” page that is not a blog, but accessible from the main page of http://lukminer.org: It’s called – who’d have guessed – “Supported Coins”, and is also statically linked to its own URL: https://lukminer.org/supported-coins/).

In the future, I’ll still add updates to the README.md as I did in the past, but will also continually update this page with any newly supported coin, changes in how to execute them, etc. In particular, I’ll use the example command lines on this page to do my own testing – so if any of those don’t work, please let me know (and/or check your firewall settings).

With that – Happy Mining!

Published by

lukMiner

To learn more about me, look at the "About" page on http://lukminer.org

8 thoughts on “Created new “static” supported-coins overview page …”

  1. Hi Luk,

    I am trying to mine BitTube and getting a hashrate at 2000H/s on 7210 with lukminer. I was expecting 2500 as you mentioned in another post about CN heavy. Is 2000H/s normal for CN Saber?

    Thanks!

    Like

    1. I haven’t done too much performance measuring on it, yet, but yes, saber is _significantly_ more costly than regular cryptonight variants. Main modification in saber is that one of the aes rounds got slightly modified – to the extend that what was previously a single “aesenc” instruction is now a sequence of a few dozen individual instructions, and that costs … a lot ….

      Like

  2. Hi everyone – am having trouble installing mpss 4 (rhel 7.2) version for my 7220P from the above link. Followed the steps precisely (3 times) in the linux set up guide, but keep getting the following errors:

    modprobe: WARNING: Module mic_x200_dma not found.
    modprobe: WARNING: Module scif_bus not found.
    modprobe: WARNING: Module vop_bus not found.
    modprobe: WARNING: Module cosm_bus not found.
    modprobe: WARNING: Module scif not found.
    modprobe: WARNING: Module vop not found.
    modprobe: WARNING: Module mic_cosm not found.
    modprobe: WARNING: Module mic_x200 not found.

    Can anyone help? I understand that these are kernel modules on the host but no idea why they arent getting installed/recognised, as the rpms seem to be installing succesfully

    Like

    1. Hey,
      First, double-check which RHEL versoins are actually supported. I’m constantly mixing up my RHEL/CentOS versions, so take what I say with a grain of salt – but 7.2 _does_ sound a bit too new to me (I’m _pretty_ sure I usually use 6.3).
      Other than that – you may want to try to rebuild the mic module – there’s docs on that in the mpss manual. Basically MPSS does include _some_ precompiled version of these modules, but every time you update your system you change the kernel, and these modules may not work any more – so generally, unless you know that you have exactly the same OS/kernel version that Intel had when they pre-built those modules you probably want to recompile them on a new system, and then install the new version rather than the old ones. Note it’s only the kernel modules that need rebuilding, not all of mpss!. It’s actually pretty easy, too – probably something like “rpmbuild –rebuild “, followed by copying the thereby-built modules to the right location. That said, the rebuild will only work if your kernel is not “too far diverged” from the kernel that exsited when the modules were written, hence my “7.2 may be too new”.

      Like

  3. As I indicated to that person, he/she needs to rebuild the kernel. It won’t work by simple re-compile as the kernel changed and as such, the source code fails to compile. Need to fix the kernel sources a bit to get this working. Haven’t had the time to do this myself as I am having the sample problem on CentOS…

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s