Order no. 3# here
No email advising of dispatch, order status on BA site is still 'Processed'
I ordered in mid September last year, I would assume mine would be shipped pretty quickly after shipping being announced.
Not happy at all
I'd like to know how you can be order #3 for an X1 and yet it's been stated that a batch is being delivered to re-sellers! How is that shipping by paid date? I would like to know how you know the reseller didn't pay before you? |
|
|
|
I haven't had a Gridseed USB Mini come in the little white box since mid April.
Gridseed also ship boxes of 10 units, not just single boxes, (there use to be photos on the GAW site of the 10pack) so if the unit was from a box of 10 you wouldn't get the small box. |
|
|
|
|
I am having trouble understanding the last update, exactly what is being shipped and when for people that have X1 orders via Minersource?
|
|
|
|
Why would BA ship to resellers first when they haven't even started shipping to its direct customers yet?
Because resellers are probably their biggest customers. |
|
|
|
My losses total 1 BTC Plus the loss of 0.125 BTC in shares at CryptoStock (who didn't assign the one for 8 share dilution) Total losses 1.125 BTC The Whois for CoinEX.PW points to PO Box 16 Nobby Beach Queensland 4218 Which is on the Gold Coast in Australia. http://dig.whois.com.au/whois.php?dom=coinex.pw&submit=WHOIS+Lookup (Feel free to try it out) *rattle* *rattle* 1AhuQTWMu185kWFmiUHhmTTVYjKR7BfirW That's just the postal address of privacyprotect.org, the company who masks contact details in DNS records to stop fake renewal notice scammers etc. . |
|
|
|
Just an fyi looks like at least one Fury has had the power supply melt causing a potential fire hazard and seems to be poor soldering on the barrel connector as it detached from that particular persons Fury. I should've saved the pictures...
This was on the Gawminers community forum however that thread has since been deleted.
I have seen a lot of similar connectors melt on cheap USB 10 port hubs when fed off a 5Amp power supply. I suspect that they might not be making good contact for the current. Make sure the connector is not loose in the socket, else it can arc and heat up. The connectors have a 5A rating http://www.newark.com/cliff-electronic-components/dc10a/connector-2-1mm-dc-power-jack/dp/08WX2563 |
|
|
|
|
Has it really been 7mths for some people? I didn't order until Jan so it just over 6 mths for me. it's quite interesting to note that BFL "only" took 6mths to deliver my jalapenos last year.
|
|
|
|
|
My Fury arrived quickly and works great, no complaints. I ended up recompiling the cgminer 3.3.1 source they provided, so I had curses support.
|
|
|
|
Ah good, the source wasn't there last night when I grabbed the Pi binary, they have added it since then. I can't handle cgminer without curses support, easy fixed. autoreconf -fvi
./configure CFLAGS="-O2" --with-curses
make With the 328 suggested clock, the Fury want's to run at around 1.3MH/s which just seems to have a few too many HW errors (5%), I would be interested to see what clock people think is best. The sweet spot for me seems to set the clock around 310 |
|
|
|
[code
[2014-05-28 07:08:40] Accepted bd6d320e Diff 216/182 ICA 0
[2014-05-28 07:08:45] Accepted 2abc7adb Diff 797/182 ICA 0
[2014-05-28 07:08:51] Accepted 0107184b Diff 341/182 ICA 0
[2014-05-28 07:09:08] Accepted a42457f5 Diff 340/182 ICA 0
[2014-05-28 07:09:11] Accepted 024af4d3 Diff 3.12K/182 ICA 0
[2014-05-28 07:09:18] Accepted 432684ff Diff 200/182 ICA 0
[2014-05-28 07:09:22] Pool 0 stale share detected, submitting as user requested
[2014-05-28 07:09:22] Accepted 8d6e8c35 Diff 315/182 ICA 0
[2014-05-28 07:09:23] Pool 0 stale share detected, submitting as user requested
[2014-05-28 07:09:23] Accepted 81cd16be Diff 355/182 ICA 0
[2014-05-28 07:09:33] Pool 0 stale share detected, submitting as user requested
[2014-05-28 07:09:33] Accepted 006be7ae Diff 532/182 ICA 0
[2014-05-28 07:09:39] Network diff set to 6.2M
[2014-05-28 07:09:39] Stratum from pool 0 detected new block
[2014-05-28 07:09:52] Accepted 16e89187 Diff 1.87K/182 ICA 0
[2014-05-28 07:09:59] Accepted d12e6f5e Diff 306/182 ICA 0
(5s):397.8K (avg):1.238Mh/s | A:67 R:0 HW:3 U:11.8/m WU:1510.2/m
GAW Fury mining away quite happily using 328 clock. About 54watts at the wall but that includes my Pi, and USB 3.0 hub plug packs. |
|
|
|
|
My week one Fury just arrived a few minutes ago.
What miner do I use with it?
|
|
|
|
|
They started shipping on the 26th. as promised.
|
|
|
|
Mining is mostly irrelevant to recovery. It was/is an exchange first and foremost.
To that, simply functioning as an exchange would generate fee's to repay everyone with, which was the original intention. If the site can not function as an exchange, then there is no chance of recovering. It's not functioning as an exchange however, so recovery is dead.
The problem on top of the broken mining is the wallets are empty, people are not going to deposit there, too high risk, but many would mine a few low coins like DEM which worked until a day ago, and perhaps a couple of low diff ones like OSC and others which don't require massive hash rates. Erundook should pull all but a few coins out of the list of mining pools and focus on keeping those running, perhaps increase the fees a bit. If it looked like he was interested, many people would support him. It's his move. |
|
|
|
|
Is there any coin you can still mine on Coinex? Every coin I tried failed. If Erundook is not going to let people mine, then he has no chance of recovering the exchange in which case why is it still online?
|
|
|
|
|
Step #1 Fix the security holes.
Step #1 Disable most of the coins with empty wallets, take them off the screen, put them back at a later date.
Step #3 Let people mine and trade a limited number of coins to help build up exchange liquidity from fees.
At the moment people are just trying to convert and withdraw whatever they can get out which doesn't help the exchange regain funds. It needs people mining.
|
|
|
|
To all! Go to this pool. Together we will find a lot of blocks!
Not much point finding blocks if the auto-payout doesn't work for me. Is there some way to do a manual payout? |
|
|
|
Most people are a lot reluctant to pay for more hardware when the first lot has even shipped.
Most miners are not very bright, you only have to look at all the hash power focused on BTC to see that! The upsize mentality. |
|
|
|
I am trying to understand why BA are still doing procurement of non ASiC related components (cases, LCD etc) several months after the promised ship date of Feb 24 th. Can someone enlighten me, did I miss something important?
It all started with the "Pin-out" of the Minion,they couldn't finish the design of the PCB and other componants until they new the size/location/number of the little pins on the bottom of the Minion,they wouldn't know this until they got the first test waffer from Global,not haveing the PCBs and other shit finalized held up everything else. They did get the LCDs but the were crap so they send them back and started over.Fit problems also heled things up a bit. But LCD's and cases have nothing to do with the layout of the pins on the printed circuit board, if the displays were crap, then I would imagine they sent them back in January or early February at the latest with the expected ship date of Feb 24th. |
|
|
|
|
I am trying to understand why BA are still doing procurement of non ASiC related components (cases, LCD etc) several months after the promised ship date of Feb 24 th. Can someone enlighten me, did I miss something important?
|
|
|
|
I am having trouble compiling cgminer, pretty much any version from the past few months on either Mac OSX 10.9 (Mavericks) or 10.6.11 (Snow Leopard) I am using the Mac ports collection for the dependencies, and I was able to comilpe a few months ago but can't anymore, so something has changed. The error I get is: Making all in libusb-1.0
/Applications/Xcode.app/Contents/Developer/usr/bin/make all-recursive
Making all in libusb
CC os/libusb_1_0_la-darwin_usb.lo
In file included from /System/Library/Frameworks/IOKit.framework/Headers/usb/IOUSBLib.h:27:0,
from os/darwin_usb.h:27,
from os/darwin_usb.c:43:
/System/Library/Frameworks/IOKit.framework/Headers/usb/USB.h:584:9: error: too many #pragma options align=reset
#pragma options align=reset
^
In file included from /System/Library/Frameworks/IOKit.framework/Headers/usb/IOUSBLib.h:27:0,
from os/darwin_usb.h:27,
from os/darwin_usb.c:43:
/System/Library/Frameworks/IOKit.framework/Headers/usb/USB.h:754:9: error: too many #pragma options align=reset
#pragma options align=reset
^
/System/Library/Frameworks/IOKit.framework/Headers/usb/USB.h:806:9: error: too many #pragma options align=reset
#pragma options align=reset
^
/System/Library/Frameworks/IOKit.framework/Headers/usb/USB.h:824:9: error: too many #pragma options align=reset
#pragma options align=reset
^
/System/Library/Frameworks/IOKit.framework/Headers/usb/USB.h:844:9: error: too many #pragma options align=reset
#pragma options align=reset
^
make[5]: *** [os/libusb_1_0_la-darwin_usb.lo] Error 1
make[4]: *** [all-recursive] Error 1
make[3]: *** [all] Error 2
make[2]: *** [all-recursive] Error 1
Using gcc 4.8, but also tried earlier versions. I know there are pre-compiled Mac binaries around, but I would rather conquer this problem, obviously someone has. Any suggestions? |
|
|
|
|
Show Posts
