 Show Posts
|
|
Pages: « 1 [2] 3 4 »
|
i need this week dividends to buy more shares pay us  Agreed. If the dividends were paid on time, I could have afforded 2 shares during the recent panic sales rather than just one. I'm a little pissed at that. I understand that both parties involved in the transfer are probably trying to do the right thing, but that is just me guessing since we haven't heard anything from either of them in a while. What's going on guys? _theJestre |
|
|
|
Well, I didn't think this was going to happen- My butterfly order shows shipped before I received my K16s. Wish it would have been the other way around.
Haha ya, I just received my December Jalapeno. Didn't see that coming before these, _theJestre |
|
|
|
Wednesdays use to be my favorite days because of ASICMINER dividends. Just saying something now because we didn't get dividends until I mentioned something last week on Friday.
Thanks for your work,
_theJestre
Another Wednesday is almost over. Thank you, _theJestre |
|
|
|
bump
Is this still available? |
|
|
|
So, I am running late Batch 2 with 20130703. Will flashing to the latest version increase hash rate?
Thanks!
The 20130818 firmware increased my speed by at least 1 GH/s consistently, so I'd say choose that one or later to flash. |
|
|
|
Hi, the other day I've upgraded three batch #1 three modules Avalons from 20130519 to 20130814... I've lost a good 10% of hashing capacity  Inside Avalon GUI I still see 70 GH, I'm not using --avalon-auto (nor any other option) given that I'm still using the stock PSU, but on pool graph you can clearly see when I've updated them My question is: can I go back to 20130519 without problems or do I risk to brick them? TIA spiccioli ps. I see that there is now 20130818, but I'd prefer to go back to what was working before trying next firmware. I used --avalon-auto without upgrading my batch #2 PSU. I have flashed older firmware after newer firmware successfully without much hassle. 20130818 is awesome firmware, I'd say try that at least before going backwards. _theJestre |
|
|
|
On my batch #3 three blade miner the miner #24 looks like not working well:
[match_work_count24] => 0
Any idea what I can do to check them or to test them?
I've disabled it simply now by using only configuring Miner Count = 23 because it is latest miner which is not working.
Shoot, I checked my logs to see what was going on and found this: [match_work_count3] => 0 EDIT: Batch #2 unit running 20130818 |
|
|
|
You guys really like getting your panties bunched up over every little thing that could go wrong.
Oh shoot, now you've done it... We need to argue about what _color_ those panties are now... |
|
|
|
New problem after firmware system powered down. Restarted now have solid Red light and solid orange light and no access to Avalon any ideas how to fix
Has anyone successfully power cycled after update? well powed down and I have it powered up but now solid red light and orange and cant connect to device. Its as tho its crashed partly through firmware upgrade and gone tits up now unable to access even when trying to put into fail safe You probably already tried this, but have you tried to access it on the 192.168.0.100 IP as well as whatever static IP you had it on before the upgrade? After one of my flashes I experienced the strange behavior that the unit remembered the old IP settings even though I told it to not remember the settings. Good luck, _theJestre |
|
|
|
Any idea what the hell is with the orange light lol going on and off all the time is a wierd one I must admit as wasnt doing on any other versions hope its nothing to be alarmed by.
I don't see an orange light. It isn't very dark around my unit, so I'll check again later, but I see the white light and no orange. |
|
|
|
|
Perhaps it is best to avoid speculating about what could happen.
I mean, little green men could come down from Mars and steal batch 1. What happens then?
Steamboat probably already knows what he will do, and I bet most buyers in his group buys will agree with his decision.
_theJestre
|
|
|
|
I think I done fcked myself a bit with firmware , but not too bad. Had some _really_ strange experiences flashing to 20130813-1 then trying to go back to 20130703. Let's just say things were kind of strange - made sure to NOT check the "keep settings" box, but settings were held over. Anyway Prof, looks like your hashes are nicer than mine right now. Mind posting the changes you made after you flashed to 20130814 [options set, flags, etc]? I might try that firmware when I get home tonight, my Avalon is hashing around 70 Gh/s right now, and that feels a bit slow, considering it was closer to 80 before I mucked things up by trying to "fix" it. Although I just read ck's comment about hash rate being more marketing than power. Interested to see others' results. Thanks, _theJestre |
|
|
|
|
Wednesdays use to be my favorite days because of ASICMINER dividends. Just saying something now because we didn't get dividends until I mentioned something last week on Friday.
Thanks for your work,
_theJestre
|
|
|
|
Maybe I misunderstood something I read earlier, I'm a bit confused with the different batches wanting different temperatures.
I thought with the new firmware that "70 was the new 50" for Batch 2 Avalons. Did I get that totally wrong?
For batch 3 Avalons, so yes you got it wrong. Remove those lines ASAP. Thank you so much for your advice, support, and software! I've removed the temp settings, now only have this: --avalon-auto --avalon-freq 325-375 I'll throw some BTC your way later today or tomorrow, need to eat now. Thanks again! _theJestre |
|
|
|
--avalon-auto --avalon-cutoff 80 --avalon-freq 300-360 --avalon-temp 70
Interesting. I uploaded a 20130814 (which is basically the same as the 20130813-1 firmware, just with the cgminer 3.3.4 tag). What I've found with the changed code is that my (batch2) avalon hovers at a lower frequency of 345 instead of 352, but ends up with the same hashrate. If there was something I'd recommend for you on batch 2, it is NOT setting your temperature so high. That is almost certainly contributing to your hardware errors and may damage your chips. If you really want to run them high, I'd suggest 60/70 instead of 70/80, but the defaults are there for a reason. Maybe I misunderstood something I read earlier, I'm a bit confused with the different batches wanting different temperatures. I thought with the new firmware that "70 was the new 50" for Batch 2 Avalons. Did I get that totally wrong? Thanks, _theJestre |
|
|
|
Hey, what are some Pools you guys would recommend I join?
I'm currently gpu mining at btcguild, but once I get my knc I wanna change pools for decentralization purposes.
I'm in the USA.
So far, bitparking and eclipsemc look pretty good.
I'm on BTCGuild now, and have to say I had terrible experiences with Ozcoin. I'd skip them if you were trying out new pools. Just my opinion, that's all. _theJestre |
|
|
|
|
Hi all,
Just saw the new firmware 20130813-1 and thought I'd upgrade from 20130703, which was giving me ~78Gh/s on my batch 2 Avalon. I was using just --avalon-auto to achieve this.
I'm getting less Gh/s now, probably about 72 or so. I'm using these options:
--avalon-auto --avalon-cutoff 80 --avalon-freq 300-360 --avalon-temp 70
Am I doing something wrong, do these numbers look completely off base?
Should batch 2 Avalons just stick to the 20130703 firmware?
Thanks,
_theJestre
|
|
|
|
Thanks for weathering the storm with us Steamboat. This position sucks, for both you and us. Up to this point I was still optimistic about these chips and units. At this point I think it is time to try and leverage a discount on these chips, although I understand there isn't much you can use to force the issue since BTC transactions are final.
EDIT: man this sucks.
"BTC transactions are final."? They have a refund option on all pre-orders of the 10k batches, and avalon is a company. Some groupbuyers have done it, but no reply since, and first one i've seen was done six days ago. Just because the monetary transaction used was BTC, doesn't make their actions legal or able to be left unaccountable for. http://support.avalon-asic.com/ , this is where the purchases can be refunded.. Sorry, I meant that BTC transactions are irreversible. http://bitcoin.org/en/you-need-to-know |
|
|
|
Yifu has posted a response regarding the chip delivery delays, which can be found here: http://avalon-asics.comUnfortunately, the post does not provide any specifics on shipping dates moving forward, and offers very little information about the delays experienced to this point. Our inquiries by other means specifically regarding our orders have remain unanswered, and we have not received any information as to the status of our batches from either Yifu or any member of his team. For these reasons, we have chosen to close Batch 7. Those who have placed an order for Batch 7 have been sent an email with further information. We remain optimistic the chips which have already been ordered will be delivered, though we do not have any information as to when our orders will be fulfilled. We are exploring our options, and will continue to monitor the situation closely. We will post an update the moment we have definitive information. Thanks for weathering the storm with us Steamboat. This position sucks, for both you and us. Up to this point I was still optimistic about these chips and units. At this point I think it is time to try and leverage a discount on these chips, although I understand there isn't much you can use to force the issue since BTC transactions are final. EDIT: man this sucks. |
|
|
|
BitMinter ( https://bitminter.com) Nice stats and info on the progress. Merged mining with NMC for a little extra income. Not too big (yet). What has been your average BTC/24hr at what hash rate? I have been pretty close to 1 BTC/24hr @ 77 Gh/s in BTCGuild PPLNS, which also does NMC merged mining. |
|
|
|
|
