Pages:
Author

Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 100. (Read 5805523 times)

vs3
hero member
Activity: 622
Merit: 500
Doesn't really make sense since if it can talk to it, it will mine on it.
If it can't mine on it, then that would be coz it can't talk to it thus it can't tell it to turn the led off.

It is possible to enable/disable a device using the USB menu. I have sometimes slow nanofurys because of several reasons. To find them I disable and wait. Then I try to find the cold one. If the LED would be switched off, it would be much easier.

Disable doesn't currently turn them off, it just stops sending them work because the init sequence is involved and once they're running I try and not visit the init/shutdown code as the driver design assumes it will only ever be done once and prefers to just drop the device if it fails and lets it be hotplugged again if need be. I can revisit it.

actually I think we're talking about two separate features (that are missing in that sense) :
- Identify - the LED can be controlled independently of the device' power; Just flickering the LED would be sufficient for what rgr_rgr wants;
- power-off/on - main "power switch" (if we can call it so) within each NanoFury can also be flipped. This might be helpful when testing for possibly overloaded hub without having to physically remove the device.
newbie
Activity: 13
Merit: 0
thanks Kano, I thought I tracked it to cgminer, but was a prob in my own code :-) Great soft!
I've got a problem with API command addpool. It looks like it always forces username to lowercase. It looks neat, however when using P2P pools and using bitcoin address as a username this is quite a problem.

Version I'm using is cgminer 4.1.0 (embedded in Terraminer IV). I do not really dare to try to fix this on my own and recompile as it might be tricky to compile for their embedded linux.

Are there any workarounds?
No it doesn't.

(also note that whatever Terraminer does to cause this, we don't in cgminer)
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
I've got a problem with API command addpool. It looks like it always forces username to lowercase. It looks neat, however when using P2P pools and using bitcoin address as a username this is quite a problem.

Version I'm using is cgminer 4.1.0 (embedded in Terraminer IV). I do not really dare to try to fix this on my own and recompile as it might be tricky to compile for their embedded linux.

Are there any workarounds?
No it doesn't.

(also note that whatever Terraminer does to cause this, we don't in cgminer)
newbie
Activity: 13
Merit: 0
Edited: my own problem, disregard  Angry




I've got a problem with API command addpool. It looks like it always forces username to lowercase. It looks neat, however when using P2P pools and using bitcoin address as a username this is quite a problem.

Version I'm using is cgminer 4.1.0 (embedded in Terraminer IV). I do not really dare to try to fix this on my own and recompile as it might be tricky to compile for their embedded linux.

Are there any workarounds?
legendary
Activity: 1190
Merit: 1000
Off topic, but the translation from English to Malay done poorly by google translator  Cheesy
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
Hi any body here knows where do can i buy CGMINER ASIC in singapore and how much each Smiley

Thanks.
Tidak pasti apa yang anda maksudkan tetapi cuba menggunakan google translate jika bahasa inggeris anda adalah miskin.
Saya menganggap anda benar-benar bermakna peranti ASIC perlombongan yang bekerja dengan cgminer.
Cukup banyak mana-mana peranti ASIC - lihat senarai dalam post di atas.
Sudah tentu teks ini telah dicipta dengan google translate juga Smiley
Juga ambil perhatian bahawa pautan di atas mengabaikan fakta bahawa kebanyakan pembekal akan merobek anda - harga mereka adalah di atas apa yang anda akan peroleh.

Not sure what you mean but try using google translate if your english is poor.
I presume you actually mean a mining ASIC device that works with cgminer.
Pretty much any ASIC device - see the list in the post above.
Of course this text was created with google translate also Smiley
Also note that the link above ignores the fact that most of the suppliers will rip you off - their price is above what you will earn.

And in case you don't speak Malay Smiley
不知道你的意思,但尝试使用谷歌翻译,如果你的英语很差。
我相信你的意思采矿ASIC器件,与cgminer工作。
几乎任何ASIC器件 - 参见上面的帖子列表。
当然,这个文本是与谷歌翻译也创造了Smiley
另外请注意,上面的链接忽略了一个事实,大多数供应商将撕裂你了 - 他们的价格高于你能挣到多少。
legendary
Activity: 1190
Merit: 1000
Hi any body here knows where do can i buy CGMINER ASIC in singapore and how much each Smiley

Thanks.

Which one you need, cgminer or asic?
cgminer is the software & it's free.
If looking for asic, there is many manufacture https://bitcointalksearch.org/topic/guide-dogies-comprehensive-manufacturer-trustworthiness-guide-1st-feb-2016-456691
legendary
Activity: 1190
Merit: 1000
Just make sure you've got pleanty of ram and hardrive space for mxe. I had a 10 Gig virtual drive setup and mine stopped when it somehow filled it. Mine took alot less than 3 days with those requirements filled


Nice, i already set 50G on virtual box, hopefully it's will enough  Cheesy
I only run them 12 hour a day, that's why it's take so long. Now i will run them 24 H until finish  Grin
hero member
Activity: 546
Merit: 500
Just make sure you've got pleanty of ram and hardrive space for mxe. I had a 10 Gig virtual drive setup and mine stopped when it somehow filled it. Mine took alot less than 3 days with those requirements filled

legendary
Activity: 1190
Merit: 1000
New release: version 4.3.0, 18th April 2014

Mainly new driver updates. Uploaded 32 bit linux binaries as well now.


Human readable changelog:

........
- Fixes for building on windows.
- ........


Thanks ck  Grin
Going to try on mingw after finish installing mxe.
mxe make process already run for 3 days but still not finish  Shocked
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
New release: version 4.3.0, 18th April 2014

Mainly new driver updates. Uploaded 32 bit linux binaries as well now.


Human readable changelog:

- Spondoolies driver. Note this is for dedicated hardware attached to a beaglebone so the code should not be compiled into a generic use-everywhere binary.
- Add API output for spondoolies driver.
- Add temperature to spondoolies API output.
- Update to bi*fury driver (bxf) to support many chips, it will report up to 6 chips as HXF for hex*fury and more than that generically as MXF which currently is how the onestring miners appear until newer firmware comes out uniquely identifying them.
- Fixed the output for the proper amount of chips in *XF devices.
- Fix for solo mining to detect when we are mining on an orphan branch and switch to the correct one.
- Fix for syslog.
- Fixes for building on windows.
- Much faster startup for hashfast devices, the more devices the bigger the speedup.


Full changelog:

- Put sleep in spond hash instead of queue full function
- Remove unused function for when compiled without curses
- Fix typo
- Add temperature rate, front, rear and device temperature to spond API output
- Limit bxf sleep in bxf_scan to 100ms minimum for strings of many chips
- -Werror=format-security error on driver-bitmain.c
- Fix parameters passed with getblockhash
- Check the block hash with the proper command when looking for orphan chains
- syslog requires a facility ... in more than one place
- Shuffle windows headers included
- Adjust the bxf sleep time according to the number of chips detected
- Fix off by one error in bxf chip count when adjusting device size
- Recalloc correct pointer
- Make instructions associated with winusb error even more explicit
- Add midsing headers to cgminer source in Makefile
- Trivial style changes to mg proto parser
- Trivial style and warning clean ups on spondoolies driver
- Merge spondoolies driver patch
- Call any BXF device with 3-6 chips reported HXF
- Avoid derefrence when calling statline before on hfa device during init
sequence
- Calloc the info structures even on failed hfa reset to prevent later possible
dereference
- Load all hfa devices based on identification alone and defer init sequence
till mining thread init sequence to allow all devices to be recognised rapidly
but each device initialisation not delay others
- Do not do thread shutdown unless thread init succeeded
- Remove unnecessary check for thread_prepare function
- Recognise variations on BXF based on chip value returned in responses
- Provide helper function for recallocing memory
- syslog requires a facility
legendary
Activity: 1288
Merit: 1004
Thank you I will do this tomorrow afternoon and get you the results.


I have a quick question.
I have a clean Win  system all updated and no issues running my OneString Miner setup and cgminer every 8 hrs or so crashes.  I have ran it alone and on another system and it just says it stops working.  It will take multiple tries to get it restarted.
4.2.3 did not fix it either.  I have no problems with any other miners or software I have tried on it to test if it was the system.

I've not seen this on linux, so try a debug build with the instructions here:
http://ck.kolivas.org/apps/cgminer/debug/
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
I have a quick question.
I have a clean Win  system all updated and no issues running my OneString Miner setup and cgminer every 8 hrs or so crashes.  I have ran it alone and on another system and it just says it stops working.  It will take multiple tries to get it restarted.
4.2.3 did not fix it either.  I have no problems with any other miners or software I have tried on it to test if it was the system.

I've not seen this on linux, so try a debug build with the instructions here:
http://ck.kolivas.org/apps/cgminer/debug/
legendary
Activity: 1288
Merit: 1004
I have a quick question.
I have a clean Win  system all updated and no issues running my OneString Miner setup and cgminer every 8 hrs or so crashes.  I have ran it alone and on another system and it just says it stops working.  It will take multiple tries to get it restarted.
4.2.3 did not fix it either.  I have no problems with any other miners or software I have tried on it to test if it was the system.
legendary
Activity: 1190
Merit: 1000

This is the closest update for that windows build file and I at least put the details I got from the issues area on mxe's github page https://github.com/mxe/mxe/issues/338

Here https://github.com/techman05/cgminer/blob/master/windows-build.txt

I should probably try to add it into ckolivias/cgminer but most of my other files in my github fork of cgminer that I tried to tweak should be purged or put in the closet sot of speak

Thanks, this is what i looking for  Grin
hero member
Activity: 546
Merit: 500
I see, now i need to ask google about mxe  Cheesy or you maybe can add some guide to windows-build.txt  Roll Eyes
That file is horribly outdated from the GPU days and since I started cross compiling with mxe there is no way I'm going to try and build it directly on windows or any other way any more, sorry. In fact that windows build file wasn't even made by me if you read it, but a very dedicated user...

No problem  Wink
I will learn mxe step by step  Cheesy

This is the closest update for that windows build file and I at least put the details I got from the issues area on mxe's github page https://github.com/mxe/mxe/issues/338

Here https://github.com/techman05/cgminer/blob/master/windows-build.txt

I should probably try to add it into ckolivias/cgminer but most of my other files in my github fork of cgminer that I tried to tweak should be purged or put in the closet sot of speak
legendary
Activity: 1190
Merit: 1000
I see, now i need to ask google about mxe  Cheesy or you maybe can add some guide to windows-build.txt  Roll Eyes
That file is horribly outdated from the GPU days and since I started cross compiling with mxe there is no way I'm going to try and build it directly on windows or any other way any more, sorry. In fact that windows build file wasn't even made by me if you read it, but a very dedicated user...

No problem  Wink
I will learn mxe step by step  Cheesy
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
After searching on google, look like i found the problem. http://msdn.microsoft.com/en-us/library/windows/desktop/ms737629%28v=vs.85%29.aspx
There is some wrong include on util.h line 32. Base on the article, winsock.h must be include before ws2tcpip.h.
Thanks for your investigating. I build all the official binaries with mxe, so it works either way, but I have shuffled things slightly based on that info and removed the windows.h include entirely. I have no idea what effect that will have on other build environments  Tongue

I see, now i need to ask google about mxe  Cheesy or you maybe can add some guide to windows-build.txt  Roll Eyes
That file is horribly outdated from the GPU days and since I started cross compiling with mxe there is no way I'm going to try and build it directly on windows or any other way any more, sorry. In fact that windows build file wasn't even made by me if you read it, but a very dedicated user...
legendary
Activity: 1190
Merit: 1000
After searching on google, look like i found the problem. http://msdn.microsoft.com/en-us/library/windows/desktop/ms737629%28v=vs.85%29.aspx
There is some wrong include on util.h line 32. Base on the article, winsock.h must be include before ws2tcpip.h.
Thanks for your investigating. I build all the official binaries with mxe, so it works either way, but I have shuffled things slightly based on that info and removed the windows.h include entirely. I have no idea what effect that will have on other build environments  Tongue

I see, now i need to ask google about mxe  Cheesy or you maybe can add some guide to windows-build.txt  Roll Eyes
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
After searching on google, look like i found the problem. http://msdn.microsoft.com/en-us/library/windows/desktop/ms737629%28v=vs.85%29.aspx
There is some wrong include on util.h line 32. Base on the article, winsock.h must be include before ws2tcpip.h.
Thanks for your investigating. I build all the official binaries with mxe, so it works either way, but I have shuffled things slightly based on that info and removed the windows.h include entirely. I have no idea what effect that will have on other build environments  Tongue
Pages:
Jump to: