 Show Posts
|
|
Pages: [1] 2 3 »
|
|
Got my refund today, two weeks before the 61-day limit.
I'm happy with it, and even more happier that i dont need to read all your crappy shit talk flaming terror in this thread anymore.
Good luck everyone, bye.
|
|
|
|
ok ive been mining for a while on pools but want to try solo mine this on cgminer for the first time,
i know i need to make a .conf file and a .bat file linking to the .conf but can somebody give me an example of what the files would look like as i have been trying to mine another coin but cant seem to get it to work, also in the wallet options there is ip option and port, i turned it on and the ip in the conf. was the same as the wallet but there was no port(how do i know what port to use)
Just look here: http://www.stabilityshar.es/how%20to%20connect.html |
|
|
|
at lower voltage it will draw more amps for same performance
I think you are wrong. There is no DC/DC converter "inside" the chips  |
|
|
|
Ok, form has answered on that question. one more thing, if you connect fan to the board cut the yellow wire, it will reset PIC16LF1459 all the time. everything else is ok on that side.
@form what we need to change in the code for tach to working ? i have removed it from hardware completely, but it can be used for some alarm when the fan stop working or something like that ... is it big change or minor ? Thanks,
Thats an issue caused by non-standard fans, which actively outputs +12 volts on the tacho-output. The board is designed for normal CPU-fans (i think it was specified by intel), which have a passive open-collector output on the tacho-pin, which alternatevly connects this pin to GND and leave it open again. When a non-standard fan outputs +12 volts there, the PIC is entering high voltage programming mode, which is not intended to happen. So actually no way to avoid it via software, just cut the wire - The software doesnt take care of the RPM anyway. |
|
|
|
One last retarded question before I move to the chain. The fifth board is bothering me. What 2 points are you measuring to adjust voltage? TP1 to ground?
yes |
|
|
|
The firmware loaded fine but I can't get BFGminer to compile that driver. I think it's due to the .o file but I'm not sure how to fix that.
It seemed he used an older version of bfgminer. You can use the normal version and just change 2 lines: #define MAX_WORK_COUNT 8 #define LATE_UPDATE_MS ((int)(0.5 * 1000)) These changes did a good job for me. I never saw a duplicate/idle message anymore since that, even with the board-firmware from before. (Including a slightly higher hashrate) His new firmware for the board didnt work so well for me, the old one is faster at even lower frequencies, but i still have to debug it a little further... |
|
|
|
I'm going to post the firmware updates shortly. A question: what is the optimal way of posting the firmware updates? I could send it to the author of the original project to be incorporated in the github repository. The bfgminer software also has to be modified for operation at maximum speed.
Great work! I can merge your code into the github-repo, or giving you direct access to it. Can i just verify your work? Just send a PM with a link to an archive with your firmware and bfgminer-patch please. |
|
|
|
What must I do to make this board mining under cgminer? Please help me
Edit driver-klondike.c and set MAX_WORK_COUNT to 8, then compile again. |
|
|
|
|
One important thing i forgot:
The value of MAX_WORK_COUNT in klondike.h has to match the value in the driver of cg/bfgminer.
In the github-repository i set it to "8" everywhere.
So when you are using other non-patched mining software (bfgminer for example), be sure to change it to "8", too.
@cdragon: Why are you hashing at 500 MHz?
|
|
|
|
I don't know how to adjust clock.
You should add this to the parameters of cg/bfgminer: --klondike-options 1300:70 First number is frequency in MHz, second is desired temperature in °C. |
|
|
|
|
Did you used the .hex file from yesterday?
|
|
|
|
Thanks Form, u're you superb ! After adjustment I'm now getting 11 - 14 G ~ with almost no error , < 1%..  I'm getting alot of " went idle before work was sent" Yeah, i get these messages here, too - since months  Actually, changing TICK_TOTAL adjusts the timeout for one job. When the value is too big/small the result is many dupe/idle messages. I think 20800 is near the "golden mean". It doesnt affect the hashrate as much as one would think. I have updated the code (and the .hex) in the github-repo now, too. Can you tell something about your frequency and voltage settings? Are you cooling the chips from topside, too? |
|
|
|
|
try to adjust this value in klondike.h:
#define TICK_TOTAL 20800
|
|
|
|
After looking at the Avalon data sheet I don't see how to get the clock frequency above 999mhz and satisfy all 3 equations.
Were you able to decipher the data sheet and set the core clock frequency at 1000mhz or above.
If so what values did you use for F,R & OD.
Thanks for any help you can provide to understand this.
You can see what values are used, when you look at this function in the firmware: https://github.com/formtapez/avalon/blob/master/firmware/Klondike.X/klondike.c#L307The newest datasheet shows slightly other formulas, i didnt got it to work that way, still using the formulas from the older datasheet, works fine. |
|
|
|
I know that the driver for gen2 Avalon needs to subtract 0x180 from the returned nonce but are there any other changes?
There was a limitation (999 MHz) for the command-line parameter for the desired chip-frequency in some versions of cgminer - That has to be removed or changed to 5000 or so. Thats the only thing that has to be changed, additionaly to the 0x180 substraction (which BFGminer detects automatically). |
|
|
|
|
Looks like you dont used the patched cgminer version.
You can also use BFGminer, which includes automatic detection of this boards.
Btw (not the problem here): Did you changed the chipcount to 16 in the code? The precompiled one is for the 10 chips board.
|
|
|
|
If someone needs cheap power-modules (PTH12040WAH) send a message to Lucko. |
|
|
|
Data sheet of A3255Q48 does not show pin-assignments (DVDDx...) See picture on page 12 (of 15) in the mentioned pdf-file above.
Pin assigment is on pages 10, 11 and 12. Are you blind? |
|
|
|
|
