After flashing to the July update, my HW errors went from 3ish percent to now 30%. I'm thinking I will revert...
That makes no sense =/
Topic: Avalon ASIC users thread - page 125. (Read 438516 times)
That makes no sense =/
After flashing to the July update, my HW errors went from 3ish percent to now 30%. I'm thinking I will revert...
That makes no sense =/
After flashing to the July update, my HW errors went from 3ish percent to now 30%. I'm thinking I will revert...
Problems mining on a pool is this cgminer problem within unit or is this problem on their side on the pool
The shares you sent have been looking like this:
020000005e4757cdbd7b756ceac436c46fe3ba6d9f532adaca8541c3beba010000000000246cf2c 7800231d5d50c5a7c9241e7465fb2085346478a4b95c70a34d43fec20daa1dc518db6011b70523f dc80000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000280
I think your miner messed up formatting the shares from mining to results.
it seems that it puts the result at the beginning
correct form should be:
result of the hash:
020000005e4757cdbd7b756ceac436c46fe3ba6d9f532adaca8541c3beba01
data sent to pool
0000000000246cf2c7800231d5d50c5a7c9241e7465fb2085346478a4b95c70a34d43fec20daa1d c518db6011b70523fdc800000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000280
Is this a bug to be fixed? or something to do with cgminer or something to do on their side on the pool ?
The shares you sent have been looking like this:
020000005e4757cdbd7b756ceac436c46fe3ba6d9f532adaca8541c3beba010000000000246cf2c 7800231d5d50c5a7c9241e7465fb2085346478a4b95c70a34d43fec20daa1dc518db6011b70523f dc80000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000280
I think your miner messed up formatting the shares from mining to results.
it seems that it puts the result at the beginning
correct form should be:
result of the hash:
020000005e4757cdbd7b756ceac436c46fe3ba6d9f532adaca8541c3beba01
data sent to pool
0000000000246cf2c7800231d5d50c5a7c9241e7465fb2085346478a4b95c70a34d43fec20daa1d c518db6011b70523fdc800000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000280
Is this a bug to be fixed? or something to do with cgminer or something to do on their side on the pool ?
i've done it more times than i could count... thought i bricked one once but a quick hard reboot solved it all
Isn't rebooting during a flash pretty much the worst possible idea?
I've done this a million times on server hardware. Never with an ASIC. The downtime in case of an issue and probable lack of being able to return it is what scares me.
All you are flashing is the router really =) nothing else. It should be fine, I doubt it has a very high failure rate... I havent heard of any known flashing failures on avalon, under normal conditions.
But yeah, its just like flashing a mobo, same chances of failing I suppose... which over my PC career seems to be 1% of flashes I do, something breaks =P
It actually happened to me. The reality is that the TPLINK routers in these things are not 100% perfect and some of them will have some minor failures and defects. So, in the rare event that this happens to you I STRONGLY suggest you get yourself a Raspberry Pi as a backup mining device.
i've done it more times than i could count... thought i bricked one once but a quick hard reboot solved it all
Isn't rebooting during a flash pretty much the worst possible idea?
I've done this a million times on server hardware. Never with an ASIC. The downtime in case of an issue and probable lack of being able to return it is what scares me.
All you are flashing is the router really =) nothing else. It should be fine, I doubt it has a very high failure rate... I havent heard of any known flashing failures on avalon, under normal conditions.
But yeah, its just like flashing a mobo, same chances of failing I suppose... which over my PC career seems to be 1% of flashes I do, something breaks =P
i've done it more times than i could count... thought i bricked one once but a quick hard reboot solved it all
Isn't rebooting during a flash pretty much the worst possible idea?
I've done this a million times on server hardware. Never with an ASIC. The downtime in case of an issue and probable lack of being able to return it is what scares me.
i've done it more times than i could count... thought i bricked one once but a quick hard reboot solved it all
Sounds good to me, performance looks awesome already but some more reliability would be even more important.
I will admit flashing it sounds a little scary. If I brick it it's all over.
I will admit flashing it sounds a little scary. If I brick it it's all over.
It sounds scary, but I've done it twice on three different ones and it was fine.
craslovell - seriously - one or two posts - not 9.
Have you never used a forum before in your life?
Have you never used a forum before in your life?
Sorry, this thing cost me a pretty penny. I just wanted some advice to help get it working. Was running fine for hours then started fudging around.
Thanks for the valuable input..
FW update is a must to get the thing running better then it is now =)
Improves reliability significantly.
Sounds good to me, performance looks awesome already but some more reliability would be even more important.
I will admit flashing it sounds a little scary. If I brick it it's all over.
craslovell - seriously - one or two posts - not 9.
Have you never used a forum before in your life?
Have you never used a forum before in your life?
Sorry, this thing cost me a pretty penny. I just wanted some advice to help get it working. Was running fine for hours then started fudging around.
Thanks for the valuable input..
FW update is a must to get the thing running better then it is now =)
Improves reliability significantly.
craslovell - seriously - one or two posts - not 9.
Have you never used a forum before in your life?
Have you never used a forum before in your life?
Sorry, this thing cost me a pretty penny. I just wanted some advice to help get it working. Was running fine for hours then started fudging around.
Thanks for the valuable input..
how can I force it to use the secondary wired connection for pool connecting? I'm connected to the default 192.168.0.100
I added the secondary as 192.168.1.45
I added the secondary as 192.168.1.45
I am so confused dude, what exactly is it that you are trying to do?
Also, first update the avy firmware to conmans latest cgminer build:
http://ck.kolivas.org/apps/cgminer/avalon/20130703/
It's running on wireless again. I'm going to monitor it for now. Will consider FW update later this week.
craslovell - seriously - one or two posts - not 9.
Have you never used a forum before in your life?
Have you never used a forum before in your life?
how can I force it to use the secondary wired connection for pool connecting? I'm connected to the default 192.168.0.100
I added the secondary as 192.168.1.45
I added the secondary as 192.168.1.45
I am so confused dude, what exactly is it that you are trying to do?
Also, first update the avy firmware to conmans latest cgminer build:
http://ck.kolivas.org/apps/cgminer/avalon/20130703/
how can I force it to use the secondary wired connection for pool connecting? I'm connected to the default 192.168.0.100
I added the secondary as 192.168.1.45
I added the secondary as 192.168.1.45
tried to add secondary lan connection for wired connection and now I can't connect to the miner at all.... what a headache this is causing
pure stales coming across now
Looks like cgminer is started, but no accepts or anything....
Ahhh I just want this contraption to work!
Ahhh I just want this contraption to work!
And I'm getting socket connect failed now. No cgminer start.
From what I read I may have some ports being blocked? Hopefully ISP didn't shut me down!
From what I read I may have some ports being blocked? Hopefully ISP didn't shut me down!
Jump to: