Search content
Sort by
Showing 5 of 5 results by floe
$ ./poclbm.py
Traceback (most recent call last):
File "./poclbm.py", line 27, in
platforms = cl.get_platforms()
pyopencl.LogicError: clGetPlatformIDs failed: invalid/unknown error code
Traceback (most recent call last):
File "./poclbm.py", line 27, in
platforms = cl.get_platforms()
pyopencl.LogicError: clGetPlatformIDs failed: invalid/unknown error code
When you have this problem, you should check /etc/OpenCL/vendors/amdocl32.icd - this file should exist and contain the string "libamdocl32.so"
(for a 64-bit system, replace 32 with 64).
Floe
Re: Ufasoft Miner Thread - SSE2-optimized for Intel CPUs, version 0.10 (2011-May)
Hi everyone,
I'm getting a bit of a weird assembler error here on Ubuntu 11.04 with jwasm 2.05 (didn't find any specific version requirements):
However, the respective scale factors in the assembler code are always 4...?
Error occurs both in 64-bit and 32-bit compilation. Any hints?
Thanks,
Florian
I'm getting a bit of a weird assembler error here on Ubuntu 11.04 with jwasm 2.05 (didn't find any specific version requirements):
Code:
[0] $ make
jwasm -3 -elf -zcw -c -Fosha256sse.o sha256sse.asm
JWasm v2.05, May 29 2011, Masm-compatible assembler.
Portions Copyright (c) 1992-2002 Sybase, Inc. All Rights Reserved.
Source code is available under the Sybase Open Watcom Public License.
sha256sse.asm(76) : Error A2036: Scale factor must be 1, 2, 4 or 8
sha256sse.asm(77) : Error A2036: Scale factor must be 1, 2, 4 or 8
sha256sse.asm(153) : Error A2036: Scale factor must be 1, 2, 4 or 8
sha256sse.asm(169) : Error A2036: Scale factor must be 1, 2, 4 or 8
sha256sse.asm: 316 lines, 1 passes, 0 ms, 0 warnings, 4 errors
make: *** [sha256sse.o] Error 1
jwasm -3 -elf -zcw -c -Fosha256sse.o sha256sse.asm
JWasm v2.05, May 29 2011, Masm-compatible assembler.
Portions Copyright (c) 1992-2002 Sybase, Inc. All Rights Reserved.
Source code is available under the Sybase Open Watcom Public License.
sha256sse.asm(76) : Error A2036: Scale factor must be 1, 2, 4 or 8
sha256sse.asm(77) : Error A2036: Scale factor must be 1, 2, 4 or 8
sha256sse.asm(153) : Error A2036: Scale factor must be 1, 2, 4 or 8
sha256sse.asm(169) : Error A2036: Scale factor must be 1, 2, 4 or 8
sha256sse.asm: 316 lines, 1 passes, 0 ms, 0 warnings, 4 errors
make: *** [sha256sse.o] Error 1
However, the respective scale factors in the assembler code are always 4...?
Error occurs both in 64-bit and 32-bit compilation. Any hints?
Thanks,
Florian
Just cloned the git repo on my Ubuntu 11.04 machine and started the miner without any issues at all.
Thanks for such a smooth piece of software
Currently reporting ~ 6.3 Mhash/s on my Geforce 8600 GT, very impressive.
One additional question: do the hashes generated by poclbm show up in the "hashespersec" statistic shown by "bitcoind getinfo"? Seems like they don't...
Florian
Thanks for such a smooth piece of software
Currently reporting ~ 6.3 Mhash/s on my Geforce 8600 GT, very impressive.
One additional question: do the hashes generated by poclbm show up in the "hashespersec" statistic shown by "bitcoind getinfo"? Seems like they don't...
Florian
1. Yep, that's how it works, kind of...
OK, so I got that right :-)2. The only thing you're missing is that you don't need to go back through the entire chain- just to the previous transaction where it came under that address' control. Since every time you send coins it verifies that there is a tx where the coins came under your control, the block chain forms a transaction chain that is self building.
basically, you only need to look at the tx that gave the coins to the address that is spending them, not all the way back to generation- the blockchain already does that.
OK, I think I got that too. So scanning the entire block chain is only necessary if, say, you want to know the balance for an address that is not your own? Even then, you probably can scan backwards from the current block and stop when you've found all generation transactions.basically, you only need to look at the tx that gave the coins to the address that is spending them, not all the way back to generation- the blockchain already does that.
Florian
Hello everyone, I've been reading a bit of the bitcoin wiki and I'm really impressed by the technical details.
However, I have one question: how is the balance of a single address or an account calculated?
AFAICT, this is the sum over all transactions in the longest chain involving that address, correct?
If yes, this leads to the next question: won't the amount of computation needed to scan through the
entire chain become prohibitive at some point? Especially if the number of transactions increases at
a similar rate as, e.g. the global hash rate?
Florian
However, I have one question: how is the balance of a single address or an account calculated?
AFAICT, this is the sum over all transactions in the longest chain involving that address, correct?
If yes, this leads to the next question: won't the amount of computation needed to scan through the
entire chain become prohibitive at some point? Especially if the number of transactions increases at
a similar rate as, e.g. the global hash rate?
Florian