Topic: The combined sidehack-novak usb stick review thread. AKA GekkoScience BM1384 - page 9. (Read 26365 times)
July 06, 2015, 11:40:30 AM
Running my stock 4.9.0 at 250MHz I'm seeing 13.7GH; running your custom build at 250MHz I got up to 11.5GH with a lot of resets. The power draw was what I expected for 250MHz but the hashrate and WU came in low. Not sure what's up.
July 05, 2015, 11:41:02 PM
PM sent - forum's having some glitches, postponing cgminer build thread until tomorrow/day after depending on hours.
July 05, 2015, 11:05:21 PM
I certainly wouldn't mind getting ahold of that cgminer build. Novak's gonna be busy all week catching up on his own projects and I need to be manufacturing PSU gear so I doubt either of us are gonna have much time for cgminer coding.
Also, by now there should be at least six of the new final-prototype sticks delivered to US testers (three more went to people overseas). Hopefully this week enough of them will post info that we can get a consensus whether or not they're sellable. Might open an order queue as early as Friday.
Also, by now there should be at least six of the new final-prototype sticks delivered to US testers (three more went to people overseas). Hopefully this week enough of them will post info that we can get a consensus whether or not they're sellable. Might open an order queue as early as Friday.
July 05, 2015, 10:38:31 PM
That's pretty cool !
Great job guys
Great job guys
July 05, 2015, 10:30:06 PM
Hopefully no magic smoke was released in an untimely coincidence. I'll see about documenting the cgminer build (mis-)steps somewhere (not this thread, way too o/t). If anybody wants to play with my binary, shoot me a PM - or just wait for sidehack/novak's build
Not trying the build yet but photos of my gear at freq 250. I am impressed with these little sticks.
say 2.2 amps x 4.75 volts = 9.9 watts giving 27.46gh this is 0.36 watts per gh at a high overclock.
http://imageshack.com/a/img907/1672/EqSGyN.jpg
http://imageshack.com/a/img908/3190/27EUgh.jpg
http://imageshack.com/a/img673/7530/VDJCEv.jpg
http://imageshack.com/a/img673/766/zfie6A.jpg
so in an 82 f garage and a 140 mm pair of fans these sticks are merely warm
my pc running cgminer and bitcoin and the hub running the 2 sticks use 46-47 watts
the 2 sticks and the hub use 16 watts
the cgminer has run more then a ½ day at this setting 8HW FOR ONE AND 2HW FOR THE OTHER!!
pretty good.
July 05, 2015, 10:14:34 PM
Hopefully no magic smoke was released in an untimely coincidence. I'll see about documenting the cgminer build (mis-)steps somewhere (not this thread, way too o/t). If anybody wants to play with my binary, shoot me a PM - or just wait for sidehack/novak's build
July 05, 2015, 10:13:19 PM
TheRealSteve sent me a cgminer build.
Will test it in the morning.
Thanks steve.
BTW these sticks float along at freq 250
30 plus hours one has 2 or 3 hw's the 5 or 6.
Stats are
4.73v 1.12amps
4.73v 1.07amps
I got a second meter. I will post a photo in a few mins.
Will test it in the morning.
Thanks steve.
BTW these sticks float along at freq 250
30 plus hours one has 2 or 3 hw's the 5 or 6.
Stats are
4.73v 1.12amps
4.73v 1.07amps
I got a second meter. I will post a photo in a few mins.
July 05, 2015, 10:07:24 PM
Yeah, that's the one.
I won't have any more progress until tomorrow when I get into the shop. Not sure if something in the compile scripts hosed USB or if the hub's smoked out or what but I got no sticks even on the cgminer already built into minera, which actually was still working after the first unsuccessful rebuild from git (in a different location).
I'll talk to Novak tomorrow and see what he thinks, since linux and programming are both more his thing. It's funny, I'm the one with a CS degree to his Aero but he's the far better programmer.
I won't have any more progress until tomorrow when I get into the shop. Not sure if something in the compile scripts hosed USB or if the hub's smoked out or what but I got no sticks even on the cgminer already built into minera, which actually was still working after the first unsuccessful rebuild from git (in a different location).
I'll talk to Novak tomorrow and see what he thinks, since linux and programming are both more his thing. It's funny, I'm the one with a CS degree to his Aero but he's the far better programmer.
July 05, 2015, 09:42:08 PM
Actually, I'm on an XP laptop in my living room, SSH'd into a Debian server at the shop, re-SSH'd into a Pi with Minera on a shelf in the office, and building it on that.
Must. Go. Deeper.
In the mean time, I got mine to build. This took well over 100 steps (admittedly, this includes clicking trivial buttons and such - was documenting it in screenshots just in case) and a whole bunch of googling and crossing fingers.. and the particular error I was facing semi-last (there were two more after that) is actually a MinGW issue that should be fixed soon.
For reasons I haven't explored yet, I also ended up needing 'libgcc_s_dw2-1.dll', but then it started right up and fired off on a Block Erupter USB without issue (so far - not a fan of the zadiggery and tend to run older cgminer).
@sidehack: what are the functions that need tweaking in addition to the define and LUT?
Edit: I suspect it's the set_float_100_to_250 cap on input parameters?
July 05, 2015, 08:46:03 PM
Actually, I'm on an XP laptop in my living room, SSH'd into a Debian server at the shop, re-SSH'd into a Pi with Minera on a shelf in the office, and building it on that.
Which cgminer 4.9.2 built straight from git isn't picking up my sticks either. But now the stock cgminer isn't picking them up either? Dunno what's up.
Which cgminer 4.9.2 built straight from git isn't picking up my sticks either. But now the stock cgminer isn't picking them up either? Dunno what's up.
July 05, 2015, 08:25:07 PM
Hey, at least you got that far 
I haven't compiled cgminer on windows in a very long time; the instructions are outdated, several things have changed in various locations, and just when I thought it was getting somewhere... I'm hitting make complaining about the size of struct timespec being unknown
( cross-compiling on a linux install is much more fun )
I haven't compiled cgminer on windows in a very long time; the instructions are outdated, several things have changed in various locations, and just when I thought it was getting somewhere... I'm hitting make complaining about the size of struct timespec being unknown ( cross-compiling on a linux install is much more fun )
July 05, 2015, 08:12:34 PM
So I added a bunch of frequencies to driver-icarus. You also have to modify a function in a few places in cgminer.c to take the accepted max up from 250 to 300.
I added that into the current git code (4.9.2) Recompiled and all that, cgminer starts and recognizes --au3-freq above 250 but doesn't see sticks. Of course I didn't test compile the stock code to see if it worked before I made my changes. Whoops.
I added that into the current git code (4.9.2) Recompiled and all that, cgminer starts and recognizes --au3-freq above 250 but doesn't see sticks. Of course I didn't test compile the stock code to see if it worked before I made my changes. Whoops.
July 05, 2015, 06:18:02 PM
Borrowed from an S1 thread, clock and hex:
256.25 1405
262.50 0a01
268.75 1505
275.00 0a81
281.25 1605
287.50 0b01
293.75 1705
300.00 0580
You're going to want to find driver-icarus.c. Change the ANT_U3_MAXFREQ to 300 and add these to the u3freqtable around line 400 then recompile. Doing that on Windows is going to be less than fun.
I've got my sticks on a Pi at the shop but I can ssh into it. I'll see if I can do it there.
256.25 1405
262.50 0a01
268.75 1505
275.00 0a81
281.25 1605
287.50 0b01
293.75 1705
300.00 0580
You're going to want to find driver-icarus.c. Change the ANT_U3_MAXFREQ to 300 and add these to the u3freqtable around line 400 then recompile. Doing that on Windows is going to be less than fun.
I've got my sticks on a Pi at the shop but I can ssh into it. I'll see if I can do it there.
may be over my head. but I will keep trying a few ideas.
July 05, 2015, 06:09:40 PM
Borrowed from an S1 thread, clock and hex:
256.25 1405
262.50 0a01
268.75 1505
275.00 0a81
281.25 1605
287.50 0b01
293.75 1705
300.00 0580
You're going to want to find driver-icarus.c. Change the ANT_U3_MAXFREQ to 300 and add these to the u3freqtable around line 400 then recompile. Doing that on Windows is going to be less than fun.
I've got my sticks on a Pi at the shop but I can ssh into it. I'll see if I can do it there.
256.25 1405
262.50 0a01
268.75 1505
275.00 0a81
281.25 1605
287.50 0b01
293.75 1705
300.00 0580
You're going to want to find driver-icarus.c. Change the ANT_U3_MAXFREQ to 300 and add these to the u3freqtable around line 400 then recompile. Doing that on Windows is going to be less than fun.
I've got my sticks on a Pi at the shop but I can ssh into it. I'll see if I can do it there.
July 05, 2015, 05:51:35 PM
here is a screenshot of my 4.9.2
fullsize link
http://imageshack.com/a/img540/3146/eN85t7.png
My coding skills are poor I can do a start bat file and not much else.
fullsize link
http://imageshack.com/a/img540/3146/eN85t7.png
My coding skills are poor I can do a start bat file and not much else.
July 05, 2015, 05:43:13 PM
I think you'd need to adjust driver-icarus.c:
The function anu3_find_freqhex basically does a look-up of the frequency given on the command line in the table without exceeding it. So supplying it with '166' will make it use the '150' freq.
The function set_anu_freq sends the frequency on over and then it's wait and see if things freak out or not
* No idea if making it use anu_find_freqhex instead wouldn't work. Can't spot a reason for using a LUT for the U3 in the cgminer commits.
Code:
#define ANT_U3_MAXFREQ 250
Change to 450Code:
} u3freqtable[] = {
{ 100, 0x0783 },
{ 125, 0x0983 },
[...]
{ 243.75, 0x1306 },
{ 250, 0x0982 },
Extend that with:{ 100, 0x0783 },
{ 125, 0x0983 },
[...]
{ 243.75, 0x1306 },
{ 250, 0x0982 },
Code:
{ 275, 0x0a82 },
{ 300, 0x0b82 },
{ 325, 0x0c82 },
{ 350, 0x0d82 },
{ 375, 0x0e82 },
{ 400, 0x08f2 },
{ 425, 0x0801 },
{ 450, 0x0881 },
( values from datasheet - there's a formula if you want to try other values* If bfgminer works feed it hex values directly ){ 300, 0x0b82 },
{ 325, 0x0c82 },
{ 350, 0x0d82 },
{ 375, 0x0e82 },
{ 400, 0x08f2 },
{ 425, 0x0801 },
{ 450, 0x0881 },
The function anu3_find_freqhex basically does a look-up of the frequency given on the command line in the table without exceeding it. So supplying it with '166' will make it use the '150' freq.
The function set_anu_freq sends the frequency on over and then it's wait and see if things freak out or not
* No idea if making it use anu_find_freqhex instead wouldn't work. Can't spot a reason for using a LUT for the U3 in the cgminer commits.
Okay so lets say I want to get my working version of cgminer 4.9.2 to add for the sake of argument
freq 256.25
freq 262.50
freq 268.75
freq 275.00
freq 281.25
freq 287.50
freq 293.75
freq 300.00
which I THINK MY SETUP AND THE USB STICKS CAN DO.
I do not understand how to splice it into the cgminer 4.9.2 I have.
give me a few minutes to show a screen shot or two.
July 04, 2015, 05:15:43 AM
The code I wrote to help with S1 undervolting (http://gekkoscience.com/misc/set_freq.cpp) should print out valid hex for the nearest possible setpoint to any arbitrary frequency, if you want more granularity than 25MHz steps just add whatever lines you want to it.
July 04, 2015, 01:04:07 AM
I think you'd need to adjust driver-icarus.c:
The function anu3_find_freqhex basically does a look-up of the frequency given on the command line in the table without exceeding it. So supplying it with '166' will make it use the '150' freq.
The function set_anu_freq sends the frequency on over and then it's wait and see if things freak out or not
* No idea if making it use anu_find_freqhex instead wouldn't work. Can't spot a reason for using a LUT for the U3 in the cgminer commits.
Code:
#define ANT_U3_MAXFREQ 250
Change to 450Code:
} u3freqtable[] = {
{ 100, 0x0783 },
{ 125, 0x0983 },
[...]
{ 243.75, 0x1306 },
{ 250, 0x0982 },
Extend that with:{ 100, 0x0783 },
{ 125, 0x0983 },
[...]
{ 243.75, 0x1306 },
{ 250, 0x0982 },
Code:
{ 275, 0x0a82 },
{ 300, 0x0b82 },
{ 325, 0x0c82 },
{ 350, 0x0d82 },
{ 375, 0x0e82 },
{ 400, 0x08f2 },
{ 425, 0x0801 },
{ 450, 0x0881 },
( values from datasheet - there's a formula if you want to try other values* If bfgminer works feed it hex values directly ){ 300, 0x0b82 },
{ 325, 0x0c82 },
{ 350, 0x0d82 },
{ 375, 0x0e82 },
{ 400, 0x08f2 },
{ 425, 0x0801 },
{ 450, 0x0881 },
The function anu3_find_freqhex basically does a look-up of the frequency given on the command line in the table without exceeding it. So supplying it with '166' will make it use the '150' freq.
The function set_anu_freq sends the frequency on over and then it's wait and see if things freak out or not
* No idea if making it use anu_find_freqhex instead wouldn't work. Can't spot a reason for using a LUT for the U3 in the cgminer commits.
July 03, 2015, 06:08:13 PM
Yeah, I had forgotten the U3 code only has up to 250MHz in it. The actual code shouldn't be too hard to modify to add additional frequencies, it'd be dropped into the Icarus driver.
The black-heatsink stick was made with one of our new-from-Bitmain sample chips, the gold one actually has a pulled chip. The power dissipation also increases with heat, so the smaller heatsink on the gold stick probably adds to that slightly.
The black-heatsink stick was made with one of our new-from-Bitmain sample chips, the gold one actually has a pulled chip. The power dissipation also increases with heat, so the smaller heatsink on the gold stick probably adds to that slightly.
still 250 is pretty good. someone that knows how to mod the Icarus will need to give me a few screen shots on that.
I am pretty sure that with a quality high speed fan these will do more then freq 250 and 13.8 or 13.9 gh.
I will run them overnight at freq 250 then back down to 218.75
July 03, 2015, 04:52:15 PM
Yeah, I had forgotten the U3 code only has up to 250MHz in it. The actual code shouldn't be too hard to modify to add additional frequencies, it'd be dropped into the Icarus driver.
The black-heatsink stick was made with one of our new-from-Bitmain sample chips, the gold one actually has a pulled chip. The power dissipation also increases with heat, so the smaller heatsink on the gold stick probably adds to that slightly.
The black-heatsink stick was made with one of our new-from-Bitmain sample chips, the gold one actually has a pulled chip. The power dissipation also increases with heat, so the smaller heatsink on the gold stick probably adds to that slightly.
Jump to: