Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 221. (Read 5805531 times)
September 23, 2013, 09:17:41 PM
September 23, 2013, 08:34:52 PM
New debug executables uploaded.
All done and started, now we just have to play the waiting game.
I haven't seen it crash for at least 2-3 days on 3.4.3
I'm currently swamped with other work and probably need a small break from regular cgminer coding anyway.
Still running without that crash non stop since the 17th lol.
3.4.3 seems to be the most stable so fair. Still running the debug version though, so if/when it does we will catch it.
September 23, 2013, 08:25:47 PM
I'm trying to install CGminer on a Pi.
...
Or is there a later post in the thread I haven't found that would work better?
Use current cgminer....
Or is there a later post in the thread I haven't found that would work better?
It compiles fine on an RPi (though all earlier versions did also - so I've no idea what is corrupted on your RPi)
RPi binaries up to 3.4.2 are also here: https://github.com/kanoi/cgminer-binaries
There may, indeed, be something wrong with my Pi. Many people say Minepeon works great but it has never worked on mine.
I've been wondering if it's some kind of firmware version or something.
Thanks for pointing out the RPi binaries. Not sure what to do with them but I'll give it a try.
September 23, 2013, 06:25:39 PM
I'm trying to install CGminer on a Pi.
...
Or is there a later post in the thread I haven't found that would work better?
Use current cgminer....
Or is there a later post in the thread I haven't found that would work better?
It compiles fine on an RPi (though all earlier versions did also - so I've no idea what is corrupted on your RPi)
RPi binaries up to 3.4.2 are also here: https://github.com/kanoi/cgminer-binaries
September 23, 2013, 06:21:20 PM
Hello,
I'm running cgminer3.4.3 on windows.
I have 24 bitburners XX and 1 X, total 25 boards and 490 chips.
I try to run with the options:
--avalon-options 115200:49:10:d:300 --bitburner-voltage 1290 --avalon-temp 55 --avalon-cutoff 65 --avalon-fan 80 --queue 4
And cgminer just closes with no error no nothing outputted (nothing also on a cmd line)
But running:
--bitburner-voltage 1290 --avalon-temp 55 --avalon-cutoff 65 --avalon-fan 80 --queue 4
It mines ok, no problems whatsoever.
What am i doing wrong?
Are they chained or USB each one? i.e. '49'.I'm running cgminer3.4.3 on windows.
I have 24 bitburners XX and 1 X, total 25 boards and 490 chips.
I try to run with the options:
--avalon-options 115200:49:10:d:300 --bitburner-voltage 1290 --avalon-temp 55 --avalon-cutoff 65 --avalon-fan 80 --queue 4
And cgminer just closes with no error no nothing outputted (nothing also on a cmd line)
But running:
--bitburner-voltage 1290 --avalon-temp 55 --avalon-cutoff 65 --avalon-fan 80 --queue 4
It mines ok, no problems whatsoever.
What am i doing wrong?
--avalon-freq 300
Also, you need to run it in a command line and log the output - coz it will tell you what is wrong
cgminer ....... blah ...... blah ..... 2> cgminer.log
September 23, 2013, 03:44:43 PM
Hello,
I'm running cgminer3.4.3 on windows.
I have 24 bitburners XX and 1 X, total 25 boards and 490 chips.
I try to run with the options:
--avalon-options 115200:49:10:d:300 --bitburner-voltage 1290 --avalon-temp 55 --avalon-cutoff 65 --avalon-fan 80 --queue 4
And cgminer just closes with no error no nothing outputted (nothing also on a cmd line)
But running:
--bitburner-voltage 1290 --avalon-temp 55 --avalon-cutoff 65 --avalon-fan 80 --queue 4
It mines ok, no problems whatsoever.
What am i doing wrong?
I'm running cgminer3.4.3 on windows.
I have 24 bitburners XX and 1 X, total 25 boards and 490 chips.
I try to run with the options:
--avalon-options 115200:49:10:d:300 --bitburner-voltage 1290 --avalon-temp 55 --avalon-cutoff 65 --avalon-fan 80 --queue 4
And cgminer just closes with no error no nothing outputted (nothing also on a cmd line)
But running:
--bitburner-voltage 1290 --avalon-temp 55 --avalon-cutoff 65 --avalon-fan 80 --queue 4
It mines ok, no problems whatsoever.
What am i doing wrong?
September 23, 2013, 03:42:19 PM
Decided to just use the prebuilt Binaries instead of compiling it for Windows XP 32bit because I ran into too many problems. I can get CGminer to load but it is only recognizing the card in the first PCI-E slot. I have a dual card system with an Invidia gt520 in the first PCI-E slot and the XFX 5870 HD. Cgminer will only mine on the Nvidia card although it gives and error of Multiple OpenCl devices and ADL devices being misdetected/mismatched. I tried to use the -n function in a bat file but I get a brief flash of readout and then the program shuts down. I have been able to mine BTC on OpenCL via GIUminer on the ATI card but for some reason it's giving me errors for scrypt mining with CGminer. Any suggestions?
1. Is there anyway to generate a Log file so I can read the error output message?
2. Is there a command to put in the Bat file to ignore the primary card (nvidia) and only work off the secondary card (ati). Since I can't get -n command to function it I don't even know if it is being detected? It is being detected by cpuz and the system registry and I have been able to mine BTC with it but not Litecoin in scrypt?
Add a "pause" to your batch file, e.g.:1. Is there anyway to generate a Log file so I can read the error output message?
2. Is there a command to put in the Bat file to ignore the primary card (nvidia) and only work off the secondary card (ati). Since I can't get -n command to function it I don't even know if it is being detected? It is being detected by cpuz and the system registry and I have been able to mine BTC with it but not Litecoin in scrypt?
cgminer.exe -c gristle.conf -n
pause
exit
It will wait for you to hit any key before it exits cmd window.
In your gristle.conf file add the line:
"device" : "1",
and cgminer will only enable device 1.
TY I'll give it a try tonight. I think my problem is system RAM. As I have read it is critical to scrypt mining..I'm only running 2GB on an old socket 939 ASUS board with a XFX 5870 HD 1GB memory.
September 23, 2013, 03:40:22 PM
I'm trying to install CGminer on a Pi.
My mining device is a BFL Little Single.
I found the post (#7259) by ChipGeek and it went just great until I got to 'sudo make'
(if it matters, I used the same thing he did at the Configure CGminer step 'sudo ./autogen.sh --enable-bitforce --with-libudev')
it ran for a little while looking good until it spit out
I realize this is an old post and things in the software world evolve.
I don't speak whatever language this stuff is.
Someone please tell me what I need to make this successful.
Or is there a later post in the thread I haven't found that would work better?
My mining device is a BFL Little Single.
I found the post (#7259) by ChipGeek and it went just great until I got to 'sudo make'
(if it matters, I used the same thing he did at the Configure CGminer step 'sudo ./autogen.sh --enable-bitforce --with-libudev')
it ran for a little while looking good until it spit out
Code:
CC libusb_1_0_la-io.lo
In file included from /usr/include/signal.h:356:0,
from io.c:23:
/usr/include/arm-linux-gnueabihf/bits/sigstack.h:1:26: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'definitions'
/usr/include/arm-linux-gnueabihf/bits/sigstack.h:5:40: error: unknown type name 'you'
/usr/include/arm-linux-gnueabihf/bits/sigstack.h:5:48: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'redistribute'
/usr/include/arm-linux-gnueabihf/bits/sigstack.h:5:48: error: unknown type name 'redistribute'
/usr/include/arm-linux-gnueabihf/bits/sigstack.h:7:58: error: unknown type name 'either'
/usr/include/arm-linux-gnueabihf/bits/sigstack.h:8:12: error: expected '=', ',', ';', 'asm' or '__attribute__' before numeric constant
/usr/include/arm-linux-gnueabihf/bits/sigstack.h:11:30: error: unknown type name 'without'
/usr/include/arm-linux-gnueabihf/bits/sigstack.h:11:43: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'the'
/usr/include/arm-linux-gnueabihf/bits/sigstack.h:11:43: error: unknown type name 'the'
/usr/include/arm-linux-gnueabihf/bits/sigstack.h:16:42: error: expected identifier or '(' before 'if'
make[5]: *** [libusb_1_0_la-io.lo] Error 1
make[5]: Leaving directory `/usr/src/cgminer/compat/libusb-1.0/libusb'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/usr/src/cgminer/compat/libusb-1.0'
make[3]: *** [all] Error 2
make[3]: Leaving directory `/usr/src/cgminer/compat/libusb-1.0'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/usr/src/cgminer/compat'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/cgminer'
make: *** [all] Error 2
I realize this is an old post and things in the software world evolve.
I don't speak whatever language this stuff is.
Someone please tell me what I need to make this successful.
Or is there a later post in the thread I haven't found that would work better?
September 20, 2013, 05:43:49 PM
One of the most frustrating parts about mining...
And fun/interesting!
...is the vast number of versions of libraries, SDKs, etc that can be mixed and matched.
No doubt.
It is just that what I thought would be a simple upgrade ended bringing the whole rig down... no longer works at all.
AND, on top of it all, all the old sources I used to build the working machine are no longer available online. (Teaches me to rely on other people hosting stuff. :p)
What error are you getting ? If it linux I'd think you'd just do app-get update -- fix missing and let it run .Maybe next update.to cg miner , it should run the commands to get what it wants and the auto file before it starts to check. If I hit this I would have coppied the config file and re cloned, enabled and made fresh. look for the link to butterfly labs in posts I've been talking in. It has the command files needed for 4.3.3 and where to put them.
September 13, 2013, 08:40:10 AM
Where can I find documentation for Block Erupters? I'd like to write my own driver.
cgminer version 3.1.1 
Look for the specs on the Icarus FPGA since that is the interface BE use. Seems plausible to me anyway.
They all work the same way ... just different speeds and different core counts.
CMR does, however, also have a glasswalker bitream that has extra options, but the other 4 are ... well ... missing any useful functionality other than simply hash 4 billion times in a row.
That's why an AMU costs SFA to make and why Friedcat has literally made something like a million selling them.
All right, thanks.
September 20, 2013, 05:18:22 PM
I don't have the expertise to evaluate this, but I'm wondering about your thoughts on this:
https://github.com/adamvillena/cgminer/commit/ea532254829d8f57dd561eb223129b4f88a41c61#diff-0ff4390339955f5d81e4a259179a42cd
That code is simply unrolling the code as the compiler is already told to do. That means the code generated will be identical. https://github.com/adamvillena/cgminer/commit/ea532254829d8f57dd561eb223129b4f88a41c61#diff-0ff4390339955f5d81e4a259179a42cd
September 20, 2013, 05:11:20 PM
I don't have the expertise to evaluate this, but I'm wondering about your thoughts on this:
https://github.com/adamvillena/cgminer/commit/ea532254829d8f57dd561eb223129b4f88a41c61#diff-0ff4390339955f5d81e4a259179a42cd
The conclusion that my friend has come to is that this isn't shit. Other people who have tested this guy's modified file have reported identical speeds as before. The thing we don't know is what driver versions people are using. We suspect that the coder is using a newer driver while everyone else who tested this is using an older version. We know for a fact that 12.8 drivers are faster than newer versions, so this could be making up for a bug or crappy change AMD made in their newer drivers. https://github.com/adamvillena/cgminer/commit/ea532254829d8f57dd561eb223129b4f88a41c61#diff-0ff4390339955f5d81e4a259179a42cd
September 20, 2013, 05:04:49 PM
I don't have the expertise to evaluate this, but I'm wondering about your thoughts on this:
https://github.com/adamvillena/cgminer/commit/ea532254829d8f57dd561eb223129b4f88a41c61#diff-0ff4390339955f5d81e4a259179a42cd
https://github.com/adamvillena/cgminer/commit/ea532254829d8f57dd561eb223129b4f88a41c61#diff-0ff4390339955f5d81e4a259179a42cd
September 20, 2013, 04:35:36 PM
Hey, OP. I'm sure this isn't going to be on your priority list, but I'm also sure it'll be a very quick fix.
cgminer will be a big push to standardize hash measurements in writing (since nearly everyone uses it) and the current symbols used are not correct. Just like how we wouldn't write Kwh (kWh) and how we don't write KB/s to represent 1000 B/s (kB/s), the symbols used for hashing should be changed to kH/s and MH/s, GH/s, TH/s, etc.
The little table on the Wikipedia page for kilobyte explains it the same (check out the kilowatt page as well): http://en.wikipedia.org/wiki/Kilobyte
The longer form would likely look like kHash/s or MHash/s.
The PHP script, that I'm pretty sure is still shipped with cgminer, lists it as MHS. That should be updated as well.
Finally, I'm basing this off of using 1000x. If we are actually using 1024 (and I'm pretty sure we aren't), the only change will be an uppercase K.
Edit: The above post still applies, but I'm currently getting input on actually creating a symbol for cryptographic hashing. It seems the entire cryptographic sector doesn't have anything to specifically represent hashes or hashes per second.
cgminer will be a big push to standardize hash measurements in writing (since nearly everyone uses it) and the current symbols used are not correct. Just like how we wouldn't write Kwh (kWh) and how we don't write KB/s to represent 1000 B/s (kB/s), the symbols used for hashing should be changed to kH/s and MH/s, GH/s, TH/s, etc.
The little table on the Wikipedia page for kilobyte explains it the same (check out the kilowatt page as well): http://en.wikipedia.org/wiki/Kilobyte
The longer form would likely look like kHash/s or MHash/s.
The PHP script, that I'm pretty sure is still shipped with cgminer, lists it as MHS. That should be updated as well.
Finally, I'm basing this off of using 1000x. If we are actually using 1024 (and I'm pretty sure we aren't), the only change will be an uppercase K.
Edit: The above post still applies, but I'm currently getting input on actually creating a symbol for cryptographic hashing. It seems the entire cryptographic sector doesn't have anything to specifically represent hashes or hashes per second.
September 13, 2013, 08:13:31 AM
Where can I find documentation for Block Erupters? I'd like to write my own driver.
cgminer version 3.1.1 
September 20, 2013, 10:08:40 AM
One of the most frustrating parts about mining...
And fun/interesting!
...is the vast number of versions of libraries, SDKs, etc that can be mixed and matched.
No doubt.
It is just that what I thought would be a simple upgrade ended bringing the whole rig down... no longer works at all.
AND, on top of it all, all the old sources I used to build the working machine are no longer available online. (Teaches me to rely on other people hosting stuff. :p)
September 20, 2013, 10:00:54 AM
Probably won't help but you have to do it real slowly. I at first did this by wireless and had to do it again though luckily linux I could use the up key after restart on wired to do again.
This is what I followed to get all the files for at least eroupters from https://forums.butterflylabs.com/bitcoin-discussion/3238-super-tutorial-raspberry-pi-raspbian-cgminer-tightvnc-wifi-boot.html
I thought on github it had the filenames to apt-get install for the other sdks for nvidia and amd. After that autogen.sh does the long stuff moving things to the right spots.
Good luck for now.
This is what I followed to get all the files for at least eroupters from https://forums.butterflylabs.com/bitcoin-discussion/3238-super-tutorial-raspberry-pi-raspbian-cgminer-tightvnc-wifi-boot.html
Code:
sudo aptitude install git autoconf libtool libcurl4-openssl-dev libncurses5-dev pkg-config yasm make libusb-1.0-0-dev Will ask "Do you want to continue?", "Y" to say Yes and wait until finish
I thought on github it had the filenames to apt-get install for the other sdks for nvidia and amd. After that autogen.sh does the long stuff moving things to the right spots.
Good luck for now.
September 13, 2013, 07:46:55 AM
Where can I find documentation for Block Erupters? I'd like to write my own driver.
September 20, 2013, 09:59:18 AM
One of the most frustrating parts about mining...
And fun/interesting!
...is the vast number of versions of libraries, SDKs, etc that can be mixed and matched.
September 20, 2013, 09:45:06 AM
One of the most frustrating parts about mining is the vast number of versions of libraries, SDKs, etc that can be mixed and matched.
With the latest Linux 3.4.3 is there a suggested version of:
AMD Catalyst Drivers (AMD_CATALYST_DRIVERS)
AMD APP SDK
Open CL
ADL SDK
to use?
I tried to update to 3.4.3 last night and it nothing seems to compile or work correctly anymore.
Thoughts? Advice?
With the latest Linux 3.4.3 is there a suggested version of:
AMD Catalyst Drivers (AMD_CATALYST_DRIVERS)
AMD APP SDK
Open CL
ADL SDK
to use?
I tried to update to 3.4.3 last night and it nothing seems to compile or work correctly anymore.
Thoughts? Advice?
Jump to: