HashFast Sierra's Owners Thread - page 9.

kevin911

member

Activity: 87

Merit: 10

this is from a different thread :-

Quote from: perezoso on March 17, 2014, 10:28:02 PM

Quote from: Beans on March 17, 2014, 09:09:26 PM

Quote from: kevin911 on March 17, 2014, 06:24:53 PM

Has anyone else with a higher order than 2211 received their order yet or some notification that is even being dispatched?
this isn't a rhetorical question, i'm actually asking all members reading this if they can throw some light on this subject and let us know whats going on as hashfast is giving us nothing. we need to work together here.

They don't even return my emails.

I have an order about 100 below that (21XX). Nothing shipped. No notifications whatsoever.

so much for them following the order chain.
how come winit got his/hers first?

winit

newbie

Activity: 45

Merit: 0

Quote from: HashFast_CL on March 17, 2014, 04:59:06 AM

Quote from: winit on March 17, 2014, 04:33:26 AM

Please detail what I should disconnect to isolate a single board to try and determine which is giving me the LIBUSB error.

Nearly a week has passed and not one response to my emails to hashfast regarding my faulty units.

Use the latest cgminer and firmware. Run at 550Mhz when troubleshooting.

Take pictures of the original config before you change anything so you can put it back.

The ribbon cable is used to link the chain.

Disconnect all the ribbon cables to isolate a board.

Use two PCIE power cables from the same PSU for an isolated board.

Connect the power cable (white connector) from the board to its PSU, if it is not already.

Connect the USB cable (black connector) to the board, but make sure the thick black wire is closest to the ASIC (red wire farthest from ASIC).

Try running the boards in pairs (sets of two). If that works, add the third back in. Some boards don't like to the be the master (first board in chain) so try boards in different orders.

Can you provide a step by step guide to isolating a board because I dont want to start taking this expensive machine apart to end up being told that it was my fault it now doesnt work.

1 machine simply throws the LIBUSB error from startup the other runs for a minute and then throws 'No valid hashes for 22 seconds, shutting down thread.

Both are running the latest frimware and CGminer

Two very expensive machines not working for a week and no response to my emails. I appreciate you have responded here but to be honest expect much more from you. These machines should be on their way back to you to be replaced.

bkminer

full member

Activity: 216

Merit: 100

Don't let the nam-shub in your operating system.

My question to HashFast_CL is, will Batch 3 Sierra customers ever see their Sierras? By May 31st? June 31st? I'm doubting that it will be March 31st because I haven't even gotten the address confirmation email....

winit

newbie

Activity: 45

Merit: 0

Quote from: HashFast_CL on March 17, 2014, 04:59:06 AM

Quote from: winit on March 17, 2014, 04:33:26 AM

Please detail what I should disconnect to isolate a single board to try and determine which is giving me the LIBUSB error.

Nearly a week has passed and not one response to my emails to hashfast regarding my faulty units.

Use the latest cgminer and firmware. Run at 550Mhz when troubleshooting.

Take pictures of the original config before you change anything so you can put it back.

The ribbon cable is used to link the chain.

Disconnect all the ribbon cables to isolate a board.

Use two PCIE power cables from the same PSU for an isolated board.

Connect the power cable (white connector) from the board to its PSU, if it is not already.

Connect the USB cable (black connector) to the board, but make sure the thick black wire is closest to the ASIC (red wire farthest from ASIC).

Try running the boards in pairs (sets of two). If that works, add the third back in. Some boards don't like to the be the master (first board in chain) so try boards in different orders.

Thanks for the response, any chance of having an email response to my tech support emails regarding my dead machines. Your auto reply claims reply within 1 business day... I count 4 with no reply... simply adding to the damages you have caused being several months late in delivering my order.

CryptKeeper

legendary

Activity: 2044

Merit: 1055

Quote from: kevin911 on March 17, 2014, 06:22:14 PM

Quote from: bkminer on March 16, 2014, 11:01:22 AM

It seems HashFast has stopped shipping all together.... and I don't think they're processing "refunds" for people who paid in USD.

they seem to have processed some orders, winit was order 2211 but yet he's got his, i'm order 2434 & still waiting for mine.
Has anyone else with a higher order than 2211 received their order yet or some notification that is even being dispatched?
this isn't a rhetorical question, i'm actually asking all members reading this if they can throw some light on this subject and let us know whats going on as hashfast is giving us nothing. we need to work together here.

I have order 23xx and I am also still waiting...

kevin911

member

Activity: 87

Merit: 10

Quote from: bkminer on March 16, 2014, 11:01:22 AM

It seems HashFast has stopped shipping all together.... and I don't think they're processing "refunds" for people who paid in USD.

they seem to have processed some orders, winit was order 2211 but yet he's got his, i'm order 2434 & still waiting for mine.
Has anyone else with a higher order than 2211 received their order yet or some notification that is even being dispatched?
this isn't a rhetorical question, i'm actually asking all members reading this if they can throw some light on this subject and let us know whats going on as hashfast is giving us nothing. we need to work together here.

HashFast_CL

full member

Activity: 168

Merit: 100

HashFast Community Liaison

Quote from: winit on March 17, 2014, 04:33:26 AM

Please detail what I should disconnect to isolate a single board to try and determine which is giving me the LIBUSB error.

Nearly a week has passed and not one response to my emails to hashfast regarding my faulty units.

Use the latest cgminer and firmware. Run at 550Mhz when troubleshooting.

Take pictures of the original config before you change anything so you can put it back.

The ribbon cable is used to link the chain.

Disconnect all the ribbon cables to isolate a board.

Use two PCIE power cables from the same PSU for an isolated board.

Connect the power cable (white connector) from the board to its PSU, if it is not already.

Connect the USB cable (black connector) to the board, but make sure the thick black wire is closest to the ASIC (red wire farthest from ASIC).

Try running the boards in pairs (sets of two). If that works, add the third back in. Some boards don't like to the be the master (first board in chain) so try boards in different orders.

winit

newbie

Activity: 45

Merit: 0

Please detail what I should disconnect to isolate a single board to try and determine which is giving me the LIBUSB error.

Nearly a week has passed and not one response to my emails to hashfast regarding my faulty units.

aasl

sr. member

Activity: 476

Merit: 250

Quote from: HashFast_CL on March 13, 2014, 03:16:22 AM

Quote from: aasl on March 12, 2014, 09:34:41 PM

shouldn't hf test the devices before shipping? the fault rate seems so high! and I wonder how long the RMA takes?

We do test the devices before shipping. But vendor implementation of the USB spec varies. If your laptop doesn't work, try your desktop.

A high quality PCIE/PCI USB adapter often helps.

If the boards are having trouble running in a chain, try running one or two independently and isolating the problematic board on its own USB and cgminer instance.

Always use the latest firmware (0.4) and cgminer (4.1.0).

Wow! Thanks for the official reply!

bkminer

full member

Activity: 216

Merit: 100

Don't let the nam-shub in your operating system.

It seems HashFast has stopped shipping all together.... and I don't think they're processing "refunds" for people who paid in USD.

kevin911

member

Activity: 87

Merit: 10

anyone else from batch 2 received their sierra order yet?

winit

newbie

Activity: 45

Merit: 0

Finally updated the firmware on all machines, looking a tiny bit more powerful than before.

The unit which wouldn't power is now fine.

The unit with the LIBUSB error is still the same after firmware upgrade so looks like that machine isnt going to play ball at all.

I took the lid off and see that the board revision is 1.0 where as the other machine is 1.2.

I've no idea what to unplug / leave plugged to test each board individually.

winit

newbie

Activity: 45

Merit: 0

I opened up the case on the non powering machine and found that the yellow / black connector on the top board was not seated, in fact it's retaining clip was pushed into the top of the neighbouring cap with a dent.

I have managed to seat it correctly but a little concerned about powering it if the cap is damaged?

winit

newbie

Activity: 45

Merit: 0

Well so far 6 emails across 48 hrs to HF and not one reply so RMA is looking like taking a while.

Phoning tech support just gets a 'We're not able to take your call right now'

HashFast_CL

full member

Activity: 168

Merit: 100

HashFast Community Liaison

Quote from: aasl on March 12, 2014, 09:34:41 PM

shouldn't hf test the devices before shipping? the fault rate seems so high! and I wonder how long the RMA takes?

We do test the devices before shipping. But vendor implementation of the USB spec varies. If your laptop doesn't work, try your desktop.

A high quality PCIE/PCI USB adapter often helps.

If the boards are having trouble running in a chain, try running one or two independently and isolating the problematic board on its own USB and cgminer instance.

Always use the latest firmware (0.4) and cgminer (4.1.0).

aasl

sr. member

Activity: 476

Merit: 250

shouldn't hf test the devices before shipping? the fault rate seems so high! and I wonder how long the RMA takes?

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: winit on March 12, 2014, 05:48:07 PM

Hey Thanks CK... I'll see about updating my Ubuntu tomorrow and see if I have any joy there.

Do you think the firmware will resolve the machine with the LIBSUB error?

Doubt it. From what I've seen of the devices out there, some have unfixable problems and need to be RMAd.

winit

newbie

Activity: 45

Merit: 0

Hey Thanks CK... I'll see about updating my Ubuntu tomorrow and see if I have any joy there.

Do you think the firmware will resolve the machine with the LIBSUB error?

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: winit on March 12, 2014, 04:05:06 PM

Losing the will to live here. Having gone through the ballache of installing Ubuntu in order to update the firmware, in trying to update all I get back is this

Code:

Reading serial number from module.
x86_64/readserial: symbol lookup error: x86_64/readserial: undefined symbol: libusb_strerror

Same response for a machine that works and the machine that has the LIBUSB error.

So now what?

Looks like you're on an older ubuntu. For whatever reason, hashfast's loader is not that portable and looks like it needs a recent ubuntu, probably 13.10

winit

newbie

Activity: 45

Merit: 0

Losing the will to live here. Having gone through the ballache of installing Ubuntu in order to update the firmware, in trying to update all I get back is this

('confirm is ', False)
('FIRMWARE_DIR is ', '.')
UC_HFU_FILE at './uc3.cropped.hfu'.
READSERIAL found at 'x86_64/readserial'.
HFUPDATE found at 'x86_64/hfupdate'.
ENTERLOADER found at 'x86_64/enterloader'.

HashFast Firmware Updater

Reading serial number from module.
x86_64/readserial: symbol lookup error: x86_64/readserial: undefined symbol: libusb_strerror
Entering Boot Loader...
x86_64/enterloader: symbol lookup error: x86_64/enterloader: undefined symbol: libusb_strerror
Traceback (most recent call last):
File "./field_firmware_update.py", line 184, in
firmware_updater()
File "./field_firmware_update.py", line 143, in firmware_updater
enterloader()
File "./field_firmware_update.py", line 62, in enterloader
subprocess.check_call([ENTERLOADER])
File "/usr/lib/python2.7/subprocess.py", line 511, in check_call
raise CalledProcessError(retcode, cmd)
CalledProcessError: Command '['x86_64/enterloader']' returned non-zero exit status 127
Command '['x86_64/enterloader']' returned non-zero exit status 127
Firmware Update had an error. Please retry or report to HashFast Support.

Same response for a machine that works and the machine that has the LIBUSB error.

So now what?

Topic: HashFast Sierra's Owners Thread - page 9. (Read 23819 times)