FabulousPanda
Comments
-
Did you try moving it to your Applications folder?Are you only using the ASIC window, and do you have MobileMiner set up? Please let me know every setting you changed so I can attempt to reproduce the error.
Unless your electricity is free and you don't intend to keep the mac longer than it's warranty period it wouldn't hurt, but you'd only earn a few cents…The default setting for the CPU miner window is Litecoin mining as that's e…Ah - I should have looked at the model of the GPU you're using… I'm afraid it's not really capable of mining, it might work if you set the intensity to the lowest possible value but you'd probably get about 1Mh/s - these days 1Gh/s is hard enough to…Uh-oh, your GPU is failing for some reason! Did you change any of the settings, particularly increasing the intensity could have done it? Or did you just update to the latest version and as soon as you did you got this error?That sounds like really good news! Can you please post a brief summary of how you've set them up, and their hash rates? It would be great if we could get them all running in just the ASIC window togetherThanks for posting all that, I think I got what I needed from the bit that says thread 6 crashed. Seems to be expected a string to be something it's not…Probably won't make a difference, but could you please move MacMiner to yo…Ah, what were you doing when it quit unexpectedly? Can you reproduce the crash and if so, when the panel comes up click 'report' and paste the debug info for me here please?The problem you've having now is that because it quit …(Quote) In that the miner frequently restarts itself in .25b whereas it didn't before, and if so is that the case with ONLY U2s connected or it happens only when both types are connected? Sorry to pester for details, need to send luke-jr an accura…BTW extra thanks for your report on the MobileMiner issue, I believe I've sorted that bug properly (devices in mobile miner are displayed much more accurately when multiple instances are monitored in API Output) and once bfg 5.2 is out which should …Ah, wasn't sure sure whether that was due to a problem unit. In that case same applies but you'll have to use the multiple instances of MacMiner - at least you can skip the applescript portion! I'll post back here when bfgminer is updated…Are you using the flags - and ONLY the flags - I mentioned, in the FPGA/ASIC window? What happens when you click start?yeah, but you could get it all going in a single instance of MacMiner if ASIC flags (with correct devices listed) are-S noauto -S antminer:/dev/cu.SLAB_USBtoUART -S antminer:/dev/cu.SLAB_USBtoUART1 -S antminer:/dev/cu.SLAB_USB…You mean because the GPU and ASIC windows would start at the same time? I'm pretty sure that's not an issue if you use -S noauto in each followed by the devices to be used in each windowI haven't looked in to the serial issue, the serial is set by the manufacturer so there's a good chance all units of the same model have the same serial in which case you'd need to get a bit hands on to work around that.If you'…I'd definitely recommend specifying the devices one by one, as long as they're no unplugged and replugged they should keep the original numbers - then maybe you can use all for the U3 in the second instance of MacMiner, or if we're lucky and they al…Oooh, what are the hash rates you're getting in this setup? Maybe the bfgminer beta is currently too U3 focused!If your machine has just started up the miners should be from/dev/cu.SLAB_USBtoUARTto<…Another option is to set the U3 up like-S noauto -S antminer:/dev/cu.SLAB_USBtoUART(assuming you can identify it…)then in the second miner window use-S …haha, must be the result of replugging them. To get a list of currently connected miners (among other things) type this in to the Terminal app:ls -la /dev/cu*Aha! Rinse and repeat with another unit, if it behaves leave the dodgy one out till troubleshooting is though…Also, if you're using all of these in the beta version with antminer U3 support I'd check whether the U2 behaviour changes in the standard version, but please note down all the behaviours you notice and the differences in behaviour with the new vers…If I were you I'd set up the ASIC window to use your U2s by flags like-S noauto -S antminer:/dev/cu.SLAB_USBtoUART -S antminer:/dev/cu.SLAB_USBtoUART1 -S antminer:/dev/cu.SLAB_USBtoUART2etc.
by checking the antminer box? I'm not sure that's necessary any more, things have changed a bit since that was coded, I'd uncheck them all - it detects my BFL now regardless of whether it's set to in options, though that's not true for Block eruptor…ack, what are the manual flags you're using, and are any other options set in the config panel? The U3 driver is still in beta so it could be that… Still got the original power supply?The GPU window isn't configured to allow shutting of the GPU unfortunately, so you can either just set the intensity on the gpu miner to -10 so that it doesn't put much strain on the system, or use the workaround from my past post for the ASIC windo…That's really curious! Have you been watching the API Output window, which shows stats for individual devices? Whatever shows up there should show up in MobileMiner, if not something is wrong…The ASIC window is set up for SHA256 mining only so you'd have had to set up a bitcoin pool, alternately if the U3 has a temp sensor and you'd like to see the reading a dirty workaround would be to add (again with two dashes)--…Great news! Thank you for coming back to help us out
That auto restart behaviour was put in in case something causes an unexpected stop (my Jalapeño stops every 10mins which breaks bfgminer and requires it to start over)The behaviour is very annoying when it's due to an initial s…The problem is that you need two dashes i.e. -- in front of set, so it's --set not -setAh, glad to hear you got a speed boost!That said, you should be able to use the Gridseed in the GPU window (Or ASIC window for that matter) if configured appropriately.In GPU window open up the opti…