So with the oncoming ASIC tsunami, which coins should be the best bet for small miners with USB miners and Jally
|
|
|
The firmware tests the engine (and chip if you have multiple chips) performance at startup and adjusts the speed accordingly based on how "correct" the answers are from each engine. It is not unusual for the existing Jals out there to be somewhere between 27 and 30 units when run at the higher speeds. 30 is the most that can be activated on 2+ chip units. When run at their lowest speed as 5GH units, most of the engines seem to work making all 30 start at 189MHz ~5.7GH. I posted firmware which relaxes the test dramatically making it far more likely to activate all 30 engines at speed setting "7" which is 274MHz, so 30 engines at 274 ~8.2 GH. I can't comment on the binned versus unbinned policy for chips by BFL but it looks like earlier units were unbinned making them potentially full speed, while later ones were chosen to reach the guaranteed speed as a minimum.
Unfortunately some of the hardware errors are currently counted towards the hashrate so you cannot simply look at the hashrate and determine whether you're creating all good work. I'm planning on rectifying that next cgminer version.
Can you be so kind to please post the code to the modified firmware, since I want to test my Jally at speeds "9" and using all engines.
|
|
|
If you order today, most likely you will get it in Dec or Jan 2014. ONLY IF BFL maintains its production at current speed... I ordered another 4 Jala after i got my first 2. Kinda predict it will reach at Dec 2013. *fingers crossing*
Is there no way BFL can pull up its socks and increase production rates?
|
|
|
Eventually someone will bring up this topic, so why not just start here... If AsicMiner will add 800-1000TH to mining, then the individual's small machines will be useless. https://bitcointalk.org/index.php?topic=247168.msg2622243#msg2622243When this happens, will anyone think it is justifiable to block mining power from China? Will this cause too much collateral damage since there are so many individual miners in China as well? If it is justifiable, then how to do it technically or what is the process to seek consensus? Hold on cowboy, let's get an open-source, crowd sourced, asic developed instead, and convince intel or glofo to manufacture it for us. I donot see any other means to stop the AM tsunami.
|
|
|
NOTE Re: Enermax 850W PSU that comes with some avalon batch 2.
I upgraded to a larger PSU while trying to troubleshoot some problems, it did not seem to be the problem, but I left the larger PSU in the avalon and thought I could use the 850W Enermax to power a small 2X7970 system... connect the 24 pin to the MB, connect one of each 7970 to the PCIe plugs, good to go, right?
It powered up just fine, but got no OS loaded error... doh! forgot to plug in the HDD... no big.
so then I pluged in the HDD to one of the 6 pin connectors on the PSU, no boot, no power on, no nothing... I tried a couple other of the 6 pin connectors, first one, same thing, second one, the system would power up, but I still get no OS error... boot into bios, no HDD detected... weird.
So then I thought I'd try another HDD, maybe that one died in the 1 week that it's been disconnected?
Bad move.
Sparks and then FLAMES started shooting out of the HDD. I kinda freaked/zoned out so it took me a few seconds to pull the plug.
Has anyone else tried to use the Enermax 850W with the chinese writing for a normal computer? Is it possible these PSUs are wired differently? I thought it was a standard ATX? maybe I just had 2 bad HDD in a row? (not willing to risk a third) How long 'till my apartment no longer smells like blue smoke?
I would get a voltmeter and check the psu voltage output.
|
|
|
Most of them will be overloaded by hardware errors at speed 9. Most peoples' Jals will work best at 7 or 8.
So does the average hashrate reported by cgminer considers hw error or do we have to account for hw errors by some other method?
|
|
|
I don't understand why I see so many people happy about this? That scares the hell out of me. Not even BFL MiniRigs or KNC will be able to compete. You'd have to buy a crap load of Jupiters and then ASICMiner will just bring another 2-5PH online quickly early next year at this rate.
I dunno, I'm just not too happy about it. I was hoping we'd see a couple generation of ASIC's go by before bringing the network that large. Nobody will be able to make much of anything except for a small select few.
Maybe I am calculating something wrong and don't understand their investment strategy. Seems very piggish. Managing your own hardware looks like it will quickly take a back seat into letting the Chinese do it all for you.
Fucking BFL...move your ass.
+1
|
|
|
i dunno, it'd depend where you ordered it from i guess, since you dont specify
order one from a reputable (re)seller on ebay and it'd just be a few days probably
okay, corrected. It's from BFL for USD 308 ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
Just wanted to see if it would make sense to order that Jally from BFL website for USD 308 soon.
Ordered the 25 GH/s Bitcoin Miner BF0025G for $1,283.00, since it probably will use the same board(s) as the Jalapeņo, and a bunch of Jallys did ship a while back.
|
|
|
great thanks! used the python api-example.py code.
python api-example.py stats
{u'STATUS': [{u'STATUS': u'S' u'Msg': u'CGMiner stats' u'Code': 70 u'When': 1372553376 u'Description': u'cgminer 3.3.1'}] u'STATS': [{u'Temp2 Max Time': 1372553345 u'Temp1 Max': 33.0 u'Min': 99999999.0 u'Que Watermark': 32 u'Driver': 2 u'Firmware': u'1.2.5' u'Flush ID': 0 u'Scan Sleep': 891 u'Results Sleep': 100 u'Que Full': 36 u'Overheat': False u'Work Queued': 37 u'Max': 0.0 u'Result ID': 251 u'Vmain': 12.398 u'USB Pipe': u'0' u'Elapsed': 204 u'Vcc1': 3.846 u'Vcc2': 0.993 u'Flushed': False u'Chips': u'(null)' u'Wait': 0.0 u'Que Low': 8 u'STATS': 0 u'Calls': 0 u'Que Size': 40 u'Work Complete': 420 u'Temp1 Max Time': 1372553224 u'ID': u'BAJ0' u'Work ms': 954 u'Temp2 Max': 45.0 u'Temp2': 42.81 u'Temp1': 32.41 u'GetInfo': u'DEVICE: BitFORCE SC0x0aFIRMWARE: 1.2.50x0aIAR Executed: NO0x0aCHIP PARALLELIZATION: YES @ 20x0aQUEUE DEPTH:400x0aPROCESSOR 3: 15 engines @ 319 MHz -- MAP: FFFE0x0aPROCESSOR 7: 13 engines @ 326 MHz -- MAP: F5FE0x0aTHEORETICAL MAX: 9023 MH/s0x0aENGINES: 280x0aFREQUENCY: 291 MHz0x0aXLINK MODE: MASTER0x0aCRITICAL TEMPERATURE: 00x0aXLINK PRESENT: NO0x0aOK0x0a0x00'} {u'Temp2 Max Time': 1372553347 u'Temp1 Max': 31.0 u'Min': 99999999.0 u'Que Watermark': 32 u'Driver': 2 u'Firmware': u'1.2.5' u'Flush ID': 0 u'Scan Sleep': 913 u'Results Sleep': 100 u'Que Full': 36 u'Overheat': False u'Work Queued': 37 u'Max': 0.0 u'Result ID': 249 u'Vmain': 12.097 u'USB Pipe': u'0' u'Elapsed': 204 u'Vcc1': 3.404 u'Vcc2': 0.987 u'Flushed': False u'Chips': u'(null)' u'Wait': 0.0 u'Que Low': 8 u'STATS': 1 u'Calls': 0 u'Que Size': 40 u'Work Complete': 372 u'Temp1 Max Time': 1372553328 u'ID': u'BAJ1' u'Work ms': 954 u'Temp2 Max': 43.0 u'Temp2': 40.98 u'Temp1': 30.11 u'GetInfo': u'DEVICE: BitFORCE SC0x0aFIRMWARE: 1.2.50x0aIAR Executed: NO0x0aCHIP PARALLELIZATION: YES @ 20x0aQUEUE DEPTH:400x0aPROCESSOR 3: 13 engines @ 286 MHz -- MAP: FFE60x0aPROCESSOR 7: 15 engines @ 284 MHz -- MAP: FFFE0x0aTHEORETICAL MAX: 7978 MH/s0x0aENGINES: 280x0aFREQUENCY: 291 MHz0x0aXLINK MODE: MASTER0x0aCRITICAL TEMPERATURE: 00x0aXLINK PRESENT: NO0x0aOK0x0a0x00'} {u'Min': 99999999.0 u'Work Roll Time': 0 u'Work Can Roll': False u'Work Diff': 10.0 u'Net Bytes Recv': 17219 u'Times Recv': 271 u'Times Sent': 263 u'Max': 0.0 u'Elapsed': 204 u'Pool Min': 99999999.0 u'Min Diff': 1.0 u'Work Had Expire': False u'Wait': 0.0 u'STATS': 2 u'Calls': 0 u'Bytes Sent': 30881 u'Pool Max': 0.0 u'Max Diff': 11.0 u'ID': u'POOL0' u'Work Had Roll Time': False u'Pool Calls': 0 u'Net Bytes Sent': 31610 u'Pool Av': 0.0 u'Bytes Recv': 17219 u'Max Diff Count': 443 u'Pool Attempts': 0 u'Pool Wait': 0.0 u'Min Diff Count': 219} {u'Min': 99999999.0 u'Work Roll Time': 0 u'Work Can Roll': False u'Work Diff': 1.0 u'Net Bytes Recv': 124376 u'Times Recv': 2 u'Times Sent': 2 u'Max': 0.0 u'Elapsed': 204 u'Pool Min': 99999999.0 u'Min Diff': 1.0 u'Work Had Expire': False u'Wait': 0.0 u'STATS': 3 u'Calls': 0 u'Bytes Sent': 232 u'Pool Max': 0.0 u'Max Diff': 1.0 u'ID': u'POOL1' u'Work Had Roll Time': False u'Pool Calls': 0 u'Net Bytes Sent': 1236 u'Pool Av': 0.0 u'Bytes Recv': 123936 u'Max Diff Count': 1 u'Pool Attempts': 0 u'Pool Wait': 0.0 u'Min Diff Count': 1} {u'Min': 99999999.0 u'Work Roll Time': 0 u'Work Can Roll': False u'Work Diff': 1.0 u'Net Bytes Recv': 1989 u'Times Recv': 3 u'Times Sent': 3 u'Max': 0.0 u'Elapsed': 204 u'Pool Min': 99999999.0 u'Min Diff': 1.0 u'Work Had Expire': False u'Wait': 0.0 u'STATS': 4 u'Calls': 0 u'Bytes Sent': 464 u'Pool Max': 0.0 u'Max Diff': 1.0 u'ID': u'POOL2' u'Work Had Roll Time': False u'Pool Calls': 0 u'Net Bytes Sent': 1348 u'Pool Av': 0.0 u'Bytes Recv': 692 u'Max Diff Count': 1 u'Pool Attempts': 0 u'Pool Wait': 0.0 u'Min Diff Count': 1}] u'id': 1}
|
|
|
read API readme file and sample file above api readme file.
Okay so i guess i need to compile the sample api code. thanks
|
|
|
look like your Jal 1 asic chips not good grade chip and Jal 0 look good.
ps: to get getinfo work u need to run cgminer config setting with api
Then how can I get the API info? Can it be done with a browser URL? Thanks
|
|
|
Just tweaked the firmware. changes ln 101 in std_defs.h #define __ASIC_FREQUENCY_ACTUAL_INDEX 9 New Speeds Before Jalapeno 0: 8.6GH/s : After Jalapeno 0: 9.2GH/sBefore Jalapeno 1: 7.7GH/s : After Jalapeno 1: 7.9GH/s [P]ool management [S]ettings [D]isplay options [Q]uit BAJ 0: max 35C 3.76V | 9.213G/9.197Gh/s | A:171 R:0 HW: 7 U: 22.82/m BAJ 1: max 41C 3.50V | 6.986G/7.907Gh/s | A:150 R:0 HW:35 U: 20.01/m
|
|
|
a) a tiny hex screwdriver to remove the screws off the bottom of the Jalapeno
Btw the correct terminology for the required driver is Torx T9 ![Grin](https://bitcointalk.org/Smileys/default/grin.gif)
|
|
|
Before Jalapeno 0: 6.2GH/s : After Jalapeno 0: 8.6GH/s Before Jalapeno 1: 5.5GH/s : After Jalapeno 1: 7.7GH/s
Very good. You must have 30 (or more) engines on Jalapeno 0. How can I get the stats of engines? I would want to know that. Thnks
|
|
|
@goxed What kind of temps are you getting with those aluminum heatsinks from the getinfo command? Is it a nice drop off from the original cooling solution?
those are just for use during flashing. It will kill the Jally for sure if used as a replacement after flashing. ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
Before Jalapeno 0: 6.2GH/s : After Jalapeno 0: 8.6GH/s Before Jalapeno 1: 5.5GH/s : After Jalapeno 1: 7.7GH/s
Setup for flashing Rev 2 Jalapeno with all aluminum heatsink.
Cool! Have you tried tweaking the firmware? Just tweaked the firmware. changes ln 101 in std_defs.h #define __ASIC_FREQUENCY_ACTUAL_INDEX 9 New Speeds Before Jalapeno 0: 8.6GH/s : After Jalapeno 0: 9.2GH/sBefore Jalapeno 1: 7.7GH/s : After Jalapeno 1: 7.9GH/s [P]ool management [S]ettings [D]isplay options [Q]uit BAJ 0: max 35C 3.76V | 9.213G/9.197Gh/s | A:171 R:0 HW: 7 U: 22.82/m BAJ 1: max 41C 3.50V | 6.986G/7.907Gh/s | A:150 R:0 HW:35 U: 20.01/m
|
|
|
Before Jalapeno 0: 6.2GH/s : After Jalapeno 0: 8.6GH/sBefore Jalapeno 1: 5.5GH/s : After Jalapeno 1: 7.7GH/sSetup for flashing Rev 2 Jalapeno with all aluminum heatsink. ![](https://ip.bitcointalk.org/?u=http%3A%2F%2Falumni.cs.ucr.edu%2F%7Eamitra%2Fbfl_jalapeno%2Fdragon%2Bjally.JPG&t=663&c=uz6hxEuEs1JvYg)
|
|
|
|