![]() ![]() You can adjust the clock frequency, provided you have a fan. Stratum from pool 0 requested work restart Found Zeus at /dev/cu.SLAB_USBtoUART20, mark as 0 ![]() SB management ool management ettings isplay options uitĠ: ZUS cu.SLAB_USBt: 1 chips 144 MHz | 98.30K / 98.29Kh/s WU: 0.0/mġ: ZUS cu.SLAB_USBt: 1 chips 144 MHz | 106.2K / 103.2Kh/s WU:110.0/m cgminer -scrypt -zeus-chips 1 -zeus-clock 144 -zeus-nocheck-golden -url stratum+tcp://us.:3333 -user user -pass pass -S /dev/cu.SLAB_USBtoUART -S /dev/cu.SLAB_USBtoUART20Ĭgminer version 4.3.5-scrypt.2 - Started: Make sure the switch is in the proper position on each USB stick (switches to the right) I tried both the tty.SLAB_USB* and cu.SLAB_USB* devices, only the cu.SLAB_USB* seem to work. I don't know if you already solved this, but I got 2 of the 144KH/S-280KH/S USB LiteCoin miners running on my Mac - El Capitan by doing the following:ĭownload, build and install dmaxl/cgminer: ssh into your raspberry pi Pull down any updates to any packages you have currently installed, sudo apt-get update Install the updates you just downloaded. You can get a list of devices that are plugged in with lsusb. When you plug it in, it should create the device /dev/ttyUSB1, and a device under /media or /mnt. $ sudo apt-get install build-essential libtool autotools-dev autoconf git Possible fixĪll instructions are intended for Debian/Ubuntu/Raspbian. (I think it is, based on the screenshots on that page.) The latter is usually distributed with your mining program of choice. The former is distributed with Raspbian, assuming the bridge is a Silicon Labs CP210x. You need a driver for the USB-to-UART bridge, and a driver for the ASIC. Also, some of the reviews on that item say that they've had luck on linux with a fork of cgminer with ZeusMiner support. Another thing on the todo list for this, is to have cgminer run inside a container, and then on K8S.I think these might be rebranded ZeusMiner ASICs - LKETC doesn't appear to sell any scrypt miners below the 1MH/s range. To get this a bit more stable, I likely need to relocate the “cluster” to my server cabinet for better cooling, the little USB keys get painfully hot. ![]() This is then installed, sort of like this:Ĭgminer version 4.10.0 - Started: 67-95: Sets up cgminer to start on boot.41-59: Runs both the prebuild setup and then compiles cgminer.31-39: Downloads the patched cgminer source with 2PAC support.19-29: Create, and then ensure directories exist for the source and build.12-17: Use apt to install prerequisite packages (build-essential, and so on). ![]() To ensure I can do this again at some point, I wrote an Ansible playbook to do the heavy lifting for me:įor those not familiar with Ansible, here’s what it is doing: Installing cgminerįor these particular ASICs, one needs to first compile cgminer with the appropriate support. These are still configured as they were in my OpenFaaS post. I’m not sure if my affiliate account is still active, but if so, this is full disclosure that they may indeed be affiliate links. The Gearįor this project, I reused my Kubernetes / OpenFaaS cluster, and added some ASICs. The conclusion of which will be to run the miners inside containers backed by Kubernetes. Rather this is a “because I can” project. In that vein, I bring you ASIC Bitcoin mining on Raspberry Pi.Īs you read, keep in mind, that the goal here, like in the afore mentioned posts is not to be practical. Not the least of which is OpenStack Swift on USB Keys, or the pre-chaos engineering random VM snapshot deleter. I’ve had some pretty terribad ideas in the past. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |