I want to make a collection of all the fake addresses OR all the addresses with "bad" information. (such as the previous one with a wrong zip code.)
Here are all the addresses I have from HashFast: HF address on my Aug 8 invoice: HashFast Technologies LLC
1060 Gilman
San Francisco, CA 94124
United States HF legally registered address /w incorrect zip: HashFast Technologies LLC
649 Mission St. 5th Floor
San Francisco, CA 90291
United States HF while @ Uniquify: HashFast Technologies LLC
2030 Fortune Dr.
San Jose, CA 95131-1835
United States HF while @ NextSpace San Jose: HashFast Technologies LLC
97 South Second Street #175
San Jose, CA 95113
United States HF while @ NextSpace San Francisco: HashFast Technologies LLC
365 Vermont Street
San Francisco, CA 94103
United States HF current location: HashFast Technologies LLC
100 Bush Street, Suite 650
San Francisco, CA 94104
United States
|
|
|
|
Meh, doom and gloom. Either way no matter how you slice it KNCMiner customers got and will get better treatment than HashLast customers. HashFast screwed it's batch1 and likely bath2 customers sans souci sans lube. They sure know we like it rough.  mais oui oui! Well at least there is one company doing right by their Customers. After the initial promises, HF has disappointed on every step along the way. I received my BJ 3 months late and even now it runs below spec (385GH/s) and unstable (have not been able to get it to run for 48h straight without needing hard RPi reboot/hotplugging). Funny thing is, my warranty has already expired. MPP seems to have been another empty promise. I sure they are hard at work trying to figure out a way to get around this commitment. While no hard dates were given regarding delivery, the ROI calculation example certainly implied that the MPP modules would ship out after the 90 day MPP window. A window that closed last month. The only good thing I can say about HF is Phil, and his forum support was not even part of his daily job. |
|
|
|
Came back from work today and noticed my BJ was dead again. *sigh* I needed to hard-reset the Pi and hot-plug the USB cable before it came back. Take a look at my mining graphs and tell me I have a stable system.. (This is at normal clock speed) I will give 3.11 another shot. Network provider is stable ? Dropped connection could spin it out - shutdown. Just a variable no one mentioned yet. DSL and wireless not so good for this stuff. When I went to TWarner to ask about this, they asked "what are you doing" I told them 900k up 1500k down 24/7 They said it was allowed and not over or excessive. Some will cut you off if they see to much constant traffic. I think my network connection is fine. I've been using another RPi minepeon setup with my 30 GH/s BFL little single since early July and never had any stability issues with it (apart from the SD card becoming corrupted every 3 months or so). In any case I switched to 3.11 as seems to be the most stable image for my BJ so far. Clearly the BJ hardware/firmware is still somewhat half baked. In a sense we are all overpaying alpha testers with a hardware warranty of 10 days.. Even BFL was nice enough to provide lifetime warranty on their products. |
|
|
|
Came back from work today and noticed my BJ was dead again. *sigh* I needed to hard-reset the Pi and hot-plug the USB cable before it came back. Take a look at my mining graphs and tell me I have a stable system.. (This is at normal clock speed) I will give 3.11 another shot. |
|
|
|
So what's going to happen with our Upgrades and MPP?
Good question. When it comes to MPP I don't think HF gave a 'guaranteed' delivery date. So likely they are prioritizing all batches with guaranteed delivery dates to avoid refunds and/or legal action from customers. In other words, HF does what is good for HF and the customer be damned. |
|
|
|
@Phil - Would it be possible to go back to 3.11? That is the only version that was stable for me. I know some folks complained about lower hashrates in minepeon (after halving the reported rate) but that is because ckolivas made some changes to discard invalid shares. 3.9 is causing full-tilt spikes again and also caused my RPi to crash completely. It also requires me to physically hot plug the miner to be detected... :/ https://i.imgur.com/d1P8FXR.png |
|
|
|
Last night I got the 3.12.0hf3 update and since then the miner mines for about an hour and then restarts. It's not a full RPI reboot, but cgminer crashes/quits then restarts. The cgminer restarts seem to be about every 75 minutes or so. I'm running stock clocks.
Since the automatic update I'm only getting about 350-370GH/s.
Same here. You can see how the hash rate graph changes after loading 3.12.0hf3. It becomes more erratic and the little dips appear to be miner restarts.  On the pool side the hashrate has remained roughly the same (slight dip) but my stale rate appears to have gone up significantly (more than doubled). MinePeon Version: 0.2.4.3hf7 Miner Version: cgminer3.12.0hf3 |
|
|
|
The firmware is still in massive flux. I discovered that a few devices were released with work-restarts disabled because of the power draw problems it had, leading to much higher rejects than usual, especially on good old p2pool. Fortunately this has been fixed in upcoming firmware, but the ability to flash these devices and the newer firmware is not yet available. Not surprisingly things are still unfinished in the quest to get the hardware out ASAP, which I'm sure the customers prefer provided it hashes stable... I'm currently working on better thermal control which will work with the newer firmware and hopefully it will all be out soon.
Thanks for your continued support ckolivas! I really hope HF is compensating you adequately for your efforts. |
|
|
|
the HFB comes with a one page manual "Welcome to your new Baby Jet" and a 3 (three) page "Cover our ass Limited Hardware Warranties" stating you are SOL when the hardware does not work as it's always your fault when it breaks. Now, this is funny. It's clear the lawyer has completely taken over any common sense Looks like so... Btw, have anyone ever noticed that one of the business address we have of HF is exactly the same as the lawyers' business address? HashFast Technologies LLC 649 Mission Street 5th Floor San Francisco, CA 90291Strategic Counsel Corp. 649 Mission Street, Fifth Floor San Francisco, CA 94105 Did anyone notice they [seemingly] intentionally used a fake Zip code for the address?  I can only assume they did not want any "official mail" coming to their inbox? Quick serve them in small claims court and then win on the default judgement. [just kidding!] Yes, I realized this when I sent them my refund request. See: https://bitcointalk.org/index.php?topic=262052.msg4378282#msg4378282You can actually see the receipt shows 'Venice CA' never realized it was LA until I got the "Undeliverable as Addressed" notification from USPS. I assume it was a mistake from HF. |
|
|
|
BTW, I'm doing this on my own, Supporting you guys is not in my job description, nor was I asked to by my bosses.
Phil, you are doing an awesome job. Everybody wants to get their miner running smoothly and understand what is going on. We know there are some issues to be worked out and that is totally ok. Hopefully, if we work together we get there sooner  |
|
|
|
When I try any clock speed above 600 I get: [2014-01-30 23:12:26] HFB 6 HFGetHeader usb read err:(-9) LIBUSB_ERROR_PIPE
[2014-01-30 23:12:26] HFB 6: device disappeared, disabling
[2014-01-30 23:12:26] HFB 6 failure, disabling!
[2014-01-30 23:12:34] Hotplug: Hashfast added HFB 7
Anyone seen this? Yes, it is a known issue. I don't think it is related to overclocking though as I get those errors at stock speed. Btw, my BJ hashrate chart on minepeon is starting to look pretty ridiculous now: https://i.imgur.com/0OM87Vl.pngBut the system does appear to be stable and the mining pool reports the correct hashrate: 383.55 Gh/s Temps have come down a lot too: HFB 1: 76C/.79V 76C/.79V 70C/.79V 71C/.80V 708.2G/740.7Gh/s | A:918350 R:1500 HW:3045 WU:10347.7/m |
|
|
|
I flipped the chassis fan to blow in and that lowered the die temperature by 2 degrees (80C > 78C). I'm still seeing a lot of USB errors though: [2014-01-30 18:55:53] HFB 0: Bad CRC 180 vs 213, discarding packet
[2014-01-30 18:55:53] HFB 0: Bad CRC 0 vs 241, discarding packet
[2014-01-30 18:55:53] HFB 0 HFGetHeader usb read err:(-9) LIBUSB_ERROR_PIPE
[2014-01-30 18:55:53] HFB 0: device disappeared, disabling
[2014-01-30 18:55:53] HFB 0 failure, disabling!
[2014-01-30 18:56:00] Hotplug: Hashfast added HFB 1
[2014-01-30 18:56:18] Accepted 82e4dc8d Diff 501/450 HFB 1 pool 0 [2014-01-30 19:08:04] HFB 1: Bad CRC 180 vs 213, discarding packet
[2014-01-30 19:08:04] HFB 1: Bad CRC 0 vs 241, discarding packet
[2014-01-30 19:08:05] HFB 1 HFGetHeader usb read err:(-9) LIBUSB_ERROR_PIPE
[2014-01-30 19:08:05] HFB 1: device disappeared, disabling
[2014-01-30 19:08:05] HFB 1 failure, disabling!
[2014-01-30 19:08:11] Hotplug: Hashfast added HFB 2
[2014-01-30 19:08:28] Accepted 0a3af57d Diff 6.41K/450 HFB 2 pool 0 I understand the USB errors are addressed in cgminer 3.12 so looking forward to that update rolling out to HF minepeons soon. The good news is that my BJ seems to recover well from these errors now, so I don't have huge gaps where mining stops altogether anymore. |
|
|
|
Also, we did have some early BabyJets escape the factory with the fans installed the wrong way. The top radiator fans should be blowing out (up) and the other chassis fans should be blowing in. You should be able to reverse them with a phillips screwdriver if you feel comfortable. This will help cooling.
Thanks Phil, really appreciate your support on this forum! It was sorely needed. Looks like one of the chassis fans (the one next to the board) was incorrectly installed in my case as it is blowing out. I'll try to reverse it to see if it helps cooling/stability. |
|
|
|
4 of my 12 BJ's had air blowing IN the radiator. The rest blowing out.
HF is certainly good at blowing hot air. |
|
|
|
Furthermore, there are extra screws
Those extra screws are there so you can go screw yourself. Consider it a gift from HF |
|
|
|
Rebooted my RPi today and it upgraded minepeon to: MinePeon Version: 0.2.4.3hf4
Miner Version: cgminer3.11.0hf1 Lets see if that fixes some of the stablility issues I've had over the past week. Happy to see HF frequently updating the software though! And of course kudos to ckolivas for doing most of the hard work Btw, this update seems to break the 'monitor' tab for me in minepeon... |
|
|
|
In my best guess HF will only do what BFL did at best and offer customers a discount on a new pre-order for a new product range. Like BFL did with the Monarch for their 65nm pre-order customers. Which they first promised for delivery last October and are now say late March delivery at the earliest IIRC If I remember correctly, BFL first jacked the prices of their miners by 100% and then gave pre-order customers a 25% discount voucher for future purchases to compensate for the delays. Also, the voucher would expire ~30 days after issuance... |
|
|
|
Has anyone been able to get out of HashFast the details of the MPP yet? Like.. when/what/where/how??
Mum's the word. Come on HF, the MPP ROI calculation window has ended for Batch 1 customers (with pitiful results due to the delays of the original hardware). Live up to your promises. A ROI calculation does not make sense if you send out the additional modules at some arbitrary date in the future. |
|
|
|
I'm experiencing a similar problem. What version of minepeon and cgminer are you using?
I'm using what HF shipped me: - MinePeon Version: MinePeon 0.2.4.3
- Miner Version: cgminer3.9.0h2
Once I find some free time I will try a different USB cable, upgrading to 3.11 and reflashing the SD card to see if any of these options help. |
|
|
|
Just happened again. Checking the cgminer logs this is the error I get: [2014-01-28 20:53:32] HFA 0: Bad work sequence tail
[2014-01-28 20:53:33] HFA 0 HFClearRead usb read err:(-9) LIBUSB_ERROR_PIPE
[2014-01-28 20:53:33] HFA 0 attempted reset got err:(-5) LIBUSB_ERROR_NOT_FOUND
[2014-01-28 20:53:38] Hotplug: Hashfast added HFA 1
In most cases I end up with two devices HFA 0 reporting some crazy TH figures, and a new HFA 1 device working correctly. In some cases HFA 1 does not appear and mining stops. |
|
|
|
|
Show Posts
