I hereby request:
hi-def photos of each side (reverse, obverse) of each of your products.
one picture of each your products in a "redeemed" state, so everyone can judge online if an item is "okay" or not.
All you need to do is look earlier in this thread, or go to the site link in the first post and click where it says "high definition photos here". If the pictures aren't to your liking, it will only cost net .25 BTC to order one and attempt to re-sticker your spent coin and take your own satisfactory pictures.  I obviously need a new camera, but the difference should be apparent. |
|
|
|
That is custom die, or Altera don't know true dimensions of their own dies? "Hi, I'll give 5 BTC to whoever can figure out the die size for the Altera EP3SL150F780."
"Finding this number in Altera documentation would be perfect."
I have provided Altera data you asked for.
Where? But of course, you ain't gonna belive official Altera paper but guy micrometering unknown chip.  You aren't reading that report correctly (or you aren't convincing anyone you found an answer). That particular part of the report is detailing the solder reliability of the different BGA packages, and each line is a report of a specific test case. It doesn't list the model of die core or the FPGA series tested (or if it is even an FPGA) - it merely lists the die size of the particular chip tested in the reliability trial. This is why there are multiple die sizes for each package type listed, because many different FPGAs can go in a particular package, just like many different CPU cores can go in an AMD socket AM2 package. |
|
|
|
x.co is a domain shortener. It was probably directing to a honeypot attempting to log people accessing that URL. Remember, these are payments sent to the extortioner's address. I think the search warrant that states really ignorant stuff like they are kicking in the door looking for pastebins shows it is just as likely he was operating a TOR exit node and somebody government crank got his IP address instead of realizing that they will not find the anonymous perpetrator. |
|
|
|
Plus spell-check...
Yes... Relativily -> Relatively bitcoin -> Bitcoin anoymous -> anonymous predictible -> predictable alot -> a lot Because of the nature of Bitcoin's "coins" being a free market. The price fluctuates alot. Fragment sentence. Not just to be ironic. But using Bitcoin... http://www.youtube.com/watch?v=ODGA7ssL-6g |
|
|
|
|
Bitcoin is erroneously compared in the first paragraph with companies that transfer dollars. That is similar to saying "The Japanese Yen is like Western Union". Bitcoin is a currency of its own which gets its value from having a built-in transfer mechanism that allows people to send it to anyone in the world instantly without the need for, or interference by, a bank. In addition, Bitcoin's set rate of money creation is known, making it's value inflation-resistant; more can't just be printed by a government whenever they need to debase your savings to bail out their banking cronies.
If you are explaining Bitcoin to, and soliciting Bitcoin payment from, people who have never heard of it, the next thing you should address is how to get it. "So I just have to buy them?". "You might choose to do so. However, no. Do you just have to buy US Dollars? Anything you do that creates value can earn you Bitcoin: services, goods, even related money services (or as the authorities see it: prostitution, drugs, gambling and money laundering). Even running Internet services can earn you Bitcoin."
Investigating Bitcoin quickly makes people start to ponder what money actually is - like: Why does money have value? Why do we pay taxes to a government in their own currency, when they can just manufacture it themselves (Is it because inflation takes from the rich?) Is it really a "government backed" currency, or more a "government mandated" currency? - any private enterprise could take Bitcoin, but when you pay your taxes or parking tickets you must have some government-issued money to pay them.
Plus spell-check...
|
|
|
|
The policy to not remove anything worked when the forum was small. Now that we have thousands of posts a day, we can't afford 50% of them being junk. The moderators are now instructed to be less tolerant of low-value posts.
Some guidelines:
1. Free speech - you can say anything as long as it is relevant and presented in a calm and polite manner. Swearing, SHOUTING etc. make your post more likely to be removed.
2. No zero value posts or threads, like "SELL SELL SELL"
3. No pointless or uninteresting threads.
4. No referral code spam
5. No NSFW content
Button Hit. |
|
|
|
|
Trixx does a weird thing where if you start it up at stock speeds (like 1000MHz RAM), you can only adjust down to 600 or so - you have to close it and open it again, then you can adjust down some more until you finally get the speed you want. After restarting a few times and setting the final speed, you should be able to save that clock to slot 1, and set the options to start at windows startup, start minimized, and restore clocks. If it doesn't work right still, you could always try the uninstall/reinstall route.
|
|
|
|
|
Pools don't receive a report of miner hashrate, they get difficulty 1 share submissions and must extrapolate what the miner hashrate may be.
The average number of hashes required to find a difficulty one share is:
2**48 / 65535
so we estimate 4,295,032,833 hashes performed by a miner per share submitted.
Then lets estimate a miner's hashrate for the last 10 minutes (600 seconds):
S Shares/600 seconds * 4,295 MHash/share = S (4295/600) MHash/second = S * 7.158388 Mhash/s,
so if a miner finds 60 shares in this 10 minutes, their estimated hashrate is 429.5 Mhash/s.
|
|
|
|
That won't be much use to you. The blockchain height of "bootstrap.dat" is 193000, of which only about 189205 blocks will import. You say you already have blocks 195,000+. You would be better getting blk0002.dat from this thread, rename it to bootstrap.dat, and put it in your bitcoin data directory. Then start Bitcoin. Note that you must have the current version of Bitcoin for the bootstrap.dat process to work. That file contains blocks from 188529 to 206000; blocks that are older than your current blockchain height will be quickly skipped and then importing will continue at the next block you don't have. However, you may discover that the problem you are having, not downloading any blocks even though you have connections, may continue if your local blockchain is corrupted. |
|
|
|
Useless post spam now thanks to Butterfly Labs, they have contest rules that encourage putting their signature in and spamming the forum. Added josephliton, but I could pretty much add everyone that is on their contest page. |
|
|
|
|
This has to be unobtanium info unless you call Altera or pop the heat spreader on the chip. There is no indication of the physical TMSC-made die. For all we know, they could be the same die throughout the entire Stratix III line or parts of it, with yield-disabled LEs, they could even have two or three base die masks where all can potentially be smaller products but only one or two of them could be SL150..., there could be different mask or process revisions throughout time affecting die size, etc.
"Stratix III, Cyclone III and Cyclone IV products are fabricated on a 65/60 nm process technology that
supports up to 9 layers of Cu metallization and Low-k with one layer of Salicided polysilicon. Stratix
III devices are available in FlipChip FBGA packages with logic density ranging from 47.5K to 337.5K
LEs and 2,430 to 20,491 Kbits of total memory. Cyclone III and Cyclone IV devices are available in
QFP, QFN, FBGA and UBGA packages with logic density ranging from 5,136 to 149,760 LEs and 414
to 6,480 Kbits of memory. The Stratix III product families operate with a 1.1V supply. Cyclone III and
Cyclone IV product families operate with a 1.2V supply. Lifetest is conducted at 1.32V and 1.44V
respectively, which is a 20% overvoltage. Lifetest uses dynamic life with a real clocked configuration
and was run at junction temperature of 125°C to keep it below absolute maximum ratings.
Stratix III EP3SL150 (DE3-150)
•142,000 logic elements (LEs)
•5,499K total memory Kbits
•384 18x18-bit multipliers blocks
•736 user I/Os"
|
|
|
|
|
I suspect that the reason you are seeing this message is that there is some problem with your local blockchain database. Failure to synchronize, to download new blocks, is the problem. However, you should check the version that you are currently using; if you used the Ubuntu software center, it still has version 0.3.24, which is a year and a half old.
Close Bitcoin, and open a terminal window to perform these operations.
Let's make a wallet backup just for the fun of it:
cp ~/.bitcoin/wallet.dat ~/wallet.backup.Nov2012
First check your version:
bitcoin-qt --help | grep version
You should see a line with the version number, here's the most recent:
Bitcoin-Qt version v0.7.1.0-geb49457-beta
If you do not have the latest version, lets get it and add it to the updates that will be automatically checked by Ubuntu (enter password when requested):
sudo apt-add-repository ppa:bitcoin/bitcoin
sudo apt-get update
sudo apt-get install bitcoin-qt
Check the version again; if it is not current, you may have previously downloaded another copy of Bitcoin to your home directory you will need to find and remove.
Now lets start Bitcoin in a way that will upgrade your wallet version and also perform a validation of some important files:
bitcoin-qt -upgradewallet -checkblocks=0 -checklevel=2 -printtoconsole &
(note:You will get to see all of Bitcoin's messages on the console instead of having them logged if you use -printtoconsole)
Messages after the long validation should start looking like this, indicating new blocks are coming:
received block 00000000000000981dbc
SetBestChain: new best=00000000000000981dbc height=206625 work=580312196692094599432 date=11/05/12 18:57:21
ProcessBlock: ACCEPTED
received block 000000000000043fa333
SetBestChain: new best=000000000000043fa333 height=206626 work=580326389011294426460 date=11/05/12 19:01:40
ProcessBlock: ACCEPTED
received block 0000000000000340e55b
SetBestChain: new best=0000000000000340e55b height=206627 work=580340581330494253488 date=11/05/12 19:03:42
ProcessBlock: ACCEPTED
received block 000000000000022e5c93
SetBestChain: new best=000000000000022e5c93 height=206628 work=580354773649694080516 date=11/05/12 19:23:54
ProcessBlock: ACCEPTED
This is what bad output might look like, and if so, we will need to do some fixing:
received block 00000000000000888968
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 00000000000001064014
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 00000000000002e26a33
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
If Bitcoin doesn't start downloading blocks after the above steps even with several connections, then we likely need to do further repairing. We will re-import all of the previously downloaded blockchain blocks, which may take several hours but won't need the network:
With Bitcoin shut down, we will rename the blockchain files:
cd ~/.bitcoin
mv blkindex.dat blkindex.bak
mv blk0001.dat blk0001.bak
mv blk0002.dat blk0002.bak
Now start Bitcoin with a command to re-import all data from the old blocks.
bitcoin-qt -loadblock=blk0001.bak -loadblock=blk0002.bak &
Bitcoin should start up with the message "Importing blockchain data file". This will take a long time to complete. After Bitcoin starts up, it should be syncronizing with the network again.
|
|
|
|
Hi, i don't have nothing on the wallet, yet, i'm just trying out ecoinpool, to try and get a pool running to test for a private pooling solution. Aparently only 0.6.3, works with ecoinpool. My problem is that i can´t import backed up blk*.dat files because the client gives me an error about blkindex.dat and i'm not being able to download the block chain. On top of that i'm trying to downgrade the client, wich i managed to, i think, figure out.
I'm o VM, now i can't point a miner to the pool to see if it works... I'm looking for some dyndns service for free that actually works...
Only problems!!! Well, thanks for you info.
If you don't need the current wallet and are just going to download the blockchain again, delete the entire .bitcoin directory, and install the version you want! |
|
|
|
|
First you must prepare the blockchain database so that it will be useable by an older version of bitcoin. Start the current bitcoind or bitcoin-qt with the command line bitcoin-qt -detachdb. After it starts up, close it (close bitcoind with the RPC command bitcoind stop true), which will take a few minutes of disk-writing behind the scenes to close the databases. After you have verified it is closed (you can check jobs with top) Then ensure you have a backup of the ~/.bitcoin/wallet.dat somewhere else (like a usb drive).
You can then uninstall the old version using the package management you used to install it (or just remove the file if you downloaded the executable), and use the new version.
|
|
|
|
So basically i uninstall all Gygabite drivers, manually remove DLL and download and install the file you mentionned ?
Will that mean I'll get less performance playing videogames with those older drivers ? Should my card not still be detected with the newest driver and at worse affect bitcoin mining performance ?
I wouldn't recommend this if it wasn't the right thing to doⒸ. If you underclock RAM for mining, you should set the RAM back for gaming. Newer versions of the AMD's OpenCL have changes that are to the detriment of Bitcoin mining performance. The driver will work if installed correctly, however I would recommend CGMiner or Phoenix software for mining - once it is configured you will have higher performance. |
|
|
|
I tried to address that here: https://bitcointalk.org/index.php?topic=121845.0Get the blockchain merge-mined by a lot of existing Bitcoin pool hashpower before it becomes active or generates coins. Otherwise there will always be some entity able to attack the working coin. One would need to convince a large percentage of exiting miners that the new blockchain is a worthwhile concept first. |
|
|
|
However, there was an error writing the blkindex.dat file; likely this file was corrupted, there is a disk CRC write error/bad block, or another Bitcoin is concurrently attempting to access it, etc. The error is unanticipated/unhandled by the code.
Huh. So any kind of failure to write to a critical file causes the client to either crash or hang while leaving the database in an inconsistent state without even displaying an error message? That seems like a pretty big oversight to me.  In this case, rebuilding the index, or restoring/redownloading the blockchain is the remedy.
For future reference, how exactly does one rebuild the index? I don't see any command-line options for doing this. Although it doesn't really help now, when Bitcoin 0.8.0 is released, it will have a new database system for storing the blockchain that will be more robust for the 4+ GB that Bitcoin has become. If you suspect that the database index is corrupt (blkindex.dat in the bitcoin data directory), it can be deleted, the blockchain files blk0001.dat and blk0002.dat moved out of the data directory (like to the root of C: drive) and then the blocks can be re-imported from these original blockchain files: bitcoin-qt -loadblock=c:\blk0001.dat -loadblock=c:\blk0002.dat |
|
|
|
|
Republitroll warning! Thinks a presidential election affects the Federal Reserve Cabal.
Election results:
Massachusetts (where Romney was governor): Mitt Romney 37%
Utah (land of the Mormon): Mitt Romney 74%
|
|
|
|
|
Show Posts
