Topic: [ANN] Spondoolies-Tech - carrier grade, data center ready mining rigs - page 325. (Read 1260290 times)

Hopefully it will pick up the not hashing board this way without any other changes.

As for wget, sorry I was trying to simplify the instructions. You need to copy it across some other way, like with winscp on windows or scp on linux.

Can be, the watchdog limits and tasks (including restart) are not defined in CGminer settings. I'd not overdo the restart though. It's restarting _very_ often already.

Funny thing just noted on my sp30.. wget is not found anywhere on the filesystem. Even the newer firmware gets downloaded using curl (/usr/local/bin/download.sh)

LATER EDIT : When I tried to download cgminer using a browser, it automatically saves it with a txt extension, so I'm pretty sure the browser does not treat the file without extension as an application/octet-stream .. maybe it works. To be sure, I've downloaded  http://nebm.ist.utl.pt/~glopes/wget/ .. dumped it on my desktop .. and run it with the target. Even this grabbed the file as [text/plain] with a length of 264284 bytes (258k).

Then, the actual cgminer binary is not located in /usr/bin, but in /etc/bin .. you might want to update your paths in the steps given by ckolivas. It looks HUGE in comparison 2150KiB existing, versus 258KiB downloaded. Something is not right ..


After renaming the existing cgminer and copying the new one in the same location the new one did not start ..



.. reverting back to old one .. and I'm hashing again.

Same issue - I've no shipment schedule yet.

Anyone know when the October Batch 1 - SP31s will be shipping?   I have not got notification as of yet.


Thanks

If this gets incorporated in the firmware does this mean that the miner will auto restart when only one board is hashing?

Understood. Thanks for looking into it. If the switchpool|N will also change eventually the pool ID , I can issue an API command to rewrite/update the CFG file explicitly.
I guess I can modify the CFG file directly using a PHP script ..  was trying to avoid that though.

That would completely change the semantics of cgminer which has never written to/modified the config file without being expressly asked to. Sorry, no.

ckolivas: in short, yes ..

The cgminer api is used to add the pools in cgminer on the SP30, so we already use the API to modify the configuration when we define the pools. Presently the switchpool|N (*) API command (when called) changes only the pool priority. Can it change also the pool ID and update the cfg file accordingly?

Ex: There is no reply section just the STATUS section stating the results of switching pool N to the highest priority (the pool is also enabled) The Msg includes the pool URL.

If all three ASICs in a loop are set to "Removed", then minergate will not attempt to initialize the DC2DC converters on that loop. Occasionally, there will be problems in that initialization process that can cause startup of minergate to fail if they're set to Disabled and not Removed. We've got a couple machines here that are that way. Usually Disabled is enough, though. Only use Removed if you're marking all three ASICs as Removed, as marking a single asic Removed instead of Disabled may cause issues, I think.

If you have a machine that shows problems within 5 minutes, then you don't need to test for 40 each time. A common problem results in the vlt1 values for all ASICs decreasing over time instead of increasing if one bad ASIC is enabled. You can often see if that's happening within 45 seconds.

You want cgminer to automatically save changes done on the fly to the pool configuration itself?...

ckolivas: Besides the low average hash rates being reported by CGminer 2.6.0 on the SP30 (about 1Gh/s), there is/was an issue with the pools switch .. i.e. when "promoting" a pool via CGminer API, the ID of the pool should change too, together with the priority. I'm not sure if that's fixed now (i've seen some posts on the cgminer thread), however, with respect to the watchdog on the SP30, if the pool ID does not change when promoted, the CGminer gets restarted with the initial configuration mining on the 1st defined pool in the config file (ID 0). This whole setup renders the "promote pool" functionality unusable on the SP30. As a matter of fact, the code to change the pools is coded into the units but presently commented out. I have no issues with the watchdog restart, but CGminer should mine on the newly promoted pool after it happens.

You are correct, the /usr/bin is not persistent after reboot. However, the cgminer runs from /etc/bin which looks to be persistent !!!

Binary built from the latest git cgminer for the sp30 for testing:

http://ck.kolivas.org/apps/cgminer/sp30/141016/cgminer

There are some minor changes to improve CPU usage which should help when you first connect to pools that start from a low diff, and if you're reading the hashrate from the cgminer API, it's now share based instead of work based. The web interface will NOT display anything differently since it doesn't display hashrate by the cgminer API (yet?). This might help you pick up when one board stops producing shares, and you're only submitting half the hashrate, but the web interface still shows everything normal.

ssh into your machine and copy the file into /etc/bin to replace the existing binary to try it and chmod +x to make it executable.

I believe the storage space there isn't permanent so if you reboot it will restore the old binary, but just in case, backup your old one.

EDIT: Instructions for copying to it assumed you had wget which it doesn't. Use something like scp or rsync on linux or winscp on windows to overwrite the old binary. Then kill cgminer via the command line. (The watchdog will automatically restart cgminer for you)

Assuming all goes well and the spondoolies team like the changes, they should be incorporated into new firmware, and ideally the web interface will be changed to use the API's hashrate meter too.

I have read that you don't use the Removed option. Only if the physical chip has been extracted. Use Disable!

ah!! i just started doing this, i c i am on the right track. but I've only just Disabled the asic, not set to Removed. Is it necessary to set to Removed (for the whole loop)? and is only a few min.s enough to test each loop? i've been testing each for ~40mins.

Cheers,
QG

You would need to pay VAT then  

The shipping rates are very fair in my opinion, FedEx shipping from Israel to US takes only around 48hours, and for 300$ on a 19kg package, it is provided at cost.

Nobody makes money on shipping nowadays.

The only posts I removed (total of about 3 posts) are completely off topic posts, usually political in nature. This is done only after fair warning.
I do report to moderators some other extremely trolling posts, but I don't remove them. The moderators may, but usually don't.

Guy

Please contact support@ on Sunday (after our last holiday weekend). Set remote ssh and https access in advance. Remo will take a look.

Yet rarely actually moderated.

One of the few that doesn't remove customers complaints.

Given the spam that often occurs in these forums it is really mandatory for fabricators to set up a moderated thread.

It is not an indicator of a scam or trying to bend the discussion away from problems in this thread.

Can you tell me why this is self moderated?

has anyone had problems where the miners just seem to shut down in the graphs and then become erratic and then seem to recover but only to about 3,200 GH/s until you reboot them?   We have about 12 that are real pains in the butt whereas the majority are very stable (or have become stable over the last couple weeks after changing settings.   
Also, we are running 208V so we are setting at 1300 / 1300 as we were told but notice that the many have 1330 /1330 even though we have set them back to 1300 /1300.

have also noticed some variability in power draw (two to a breaker (208V 30 AMP)) trips every now and then on some machines.  (208V 30 AMP plugs are cutting it close but 6kW / 7.2kW leaves enough not to trip usually).   I expected we would be lower than this since we set the max's at 1300 / 1300.

In general would have to say I am again impressed in the equipment though.   Just like the SP10s, get them stable and forget about them.   Kind of like where the Jupiters got to after months of tweaking (painful tweaking and painful RMAs for bad boards and melted plugs)....     Definitely blow away the cointerras.