Show Posts
|
Pages: [1]
|
Happy to see that if I start posting with huge and colored text I'll have some answer....
Marto, still waiting for replacement, don't make me become blind in posting such messages for my situation (many mails on order reference LVMLEVBLF - 40 GH/s Full set Technobit S-hash 16 chip Bitfury based bitcoin miner)
THANK YOU
|
|
|
marto,
I think you have to give us a few answers. Escaping from it without facing all these problems will fuck your trustness here as a producer, as a vendor and as a person.
We gave you money, and me and my friends (I'm sure you have realized that I'm not alone here in running our rig) are not new to legal action against non-serious people, even international ones.
I don't want to start this kind of fight, and I'm sure all the others don't want it too, but you have to provide answers, refunds, and shipments FAST. This is one of the main forums on this stuff, screwing here means screwing your market.
I'm sure you're pretty smart to understand what we're all saying.
I'm still waiting for your replace product (as agreed), and related tracking code.
|
|
|
@marto74
still waiting for address confirmation (see pm). Can you send me the tracking code for the substituted device you've sent today?
thanks
hello?
|
|
|
@marto74
still waiting for address confirmation (see pm). Can you send me the tracking code for the substituted device you've sent today?
thanks
|
|
|
1 HEX16B will be fine. I have to ask if you can send the device concurrently with this I'm sending back, just to regain a couple of days.
I'll send all the related order information about the faulty one via pm or email.
Please let me know.
thank you again.
Monday ? Both sendings Deal. I'll send the shipping information and previous order information via pm and email too. Thanks
|
|
|
Ship it ASAP I do not have spare in stok SO I can send replacement hashing power insted 1 HEX16B or 2 HEX16A2
What do you think?
1 HEX16B will be fine. I have to ask if you can send the device concurrently with this I'm sending back, just to regain a couple of days. I'll send all the related order information about the faulty one via pm or email. Please let me know. thank you again.
|
|
|
@marto74
via teamspeak acidfox and me did a lot of tests with the s-hash 40 ghs, and the result is that it's not working at all. In the past posts you can see all the story. I've also unsoldered the fan and connected it directly in order to undestand if it was draining too many power from the device. I've also discovered that the device is making a strange sound, like a tiny crackling while powered on.
As said, it powers on, it connects to the pool it has a working webgui and a working console, but it's not warming up chips, and it's not mining.
As I've already sent back a nanofury (1 out of 9 to be honest) and I still have no news about it, I would like to know how to deal with this problem asap, since It has been a lot of time since the order and i would like to get rid quickly of this issue (and the other with the nanofury too) and start mining before the end of this year..
thank you
|
|
|
it has a static ip address. You can see, the log says it connects to the pool, gets the difficulty and the requests for mining.
Hi Lancelot, yes i see the miner was connect to any pool but then it was waiting for an ip. Maybe there is a problem with dns or your ip settings. If you want I can have a look at your miner per teamviewer. activated DHCP, same story PHY ID 20005c90 MAC 023d mac: 78-dd-d6-24-02-3d
S-HASH 9 switching to pool 0 initializing bitfury chip init 0 chip init 1 chip init 2 chip init 3 chip init 4 chip init 5 chip init 6 chip init 7 chip init 8 chis-hash > web server on port 80 miner waiting for IP address p init 9 chip init 10 chip init 11 chip init 12 chip init 13 chip init 14 chip init 15 init DHCP DHCP ready 1 Hostname shash023d.local Full duplex 100 Mbps dhcp: sending DHCPDISCOVER dhcp: address 192.168.10.110 mask 255.255.255.0 bcast 0.0.0.0 router 192.168.10.1 nameserver 192.168.10.1 Trying pool 0, server eu-stratum.btcguild.com:3333 as user lancelot6_1:123 Miner 192.168.10.110 connecting to server 54.246.170.18:3333 set difficulty 2 mining notify: job_id '19468' coinbase 234+86 ntime 1388934314 merkle 5 mining notify: job_id '19469' coinbase 234+86 ntime 1388934344 merkle 6 mining notify: job_id '19470' coinbase 234+86 ntime 1388934375 merkle 7 can't close() in state FIN-WAIT-2 mining notify: job_id '19471' coinbase 234+86 ntime 1388934403 merkle 5 PHY ID 20005c90 MAC 023d mac: 78-dd-d6-24-02-3d
S-HASH 9 switching to pool 0 initializing bitfury chip init 0 chip init 1 chip init 2 chip init 3 chip init 4 chip init 5 chip init 6 chip init 7 chip init 8 chis-hash > web server on port 80 miner waiting for IP address p init 9 chip init 10 chip init 11 chip init 12 chip init 13 chip init 14 chip init 15 init DHCP DHCP ready 1 Hostname shash023d.local Full duplex 100 Mbps dhcp: sending DHCPDISCOVER dhcp: address 192.168.10.110 mask 255.255.255.0 bcast 0.0.0.0 router 192.168.10.1 nameserver 192.168.10.1 Trying pool 0, server eu-stratum.btcguild.com:3333 as user lancelot6_1:123 Miner 192.168.10.110 connecting to server 54.246.170.18:3333
I guess we should declare it officially dead. @acidfox, if you have time for a look via teamviwer, I want to thank you in advance for the assistance
|
|
|
then it starts over from the beginning.
Any other idea accepted...
You have to activate DHCP or use a static IP. Easiest way is to use dchp. Type "dhcp on" in terminal, set your miner datas in the webinterface and report again please. it has a static ip address. You can see, the log says it connects to the pool, gets the difficulty and the requests for mining.
|
|
|
Yes i think its a problem of the current supply. Are you sure you have connected the cable right and didn't invert plus and minus? Inner terminal should be positiv and outer negativ. I hope the other 2 cables aren't (black, red) leaky!? Have you possibility to solder the 2 cables (yellow, black) from the 4 Pin-molex connector directly to the board?
I soldered the 2 cables directly on the board, paying attention to polarity. Song didn't change, here's what written on console (usb cable) set difficulty 512 mining notify: job_id '2bc700f5' coinbase 118+228 ntime 1388793564 merkle 10 set difficulty 20 mining notify: job_id '2bc700f6' coinbase 118+228 ntime 1388793594 merkle 10 mining notify: job_id '2bc700f7' coinbase 118+228 ntime 1388793596 merkle 7 can't close() in state FIN-WAIT-2 can't close() in state FIN-WAIT-2 mining notify: job_id '2bc700f8' coinbase 118+228 ntime 1388793654 merkle 8 mining notify: job_id '2bc700f9' coinbase 118+228 ntime 1388793684 merkle 8 mining notify: job_id '2bc700fa' coinbase 118+228 ntime 1388793714 merkle 8 PHY ID 20005c90 MAC 023d mac: 78-dd-d6-24-02-3d
S-HASH 9 switching to pool 0 initializing bitfury chip init 0 chip init 1 chip init 2 chip init 3 chip init 4 chip init 5 chip init 6 chip init 7 chip init 8 chis-hash > web server on port 80 miner waiting for IP address p init 9 chip init 10 chip init 11 chip init 12 chip init 13 chip init 14 chip init 15 init DHCP DHCP ready 0 Hostname shash023d.local Full duplex 100 Mbps then it starts over from the beginning. Any other idea accepted...
|
|
|
Yes i think its a problem of the current supply. Are you sure you have connected the cable right and didn't invert plus and minus? Inner terminal should be positiv and outer negativ. I hope the other 2 cables aren't (black, red) leaky!? Have you possibility to solder the 2 cables (yellow, black) from the 4 Pin-molex connector directly to the board?
the other 2 cables have been sealed with tape. Polarity should be ok (web interface ok, serial interface ok, air direction of fan correct). I would solder the 2 cables to the board directly, but only if this does not cause problems in sending it back, if after that we prove that it's faulty. marto74, what do you say?
|
|
|
Can you show us a pic of your connectors, please? Here they are: Are you thinking about a cable (lack of Ampere) issue? Of course, you can see all the wires from the molex going to the connection, but only one black and one yellow are forwarded to connector.
|
|
|
Just unpacked and connected. No modification at all. I'll test it with btcguild and report asap. thanks
Have your board an dc connector or an 4-Pin Molex connecter? Please post us also the data of your power supply. no luck with btcguild. Board has a dc connector, PSU is a thermaltake PurePower TWV480 (actually, 80 watt used) ( http://www.techtastic.ca/reviews3/twv480.html)
|
|
|
Can you test it with btcguild? Have you overlock the miner per pencil mod? If the miner got to high voltage it has the same effect.
Just unpacked and connected. No modification at all. I'll test it with btcguild and report asap. thanks
|
|
|
Hello all, still having problems with my s-hash. Already tried many configuration, already tried to upgrade the firmware from technobit (actually, version 0.1.10), already connected via usb to the console system for debugging. I can see it's connected to the pool, I can see notification like set difficulty 512 mining notify: job_id '23762d65' coinbase 118+180 ntime 1387628053 merkle 10 set difficulty 20 mining notify: job_id '23762d66' coinbase 118+180 ntime 1387628113 merkle 10 but graphs are not updating neither on webgui nor on pool side. Tried with: give-me-coins pool deepbit.net pool ghash.io pool and tried pointing it to a bfgminer process in order to make it work as a proxied device (on the same bfgminer 1 erupter blade and 2 Hashbuster Micro are currently running without any problems). Configured with and without passwords, duplicating and not duplicating the same pool. I really need help, before considering this devide faulty and send it back.. more information here: https://bitcointalk.org/index.php?topic=379768thank you
|
|
|
can a moderator move this topic to the right section? I'm sorry about the OT, but I was not allowed to post elsewhere, and time is money with such things @ Marto74 tried with: give-me-coins pool deepbit.net pool ghash.io pool and tried pointing it to a bfgminer process in order to make it work as a proxied device (on the same bfgminer 1 erupter blade and 2 Hashbuster Micro are currently running without any problems). Any advice? thanks
|
|
|
any other kind of tests I can do for confirming it's faulty?
thanks
|
|
|
Sounds like a hardware problem. Can you tell if all chips are getting hot ?
I can confirm that they're not getting hot.
|
|
|
Hello, probably OT but of course, I'm restricted here and cannot write elsewhere or pm anyone. I'm fighting with a bitfury s-hash device, which appears not wanting to do its job. Already tried many configuration, already tried to upgrade the firmware from technobit (actually, version 0.1.6), already connected via usb to the console system for debugging. I can see it's connected to the pool (tried different ones too), I can see notification like set difficulty 512 mining notify: job_id '23762d65' coinbase 118+180 ntime 1387628053 merkle 10 set difficulty 20 mining notify: job_id '23762d66' coinbase 118+180 ntime 1387628113 merkle 10 but graphs are not updating neither on webgui nor on pool side. I head about another firmware from c-scape, but didn't find any place to download from. Anyone wishing to help will be remembered in my prayers, as right now this device is a too expensive cooling fan.. thank you!
|
|
|
|