Latest posts of: Chamaelion

Bitcoin Forum

June 26, 2024, 07:34:28 AM

Welcome, Guest. Please login or register.

News: Latest Bitcoin Core release: 27.0 [Torrent]

Home

Help

Search

Login

Register

More

Show Posts
Pages: [1]

1

Alternate cryptocurrencies / Mining (Altcoins) / Re: [MinerEU.com]Scrypta controller for 28nm Innosilicon A2 Miners

on: June 11, 2014, 02:40:42 AM

Quote from: minereu.com on June 10, 2014, 06:40:19 PM Quote from: Chamaelion on June 10, 2014, 01:53:18 PM OK - have an A2MINI, and everything runs fine with the innosilicon supplied SD card. Swapped out for a known working alternate card with a fresh install of wheezy & ran root bash to install MinerEU Scrypta A2 image. Seemed to install no problem. After reboot, webpage accessible without any errors & fully functional, although miner not starting. SSH'd in and attempted to run cgminer manually, miner would not start & received following error: "No any a1 board" Am downloading the SD image & will try again with this, but not hopeful. Please advise. humm, this is interesting. which image were you using ? or it is the SD card comes with the miner? I've left the original SD card provided with the miner untouched, so I can go back to it if need be - it's currently in the A2 right now, which is hashing away happily. I used another relatively new SD card which was running in a PI looking after some gridseeds until recently. I formatted it, did a fresh install of wheezy, and then ran your install script - no errors reported on install. I then rebooted the PI (sudo reboot, not a power cycle), the Scrypta webpage came up no problems, but cgminer not starting (error described above when attempted to run manually). Please assist / advise...

2

Alternate cryptocurrencies / Mining (Altcoins) / Re: [MinerEU.com]Scrypta controller for 28nm Innosilicon A2 Miners

on: June 10, 2014, 01:53:18 PM

OK - have an A2MINI, and everything runs fine with the innosilicon supplied SD card. Swapped out for a known working alternate card with a fresh install of wheezy & ran root bash to install MinerEU Scrypta A2 image. Seemed to install no problem. After reboot, webpage accessible without any errors & fully functional, although miner not starting. SSH'd in and attempted to run cgminer manually, miner would not start & received following error: "No any a1 board" Am downloading the SD image & will try again with this, but not hopeful. Please advise.

3

Alternate cryptocurrencies / Mining (Altcoins) / Re: [Minera] New web management system for Gridseed devices

on: May 14, 2014, 07:59:32 AM

Quote from: michelem on May 13, 2014, 10:59:52 PM Just added a "save current frequency" button. Commit/push tomorrow Mate, you're an artist - love your work & can't wait to see this functionality in your next push If you ever find yourself down under, the first round's on me!

4

Alternate cryptocurrencies / Mining (Altcoins) / Re: [Minera] New web management system for Gridseed devices

on: May 14, 2014, 07:49:34 AM

Quote from: Chamaelion on May 11, 2014, 01:19:28 PM Quote from: michelem on May 11, 2014, 08:06:17 AM Quote from: Chamaelion on May 11, 2014, 05:47:41 AM Hey mate - love your work, Minera is a great piece of code:) Lovely smooth interface, and I'm running P2Pool on my own local node - it's giving me the best hashrate I've seen to date. Problems with 1.0.6 though - after I upgraded this morning, my rig had it's hashrate at the pool cut by half... Not sure what you've changed that could affect the hashrate like that, but I've reverted to 0.1.5 (commit 691c659) 'til you've got it sorted out. After reverting, my hashrate's back up to what it was before the upgrade, and I've made no other changes to the gridseeds, pi, node, or infrastructure. This could be related to the new cpuminer release but it's weird, did you try to restart the minerd command? Can you show me your command line string? You should find it on settings page. Thanks OK - the rig I've got is using 2 pi's running 13 gs each, and they both demonstrated the same halved poolside hashrates once they were upgraded to to 0.1.6. This was after restarting minerd, rebooting, or even flashing the SD and rebuilding everything again from scratch & pulling straight to 0.1.6. And yes, I did give them several hours to see if the poolside hashrate would climb - no dice After rolling back to 0.1.5 and a reboot, both pi's were back to their old hashrates at the pool within 15-20 minutes... Here's the 0.1.5 command lines: --gc3355-detect --gc3355-autotune --freq=850 -o stratum+tcp://10.0.0.1:9327 -u Castor -p x --retries=1 --gc3355-detect --gc3355-autotune --freq=850 -o stratum+tcp://10.0.0.1:9327 -u Pollux -p x --retries=1 And here's what I was using for 0.1.6 (built using the "guided" option & adding "--retries=1" in the extra variables area - I didn't decide to arrange it this way): --gc3355-detect --gc3355-autotune --freq=850 --retries=1 -o stratum+tcp://10.0.0.1:9327 -u Castor -p x --gc3355-detect --gc3355-autotune --freq=850 --retries=1 -o stratum+tcp://10.0.0.1:9327 -u Pollux -p x Let me know if you've got any ideas, or if you need anything else to help track this down. No rush on getting this one fixed either, I'm more than happy to keep going with 0.1.5 in the interim - it's got my rig performing the best it's ever been. I'll just keep checking the updates on a spare SD I've got and will bring the others back to the current version once it's up to the same performance. Thanks again for the great work! -- Suggestion -- A backup / log to hold a record of GS serial # / hashrate pairs so that after a restart / reboot the GS's can all be ramped up to the frequencies they were at prior to the reboot - this would save having to wait the 10-12 hours it takes for autotune to dial them in. Hey michelem - just wanted to say been running 0.1.7 for over 24 hours on one of the Pi's, and there are no problems at all, hashrates are up to the same levels experienced on 0.1.5. Also just upgraded it to 0.1.8 without any hassles too. Keep up the good work, LTC donation coming your way PS - let me know if you need a hand getting a Pi image set up, happy to help out if I can.

5

Alternate cryptocurrencies / Mining (Altcoins) / Re: [Minera] New web management system for Gridseed devices

on: May 11, 2014, 01:19:28 PM

Quote from: michelem on May 11, 2014, 08:06:17 AM Quote from: Chamaelion on May 11, 2014, 05:47:41 AM Hey mate - love your work, Minera is a great piece of code:) Lovely smooth interface, and I'm running P2Pool on my own local node - it's giving me the best hashrate I've seen to date. Problems with 1.0.6 though - after I upgraded this morning, my rig had it's hashrate at the pool cut by half... Not sure what you've changed that could affect the hashrate like that, but I've reverted to 0.1.5 (commit 691c659) 'til you've got it sorted out. After reverting, my hashrate's back up to what it was before the upgrade, and I've made no other changes to the gridseeds, pi, node, or infrastructure. This could be related to the new cpuminer release but it's weird, did you try to restart the minerd command? Can you show me your command line string? You should find it on settings page. Thanks OK - the rig I've got is using 2 pi's running 13 gs each, and they both demonstrated the same halved poolside hashrates once they were upgraded to to 0.1.6. This was after restarting minerd, rebooting, or even flashing the SD and rebuilding everything again from scratch & pulling straight to 0.1.6. And yes, I did give them several hours to see if the poolside hashrate would climb - no dice After rolling back to 0.1.5 and a reboot, both pi's were back to their old hashrates at the pool within 15-20 minutes... Here's the 0.1.5 command lines: --gc3355-detect --gc3355-autotune --freq=850 -o stratum+tcp://10.0.0.1:9327 -u Castor -p x --retries=1 --gc3355-detect --gc3355-autotune --freq=850 -o stratum+tcp://10.0.0.1:9327 -u Pollux -p x --retries=1 And here's what I was using for 0.1.6 (built using the "guided" option & adding "--retries=1" in the extra variables area - I didn't decide to arrange it this way): --gc3355-detect --gc3355-autotune --freq=850 --retries=1 -o stratum+tcp://10.0.0.1:9327 -u Castor -p x --gc3355-detect --gc3355-autotune --freq=850 --retries=1 -o stratum+tcp://10.0.0.1:9327 -u Pollux -p x Let me know if you've got any ideas, or if you need anything else to help track this down. No rush on getting this one fixed either, I'm more than happy to keep going with 0.1.5 in the interim - it's got my rig performing the best it's ever been. I'll just keep checking the updates on a spare SD I've got and will bring the others back to the current version once it's up to the same performance. Thanks again for the great work! -- Suggestion -- A backup / log to hold a record of GS serial # / hashrate pairs so that after a restart / reboot the GS's can all be ramped up to the frequencies they were at prior to the reboot - this would save having to wait the 10-12 hours it takes for autotune to dial them in.

6

Alternate cryptocurrencies / Mining (Altcoins) / Re: [Minera] New web management system for Gridseed devices

on: May 11, 2014, 05:47:41 AM

Hey mate - love your work, Minera is a great piece of code:) Lovely smooth interface, and I'm running P2Pool on my own local node - it's giving me the best hashrate I've seen to date. Problems with 1.0.6 though - after I upgraded this morning, my rig had it's hashrate at the pool cut by half... Not sure what you've changed that could affect the hashrate like that, but I've reverted to 0.1.5 (commit 691c659) 'til you've got it sorted out. After reverting, my hashrate's back up to what it was before the upgrade, and I've made no other changes to the gridseeds, pi, node, or infrastructure.

Pages: [1]

Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines