Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums

(Advanced Search)

Forum Statistics
» Members: 1,429
» Latest member: ManCreature
» Forum threads: 354
» Forum posts: 2,140

Full Statistics

Online Users
There are currently 24 online users.
» 0 Member(s) | 24 Guest(s)

Latest Threads
[Awesome Miner] - Powerfu...
Forum: CryptoCurrency
Last Post: Monet
06-24-2019, 08:50 PM
» Replies: 0
» Views: 18
Raspberry Pi 4: $35 compu...
Forum: Skywire
Last Post: mrtom31
06-24-2019, 07:25 AM
» Replies: 0
» Views: 21
Claymore's Dual Ethereum ...
Forum: CryptoCurrency
Last Post: Monet
06-24-2019, 07:04 AM
» Replies: 0
» Views: 17
[ANN] sgminer v5.6.0 - op...
Forum: CryptoCurrency
Last Post: Monet
06-22-2019, 07:42 PM
» Replies: 0
» Views: 20
Claymore’s Miner Manager ...
Forum: CryptoCurrency
Last Post: Monet
06-21-2019, 08:57 PM
» Replies: 0
» Views: 26
[JCE]Fast & stable CN/v8/...
Forum: CryptoCurrency
Last Post: Monet
06-21-2019, 07:40 AM
» Replies: 0
» Views: 19
T-Rex 0.12.0 NVIDIA GPU m...
Forum: CryptoCurrency
Last Post: Monet
06-19-2019, 08:46 PM
» Replies: 0
» Views: 29
MSI Afterburner 4.6.2 Dow...
Forum: CryptoCurrency
Last Post: Monet
06-18-2019, 09:17 PM
» Replies: 0
» Views: 35
Pi Skyminer Setup brickwa...
Forum: Skywire
Last Post: skyguy
06-18-2019, 05:29 AM
» Replies: 1
» Views: 58
[Minera v0.9.1] Your next...
Forum: CryptoCurrency
Last Post: Monet
06-18-2019, 12:11 AM
» Replies: 0
» Views: 38

 
  EthMonitoring \ EthControl v1.09 (PhoenixMiner,EWBF, Claymore’s, CCMiner, AntMiner, A
Posted by: Monet - 06-04-2019, 07:16 PM - Forum: CryptoCurrency - No Replies

Supported OS:

Windows 7/10
Ubuntu
EthOS
nvOC
SimpleMining OS

Current version 1.0.9:


  • Added NoncerPro support

  • Added lolMiner support port: 8080

  • Added more detailed view of T-Rex stats.

  • Fixed GMiner reading

  • Added TTMiner support

  • Added NBMiner support

  • Fixed claymore fan&temp issue

  • Supports CCMiner auto-restart when CPU does not validate.

  • Supports EWBF auto-restart when cuda device thread exited.

  • Adds GPU fan speed monitoring with EWBF miner

  • Bulk updates for remote configuration / install.

  • Ethminer full monitoring with GPU hashrate, GPU temp and GPU fan speeds.

  • Remote rig reboot support.

  • Remote stop/start support for mining software.

  • Web console for remote diagnostic

  • Automatic miner software installation support and updates

Current version 0.0.33 - 1.0.8:

Support SMS/Telegram/Push notifications when:
– GPU temperature gets higher than required
– GPU temperature gets lower than required
– Miner is not responding for X amount of minutes
– GPU Fan speed is lower than X
– GPU Fan speed is higher than X
– Miner hashrate too low
– GPU hashrate too low

Supports multiple miners with one local software installed.

Log file support.
CCMiner-Alexis 1.0
CCMiner Palgin skunk mod
CCMiner SP Skunk mods
CCMiner >= 2.0
EWBF Support
XMR-Stak
SGMiner
dstm ZM
EthMiner
BMiner
PhoenixMiner
Excavator by NiceHash (1.4, 1.5)
Claymore’s Dual Miner support
Added SSL support for data update.
ASIC AntMiner support

Web service

Profit monitoring
Dailiy profit graph
WhatToMine.com 2 profit calculation based on current hashrate and power
Hashrate graphs
Temp graphs
Power usage graphs

EthControl v0.0.19a

Supports CCMiner auto-restart when CPU does not validate.
Supports EWBF auto-restart when cuda device thread exited.
Bulk updates for remote configuration / install.
Ethminer full monitoring with GPU hashrate, GPU temp and GPU fan speeds.
Remote rig reboot support.
Remote stop/start support for mining software.
Web console for remote diagnostics
Automatic miner software installation support and updates
GPU monitoring.
Afterburner profile loading
Starts with windows automatically
Crash reports
CCMiner “invalidate cpu” error auto-restart
Easily deploy custom ccminer forks, claymore updates, custom software to multiple rigs

# Supports #

CCminer
Cast XMR
EthMiner
Claymore dual miner
ZM dstm
EWBF
eMiner
bMiner
Phoenix Miner
Excavator
Gateless gate
XMR-Stak
Cast-XMR

How to use:

Download windows binary from here
Download EthMonitoring

iOShttps://itunes.apple.com/us/app/ethmonitoring/id1257053708

Android
https://play.google.com/store/apps/details?id=com.jldev.ethmonitoring

Print this item

  PhoenixMiner 4.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
Posted by: Monet - 06-03-2019, 12:49 PM - Forum: CryptoCurrency - No Replies

Important message for everyone that is running older versions of PhoenixMiner (before 4.2):

Changes in version 4.2c (since 4.1c):


  • Added support for dual mining Ethash and Blake2s on Nvidia GPUs

  • Added new Nvidia kernels v3 with slightly higher hashrate and lower power consumption (up to about 1-1.5% less power). The new kernels are supported only on GTX1050/1060/1070/1080/Ti GPUs and are enabled by default on these GPUs. Note that you can't use these kernels for dual-mining, only -nvkernel 2 works for dual mining on Nvidia.

  • Added new command-line option -nvkernel to select the old (v1 CUDA kernels from PhoenixMiner 3.5), newer (v2 introduced with PhoenixMiner 4.0), or the latest CUDA kernels (v3). The possible values are 0 (auto; the default, selects the best kernel for each GPU), 1 , 2, or 3 (forces v1, v2, or v3 kernels respectively). Note that only v2 CUDA kernels support dual mining.

  • Added experimental support for ProgPOW mining of Bitcoin Interest (BCI). Note that the kernels are not optimized and only work on AMD. You must add -coin bci to the command line (or COIN: bci to your epools.txt file) in order to mine BCI.

  • Added parameter to enable or disable driver-specific optimizations on Nvidia GPUs. Use -nvdo 1 (the default is 0) to enable the optimizations. This won't change hashrate (or will change it only slightly) but can make the cards more stable depending on the concrete Nvidia driver.

  • Added support for EthereumStratum/2.0.0 protocol (use -proto 5 if the pool requires it).

  • AMD hardware control code was rewritten, now should be more stable and work on older cards too

  • Added command-line option -fcm to set the way fans are controlled (AMD/Windows only). The possible values are 0 (auto; the default behavior), 1 (use VBIOS/driver), 2 (force custom control of the fans regardless of VBIOS/drivers fan curves, etc). Use -fcm 2 if the fans are not controlled properly or at all

  • Added support for Radeon VII

  • Added support for Windows AMD drivers 19.3.3

  • Increased the maximum supported DAG epoch to 329. This should be fine for at least a year or so.

  • Added support for direct mining without DAG switching of Yocoin (YOC)Bitcoiin2Gen (B2G)Ethersocial (ESN)Atheios (ATH), and REOSC. See the -coin parameter in Readme.txt for more information.

  • Fixed the slower DAG generation on Vega and Radeon VII GPUs

  • Fixed the problem with the watchdog timer when solo mining

  • Other small improvements and fixes.
PhoenixMiner is fast (arguably the fastest) Ethash (ETH, ETC, Muiscoin, EXP, UBQ, etc.) miner that supports
both AMD and Nvidia cards (including in mixed mining rigs). It runs under Windows x64 and Linux x64
and has a developer fee of 0.65% (the lowest in the industry). This means that every 90
minutes the miner will mine for us, its developers, for 35 seconds.

PhoenixMiner also supports Ubqhash for mining UBQ, ProgPOW for mining BCI, and dual mining
Ethash/Ubqhash with Blake2s.

The speed is generally faster than Claymore's Ethereum miner in eth only mode
(we have measured about 0.4-1.3% speed improvement but your results may be slightly lower or
higher depending on the GPUs). To achieve highest possible speed on AMD cards it may be needed
to manually adjust the GPU tune factor (a number from 8 to about 400, which can be changed
interactively with the + and - keys while the miner is running).

If you have used Claymore's Dual Ethereum miner, you can switch to PhoenixMiner with
minimal hassle as we support most of Claymore's command-line options and confirguration
files.


1. Quick start

You can download PhoenixMiner 4.2c from here:

https://mega.nz/#F!TQcCnADA!rEvfBgr0BSsqcVlnpFYtGQ

Examples of settings for different pools.

ethermine org (ETH):
PhoenixMiner.exe -pool eu1 ethermine org:4444 -pool2 us1 ethermine org:4444 -wal YourEthWalletAddress.WorkerName -proto 3
ethermine org (ETH, secure connection):
PhoenixMiner.exe -pool ssl: //eu1 ethermine org: 5555 -pool2 ssl: //us1 ethermine org: 5555 -wal YourEthWalletAddress.WorkerName -proto 3
ethpool org (ETH):
PhoenixMiner.exe -pool eu1 ethpool org:3333 -pool2 us1 ethpool org:3333 -wal YourEthWalletAddress.WorkerName -proto 3
dwarfpool com (ETH):
PhoenixMiner.exe -pool eth-eu dwarfpool com:8008 -wal YourEthWalletAddress / WorkerName -pass x
nanopool org (ETH):
PhoenixMiner.exe -pool eu1 nanopool org:9999 -wal YourEthWalletAddress / WorkerName -pass x
nicehash (ethash):
PhoenixMiner.exe -pool stratum + tcp: //daggerhashimoto eu nicehash com: 3353 -wal YourBtcWalletAddress -pass x -proto 4 -stales 0
f2pool (ETH):
PhoenixMiner.exe -epool eth f2pool com:8008 -ewal YourEthWalletAddress -pass x -worker WorkerName
miningpoolhub (ETH):
PhoenixMiner.exe -pool us-east ethash-hub miningpoolhub com:20535 -wal YourLoginName.WorkerName -pass x -proto 1
coinotron com (ETH):
PhoenixMiner.exe -pool coinotron com:3344 -wal YourLoginName.WorkerName -pass x -proto 1
ethermine org (ETC):
PhoenixMiner.exe -pool eu1-etc ethermine org:4444 -wal YourEtcWalletAddress.WorkerName
dwarfpool com (EXP):
PhoenixMiner.exe -pool exp-eu dwarfpool com:8018 -wal YourExpWalletAddress / WorkerName
miningpoolhub (MUSIC):
PhoenixMiner.exe -pool europe ethash-hub miningpoolhub com:20585 -wal YourLoginName.WorkerName -pass x -proto 1
ubiqpool (UBIQ):
PhoenixMiner.exe -pool stratum + tcp: //eu ubiqpool io: 8008 -wal YourUbiqWalletAddress -pass x -worker WorkerName
minerpool net (PIRL):
PhoenixMiner.exe -pool pirl minerpool net:8002 -wal YourPirlWalletAddress -pass x -worker WorkerName
dodopool com (Metaverse ETP):
PhoenixMiner.exe -pool etp dodopool com:8008 -wal YourMetaverseETPWalletAddress -worker Rig1 -pass
minerpool net (Ellaism):
PhoenixMiner.exe -pool ella minerpool net:8002 -wal YourEllaismWalletAddress -worker Rig1 -pass x

Pool options:

[b]3. Command-line arguments

Note that PhoenixMiner supports most of the command-line options of Claymore's dual Ethereum miner
so you can use the same command line options as the ones you would have used with Claymore's miner.
[/b]
-pool <host[Image: clear.png]ort> Ethash pool address (prepend the host name with ssl:// for SSL pool, or http:// for solo mining)
-wal <wallet> Ethash wallet (some pools require appending of user name and/or worker)
-pass <password> Ethash password (most pools don't require it, use 'x' as password if unsure)
-worker <name> Ethash worker name (most pools accept it as part of wallet)
-proto <n> Selects the kind of stratum protocol for the ethash pool:
1: miner-proxy stratum spec (e.g. coinotron)
2: eth-proxy (e.g. dwarfpool, nanopool) - this is the default, works for most pools
3: qtminer (e.g. ethpool)
4: EthereumStratum/1.0.0 (e.g. nicehash)
5: EthereumStratum/2.0.0
-coin <coin> Ethash coin to use for devfee to avoid switching DAGs:

auto: Try to determine from the pool address (default)
eth: Ethereum
etc: Ethereum Classic
exp: Expanse
music: Musicoin
ubq: UBIQ
pirl: Pirl
ella: Ellaism
etp: Metaverse ETP
pgc: Pegascoin
akroma: Akroma
whale: WhaleCoin
vic: Victorium
nuko: Nekonium
mix: Mix
egem: EtherGem
aura: Aura
hbc: Hotelbyte Coin
gen: Genom
etz: EtherZero
clo: Callisto
dbix: DubaiCoin
moac: MOAC
etho: Ether-1
etcc: EtherCC
yoc: Yocoin
b2g: Bitcoiin2Gen
esn: Ethersocial
ath: Atheios
reosc: REOSC

4. Configuration files

Note that PhoenixMiner supports the same configuration files as Claymore's dual Ethereum miner
so you can use your existing configuration files without any changes.

Instead of using command-line options, you can also control PhoenixMiner with configuration
files. If you run PhoenixMiner.exe without any options, it will search for the file config.txt
in the current directory and will read its command-line options from it. If you want, you can
use file with another name by specifying its name as the only command-line option
when running PhoenixMiner.exe.

You will find an example config.txt file in the PhoenixMiner's directory.

Instead of specifying the pool(s) directly on the command line, you can use another configuration
file for this, named epools.txt. There you can specify one pool per line (you will find an example
epools.txt file in the PhoenixMiner's directory).

For the dual mining pools, you can use the dpools.txt file, which has the same format as epools.txt
but for the secondary coin. You will find an example epools.txt file in the PhoenixMiner's directory.
Note that unlike the epools.txt, which is loaded each time when the miner starts, the dpools.txt file
is only read if you specify a dual mining pool on the command line with -dpool, or at least add
the -dcoin blake2s command-line option.

The advantages of using config.txt and epools.txt/dpools.txt files are:
- If you have multiple rigs, you can copy and paste all settings with these files
- If you control your rigs via remote control, you can change pools and even the miner options by
uploading new epools.txt files to the miner, or by uploading new config.txt file and restarting
the miner.

5. Remote monitoring and management

Phoenix miner is fully compatible with Claymore's dual miner protocol for remote monitoring and
management. This means that you can use any tools that are build to support Claymore's dual miner,
including the "Remote manager" application that is part of Claymore's dual miner package.

We are working on much more powerful and secure remote monitoring and control functionality and
control center application, which will allow better control over your remote or local rigs and some
unique features to increase your mining profits.

Print this item

  Gone from whitelist!!
Posted by: radarlarry1 - 06-01-2019, 06:34 AM - Forum: Skywire - Replies (1)

I have an 8 node miner.  I have them connected to WIFI via CAT5E from a wireless repeater.  They've been happily running at 99.5% for the past month.  Apparently, the repeater went down sometime while I was out today.  I recycled the main router, the repeater and the nodes.  I have 4 nodes up and running, so far.  I checked the whitelist and was greeted to an NA, as usual when the nodes are down.  Now it says, "No results" and "No Miners
You don't have an approved miner registered on your account. Submit an application, or wait for your application to be approved."  WTF?  I know I need to get a new repeater, but do I really have to re-submitt to the whitelist?  Why did it drop them all?  Never did that before.  Just said N/A until they came back up.  Any insight to help me understand what happened?
Larry B.

Print this item

  [ANN] FarmCP - Web-based Rig Control Panel on your rig (Win,Linux, BAMT)
Posted by: Monet - 05-30-2019, 06:12 PM - Forum: CryptoCurrency - No Replies

Hello guys,

I want to share a little dashboard I've made for my farm. I am using BAMT 1.3 on my rigs, I wanted to at least be able to switch pools without sshing to each of my rigs.

Features:

*Work for win in just click (not register)
* only need to install on one of your rigs
* works on any Linux-based system
* open-source and free
* pretty cool dashboard on which you can monitor all your rigs hashrate, temperature and rejected shares
* ability to add a pool to all of your rigs at the same time, and switch pools on each rig
* anyone can contribute new features (Ruby on Rails project)

Download and installation instructions:

Download for windows: 
https://mega.nz/#!bd9R0ACD!09vSAAguEp6P-ak2JvPgEx5jCxV4XWIS5jZrvFIVmsk

https://github.com/mrbrdo/farmcp/blob/master/README.md

Donations welcome: 1NfCD5dEJv6MxwiAFF4S68t4r7QxkCSnPs (BTC)

Screenshots:
[Image: ?u=http%3A%2F%2Fi.imgur.com%2Fs4svPDX.pn...D3KR4ODr_g]
[Image: ?u=http%3A%2F%2Fi.imgur.com%2FAazewCo.pn...KsYi2ma1wQ]

Print this item

  DIY Check your node on OLED display
Posted by: mrtom31 - 05-17-2019, 07:45 PM - Forum: Skywire - Replies (2)

Hello,

I wanted to share the little code I made today.

Description:

It uses the API request to check if your node are connected or not and then it display on OLED ssd1306
It should also support ssd1309, ss1325, ss1331, sh1106 if you substitute the name in the code.



Requirements:

  • And OLED SSD1306 on i2c
  • you need latest luma.oled
  • check if your device is available here
Install

Code:
cd ~
git clone https://github.com/mrtom31/SkyDisplay.git
cd SkyDisplay
echo "MyPasswordSkycoin">secret.txt
Change "MyPasswordSkycoin" by ... I let you guess.

Usage
Check if it works first:
Code:
python OLEDSkycoinDisplay.py

Then use
Code:
crontab -e

to setup a schedule and add those lines:
Code:
* 8 * * * /home/pi/SkyDisplay/OLEDSkycoinDisplay.py
* 19 * * * kill $(cat /home/pi/SkyDisplay/pid.txt)

Replace
Code:
/home/pi
with the location where you cloned the repository.


Tell me if you have any issue.

[Image: giphy.gif]

Also it can scroll automatically with delay if you have lot of node. It doesn't show here since I only have 5 nodes.

Print this item

  go install -> gcc can't allocate
Posted by: mrtom31 - 05-08-2019, 11:50 PM - Forum: Skywire - Replies (1)

Code:
/usr/local/go/pkg/tool/linux_arm64/link: running gcc failed: fork/exec /usr/bin/gcc: cannot allocate memory

github.com/skycoin/skywire/cmd/ssh/sshc
github.com/skycoin/skywire/cmd/ssh/sshs
user@node1:~/go/src/github.com/skycoin/skywire/cmd$ free -h
             total        used        free      shared  buff/cache   available
Mem:           481M         78M        294M        644K        108M        392M
Swap:          240M         63M        176M

user@node1:~/go/src/github.com/skycoin/skywire/cmd$ go version
go version go1.9.2 linux/arm64

Hi,
During go install process gcc can't allocate but I have 13GB free disk space.
Idk what's going on.

Print this item

  ArchlinuxARM on OrangePiPrime + skywire
Posted by: moe_narrow - 05-03-2019, 10:23 PM - Forum: Skywire - No Replies

Perhaps some of you have seen me around on telegram @moe_narrow

I don't get e-mails from skywug so you can contact me on telegram if you have questions.

I would like to document how I created ArchlinuxARM images for the OrangePiPrime
(or the general process which works for other boards)

Once you have archlinux on your board; setting up skywire is trvial because I have submitted PKGBUILD scripts for various skycoin repos to the Archlinux User Repos.
This means that all the hard parts are handled by the AUR package manager (such as yay)
Or you can (in just three steps) build and install the package yourself.

The other, major advantage of archlinux is that you can install a current version of golang with the following command:
```
sudo pacman -S go-pie
```

or

```
sudo pacman -S go
```

It's recommended to use go-pie


CREATING THE IMAGE

The hardest part is getting an archlinuxARM image that will boot on your board. The rest is very easy.
The officially supplied images (for archlinux on orangepiprime) do not work.
Perhaps you might have better luck with by default working images for different boards. 

This method is a bit of a Frankenstein method, but it works (eventually).

To start; take a working image which will boot on your board

For the prime, let's start with this armbian image:
https://dl.armbian.com/orangepiprime/Deb...7z.torrent

And then get the archlinuxARM you want to use:
http://fl.us.mirror.archlinuxarm.org/os/...est.tar.gz


I recommend this one, however with the orangePiPrime it seems that I cannot mount USBs with this.
I will try this with the generic armv7 tarball and see if that fixes the USB issues for the prime.

*EDIT*
There are several sources you can use for archlinuxarm which don't work right or you will later observe have some kind of ip conflict because of mac addresses being the same.
This one didn't seem to be the right one for me with the prime for whatever reason. I am going to link to a working image on github; if you are trying to repeat this process; I have gotten it to work before but I don't recall the correct sources.
*EDIT*

For the next step, I use gnome-disks-utility. You can use something else if you wish.

Extract the armbian image and attach it as a disk image using gnome-disks.
Just so you can see what you are looking at


https://ibb.co/hK8mVdM
https://ibb.co/B3bJm70



next, create a new disk image of the same size. Name it whatever you like


https://ibb.co/R2fndqh
https://ibb.co/dcbzk4X
https://ibb.co/Sv6VPNK

Note the location in `/dev` as shown.

https://ibb.co/sCJ5FV9

then, open up a terminal in the directory where you extracted armbian and execute the following:
```
sudo dcfldd if=Armbian_5.75_Orangepiprime_Debian_stretch_next_4.19.20.img of=/dev/loop1
```
If you do not have dcfldd you can use dd

Click the triangle 'play' button to mount the root filesystem and follow the link that says 'Mounted at' to view the root filesystem.
Either open a terminal in this location or open a file manager with sudo (sudo thunar, sudo nautilus, etc..) in this location.

https://ibb.co/ZKNq6J8

Remove every folder except /boot. Make sure you check for hidden and trash / lost+found files


https://ibb.co/RS17hVg

Now what you want to do is make a copy of ArchLinuxARM-aarch64-latest.tar.gz or whatever archlinuARM you downloaded.


Open the archive (without extracting it) of the copy you wish to modify and delete the /boot folder.

https://ibb.co/7bGBwSJ


Now, to extract the contents into the mounted disk image that you deleted everything but /boot from

YOU MUST BE ROOT FOR THIS (not with sudo)

```
bsdtar -xpf '/path/to/ArchLinuxARM-aarch64-latest-noboot.tar.gz' -C /path/to/mounted/image/rootfs/131e06c6-00b8-4657-8b48-6e6c806305bb/
```


Now if you have done everything correctly, you can unmount the images and you will have an archlinuxARM image you can write to a microsd and which will hopefully boot on your board.

So I will test what I have to make sure I did it right.

The default user:pass is alarm:alarm and root:root

RESULTS

The board boots, but strangely I could not ssh into it!

This happened before and I fixed it by using a different archlinuxarm rootfs. I forget which one, but I have already made a working image for this board.
The image for this posted already on https://github.com/0pcom/skyalarm in the releases.
I will update soon; in case you don't want to go through this whole process and figure out what is missing. However, the above is still useful for reference.

Here is a (mostly) unconfigured image for the orangepiprime:
https://github.com/0pcom/skyalarm/releas...img.tar.xz
sorry it' so big, there are some makedependancies for still installed. Go and yay are already installed.


INITIAL CONFIGURATION

When you have logged in via ssh, the first thing to do is initialize & populate the pacman keyring (as root)

```
pacman-key --init
pacman-key --populate archlinuxarm
```
then update the keyring

```
pacman -S archlinuxarm-keyring
```
then update the filesystem

```
pacman -Syy
pacman -Syu
```

If you get an error about a key; locally sign the key to trust it

```
pacman-key --lsign DE08F924EEE93832DABC642CA8DC761B1C0C0CFC
```

when your system is up to date and you make a user account; it's time to set up skywire.

But first we need an AUR package manager. And you must be a regular user (not root) for some of the following steps.
A wonderful command-line utility for AUR package management which is written in golang is Y.A.Y. (yet another yaourt aur package manager)

yay should be included in the skyalarm image, but lets's assume for a moment that you don't have yay.
What do you do? Here is the simple 3 step process of making a package from the Archlinux User repos.

```
wget https://aur.archlinux.org/cgit/aur.git/p...UILD?h=yay
mv PKGBUILD?h=yay PKGBUILD
makepkg -scif
```

You will be prompted for the sudo password to install yay, once it is built.

When that has taken place, yay will do what you just did for you (from now on).

To install skywire

```
yay -S skywire
```

I have just today updated the PKGBUILD for skywire to include the system.d services.

```
sudo systemctl start skywire-manager
```
starts the node and manager.

```
sudo systemctl start skywire-node
```

starts a node pointed at 192.168.0.2

If you have a different manager IP address for your DIY setup; edit the script at /usr/bin/skywire-node-miner with the IP address of your manager instance.


BUT WAIT, THERE'S MORE!

```
yay -S skywire-mainnet
```
run a node on the mainnet. After installation with the above command; run the setup with
```
skywire-setup
```

Or, run a skycoin node:

```
yay -S skycoin

```

I have also packaged cx, cxo, and the skywire-discovery server.

UPDATING
For now, the package version for skywire is autogenerated at the time of the build.
To update, simply reinstall the package. You will get the latest commits from either master or mainnet.


CONFIGURING LOCAL PACKAGE REPOS

Something you can do for bootstrapping or to update faster is to make a repository for built packages.
They can be built once and installed on every board rather than having to pull the sources from github and build for each board.

To do this, probably the simplest way, use darkhttpd to serve the directory containing your package repo.
Build the package with one board, then put the built package in that directory. I recommend signing the packages you create; then use the repo-add tool to create your package repo

You can configure pacman.conf to include your repo, take a look at skytergos repo on my github and feel free to message me if you have any questions.

Print this item

  Updating or editing whitelist information
Posted by: radarlarry1 - 04-21-2019, 11:51 PM - Forum: Skywire - Replies (1)

Hello all!  I submitted my whitelist application 4 days ago.  I realize now that I did not enter proper architecture.  I think I just said 7 Orange Pi Primes and I don't think I had a wallet at that time.  I do now though.  Is that part of the whitelist application?  I can't remember.  Anyway, I'd like to be able to edit the info in the application to be more precise.  Even location, I only put Las Vegas, NV... not my address.  Am I correct in thinking that if my nodes are successfully whitelisted, it could not happen prior to 1 June. 2019?
Thanks,
Larry B.

Print this item

  Orange Pi Prime miner issues
Posted by: Radarlarrry - 04-17-2019, 09:05 PM - Forum: Skywire - No Replies

When I checked the monitor this morning, all seven nodes were up.  (One bad OPi)  However, in the STARTED column #7 said 10 hours ago, the rest said 38 minutes ago.  Does this indicate 1 thru 6 rebooted 38 minutes prior?  If so, why only 1-6 and not 7?  Is there an error log somewhere so I can see what happened?  Can I tell how long they were offline?
Now it's done it again, 2 hours ago... all except #7.

P.S. I don't have static IPs set for the Pis. Could this be happening when the addresses change? I would set them, but not exactly sure how to do it. The only info I could find on it is for RPi. I also did not do the port changes, as it seems to work fine on the ports as configured. But, what do I know?

Thanks,
Larry B.
[Image: Skyminer-2.jpg]

[Image: Skyminer3.jpg]

Print this item

  Orange : Pi Zero plus or Pi prime?
Posted by: mrtom31 - 04-13-2019, 05:10 PM - Forum: Skywire - No Replies

Hello fellow skycoinnoisseiur,

I am fairly new to this. I want to know before buying anything. Has anyone tried with Orange Pi Zero plus by following the guide :https://skywug.net/forum/Thread-Orange-Pi-Setup-Guide
and just replacing armbian for prime with zero plus ?

Is it safer to buy orang pi prime instead? (knowing that for 8 node it will be way mor expensive)

Thank you for reply,
mrtom

Print this item