I uninstalled everything else i had installed to it by plugging it in, deleting the driver, then unplugging it and replugging it back in until my computer didn't know what it was again (each time it deleted a different driver) It's still happily showing up as COM113 but it's never once even lit up for me or appeared in bitminter or bfgminer. Btw is there any bfgminer or cgminer that doesn't piss off your anti-virus? if so a link to it would be awesome. I'd rather see it working in bitminter though. I've unplugged and replugged it in used the reset button, the program button (which to my knowledge does nothing) while probing the port at various times. The only thing it HAS done is show up as COM113 device in device manager. I got an Ice Fury Nano too because i guess i wanted to torture myself. They might both make a trip back to amazon if i can't get either to even blink a light at me.
What does Bitminter client say when you probe COM113? For the nanofury, try bfgminer. It's not supported in Bitminter client, at least not yet. |
|
|
|
Edit, i messed with it some more and got it to load the bf1.inf file with the "but there's no signature" and everything wokring right and it now lives in COM113. But when i go to add it to Bitminter, COM113 times out every time. I used the Bit Fury support center forum (not enough bitminter problems though).
That's the right driver. You may want to uninstall Zadig and the other things you installed. I have never used Zadig myself but from what I understand it interferes with normal drivers. The red fury often gets confused and just dies on you. To get it working again you have to unplug it, then plug it back in the USB port again. After that the client should be able to detect it and mine with it. There's also a reset button. In my experience this button doesn't actually do anything, but maybe that's just mine being broken. |
|
|
|
Thanks, do you have to add them to the list or are they automatically recognized when i name them in Cgminer?
Add them to the list on the website first, then use them in cgminer. Remember to put your username and an underscore in front of the worker name in cgminer. See explanation on the front page of bitminter.com Example: cgminer -o stratum+tcp://mint.bitminter.com:3333 -u Cheeseater_1 -p X
time to change the subject again. 810 is behind us.
1000 almost within reach  |
|
|
|
"Antminer (COM9): Not getting any results. Retuning timers."
Sometimes this doesn't work reliable. But stopping the device and starting it again is fine.
Is it possible to add an option how to deal with failing devices? Maybe some kind of event based actions similar to the scheduled actions.
What happens when it fails? The device is doing miscalculations over and over again until the client gives up on it? Or it times out? If the timer retuning fails there is probably something wrong. It's not getting any data from the device with regular mining for a while, which is possible although unlikely. In this event it sends the device some work that is known to produce a certain result. In this case the device should respond with the correct answer if it has not malfunctioned. In the options you can set it to scan for devices at regular intervals. You can also set it to start new devices automatically. This way you can use devices that occasionally die but recover after a while. |
|
|
|
Will Bitminter be including the functionality to control the Monarchs and Imperial Monarchs?
I will look into it. |
|
|
|
How do you add workers? I have two used the underscore to name them but they are both showing as worker 1.
Did you go "my account" -> "workers" in the website menu and add workers to the list there? If you did that but the work still gets registered under the "1" worker then it's because you typed the worker names wrong. The "1" worker is set up as a default worker, so if you mine with only the user name or with a mistyped worker name it is registered on that worker. You can choose a different default worker if you want. Access the options for a worker on the workers page by clicking the gears icon. The "default" setting is the topmost one. |
|
|
|
I keep getting "Bad Credentials" but it is only asking for my User Name and Worker Name.
It means you typed the user name or worker name wrong. If you're not sure what's wrong tell me what names you typed and I'll look them up. |
|
|
|
|
No, the log isn't saved. All of this sounds pretty odd. If you have this problem again see if you can get some screenshots and/or copy the log.
COM ports disappearing, not just in Bitminter but on OS level, and coming back, is usually because the device isn't getting enough power.
In Windows you can have a look in the device manager to see how many devices are detected by the OS and assigned to COM ports.
|
|
|
|
I had repeated disconnections, random miners would stop or be lost, and for some reason, when I got another new hub, I couldn't add more than 11 miners.
Did you notice if the Antminer COM ports would disappear at that point? Or were the COM ports still present, but the client still unable to communicate with the Antminters properly? |
|
|
|
Not too familiar with those, but looks to me like you need to set port on cube to 8332.
Problem is, that is the getwork port. I'm trying to steer away from that. To get on the more efficient stratum. I am fallowing this tutorial https://bitcointalk.org/index.php?topic=27062.msg3046129#msg3046129 Which is many pages back in this forum. But thank you for the idea. Got me thinking of another way. That's exactly right. The cubes only understand getwork. It's the only protocol they can use. But you are sending them to a stratum port on the proxy. So the proxy expects stratum, but the cube is talking getwork. That won't work. The cube should connect to the getwork port of the proxy. |
|
|
|
SO! I just picked up one of these Block Erupter cubes. Got er all set up, and ran into a slight snag. Can't seem to get it working with my mac. Aside from taking a hammer to may machines and buying new hardware, anyone have any advice on how to get this thing mining on bitminter?
Did you try this? https://bitcointalk.org/index.php?topic=27062.msg3046129#msg3046129 |
|
|
|
|
Dude. Half the thread is you trying to convince people you were trolling.
Noone believes you. Just let it go.
|
|
|
|
|
The only way Andreas can know that Dorian is not Satoshi is if Andreas is Satoshi.
Ah-hah!
|
|
|
|
what hell is going on?  Idiot posts misleading information. eleuthria goes on first class rant. Amusing Jesus image. That pretty much sums it up. You forgot: Some dude deletes his posts. Pretends he was just trolling. Tries too hard to make it look like trolling. It becomes awkward. |
|
|
|
I have asked multiple times for blockchain.info to correct that tag and they do nothing as always.
Probably best to stop using blockchain.info. What's the best alternative? |
|
|
|
Nice looking app, Morlock |
|
|
|
|
Hm, that is odd. I only have one Antminer U1 and I can change the speed up and down fine with it plugged in.
Does it help if you set their speed to 3 GH/s, see two of them fail, then restart Bitminter client?
I don't know what is causing that issue. Anyone else having such problems?
|
|
|
|
maybe I was not clear... the thing is that when I swap the antminers from one usb to another where the antminer that works fine was, then they start to work fine with the settings that the good antminer had (but previously they didn't get even to 2GH/s) is that a bug on the bitminter software or or is it a problem with the antminers? the antminers must have some difference but they are able to work at the same speed as I had proven with that swap.
Is there a way to disable self test? Maybe it would work fine without self test
The self test is that the app sends some work to the device where it knows what the answer should be. If this comes back wrong, that's not good. You'd get hardware errors while mining. It does try several times though, and if the device is able to get it right once, it will mine (and get some hardware errors, but hopefully not 100%). If it gets no good results for a while, it runs self test again. I'm not sure what's going on there. Bitminter client treats them the same, I don't think there's a problem there. But I really don't know why one COM port would work better than another. Is there any difference between the ports? Or are they all the same (on PC, or on same hub)? |
|
|
|
|
Bitminter client identifies the devices by their COM number. So if they get switched then they will get the wrong settings.
I could fix this for Red Fury which reports a serial number. But I don't know how I could fix this for Antminer. I don't think there's a way to tell one device apart from the other.
|
|
|
|
I use 2 BitFury Red Fury's.
I've seen some other complaints here as well about them not working properly.
Which driver did you install? Are they being detected and mine for a while, but then fail? Or not being detected at all? I have one red fury running perfectly stable. The only problem is sometimes if I stop mining and try to start again the red fury gets confused and refuses to work. Then I have to unplug it and plug it back in, and it works again. I believe this is a bug/issue with all red fury units. |
|
|
|
|
Show Posts
