Topic: LightningAsic Gridseed Controller Firmware V3 - page 23. (Read 51149 times)

I just changed the worker name field to only one worker and am now getting a response.

Isn't it still possible to define each unit as its own worker?

Didn't help. I switched to a standard pool from my P2Pool and it I'm getting no shares submitted.

Already done that 3x :/

Power on, 2x short blue light (1 ½ sec, and one 1 sec) then it just dies out, no light.

Try power cycling your controller.

hmm.. just uploaded LAG3355_upgrade_v1.bin to my controller. now it just flashes blue once when powered on, and then nothing more?

It may be picky with pools, so please try a different pool.


The DHCP may have assigned a different IP address.

I'm having trouble accessing the ip address from the web browser. It keeps trying to load but I get nothing. This has been the case since my two miners were fried. It looks like whatever happened blew the USB-to-TTL board in each of the miners. Is there a way to reset the TP-link or is probably dead?

Edit: Paperclip in the reset button worked. Still not sure about the stability on these. Anyone else try a non-powered usb with better results?


Now, I get the following message when I try to load the V1 bin.  V2 bin is rejected as unknown file.



Edit: Okay, it turns out these bin files are a one time use. You have re-download the file for each controller that you need to flash.

After updating, still staying with 850Mhz, I'm getting 100% rejects. Even backing down to 700Mhz, still all rejects, no accepted shares via P2Pool.

That will not happen any time soon.  Good luck hacking the bin, it's well protected.

If nothing is flashed to the actual gridseed units, how do these perform faster? Is it just a case of previously not being able to up the frequency on the old controller firmware? I'm using a Winblows PC atm, will be switching to the Pi soon.

Ok. Upgraded now from v1 to v3.

After loading the upgrade from v1 file and the controller rebooting, I got an error "MD5 is not correct" or something like it when trying to upload the RC10 file. I tried it a few more times and it worked.

Looking good right now, setting it up and starting the miners.

Going to let it run for a while before starting to up the frequency per miner.

I'm upgrading now.

I had trouble with the upload not really doing anything. Disabled the miners and it worked very quickly.

So a tip for anyone planing to upgrade, stop the miners by disabling them before proceeding.

Quick, someone port this over to rPi!

Wicked stuff - Thanks for the effort sandor - will test it in an hour

THE FASTEST HASHING AND MOST STABLE GRIDSEED MINER SOFTWARE
WORKS WITH WIIBOX


Required:

• ONE OF: Tp-link 703N, Wiibox or LightningAsic controller

Features:
FIXED ISSUE WITH 100% REJECTS

• Auto Overclocking
• Up to 128 miners per controller, however due to memory limitations 50 is the max for 32MB RAM
• Backup pools
• Individual Gridseed miner frequency setting
• Custom miner software, frequency selectable up to 1200 MHz and multithreaded
• Stripped, custom compiled OpenWrt (controller's OS) image optimized for size and speed
• Stability is heavily emphasized and guaranteed! No more random reboots or crashes
• Advanced miner monitoring and management
• Auto power cycle miners when one of the miners is stuck, this is done software wise and it has the same effect as unplugging, and plugging in the USB cable! (see note#1)
• Miner logs

Downloads:
New (22/04): https://www.dropbox.com/s/5btgj4dqzm8zc34/LAG3355_12-RC10g.bin
https://www.dropbox.com/s/u4qg3t5v7g9blnv/LAG3355_upgrade_v1.bin
https://www.dropbox.com/s/2xvzhdnxacsziqs/LAG3355_upgrade_v2.bin

Installation:
DO NOT PROCEED IF YOU DON'T HAVE A TP-LINK 703N OR WIIBOX CONTROLLER, AS THIS WILL BRICK YOUR CONTROLLER.
DO THIS AT YOUR OWN RISK - I AM NOT RESPONSIBLE IF YOU BRICK YOUR CONTROLLER.
Tp-link 703N/Wiibox Controller
For flashing Chinese Tp-link 703N, upload LAG3355_upgrade_v1.bin; see http://www.siongboon.com/projects/2013-10-06_tl-wr703n_setup/image/flashing%20new%20firmware.png
1. Login to SSH (Password for Wiibox controller: 2.02 or lower "123456" - 2.0.3 or higher "+xTjPR4L%V?=s4-!Ahz3~FXZM^sW:gA_")
2. Upload LAG3355_upgrade_v1.bin to the /tmp directory (on Windows use WinSCP)
3. In SSH enter: "mtd -r write /tmp/LAG3355_upgrade_v1.bin firmware"
4. Wait until it has rebooted
5. See step 5 below
LightningAsic Controller
1. Determine your firmware version, if it is v1 download the v1 upgrade bin (LAG3355_upgrade_v1.bin), v2 and above download the v2 upgrade bin (LAG3355_upgrade_v2.bin)
2. Proceed to the firmware upgrade page on your controller, this is http://your-controller-ip/update.php
3. Browse for either LAG3355_upgrade_v1.bin or LAG3355_upgrade_v2.bin (see step 1) and click on the update button to start updating
4. Wait until the page has stopped loading, if it doesn't automatically reboot you will need to power cycle your controller
5. If all is well you should be presented with another upgrade page at http://your-controller-ip, this is to upload the actual firmware.
6. Browse for LAG3355_12-RC10c.bin and click the update button to start updating
7. See step 4
8. Voila! Enter your pool settings (specify 1 worker only), specify frequency and click on save and you are good to go!

Notes
1. Auto power cycle option will only work if you have connected your controller to an unpowered USB hub.
2. Charts are a bit buggy sometimes, it is recommended to turn it off if you are running with 20 or more miners.
3. Some pools may not play nice with the miner software, then please choose a different pool, such as Ghash.io.

Troubleshooting
To avoid any issues it's best that you are doing the updating process from Chrome and on a Windows 7 PC. Avoid Mac.
Most of the times a cold reboot is required after flashing.
Don't rename any of the bin files, or it will fail to update.
If you can't reach the miners, the DHCP may have assigned a different IP, so please check with your router.
If you still can't find the IP, power cycle the controller and that should fix it.
"Failed to unpack" : try the other upgrade bin
"Image check 'platform_check_image' failed" : try the v1 bin image
"MD5 differs" : corrupted bin or clear your browser cache
Rejected shares? Make sure that you have filled in a single worker, or try a different pool, it may be picky.

Donations
1AMsjqzXQpRunxUmtn3xzQ5cMdhV7fmet2
DFZ3rxAUgFspMfpZbqMzgRFFQKiT695HCo
Lc75scqhMCkpMhC3aYGPVB4BEAzHvvz2rm

That is all.