[Dev] NeoScrypt GPU Miner - Public Beta Test
-
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
-I 13 -g 3 --thread-concurrency 11264 -w 48 -s 15 -Q 3 -E 60 --auto-gpu --gpu-powertune 20 --gpu-engine 900-1000,1050 --gpu-memdiff 325,300 --temp-target 80,95 --temp-overheat 90,105 --temp-cutoff 95,115
but the 3.7.7b doesnt like the concurrency, and without it, only managed about 45 kh/s.
-
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?)
Im looking for a working config :\ my GPU (HD6670) gets outmined by just 1core of my core2Quad Q6600
-
Definitely need to adjust settings… Where are you starting at?
-
Im looking for a working config :\ my GPU (HD6670) gets outmined by just 1core of my core2Quad Q6600
If your card is older than HD7000 series, don’t bother now. The kernel isn’t vectorised properly for the older cards. I have explained it on the previous page.
-
You are missing OpenCL libraries. If you have them installed correctly - it will say OpenCL found and then follow the rest of the instructions.
I found these instructions somewhere and fine-tuned them.
Try this - version numbers may have changed.
1) AMD app sdk:
http://developer.amd.com/tools-and-sdks/opencl-zone/amd-accelerated-parallel-processing-app-sdk/
- cd ~/Downloads/
- mkdir amd_sdk
- mv AMD-APP-SDK-v2.9-lnx64.tgz amd_sdk
- cd amd_sdk
- tar zxvf AMD-APP-SDK-v2.9-lnx64.tgz
- sudo ./Install-AMD-APP.sh
The installer for the APP_SDK seems to break some files, or at least it did during testing. Do the following to fix it:
cd /etc/OpenCL/vendors/
in here are two files amdocl32.icd and amdocl64.icd, you will find their contents (they are just text files) to be “libamdocl32.so” and “libamdocl64.so” respectively.
Edit them to include their full paths, so the contents of
amdocl32.icd --> “/usr/lib32/fglrx/libamdocl32.so”
amdocl64.icd --> “/usr/lib/fglrx/libamdocl64.so”.
NOTE: A user building on Xubuntu 13.10 reported his libamdocl32.so and libamdocl64.so libraries being at /usr/lib/i386-linux-gnu/libamdocl32.so and /usr/lib/libamdocl64.so respectively.
2) ADL SDK
http://developer.amd.com/tools-and-sdks/graphics-development/display-library-adl-sdk/
In this example, my source code is in ~/Miners/cgminer
- cd ~/Downloads/
- mkdir adl
- mv ADL_SDK_6.0.zip adl
- cd adl
- unzip ADL_SDK_6.0.zip
- cd include
- cp * ~/Miners/cgminer/ADL_SDK
-
I read somewhere that thread-concurrency has no bearing in neo-scrypt
I have compiled 3.7.7b under Ubuntu.
I have not managed to get it to run for more than 24 hours at a time.
Lots of restarts between accepts - i am running this against a p2p pool for PXC.
-
I read somewhere that thread-concurrency has no bearing in neo-scrypt
I have compiled 3.7.7b under Ubuntu.
I have not managed to get it to run for more than 24 hours at a time.
Lots of restarts between accepts - i am running this against a p2p pool for PXC.
I have had the same problem with all versions not running very long I’ve tried all suggestions but it still quits. Only thing that works for me is start it with the -T option and it runs and runs…
-
Hi everyone! First real post here. Long time lurker, but finally got around to creating account due to NeoScrypt. So far I am very excited and think this is a great move. I do have some questions though.
Does anyone know if the current settings for solo mining are going to be the same once we fork? If my understanding is correct, we just need to have neoscrypt cgminer running when feathercoin forks and we should be good, right?
-
You can solo mine with the neoscrypt cgminer, but I’ve found that you will need different setting to what you use for Scrypt mining.
The easiest way to try it out now is to set yourself up to attempt solo mining on Phoenix coin to work out your optimum settings and then you just need to change your solo miner setup to point back from the PXC wallet to your Feathercoin one.
-
I’m on windows8.1
my bat file:cgminer.exe --neoscrypt -o stratum.pxc.theblocksfactory.com:3332 -u estah.2 -p x --api-listen
HD6670
-
Imperialcoin (IPC) is making the switch to neoscrypt in 450 blocks.
Difficulty will be way lower than Phoenixcoin. Maybe use that one for solo mining testing.
My batch files
for p2pool mining : cgminer.exe --neoscrypt -I 14 -w 48 -g 2 -o stratum+tcp://prometheus.phoenixcoin.org:10554 -u -p x
gives 90 kh/s on amd 280x
for local mining : cgminer.exe --neoscrypt -I 13 -w 32 -g 2 -o 127.0.0.1:9554 -u -p
gives about 80 on the wallet
AMD 14.9 drivers
You can solo mine with the neoscrypt cgminer, but I’ve found that you will need different setting to what you use for Scrypt mining.
The easiest way to try it out now is to set yourself up to attempt solo mining on Phoenix coin to work out your optimum settings and then you just need to change your solo miner setup to point back from the PXC wallet to your Feathercoin one.
-
I’m on windows8.1
my bat file:cgminer.exe --neoscrypt -o stratum.pxc.theblocksfactory.com:3332 -u estah.2 -p x --api-listen
HD6670
See this post.
https://forum.feathercoin.com/index.php?/topic/7780-neoscrypt-gpu-miner-public-beta-test/?p=68572
-
The coin that is switching is IPC, not IMP… https://bitcointalk.org/index.php?topic=476091.0
IMPerialcoin (IMP) is making the switch to neoscrypt in 450 blocks.
Difficulty will be way lower than Phoenixcoin. Maybe use that one for solo mining testing.
My batch files
for p2pool mining : cgminer.exe --neoscrypt -I 14 -w 48 -g 2 -o stratum+tcp://prometheus.phoenixcoin.org:10554 -u -p x
gives 90 kh/s on amd 280x
for local mining : cgminer.exe --neoscrypt -I 13 -w 32 -g 2 -o 127.0.0.1:9554 -u -p
gives about 80 on the wallet
AMD 14.9 drivers
-
The coin that is switching is IPC, not IMP… https://bitcointalk.org/index.php?topic=476091.0
Aargh, typo. edited original post
Thanks for correcting me :)
about 250 blocks left before the switch
-
Aargh, typo. edited original post
Thanks for correcting me :)
about 250 blocks left before the switch
I just didn’t want people looking for the wrong Imperial coin to experiment with, like I did… :)
Lol, who in their right mind would start a coin with an existing name but use different letters? Wow, thought much not used by IMP devs!!
-
If your card is older than HD7000 series, don’t bother now. The kernel isn’t vectorised properly for the older cards. I have explained it on the previous page.
See this post.
https://forum.feathercoin.com/index.php?/topic/7780-neoscrypt-gpu-miner-public-beta-test/?p=68572
Please vectorise the HD6000 series… I want to mine PXC :c
-
Update!
Well I love following this thread. I get all kinds of hints related to what I’m interested in.
The post about IPC starting after 66000 was cool because I figured out after a lot of googleing + stray posts to get the IPC client to solo mine.
I started on the PXC and got some blocks solo mining too. But now back to the blocks factory.
Now I’m waiting for feathercoin to arrive around the 24th.
At this point I’ve got minerd running with my i7 2600k slightly over’d getting 26.3K
My cgminer is running a hd 7750 3gb at 13 K with the -T option because what has come so far doesn’t last the 24 hr test
Best regards,
Raintowers
-
I like the site idea. But it may also be worth looking at the minerC checkaz is working on as it should make the whole thing simple for everyone. :)
-
About 1 hour to the IPC switchover, if anyone wants to try out solo mining something neoscrypt with low diffifficulty.
-
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…
