Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 834. (Read 5806004 times)
July 19, 2011, 07:25:11 PM
thanks.. ill script it.
July 19, 2011, 07:19:23 PM
There isn't a binary distribution packaging command, only a source one (make distdir). Ycros has been packaging the 3 necessary dlls, the 2 .cl files, the executable and READMEs himself into zips. He may have automated it for himself, I'm not sure.
July 19, 2011, 07:06:00 PM
quick question re: mingw.
Once I have run ./configure and make.. how do i package the cgminer.exe and the dependant dlls.
Been making some pretty cpu specific compiles.. just not sure what the cmd is to package them after compile.
Once I have run ./configure and make.. how do i package the cgminer.exe and the dependant dlls.
Been making some pretty cpu specific compiles.. just not sure what the cmd is to package them after compile.
July 19, 2011, 06:53:37 PM
Updated tree: Re-enabled the watchdog thread code (which was disabled in 1.3.0), reworked to be smarter and only restart threads not waiting on work and have gone idle for some other reason (gpu overheated, gpu code stuck etc.).
July 19, 2011, 03:59:22 PM
Code:
zenitur@athlon64x2 ~/cgminer-1.3.0 $ cgminer -o http://pool.itzod.ru:8344 -u Zenitur_0 -p apetytype -I 10
Summary of per device statistics:
GPU 0: [33.1 Mh/s] [Q:2 A:2 R:0 HW:0 E:100% U:1.17/m]
zenitur@athlon64x2 ~/cgminer-1.3.0 $ cgminer -o http://pool.itzod.ru:8344 -u Zenitur_0 -p apetytype -I 10 -T --cpu-threads 1
Summary of per device statistics:
GPU 0: [33.9 Mh/s] [Q:2 A:0 R:0 HW:0 E:0% U:0.00/m]
CPU 0: [0.0 Mh/s] [Q:1 A:0 R:0 HW:0 E:0% U:0.00/m]
zenitur@athlon64x2 ~/cgminer-1.3.0 $ cgminer -o http://pool.itzod.ru:8344 -u Zenitur_0 -p apetytype -I 10 -T --cpu-threads 0
Summary of per device statistics:
GPU 0: [32.5 Mh/s] [Q:2 A:0 R:0 HW:0 E:0% U:0.00/m]
zenitur@athlon64x2 ~/cgminer-1.3.0 $ cgminer -o http://pool.itzod.ru:8344 -u Zitur_0 -p apetytype -I 10 -T --cpu-threads 1 --algo sse2_64
Summary of per device statistics:
GPU 0: [32.2 Mh/s] [Q:2 A:0 R:0 HW:0 E:0% U:0.00/m]
CPU 0: [0.0 Mh/s] [Q:1 A:0 R:0 HW:0 E:0% U:0.00/m]
zenitur@athlon64x2 ~/cgminer-1.3.0 $ cgminer -o http://pool.itzod.ru:8344 -u Zenitur_0 -p apetytype -I 10 -T --cpu-threads 1 --algo cryptopp
Summary of per device statistics:
GPU 0: [32.6 Mh/s] [Q:2 A:0 R:0 HW:0 E:0% U:0.00/m]
CPU 0: [0.0 Mh/s] [Q:1 A:0 R:0 HW:0 E:0% U:0.00/m]
0.0 Mh/s with CPU. Why? Linux.
P.S. I'm using 1 thread because of nvidia driver loads 1 CPU core on 100% when working.
July 19, 2011, 03:49:12 PM
I'm running 2 6990s (both with the OC switch on the overclocked position, but no further OCing) on a single-core Sempron 140. With cgminer, one card gets the expected performance, but the other one is incredibly low (40-50Mhash per GPU). I'm using an intensity of 9 as suggested in the original post for 6990s.
This is the exit output:
GPU 0: [395.7 Mh/s] [Q:91 A:85 R:3 HW:0 E:93% U:5.55/m]
GPU 1: [395.6 Mh/s] [Q:92 A:96 R:1 HW:0 E:104% U:6.20/m]
GPU 2: [39.4 Mh/s] [Q:12 A:5 R:0 HW:0 E:42% U:3.13/m]
GPU 3: [46.4 Mh/s] [Q:13 A:10 R:0 HW:0 E:83% U:5.95/m]
This is the exit output:
GPU 0: [395.7 Mh/s] [Q:91 A:85 R:3 HW:0 E:93% U:5.55/m]
GPU 1: [395.6 Mh/s] [Q:92 A:96 R:1 HW:0 E:104% U:6.20/m]
GPU 2: [39.4 Mh/s] [Q:12 A:5 R:0 HW:0 E:42% U:3.13/m]
GPU 3: [46.4 Mh/s] [Q:13 A:10 R:0 HW:0 E:83% U:5.95/m]
July 19, 2011, 01:28:47 PM
July 19, 2011, 01:06:57 PM
Yesterday i had the same problem, the miner crashing after ~10seconds. The problem was wrong login/url details, i fixed them and problem solved 
July 19, 2011, 10:28:00 AM
how does one specify phatk110714.cl or poclbm110717.cl ?
One does not. The poclbm kernel is far far behind the phatk kernel in speed and any hardware that can run the phatk kernel is given it. The poclbm kernel is reserved for nvidia cards and ATI 4x cards only. The phatk kernel, even without bitalign patching, crashes on these lesser mining cards.Phoenix with phatk worked on my 4850, and that was faster than poclbm.
July 19, 2011, 09:38:45 AM
likely using a urlX counter in the parameters will be the solution
Please don't; JSON has nice shiny arrays for that sort of thing.Quote from: xcooling
then spaces in passwords and @ in usernames is not an issue ;-P
OK, I'll bite: Passwords with colons in them, anyone? :-PThe best string to parse is one which you don't need to parse at all.
July 19, 2011, 09:34:48 AM
lol..
u prase the string from right to left..
then spaces in passwords and @ in usernames is not an issue ;-P
Json encoded is prefered
connections: [
{url: "http://foo.example.org:8332", username: "bar", password: "baz"},
{url: "http://bar.example.org:8332", username: "baz", password: "quux"}
],
…
u prase the string from right to left..
then spaces in passwords and @ in usernames is not an issue ;-P
Json encoded is prefered
connections: [
{url: "http://foo.example.org:8332", username: "bar", password: "baz"},
{url: "http://bar.example.org:8332", username: "baz", password: "quux"}
],
…
July 19, 2011, 09:30:11 AM
I don't like the one-string "http://bar:[email protected]:8332" style.
(a) it's ugly and human-unfriendly
(b) you'll almost certainly get parsing that thing wrong (passwords with spaces in them, anyone?)
(c) this way you can use additional options, like different timeouts or "ignore this host's longpoll offer, it's broken" options, per connection.
(d) there are pools like deepbit that have an @ in the username...(a) it's ugly and human-unfriendly
(b) you'll almost certainly get parsing that thing wrong (passwords with spaces in them, anyone?)
(c) this way you can use additional options, like different timeouts or "ignore this host's longpoll offer, it's broken" options, per connection.
Which reminds me, long polling still isn't working with deepbit.
July 19, 2011, 09:04:00 AM
Hi,
for JSON a sensible multi-host config would look like this:
{
…
connections: [
{url: "http://foo.example.org:8332", username: "bar", password: "baz"},
{url: "http://bar.example.org:8332", username: "baz", password: "quux"}
],
…
}
I don't like the one-string "http://bar:[email protected]:8332" style.
(a) it's ugly and human-unfriendly
(b) you'll almost certainly get parsing that thing wrong (passwords with spaces in them, anyone?)
(c) this way you can use additional options, like different timeouts or "ignore this host's longpoll offer, it's broken" options, per connection.
for JSON a sensible multi-host config would look like this:
{
…
connections: [
{url: "http://foo.example.org:8332", username: "bar", password: "baz"},
{url: "http://bar.example.org:8332", username: "baz", password: "quux"}
],
…
}
I don't like the one-string "http://bar:[email protected]:8332" style.
(a) it's ugly and human-unfriendly
(b) you'll almost certainly get parsing that thing wrong (passwords with spaces in them, anyone?)
(c) this way you can use additional options, like different timeouts or "ignore this host's longpoll offer, it's broken" options, per connection.
July 19, 2011, 08:52:08 AM
Updated git tree:
- The order of urls/user/pass is not critical any more so long as you give it the same number of urls and credentials
- json config file is now working again. json does not allow the same entry to be used twice so for the time being, to get two or more pools working you need to create a config file for each and pass multiple -c to cgminer. I'm considering options for how to tackle this, but likely using a urlX counter in the parameters will be the solution I go with. Or move to a different format entirely.
- The order of urls/user/pass is not critical any more so long as you give it the same number of urls and credentials
- json config file is now working again. json does not allow the same entry to be used twice so for the time being, to get two or more pools working you need to create a config file for each and pass multiple -c to cgminer. I'm considering options for how to tackle this, but likely using a urlX counter in the parameters will be the solution I go with. Or move to a different format entirely.
July 19, 2011, 06:34:31 AM
I assume the json cfg supports multiple pools ?
It doesn't even support a single server yet...see http://forum.bitcoin.org/index.php?topic=28402.msg378597#msg378597
July 19, 2011, 06:23:34 AM
I'm not sure if the config file works. Probably not yet. I spent an awful lot of time getting this feature working and then wanted to release it because the demand for it was high. I was hoping people would test it and then I could worry about the interface...
July 19, 2011, 06:16:07 AM
yeah, thats why i was asking ;-P
I assume the json cfg supports multiple pools ?
I assume the json cfg supports multiple pools ?
Code:
{
"_comment1" : "Any long-format command line argument ",
"_comment2" : "may be used in this JSON configuration file",
"url" : "http://127.0.0.1:8332",
"user" : "rpcuser",
"pass" : "rpcpass",
"url" : "http://127.0.0.1:8334",
"user" : "rpcuser2",
"pass" : "rpcpass2",
"algo" : "sse2_64",
"threads" : "4",
"quiet" : true
}
July 19, 2011, 06:07:39 AM
how does one specify phatk110714.cl or poclbm110717.cl ?
One does not. The poclbm kernel is far far behind the phatk kernel in speed and any hardware that can run the phatk kernel is given it. The poclbm kernel is reserved for nvidia cards and ATI 4x cards only. The phatk kernel, even without bitalign patching, crashes on these lesser mining cards. July 19, 2011, 06:04:45 AM
how does one specify phatk110714.cl or poclbm110717.cl ?
July 19, 2011, 05:00:15 AM
yes
Jump to: