--hexminer8-set-diff-to-one 1 --hexminer8-chip-mask 255 --hexminer8-voltage 955 --hexminer8-options 8:240 One by one --hexminer8-set-diff-to-one 1/0 the diff when set to 1 like mine - am testing it now brings a lot pressure between UB-HOST and PIC/ASIC communication Coin crafts can filter their response based on difficulty configured. When you set to one you got all nonces match diff 1 which has to be filtered and not send to the pool amusing you mine at diff greater than one. The only real advantage setting it to one is the cgminer 5 secs stats not moving up/down like crazy and average stats are settling down more quickly. Assume that you mine at diff 128. Cgminer sets it individually for each work passed to asic so it stays in sync with your pool always. Even if it is 1! When you set it to zero - ASIC send to the pic only nonces matching the diff 128 and back to host so you have about 128 times less data transfer, and cgminer shorts the time for submitting the nonce not checking against pool diff if it is a HW and all nasty stuff inside. the only disadvantage is that each nonce is counted not as one like before but as work difficulty itself which causes the stats variation. I suggest to use --hexminer8-set-diff-to-one 0 and configure your worker to mine at some constant higher difficulty. for instance when btcguild changes difficulty some old work may become stale oldddiff even though it is valid. In general if you happen to be in between two pools difficulties and your pool changing it up and down frequently you can have higher pool reject ratio - not good --hexminer8-chip-mask 255 - this was for development you can enable/disable chips based on binary mask bin 11111111 - 255 dec all chips enabled. Obviously zero is not a good choice here --hexminer8-voltage 955 the core voltage in milivolts. Do not go above one volt 1000 or do it on your risk --hexminer8-options 8:240 8 is chip count - used for some internal usb timing calculations , 240 is the frequency. The actual chip frequency is multiplied by four so 240 means 880 actually. the maximum value as far as know is 275. But try to stay below 260 in general And finally use --quiet when you have seen enough of course
|
|
|
This is what happens. On some boards more offend then others:
001: HEX8 1: 260 1000/ 998mV | 10.62G/282.0Gh/s | A:158720 R:1034/0.65% HW:0/0.00% WU: 3.8/m
Sometimes it goes down to less then 1Gh...
There is a variation on hashrate but i never see 10 GH/s.
|
|
|
Do boards stop mining from time to time? And then start again... First I thought it is because of too many boards on one router but it happens with only 2 on it too. Is there a setting I can change or something?
No, that should not happen. I only had one board so i am not sure what is the cause.
|
|
|
Is that it? Mem: 16400K used, 12956K free, 0K shrd, 1724K buff, 4620K cached CPU: 34% usr 26% sys 4% nic 33% idle 0% io 0% irq 0% sirq Load average: 2.65 2.22 2.09 8/65 2079 PID PPID USER STAT VSZ %VSZ %CPU COMMAND 760 752 root S 75220 256% 65% /usr/bin/cgminer --hexmineru-frequenc
Indeed
|
|
|
Can u please write me a "top" result with these miners?!
By top you mean what? Best share? Total hashrate? Best hashrate? iFA88 mean top command. He want to see your CPU & memory usage
|
|
|
Zich, There are more sample chips for sale on that website. I just bought 16 of them.
Nice, thanks for the information
|
|
|
Can someone help me figure out what I'm I doing wrong. Set router password Set router timezone Set router time Reboot Setup pools SSH on router screen -r and I see this ntpd: resolved peer 3.openwrt.pool.ntp.org to 89.212.75.6 ntpd: sent query to 89.212.75.6 ntpd: resolved peer 2.openwrt.pool.ntp.org to 193.95.228.232 ntpd: sent query to 193.95.228.232 ntpd: resolved peer 1.openwrt.pool.ntp.org to 193.2.78.2 ntpd: sent query to 193.2.78.2 ntpd: resolved peer 0.openwrt.pool.ntp.org to 89.212.160.254 ntpd: sent query to 89.212.160.254 ntpd: reply from 89.212.75.6: reach 0x01 offset -6.394512 delay 15.235440 status 0x24 strat 2 refid 0xc1020175 rootdelay 0.006912 ntpd: reply from 193.95.228.232: reach 0x01 offset -3.555069 delay 10.418542 status 0x24 strat 2 refid 0xc1020175 rootdelay 0.005386 ntpd: reply from 193.2.78.2: reach 0x01 offset -1.131939 delay 4.735346 status 0x24 strat 2 refid 0xc1020175 rootdelay 0.000458 Alarm clock
DNS problem. Need to restart modem or router.
|
|
|
With 200/900 speed/voltage, after 8.7 hours, 11635 nonces @ 128 difficulty, 204.2GH/s average speed, zero hardware errors
Restarting with 210/900
@900mV you can go upto 240 freq on some boards after 10.5 hours at 210/900 (38112 seconds) 14986 nonces @ 128 difficulty 6 hardware errors 216.169 GH/s And my other WR-703N is playing silly buggers and not starting cgminer by itself, having to resort to putty. Admittedly that specific WR-703N and release 0.1.0 on it which I upgraded to 0.2.0 with the factory bin file, and kept the settings.... That was really nice result, my board can not run stable like that.
|
|
|
You miss git checkout command. 1. sudo aptitude update 2. sudo aptitude upgrade 3. sudo aptitude install libudev-dev libusb-1.0-0-dev libfox-1.6-dev 4. sudo aptitude install autotools-dev autoconf automake 5. sudo aptitude install libtool libncurses-dev yasm 6. sudo aptitude install curl libcurl4-openssl-dev libjansson-dev screen 7. sudo aptitude install pkg-config uthash-dev make git-core
Then download cgminer 4.0.0 1. git clone https://github.com/ckolivas/cgminer.git 2. mv cgminer cgminer-4.0.0 3. cd cgminer-4.0.0 4. git checkout 2786526d9f1acb7bd903ece3c822c2c9203aa0b7 5. wget https://www.dropbox.com/s/tyerzzpc1xjqegj/2786526d9f1acb7bd903ece3c822c2c9203aa0b7.patch 6. patch -p1 < 2786526d9f1acb7bd903ece3c822c2c9203aa0b7.patch 7. ./autogen.sh --enable-hexminera --enable-hexminerc --enable-hexminerb --enable-hexmineru --enable-hexminer8 8. make
Step 5 is patch uploaded to dropbox by myself, so you can use your own that downloaded from technobit download page if you want Make sure there is no error message on each step. No need to install, you can run cgminer from folder. 1. screen 2. sudo ./cgminer --hexminerc-voltage 1100 --hexminerc-options 16:1500 --hexminer8-set-diff-to-one 0 --hexminer8-chip-mask 255 --hexminer8-voltage 1005 --hexminer8-options 8:260 --set_default_to_8
Or add the setting to cgminer.conf so you don't have to type setting command each time sudo nano /root/.cgminer/cgminer.conf
{ "pools" : [ { "url" : "stratum+tcp://stratum-lb-usa48.btcguild.com:3333", "user" : "user", "pass" : "123" } ] , "api-mcast-port" : "4028", "api-port" : "4028", "expiry" : "120", "hotplug" : "5", "log" : "5", "no-pool-disable" : true, "queue" : "1", "scan-time" : "60", "shares" : "0", "hexminera-voltage" : "1460", "hexminera-options" : "16:480", "hexminerc-voltage" : "1100", "hexminerc-options" : "16:1500", "hexminerb-voltage" : "900", "hexminerb-options" : "16:540", "hexminer8-set-diff-to-one" : "0", "hexminer8-chip-mask" : "255", "hexminer8-voltage" : "1005", "hexminer8-options" : "8:260", "hexmineru-frequency" : "54", "kernel-path" : "/usr/local/bin" }
|
|
|
Urgent help needed I´ve upgraded my router with last image and now i get this error in SSH: ntpd: bad address '3.openwrt.pool.ntp.org' ntpd: could not resolve peer 3.openwrt.pool.ntp.org, skipping ntpd: bad address '2.openwrt.pool.ntp.org' ntpd: could not resolve peer 2.openwrt.pool.ntp.org, skipping ntpd: bad address '1.openwrt.pool.ntp.org' ntpd: could not resolve peer 1.openwrt.pool.ntp.org, skipping ntpd: bad address '0.openwrt.pool.ntp.org' ntpd: could not resolve peer 0.openwrt.pool.ntp.org, skipping Alarm clock ntpd: bad address '3.openwrt.pool.ntp.org' ntpd: could not resolve peer 3.openwrt.pool.ntp.org, skipping ntpd: bad address '2.openwrt.pool.ntp.org' ntpd: could not resolve peer 2.openwrt.pool.ntp.org, skipping ntpd: bad address '1.openwrt.pool.ntp.org' ntpd: could not resolve peer 1.openwrt.pool.ntp.org, skipping ntpd: bad address '0.openwrt.pool.ntp.org' ntpd: could not resolve peer 0.openwrt.pool.ntp.org, skipping Cgminer won´t start Ip mask gw and DNS check them I have the same problem but I can not solve it. could you tell me what to do? thanks As loshia said, this cause by DNS. You need to reset your modem & or router.
|
|
|
Bummer, the Antminer has a pretty sweet little tab there which is why I thought i was missing something.
Thank you for this guide, previously I had only been able to run these with an RPi, which I can now free up for other projects (Like the new Gridseeds)
You are welcome
|
|
|
Yeah working fine now... thanks. I seem to be missing the cgminer status menu that OP had in his photos, and I do have on my Ant S1. Was that something you added or did I piss off the OpenWRT Gods this week Ahh sorry about cgminer status on the screenshot Officially that's was unavailable, i just trying to play with code. The page appear but not working, all the value not available
|
|
|
I've installed screen to use with this so I can ssh in and see the familiar CLI for cgminer, does anyone have an idea of how to configure OpenWrt so that cgminer boots with a reattachable screen?
As Gator said, screen already installed, cgminer even already configured to run under screen. I am not sure what exactly happen on yours. Ofc wrong command will kill the screen. After login to TL-MR3020, you can use command screen -r to enter cgminer cli. To exit type ctrl-a + d. To check how many screen currently available use command screen -ls
|
|
|
Nice, thanks marto
|
|
|
well done! all is up and running and i truly will say the easiest setup ive had for a long time.
thanks for your help.
You are welcome
|
|
|
actualy already made this but with some other changes in components
Is there anywhere else on the board we can solder these legs to Marto? When they come off they take the circuit board contract with them so they cannot be soldered back to their original place. Zich's solution of soldering to the nearest good leg wont work for someone with Eestimee's problem where all the poly-fuses have a bad left leg. Maybe if you fix Eestimee's board you can take a photo to show us what you did? Thanks. Agree, i would love to see the via I already try measure with connectivity but not found any near smd capacitor.
|
|
|
I got my HEX8A1 to operate this morning, but it was an adventure:
* Tried OZC 550w PSU yesterday, default settings: 260 clock,1000mV => Miner started hashing but as soon as I checked hashrate in terminal (next room) I saw it already disabled itself. Went back to the PSU, HEX8A1 is off. PSU is dead. * Next try: El cheapo CP 750 Plus PSU. The label says 2*12V rails with 30A each = 720W. I used only the 2 PCI-e power cords, no other load. I tried default settings again. Miner hashes, with very high hashrate (way over 260GHs) but after 20 minutes, PSU switched off. PSU in failsafe mode. * Couple of additional tries ending with PSU switching off. * Here is what finally worked (stable for a few hours now): 255 clock, 980mV. Results in fairly stable 260.5GHs. I didn't measure the actual power draw at the wall yet, but I am scared already.
Why did you test your board with try & error method? The PSU clearly had specification about 12V rail, how many rail & what is maximum amp per rail. I already post the HEX8 consumption on 260/1000 setting, it's 33 A on 12V rail. You said "El cheapo CP 750 Plus PSU. The label says 2*12V rails with 30A=720W", clearly you see the 720W not the limit 30A per rail. About OCZ 550W, i don't know which type you use. OCZ Fatal1ty 550W is 2 rail, max 25 A per rail which clearly will overload OCZ ZS 550W is single rail, max 38 A & OCZ ZT 550W is single rail, max 45 A should do the job
|
|
|
on step 5 the patch I am getting error 404 not found
I guess you type it line by line. You can just copy it then paste it on ssh using right click.
|
|
|
powered usb for what? If you had many HEX board
|
|
|
|