Updating the system bios
This can be set in the Antimalware Policies in SCCM.This update method should be set as first or only update mechanism for SCEP.Getting Support Quick Start Guide Editing Config with Nano Editing Token with Nano Common Commands on eth OS Video Guides Mining Zcash Mining Monero Updating eth OS to the Latest Version Updating Miners to Latest Versions Installing Fixes on the Latest eth OS Version Writing eth OS to an 8gb USB 3.0 / HDD / SSD on Windows Writing eth OS to an 8gb USB 3.0 / HDD / SSD on Linux (debian/ubuntu flavors) Writing eth OS to an 8gb USB 3.0 / HDD / SSD or SSD on OS X Booting a Rig without a Power Button Initial Setup (using a Keyboard and Monitor on eth OS) Booting into eth OS Provisioning AMD boards Provisioning Intel boards Properly distributing riser power to avoid instability Fixing Kernel Panic with 5 GPUs on Intel Z170/X/270/X/H110 Fixing 290/390/470/480 boot problems with Intel boards Fixing ADL Error / Hardware Error Robust Troubleshooting Guide for Motherboards and other Rig Components Using SSH to Login to eth OS from Windows Forcing eth OS to keep changes after Reboots Setting and Switching your Wallet and/or Pool Changing or removing your Worker Name Using a Pool that Requires Workers, Usernames, and Passwords (suprnova) Setting up your own Remote Config Using Config for your Remote Config Setting up a Digital Ocean Droplet for your Remote Server Setting a Static Internal IP for your eth OS Rig Overclocking Managing Temperature Setting a custom Panel ID Fixing Unexpected low Pool Hashrate Autotrading Altcoins for Bitcoin Mining and Common Issues Using Team VIewer in eth OS eth OS Command list and Common Answers: ♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦ Remote/Local Confs /home/ethos//home/ethos/Documentation / Sample Conf ethosdistro.com/kb ethosdistro.com/helpme: show the list of common commands allow/disallow: allow OR disallow miner (automatic start) minestop: turn off all miner instances show: show output of various log files ww: show the eth OS desktop text in your terminal dmesg: show display messages and driver messages r/hard-reboot: issue a regular OR hard reboot gethelp: generate a diagnostics file for getting support df | pasteit: send output of command (ex: df) to paste server clear-thermals: reset thermal-related throttling back to normal force-local: disable remote config reset-config: reset remote/local configuration back to default reset-network: reset network configuration back to default update: send stats to stats panel putconf: manually put remote conf into local conf browser: launch web browser on local rig lock: lock the eth OS desktop ethos-overclock: force overclocks to apply from local conf ethos-update: update eth OS to the latest version restart-proxy: restart local stratum proxy ethos-driver on/off: turn on/off graphics driver for the next boot ethoschat: help chat (in current terminal session) ethoschat-local: help chat (on rig, in separate window) find-gpu: example: find-gpu 1 (revs gpu1 fan up/down) sudo atiflash: flashing utility for AMD GPUs lga1151-flasher: see ethosdistro.com/M update-miner(s): updates all miner programs to latest versions ♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦♦ If fewer GPUs show up here than are connected to your rig, check all connections and reboot, If some GPUs are still missing, it is a hardware, riser, or motherboard bios problem, not a software problem. If the issue is not resolved, reimage the drive from the eth OS download link to your current drive, or a spare drive.If your rig fails to boot due to "Kernel Panic", reseat and test all RAM.Make sure that your rig detects at least 4gb of RAM.If the issue persists, continue with the below guides: Example: You suspect that your motherboard is faulty.Please use the pool-side effective hashrate to see your true hashrate for the entire rig.Because we had serious problems with SCEP, which uses the Windows Update Service, we were advised to enable updates through an UNC path.
If and when the error occurs in an environment is unpredictable and highly dependend on the WSUS maintenance, the number of updates to scan, installed products on a system (less products = less updates).
This way, all rigs on one network can report to the same panel.
If your public IP changes, your panel ID will change.
This robust troubleshooting procedure is useful because it isolates the issue to your suspect component.
Otherwise, the issue could be a power balance issue, riser problem, loose cabling, bad power socket, bad PSU, etc.
INSTEAD, SWAP YOUR SUSPECT MOTHERBOARD INTO ANOTHER WORKING RIG!