 Show Posts
|
|
Pages: [1] 2 3 4 5 6 »
|
Guys dont forget to vote on mintpal. Please take a min and send a twitt to mintpal https://twitter.com/MintPalExchangeasking them to add yin and yang this would be very helpful. I think if someone vote on mintpal.The dev can give him some coins as a reward. Then people will vote again.  This is just a suggestion.  I agree! |
|
|
|
Dear FairCoin community,
A lot of the active members here have probably seen my previous posts regarding projects for the better of the future of FairCoin. I plan to put them to reality. One of the more favorable and unique projects is the implementation of an emailing system into the wallet; and the wallet address acting as the email address! This will allow the transfer of messages, pictures, and videos straight through your FairCoin wallet, into another wallet. The receiver would be able to view the letter in an inbox section of the wallet. For this project, I will be working with numerous other new FairCoin developers with programming experience to provide this secure, reliable, unique, convenient, and innovative service for the FairCoin community. I would also like to thank the CinniCoin developer for providing the basis of this idea, from his coin.
In addition, I plan to implement daily financial analysis reports on the FairCoin price and projections of future value. Such analysis will involve the utilizing of simple methods such as the setting of the support, resistance, point of recovery, breakout, and consolidation. Different variations of analysis will be available too.
Overall, I personally want to expand the FairCoin community. That is why we very soon will have a new IRC chat room for all of us to hang out, a brand new website, a new video, and a Twitter account that constantly will be posting updates on FairCoin. Together, we will make the fair dream true.
More to come soon!
Kindest regards,
Adam Trat (Gladimor)
CEO, Shop Crypto
Community Manager, CinniCoin/FairCoin
Hello. I am a part of the Cinni Dev team, and the official Community Manager of CinniCoin. You are not a community manager of Cinni Coin. Please remove that misleading information from your post. Hello there, First off, here is the evidence of my placement as a community manager of CinniCoin My request to be on the team:  The developer's response:  If I am not mistaken, his two-word response to my short resume was a general acceptance into the CinniCoin development team. Upon my seating in the CinniCoin development team, I immediately made plans to create physical CinniCoins, create a video, and use social networking to spread the word of the arrival of a coin with unique innovations (eg; encrypted messaging). When I requested access to the CinniCoin Team twitter account, I was formally ignored, and later on rejected. In dismay, I moved off to creating the promised physical CinniCoins. I have access to a CNC machine, and CNC software. Not long ago I was finished designing the actual coin, but for some odd reason, I could not test the toolpath because the program could not communicate with the actual CNC machine. In the case of the video, I have spoken with a member of the CinniCoin community previously, which has experience with video making, to in the future work with me on creating the video. If you wish to speak to him in regards to this matter, his name is "Jenko" in the IRC chat room. While the entire dev team was working out in the open in front of all the community to see, I was in the back, ready to introduce physical variations of the coin; what many coins in the cryptocurrency community lack. There was just a minor error on behalf of the communication procedures between the program and the machine itself, which soon will be resolved. After reading the past few messages here, from developers of the CinniCoin team and the CinniCoin community, I was relatively astounded by the lack of recognition of my position in the CinniCoin team. I was even more taken aback when the CinniCoin developer himself agreed that I was not part of the effort. If this is the case, and my one week's worth of silence has removed my from the position of community manager, than so be it. Effective immediately, I will be removing all of my associations with CinniCoin, and my full focus shall fall upon FairCoin. I was not even able to do my main part as a community manager of CinniCoin due to being rejected from having access to official CinniCoin accounts in major social media (by WizFarm, or Batt). These are not petty excuses, but a reality. From now on, all of my efforts will be diverted to FairCoin. For those of you that don't believe that I will implement innovative functions, utilize social media on a super-frequent basis to spread word of FairCoin's revitalization and existence, or get major businesses to start accepting this coin, well... "Just watch me."
- Pierre Elliot Trudeau Kindest regards, Adam Trat ( Gladimor) CEO, Shop CryptoCommunity Manager, FairCoinso thats sorted, what about the multipool payout mentioned by jeromey? Can't you people understand that was controlled by the OLD DEV! The new team has nothing to do with it. Besides it was payed out as far as I know. |
|
|
|
The community wrote 150 pages (100pages old thread and 50 pages new thread) from the moment it proved what old dev made. There are only 4days! We would have now 10k sat for 1 AC. Let's do it all together now with full confidence to new Dev team!
Good idea |
|
|
|
I thought FAC was dead. It seems it back to life again today, let's see how it looks like tomorrow.
Me.too |
|
|
|
 so many waterB,so many shuazi it's funny, are you fucking kidding me?  you can you up, no zuo no die.  this guy... |
|
|
|
|
I just tried Ubuntu 13.10 + cgminer 4.2.1 and FW 0.4.
Die 4 just doesn't work. However I found out that it DOES work up to 150Mhz clock rate. After that, it's like it's not there, doesn't even get squelched.
|
|
|
|
Hashfast per die clock rate setting: I have noticed that in driver-hashfast.c, there seems to be adaptive clock rate setting per die: applog(LOG_INFO, "%s %d: Die temp below range %.1f, increasing die %d clock to %d",
hashfast->drv->name, hashfast->device_id, info->die_data[die].temp, die, hdd->hash_clock);
hfa_send_frame(hashfast, HF_USB_CMD(OP_WORK_RESTART), hdata, (uint8_t *)&diebit, 4); Is there a way to set per die clock from command line or conf file? Reason I'm asking is one of my dies seems to work fine up to 150MHz then it completely stops working and I would like to clock dies 0-2 with normal clock and underclock die 3. Edit: By the looks of your comments and the code it seems that per die clock setting will be possible for FW 0.5 and up. Do you already got FW 0.5 from hashfast by any chance? |
|
|
|
Well I tried all the miners with all the firmwares at pretty much any clock rate (even lower ones)
Your help is appreciated, I asked because if you had any indication that cgminer 4.2 on ubuntu 13.10 with FW 0.4 would solve my problem, I would try that again, to make sure I didn't miss something.
yup ! i tell you that cause one of my 9 bj's i had got a similar issue , and i can solve it in this way. bye bye windows, bye bye piece of shit raspberry pi , bye bye "hashfast special version of cgminer". hashfast: go to hell ! and Ckolivas: Thanx a lot man..  Big up to you! [/quote] So one of your babyjets had a full die (=96 cores) not working and by using u13.10, CGminer 4.2 and FW 0.4 you fixed that? Did you had to configure cgminer in any special way or did it just work with default settings? |
|
|
|
if you see sometime: 3 non working dies ( with a config a) , and then only one non working die with another config , that's not necessary mean you have a broken chip.... and if i ask , it's only to help you .... cheers.  . i already had some sick output on some of my miners, and squelching errors, but all is solved now. i hope you can find a solution to your problem. Well I tried all the miners with all the firmwares at pretty much any clock rate (even lower ones) Your help is appreciated, I asked because if you had any indication that cgminer 4.2 on ubuntu 13.10 with FW 0.4 would solve my problem, I would try that again, to make sure I didn't miss something. |
|
|
|
I installed the 0.4RC Hashfast sent me, but everything is like before: - still only 3 dies working. - CGMiner no longer working (Windows) I'm a sad panda  what clock rate are you running storm2k5 ? Tried them all, Megahurtz by Megahurtz Currently maxing it out at 687 cause I get the best perf with it and I gave up on Hashfast (multiple tickets open for replacement, no communication, thread on their forums, no communication) I just stopped giving a damn and hope karma will strike back on them some day. I solved the cgminer problem btw: Newer versions of cgminer on windows wont detect hashfast devices on USB3 ports. have you try to run your miner on ubuntu 13.10 , with cgminer 4.2.0 , and the last firmware? ( try to go back to 550 gh/s , and then if all seem ok , overclock again at 575 mhz. Yes I tried. Die 4 just doesn't do anything it seems. Why do you ask, do you know somebody with a non working die where this helped? |
|
|
|
I installed the 0.4RC Hashfast sent me, but everything is like before: - still only 3 dies working. - CGMiner no longer working (Windows) I'm a sad panda what clock rate are you running storm2k5 ? Tried them all, Megahurtz by Megahurtz Currently maxing it out at 687 cause I get the best perf with it and I gave up on Hashfast (multiple tickets open for replacement, no communication, thread on their forums, no communication) I just stopped giving a damn and hope karma will strike back on them some day. I solved the cgminer problem btw: Newer versions of cgminer on windows wont detect hashfast devices on USB3 ports. |
|
|
|
Ok that's suspicious of being plugged into a usb port that winusb doesn't recognise, such as a usb3 port. I suspect the earlier version of cgminer included a different libusb which probably did recognise it (though that libusbx is buggy in so many other ways which is why I dropped it). See if you have any usb2 ports anywhere or a usb2 hub to plug in and see if it's recognised. If it doesn't show up with cgminer.exe -n then it will never work.
W00t.....USB 2.0 port works! Thanks alot! I can confirm it worked on the USB3 port with earlier releases. |
|
|
|
No idea then. Heck hashfast weren't even looking for windows support from me, I just told them I could get it working on it as an afterthought. You're ALWAYS going to be better off mining with linux with cgminer but I might take a look at losedows soon to see if I can figure out what the problem is. What does it show with "cgminer.exe -n" ?
Yeah, I don't want to complain really. It's just the windows binaries/readme suggest hashfast devices will work with it and I wondered if maybe the problem is at my end. cgminer -n: [2014-03-19 10:46:24] USB all: found 6 devices - listing known devices
[2014-03-19 10:46:24] No known USB devices cgminer -D startup output (these PID's are all HID devices) [2014-03-19 10:45:11] Started cgminer 4.2.0
[2014-03-19 10:45:11] USB scan devices: checking for ICA devices
[2014-03-19 10:45:11] RES: thread starting
[2014-03-19 10:45:11] ICA looking for ICA 067b:2303 but found 8086:1c26 instead
[2014-03-19 10:45:11] ICA looking for AMU 10c4:ea60 but found 8086:1c26 instead
[2014-03-19 10:45:11] ICA looking for ANU 10c4:ea60 but found 8086:1c26 instead
[2014-03-19 10:45:11] ICA looking for BLT 0403:6001 but found 8086:1c26 instead
[2014-03-19 10:45:11] ICA looking for LLT 0403:6001 but found 8086:1c26 instead
[2014-03-19 10:45:11] ICA looking for CMR 0403:6014 but found 8086:1c26 instead
[2014-03-19 10:45:11] ICA looking for CMR 0403:8350 but found 8086:1c26 instead
[2014-03-19 10:45:11] ICA looking for ICA 067b:2303 but found 8086:1c2d instead
[2014-03-19 10:45:11] ICA looking for AMU 10c4:ea60 but found 8086:1c2d instead
[2014-03-19 10:45:11] ICA looking for ANU 10c4:ea60 but found 8086:1c2d instead
[2014-03-19 10:45:11] ICA looking for BLT 0403:6001 but found 8086:1c2d instead
[2014-03-19 10:45:11] ICA looking for LLT 0403:6001 but found 8086:1c2d instead
[2014-03-19 10:45:11] ICA looking for CMR 0403:6014 but found 8086:1c2d instead
[2014-03-19 10:45:11] ICA looking for CMR 0403:8350 but found 8086:1c2d instead
[2014-03-19 10:45:11] ICA looking for ICA 067b:2303 but found 046a:0107 instead
[2014-03-19 10:45:11] ICA looking for AMU 10c4:ea60 but found 046a:0107 instead
[2014-03-19 10:45:11] ICA looking for ANU 10c4:ea60 but found 046a:0107 instead
[2014-03-19 10:45:11] ICA looking for BLT 0403:6001 but found 046a:0107 instead
[2014-03-19 10:45:11] ICA looking for LLT 0403:6001 but found 046a:0107 instead
[2014-03-19 10:45:11] ICA looking for CMR 0403:6014 but found 046a:0107 instead
[2014-03-19 10:45:11] ICA looking for CMR 0403:8350 but found 046a:0107 instead
[2014-03-19 10:45:11] ICA looking for ICA 067b:2303 but found 046d:c05a instead
[2014-03-19 10:45:11] ICA looking for AMU 10c4:ea60 but found 046d:c05a instead
[2014-03-19 10:45:11] ICA looking for ANU 10c4:ea60 but found 046d:c05a instead
[2014-03-19 10:45:11] ICA looking for BLT 0403:6001 but found 046d:c05a instead
[2014-03-19 10:45:11] ICA looking for LLT 0403:6001 but found 046d:c05a instead
[2014-03-19 10:45:11] ICA looking for CMR 0403:6014 but found 046d:c05a instead
[2014-03-19 10:45:11] ICA looking for CMR 0403:8350 but found 046d:c05a instead
[2014-03-19 10:45:11] ICA looking for ICA 067b:2303 but found 8087:0024 instead
[2014-03-19 10:45:11] ICA looking for AMU 10c4:ea60 but found 8087:0024 instead
[2014-03-19 10:45:11] ICA looking for ANU 10c4:ea60 but found 8087:0024 instead
[2014-03-19 10:45:11] ICA looking for BLT 0403:6001 but found 8087:0024 instead
[2014-03-19 10:45:11] ICA looking for LLT 0403:6001 but found 8087:0024 instead
[2014-03-19 10:45:11] ICA looking for CMR 0403:6014 but found 8087:0024 instead
[2014-03-19 10:45:11] ICA looking for CMR 0403:8350 but found 8087:0024 instead
[2014-03-19 10:45:11] ICA looking for ICA 067b:2303 but found 8087:0024 instead
[2014-03-19 10:45:11] ICA looking for AMU 10c4:ea60 but found 8087:0024 instead
[2014-03-19 10:45:11] ICA looking for ANU 10c4:ea60 but found 8087:0024 instead
[2014-03-19 10:45:11] ICA looking for BLT 0403:6001 but found 8087:0024 instead
[2014-03-19 10:45:11] ICA looking for LLT 0403:6001 but found 8087:0024 instead
[2014-03-19 10:45:11] ICA looking for CMR 0403:6014 but found 8087:0024 instead
[2014-03-19 10:45:11] ICA looking for CMR 0403:8350 but found 8087:0024 instead
[2014-03-19 10:45:11] USB scan devices: checking for BAS devices
[2014-03-19 10:45:11] BAS looking for BAS 0403:6014 but found 8086:1c26 instead
[2014-03-19 10:45:11] BAS looking for BAS 0403:6014 but found 8086:1c2d instead
[2014-03-19 10:45:11] BAS looking for BAS 0403:6014 but found 046a:0107 instead
[2014-03-19 10:45:11] BAS looking for BAS 0403:6014 but found 046d:c05a instead
[2014-03-19 10:45:11] BAS looking for BAS 0403:6014 but found 8087:0024 instead
[2014-03-19 10:45:11] BAS looking for BAS 0403:6014 but found 8087:0024 instead
[2014-03-19 10:45:11] USB scan devices: checking for BF1 devices
[2014-03-19 10:45:12] BF1 looking for BF1 03eb:204b but found 8086:1c26 instead
[2014-03-19 10:45:12] BF1 looking for BXF 198c:b1f1 but found 8086:1c26 instead
[2014-03-19 10:45:12] BF1 looking for NF1 04d8:00de but found 8086:1c26 instead
[2014-03-19 10:45:12] BF1 looking for BXM 0403:6014 but found 8086:1c26 instead
[2014-03-19 10:45:12] BF1 looking for BF1 03eb:204b but found 8086:1c2d instead
[2014-03-19 10:45:12] BF1 looking for BXF 198c:b1f1 but found 8086:1c2d instead
[2014-03-19 10:45:12] BF1 looking for NF1 04d8:00de but found 8086:1c2d instead
[2014-03-19 10:45:12] BF1 looking for BXM 0403:6014 but found 8086:1c2d instead
[2014-03-19 10:45:12] BF1 looking for BF1 03eb:204b but found 046a:0107 instead
[2014-03-19 10:45:12] BF1 looking for BXF 198c:b1f1 but found 046a:0107 instead
[2014-03-19 10:45:12] BF1 looking for NF1 04d8:00de but found 046a:0107 instead
[2014-03-19 10:45:12] BF1 looking for BXM 0403:6014 but found 046a:0107 instead
[2014-03-19 10:45:12] BF1 looking for BF1 03eb:204b but found 046d:c05a instead
[2014-03-19 10:45:12] BF1 looking for BXF 198c:b1f1 but found 046d:c05a instead
[2014-03-19 10:45:12] BF1 looking for NF1 04d8:00de but found 046d:c05a instead
[2014-03-19 10:45:12] BF1 looking for BXM 0403:6014 but found 046d:c05a instead
[2014-03-19 10:45:12] BF1 looking for BF1 03eb:204b but found 8087:0024 instead
[2014-03-19 10:45:12] BF1 looking for BXF 198c:b1f1 but found 8087:0024 instead
[2014-03-19 10:45:12] BF1 looking for NF1 04d8:00de but found 8087:0024 instead
[2014-03-19 10:45:12] BF1 looking for BXM 0403:6014 but found 8087:0024 instead
[2014-03-19 10:45:12] BF1 looking for BF1 03eb:204b but found 8087:0024 instead
[2014-03-19 10:45:12] BF1 looking for BXF 198c:b1f1 but found 8087:0024 instead
[2014-03-19 10:45:12] BF1 looking for NF1 04d8:00de but found 8087:0024 instead
[2014-03-19 10:45:12] BF1 looking for BXM 0403:6014 but found 8087:0024 instead
[2014-03-19 10:45:12] USB scan devices: checking for CTA devices
[2014-03-19 10:45:12] CTA looking for CTA 1cbe:0003 but found 8086:1c26 instead
[2014-03-19 10:45:12] CTA looking for CTA 1cbe:0003 but found 8086:1c2d instead
[2014-03-19 10:45:12] CTA looking for CTA 1cbe:0003 but found 046a:0107 instead
[2014-03-19 10:45:12] CTA looking for CTA 1cbe:0003 but found 046d:c05a instead
[2014-03-19 10:45:12] CTA looking for CTA 1cbe:0003 but found 8087:0024 instead
[2014-03-19 10:45:12] CTA looking for CTA 1cbe:0003 but found 8087:0024 instead
[2014-03-19 10:45:12] USB scan devices: checking for HFA devices
[2014-03-19 10:45:12] HFA looking for HFA 297c:0001 but found 8086:1c26 instead
[2014-03-19 10:45:12] HFA looking for HFA 297c:0001 but found 8086:1c2d instead
[2014-03-19 10:45:12] HFA looking for HFA 297c:0001 but found 046a:0107 instead
[2014-03-19 10:45:12] HFA looking for HFA 297c:0001 but found 046d:c05a instead
[2014-03-19 10:45:12] HFA looking for HFA 297c:0001 but found 8087:0024 instead
[2014-03-19 10:45:12] HFA looking for HFA 297c:0001 but found 8087:0024 instead
[2014-03-19 10:45:12] USB scan devices: checking for KLN devices
[2014-03-19 10:45:12] KLN looking for KLN 04d8:f60a but found 8086:1c26 instead
[2014-03-19 10:45:12] KLN looking for KLI 04d8:f60a but found 8086:1c26 instead
[2014-03-19 10:45:12] KLN looking for KLN 04d8:f60a but found 8086:1c2d instead
[2014-03-19 10:45:12] KLN looking for KLI 04d8:f60a but found 8086:1c2d instead
[2014-03-19 10:45:12] KLN looking for KLN 04d8:f60a but found 046a:0107 instead
[2014-03-19 10:45:12] KLN looking for KLI 04d8:f60a but found 046a:0107 instead
[2014-03-19 10:45:12] KLN looking for KLN 04d8:f60a but found 046d:c05a instead
[2014-03-19 10:45:12] KLN looking for KLI 04d8:f60a but found 046d:c05a instead
[2014-03-19 10:45:12] KLN looking for KLN 04d8:f60a but found 8087:0024 instead
[2014-03-19 10:45:12] KLN looking for KLI 04d8:f60a but found 8087:0024 instead
[2014-03-19 10:45:12] KLN looking for KLN 04d8:f60a but found 8087:0024 instead
[2014-03-19 10:45:12] KLN looking for KLI 04d8:f60a but found 8087:0024 instead
[2014-03-19 10:45:12] USB scan devices: checking for DRB devices
[2014-03-19 10:45:12] DRB looking for DRB 03eb:2404 but found 8086:1c26 instead
[2014-03-19 10:45:12] DRB looking for DRB 03eb:2404 but found 8086:1c2d instead
[2014-03-19 10:45:12] DRB looking for DRB 03eb:2404 but found 046a:0107 instead
[2014-03-19 10:45:12] DRB looking for DRB 03eb:2404 but found 046d:c05a instead
[2014-03-19 10:45:12] DRB looking for DRB 03eb:2404 but found 8087:0024 instead
[2014-03-19 10:45:12] DRB looking for DRB 03eb:2404 but found 8087:0024 instead
[2014-03-19 10:45:12] USB scan devices: checking for AVA devices
[2014-03-19 10:45:13] AVA looking for BTB 0403:6001 but found 8086:1c26 instead
[2014-03-19 10:45:13] AVA looking for BBF 0403:6001 but found 8086:1c26 instead
[2014-03-19 10:45:13] AVA looking for AVA 0403:6001 but found 8086:1c26 instead
[2014-03-19 10:45:13] AVA looking for BTB 0403:6001 but found 8086:1c2d instead
[2014-03-19 10:45:13] AVA looking for BBF 0403:6001 but found 8086:1c2d instead
[2014-03-19 10:45:13] AVA looking for AVA 0403:6001 but found 8086:1c2d instead
[2014-03-19 10:45:13] AVA looking for BTB 0403:6001 but found 046a:0107 instead
[2014-03-19 10:45:13] AVA looking for BBF 0403:6001 but found 046a:0107 instead
[2014-03-19 10:45:13] AVA looking for AVA 0403:6001 but found 046a:0107 instead
[2014-03-19 10:45:13] AVA looking for BTB 0403:6001 but found 046d:c05a instead
[2014-03-19 10:45:13] AVA looking for BBF 0403:6001 but found 046d:c05a instead
[2014-03-19 10:45:13] AVA looking for AVA 0403:6001 but found 046d:c05a instead
[2014-03-19 10:45:13] AVA looking for BTB 0403:6001 but found 8087:0024 instead
[2014-03-19 10:45:13] AVA looking for BBF 0403:6001 but found 8087:0024 instead
[2014-03-19 10:45:13] AVA looking for AVA 0403:6001 but found 8087:0024 instead
[2014-03-19 10:45:13] AVA looking for BTB 0403:6001 but found 8087:0024 instead
[2014-03-19 10:45:13] AVA looking for BBF 0403:6001 but found 8087:0024 instead
[2014-03-19 10:45:13] AVA looking for AVA 0403:6001 but found 8087:0024 instead
[2014-03-19 10:45:13] No devices detected!
[2014-03-19 10:45:13] Waiting for USB hotplug devices or press q to quit
[2014-03-19 10:45:13] Need to specify at least one pool server.
[2014-03-19 10:45:17] Shutdown signal received.
I can confirm the HF device is there, WinUSB installed, PID is correct in device manager. |
|
|
|
@ckolivas: Are there known issues with the newer CG miner versions with Hashfast devices on Windows(tm) or has anything changed prerequisite wise? I been trying all the cgminer releases since ~4.0 (The hashfast firmware update releases) and none of them works on windows. No devices detected. Only seems to show HID PID's in debug log. No problems whatsoever on Linux though There are no known problems on windows, but then I have not tried running any hashfast devices on windows since my very first release. You did the WinUSB driver dance with zadig? Yes I did the moonwalk with Zadig, and earlier releases of cgminer worked well with it! |
|
|
|
@ckolivas: Are there known issues with the newer CG miner versions with Hashfast devices on Windows(tm) or has anything changed prerequisite wise? I been trying all the cgminer releases since ~4.0 (The hashfast firmware update releases) and none of them works on windows. No devices detected. Only seems to show HID PID's in debug log. No problems whatsoever on Linux though |
|
|
|
I created a user there, but apparently users can't post / reply / do anything there (?) |
|
|
|
|
Amy, is there anything in the works firmware wise that fixes non-working dies?
|
|
|
|
|
@ckolivas: Since I upgraded the firmware to 0.4RC (from you) and 0.4RCx (from Hashfast) cgminer (all versions, didn't try 4.01 yet) can't see my babyjet anymore (I'm on Windows 7)
Is this a known problem with cgminer on Windows or should it work / am I doing it wrong?
Edit: I just tried 4.01 with Ubuntu 64, worked right from the start.
@To all the people hoping for firmware miracles: Both firmware releases didn't fix anything for me, in fact it hashes a little bit slower with the new F/W. Overclockability seems the same. IMO, if your BJ is hashing ok & is more or less stable, you should wait for the official release from HF.
|
|
|
|
Hi BFG pros I have a problem with my Hashfast Babyjet, it's 4th die isn't working. I was wondering if someone could maybe make sense out of this and tell me what might be going on: [2014-02-27 14:29:50] HFA 0: STATUS from chipaddr=0x03 with hdata=0x5e07 (isn=0x2f4): total=96 uptodate=96 active=0 pending=0 transitioned=96
[2014-02-27 14:29:50] HFA 0: STATUS from chipaddr=0x02 with hdata=0x5e02 (isn=0xbc): total=96 uptodate=96 active=94 pending=94 transitioned=2
[2014-02-27 14:29:50] HFA 0: STATUS from chipaddr=0x01 with hdata=0x5e02 (isn=0xbe): total=96 uptodate=96 active=95 pending=95 transitioned=1
[2014-02-27 14:29:50] HFA 0: STATUS from chipaddr=0x00 with hdata=0x5e02 (isn=0xbe): total=96 uptodate=96 active=95 pending=65 transitioned=31 I notice the different hdata and isn values for my 4th die. As the newest 0.4RC firmware from hashfast didn't fix this I'm wondering if maybe there is something that could be done in BFGMiner to solve this problem? If I look at the "dead" cores in BFGMiner, they show as enabled, 0ghps hash rate (not in RST state) I can disable and enable them, but they just sit at 0ghps. |
|
|
|
|
