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

    [Dev] NeoScrypt GPU Miner - Public Beta Test

    Technical Development
    52
    802
    574306
    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.
    • 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
                      • R
                        raintowers last edited by

                        No I didn’t see any booooo so I’d assume no rejects, just no yay!!!

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

                          No I didn’t see any booooo so I’d assume no rejects, just no yay!!!

                          Oh, ok, I had an issue solo mining IPC. Solved about 25% of the blocks but 100% rejects, so I went back to PXC…

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

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

                            Which settings/drivers did you use to get that high of a hash rate? Highest I’ve seen so far is 111Kh/s with an R9 290 (hynix ram) with the settings I mentioned earlier.

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

                              I kept getting ‘Share is above target’ I was using The Blocks Factory PXC pool for testing, as soon as I used a P2Pool that error went away. Maybe its something to do with their vardiff…

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

                                Which settings/drivers did you use to get that high of a hash rate? Highest I’ve seen so far is 111Kh/s with an R9 290 (hynix ram) with the settings I mentioned earlier.

                                Posted in this thread… https://forum.feathercoin.com/index.php?/topic/7929-gpu-comparison-neoscrypt/

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

                                  I’m seeing a nice bump in kh/s for 3.7.7b when using AMD 14.9 driver with a 14.9 .bin.

                                  Jumped to 60kh/s with 14.9/14.9.bin from 37kh/s when using AMD 13.12 driver 13.12.bin.

                                  Not sure if its just me because others have reported differently and say to use a 13.12.bin to see improvement

                                  which was not the case for me as I tested each way and 14.9 with 14.9.bin gave me the best results/better hash rate.

                                  Found some small improvement for Nvidia, but will save that for another post later when its confirmed more.

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

                                    Hi,

                                    can some of the developers comment to this:

                                    https://forum.feathercoin.com/index.php?/topic/7934-error-61-clcreatebuffer-padbuffer8/#entry68753

                                    ???

                                    Thanks in advance,

                                    cu

                                    (Maybe I am simply to dumb …)

                                    1 Reply Last reply Reply Quote 0
                                    • V
                                      vehre last edited by

                                      Has anyone compiled https://github.com/vehre/neo-gpuminer from source on Linux and successfully mined PXC or FTC on the testnet? All I get are hw errors, with any settings I’ve tried. Specifying no options to cgminer beyond a stratum connection and user/pass, or using even a bare minimum of -I 12 -w 32 -g 2 doesn’t help. I’m on 14.6 catalyst drivers with APP SDK 2.9.

                                      I’m happy to provide any additional logs/info/settings or help troubleshoot if anyone has any suggestions.

                                      The bare minimum would be -I 8 -w 128 and -g 1

                                      I am mining PXC on the life net and have no problems yet. FTC is not yet on neoscrypt therefore mining on testnet is ok and should work, although I haven’t tested.

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

                                        Has anyone compiled https://github.com/vehre/neo-gpuminer from source on Linux and successfully mined PXC or FTC on the testnet? All I get are hw errors, with any settings I’ve tried. Specifying no options to cgminer beyond a stratum connection and user/pass, or using even a bare minimum of -I 12 -w 32 -g 2 doesn’t help.

                                        I started on 14.6 catalyst drivers (APP SDK 2.9), and then upgraded to 14.9 after it wasn’t working on v14.6.

                                        I’m happy to provide any additional logs/info/settings or help troubleshoot if anyone has any suggestions.

                                        You gotta start on 13.xx drivers or all you will get is hw errors with 3.7.7b… If you use the 14.xx drivers you need to use the bins created by 13.xx.

                                        Use a driver cleaner to get rid of all of the 14.xx drivers.

                                        In the cgminer folder, dump all the binfiles created by the 14.xx drivers.

                                        Install 13.xx drivers, try out lots of settings, and save the bin files. (write down the settings you used on 13.xx so you can use them again in 14.xx)

                                        Install 14.xx drivers, try out the settings you used on 13.xx so you use the 13.xx binfiles.

                                        Any new settings that you try to use in 14.xx that you don’t have a 13.xx bin for will get nothing but hw errors.

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

                                          Using -I 8 -w 128 -g 1 on PXC, I still only see HW errors.

                                          Ah, that explains a lot, thanks. Unfortunately, it seems like a fairly large barrier to entry as far as getting an average miner interested in mining neoscrypt.

                                          I’ll give that a try and report back.

                                          On a related note, are there any plans to get neoscrypt support built into something more modern like sgminer v5?

                                          Yeah, that’s only to get the optomized settings out of the software that we have… At some point whatever is causing that issue will get found and corrected, and things will get easier. :)

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

                                            It’s very confusing to find how to get neoscrypt mining going, and where to post problems. There is no one description of where things are and generally how to do them and confilicting posts. (posted this in the mining thread by mistake, last night)

                                            Its pretty much like the thread title says, its a open beta test at the moment for reporting problems and errors found.

                                            I’m sure once more bugs are worked out and a more stable version is released there will be a updated page for

                                            download and more info on how to setup and run the miner software which should fall pretty much in the norm for

                                            usage/setup in a final release versions.

                                            Edit: I’ll be testing a 2nd rig with 2x R9 270x in a little while and will report back on my findings with drivers on that 2nd rig later this morning.

                                            I’ll also try working with the rig with the 2x6950 unlocked to 6970’s if I can squeeze in enough time for it as well.

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