MaxHedrm
BTC: 1BSpnsx4ZmE4v2oUS6sEo54n6kDztQwzso
Comments
-
Oh, I see what you were asking better now. I am still running the U3 in the GPU window. I haven't had time to mess around with it a lot to try the consolidated method again.
-
Well, that is all for U2 & the clock setting works. I haven't played with the clock on the U3 really.
-
Hmmm ... what works: (Quote)So, it certainly isn't a simple replace, and I have yet to find decent documentation for the various switches & arguments.
-
oops, yeah, I meant -s.Maybe I'll play with -d then.
-
Interesting. I just had to do my occasional reboot & even though only one of the UART addresses matched, it fired up all five of the U2s (the U3 wasn't plugged in). I guess -noauto doesn't do much.
-
That's actually what I decided to do once I found it seemed to be behaving with the U2s this time around.
What…Oh, here is a screenshot of the last several days...That's interesting ... I just rebooted from the memory leak & 1.5.25b started up first, so it grabbed the U2s (the FPGA/ASIC window auto starts). It is getting 11+GH/s out of them. I guess I'll leave it running & see if it behaves.Remember my drive space issue? It seems to be a memory leak, the cache folder isn't huge. :-)Right now I am still running in the 2 different versions of MacMiner.1.5.25:5 U2s - usually ar…The U3 has been running pretty stably lately. I haven't had to reset the device but once in the last 48 hours or so, & didn't have to restart the app at all.I may have to play with them again to see, I've slept with them. I think it was more that they weren't detected & wouldn't start up. I can't recall for sure if I tried it with only them connected. That should be testable tomorrow though.Except that the 1.5.25b seems unreliable with the U2s.Because the GPU & ASIC windows would start at the same time in both instances. Same prefs, remember? I guess that would only be a problem at start-up then because of the windows being told to open at start up. That should be manageable.So, the problem with running 2 MacMiner instances, is that they both use the same prefs and ASIC Miner options. So, when .25b restarted, it used the long list of miners, missing 44. Is there a way to separate the prefs?Could I use the serial numbers for the -S as well or does it have to use the /dev?I get ~33Gh on the U3, plus ~10Gh on the 5 U2s. I think that's about 50% of what the U3 is rated at, so I'll have to look at those switches again once things seems to be behaving.I never really investigated it, I just know rebooting fixes it.
I'll take a look next time they run for a few days.…Oh, I forgot to mention that the U3 was unplugged from the USB when I started the 1.5.25. That's important.
I decided to try it this way...start MacMiner 1.5.25 with -S antminer:allthenstart MacMiner 1.5.25b with -S antminer:/dev/cu.SLAB_USBtoUART44(I tried using :all…That would also mean I'd have to make sure they started in the right order. I guess that'd only be an issue for power outages. (And… But before it was [null], 1, 2, 3, 4, 5. Dynamic stuff is annoying. Hahah. So, that's why it only picked one of them. I turned auto back on & it detected:[2015-03-21 20:55:43] AMU 0: Opened /dev/cu.SLAB_USBtoUART37
[2015-03-21 20:55:43] AMU 2: Opened /dev/cu.SLAB_USBtoUART36
[2015-03-21 …
Oddly, I tried:-S noauto -S antminer:/dev/cu.SLAB_USBtoUART -S antminer:/dev/cu.SLAB_USBtoUART1 -S antminer:/dev/cu.SLAB_USBtoUART2 -S antminer:/dev/cu.SLAB_USBtoUART3 -S antminer:/dev/cu.SLAB_USBtoUART4It still fire…Yeah, I just had antminer checked. With it unchecked nothing detects.-S noauto -S antminer:/dev/cu.SLAB_USBtoUART gives me one U2 (which makes sense). Amusingly, it was the one that was most often having issues detecting on aut…Weird. Now I just have the U2s plugged in. It seems to be detecting 4 at most, and the ones it doesn't detect vary. Then it stops again. *sigh* <wahhhhhhh>Why does this have to be so hard.</wahhhhhhh>in Antminer U3 + 5 Antminer U2 Comment by MaxHedrm March 2015
I removed all the manual flags, basically, I'm just telling it to try to detect antminer in the settings window.As for MobileMiner, I think it is showing things correctly now for the most part.First try was no good. So I restarted the U3 too. Then it ran a little, but ended up stopping. So, maybe it is bad. *sigh* I even invested in a better power supply for it.Ahh. I was wondering how I would do that. I'll start by just unplugging the U2s to see if the U3 will behave on its own.
