Search content
Sort by
Showing 20 of 23 results by smurfix
Re: CGMINER GPU bitforce overclock monitor fanspeed RPC in C linux/windows/osx 2.2.1
Dead+Orphan are zero. Only 2 shares after an hour at 370 Mhash/sec, with a 40% reject rate, doesn't look too great.
Well as it seems to work for others here, I'll check over at the p2pool thread.
Well as it seems to work for others here, I'll check over at the p2pool thread.
Re: CGMINER GPU bitforce overclock monitor fanspeed RPC in C linux/windows/osx 2.2.1
Hmm. I just fired up a new p2pool job (default settings, pretty much, except for talking to bitcoind of course 
) and then connected cgminer 2.2.1 to it.
Somehow, this doesn't fill me with confidence WRT getting an adequate return from p2pool:
) and then connected cgminer 2.2.1 to it.Somehow, this doesn't fill me with confidence WRT getting an adequate return from p2pool:
Code:
[2012-01-30 21:08:47] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:08:48] Rejected 00000000.0bfac560.17d1b0c4 GPU 1 thread 3 pool 0
[2012-01-30 21:08:51] Rejected 00000000.8bcfb95f.587deee1 GPU 0 thread 0 pool 0
[2012-01-30 21:08:52] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:08:59] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:09:03] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:09:06] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:09:08] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:09:14] Accepted 00000000.5d6dbc1a.c3b4708e GPU 0 thread 0 pool 0
[2012-01-30 21:09:27] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:09:29] Rejected 00000000.b1fd754a.a40963c3 GPU 0 thread 0 pool 0
[2012-01-30 21:09:31] Rejected 00000000.2af24ce5.0c9d8cca GPU 1 thread 3 pool 0
[2012-01-30 21:09:40] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:09:43] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:10:03] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:10:04] Rejected 00000000.823d886b.03e7ea8a GPU 0 thread 0 pool 0
[2012-01-30 21:10:09] Accepted 00000000.18339988.020e4a54 GPU 1 thread 3 pool 0
[2012-01-30 21:10:13] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:10:17] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:10:33] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:10:38] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:10:48] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:10:56] Accepted 00000000.dadb0773.20b35c1d GPU 1 thread 3 pool 0
[2012-01-30 21:10:56] Accepted 00000000.dded65c8.5fdcc694 GPU 0 thread 0 pool 0
[2012-01-30 21:11:09] Accepted 00000000.7936594f.11a3ce7f GPU 0 thread 0 pool 0
[2012-01-30 21:11:16] Accepted 00000000.80e299be.caf484cb GPU 1 thread 3 pool 0
[2012-01-30 21:11:17] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:11:21] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:11:29] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:11:39] Accepted 00000000.fafd76f3.79ad8cc8 GPU 0 thread 0 pool 0
[2012-01-30 21:11:44] Accepted 00000000.e2283613.344f4379 GPU 1 thread 3 pool 0
[2012-01-30 21:11:47] Accepted 00000000.abee8afd.1be1955c GPU 0 thread 0 pool 0
[2012-01-30 21:11:50] Accepted 00000000.0e06fa8b.b7b2a8ea GPU 1 thread 3 pool 0
[2012-01-30 21:11:57] Accepted 00000000.5931ea9c.ecc3aa6c GPU 0 thread 0 pool 0
[2012-01-30 21:11:59] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:12:03] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:12:06] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:12:11] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:12:12] Rejected 00000000.370dbc90.26abc167 GPU 0 thread 0 pool 0
[2012-01-30 21:12:15] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:12:17] LONGPOLL requested work restart, waiting on fresh work
esp. since many of those Accepts seem to be from another pool I'm load-balancing to.[2012-01-30 21:08:48] Rejected 00000000.0bfac560.17d1b0c4 GPU 1 thread 3 pool 0
[2012-01-30 21:08:51] Rejected 00000000.8bcfb95f.587deee1 GPU 0 thread 0 pool 0
[2012-01-30 21:08:52] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:08:59] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:09:03] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:09:06] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:09:08] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:09:14] Accepted 00000000.5d6dbc1a.c3b4708e GPU 0 thread 0 pool 0
[2012-01-30 21:09:27] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:09:29] Rejected 00000000.b1fd754a.a40963c3 GPU 0 thread 0 pool 0
[2012-01-30 21:09:31] Rejected 00000000.2af24ce5.0c9d8cca GPU 1 thread 3 pool 0
[2012-01-30 21:09:40] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:09:43] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:10:03] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:10:04] Rejected 00000000.823d886b.03e7ea8a GPU 0 thread 0 pool 0
[2012-01-30 21:10:09] Accepted 00000000.18339988.020e4a54 GPU 1 thread 3 pool 0
[2012-01-30 21:10:13] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:10:17] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:10:33] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:10:38] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:10:48] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:10:56] Accepted 00000000.dadb0773.20b35c1d GPU 1 thread 3 pool 0
[2012-01-30 21:10:56] Accepted 00000000.dded65c8.5fdcc694 GPU 0 thread 0 pool 0
[2012-01-30 21:11:09] Accepted 00000000.7936594f.11a3ce7f GPU 0 thread 0 pool 0
[2012-01-30 21:11:16] Accepted 00000000.80e299be.caf484cb GPU 1 thread 3 pool 0
[2012-01-30 21:11:17] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:11:21] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:11:29] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:11:39] Accepted 00000000.fafd76f3.79ad8cc8 GPU 0 thread 0 pool 0
[2012-01-30 21:11:44] Accepted 00000000.e2283613.344f4379 GPU 1 thread 3 pool 0
[2012-01-30 21:11:47] Accepted 00000000.abee8afd.1be1955c GPU 0 thread 0 pool 0
[2012-01-30 21:11:50] Accepted 00000000.0e06fa8b.b7b2a8ea GPU 1 thread 3 pool 0
[2012-01-30 21:11:57] Accepted 00000000.5931ea9c.ecc3aa6c GPU 0 thread 0 pool 0
[2012-01-30 21:11:59] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:12:03] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:12:06] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:12:11] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:12:12] Rejected 00000000.370dbc90.26abc167 GPU 0 thread 0 pool 0
[2012-01-30 21:12:15] LONGPOLL requested work restart, waiting on fresh work
[2012-01-30 21:12:17] LONGPOLL requested work restart, waiting on fresh work
Hi,
I just had an annoying multi-hour debugging session, trying to figure out why cgminer thinks there's only one GPU in my (Debian Testing) system.
$ aticonfig --list-ad
* 0. 06:00.0 ATI Radeon HD 5800 Series
1. 07:00.0 ATI Radeon HD 5800 Series
2. 08:00.0 ATI Radeon HD 5450
Turns out that AMD is being stupid. Again.
OpenCL 1.1 AMD-APP-SDK-v2.4 (595.10) (don't remember where I downloaded it from): library works.
OpenCL 1.2 AMD-APP (831.4) (available from http://developer.amd.com/sdks/AMDAPPSDK/Pages/default.aspx ) does NOT see more than one GPU.
You can extract the build number etc. from the library with
$ strings -a /pth/to/the/library.so | grep "^OpenCL.*AMD-APP"
Sorry if this has been mentioned before, but this thread is too long to scan everything.
I just had an annoying multi-hour debugging session, trying to figure out why cgminer thinks there's only one GPU in my (Debian Testing) system.
$ aticonfig --list-ad
* 0. 06:00.0 ATI Radeon HD 5800 Series
1. 07:00.0 ATI Radeon HD 5800 Series
2. 08:00.0 ATI Radeon HD 5450
Turns out that AMD is being stupid. Again.
OpenCL 1.1 AMD-APP-SDK-v2.4 (595.10) (don't remember where I downloaded it from): library works.
OpenCL 1.2 AMD-APP (831.4) (available from http://developer.amd.com/sdks/AMDAPPSDK/Pages/default.aspx ) does NOT see more than one GPU.
You can extract the build number etc. from the library with
$ strings -a /pth/to/the/library.so | grep "^OpenCL.*AMD-APP"
Sorry if this has been mentioned before, but this thread is too long to scan everything.
Salting bascially changes the original value and the comparison value with a known figure so the hashes can't be referenced to a lookup table, and so they can't be broken without knowing the salt value. Oh wait, we know the salt value now. Haha, that was easy.
Again, with the big exclamation of, "Everyone lock your doors, they might have gotten a copy of the KEY TO THE KINGDOM! *attachment: high-res picture of key to the kingdom.jpg*"
You forget that everybody and their dog can just go and check out the forum PHP code themselves, and examine the password hashing algorithm in detail.Again, with the big exclamation of, "Everyone lock your doors, they might have gotten a copy of the KEY TO THE KINGDOM! *attachment: high-res picture of key to the kingdom.jpg*"
This mess. ultimately, is the PHP language authors' fault. They seem to argue that securing your scripts (and not just from SQL injections) is the programmer's problem.
A properly designed SQL interface (with prepared statements and placeholders) makes writing code that's prone to injections more difficult to write than code which isn't.
In PHP, it's the other way round, and the language authors don't think that's a problem.
Well, I happen to disagree, rather vehemently in fact, which is why I try to encourage people to program their web sites in some other language (Python for instance), and why every single PHP-using website on my server runs in a FastCGI sandbox and has (almost) no access to the rest of the system.
Re: Mining on MMC is now 2x (EDIT: 3x) more profitable than mining Solidcoins !!!
Well, I lucked out bought a whole bunch of solidcoins when they sold for 0.0015BTC and sold them for 0.015BTC, so yeah, solidcoins paid for my next mining rig. ;-)
Re: MTGOX PROBLEM - Sold BTC was never credited USD - Check YOUR History
Ouch. Somebody should teach them about this novel database concept called a "transaction".
DDoS or not, it should simply be impossible for something like this to happen.
DDoS or not, it should simply be impossible for something like this to happen.
Re: Official CGMINER thread - CPU/GPU miner in C for linux/windows/osx
Thanks. Again, it's not a temperature problem!
Card is well cooled and staying around ~75°C.
Mmh. Is the temperature measured on the GPU die, or is there an external temperature sensor on the heat sink?Card is well cooled and staying around ~75°C.
If the latter ⇒ bad heat transfer paste could still be the reason.
Excellent site.
One nit: the detail info when you mouse over the market depth graph is only half right. For the left sde you need at least of bitcoins to pull the price down, not $$.
One nit: the detail info when you mouse over the market depth graph is only half right. For the left sde you need at least of bitcoins to pull the price down, not $$.
Re: Official CGMINER thread - CPU/GPU miner in C for linux/windows/osx
What exactly do you mean by a socket? It looks to just be a filename on that summary. I assume this is not just redirecting stderr to your file of choice?
./cgminer -blah 2>/path/to/file
?
No it's not a file. It's a socket, just backed by a file instead of an IP address+port../cgminer -blah 2>/path/to/file
?
Something listens on the other end and does stuff with the data (like, forward to a master system).
Said other end can also send commands to you, since sockets are bidirectional; I haven't used BAMT yet, so no idea whether it actually does that or whether it uses the port just for reporting.
None of these alternative currencies has so far shown even a fraction of the elegance bitcoin has.
Since they're mostly the same, they can't be that much less elegant.So far I've seen two more interesting approaches:
Namecoins add names.
Solidcoins add faster transctions and less upwards volatility-of-difficulty.
Both ideas have inherent value. That's rather important; we don't just invent a new currency. Anybody can do that. (Look up Norton I, self-styled Emperor of San Francisco, for a particularly interesting example.)
We want to do new things here which we couldn't do before.
One can send money and exchange it for different money with any bank. That's not the point of Bitcoins.
Neither is the ability to mint your own money. That's a nice feature, for now, but it'll stop working (i.e. "generate enough coins to offset the power bill") soon enough.
Re: Official CGMINER thread - CPU/GPU miner in C for linux/windows/osx
Well, that's not a fix as it won't make it work on RHEL5, that's just making the failure message more informative.
Good thing IMHO. configure.ac is supposed to test for minimum features, after all.Quote
I guess I can try compiling static builds against newer curl, but I don't really understand if anyone is interested in RHEL5 builds other than me.
The problem with this idea is that network-using static libraries are not supported by glibc.You should be able to build your own version of "new" libcurl and compile+link against that.
Adding a --with-libcurl=/usr/local/src/newcurl option to configure is reasonably simple.
Re: Official CGMINER thread - CPU/GPU miner in C for linux/windows/osx
As I said the curl version is too old, there is no fix unless ck makes longpoll optional / figures out how to implement this functionality only using old curl's features.
The fix is to add a check to configure.ac, for "new curl" (i.e. version and/or data type and/or library call) and to refuse to continue if that's not present.Should be straightforward to implement.
As ckolivas already mentioned
Bah. I was sure I've read the whole thread.Thanks.
Hi,
has anybody gotten cgminer to run on the console (i.e., no running X)?
Tracing the cgminer process, it gets as far as opening /dev/ati/card0 and running a few ioctl calls (and incidentally _not_ opening /dev/ati/card1, despite the fact that I have two of them), but then clGetDeviceIDs() returns -1. Ouch.
has anybody gotten cgminer to run on the console (i.e., no running X)?
Tracing the cgminer process, it gets as far as opening /dev/ati/card0 and running a few ioctl calls (and incidentally _not_ opening /dev/ati/card1, despite the fact that I have two of them), but then clGetDeviceIDs() returns -1. Ouch.
Not to forget:
cgminer (gpu and/or cpu miner, linux/windows/OSX, features: evolving ;-) ):
http://forum.bitcoin.org/index.php?topic=28402.0
cgminer (gpu and/or cpu miner, linux/windows/OSX, features: evolving ;-) ):
http://forum.bitcoin.org/index.php?topic=28402.0
Re: Official CGMINER thread - CPU/GPU miner in C for linux/windows/osx
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.
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:baz@foo.example.org: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:baz@foo.example.org: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.
Well, I think they're a bit annoying. Four content-free posts in the Newbie section aren't that difficult.
Why don't you allow enabling an account with a Bitcoin transfer? I'd consider 1 Bitcent to be reasonable for purposes of spam blocking.
Why don't you allow enabling an account with a Bitcoin transfer? I'd consider 1 Bitcent to be reasonable for purposes of spam blocking.