Pages:
Author

Topic: [GUIDE] GridSeed GC3355 5 Chip Setup/power/windows/linux/rpi by UnicornHasher - page 14. (Read 365630 times)

hero member
Activity: 519
Merit: 502
It has nothing to do with the screen. From what I can see you might be running windows 7 just go to start and search for device manager and do the same as I told you to do in windows xp since it can still turn it off.

BTC Address:1MQgDfn3b4RETVMABNzKB3oqbu6e8pTd5Z
Donate to a newbie Wink
newbie
Activity: 42
Merit: 0
Thanks, I will try that

but the problem occurs even if the screen is still on, I changed the setting for the computer to go sleep after 5 hours and the problem still occurs.

very strange...

hero member
Activity: 519
Merit: 502
Which windows are you running for me I was using windows xp (it varies from windows to windows) so I right clicked on my computer went to properties>> Device Manager
Scrolled down to Universal Serial Bus Controllers expanded them then right click on all the USB Root Hub individually go to their properties>> Then look for Power management Tab on top click on it and it should say something like allow computer to switch off ... uncheck that on all the USB Root Hub.


BTC Address:1MQgDfn3b4RETVMABNzKB3oqbu6e8pTd5Z
Donate to a newbie Wink
newbie
Activity: 42
Merit: 0
Thanks for your help

here is the bat file

cgminer.exe --scrypt -o stratum+tcp://uswest.wafflepool.com:3333 -u bitcoinaddress -p x -o stratum+tcp://ca.suchcoins.com:3334 -u username-p x -o stratum+tcp://scrypt1.poolwarz.com:3333 -u 11284.1 -p x --failover-only --gridseed-options=baud=115200,freq=850,chips=5 --hotplug 30

pause

Where can I check if the power setting shut down the USB??? I set it up so it will only dim the screen and not go to sleep for 5 hours, but the problem happens after a few minutes and I can see no shares being submitted for hours...

thanks again for all your guidance out there....

i am very new to this and highly appreciate all your efforts

Thanks
hero member
Activity: 519
Merit: 502
Yes, I have the hotplug set to 30, should I change it?Huh

Yes if this doesnt work I will try BFGminer,

Anyone has any experience this problem? what might be the cause of this?

I only have 1 Gridseed running before I buy more, but wanted to see how it works first

Thanks again for all your help

Oren

Do let me know how to uninstall the driver I am new here too would like to try the bfgminer also.

As for your problem look under your power settings if the pc is not closing the usb hubs. Post your .bat file here maybe there is a mistake in that.
newbie
Activity: 42
Merit: 0
Yes, I have the hotplug set to 30, should I change it?Huh

Yes if this doesnt work I will try BFGminer,

Anyone has any experience this problem? what might be the cause of this?

I only have 1 Gridseed running before I buy more, but wanted to see how it works first

Thanks again for all your help

Oren
legendary
Activity: 3654
Merit: 8909
https://bpip.org
Thanks

but the problem happens even when I mine small difficulty coins, after about 2-5 minutes CGminer stop submitting shares... I can wait for over an hour and the total number of shares submitted remains the same...

the only way ot make it work again is to shut down CGminer, take the USB cable out and reconnect and then it will work again for a few minutes.

Anyone has any advice?

Thanks

Have you tried reconnecting the USB cable with cgminer still running? Make sure to run it with hotplug parameter.

If that doesn't work try bfgminer (you'll need to uninstall Zadig drivers).
newbie
Activity: 42
Merit: 0
Thanks

but the problem happens even when I mine small difficulty coins, after about 2-5 minutes CGminer stop submitting shares... I can wait for over an hour and the total number of shares submitted remains the same...

the only way ot make it work again is to shut down CGminer, take the USB cable out and reconnect and then it will work again for a few minutes.

Anyone has any advice?

Thanks
hero member
Activity: 519
Merit: 502
Anyone can help a newbie out please

I got my gridseed, connected it with my laptop using the 3.7.2 CGminer for gridseed and set up my pools. I am mining at the switching profit pool at waffle.

For some reason CGminer stop reporting shares being accepted after 2-5 minutes and only shows the difficulty change on the pool and informing me when blocks are being found but it stops to submitting shares.

There is no error code and the reported hash rate is about 362KH (850MH). When I restart CGminer I get error message that there is no device found but there is no error prior to me restarting CGminer. What I have to do to get it working again is close CGminer remove the USB cable and put it back in and then open CGminer again. It will work for a few minutes and then stop submitting shares again....

I disabled the go to sleep mode on the laptop so I am not sure why this keeps on happening.

I know its not a pool problem because my GPU rig is working fine at waffle and the problem is happening even when I switch to a different pool

Anyone has any thought or suggestions?

Please help

Thanks


Just let it run. I am new here to I seem to be having different problems. But with waffle please take note that it changes difficulty and therefore it takes longer to mine coins. For example if the pool switches from Litecoin to Doge it will find more shares. Let it run for about 24 hrs and see how it goes. If you like try and mine https://dgc.d2.cc/index.php mine dgc here they have small difficulty and you can always trade them for btc which is what waffle does. I have been switching between them to see the best result not sure which one to use.
newbie
Activity: 42
Merit: 0
Anyone can help a newbie out please

I got my gridseed, connected it with my laptop using the 3.7.2 CGminer for gridseed and set up my pools. I am mining at the switching profit pool at waffle.

For some reason CGminer stop reporting shares being accepted after 2-5 minutes and only shows the difficulty change on the pool and informing me when blocks are being found but it stops to submitting shares.

There is no error code and the reported hash rate is about 362KH (850MH). When I restart CGminer I get error message that there is no device found but there is no error prior to me restarting CGminer. What I have to do to get it working again is close CGminer remove the USB cable and put it back in and then open CGminer again. It will work for a few minutes and then stop submitting shares again....

I disabled the go to sleep mode on the laptop so I am not sure why this keeps on happening.

I know its not a pool problem because my GPU rig is working fine at waffle and the problem is happening even when I switch to a different pool

Anyone has any thought or suggestions?

Please help

Thanks
legendary
Activity: 1270
Merit: 1000
Yes the hashrate displayed is basically (time elapsed x some constant x frequency x 5). So in that sense, hardware errors don't affect hashrate, at all. The way I do it, increment a hashes variable and time_spent_hashing variable, when a HW error occurs the hashes isn't incremented, but the time_spent_hashing is, and thus hashrate drops. That is the way it should be IMO, to get an accurate estimation of how HW errors affect the hashrate. Not using any of those, but Lighningasic firmware (which uses cpuminer) has per chip auto overclocking ATM.

Yea, I knew that about cgminer. I think both are beneficial...but yes, the hashrate cgminer provides does not take into account HW errors. I believe WU shows hashrate minus HW errors but it is currently not accurate/broken. I suspect no one has looked at that part of the code to make it work with Gridseed miners.
legendary
Activity: 1270
Merit: 1000
Prolly being biased, but you guys should throw away the Rpi and switch to Lightningasic firmware, we now have an auto-overclocking feature that will overclock each individual chip (5 chips per Gridseed miner). Also the reject rate is close to 0, I've been getting 99.91% accepted running over 24 hours at Ghash.io.
BTW, Jack is making a test rig with 100 miners connected on a single controller, I will have a pic up to prove it.

Thanks sandor111. I actually have a few wiibox's that I have never used. Will load up your firmware and let you know how it does. Great job on tuning per chip as I have seen that each chip can be pushed to different levels.

Edit: threw away my Pi over a week ago!  (threw away=returned to store)  Cheesy
legendary
Activity: 3654
Merit: 8909
https://bpip.org
Yes the hashrate displayed is basically (time elapsed x some constant x frequency x 5). So in that sense, hardware errors don't affect hashrate, at all. The way I do it, increment a hashes variable and time_spent_hashing variable, when a HW error occurs the hashes isn't incremented, but the time_spent_hashing is, and thus hashrate drops. That is the way it should be IMO, to get an accurate estimation of how HW errors affect the hashrate. Not using any of those, but Lighningasic firmware (which uses cpuminer) has per chip auto overclocking ATM.

Can you explain (or provide a link to) how the auto overclocking feature works? Thanks.

https://bitcointalksearch.org/topic/m.6155656

Thanks, this sounds good. I have a few controllers laying around so I think I'll check out your firmware.
hero member
Activity: 616
Merit: 500
Yes the hashrate displayed is basically (time elapsed x some constant x frequency x 5). So in that sense, hardware errors don't affect hashrate, at all. The way I do it, increment a hashes variable and time_spent_hashing variable, when a HW error occurs the hashes isn't incremented, but the time_spent_hashing is, and thus hashrate drops. That is the way it should be IMO, to get an accurate estimation of how HW errors affect the hashrate. Not using any of those, but Lighningasic firmware (which uses cpuminer) has per chip auto overclocking ATM.

Can you explain (or provide a link to) how the auto overclocking feature works? Thanks.

https://bitcointalksearch.org/topic/m.6155656
legendary
Activity: 3654
Merit: 8909
https://bpip.org
Yes the hashrate displayed is basically (time elapsed x some constant x frequency x 5). So in that sense, hardware errors don't affect hashrate, at all. The way I do it, increment a hashes variable and time_spent_hashing variable, when a HW error occurs the hashes isn't incremented, but the time_spent_hashing is, and thus hashrate drops. That is the way it should be IMO, to get an accurate estimation of how HW errors affect the hashrate. Not using any of those, but Lighningasic firmware (which uses cpuminer) has per chip auto overclocking ATM.

Can you explain (or provide a link to) how the auto overclocking feature works? Thanks.
hero member
Activity: 616
Merit: 500
This version supports "Per device frequency setting by serial number ":

https://github.com/girnyau/cgminer-gc3355

this version gives me around 10% lesser hashrate then the orginal cgminer .... I did a test with 20 miners ....

I asked for it ... with PM no answer ... so far ...

Sorry to bother you.

I just used your https://github.com/girnyau/cgminer-gc3355

which was compiled in https://bitcointalksearch.org/topic/m.5763819 for the raspberry.

Somehow I'm getting around 10% less kh with the same setup .... then with the orginal cgminer from andreed from here https://bitcointalksearch.org/topic/m.5539257

... Why does this happen ....?

Interesting. I started using the girnyau version recently but have not noticed this. Will take a closer look. The two versions are not much different from comparing the source code. The dtbartle version went away from setting static freq's and now support increments of 25. The version you referenced is an earlier build of dtbartle that had static freq.

I have considered forking the current dtbartle version with the per miner freq part of girnyau but am still undecided on doing static freq's or increments of 25. If I could figure out how to code increments of 5 that would be great. If static then there is not much benefit over just using girnyau's fork.

My miners are all over the map supporting freq's of 850 - 900+. Most of them do 863.

Are you basing your results on the pool reported hashrates? Contrary to what that one poster spams all over various threads the hashrate reported by pools are inaccurate and should not be used as a basis of your miners performance.

Edit: I'm not using a Pi. I found it too unreliable and like you mentioned about 10% lower hashrate.

IMO 25 MHz increments work the best, one of my miners runs stable at 925 MHz, but throws HW errors at 856 MHz. The 25 MHz increments have the lowest PLL frequency and other PLL dividers set at 0. I have also found that the cgminer forks does not take in account the hashing time lost when finding an invalid nonce (HW error).

Interesting. Thanks...hadn't actually looked at the methods they are using to increment. When you say "cgminer doesn't take in account the hashing time lost when finding an invalid nonce (HW error)" are you referring to it's display of hashrate? Are you using dtbartle or girnyau?

Here's a 48 hour run on girnyau. Notice that some of the individual chips are not as good as others. I think someone mentioned perhaps coding freq per chip in the future (might have been bfgminer). I'm going to scale down to increments of 25 on girnyau to see what that does. Also some of these HW errors may be due to the internet connection as I only have 1-2 bars on the mobile hotspot it's hooked up to...not the best setup for testing  Undecided


Yes the hashrate displayed is basically (time elapsed x some constant x frequency x 5). So in that sense, hardware errors don't affect hashrate, at all. The way I do it, increment a hashes variable and time_spent_hashing variable, when a HW error occurs the hashes isn't incremented, but the time_spent_hashing is, and thus hashrate drops. That is the way it should be IMO, to get an accurate estimation of how HW errors affect the hashrate. Not using any of those, but Lighningasic firmware (which uses cpuminer) has per chip auto overclocking ATM.
sr. member
Activity: 737
Merit: 262
Me, Myself & I
Anyone using CGWatcher with bfg or cgminer on the gridseeds? if yes does it work good?
I'm using it with bfgminer. But I'm using first version of bfgminer that supports gridseeds and dualminers. That version doesn't report well asic miners to cgwatcher so actual hashrate is far from acurate. Meaning it's not possible using restarts when hashrate goes down. Last version I tried was not supporting dualminers so I didn't tried it with cgwatcher.
hero member
Activity: 519
Merit: 502
Having a bit of a problem here I am running one gridseed miner on windows xp for some reason it goes into Ph/s and now Th/s. Though it is accepting shares. One thing I did was later I added another pool now everytime it clocks up and change pool and it slowly clocks down. Any body having same problems?
newbie
Activity: 50
Merit: 0
Hi, I need some help please.
I'm running one GridSeed with Cgminer and I used Zadig to replace the driver.
I changed the conf and I let it run, but now I'm having problem because even if it is running at 361 kh/s it is not accepting shares!

I waited one hour and nothing new.

Does someone had the same problem?

Thank you
hero member
Activity: 616
Merit: 500
Prolly being biased, but you guys should throw away the Rpi and switch to Lightningasic firmware, we now have an auto-overclocking feature that will overclock each individual chip (5 chips per Gridseed miner). Also the reject rate is close to 0, I've been getting 99.91% accepted running over 24 hours at Ghash.io.
BTW, Jack is making a test rig with 100 miners connected on a single controller, I will have a pic up to prove it.
Pages:
Jump to: