Bitcoin Forum
August 01, 2024, 05:53:51 AM *
News: Help 1Dq create 15th anniversary forum artwork.
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Alternate cryptocurrencies / Mining (Altcoins) / Re: [ANN] sgminer v5 - optimized X11/X13/NeoScrypt/Lyra2RE/etc. kernel-switch miner on: May 22, 2016, 04:03:53 AM
I've just seen the post, I did a guide for Neoscrypt on sgminer. I added the "wild" kernels to a github. Although, I know FTC members paid Wolf to keep his (main) work for Neoscrypt, in the open source domain. I have been looking closely at the sgminer code, at least to gradually tidyout some of the cruft (algos that never took off), as I found the latest version started to get flaky.

[Guide] How to Mine crypto-currency with Linux on AMD Graphics cards GPU, install sgminer 5.1.2

This guide is for GPU mining with Sgminer 5.1.2 on GNU/Linux (Ubuntu 14.04.0x LTS). It is set up to mine Feathercoin, which uses the neoscrypt algorythm to encrypt each transaction, but will work with multiple algorithms from other alternate currencies, with an appropriate Sgminer config file set-up.

Sgminer 5.1.2 is the same as version 5.1.1, except it has has some additional neoscrypt kernels which kave been let out in the wild and the option to return to version one, which is better with some cards.

See “forked from” on Github, if you want to use the guide on the sgminer-dev source instead.

In general the performance and complexity of GPU mineing comes down to the AMD drivers and lack of support for all previous cards versions in each release. here are also problems where certain versions of the AMD drivers will not work with versions of linux or sgminer.

In order make a stable install which will work with the neoscrypt algorithm, specific versions are used, 14.04 LTS Ubuntu operating system, 14.9 AMD fglrx, 2.9 AMD application SDK and version 6 of AMD’s ADL SDK.

This guide has been tested on R9 2** cards and is optimised for Neoscrypt on R9 280 in the guides default configuration.

#1. install Ubuntu 14.04.0x
Open a terminal and do an update to Ubuntu
Code:
sudo apt-get update
sudo apt-get upgrade -y

Install build essentials and dependencies
Code:
sudo apt-get install -y git curl unzip automake autogen yasm autoconf dh-autoreconf build-essential pkg-config openssh-server screen libtool libcurl4-openssl-dev libtool libncurses5-dev libudev-dev gdebi gedit execstack dh-modaliases lib32gcc1 dkms

sudo apt-get install -y xserver-xorg-core xserver-xorg-video-ati

#2. Manually Install correct AMD Catalyst drivers (14.9)
Code:
sudo apt-get install linux-headers-generic
sudo apt-get purge ‘fglrx*’
sudo rm /etc/X11/xorg.conf
sudo apt-get install --reinstall -y xserver-xorg-core
sudo dpkg-reconfigure xserver-xorg

Download 14.9 driver from AMD :
http://support.amd.com/en-us/download/desktop/previous/detail?os=Linux x86&rev=14.9
Code:
cd ~/
mkdir fglrx4.9

Extract the AMD driver installer
Extract the files and folders from download of the AMD Catalyst™ 14.9 Proprietary Linux x86 Display Driver zip and copy / extract them into the fglrx4.9 directory

run the install commands, after it finishes press exit, then install on the pop up.
Code:
cd fglrx4.9
sudo sh *.run

Initialise the graphics card, install xorg and dependencies.
Code:
sudo aticonfig --adapter=all --initial
sudo aptitude install -yr boinc-amd-opencl opencl-headers mesa-utils libglu1-mesa libgl1-mesa-glx libgl1-mesa-dri

#3. Reboot

#4. install AMD App SDK
Code:
cd ~/
mkdir amd-app-sdk

Download APP-SDK from AMD :
http://developer.amd.com/tools-and-sdks/opencl-zone/amd-accelerated-parallel-processing-app-sdk/
make sure it is version 2.9 AMD-APP-SDK-v2.9-lnx64.tgz extract it into /amd-app-sdk
Code:
cd amd-app-sdk
chmod a+x *.sh
sudo ./Install-AMD-App.sh
sudo aticonfig --adapter=all --initial

#5. Reboot

#6. Install sgminer 5.1.2
Code
cd ~/
git clone https://github.com/wrapperband/sgminer.git

#Download AMD/ADL_SDK_6.0.zip, extract the 'h files from include to ~/sgminer/adl_sdk
http://developer.amd.com/tools-and-sdks/graphics-development/display-library-adl-sdk/
Make sure it is the version ADL_SDK_6.0
Code:
cd ~/sgminer
git submodule init
git submodule update
autoreconf -i -f
CFLAGS="-O2 -Wall -march=native -std=gnu99" ./configure
make
(sudo make install : optional install)

Check that the build worked
Code:
./sgminer -n
export DISPLAY=:0
export GPU_MAX_ALLOC_PERCENT=100
export GPU_USE_SYNC_OBJECTS=1
./sgminer

#7. Create a sgminer start script
#Create the script file to start sgminer correctly
Code:
nano sgminer.sh

Copy in the script code and customise as required :
#!/bin/bash -
#title :sgminer.sh
#description :Start sgminer
export DISPLAY=:0
export GPU_MAX_ALLOC_PERCENT=100
export GPU_USE_SYNC_OBJECTS=1
./sgminer

#Make the bash script runnable
Code:
chmod a+x *.sh

#8. Run the sgminer script
Code:
cd ~/sgminer
./sgminer.sh

The different coin algorithms are stored in the sgminer/kernels directory. The kernels are created in C for AMD cl graphics processing programming interface. Esencially the GPU speeds up over CPU by parallel processing.

There are four neoscypts available in the 5.1.2, neoscrypt.cl, neoscrypt.v1 and neoscrypt.v2 are marked as such and version 3 which is “optimised” for R9 280 (default neoscrypt kernel) and marked as neoscrypt.280.

There is also a 79XX kernel version, with some of the 290 code replaced to handle older cards, which is included as a separate file neoscrypt.7690.
It is worth experimenting to see which kernel works best with your setup, copy one of the neoscrypt files then run a recompile…

Recompile sgminer after changing the kernel
Code:
cd ~/sgminer
rm *.bin
autoreconf -i -f && CFLAGS="-O2 -Wall -march=native -std=gnu99" ./configure && make && ./sgminer.sh

The configuration file sgminer.conf is stored in the .sgminer hidden directory. Use Ctr-H in Gnome / Nautilus or Alt . in KDE / Dolphin, to show the hidden directories in the home directories.

I have experimented and read about xIntensity, it made no difference to adjust that from 3 for neoscrypt. It gave exactly the same results with raw intensity of 5690.

An example sgminer.conf pointing towards p2pools, just replace the address with your own.
Code :
nano ~/sgminer/sgminer.conf

{
“pools”: [
{
“name”: “Neoscrypt Pool2P”,
“url”: “stratum+tcp://p2pool.neoscrypt.de:19327”,
“user”: “ftc address”,
“pass”: “password”,
“no-extranonce”: true
“priority”: “1”
},
{
“name”: “kosmoplovci Pool2P”,
“url”: “stratum+tcp://p2pool.kosmoplovci.org:19327”,
“user”: “ftc address”,
“pass”: “password”,
“no-extranonce”: true,
“priority”: “2”
}
],
“profiles”: [],
“failover-only”: true,
“algorithm”: “neoscrypt”,
“device”: “all”,
“xintensity”: “3”,
“thread-concurrency”: “8192”,
“worksize”: “32”,
“gpu-threads”: “2”,
“temp-cutoff”: “95”,
“temp-overheat”: “85”,
“temp-target”: “75”,
“gpu-memdiff”: “0”,
“shares”: “0”,
“kernel-path”: “/usr/local/bin”,
“api-mcast-port”: “4028”,
“api-port”: “4028”,
“expiry”: “12”,
“failover-switch-delay”: “60”,
“gpu-dyninterval”: “7”,
“gpu-platform”: “-1”,
“hamsi-expand-big”: “4”,
“keccak-unroll”: “0”,
“log”: “5”,
“no-pool-disable”: true,
“no-client-reconnect”: true,
“queue”: “0”,
“scan-time”: “5”,
“tcp-keepalive”: “30”,
“temp-hysteresis”: “3”,
“watchpool-refresh”: “30”
}


http://forum.feathercoin.com/topic/7446/guide-how-to-mine-ftc-neoscrypt-sgminer-ubuntu-14-04-amd

Yasm? Why yasm? If you're not doing anything with the CPU, like doing algos in assembly language, yasm isn't required if you're not doing that.  Wink

2  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][DOGE] Dogecoin - very currency - many coin - wow on: May 10, 2014, 07:03:54 PM
Okay, I am going to have to sound off here. I don't appreciate scammers and misconfigurations for the QT based wallets. In order to get all wallets to synchronize with the networks in which they belong, is you need the newest unedited version of the wallet for what ever operating system is has been built or or will be built if you are on Linux for example.

Now, the configuration file has nothing to do with synchronizing to the network, the Dogecoin-qt wallet will synchronize with the network without any .conf file being used. What you do need however, is to
select IPv6 in your networking section and set it to Automatic or if you have it already configured as a manual address and you need to add in an exception in your firewall, so that this client, the Dogecoin-qt
wallet can communicate with the external nodes and gets the blockchain data.

A quick edit; I have realized that some ISP do block you from connecting to certain IP addresses and block certain ports, however I do know that is not a concern of Comcast cable and high speed Internet, they're not blocking it because I have Comcast and have done solo mining. I primarily do pool mining for Dogecoin now.

Usually, the reason why you can't connect is because you have an old version of the wallet and needs new network nodes or your firewall on the computer is blocking it. Note: If you're on Microsoft Windows, there are two firewalls, the Microsoft Windows Firewall and the firewall that comes with your security suite, you need to fix it so both allow your wallet to connect to the outside world. When it just sits there, it means it can't connect. Also, many newer wallets use IPv6 addressing, which means that if your firewalls are fine, it could be this option stopping you up. Same thing if you're using a miner program even if you specify only IPv4 addresses, such as localhost aka 127.0.0.1.  It's just one of those funny things...

Now, about that .conf file. There is no point in using that file because, if you do solo mining and someone's unique identifier can be seen from the network nodes, your coin can be taken from you.

Now, the following should be set if you are just using the wallet as a wallet and not going to be solo mining.

# rpcuser=
# rpcpassword=
# rpcallowip=
# rpcport=22555
# server=0
# daemon=0
# addnode=162.243.113.110
# addnode=146.185.181.114

The reason for the pound sign aka the "#" is that it comments out the activity of the commands and options, as if you didn't have a .conf file to begin with.  Notice, I cleared the rpcuser and rpcpassword as well as the rpcallowip. Zeroed server and daemon as well, if you're using this as just a wallet, you don't need any further information in.

Essentially, you can use the litecoin.conf example file and change the "addnodes=" to mirror the Dogecoin network IP addresses. If you need an updated list contact https://twitter.com/BillyM2k. His G-Mail account is on there too, he's the developer of Dogecoin itself. He will probably post the official nodes for you to use and/or the example.conf file you can use for the wallet, which is the safest route.

Remember, anyone who tells you need a .conf file for you to synchronize to the network is a liar and most likely a scammer or doesn't know what in the hell they're doing. Another thing, before you go to get
a .conf file, should you want to do solo mining, please read the Litecoin tutorials, it works the same way for Dogecoin, just uses different node IP addresses and ports than Litecoin. Last but not least, encrypt your wallet, please!

I hope this helps you!

-Alex


Why the heck wont DOGECOIN wallet sync with the network? I downloaded the windows wallet on windows 7 and it just says out of sync. No loading nothing.

Did you follow the instructions and make the DOGE.conf in your appdata?

I copy/pasted the code from the first page into notepad and named it doge.conf then saved to the dogecoin folder inside roaming and yet still nothing.

C> Uses > *** > Appdata > Roaming > Dogecoin
Save the file as "Dogecoin.conf" without " obviously.

Copy/paste this inside it when you open it with notepad in txt form-

rpcuser=doge
rpcpassword=wow
rpcallowip=127.0.0.1
rpcallowip=192.168.1.1
rpcport=22555
server=1
daemon=1
addnode=162.243.113.110
addnode=146.185.181.114

Worked for me

Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!