Mine runs the 880 firmware, and it's temps usually vary between 47 and 50 C, depending on ambient. I would say you could go higher than 800.
The auto tune works by loading the fastest firmware, and running it for a set amount of time (I think 20 minutes?). If it throttles at all in that time, then it drops to the next lowest firmware. It keeps repeating this process until it finds a firmware slow enough that the unit doesn't throttle.
Did the auto-tune decide on the 800 firmware? I would try manually loading some other firmware, like the 880 or the 864.
Hello mate, thanks for the input! The auto tune decided on the 896 firware. But when I started mining it is started throttling using cgminer 2.8.7 . So I started from the top and worked my way down the speeds. They all throttled except 800. Its running at 40 centigrade right now on 800. Any ideas?? I know I can get more out of it since ambient temps are around 24 centigrade. I may be doing sumthin wrong??
|
|
|
Maybe, if you can add an additional fan or two to keep it cool
But how come it auto loaded the 896??
|
|
|
Hi
Ok so I set it up and did a auto-tune and it auto loaded the 896 MH/s firmware!
Ended up throttling . I tried every single one, all the way down to 800 and its ok now, temps around 38 centigrade !
Can it handle more you think?
|
|
|
I already tried that over 3-4 times.. Same keeps happening I just cant figure this out ... YET ...
|
|
|
Yeah, no funds in there.. Just wanna wallet , goddamit I get the same error Dia.. Any ideas?? Because Im running out of em Did you try -salvagewallet (command-line option, which moves any existing wallet.dat to wallet.{timestamp}.dat and then attempts to salvage public/private keys and master encryption keys (if the wallet is encrypted) into a new wallet.dat. This should only be used if your wallet becomes corrupted, and is not intended to replace regular wallet backups.)?
Make a backup of your wallet.dat before anyway!
Dia
You could try older versions, perhaps one works, which would allow to transfer stored funds to a new wallet? Sorry, I guess some of the core devs could perhaps give some more help here. Dia
|
|
|
I get the same error Dia.. Any ideas?? Because Im running out of em Did you try -salvagewallet (command-line option, which moves any existing wallet.dat to wallet.{timestamp}.dat and then attempts to salvage public/private keys and master encryption keys (if the wallet is encrypted) into a new wallet.dat. This should only be used if your wallet becomes corrupted, and is not intended to replace regular wallet backups.)?
Make a backup of your wallet.dat before anyway!
Dia
|
|
|
Hope its soon mate! Thanks for the insights..
When will you send it in for a replacement?
When they tell me my SC Single is ready.
|
|
|
Thanks for the insights.. When will you send it in for a replacement? Sounds like you had to do a bit of DIY I saw a quite a few people with similar issues! Do all units come this way? Or do you think yours was a one off? I mean the fan direction, too much paste etc.. Also, will it affect you if you send it in for an upgrade? I mean all the DIY? Will BFL mind that you modified the device just a little bit? Thanks Ya I had to give it some TLC, but I like tinkering. The fan direct is actually standard, as I guess it works better blowing up if you leave it in it's case, but works better blowing down if you take it out of it's case. Either way, it's pretty easy to take out of it's case. The thermal paste is another issue, as some people have said that theirs were fine, others havn't had as much luck. I do think mine was a random occurrence, tho. And finally, BFL doesn't care if you take it apart or open it up or repaste it or whatever. As long as you don't break it, they'll still accept it as an upgrade. I still plan on putting it back together when I do send it in, of course.
|
|
|
Did you have to do a bit of DIY with it?? Just plug it in and run cgminer. If it starts throttling, then worry about changing the bitstream. Most of the time when I tried autotuning, it installed a bitstream that was too fast and ended up throttling, leading me to manually lower the bitstream back to normal anyway.
|
|
|
Sounds like you had to do a bit of DIY I saw a quite a few people with similar issues! Do all units come this way? Or do you think yours was a one off? I mean the fan direction, too much paste etc.. Also, will it affect you if you send it in for an upgrade? I mean all the DIY? Will BFL mind that you modified the device just a little bit? Thanks I autotuned mine with Easyminer and that was it. I use CGMiner which is the best mining software IMHO.
I got mine, plugged it in, and it was throttling even with the stock 832 firmware. I had to bump it down to the 816 firmware so it wouldn't throttle. Then I took it apart, repasted the chips with some CM stuff (they used WAY too much paste), directed the fan down instead of up, attatched a small 80mm CPU fan from and old AMD heatsink, and now I run it outside of it's case and laying on it's side. The Easyminer autotune flashed it with the 880 firmware, which is what I'm running now. I could prolly switch to the 896 since I added the extra fan on the bottom, but I havn't done it yet. Using CGMiner, and it's been great.
|
|
|
Thank you so much!
|
|
|
Hiya Thanks! How do you autotune? What does it do exactly? What speed is it working at?
|
|
|
Hi Anyone mining with a BFL single out there. Got any tips on setting one up. Did you flash yours when you first received it? Do you recommend flashing it? Which firmware is the best to use? Which mining software? How do you go about setting it up?? I'm eager to learn, thanks in advance!
|
|
|
Here is my log file. I am running 0.7.1. I have cut the log a bit short. Thanks ERROR: FetchInputs() : 5b2febc48a mempool Tx prev not found a5d15e1498 stored orphan tx 5b2febc48a (mapsz 5613) received block 00000000000002e174e6 ProcessBlock: ORPHAN BLOCK, prev=00000000000007328218 ERROR: FetchInputs() : fafa937e40 mempool Tx prev not found 4578de4640 stored orphan tx fafa937e40 (mapsz 5614) Flushed 10661 addresses to peers.dat 246ms received block 00000000000002dd859a ProcessBlock: ORPHAN BLOCK, prev=00000000000002e174e6 Added 1 addresses from 94.179.214.34: 13 tried, 10648 new ERROR: FetchInputs() : 955e361a1a mempool Tx prev not found 6e08b7388c stored orphan tx 955e361a1a (mapsz 5615) ERROR: FetchInputs() : 1d5d5ac640 mempool Tx prev not found 52cd767862 stored orphan tx 1d5d5ac640 (mapsz 5616) ERROR: FetchInputs() : 7b2dcce78d mempool Tx prev not found 5b2febc48a stored orphan tx 7b2dcce78d (mapsz 5617) received block 00000000000002516ec0 ProcessBlock: ORPHAN BLOCK, prev=00000000000002dd859a ERROR: FetchInputs() : 23f9cd3e91 mempool Tx prev not found d281c0a3e2 stored orphan tx 23f9cd3e91 (mapsz 5618) ERROR: FetchInputs() : 6e9e03ae73 mempool Tx prev not found 5b2febc48a stored orphan tx 6e9e03ae73 (mapsz 5619) received block 0000000000000294a1bc ProcessBlock: ORPHAN BLOCK, prev=00000000000002516ec0 ERROR: FetchInputs() : 9666265669 mempool Tx prev not found fafa937e40 stored orphan tx 9666265669 (mapsz 5620) Added 1 addresses from 173.76.177.60: 13 tried, 10648 new ERROR: FetchInputs() : 5e07d9b38c mempool Tx prev not found 5b2febc48a stored orphan tx 5e07d9b38c (mapsz 5621) ERROR: FetchInputs() : 3f9a3d8ee2 mempool Tx prev not found 5b2febc48a stored orphan tx 3f9a3d8ee2 (mapsz 5622) ERROR: FetchInputs() : a993dd9d99 mempool Tx prev not found 4551f0e1cd stored orphan tx a993dd9d99 (mapsz 5623) ERROR: FetchInputs() : fd88eb3179 mempool Tx prev not found 5b2febc48a stored orphan tx fd88eb3179 (mapsz 5624) received block 000000000000066ecfe5 ProcessBlock: ORPHAN BLOCK, prev=0000000000000294a1bc Added 1 addresses from 173.76.177.60: 13 tried, 10649 new received block 000000000000010fa885 ProcessBlock: ORPHAN BLOCK, prev=000000000000066ecfe5 received block 00000000000004c689d9 ProcessBlock: ORPHAN BLOCK, prev=000000000000010fa885 ERROR: FetchInputs() : 879c40d7f5 mempool Tx prev not found 1d5d5ac640 stored orphan tx 879c40d7f5 (mapsz 5625) ERROR: FetchInputs() : 4a0138c922 mempool Tx prev not found e676005a6d stored orphan tx 4a0138c922 (mapsz 5626) received block 000000000000045c31bb ProcessBlock: ORPHAN BLOCK, prev=00000000000004c689d9 received block 000000000000051c24db ProcessBlock: ORPHAN BLOCK, prev=000000000000045c31bb received block 000000000000047ffa72 ProcessBlock: ORPHAN BLOCK, prev=000000000000051c24db ERROR: FetchInputs() : 6fc3777ee6 mempool Tx prev not found 2203f90fcb stored orphan tx 6fc3777ee6 (mapsz 5627) ERROR: FetchInputs() : a5c007a181 mempool Tx prev not found a993dd9d99 stored orphan tx a5c007a181 (mapsz 5628) received block 000000000000019b5080 ProcessBlock: ORPHAN BLOCK, prev=000000000000047ffa72 Flush(false) blkindex.dat refcount=0 ThreadSocketHandler exited ThreadMessageHandler exited ipcThread exited blkindex.dat checkpoint ThreadMapPort exited blkindex.dat closed wallet.dat refcount=0 wallet.dat checkpoint wallet.dat detach wallet.dat closed DBFlush(false) ended 1087ms StopNode() ThreadOpenConnections exited Flushed 10662 addresses to peers.dat 560ms Flush(true) DBFlush(true) ended 0ms Bitcoin exited
Bitcoin version v0.7.1.0-geb49457-beta () Using OpenSSL version OpenSSL 1.0.1c 10 May 2012 Startup time: 30/10/12 18:59:17 Default data directory /home/yr/.bitcoin Used data directory /home/yr/.bitcoin dbenv.open LogDir=/home/yr/.bitcoin/database ErrorFile=/home/yr/.bitcoin/db.log Loading block index... LoadBlockIndex(): hashBestChain=0000000034bd1e0953a3 height=43788 date=04/03/10 20:29:39 Verifying last 2500 blocks at level 1 block index 18996ms Loading wallet...
************************ EXCEPTION: St13runtime_error CDB() : can't open database file wallet.dat, error 12 bitcoin in Runaway exception
EnvShutdown exception: Invalid argument (22) |
|
|
|
Here it is. I am running 0.7.1. I have cut the log a bit short. Thanks ERROR: FetchInputs() : 5b2febc48a mempool Tx prev not found a5d15e1498 stored orphan tx 5b2febc48a (mapsz 5613) received block 00000000000002e174e6 ProcessBlock: ORPHAN BLOCK, prev=00000000000007328218 ERROR: FetchInputs() : fafa937e40 mempool Tx prev not found 4578de4640 stored orphan tx fafa937e40 (mapsz 5614) Flushed 10661 addresses to peers.dat 246ms received block 00000000000002dd859a ProcessBlock: ORPHAN BLOCK, prev=00000000000002e174e6 Added 1 addresses from 94.179.214.34: 13 tried, 10648 new ERROR: FetchInputs() : 955e361a1a mempool Tx prev not found 6e08b7388c stored orphan tx 955e361a1a (mapsz 5615) ERROR: FetchInputs() : 1d5d5ac640 mempool Tx prev not found 52cd767862 stored orphan tx 1d5d5ac640 (mapsz 5616) ERROR: FetchInputs() : 7b2dcce78d mempool Tx prev not found 5b2febc48a stored orphan tx 7b2dcce78d (mapsz 5617) received block 00000000000002516ec0 ProcessBlock: ORPHAN BLOCK, prev=00000000000002dd859a ERROR: FetchInputs() : 23f9cd3e91 mempool Tx prev not found d281c0a3e2 stored orphan tx 23f9cd3e91 (mapsz 5618) ERROR: FetchInputs() : 6e9e03ae73 mempool Tx prev not found 5b2febc48a stored orphan tx 6e9e03ae73 (mapsz 5619) received block 0000000000000294a1bc ProcessBlock: ORPHAN BLOCK, prev=00000000000002516ec0 ERROR: FetchInputs() : 9666265669 mempool Tx prev not found fafa937e40 stored orphan tx 9666265669 (mapsz 5620) Added 1 addresses from 173.76.177.60: 13 tried, 10648 new ERROR: FetchInputs() : 5e07d9b38c mempool Tx prev not found 5b2febc48a stored orphan tx 5e07d9b38c (mapsz 5621) ERROR: FetchInputs() : 3f9a3d8ee2 mempool Tx prev not found 5b2febc48a stored orphan tx 3f9a3d8ee2 (mapsz 5622) ERROR: FetchInputs() : a993dd9d99 mempool Tx prev not found 4551f0e1cd stored orphan tx a993dd9d99 (mapsz 5623) ERROR: FetchInputs() : fd88eb3179 mempool Tx prev not found 5b2febc48a stored orphan tx fd88eb3179 (mapsz 5624) received block 000000000000066ecfe5 ProcessBlock: ORPHAN BLOCK, prev=0000000000000294a1bc Added 1 addresses from 173.76.177.60: 13 tried, 10649 new received block 000000000000010fa885 ProcessBlock: ORPHAN BLOCK, prev=000000000000066ecfe5 received block 00000000000004c689d9 ProcessBlock: ORPHAN BLOCK, prev=000000000000010fa885 ERROR: FetchInputs() : 879c40d7f5 mempool Tx prev not found 1d5d5ac640 stored orphan tx 879c40d7f5 (mapsz 5625) ERROR: FetchInputs() : 4a0138c922 mempool Tx prev not found e676005a6d stored orphan tx 4a0138c922 (mapsz 5626) received block 000000000000045c31bb ProcessBlock: ORPHAN BLOCK, prev=00000000000004c689d9 received block 000000000000051c24db ProcessBlock: ORPHAN BLOCK, prev=000000000000045c31bb received block 000000000000047ffa72 ProcessBlock: ORPHAN BLOCK, prev=000000000000051c24db ERROR: FetchInputs() : 6fc3777ee6 mempool Tx prev not found 2203f90fcb stored orphan tx 6fc3777ee6 (mapsz 5627) ERROR: FetchInputs() : a5c007a181 mempool Tx prev not found a993dd9d99 stored orphan tx a5c007a181 (mapsz 5628) received block 000000000000019b5080 ProcessBlock: ORPHAN BLOCK, prev=000000000000047ffa72 Flush(false) blkindex.dat refcount=0 ThreadSocketHandler exited ThreadMessageHandler exited ipcThread exited blkindex.dat checkpoint ThreadMapPort exited blkindex.dat closed wallet.dat refcount=0 wallet.dat checkpoint wallet.dat detach wallet.dat closed DBFlush(false) ended 1087ms StopNode() ThreadOpenConnections exited Flushed 10662 addresses to peers.dat 560ms Flush(true) DBFlush(true) ended 0ms Bitcoin exited
Bitcoin version v0.7.1.0-geb49457-beta () Using OpenSSL version OpenSSL 1.0.1c 10 May 2012 Startup time: 30/10/12 18:59:17 Default data directory /home/yr/.bitcoin Used data directory /home/yr/.bitcoin dbenv.open LogDir=/home/yr/.bitcoin/database ErrorFile=/home/yr/.bitcoin/db.log Loading block index... LoadBlockIndex(): hashBestChain=0000000034bd1e0953a3 height=43788 date=04/03/10 20:29:39 Verifying last 2500 blocks at level 1 block index 18996ms Loading wallet...
************************ EXCEPTION: St13runtime_error CDB() : can't open database file wallet.dat, error 12 bitcoin in Runaway exception
EnvShutdown exception: Invalid argument (22) |
So yes, I reinstalled it again and half hour into it I get the same msg again. "WARNING: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."
Then when I close and restart the program, I get: A fatal error has occured. Bitcoin can no longer continue safely and will quit.
Exception: St13runtime_error CDB() : can't open database file wallet.dat, error 12 bitcoin in Runaway exception.
Any ideas??
Can you pastebin your debug.log? You can also try the newly introduced (0.7.1): -salvagewallet command-line option, which moves any existing wallet.dat to wallet.{timestamp}.dat and then attempts to salvage public/private keys and master encryption keys (if the wallet is encrypted) into a new wallet.dat. This should only be used if your wallet becomes corrupted, and is not intended to replace regular wallet backups.
Dia
|
|
|
So yes, I reinstalled it again and half hour into it I get the same msg again. "WARNING: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."
Then when I close and restart the program, I get: A fatal error has occured. Bitcoin can no longer continue safely and will quit.
Exception: St13runtime_error CDB() : can't open database file wallet.dat, error 12 bitcoin in Runaway exception.
Any ideas??
|
|
|
Ok, so I installed it again and restarted the syncing as you know.
about half hour in to it , it stops and says : "WARNING: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."
Any ideas??
|
|
|
Well, thanks for the tip. I installed it in a bit of a different way to what you said. I added the ppa to software sources and then downloaded and installed it from the software center. Thanks a bunch for all the enlightening info. Im still trying to get the hang of ubuntu, I feel it works in mysterious ways. I have reinstalled it in the way you described and it is syncing, fingers crossed and hope it works Thanks alot! Errors accessing wallet.dat as described above are likely from bitcoin (in one form or another) still running. Alternately, the wallet file could have been corrupted by attempting to run two different versions of Bitcoin which may concurrently access the same data directory.
Bitcoin takes a considerable amount of time to shut down after you tell it to. Bitcoin-qt (the full GUI version) will "close" when you press the close button, but it may still run in the background for a minute as it shuts down and closes the database files. Bitcoind (the daemon) may be running in a console window, but it doesn't need a window showing on your current desktop to be running.
In Ubuntu, press the superkey (Windows key), and type "System Monitor" and launch it. In the system monitor, check the processes tab to see if any copy or version of Bitcoin is running. If so you must close it and allow it to finish closing.
You do not state what version you are using or where you got it from. Either run bitcoin-qt extracted from the Sourceforge Bitcoin release bitcoin-0.7.1-linux.tar.gz (bitcoin.org -> Linux version), or follow these instructions:
Ubuntu Linux users can use the "Personal Package Archive" (PPA) maintained by Matt Corallo to automatically keep up-to-date. Just type: sudo apt-add-repository ppa:bitcoin/bitcoin sudo apt-get update
in your terminal, then install the bitcoin-qt package: sudo apt-get install bitcoin-qt
You should first remove any bitcoind or older version you have installed. Additionally, if you have never used your wallet or the addresses in it, a good fresh start would be to remove the .bitcoin directory in your home directory, which is where all data files for Bitcoin are stored.
After installing the newest version, it can be launched by typing bitcoin-qt in a terminal window if it is not added to your menu bar. Then let it run for the day or two it requires to download 4GB of data.
|
|
|
No worries, had none in there anyway. My main problem is every time I try to sync the blockchain I keep getting the same error before it completes. Exception: St13runtime_error CDB() : can't open database file wallet.dat, error 12 bitcoin in Runaway exception. I delete all files and restart the process and same thing happens again and again... Thanks for any help.. I did not say "lost".
From what you wrote, it seems that the bitcoin-client has difficulties to open and use your wallet. Most likely the information is still stored in it, but you may have to do some sorcery to get the client use it. The much easier way, of course, is when you have a backup.
I'm not a developer of any bitcoin-client.
What's current state of affairs? Do you have a backup? What order of value was stored in it? (i.e.: does it even pay to spend effort on recovering it?)
|
|
|
Bumpy road?? Why would my wallet be lost anyhow? You *do* have a backup, don't you? Terminate all running clients, restore from backup and restart...
Don't have one? And more than just a few peanuts of btc in the wallet? Probably not all hope is lost, but prepare for a bumpy road ahead.
|
|
|
|