Search content
Sort by
Showing 16 of 16 results by zomnut
Re: CGMINER ASIC FPGA miner monitoring RPC linux/win/osx/mips/arm/r-pi 3.10.0
Raspberry PI Make Error:
...
...
CCLD cgminer
cgminer-libbitfury.o: In function `spi_reset':
/home/minepeon/cgminer/libbitfury.c:226: undefined reference to `mcp2210_set_gpio_settings'
/home/minepeon/cgminer/libbitfury.c:233: undefined reference to `mcp2210_spi_transfer'
/home/minepeon/cgminer/libbitfury.c:239: undefined reference to `mcp2210_set_gpio_settings'
cgminer-libbitfury.o: In function `spi_txrx':
/home/minepeon/cgminer/libbitfury.c:255: undefined reference to `mcp2210_spi_transfer'
/home/minepeon/cgminer/libbitfury.c:265: undefined reference to `mcp2210_spi_transfer'
collect2: error: ld returned 1 exit status
make[2]: *** [cgminer] Error 1
make[2]: Leaving directory `/home/minepeon/cgminer'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/minepeon/cgminer'
make: *** [all] Error 2
...
...
CCLD cgminer
cgminer-libbitfury.o: In function `spi_reset':
/home/minepeon/cgminer/libbitfury.c:226: undefined reference to `mcp2210_set_gpio_settings'
/home/minepeon/cgminer/libbitfury.c:233: undefined reference to `mcp2210_spi_transfer'
/home/minepeon/cgminer/libbitfury.c:239: undefined reference to `mcp2210_set_gpio_settings'
cgminer-libbitfury.o: In function `spi_txrx':
/home/minepeon/cgminer/libbitfury.c:255: undefined reference to `mcp2210_spi_transfer'
/home/minepeon/cgminer/libbitfury.c:265: undefined reference to `mcp2210_spi_transfer'
collect2: error: ld returned 1 exit status
make[2]: *** [cgminer] Error 1
make[2]: Leaving directory `/home/minepeon/cgminer'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/minepeon/cgminer'
make: *** [all] Error 2
Confirmed building on a Beaglebone as well:
Code:
autogen.sh && ./configure --enable-bflsc && make
That will fail when linking as shown in netfun2000's dump. Adding --enable-bitfury to the configure command will workaround the bug and build successfully.Code:
autogen.sh && ./configure --enable-bflsc --enable-bitfury && make
It would seem that without --enable-bitfury, there is some partial libbitfury leakage into the build process.Re: CGMINER ASIC FPGA GPU overc monit fanspd RPC linux/win/osx/mip/r-pi 3.4.2
Using 3.4.2, logging to syslog.
If my cgminer log interval is not set to 5, I don't receive the log entries like
If my cgminer log interval is not set to 5, I don't receive the log entries like
Code:
(5s):xxG (avg):xxGh/s | A:xx R:xx HW:xx WU:xx/m
to syslog at all. I still get other syslog entries from cgminer, just not this entry. When log interval is equal to 5, I get that entry every 5 seconds.
Hi all. I'm considering using Electrum to store a large number of Bitcoins, but the deterministic wallet concerns me a bit.
I'm under the impression the completely random address generation of Bitcoin-QT is more secure, as a potentially attacker would need to guess every private key to spend your entire wallet.
While with Electrum only one secret (the seed) is required to spend the entire wallet
Am I correct here or am I completely missing something?
I really want to use Electrum, as I have an old netbook with very little storage that is struggling to hold the entire blockchain (< 900 MB remaining) and struggling dealing with Bitcoin-QT's IO requirements.
I really want to know if my concerns regarding deterministic wallets are valid.
Also, I suppose I should ask if Electrum can be used without a deterministic wallet?
I'm under the impression the completely random address generation of Bitcoin-QT is more secure, as a potentially attacker would need to guess every private key to spend your entire wallet.
While with Electrum only one secret (the seed) is required to spend the entire wallet
Am I correct here or am I completely missing something?
I really want to use Electrum, as I have an old netbook with very little storage that is struggling to hold the entire blockchain (< 900 MB remaining) and struggling dealing with Bitcoin-QT's IO requirements.
I really want to know if my concerns regarding deterministic wallets are valid.
Also, I suppose I should ask if Electrum can be used without a deterministic wallet?
You can use Electrum without any risk even if your seed is captured by a hacker. The seed doesnt give access to imported keys.
Generate some new keys using the javascript available on bitaddress.org and then import them into Electrum.
Importing keys into Electrum eliminates the concerns regarding a deterministic wallet by eliminating the deterministic wallet. You lose any benefit the deterministic wallet could offer and are left with a "random address" wallet.
Here is my log file
http://pastebin.com/p3z0BZiY
The private key I attempted to insert (never been used, never will be used, generated using vanitygen for this bugreport) is
5JPW1RT1bwM7GEfx6By3YAh158Yjs6vrphZ3BABLV9DXu4bCdwz
Changes to settings from default:
Unchecked "Let Armory run Bitcoin-Qt/bitcoind in the background"
I started Armory, went online, double clicked on a wallet, Selected Import/Sweep Private Keys, selected "One Key", pasted the key, and selected "Import these addresses to your wallet"
Clicked OK
Verify address, clicked Yes, this is where the traceback appears in the log. Verify address dialog closes and returns me to the Private Key Import form with no change. Address is not imported.
http://pastebin.com/p3z0BZiY
The private key I attempted to insert (never been used, never will be used, generated using vanitygen for this bugreport) is
5JPW1RT1bwM7GEfx6By3YAh158Yjs6vrphZ3BABLV9DXu4bCdwz
Changes to settings from default:
Unchecked "Let Armory run Bitcoin-Qt/bitcoind in the background"
I started Armory, went online, double clicked on a wallet, Selected Import/Sweep Private Keys, selected "One Key", pasted the key, and selected "Import these addresses to your wallet"
Clicked OK
Verify address, clicked Yes, this is where the traceback appears in the log. Verify address dialog closes and returns me to the Private Key Import form with no change. Address is not imported.
When importing a private key in 0.88 I get stuck in a confirmation loop, selecting OK after entering the private key, selecting Yes to verify the associated address, back to the key entry where I press OK, which then asks to verify the address, etc. This was not an issue in 0.87, where it would ask for the wallet password after verifying the address.
I was able to get 0.1 btc up to 6 btc using Nakabot, but quickly lost it all before I decided to cash out. So, keep looking for free coins until Nakabot is a viable option (You need 0.02 to break even on a NakaBot 61634 win)
Using Guiminer v2012-02-19, if I use an OpenCL miner it crashes my nVidia GTX550ti video driver whenever I pause the miner. Cuda has no issue, just wondering if it is a common issue with nVidia drivers.