Show Posts
|
Pages: « 1 2 3 [4] 5 »
|
I own some bitcoins, but I have upcoming expenses, so it seems I would need to sell them shortly... But, at the same time, I am bullish on bitcoin, so I am sure, I will buy them back in lets say 4-6 months when I raise enough cash back. Since I am speculating that btcusd will go up soon, what I would really like to do is guarantee myself same price to buy them at later. The best vehicle that I know of to give me that, are options (perfect would be "JAN'15 CALL option @ $450/BTC"). I would be willing to pay a premium for such a contract... I've been looking around, but no exchange/broker (not even ones wo/ reputation) is offering bitcoin options. Have I missed anything? Any ideas how to do this alternatively? I've seen some "futures" contract sites like https://icbit.se/ and bitfinex, but I dont understand them completely, and I am not sure whether they offer a "product" that would help my situation... Ideas?
|
|
|
Yifu totally screwed over batch 4 customers with his delays... 104 BTC... my unit has produced not even close to that amount. Im not happy at all.
Do you mean Batch 3? My 4 module unit has generated BTC 55.3 until today So yes, we are screwed. But not as much as the other (chip sales) customers Yifu screwed over I wonder if he is ever going to set this right or just run with the money and live with bad karma +1 Just did stats few days ago ... sum of my avalon b3 minings are 43btc ![Sad](https://bitcointalk.org/Smileys/default/sad.gif)
|
|
|
How do i SHUTDOWN avalon? Restarting is not enough as I need to shutdown machine, and I need to do it remotely. I can access it via SSH, but cant find any command there? Help?
thanks, w
|
|
|
Update: my avalon is working again. I just needed to physically turn it off, and then on again and it started hashing... Weird that system reboot did not fix this. WHAT ABOUT FUTUREAnyhow, to comment on my avalon ROI... I bought B3 avalon 4module in march, got it in only start of august, and untill now it mined around 53btc... but i paid 100btc for it. So overall i'd say I dont expect anyone from B3 to get a positive ROI. I am really sorry I missed that email from avalon team when they offered return of payment. ![Sad](https://bitcointalk.org/Smileys/default/sad.gif) I was in middle of my holidays and without email ![Sad](https://bitcointalk.org/Smileys/default/sad.gif) I would like to hear from Avalon guys with some special deal for B3 owners - upgrade modules to 28nm boards for avalon for example at a special price... Anything like that on horizont? I think they intentionally skipped making own devices from 55nm chips, as it looks like they are concentrating on 28nm chips... Cant wait to hear news on that. And, apart from what is maybe even majority view here at forum, i still think avalon guys are doing their best and are not intentionally pissing off their customers, but sometimes things do no go according to plan...
|
|
|
I think i have identical problem... Just today I noticed that my hash rate is 0 for last few days... I can connect to avalon, but remote I cannot fix it.. (i did numerous restarts, changed configs etc).. nothing... Will go inspect the unit tomorrow in person (might be that some chips died again, so i'll take unit apart and see...) Weird thing is that the fans seem to be completely off as well.. here is log. Any ideas? [Firmware Version] => 20130821 cgminer-70bc62c luci-d854edc+ cgminer-openwrt-packages-800cc58 Reply was 'STATUS=S,When=1384377764,Code=70,Msg=CGMiner stats,Description=cgminer 3.4.0|STATS=0,ID=AVA0,Elapsed=33,Calls=0,Wait=0.000000,Max=0.000000,Min=99999999.000000,baud=115200,miner_count=8,asic_count=10,timeout=40,frequency=315,fan1=0,fan2=0,fan3=0,temp1=0,temp2=0,temp3=0,temp_max=0,Device Hardware%=0.0000,no_matching_work=0,match_work_count1=0,match_work_count2=0,match_work_count3=0,match_work_count4=0,match_work_count5=0,match_work_count6=0,match_work_count7=0,match_work_count8=0,USB Pipe=0,USB Delay=r0 0.000000 w0 0.000000,USB tmo=2397 0|STATS=1,ID=POOL0,Elapsed=33,Calls=0,Wait=0.000000,Max=0.000000,Min=99999999.000000,Pool Calls=0,Pool Attempts=0,Pool Wait=0.000000,Pool Max=0.000000,Pool Min=99999999.000000,Pool Av=0.000000,Work Had Roll Time=false,Work Can Roll=false,Work Had Expire=false,Work Roll Time=0,Work Diff=1.00000000,Min Diff=1.00000000,Max Diff=1.00000000,Min Diff Count=65,Max Diff Count=65,Times Sent=3,Bytes Sent=219,Times Recv=6,Bytes Recv=10710,Net Bytes Sent=219,Net Bytes Recv=10710|STATS=2,ID=POOL1,Elapsed=33,Calls=0,Wait=0.000000,Max=0.000000,Min=99999999.000000,Pool Calls=0,Pool Attempts=0,Pool Wait=0.000000,Pool Max=0.000000,Pool Min=99999999.000000,Pool Av=0.000000,Work Had Roll Time=false,Work Can Roll=false,Work Had Expire=false,Work Roll Time=0,Work Diff=2.00000000,Min Diff=2.00000000,Max Diff=2.00000000,Min Diff Count=70,Max Diff Count=70,Times Sent=2,Bytes Sent=149,Times Recv=5,Bytes Recv=2524,Net Bytes Sent=149,Net Bytes Recv=2524|STATS=3,ID=POOL2,Elapsed=33,Calls=0,Wait=0.000000,Max=0.000000,Min=99999999.000000,Pool Calls=0,Pool Attempts=0,Pool Wait=0.000000,Pool Max=0.000000,Pool Min=99999999.000000,Pool Av=0.000000,Work Had Roll Time=false,Work Can Roll=false,Work Had Expire=false,Work Roll Time=0,Work Diff=1.00000000,Min Diff=1.00000000,Max Diff=3.00000000,Min Diff Count=27,Max Diff Count=45,Times Sent=2,Bytes Sent=150,Times Recv=7,Bytes Recv=3550,Net Bytes Sent=150,Net Bytes Recv=3550|' [STATUS] => ( [STATUS] => S [When] => 1384377764 [Code] => 70 [Msg] => CGMiner stats [Description] => cgminer 3.4.0 ) [STATS0] => ( [STATS] => 0 [ID] => AVA0 [Elapsed] => 33 [Calls] => 0 [Wait] => 0.000000 [Max] => 0.000000 [Min] => 99999999.000000 [baud] => 115200 [miner_count] => 8 [asic_count] => 10 [timeout] => 40 [frequency] => 315 [fan1] => 0 [fan2] => 0 [fan3] => 0 [temp1] => 0 [temp2] => 0 [temp3] => 0 [temp_max] => 0 [Device Hardware%] => 0.0000 [no_matching_work] => 0 [match_work_count1] => 0 [match_work_count2] => 0 [match_work_count3] => 0 [match_work_count4] => 0 [match_work_count5] => 0 [match_work_count6] => 0 [match_work_count7] => 0 [match_work_count8] => 0 [USB Pipe] => 0 [USB Delay] => r0 0.000000 w0 0.000000 [USB tmo] => 2397 0 ) [STATS1] => ( [STATS] => 1 [ID] => POOL0 [Elapsed] => 33 [Calls] => 0 [Wait] => 0.000000 [Max] => 0.000000 [Min] => 99999999.000000 [Pool Calls] => 0 [Pool Attempts] => 0 [Pool Wait] => 0.000000 [Pool Max] => 0.000000 [Pool Min] => 99999999.000000 [Pool Av] => 0.000000 [Work Had Roll Time] => false [Work Can Roll] => false [Work Had Expire] => false [Work Roll Time] => 0 [Work Diff] => 1.00000000 [Min Diff] => 1.00000000 [Max Diff] => 1.00000000 [Min Diff Count] => 65 [Max Diff Count] => 65 [Times Sent] => 3 [Bytes Sent] => 219 [Times Recv] => 6 [Bytes Recv] => 10710 [Net Bytes Sent] => 219 [Net Bytes Recv] => 10710 ) [STATS2] => ( [STATS] => 2 [ID] => POOL1 [Elapsed] => 33 [Calls] => 0 [Wait] => 0.000000 [Max] => 0.000000 [Min] => 99999999.000000 [Pool Calls] => 0 [Pool Attempts] => 0 [Pool Wait] => 0.000000 [Pool Max] => 0.000000 [Pool Min] => 99999999.000000 [Pool Av] => 0.000000 [Work Had Roll Time] => false [Work Can Roll] => false [Work Had Expire] => false [Work Roll Time] => 0 [Work Diff] => 2.00000000 [Min Diff] => 2.00000000 [Max Diff] => 2.00000000 [Min Diff Count] => 70 [Max Diff Count] => 70 [Times Sent] => 2 [Bytes Sent] => 149 [Times Recv] => 5 [Bytes Recv] => 2524 [Net Bytes Sent] => 149 [Net Bytes Recv] => 2524 ) [STATS3] => ( [STATS] => 3 [ID] => POOL2 [Elapsed] => 33 [Calls] => 0 [Wait] => 0.000000 [Max] => 0.000000 [Min] => 99999999.000000 [Pool Calls] => 0 [Pool Attempts] => 0 [Pool Wait] => 0.000000 [Pool Max] => 0.000000 [Pool Min] => 99999999.000000 [Pool Av] => 0.000000 [Work Had Roll Time] => false [Work Can Roll] => false [Work Had Expire] => false [Work Roll Time] => 0 [Work Diff] => 1.00000000 [Min Diff] => 1.00000000 [Max Diff] => 3.00000000 [Min Diff Count] => 27 [Max Diff Count] => 45 [Times Sent] => 2 [Bytes Sent] => 150 [Times Recv] => 7 [Bytes Recv] => 3550 [Net Bytes Sent] => 150 [Net Bytes Recv] => 3550 )
[/code]
|
|
|
Today I experienced smoke as well. After inspection I noticed 2 burnouts on 1 module. Other 3 modules are already working again...
SO - with this problematic one - any ideas how to make it work again? Is there any way to make this module work without the burnout part/area?
How to fix this? Is it enough to get burnout parts replaced? (are they anything special or should I get them anywhere?)... Or are the nearby chips damaged too? Any recepie from anyone who went thru this before? Experience and ideas welcome!
Looks similar to the burnt components I ran into a couple weeks ago (back a few pages in this thread). I decided to bend the pins where the bus plugs into the module, since I don't have soldering skills and finding the components and someone to do the work would be more time and effort than one worker is worth. The rest of the workers on my module seem to work just fine. O, this is awesome. I did not think of that, because all workers are interconnected .... so I thought that one not working breaks the chain... But - cant wait to try it out. Thanks!
|
|
|
Today I experienced smoke as well. After inspection I noticed 2 burnouts on 1 module. Other 3 modules are already working again...
SO - with this problematic one - any ideas how to make it work again? Is there any way to make this module work without the burnout part/area?
How to fix this? Is it enough to get burnout parts replaced? (are they anything special or should I get them anywhere?)... Or are the nearby chips damaged too? Any recepie from anyone who went thru this before? Experience and ideas welcome!
Once I knocked down one of the small capacitors around the chip, but it still hash very well so I don't bother. This one on your picture is a bit large, you might need to get a similar one to re-solder it on, I think there is an open sourced component list provided by bitsyncom a couple of months ago Yeah, these two components somehow prevent machine from starting up... I guess the big one... Will look for the component list and see what can be done.. ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) thanks.
|
|
|
Today I experienced smoke as well. After inspection I noticed 2 burnouts on 1 module. Other 3 modules are already working again... SO - with this problematic one - any ideas how to make it work again? Is there any way to make this module work without the burnout part/area? How to fix this? Is it enough to get burnout parts replaced? (are they anything special or should I get them anywhere?)... Or are the nearby chips damaged too? Any recepie from anyone who went thru this before? Experience and ideas welcome! ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FvYfIs4H.jpg&t=662&c=axEFKHoPU0-5YQ)
|
|
|
I am using WIFI... Today (after 3 days of not checking the unit), i found it with LOAD of over 18, and hashing at 5xxx MH only... I did a cgminer restart in system-services and hash rates returned to normal... (90.000MH), but load stayed over 15 ... any ideas? i checked kernel log, and looks normal until approx 3,5day into operation when bunch of entries like these show: [316582.730000] usb 1-1: clear tt 1 (9031) error -71 [316584.160000] usb 1-1: clear tt 1 (8030) error -71 [316584.180000] usb 1-1: clear tt 1 (8030) error -71 [316584.190000] usb 1-1: clear tt 1 (8030) error -71 [316584.200000] usb 1-1: clear tt 1 (0030) error -71 [316589.840000] usb 1-1: clear tt 1 (8030) error -71 [316589.850000] usb 1-1: clear tt 1 (8030) error -71 [316589.860000] usb 1-1: clear tt 1 (8030) error -71 ... .. 16824.590000] usb 1-1: clear tt 1 (8030) error -71 [316824.620000] usb 1-1: clear tt 1 (0030) error -71 [316828.000000] usb 1-1.1: USB disconnect, device number 3 [316828.150000] usb 1-1: reset high-speed USB device number 2 using ehci-platform [316828.630000] usb 1-1.1: new full-speed USB device number 4 using ehci-platform [316828.810000] ftdi_sio 1-1.1:1.0: FTDI USB Serial Device converter detected [316828.850000] usb 1-1.1: Detected FT232RL [316828.850000] usb 1-1.1: Number of endpoints 2 [316828.850000] usb 1-1.1: Endpoint 1 MaxPacketSize 16384 [316828.860000] usb 1-1.1: Endpoint 2 MaxPacketSize 16384 [316828.860000] usb 1-1.1: Setting MaxPacketSize 64 [316828.870000] usb 1-1.1: FTDI USB Serial Device converter now attached to ttyUSB0 [316830.890000] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 [316830.900000] ftdi_sio 1-1.1:1.0: device disconnected I notice that sometimes the total MHS5s hashrate drops to weird low number (like 4 digits only)... is this normal?
No. If you are using an ethernet connection, you must delete the WWAN device from the 'network' interfaces, and under network/wifi/avalon_ap make sure it shows 'wireless network is disabled'. Until I did both of these step I had the same problem. Since this describes my problem, i tried this link below, but its not working no more? ideas? thanks, Jaka One of my batch 3 avalons is performing very poorly due to a high HW errors. Unplugging all by one module, each module individually has between a 25 and 75% HW error rate at either 256 or 300Mhz.
This degraded performance starting after about 6 hours of mining at 300Mhz.
Is there anything I should try before trying to make a warranty claim?
I was calculating the hardware error rate wrong. It should be HW/LocalWork, which brings the error rates i'm seeing to a much more reasonable 1%. Regardless, 3 out of 4 of my batch 3 units end up with <10Gh/s after 3-12hrs of mining, some more frequently than others. Could this behavior be due to the new temperature throttling feature? I have the default temperature limits of 70C target and 90C cutoff, but I don't see the temps going over 70C. I'm having this same issue. EDIT: so is the solution is to disable wifi or to implement the load monitor with auto-restart? Is this issue resolved? For me, disabling/removing wifi/wlan wasn't enough. If you already removed wifi and it's still a problem, look at your load avg, if it's spiking, then you probably need the auto-restart I posted at https://bitcointalk.org/index.phptopic=140539.msg2898478#msg2898478If the load avg is low (under 1.0) then you should check all the connectors inside your avalon. I did have one of the wide ribbon cables wiggle loose (I probably bumped it installing the psu) and the result was about 20%+ lower peak hashes and odd hangups.
|
|
|
I notice that sometimes the total MHS5s hashrate drops to weird low number (like 4 digits only)... is this normal? One time I even noticed that the average MHSav was also similary low... I did a restart of cgminer service, and it went back to 80k+ ... Could we somehow implement this https://github.com/shazbits/cgminer-monitor instead of the cgminer-monitor that is run in cron? any other solution to monitor the MHSav/5s and act appropriately? thanks, J
|
|
|
Yeeeees, Got mine 4-module wo-psu avalon today! Already mining ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) All in all - looks like a well build machine. Loud as hell tho ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) but it is a warm week here in EU...
|
|
|
Order: #491x 1 avalon with 4 units no psu DHL EU paid on 3/25
|
|
|
I have time to prepare for my batch #3 avalon import... but since our customs office is really a pain in the ass - i usually need to show payment receipt or proof what is the actual value of the imported goods - so that they can then hit me with 20% tax on it...
I already heard from few users - that avalon marks $300 as the value on the box... but with my experience customs might ask me to verify this number... Now, with avalon asic and payment in BCs that might get complicated (especially is BC value goes beyond $100 by mid may)...
So I am asking all batch#1 and batch#2 european users - how was your experience, and how much tax did you pay - or even if you managed to avoid it - what did you tell the customs?
Also - has anyone sent avalon to a company's address? And particularities there?
thanks, W
|
|
|
I tried my luck with avalon #3 as well... order no #49xx ... Looking forward to smooth delivery to EU....
Team avalon - god speed to you!
|
|
|
Hmmm... I am thinking about jumping on batch 3 order, but I am wondering about the EU customs and taxation... at 20% tax on imports... which value will Avalon mark the device? 7000k USD? 1500 USD range as previous batches? This might make B3 avalon additional 20% more expensive... :|
|
|
|
Any update on the #112 Event system ticket? It was meant for 2.9.0 if i read it correctly ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) Cant wait to see it in action! cheers, W
|
|
|
Would it be possible to get summary of runtime statistics that is usually displayed at exit, automatically sent to email, for example, every 24 hours? That would be really nice, as I have 4 machines running bfgminer with p2pool, and sometimes i forget about them for days, only to find out later that one of the GPUs stopped working some time ago... ?
or - can it send alerts to email, if mining speed drops below set treshold ? that would be even better!
If this is not possible - is it possible to save this to LOG file? I am running windows binaries from script, so when i press Q scripts ends and CMD window automatically closes, so they are gone... I tried 2>log.txt, but i dont think this works under windows... ?
|
|
|
I am currently on latest p2pool (3.1), mining with cgminer (2.7.4)... Since few weeks ago a few minutes after start of cgminer, on system with 3 GPUs, only one of the GPUs still works at full power, while other two go to IDLE (mining only with few MH/s, instead of few hundreds). See the screenshot below... What is curious is the message - "Pool 0 not providing work fast enough" ... Anyone experiencing the same? Any idea how to resolve this? I reported it to cgminer thread as well, but not sure why the problem... Bitcoind is 0.6.3. http://s11.postimage.org/s0ldetish/problem2012_08_30_151010.png
|
|
|
I am currently on latest cgminer (2.7.4), mining with p2pool (3.1)... Since 2.7.x CGMINER uses all my CPU (on multicore CPU system), but what is even more problematic is that in few minutes after start of cgminer, on system with 3 GPUs, only one of the GPUs still works at full power, while other two go to IDLE (mining only with few MH/s, instead of few hundreds). See the screenshot below... What is curios is the message - "Pool 0 not providing work fast enough" ... but since p2pool v.3.1 is a month+ old, it was running without problems on older versions of cgminer... Anyone experiencing the same? Any idea how to resolve this? Should I report it to p2pool thread as well? Bitcoind is 0.6.3. http://s11.postimage.org/s0ldetish/problem2012_08_30_151010.png
|
|
|
I for one am eagerly awaiting time when revard for new mined block halves... Will be interesting to see what happens to community/price then.
|
|
|
|