Forum Home
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Popular

    [Dev] NeoScrypt GPU Miner - Public Beta Test

    Technical Development
    52
    802
    531013
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R
      rynomite last edited by

      I’m also looking for optimum settings for the 290/290x gpu’s. (maybe a google doc spreadsheet with settings can be developed sort of like the litecoin one?)

      Anyway, I’m currently running -I 14 -g 4 -w 32, and have one 290 GPU running 60 kh/s and an identical GPU running 51 kh/s. win7x64, ATI 13.25, 3.7.7b.

      Tried another setting shown in this thread

      but the 3.7.7b doesnt like the concurrency, and without it, only managed about 45 kh/s.

      I’ve configured several rigs now that are running R9 290’s. Elpida based GPU’s run around 100Kh/s, while Hynix ones tend to be around 110Kh/s on 3.7.7b

      Here’s what I’ve done on each of them:

      Step 1 - Uninstall any 14.X based driver you may already have (or anything higher than 13.12 for that matter). Then grab DDU from guru3d.com and use it to completely remove any remnant of that driver.

      Step 2 - Install 13.12

      Step 3 - Create a batch file that you can use to provide cgminer with these startup options, ie: c:\neoscrypt377b\cgminer.exe --neoscrypt -g 2 -I 14 -w 32 -o http://bla.bla:12345 -u XXX - p XXX

      Step 4 - ensure that you’ve deleted *all* .bin files created by any previous run attempts with that other driver. Wherever you run the batch file from, that’s where the bin files are created. If you’re using CGWatcher to launch this, the bin files will be created in the actual cgminer home directory, go delete them. I recommend creating a new directory called “neoScrypt377b” and placing your batch file there - this makes sure that you’re using all new bin files.

      Step 5 - Now run the newly created batch file. Cgminer should launch and your GPU’s should hash in the upper 70’s to low 80’s. This will also create a brand new bin file using these settings. Now close it.

      Step 6 - Run the 14.X installer and upgrade the driver (I’m using 14.9). Now when you run the batch file, it will be using bin files created with 13.12 - but utilizing whatever extra capability is enabled with 14.X.

      I’ve done this on several different rigs now and it’s worked exactly the same with every R9 290 card I’ve touched across 4 different manufacturers (stock card settings). The key is creating those bin files with 13.12 installed and then using them after you upgrade to 14.X. Sometimes people don’t realize where the bin files are being created to be able to delete them. If cgminer sees a bin file with the same name in the directory it’s looking at, it won’t even bother trying to make a new one for you regardless of what driver you’re using. Hopefully this helps someone out.

      note: If you’re using CGWatcher… You need to add the --temp-cutoff and --temp-overheat settings or it might throttle the GPU down and decrease the hash rate. When mining scrypt, these GPU’s got hot and pulled a lot of power. As of 3.7.7b they don’t use nearly as much power or produce as much heat…

      1 Reply Last reply Reply Quote 0
      • S
        slowhash Regular Member last edited by

        Sweet, driver changes. The mining rig has asics attached to it now, so rebooting is extra steps…

        You mention a certain set of settings, and that they will get 70 to 80 khs. Using those settings here only nets 45 to 55 khs, but I’ve gotten up to 75 kh/s with other settings in 4 or 5 different combinations… I think I’ll be trying yet more settings before and after doing the driver switch.

        The question is, do I really need to go back from 13.25 to 13.12 and re-try all the settings, before going up to 14.whatever driver? (I just checked, there’s 58 bin files…)

        1 Reply Last reply Reply Quote 0
        • A
          Alpha Wolf last edited by

          The reason there are so many .bin files is because every time you make a change to the .bat command line it will make a new .bin.

          Changes such as from -w 32 to -w 64 or -I 12 to -I 14 and so on. If you check the .bin file name with the newest date and time it

          should have numbers in it that reflect the -w numbers that are in use within its name.

          1 Reply Last reply Reply Quote 0
          • ChekaZ
            ChekaZ last edited by

            1
            edoedo
            3.15 MH/s
            13899.4

            3866

            pxc.theblocksfactory.com

            Anyone know how he achieves such a high hashrate?

            First guess is that he got about 40~ R9 280x

            Second one is that he got a miner which is way more efficient than the public one…

            BTC: 1Ges1taJ69W7eEMbQLcmNGnUZenBkCnn45
            FTC: 6sxjM96KMZ7t4AmDTUKDZdq82Nj931VQvY

            1 Reply Last reply Reply Quote 0
            • R
              rynomite last edited by

              I’ve changed driver versions so many times now that it’s practically a science. The key to driver uninstall is the DDU app. Without it you leave behind too many files and things start crashing and not running right. Someone else on this thread was talking about not going beyond 13.12 for performance reasons. Back when I first started messing with this stuff it was with 7950’s and by going beyond the 13.12 series it definitely impacted performance. I theorize that you’ll see the bump I was talking about just by reverting to the older stuff. I really don’t know why it makes a difference, but I’ve gotten great performance out of my 290’s by doing exactly what I said. 13.12 bin files seem to be gold for me when paired with 14.X. What I found is that the -g 2 setting doesn’t do anything for the 290 unless you have a 14.X series driver installed. Once you install 14.X and use the 13.12 bin with -g 2, it causes that performance bump up into the 100-110 range.

              1 Reply Last reply Reply Quote 0
              • S
                slowhash Regular Member last edited by

                The reason there are so many .bin files is because every time you make a change to the .bat command line it will make a new .bin.

                Changes such as from -w 32 to -w 64 or -I 12 to -I 14 and so on. If you check the .bin file name with the newest date and time it

                should have numbers in it that reflect the -w numbers that are in use within its name.

                I know why they are there… The point of that was that I’ve tried a fair amount of settings in an attempt to get any sort of speed with these cards, instead of just asking for someone to give me free settings. ;)

                I’ve changed driver versions so many times now that it’s practically a science. The key to driver uninstall is the DDU app. Without it you leave behind too many files and things start crashing and not running right. Someone else on this thread was talking about not going beyond 13.12 for performance reasons. Back when I first started messing with this stuff it was with 7950’s and by going beyond the 13.12 series it definitely impacted performance. I theorize that you’ll see the bump I was talking about just by reverting to the older stuff. I really don’t know why it makes a difference, but I’ve gotten great performance out of my 290’s by doing exactly what I said. 13.12 bin files seem to be gold for me when paired with 14.X. What I found is that the -g 2 setting doesn’t do anything for the 290 unless you have a 14.X series driver installed. Once you install 14.X and use the 13.12 bin with -g 2, it causes that performance bump up into the 100-110 range.

                Ok, I’ll delete the 13.25 bin files, dig up the 13.11 drivers and roll them back, try a bunch of settings, then install new drivers tonight when I get home from work.

                1 Reply Last reply Reply Quote 0
                • C
                  cisahasa last edited by

                  any future news about older radeon cards?

                  1 Reply Last reply Reply Quote 0
                  • ghostlander
                    ghostlander Regular Member last edited by

                    any future news about older radeon cards?

                    There is a better kernel, but it needs more tuning.

                    1 Reply Last reply Reply Quote 0
                    • P
                      prensel Regular Member last edited by

                      1 edoedo 3.15 MH/s 13899.4

                      3866

                      pxc.theblocksfactory.com

                      Anyone know how he achieves such a high hashrate?

                      First guess is that he got about 40~ R9 280x

                      Second one is that he got a miner which is way more efficient than the public one…

                      I’m getting 2.6MHs with 28 cards or something so my best guess is he running more GPU’s than I do :-)

                      1 Reply Last reply Reply Quote 0
                      • A
                        Alpha Wolf last edited by

                        Yea I tested a couple 6950’s unlocked to 6970 and my hash rate was maybe 2.5kh/s per card max with those.

                        Pretty sad since they do around 325khs each on scrypt.

                        1 Reply Last reply Reply Quote 0
                        • S
                          slowhash Regular Member last edited by

                          Yea I tested a couple 6950’s unlocked to 6970 and my hash rate was maybe 2.5kh/s per card max with those.

                          Pretty sad since they do around 325khs each on scrypt.

                          Ouch…

                          1 Reply Last reply Reply Quote 0
                          • U
                            uncle_muddy administrators last edited by

                            I’m having problems building under Unix :(

                            make  all-recursive
make[1]: Entering directory `/root/neo-gpuminer'
Making all in lib
make[2]: Entering directory `/root/neo-gpuminer/lib'
make  all-recursive
make[3]: Entering directory `/root/neo-gpuminer/lib'
make[4]: Entering directory `/root/neo-gpuminer/lib'
make[4]: Nothing to be done for `all-am'.
make[4]: Leaving directory `/root/neo-gpuminer/lib'
make[3]: Leaving directory `/root/neo-gpuminer/lib'
make[2]: Leaving directory `/root/neo-gpuminer/lib'
Making all in compat
make[2]: Entering directory `/root/neo-gpuminer/compat'
Making all in jansson-2.5
make[3]: Entering directory `/root/neo-gpuminer/compat/jansson-2.5'
make  all-recursive
make[4]: Entering directory `/root/neo-gpuminer/compat/jansson-2.5'
Making all in src
make[5]: Entering directory `/root/neo-gpuminer/compat/jansson-2.5/src'
make[5]: Nothing to be done for `all'.
make[5]: Leaving directory `/root/neo-gpuminer/compat/jansson-2.5/src'
make[5]: Entering directory `/root/neo-gpuminer/compat/jansson-2.5'
make[5]: Nothing to be done for `all-am'.
make[5]: Leaving directory `/root/neo-gpuminer/compat/jansson-2.5'
make[4]: Leaving directory `/root/neo-gpuminer/compat/jansson-2.5'
make[3]: Leaving directory `/root/neo-gpuminer/compat/jansson-2.5'
make[3]: Entering directory `/root/neo-gpuminer/compat'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/root/neo-gpuminer/compat'
make[2]: Leaving directory `/root/neo-gpuminer/compat'
Making all in ccan
make[2]: Entering directory `/root/neo-gpuminer/ccan'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/root/neo-gpuminer/ccan'
make[2]: Entering directory `/root/neo-gpuminer'
  CC     cgminer-cgminer.o
cgminer.c:45:21: error: jansson.h: No such file or directory
In file included from ./sha2.h:36,
                 from cgminer.c:52:
./miner.h:1048: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
cgminer.c:1491: error: expected ‘)’ before ‘*’ token
cgminer.c: In function ‘load_config’:
cgminer.c:1567: error: ‘json_error_t’ undeclared (first use in this function)
cgminer.c:1567: error: (Each undeclared identifier is reported only once
cgminer.c:1567: error: for each function it appears in.)
cgminer.c:1567: error: expected ‘;’ before ‘err’
cgminer.c:1568: error: ‘json_t’ undeclared (first use in this function)
cgminer.c:1568: error: ‘config’ undeclared (first use in this function)
cgminer.c:1581: warning: implicit declaration of function ‘json_load_file’
cgminer.c:1581: error: ‘err’ undeclared (first use in this function)
cgminer.c:1583: warning: implicit declaration of function ‘json_is_object’
cgminer.c:1597: warning: implicit declaration of function ‘parse_config’
cgminer.c: At top level:
cgminer.c:1715: warning: type defaults to ‘int’ in declaration of ‘json_t’
cgminer.c:1715: error: expected ‘;’, ‘,’ or ‘)’ before ‘*’ token
cgminer.c:1794: error: expected declaration specifiers or ‘...’ before ‘json_t’
cgminer.c: In function ‘__build_gbt_txns’:
cgminer.c:1796: error: ‘json_t’ undeclared (first use in this function)
cgminer.c:1796: error: ‘txn_array’ undeclared (first use in this function)
cgminer.c:1805: warning: implicit declaration of function ‘json_object_get’
cgminer.c:1805: error: ‘res_val’ undeclared (first use in this function)
cgminer.c:1806: warning: implicit declaration of function ‘json_is_array’
cgminer.c:1810: warning: implicit declaration of function ‘json_array_size’
cgminer.c:1819: error: ‘txn_val’ undeclared (first use in this function)
cgminer.c:1819: warning: implicit declaration of function ‘json_array_get’
cgminer.c:1820: warning: implicit declaration of function ‘json_string_value’
cgminer.c: At top level:
cgminer.c:1870: error: expected declaration specifiers or ‘...’ before ‘json_t’
cgminer.c: In function ‘update_gbt’:
cgminer.c:1875: error: ‘json_t’ undeclared (first use in this function)
cgminer.c:1875: error: ‘val’ undeclared (first use in this function)
cgminer.c:1882: warning: implicit declaration of function ‘json_rpc_call’
cgminer.c:1887: error: too many arguments to function ‘work_decode’
cgminer.c:1899: warning: implicit declaration of function ‘json_decref’
cgminer.c: At top level:
cgminer.c:1966: error: expected declaration specifiers or ‘...’ before ‘json_t’
cgminer.c: In function ‘gbt_decode’:
cgminer.c:1983: error: ‘res_val’ undeclared (first use in this function)
cgminer.c:1987: warning: implicit declaration of function ‘json_integer_value’
cgminer.c:1990: warning: implicit declaration of function ‘json_is_true’
cgminer.c:2054: error: too many arguments to function ‘__build_gbt_txns’
cgminer.c: At top level:
cgminer.c:2060: error: expected ‘)’ before ‘*’ token
cgminer.c:2090: error: expected declaration specifiers or ‘...’ before ‘json_t’
cgminer.c: In function ‘work_decode’:
cgminer.c:2092: error: ‘json_t’ undeclared (first use in this function)
cgminer.c:2092: error: ‘res_val’ undeclared (first use in this function)
cgminer.c:2092: error: ‘val’ undeclared (first use in this function)
cgminer.c:2096: warning: implicit declaration of function ‘json_is_null’
cgminer.c:2102: error: too many arguments to function ‘gbt_decode’
cgminer.c:2107: warning: implicit declaration of function ‘getwork_decode’
cgminer.c: At top level:
cgminer.c:2611: error: expected ‘)’ before ‘*’ token
cgminer.c: In function ‘submit_upstream_work’:
cgminer.c:2758: error: ‘json_t’ undeclared (first use in this function)
cgminer.c:2758: error: ‘val’ undeclared (first use in this function)
cgminer.c:2758: error: ‘res’ undeclared (first use in this function)
cgminer.c:2758: error: ‘err’ undeclared (first use in this function)
cgminer.c:2924: warning: implicit declaration of function ‘share_result’
cgminer.c: In function ‘get_upstream_work’:
cgminer.c:2960: error: ‘json_t’ undeclared (first use in this function)
cgminer.c:2960: error: ‘val’ undeclared (first use in this function)
cgminer.c:2975: error: too many arguments to function ‘work_decode’
cgminer.c: At top level:
cgminer.c:5256: error: expected ‘)’ before ‘*’ token
cgminer.c: In function ‘parse_stratum_response’:
cgminer.c:5278: error: ‘json_t’ undeclared (first use in this function)
cgminer.c:5278: error: ‘val’ undeclared (first use in this function)
cgminer.c:5278: error: ‘err_val’ undeclared (first use in this function)
cgminer.c:5278: error: ‘res_val’ undeclared (first use in this function)
cgminer.c:5278: error: ‘id_val’ undeclared (first use in this function)
cgminer.c:5280: error: ‘json_error_t’ undeclared (first use in this function)
cgminer.c:5280: error: expected ‘;’ before ‘err’
cgminer.c:5284: warning: implicit declaration of function ‘json_loads’
cgminer.c:5284: error: ‘err’ undeclared (first use in this function)
cgminer.c:5298: warning: implicit declaration of function ‘json_dumps’
cgminer.c:5298: warning: implicit declaration of function ‘JSON_INDENT’
cgminer.c:5351: warning: implicit declaration of function ‘stratum_share_result’
cgminer.c: In function ‘pool_active’:
cgminer.c:5765: error: ‘json_t’ undeclared (first use in this function)
cgminer.c:5765: error: ‘val’ undeclared (first use in this function)
cgminer.c:5808: error: ‘res_val’ undeclared (first use in this function)
cgminer.c:5808: error: ‘mutables’ undeclared (first use in this function)
cgminer.c:5818: error: ‘arrval’ undeclared (first use in this function)
cgminer.c:5820: warning: implicit declaration of function ‘json_is_string’
cgminer.c:5869: error: too many arguments to function ‘work_decode’
cgminer.c: At top level:
cgminer.c:6877: error: expected ‘)’ before ‘*’ token
cgminer.c: In function ‘longpoll_thread’:
cgminer.c:7021: error: ‘json_t’ undeclared (first use in this function)
cgminer.c:7021: error: ‘val’ undeclared (first use in this function)
cgminer.c:7021: error: ‘soval’ undeclared (first use in this function)
cgminer.c:7055: warning: implicit declaration of function ‘convert_to_work’
make[2]: *** [cgminer-cgminer.o] Error 1
make[2]: Leaving directory `/root/neo-gpuminer'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/neo-gpuminer'
make: *** [all] Error 2

                            We really should have good build instructions out there this close to switch…

                            1 Reply Last reply Reply Quote 0
                            • P
                              prensel Regular Member last edited by

                              I’m having problems building under Unix :(We really should have good build instructions out there this close to switch…

                              Seems your missing some libraries.

                              Did you run autogen.sh ?

                              1 Reply Last reply Reply Quote 0
                              • S
                                slowhash Regular Member last edited by

                                I’ve changed driver versions so many times now that it’s practically a science. The key to driver uninstall is the DDU app. Without it you leave behind too many files and things start crashing and not running right. Someone else on this thread was talking about not going beyond 13.12 for performance reasons. Back when I first started messing with this stuff it was with 7950’s and by going beyond the 13.12 series it definitely impacted performance. I theorize that you’ll see the bump I was talking about just by reverting to the older stuff. I really don’t know why it makes a difference, but I’ve gotten great performance out of my 290’s by doing exactly what I said. 13.12 bin files seem to be gold for me when paired with 14.X. What I found is that the -g 2 setting doesn’t do anything for the 290 unless you have a 14.X series driver installed. Once you install 14.X and use the 13.12 bin with -g 2, it causes that performance bump up into the 100-110 range.

                                Well, after driver dumping, reloading, and a couple reboots after running DDU, here’s the results.

                                1 GPU running 102 mh/s and one running 98 mhs, with the settings listed, and with one of the other settings I had gotten good speed with previously.

                                Also, it doesn’t matter 13.11 or 13.25 for the initial driver to create the bin, they have the same final speed with 14.whatever driver.

                                -Edit- To quote a famous gay guy, “oh my”… 136 mh/s and climbing…

                                1 Reply Last reply Reply Quote 0
                                • L
                                  Lukey_p last edited by

                                  Anyone able to make a short guide on mining for windows, i have tried the info on the 1st page, installed and reinstalled loads of drivers. All the testnet and downloads i find all error out or just CMD closes strait away. CPU mining is working fine. The PC mines Scrypt and X11 just fine, very well in fact.

                                  Looking for a basic guide really.

                                  Thanks guys, dont want to be left behind when we change!

                                  1 Reply Last reply Reply Quote 0
                                  • M
                                    mirrax last edited by

                                    Anyone able to make a short guide on mining for windows, i have tried the info on the 1st page, installed and reinstalled loads of drivers. All the testnet and downloads i find all error out or just CMD closes strait away. CPU mining is working fine. The PC mines Scrypt and X11 just fine, very well in fact.

                                    Looking for a basic guide really.

                                    Thanks guys, dont want to be left behind when we change!

                                    I guess MinerX might be suitable solution for you maybe?

                                    https://forum.feathercoin.com/index.php?/topic/7930-minerx-a-graphical-miner-for-neoscrypt-feathercoin-released/#entry68682

                                    1 Reply Last reply Reply Quote 0
                                    • L
                                      Lukey_p last edited by

                                      I guess MinerX might be suitable solution for you maybe?

                                      https://forum.feathercoin.com/index.php?/topic/7930-minerx-a-graphical-miner-for-neoscrypt-feathercoin-released/#entry68682

                                      Thanks for this, i have a 2 x 7970 rig and this gives me 75Kh per card. i assume thats about right guys? im using the 13.12 drivers.

                                      Any idea who will have a pool up strait away with the switch of will everyone be solo mining for a few days?

                                      i am now trying mining PXC and im getting a lot of (Share is above target) errors. Is this a pool issue or a miner issue?

                                      using : -I 13 -g 2 -w 48 --gpu-memclock 1500 --gpu-engine 1050

                                      EDIT: with -g 2 -I 14 -w 32 i get 85Kh per 7970 but with many share above target

                                      Cheers!

                                      1 Reply Last reply Reply Quote 0
                                      • M
                                        mirrax last edited by

                                        Thanks for this, i have a 2 x 7970 rig and this gives me 75Kh per card. i assume thats about right guys? im using the 13.12 drivers.

                                        Any idea who will have a pool up strait away with the switch of will everyone be solo mining for a few days?

                                        Cheers!

                                        Actually there are already pools prepared for switch, more will come soon:

                                        https://forum.feathercoin.com/index.php?/topic/7926-neoscrypt-mining-pools/

                                        I think big boys might try solo mining as starting difficulty will be low.

                                        1 Reply Last reply Reply Quote 0
                                        • R
                                          raintowers last edited by

                                          Solo mining IPC no luck! back to TheBlocksFactory. I had some luck with PXC.

                                          Will try FTC Solo soon!

                                          1 Reply Last reply Reply Quote 0
                                          • S
                                            slowhash Regular Member last edited by

                                            Solo mining IPC no luck! back to TheBlocksFactory. I had some luck with PXC.

                                            Will try FTC Solo soon!

                                            Was all you got rejected shares solo-mining on IPC?

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post