Is there a linux daemon build? When I build from source, the daemon is giving me a segmentation fault core dumped error.
What version are you using of: I could provide it, but i haven't compiled static yet... will have it in a day or two.... The same versions that I use to run blakecoin, photon, and electron. git-core build-essential libssl-dev libboost-all-dev libdb5.1-dev libdb5.1++-dev libgtk2.0-dev libminiupnpc-dev qt4-qmake mingw32 synaptic qt-sdk qt4-dev-tools libqt4-dev libqt4-core libqt4-gui libdb++-dev
|
|
|
Is there a linux daemon build? When I build from source, the daemon is giving me a segmentation fault core dumped error.
Edit: getting the same error with the linux qt build
|
|
|
The block crawler doesn't seem to work for me either. Looking forward to further dev for this coin. will try to help out when I can.
|
|
|
Large transactions can have an issue I will look into it
Looks like it is going through. Thanks!
|
|
|
Hey Blue, Having some issues with auto payout for B+ on NY2. Doesn't look like it was processed by the pool. There is no tx #. ID for the payout is 114251. Subsequent payouts went through though.
|
|
|
Should we come up with 3 or 4 letter currency exchange friendly symbol for BlakeBitcoin / B+?
1. BBC 2. PLUS 3. BPLS 4. BLB
etc..
|
|
|
I don't mind hoarding the large eye candy when I type ./blakebitcoind getbalance, but this sounds like a failed launch to me.
Blockcount 26164 Difficulty: 0.09428520
The difficulty retarget is totally off. There is a new block every second and the difficulty is about the same as it was 8000 blocks ago. Mining is basically about who has the network speed to add a new block instead of actually solving the block. Whether it is a premine or a public instamine, this blockchain is not very useful. I suggest reboot now
|
|
|
Curious to see what is going on with this coin. On ny2.blakecoin.com, the network info shows Network Info Difficulty 0.02357130 Est Next Difficulty 3.31476450 (Change in 2 Blocks) Est. Avg. Time per Block 1 second Current Block 18338 After 18338 blocks, the difficulty is still <1? Sounds like a huge premine to me.
|
|
|
Please help ... When you connect to the server issues
Connecting to 207.210.117.83:27015 ... STEAM validation reject
How to deal with it? When you connect to the pool with cgminer? Which port are you using?
|
|
|
I am thinking it is a bitstream issue. If I remove the whole content of the bitstreams folder, I get the same results.
This is strange. My experience of removing the bitstreams folder (ie just having cgminer plus command scripts and forgetting to copy the bitstreams folder) is that cgminer will exit immediately with an error. You certainly should not see the four (green) done LEDs light on the ztex board(s) indicating a successful bitstream load. I wonder if this is a path issue? Perhaps in the past you did a "sudo make install" on the bitcoin cgminer and it has installed the bitcoin bitstream somewhere under /etc or some other unixy place like /usr/local and this is taking precedence over blake bitstream in the local bitstreams directory? Unfortunately the makefile is fiendishly complicated and it's not easy to tease out where this may be without actually running it. So I'll try that later today on a ubuntu 12.04 LTS VM (I don't want to meddle with my raspi production installation). What you could try in the meantime is "type cgminer" (or better "which cgminer") to check if it is already installed and where, I suspect the bitstreams directory is somewhere around there. EDIT: it's likely to be /usr/local/bin from my reading of the cgminer source, you can override with --kernel-path or -K. Bingo!!! It was a path issue. I did try a cgminer bitcoin "sudo make install" before and I found ztex bitstream files in /usr/local/bin/bitstreams. Replaced them with the blakecoin bitstreams and it is hashing great. Thanks so much!
|
|
|
Does anybody have cgminer-3.1.1 working for ztex 1.15y? I get 100% HW errors on a cluster of 1.15y (version1), running Ubuntu 12.04 LTS. I tried the 2 different bitstreams from the dropbox links https://www.dropbox.com/s/1ffqdaj1dowkd0j/ztex_ufm1_15y1-v06ad-t6-ucf-150MHz-fmax-157.bit https://www.dropbox.com/s/vk3k5sb64b8641o/ztex_ufm1_15y1-v06ad-2core-ucf-140MHz-fmax-147-fixed.bitcopied the files to the cgminer-3.1.1/bitstreams folder and renamed to ztex_ufm1_15y1.bit (deleted the old file) Neither bitstream seems to work. I also tried downclocking to 100MHz and still 100% HW. I am thinking it is a bitstream issue. If I remove the whole content of the bitstreams folder, I get the same results. I don't think it is cgminer because I have it running on a cluster of 1.15x on a separate Ubuntu box that was built the same way. Does anybody know how I can check to see which bitstream is loaded by cgminer? I also want to thank Kramble for the files and personally helping me with building cgminer on ubuntu. Thanks to hal7 for the 1.15x bitstream. CA Coins sudo ./cgminer --disable-gpu --url stratum+tcp://eu1.blakecoin.com:3334 --userpass userpass:password 2>log.txt
|
|
|
PNkcEMP6rsYX83839tfv2LK43mwuXeUjPD
Thanks!
|
|
|
Item sold via PM. Thanks for bidding.
|
|
|
0.85
Highest bid so far. Bidding will end at 8AM PST, in about 5 hours. Thanks.
|
|
|
Highest bid so far 0.80BTC via PM. Thanks.
|
|
|
Highest bid so far 0.72BTC via PM. Thanks.
|
|
|
Shipping will be from California, USA as samples.
|
|
|
Payment in BTC only. Willing to do escrow if desired. Escrow and shipping pay for by buyer. Minimum offer 0.25BTC. 1BTC or best offer by Nov 27, 2013, 8AM PST. Will ship Nov 27. Brand new. Never used. I have a V3 M board and got this card in error. Stand alone H card only. Does not include RPi or M card. Not compatible with V3 M cards. See http://www.bitfurystrikesback.com/product/bfsb-h-card-v1-2/
|
|
|
I assume it's ok to run power to both the pci express power connectors and the 12V/GND screw terminals?
|
|
|
Hi guys - since the latest round of H-cards was shipped at .865v, rigs pull significantly higher wattage. I'm seeing signs of connector burn & overloaded power supplies with some customers. Please be safe - if you are overclocking or running a full rig, a 1200 watt supply is probably a better choice.
Keep your rigs away from flammables - remember these are high-wattage devices!
I've been a little out of touch, sorry if this comes late - we don't have these problems at the data center. We use a 10g high strand count copper wire between 12v supply and the metal lugs on the M-board. The length of our power cables is only about 12 inches.
Best, Dave
Just to clarify after reading the fire hazard thread. I am using 2 separate pci express power connectors to power a full rig right now. Should I also power the 12V/GND power connectors on the other end of the M-board? The rigs have been running stable for the past month. V3M/V2.2H/Corsair 870 platinum, stock settings, about 650W at the wall
|
|
|
|