I have yet another unit that throws this error when I try to upload the initial binary.
Error: Firmware with name 'LAG3355_upgrade_v2' is not found
That's a strange one, but clearing your browser cache should fix that. |
|
|
|
List of changes with the new firmware? Works with most, if not all other pools. Confirmed that it is working for me on GHash.IO which did not work with the prior version. I was able to install with no issues. I've also fine tuned my miners individually with the highest frequency that gave off no HW errors and am now getting ~7.6MH/s with 21 miners. Thought the results might be interesting to some. 1@800 1@832 6@850 1@852 4@862 8@875 That's great to hear.  |
|
|
|
List of changes with the new firmware? Works with most, if not all other pools. Reject rate significantly lowered, effective hashrate should be increased by 10-20kh/s/miner. Memory comsumption is lower, which makes it possible to run up to 50 miners. Some other speed optimizations have been implemented. Getting a failed to unpack firmware error on the new bin.
Seems to be hardware related, some have this issue :/ |
|
|
|
After using two controllers for a day with 42 miners, I have concluded that the V3 firmware preforms worse than a raspberry pi with cgminer/bfgminer or a wiibox controller with 2.1.0 firmware OCed to 850. It is convenient to have up to 40 miners on one TP-link, but the high number of stale shares is totally unacceptable. I am going back to five wiibox controllers that can still dual mine and produce a more stable hashrate.
Edit: I have two LightningASIC controllers updated to the V3 firmware that I would happily part with if anyone needs one. Just pm me a fair price and I can ship it out. Escrow is fine of course.
Please wait for the next update, I promise that it will be better and faster. |
|
|
|
I have been able to fix all the issues aforementioned, been testing on Ghash.io and it does the job perfectly now. I have also fixed some performance issues with the miner software, it should be about 10-20 kh/s/miner faster. Also the memory consumption is further reduced, so it is possible to run more than 50 units. Waiting for Jack to respond so it can be released. Tryied to upgrade my V2 units. (HW V1.6). All I get is this error "Sysupgrade: cat: write error: Broken pipe cat: write error: Broken pipe cat: write error: Broken pipe cat: write error: Broken pipe Invalid image type. Image check 'platform_check_image' failed."
Try the v1 bin image. |
|
|
|
|
I am aware of the issues with some or all miner devices not hashing at all or 100% rejects, I've been able to reproduce the problem so look forward for another firmware update very soon.
|
|
|
|
Would be even more awesome if i could unbrick my controller without needing to tear it apart and solder stuff to it  I have 3 controllers. 2 successfully updated to v3 no problem. The last one I have the same problem as you. Blue light blinks twice then nothing - hard reset with paperclip also doesn't work EDIT: sandor111 the version is 1.6 on the back of mine for reference Exactly the same, i triede pressing the reset for 30 secs and everything even - even tried the press it and connect power at the same time (quite a challange with my phat fingers../slightly chopped motoric skills.) Mines definitely bricked - 2 blue light flashes then it dies pretty much Mail me the controller if you want it fixed, you pay for shipping + I will repair it for free. If you live outside Europe it may just be cheaper to buy a new one. |
|
|
|
Doesn't work for me. My 6MH/s suddenly turned into 0.3MH/s no matter which frequency/pool I use or how many times I restart them. I strongly recommend that people do not upgrade at this time.
Which pool? I've tried a few different pools now. It doesn't seem to be pool related. Interestingly, if I only have a couple miners plugged into each hub, it seems to work. I'm playing plugging/unplugging games right now to see how many I can get working at once. So far I can't get more than 4 working with a single controller/hub. It's obviously pool related, we had no problems testing with 40+ units. What pool works then? Seems odd that I can get full speed out of 4 units, but when I plug in 10 to the hub, I get almost 0. I would think it was power related had they not been running fine for weeks on v1. Miner status (hashrate: 8 Kh/s)
(miners: 11/11 uptime: 4:10, memory usage: 65%, load average: 0.41) Same pool, same controller, same hub, but only 4 miners: Miner status (hashrate: 1212 Kh/s)
(miners: 4/4 uptime: 1:50, memory usage: 58%, load average: 0.11) Please PM me the pool that you are using, so I can further debug what is going on... we have tested with wafflepool, and dogehouse. |
|
|
|
Doesn't work for me. My 6MH/s suddenly turned into 0.3MH/s no matter which frequency/pool I use or how many times I restart them. I strongly recommend that people do not upgrade at this time.
Which pool? I've tried a few different pools now. It doesn't seem to be pool related. Interestingly, if I only have a couple miners plugged into each hub, it seems to work. I'm playing plugging/unplugging games right now to see how many I can get working at once. So far I can't get more than 4 working with a single controller/hub. It's obviously pool related, we had no problems testing with 40+ units. |
|
|
|
Doesn't work for me. My 6MH/s suddenly turned into 0.3MH/s no matter which frequency/pool I use or how many times I restart them. I strongly recommend that people do not upgrade at this time.
Which pool? |
|
|
|
[2014-04-02 21:54:10] LTC process startup: Pid=0 Worker=rammy2k2 Frequency=850
[2014-04-02 21:54:23] New miner device(s) found: 8D7446745551 (ACM0), 8D8357825551 (ACM1), 8D8650845551 (ACM2), 8D8313745551 (ACM3), 8D8521855551 (ACM4), 8D863F795551 (ACM5), 8D8355945551 (ACM6), 8D8416685551 (ACM7), 8D7D21795551 (ACM8), 8D8A57735551 (ACM9)
[2014-04-02 21:54:24] LTC process shutdown
[2014-04-02 21:54:25] LTC process startup: Pid=0 Worker=rammy2k2 Frequency=850
[2014-04-02 21:54:37] New miner device(s) found: 8D7446745551 (ACM0), 8D8357825551 (ACM1), 8D8650845551 (ACM2), 8D8313745551 (ACM3), 8D8521855551 (ACM4), 8D863F795551 (ACM5), 8D8355945551 (ACM6), 8D8416685551 (ACM7), 8D7D21795551 (ACM8), 8D8A57735551 (ACM9)
[2014-04-02 21:54:37] LTC process shutdown
[2014-04-02 21:54:38] LTC process startup: Pid=0 Worker=rammy2k2.Frequency=850 upgrade went well, now after i inserted pool details im getting only this . whats this ? LE : Looks like you need to insert all 3 pool details for controller to start Just 1 pool works fine. |
|
|
|
tried to upload it, and it said invalid file...
Do not rename the bin files, and use Win 7 + Chrome.  |
|
|
|
If i have controller from jack first miners will it work? Controller was noname than.
Should work. |
|
|
|
Working fine for me.
Could you clarify how the general frequency vs. individual frequency works?
If I have general freq 850, can I adjust individually both higher and lower? Only the ones that haven't got a individual freq set gets the general?
If you didn't fill anything there, you should see the placeholder which explains the syntax. Basically it's MinerId=Frequency, seperated by comma's. |
|
|
|
Any ideas why it doesn't play nice with P2Pool?
It should work with P2Pool, no reason why it wouldn't... which pool is that? If the job_id from the stratum response is longer than 8 bits it will break though, but I haven't seen that occur yet. |
|
|
|
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?
That's not possible anymore, as it is one miner process that controls the miners, similar to cgminer. hmm.. just uploaded LAG3355_upgrade_v1.bin to my controller. now it just flashes blue once when powered on, and then nothing more?
Try power cycling your controller. Already done that 3x :/ Power on, 2x short blue light (1 ½ sec, and one 1 sec) then it just dies out, no light. Strange. What does it say on the back of the Tp-link? The Ver. number? |
|
|
|
hmm.. just uploaded LAG3355_upgrade_v1.bin to my controller. now it just flashes blue once when powered on, and then nothing more?
Try power cycling your controller. |
|
|
|
|
Show Posts
