yes, it should.
ok it's connecting now but when miner starts it only makes a "ckolivas" .bin file
i have tried all the yescrypt .cl files
Topic: GlobalBoost-Y $BSTY GlobalBoost®, Yescrypt Social @NetworksManager™ - page 17. (Read 630492 times)
February 13, 2016, 03:47:51 AM
ok it's connecting now but when miner starts it only makes a "ckolivas" .bin file
i have tried all the yescrypt .cl files
February 12, 2016, 04:13:40 PM
yes, it should.
February 12, 2016, 12:32:52 PM
Code:
[quote author=bstdev link=topic=775289.msg13850900#msg13850900 date=1455210209]
[code]### globalboost.conf configuration file. Lines beginning with # are comments.
### Uncomment and edit options you wish to use.
## JSON-RPC options (for controlling a running GlobalBoost-Y/globalboostyd process)
# server=1 tells GlobalBoost-Y to accept JSON-RPC commands.
server=1
# You must set rpcuser and rpcpassword to secure the JSON-RPC api
# You should create your own new random password.
# The username and password MUST NOT be the same.
rpcuser=globalboostrpc
#(CHANGE THIS PASSWORD TO YOUR OWN PASSWORD)
rpcpassword=3mUvtWq1k1WhytGUgkTGzqemvLh97Hz9mtKwtdXaWn5m
# How many seconds GlobalBoost-Y will wait for a complete RPC HTTP request
# after the HTTP connection is established.
rpctimeout=30
# By default, only RPC connections from localhost are allowed. Specify
# as many rpcallowip= settings as you like to allow connections from
# other hosts (and you may use * as a wildcard character):
#rpcallowip=10.1.1.*
#rpcallowip=192.168.1.*
# Listen for RPC connections on this TCP port:
rpcport=8225
# You can use globalboostyd to send commands to GlobalBoost-Y/globalboostyd
# running on another host using this option:
#rpcconnect=127.0.0.1
# Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate
# with GlobalBoost -server or globalboostyd
#rpcssl=1
# OpenSSL settings used when rpcssl=1
rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
rpcsslcertificatechainfile=server.cert
rpcsslprivatekeyfile=server.pem
## Network-related settings:
# Run on the test network instead of the real BSTY network.
#testnet=1
# Connect via a socks proxy
#proxy=127.0.0.1:9050
# Select the version of socks proxy to use (4-5, default: 5)
#socks=5
# Use proxy to reach tor hidden services (default: same as -proxy)
#tor=
##############################################################
## Quick Primer on addnode vs connect ##
## Let's say for instance you use addnode=4.2.2.4 ##
## addnode will connect you to and tell you about the ##
## nodes connected to 4.2.2.4. In addition it will tell##
## the other nodes connected to it that you exist so ##
## they can connect to you. ##
## connect will not do the above when you 'connect' to it.##
## It will *only* connect you to 4.2.2.4 and no one else.##
## ##
## So if you're behind a firewall, or have other problems ##
## finding nodes, add some using 'addnode'. ##
## ##
## If you want to stay private, use 'connect' to only ##
## connect to "trusted" nodes. ##
## ##
## If you run multiple nodes on a LAN, there's no need for##
## all of them to open lots of connections. Instead ##
## 'connect' them all to one node that is port forwarded ##
## and has lots of connections. ##
## Thanks goes to [Noodle] on Freenode. ##
##############################################################
# Use as many addnode= settings as you like to attempt connection to specific peers
addnode=69.28.94.212
addnode=10.0.0.2:8333
addnode=104.255.33.229
addnode=107.150.60.98
addnode=108.61.48.17
addnode=138.91.64.21
addnode=192.99.35.133
addnode=194.135.89.79
addnode=198.27.97.172
addnode=23.227.190.216
addnode=5.9.67.48
addnode=74.120.220.54
addnode=77.249.199.235
addnode=84.242.139.4
addnode=213.5.27.245
addnode=69.28.94.212
addnode=69.90.132.249
# or use as many connect= settings as you like to connect ONLY to specific peers:
#connect=69.164.218.197
#connect=192.168.1.20:8333
# Do not use Internet Relay Chat to find peers.
noirc=0
# Maximum number of inbound+outbound connections.
#maxconnections=125
# Miscellaneous options
# Pre-generate this many public/private key pairs, so wallet backups will be valid
# after future transactions.
#keypool=100
# Add an optional transaction fee every time you send bsty.
#paytxfee=0.01
# Add timestamps to debug.log
#logtimestamps=1
# User interface options
# Start GlobalBoost-Y minimized
#min=1
# Minimize to the system tray
minimizetotray=0
[code]### globalboost.conf configuration file. Lines beginning with # are comments.
### Uncomment and edit options you wish to use.
## JSON-RPC options (for controlling a running GlobalBoost-Y/globalboostyd process)
# server=1 tells GlobalBoost-Y to accept JSON-RPC commands.
server=1
# You must set rpcuser and rpcpassword to secure the JSON-RPC api
# You should create your own new random password.
# The username and password MUST NOT be the same.
rpcuser=globalboostrpc
#(CHANGE THIS PASSWORD TO YOUR OWN PASSWORD)
rpcpassword=3mUvtWq1k1WhytGUgkTGzqemvLh97Hz9mtKwtdXaWn5m
# How many seconds GlobalBoost-Y will wait for a complete RPC HTTP request
# after the HTTP connection is established.
rpctimeout=30
# By default, only RPC connections from localhost are allowed. Specify
# as many rpcallowip= settings as you like to allow connections from
# other hosts (and you may use * as a wildcard character):
#rpcallowip=10.1.1.*
#rpcallowip=192.168.1.*
# Listen for RPC connections on this TCP port:
rpcport=8225
# You can use globalboostyd to send commands to GlobalBoost-Y/globalboostyd
# running on another host using this option:
#rpcconnect=127.0.0.1
# Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate
# with GlobalBoost -server or globalboostyd
#rpcssl=1
# OpenSSL settings used when rpcssl=1
rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
rpcsslcertificatechainfile=server.cert
rpcsslprivatekeyfile=server.pem
## Network-related settings:
# Run on the test network instead of the real BSTY network.
#testnet=1
# Connect via a socks proxy
#proxy=127.0.0.1:9050
# Select the version of socks proxy to use (4-5, default: 5)
#socks=5
# Use proxy to reach tor hidden services (default: same as -proxy)
#tor=
##############################################################
## Quick Primer on addnode vs connect ##
## Let's say for instance you use addnode=4.2.2.4 ##
## addnode will connect you to and tell you about the ##
## nodes connected to 4.2.2.4. In addition it will tell##
## the other nodes connected to it that you exist so ##
## they can connect to you. ##
## connect will not do the above when you 'connect' to it.##
## It will *only* connect you to 4.2.2.4 and no one else.##
## ##
## So if you're behind a firewall, or have other problems ##
## finding nodes, add some using 'addnode'. ##
## ##
## If you want to stay private, use 'connect' to only ##
## connect to "trusted" nodes. ##
## ##
## If you run multiple nodes on a LAN, there's no need for##
## all of them to open lots of connections. Instead ##
## 'connect' them all to one node that is port forwarded ##
## and has lots of connections. ##
## Thanks goes to [Noodle] on Freenode. ##
##############################################################
# Use as many addnode= settings as you like to attempt connection to specific peers
addnode=69.28.94.212
addnode=10.0.0.2:8333
addnode=104.255.33.229
addnode=107.150.60.98
addnode=108.61.48.17
addnode=138.91.64.21
addnode=192.99.35.133
addnode=194.135.89.79
addnode=198.27.97.172
addnode=23.227.190.216
addnode=5.9.67.48
addnode=74.120.220.54
addnode=77.249.199.235
addnode=84.242.139.4
addnode=213.5.27.245
addnode=69.28.94.212
addnode=69.90.132.249
# or use as many connect= settings as you like to connect ONLY to specific peers:
#connect=69.164.218.197
#connect=192.168.1.20:8333
# Do not use Internet Relay Chat to find peers.
noirc=0
# Maximum number of inbound+outbound connections.
#maxconnections=125
# Miscellaneous options
# Pre-generate this many public/private key pairs, so wallet backups will be valid
# after future transactions.
#keypool=100
# Add an optional transaction fee every time you send bsty.
#paytxfee=0.01
# Add timestamps to debug.log
#logtimestamps=1
# User interface options
# Start GlobalBoost-Y minimized
#min=1
# Minimize to the system tray
minimizetotray=0
Hi
how should this coin's .conf file look like ?
cheers
[/quote]how should this coin's .conf file look like ?
cheers
so sgminer should connect to a wallet that has this .conf ?
Code:
rpcuser=kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk
rpcpassword=hhhhhhhhhhhhhhhhhhhhhhhhhhhh
rpcport=8225
rpctimeout=30
rpcallowip=*
addnode=69.28.94.212
addnode=10.0.0.2:8333
addnode=104.255.33.229
addnode=107.150.60.98
addnode=108.61.48.17
addnode=138.91.64.21
addnode=192.99.35.133
addnode=194.135.89.79
addnode=198.27.97.172
addnode=23.227.190.216
addnode=5.9.67.48
addnode=74.120.220.54
addnode=77.249.199.235
addnode=84.242.139.4
addnode=213.5.27.245
addnode=69.28.94.212
addnode=69.90.132.249
[/code] rpcpassword=hhhhhhhhhhhhhhhhhhhhhhhhhhhh
rpcport=8225
rpctimeout=30
rpcallowip=*
addnode=69.28.94.212
addnode=10.0.0.2:8333
addnode=104.255.33.229
addnode=107.150.60.98
addnode=108.61.48.17
addnode=138.91.64.21
addnode=192.99.35.133
addnode=194.135.89.79
addnode=198.27.97.172
addnode=23.227.190.216
addnode=5.9.67.48
addnode=74.120.220.54
addnode=77.249.199.235
addnode=84.242.139.4
addnode=213.5.27.245
addnode=69.28.94.212
addnode=69.90.132.249
February 11, 2016, 12:03:29 PM
Code:
### globalboost.conf configuration file. Lines beginning with # are comments.
### Uncomment and edit options you wish to use.
## JSON-RPC options (for controlling a running GlobalBoost-Y/globalboostyd process)
# server=1 tells GlobalBoost-Y to accept JSON-RPC commands.
server=1
# You must set rpcuser and rpcpassword to secure the JSON-RPC api
# You should create your own new random password.
# The username and password MUST NOT be the same.
rpcuser=globalboostrpc
#(CHANGE THIS PASSWORD TO YOUR OWN PASSWORD)
rpcpassword=3mUvtWq1k1WhytGUgkTGzqemvLh97Hz9mtKwtdXaWn5m
# How many seconds GlobalBoost-Y will wait for a complete RPC HTTP request
# after the HTTP connection is established.
rpctimeout=30
# By default, only RPC connections from localhost are allowed. Specify
# as many rpcallowip= settings as you like to allow connections from
# other hosts (and you may use * as a wildcard character):
#rpcallowip=10.1.1.*
#rpcallowip=192.168.1.*
# Listen for RPC connections on this TCP port:
rpcport=8225
# You can use globalboostyd to send commands to GlobalBoost-Y/globalboostyd
# running on another host using this option:
#rpcconnect=127.0.0.1
# Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate
# with GlobalBoost -server or globalboostyd
#rpcssl=1
# OpenSSL settings used when rpcssl=1
rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
rpcsslcertificatechainfile=server.cert
rpcsslprivatekeyfile=server.pem
## Network-related settings:
# Run on the test network instead of the real BSTY network.
#testnet=1
# Connect via a socks proxy
#proxy=127.0.0.1:9050
# Select the version of socks proxy to use (4-5, default: 5)
#socks=5
# Use proxy to reach tor hidden services (default: same as -proxy)
#tor=
##############################################################
## Quick Primer on addnode vs connect ##
## Let's say for instance you use addnode=4.2.2.4 ##
## addnode will connect you to and tell you about the ##
## nodes connected to 4.2.2.4. In addition it will tell##
## the other nodes connected to it that you exist so ##
## they can connect to you. ##
## connect will not do the above when you 'connect' to it.##
## It will *only* connect you to 4.2.2.4 and no one else.##
## ##
## So if you're behind a firewall, or have other problems ##
## finding nodes, add some using 'addnode'. ##
## ##
## If you want to stay private, use 'connect' to only ##
## connect to "trusted" nodes. ##
## ##
## If you run multiple nodes on a LAN, there's no need for##
## all of them to open lots of connections. Instead ##
## 'connect' them all to one node that is port forwarded ##
## and has lots of connections. ##
## Thanks goes to [Noodle] on Freenode. ##
##############################################################
# Use as many addnode= settings as you like to attempt connection to specific peers
addnode=69.28.94.212
addnode=10.0.0.2:8333
addnode=104.255.33.229
addnode=107.150.60.98
addnode=108.61.48.17
addnode=138.91.64.21
addnode=192.99.35.133
addnode=194.135.89.79
addnode=198.27.97.172
addnode=23.227.190.216
addnode=5.9.67.48
addnode=74.120.220.54
addnode=77.249.199.235
addnode=84.242.139.4
addnode=213.5.27.245
addnode=69.28.94.212
addnode=69.90.132.249
# or use as many connect= settings as you like to connect ONLY to specific peers:
#connect=69.164.218.197
#connect=192.168.1.20:8333
# Do not use Internet Relay Chat to find peers.
noirc=0
# Maximum number of inbound+outbound connections.
#maxconnections=125
# Miscellaneous options
# Pre-generate this many public/private key pairs, so wallet backups will be valid
# after future transactions.
#keypool=100
# Add an optional transaction fee every time you send bsty.
#paytxfee=0.01
# Add timestamps to debug.log
#logtimestamps=1
# User interface options
# Start GlobalBoost-Y minimized
#min=1
# Minimize to the system tray
minimizetotray=0
### Uncomment and edit options you wish to use.
## JSON-RPC options (for controlling a running GlobalBoost-Y/globalboostyd process)
# server=1 tells GlobalBoost-Y to accept JSON-RPC commands.
server=1
# You must set rpcuser and rpcpassword to secure the JSON-RPC api
# You should create your own new random password.
# The username and password MUST NOT be the same.
rpcuser=globalboostrpc
#(CHANGE THIS PASSWORD TO YOUR OWN PASSWORD)
rpcpassword=3mUvtWq1k1WhytGUgkTGzqemvLh97Hz9mtKwtdXaWn5m
# How many seconds GlobalBoost-Y will wait for a complete RPC HTTP request
# after the HTTP connection is established.
rpctimeout=30
# By default, only RPC connections from localhost are allowed. Specify
# as many rpcallowip= settings as you like to allow connections from
# other hosts (and you may use * as a wildcard character):
#rpcallowip=10.1.1.*
#rpcallowip=192.168.1.*
# Listen for RPC connections on this TCP port:
rpcport=8225
# You can use globalboostyd to send commands to GlobalBoost-Y/globalboostyd
# running on another host using this option:
#rpcconnect=127.0.0.1
# Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate
# with GlobalBoost -server or globalboostyd
#rpcssl=1
# OpenSSL settings used when rpcssl=1
rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
rpcsslcertificatechainfile=server.cert
rpcsslprivatekeyfile=server.pem
## Network-related settings:
# Run on the test network instead of the real BSTY network.
#testnet=1
# Connect via a socks proxy
#proxy=127.0.0.1:9050
# Select the version of socks proxy to use (4-5, default: 5)
#socks=5
# Use proxy to reach tor hidden services (default: same as -proxy)
#tor=
##############################################################
## Quick Primer on addnode vs connect ##
## Let's say for instance you use addnode=4.2.2.4 ##
## addnode will connect you to and tell you about the ##
## nodes connected to 4.2.2.4. In addition it will tell##
## the other nodes connected to it that you exist so ##
## they can connect to you. ##
## connect will not do the above when you 'connect' to it.##
## It will *only* connect you to 4.2.2.4 and no one else.##
## ##
## So if you're behind a firewall, or have other problems ##
## finding nodes, add some using 'addnode'. ##
## ##
## If you want to stay private, use 'connect' to only ##
## connect to "trusted" nodes. ##
## ##
## If you run multiple nodes on a LAN, there's no need for##
## all of them to open lots of connections. Instead ##
## 'connect' them all to one node that is port forwarded ##
## and has lots of connections. ##
## Thanks goes to [Noodle] on Freenode. ##
##############################################################
# Use as many addnode= settings as you like to attempt connection to specific peers
addnode=69.28.94.212
addnode=10.0.0.2:8333
addnode=104.255.33.229
addnode=107.150.60.98
addnode=108.61.48.17
addnode=138.91.64.21
addnode=192.99.35.133
addnode=194.135.89.79
addnode=198.27.97.172
addnode=23.227.190.216
addnode=5.9.67.48
addnode=74.120.220.54
addnode=77.249.199.235
addnode=84.242.139.4
addnode=213.5.27.245
addnode=69.28.94.212
addnode=69.90.132.249
# or use as many connect= settings as you like to connect ONLY to specific peers:
#connect=69.164.218.197
#connect=192.168.1.20:8333
# Do not use Internet Relay Chat to find peers.
noirc=0
# Maximum number of inbound+outbound connections.
#maxconnections=125
# Miscellaneous options
# Pre-generate this many public/private key pairs, so wallet backups will be valid
# after future transactions.
#keypool=100
# Add an optional transaction fee every time you send bsty.
#paytxfee=0.01
# Add timestamps to debug.log
#logtimestamps=1
# User interface options
# Start GlobalBoost-Y minimized
#min=1
# Minimize to the system tray
minimizetotray=0
Hi
how should this coin's .conf file look like ?
cheers
how should this coin's .conf file look like ?
cheers
February 10, 2016, 05:45:21 PM
Hi
how should this coin's .conf file look like ?
cheers
how should this coin's .conf file look like ?
cheers
January 26, 2016, 08:21:23 PM
Thank you crackfoo for your support. It looks a really good pool 
.
.Thanks! We've found our first block already along with some UIS ones which we're merge mining on yescrypt as well.
January 26, 2016, 08:20:02 PM
Thank you crackfoo for your support. It looks a really good pool .
. January 26, 2016, 02:36:29 PM
January 13, 2016, 08:06:23 PM
yes, anyone can mine.
go to --> http://globalboost-y.com
or
https://globalboo.st
download the miner at the mining section and select your prefer mining pool.
post your hashrate.
go to --> http://globalboost-y.com
or
https://globalboo.st
download the miner at the mining section and select your prefer mining pool.
post your hashrate.
hello can i mine this coin at my pc ?? haw can get this plz
January 13, 2016, 08:03:03 AM
I open my wellet conx activ 14 and i have it set on 4 thread but i don't see any speed h/s???
January 12, 2016, 06:21:52 PM
hello can i mine this coin at my pc ?? haw can get this plz
January 03, 2016, 04:24:19 AM
Hi psychofractor,
I'm sorry for the late reply. I think the BST coin is dead and there is almost no node available. however, you are still not late for this one as the mining difficulty is very low, I addition the BSTY price is very cheap at the Bittrex Exchange (about 300uBTC).
https://bittrex.com/Market/Index?MarketName=BTC-BSTY
https://www.suchpool.pw/bsty/
Start Mining and trading your BSTY today!.
bstdev.
Hi guys, guess I am REALLY late for this one, but I found some BST in a wallet, any chance of exchanging them into BSTY?
Thanks for responding, bstdev. I wanted to exchange a seizable amount of BST, too bad that is not possible. I'll look into the possibility of mining.
PF
January 02, 2016, 04:48:50 PM
Hi psychofractor,
I'm sorry for the late reply. I think the BST coin is dead and there is almost no node available. however, you are still not late for this one as the mining difficulty is very low, I addition the BSTY price is very cheap at the Bittrex Exchange (about 300uBTC).
https://bittrex.com/Market/Index?MarketName=BTC-BSTY
https://www.suchpool.pw/bsty/
Start Mining and trading your BSTY today!.
bstdev.
Hi guys, guess I am REALLY late for this one, but I found some BST in a wallet, any chance of exchanging them into BSTY?
December 25, 2015, 12:17:33 PM
Hi guys, guess I am REALLY late for this one, but I found some BST in a wallet, any chance of exchanging them into BSTY?
December 16, 2015, 05:01:28 PM
Thanks guys,
Record message from PC or phone is now working. Live SMS chat is almost done and we have started the Android mobile app.
All The Best,
Bruce
Record message from PC or phone is now working. Live SMS chat is almost done and we have started the Android mobile app.
All The Best,
Bruce
Very COOL!! BSTY is the most advanced wallet design with great features, excellent GlobalBoost Team members
December 16, 2015, 11:40:29 AM
Thanks guys,
Record message from PC or phone is now working. Live SMS chat is almost done and we have started the Android mobile app.
All The Best,
Bruce
Record message from PC or phone is now working. Live SMS chat is almost done and we have started the Android mobile app.
All The Best,
Bruce
December 16, 2015, 11:36:19 AM
December 15, 2015, 01:33:41 PM
HOW-TO RUN YESCRYPT MINER ON MACHINES WITH AMD PROCESSORS:
This tutorial includes the use of Virtualbox if you are running Windows, if you are unfamiliar with running Virtualbox or any other virtual environment you choose ,it will not be covered here, please do that first.
If running Linux environment you can follow the terminal commands in the post. ( all terminal commands are in green )
1) Run a Linux based environment either directly or virtually on Windows (Virtual users on Windows make sure to allocate the number of cores of your processor that you wish to use in the Settings)
2) Find your processor info, this is needed to specify the build parameters when configuring the yescrypt miner.
Open a terminal and enter:
grep -m1 -A3 "vendor_id" /proc/cpuinfo
example output:
vendor_id: AuthenticAMD
cpu family: 15
model: 35, 43, 75 or 107
stepping: 1 or 2
model name: AMD Athlon(tm) 64 X2 Dual Core Processor
The information that you need most is cpu family and model to correctly build the miner. We will use this information in step #5
3) You will need some prerequisites before building:
Install Build Dependencies on Debian, Ubuntu and other APT-based distros:
sudo apt-get install build-essential libcurl4-openssl-dev
Install Build Dependencies on Fedora, RHEL, CentOS and other yum-based distros:
sudo yum install gcc make curl-devel
Install Build Dependencies on OpenSUSE and other ZYpp-based distros:
sudo zypper in gcc make libcurl-devel
4) Obtain miner : in this case I am using the noncepool miner (no longer around) posting.
git clone https://github.com/noncepool/cpuminer-yescrypt.git (if your new virtual machine does not have "git" just follow the prompt output)
cd cpuminer-yescrypt
./autogen.sh (again, if a fresh Linux install you may have to install auto-tools sudo apt-get install automake )
5) Here is where you will need the cpu information from above. Follow this link http://www.opikdesign.com/kios/procie_kernel/ and scan the list for your cpu family and model. You may notice that there are also Intel based listings for those of you who may want to double check the effectiveness of your current build.
Once your family and model are found, the info we want is related to CFLAGS There will be a box with 3 lines of info you want the middle line.
example: CFLAGS="-march=k8 -O2 -pipe -fomit-frame-pointer" (Please make sure you check for 32bit or 64bit )
Now we can continue with building the miner, I will use our example above which is for a 32 bit AMD Athlon 64 X2 (now back to terminal)
./configure CFLAGS="-march=k8 -O2 -pipe -fomit-frame-pointer" ( enter your specific CFLAGS command after ./configure )
make
You should have no errors reported in the compilation, now you can run the miner using a pool of your choice with the following command:
example:
./minerd -a yescrypt -o stratum+tcp://stratum1.suchpool.pw:3322 -u yourusername -p yourpassword
You can also control the number of cores you want to use by using the -t command.
example:
./minerd -a yescrypt -o stratum+tcp://stratum1.suchpool.pw:3322 -u yourusername -p yourpassword -t 3 (for 3 cores etc.)
Please note that you can use any pool you like, the above is meant as an example only.
I hope this helps those new to mining, Linux, and BSTY or those who have wanted use their AMD machines and couldn't
If you like it: XzmZG4tjj8DJZJcADUFYAChRETm1CkDkAY
This tutorial includes the use of Virtualbox if you are running Windows, if you are unfamiliar with running Virtualbox or any other virtual environment you choose ,it will not be covered here, please do that first.
If running Linux environment you can follow the terminal commands in the post. ( all terminal commands are in green )
1) Run a Linux based environment either directly or virtually on Windows (Virtual users on Windows make sure to allocate the number of cores of your processor that you wish to use in the Settings)
2) Find your processor info, this is needed to specify the build parameters when configuring the yescrypt miner.
Open a terminal and enter:
grep -m1 -A3 "vendor_id" /proc/cpuinfo
example output:
vendor_id: AuthenticAMD
cpu family: 15
model: 35, 43, 75 or 107
stepping: 1 or 2
model name: AMD Athlon(tm) 64 X2 Dual Core Processor
The information that you need most is cpu family and model to correctly build the miner. We will use this information in step #5
3) You will need some prerequisites before building:
Install Build Dependencies on Debian, Ubuntu and other APT-based distros:
sudo apt-get install build-essential libcurl4-openssl-dev
Install Build Dependencies on Fedora, RHEL, CentOS and other yum-based distros:
sudo yum install gcc make curl-devel
Install Build Dependencies on OpenSUSE and other ZYpp-based distros:
sudo zypper in gcc make libcurl-devel
4) Obtain miner : in this case I am using the noncepool miner (no longer around) posting.
git clone https://github.com/noncepool/cpuminer-yescrypt.git (if your new virtual machine does not have "git" just follow the prompt output)
cd cpuminer-yescrypt
./autogen.sh (again, if a fresh Linux install you may have to install auto-tools sudo apt-get install automake )
5) Here is where you will need the cpu information from above. Follow this link http://www.opikdesign.com/kios/procie_kernel/ and scan the list for your cpu family and model. You may notice that there are also Intel based listings for those of you who may want to double check the effectiveness of your current build.
Once your family and model are found, the info we want is related to CFLAGS There will be a box with 3 lines of info you want the middle line.
example: CFLAGS="-march=k8 -O2 -pipe -fomit-frame-pointer" (Please make sure you check for 32bit or 64bit )
Now we can continue with building the miner, I will use our example above which is for a 32 bit AMD Athlon 64 X2 (now back to terminal)
./configure CFLAGS="-march=k8 -O2 -pipe -fomit-frame-pointer" ( enter your specific CFLAGS command after ./configure )
make
You should have no errors reported in the compilation, now you can run the miner using a pool of your choice with the following command:
example:
./minerd -a yescrypt -o stratum+tcp://stratum1.suchpool.pw:3322 -u yourusername -p yourpassword
You can also control the number of cores you want to use by using the -t command.
example:
./minerd -a yescrypt -o stratum+tcp://stratum1.suchpool.pw:3322 -u yourusername -p yourpassword -t 3 (for 3 cores etc.)
Please note that you can use any pool you like, the above is meant as an example only.
I hope this helps those new to mining, Linux, and BSTY or those who have wanted use their AMD machines and couldn't
If you like it: XzmZG4tjj8DJZJcADUFYAChRETm1CkDkAY
December 15, 2015, 10:04:06 AM
Hi,
What is the problem Bittrex? Delisting or not ...
What is the problem Bittrex? Delisting or not ...
December 14, 2015, 02:37:16 PM
Was there any resolution for an AMD cpu miner??
I have found a way to successfully run the noncepool-cpuminer-yescrypt if it is built in linux with the correct CFLAGS for the processor. Perhaps others knew this already and I just missed it. So problem solved by running virtualbox Linux instance in Windows and compile the above mentioned miner with appropriate AMD processor family CFLAGS
I can post a how-to if anyone thinks it might be useful.
Hi Cryptophilanthropist,
Sounds GREat please post
Bruce
I will post a how-to with some output specs later today or early tomorrow, this should definitely help strengthen the network. Jump to: