Topic: GekkoScience Compac BM1384 Stickminer Official Support Thread - page 57. (Read 268027 times)
February 02, 2016, 08:40:24 AM
is this in a powered hub or a unpowered hub ? sounds kinda like a lil setup issues unless its only 1 stick thats not working i would suggest talking with sidehack and novak there the manufactures of the sticks and listen to them
February 02, 2016, 08:35:19 AM
Hey, was able to borrow my friend's voltmeter. It turns out the unit was set at 0.694v. I adjusted it again down to 0.559V and back up to 0.8V in increments, and restarted the client every time I made an adjustment to check for stability. I was unable to get the unit stable, unfortunately. The most I could get it to do was a few error hashes (The HW count).
I am assuming the miner is faulty, then?
I am assuming the miner is faulty, then?
February 01, 2016, 03:41:20 PM
if you mine to the burgerfund address without adding a worker_name, it will just add it to the default worker which already has stuff pointed at it, but sugg_diff won't work if its already raised for that default worker because your just adding more hash power to an existing connection.
February 01, 2016, 02:21:29 PM
I think it should have worked fine with --benchmark
Try forcing it at 100Mhs when you do it
--compac-freq 100 --benchmark
This way there's no account involved
Try forcing it at 100Mhs when you do it
--compac-freq 100 --benchmark
This way there's no account involved
Thanks, but I tried this before. I didn't realise it bypassed the pool altogether, though this makes it way easier. I am going to get a more precise voltmeter tonight and try the benchmark feature with the clock at 100mhz.
February 01, 2016, 02:05:36 PM
I think it should have worked fine with --benchmark
Try forcing it at 100Mhs when you do it
--compac-freq 100 --benchmark
This way there's no account involved
Try forcing it at 100Mhs when you do it
--compac-freq 100 --benchmark
This way there's no account involved
February 01, 2016, 01:59:34 PM
the meter that measures 0.5-0.6 cannot be described as "proper".
you need one that measures mv to the third number, like 0.653V
I use this one:
http://www.amazon.com/INNOVA-3320-Auto-Ranging-Digital-Multimeter/dp/B000EVYGZA
Second, i don't think you should dismiss the worker comment without checking, although it is a minor possibility.
Basically, Eligius detects two miners with exactly the same name.
i am not sure it does not result in conflict. in fact, it happened to me once and one miner simply dropped out (stopped hashing in a short while).
others might comment if it is in fact possible to have two workers with identical names.
I do have an account at another mining pool I can try. I will make a worker for this device exclusively.
I should have access to a more precise meter, I'll be able to test it tonight.
even simpler, make a new wallet account on blockchain.info and use that wallet address as a worker on kano.is or Eligius.
I actually had a blockchain account
Tried it in cgminer and bfgminer and it has made no difference unfortunately. The bfgminer is still not able to detect the device.
Will explore the other voltmeter tonight.
February 01, 2016, 01:57:38 PM
So more on improving cooling for my 6 gekkos.
I've ordered 2 of the following heatsink:
I plan to attach 3 sticks side by side on each, they have higher fins and they're orientated properly for my current cooling setup.
What do you think ?
I've ordered 2 of the following heatsink:
I plan to attach 3 sticks side by side on each, they have higher fins and they're orientated properly for my current cooling setup.
What do you think ?
Now I'm wondering if I should re use screws to secure the sticks or if thermal pad would be good enough....
February 01, 2016, 01:46:37 PM
the meter that measures 0.5-0.6 cannot be described as "proper".
you need one that measures mv to the third number, like 0.653V
I use this one:
http://www.amazon.com/INNOVA-3320-Auto-Ranging-Digital-Multimeter/dp/B000EVYGZA
Second, i don't think you should dismiss the worker comment without checking, although it is a minor possibility.
Basically, Eligius detects two miners with exactly the same name.
i am not sure it does not result in conflict. in fact, it happened to me once and one miner simply dropped out (stopped hashing in a short while).
others might comment if it is in fact possible to have two workers with identical names.
I do have an account at another mining pool I can try. I will make a worker for this device exclusively.
I should have access to a more precise meter, I'll be able to test it tonight.
even simpler, make a new wallet account on blockchain.info and use that wallet address as a worker on kano.is or Eligius.
February 01, 2016, 01:44:52 PM
the meter that measures 0.5-0.6 cannot be described as "proper".
you need one that measures mv to the third number, like 0.653V
I use this one:
http://www.amazon.com/INNOVA-3320-Auto-Ranging-Digital-Multimeter/dp/B000EVYGZA
Second, i don't think you should dismiss the worker comment without checking, although it is a minor possibility.
Basically, Eligius detects two miners with exactly the same name.
i am not sure it does not result in conflict. in fact, it happened to me once and one miner simply dropped out (stopped hashing in a short while).
others might comment if it is in fact possible to have two workers with identical names.
I do have an account at another mining pool I can try. I will make a worker for this device exclusively.
I should have access to a more precise meter, I'll be able to test it tonight.
February 01, 2016, 01:41:43 PM
So, set and measured with a proper meter or were you basing the measure off the pot position? Because it's possible for the pot to not work and the voltage gets locked to 550mV in which case, if it starts at all, it'll only start and work at very low frequency.
If core voltage is good, and it detects in cgminer with proper serial number displayed and such, but you don't get hashing, it's probably something wrong with the hardware.
If core voltage is good, and it detects in cgminer with proper serial number displayed and such, but you don't get hashing, it's probably something wrong with the hardware.
Yes it was a proper meter. It only measured down to one decimal point, but I was getting fluctuations between 0.5 and 0.6 at the lowest setting, and 0.8 at the highest.
Thanks for the input. I am going to try a few more tests on a different system tonight and request an RMA if I don't get anywhere.
the meter that measures 0.5-0.6 cannot be described as "proper".
you need one that measures mv to the third number, like 0.653V
I use this one:
http://www.amazon.com/INNOVA-3320-Auto-Ranging-Digital-Multimeter/dp/B000EVYGZA
Second, i don't think that you should dismiss the worker comment without checking, although it is a minor possibility.
Basically, Eligius detects two miners with exactly the same name.
i am not sure that it does not result in conflict. in fact, it happened to me once and one miner simply dropped out (stopped hashing in a short while).
others might comment if it is in fact possible to have two workers with identical names.
February 01, 2016, 11:24:53 AM
So, set and measured with a proper meter or were you basing the measure off the pot position? Because it's possible for the pot to not work and the voltage gets locked to 550mV in which case, if it starts at all, it'll only start and work at very low frequency.
If core voltage is good, and it detects in cgminer with proper serial number displayed and such, but you don't get hashing, it's probably something wrong with the hardware.
If core voltage is good, and it detects in cgminer with proper serial number displayed and such, but you don't get hashing, it's probably something wrong with the hardware.
Yes it was a proper meter. It only measured down to one decimal point, but I was getting fluctuations between 0.5 and 0.6 at the lowest setting, and 0.8 at the highest.
Thanks for the input. I am going to try a few more tests on a different system tonight and request an RMA if I don't get anywhere.
February 01, 2016, 11:07:20 AM
So, set and measured with a proper meter or were you basing the measure off the pot position? Because it's possible for the pot to not work and the voltage gets locked to 550mV in which case, if it starts at all, it'll only start and work at very low frequency.
If core voltage is good, and it detects in cgminer with proper serial number displayed and such, but you don't get hashing, it's probably something wrong with the hardware.
If core voltage is good, and it detects in cgminer with proper serial number displayed and such, but you don't get hashing, it's probably something wrong with the hardware.
February 01, 2016, 10:50:59 AM
So I didn't have any luck with BFGminer. It would not detect the stick. I tried with the default windows drivers, and also again with the zadig drivers, just to be sure. I also tried adding the device manually (it was mapping as COM16 port). Not sure if there are any special flags I need to detect the Gekko USB stick? It shows as supported on their newest version release notes.
Gave cgminer another try and got a different result this time, though.
Here is a screenshot - http://imgur.com/G5Lo0HI
It appears like it is only generating errors, but is at least trying to hash now. I was using the flag --suggest-diff 25
Gave cgminer another try and got a different result this time, though.
Here is a screenshot - http://imgur.com/G5Lo0HI
It appears like it is only generating errors, but is at least trying to hash now. I was using the flag --suggest-diff 25
did you try another address (not Burger) or at least, did you change it to have your unique worker name?
It won't work if you use just Burger address.
It seems that you are very close to make it work.
I used the same pool address/user as was set up in the cgminer-run script that is included the cgminer-gekko-win32 version. As it connects successfully to the pool, I don't believe this is the issue. I came to this conclusion because the program cannot detect any USB devices - it is not having an issue getting shares. When adding a new device, after selecting "auto", it seemed to start hashing ok on my GPU.
February 01, 2016, 10:39:40 AM
I would highly recommend finding some way to measure the core voltage. Try it on 100MHz and see if it runs a bit more stable.
I have tested this already. Right now it is set at 0.7V, but I have tried between 0.55 and 0.8 with no change in results. Just tried again at 100mhz, no change. I will try again tonight when I have access to a voltmeter again.
February 01, 2016, 10:32:00 AM
I would highly recommend finding some way to measure the core voltage. Try it on 100MHz and see if it runs a bit more stable.
February 01, 2016, 10:29:00 AM
So I didn't have any luck with BFGminer. It would not detect the stick. I tried with the default windows drivers, and also again with the zadig drivers, just to be sure. I also tried adding the device manually (it was mapping as COM16 port). Not sure if there are any special flags I need to detect the Gekko USB stick? It shows as supported on their newest version release notes.
Gave cgminer another try and got a different result this time, though.
Here is a screenshot - http://imgur.com/G5Lo0HI
It appears like it is only generating errors, but is at least trying to hash now. I was using the flag --suggest-diff 25
Gave cgminer another try and got a different result this time, though.
Here is a screenshot - http://imgur.com/G5Lo0HI
It appears like it is only generating errors, but is at least trying to hash now. I was using the flag --suggest-diff 25
did you try another address (not Burger) or at least, did you change it to have your unique worker name?
It won't work if you use just Burger address.
It seems that you are very close to make it work.
February 01, 2016, 10:21:07 AM
So I didn't have any luck with BFGminer. It would not detect the stick. I tried with the default windows drivers, and also again with the zadig drivers, just to be sure. I also tried adding the device manually (it was mapping as COM16 port). Not sure if there are any special flags I need to detect the Gekko USB stick? It shows as supported on their newest version release notes.
Gave cgminer another try and got a different result this time, though.
Here is a screenshot - http://imgur.com/G5Lo0HI
It appears like it is only generating errors, but is at least trying to hash now. I was using the flag --suggest-diff 25
Gave cgminer another try and got a different result this time, though.
Here is a screenshot - http://imgur.com/G5Lo0HI
It appears like it is only generating errors, but is at least trying to hash now. I was using the flag --suggest-diff 25
February 01, 2016, 09:14:49 AM
Try a PC running a Linux build (no messing around with zadig or usb drivers).... or a Raspberry Pi with Raspbian (a Linux build)...or
Remove zadig driver and try bfgminer 5.4.1
Going to try the BFGminer option, as I do not have access to a Raspberry Pi. I'll let you know how it goes.
February 01, 2016, 09:11:39 AM
That thing look fine..
I would try adding
Code:
--suggest-diff 25
.. in the cgminer commands, see if that allows it to start hashing, the 512 may be to much for the stick to work on within the 10 secondsRemove zadig driver and try bfgminer 5.4.1
February 01, 2016, 08:13:41 AM
Remove zadig driver and try bfgminer 5.4.1
Jump to: