Search content
Sort by
Showing 20 of 55 results by FnuGk
Linux hands down is going to be more profitable if you know what you're doing. We ran extensive tests on 58xx and 69xx systems running both Windows XP and Ubuntu 11 even with the "limited" overclocking controls we found Linux to be faster by far than Windows. Keep in mind that we first searched for the sweet spot of profitability, sometimes overclocking reduces your profit margin.
Long term this is a game about maximizing profit, and while maxing out MH/s seems like the thing to do, you should be much more concerned with MH/J, we found that over clocking outside of the 'normal' settings, resulted in a lower MH/J in all cases.
Long term this is a game about maximizing profit, and while maxing out MH/s seems like the thing to do, you should be much more concerned with MH/J, we found that over clocking outside of the 'normal' settings, resulted in a lower MH/J in all cases.
Then you obviously don't know what you are doing. Post some settings and screenshots and we'll soon find out if you're talking fanboy crap. With a 5830 the best hash rate you're going to get is around 330 MHz in Windows. "Faster by far" would be around 400 MHz. So, lets see then.
He is not talking mhz here. He is talking overall profit.
If OS A. gives 1000 MH using 500wats = 1000/500= 2
OS B. Gives 1200 MH using 550wats = 1200/500= 1,83333333
in this examble OS B i clearly filling you butcoin wallet faster but in return it is emptying it even faster than OS A. making it less desirable if you want to maximize your profit.
for all those who cant get linux on their ps3 here is some new hope:
http://www.engadget.com/2011/05/06/otheros-brings-linux-back-to-the-ps3-taunts-sony/
http://gitbrew.org/otheros/
http://www.engadget.com/2011/05/06/otheros-brings-linux-back-to-the-ps3-taunts-sony/
http://gitbrew.org/otheros/
This is my rig:
http://lh4.ggpht.com/_hVOW2U7K4-M/SgJdv7g6L2I/AAAAAAABAf0/JyEPtSpnWa4/s640/847870190_63e8e76ac5.jpg
My other one uses carrots.
http://lh4.ggpht.com/_hVOW2U7K4-M/SgJdv7g6L2I/AAAAAAABAf0/JyEPtSpnWa4/s640/847870190_63e8e76ac5.jpg
My other one uses carrots.
Do we have a winner?
Re: [announce] Namecoin - a distributed naming system based on Bitcoin
downloaded the namecoin source from github unzipped it and put it in the trunks folder.
how else should this be compiled?? (i am no programmer and have no idea what im doing besides following the manual)
how else should this be compiled?? (i am no programmer and have no idea what im doing besides following the manual)
Trunks folder?
this is the guide i am following. I am changing bitcoin to namecoin and then instead of the first step of checking the bitcoin source out from svn i am putting the namecoin source in the same folder:
Code:
Copyright (c) 2010 Laszlo Hanyecz
Distributed under the MIT/X11 software license, see the accompanying
file license.txt or http://www.opensource.org/licenses/mit-license.php.
This product includes software developed by the OpenSSL Project for use in
the OpenSSL Toolkit (http://www.openssl.org/). This product includes
cryptographic software written by Eric Young (eay@cryptsoft.com).
Mac OS X build instructions
Laszlo Hanyecz (solar@heliacal.net)
Tested on 10.5 and 10.6 intel. PPC is not supported because it's big-endian.
All of the commands should be executed in Terminal.app.. it's in
/Applications/Utilities
You need to install XCode with all the options checked so that the compiler
and everything is available in /usr not just /Developer
I think it comes on the DVD but you can get the current version from
http://developer.apple.com
1. Pick a directory to work inside.. something like ~/bitcoin works. The
structure I use looks like this:
(~ is your home directory)
~/bitcoin
~/bitcoin/trunk # source code
~/bitcoin/deps # dependencies.. like libraries and headers needed to compile
~/bitcoin/Bitcoin.app # the application bundle where you can run the app
Just execute: mkdir ~/bitcoin
This will create the top dir for you..
WARNING: do not use the ~ notation with the configure scripts.. use the full
name of the directory, for example /Users/james/bitcoin/deps for a user named
'james'. In my examples I am using 'macosuser' so make sure you change that.
2. Check out the trunk version of the bitcoin code from subversion:
cd ~/bitcoin
svn checkout https://bitcoin.svn.sourceforge.net/svnroot/bitcoin/trunk
This will make ~/bitcoin/trunk for you with all the files from subversion.
3. Get and build the dependencies
Boost
-----
Download from http://www.boost.org/users/download/
I'm assuming it ended up in ~/Downloads..
mkdir ~/bitcoin/deps
cd ~/bitcoin/deps
tar xvjf ~/Downloads/boost_1_42_0.tar.bz2
cd boost_1_42_0
./bootstrap.sh
./bjam architecture=combined address-model=32_64 macosx-version=10.6 macosx-version-min=10.5 link=static runtime-link=static --toolset=darwin --prefix=/Users/macosuser/bitcoin/deps install
This part takes a while.. use your judgement and fix it if something doesn't
build for some reason.
Change the prefix to whatever your directory is (my username in this example
is macosuser). I'm also running on 10.6 so i have macosx-version=10.6 change
to 10.5 if you're using leopard.
This is what my output looked like at the end:
...failed updating 2 targets...
...skipped 144 targets...
...updated 8074 targets...
OpenSSL
-------
Download from http://www.openssl.org/source/
We would like to build this as a 32 bit/64 bit library so we actually build it
2 times and join it together here.. If you downloaded with safari it already
uncompressed it so it will just be a tar not a tar.gz
cd ~/bitcoin/deps
tar xvf ~/Downloads/openssl-1.0.0.tar
mv openssl-1.0.0 openssl-1.0.0-i386
tar xvf ~/Downloads/openssl-1.0.0.tar
mv openssl-1.0.0 openssl-1.0.0-x86_64
# build i386 (32 bit intel) binary
cd openssl-1.0.0-i386
./Configure --prefix=/Users/macosuser/bitcoin/deps --openssldir=/Users/macosuser/deps/openssl darwin-i386-cc && make
make install # only do this on one of the architectures, to install the headers
cd ..
# build x86_64 (64 bit intel) binary
cd openssl-1.0.0-x86_64
./Configure --prefix=/Users/macosuser/bitcoin/deps --openssldir=/Users/macosuser/deps/openssl darwin64-x86_64-cc && make
cd ..
# combine the libs
cd ~/bitcoin/deps
lipo -arch i386 openssl-1.0.0-i386/libcrypto.a -arch x86_64 openssl-1.0.0-x86_64/libcrypto.a -o lib/libcrypto.a -create
lipo -arch i386 openssl-1.0.0-i386/libssl.a -arch x86_64 openssl-1.0.0-x86_64/libssl.a -o lib/libssl.a -create
Verify your binaries
file lib/libcrypto.a
output should look like this:
ib/libcrypto.a: Mach-O universal binary with 2 architectures
lib/libcrypto.a (for architecture i386): current ar archive random library
lib/libcrypto.a (for architecture x86_64): current ar archive random library
Berkeley DB
-----------
Download from http://freshmeat.net/projects/berkeleydb/
cd ~/bitcoin/deps
tar xvf ~/Downloads/db-4.8.26.tar
cd db-4.8.26/build_unix
../dist/configure --prefix=/Users/macosuser/bitcoin/deps --enable-cxx && make && make install
wxWidgets
---------
This is the big one..
Check it out from svn
cd ~/bitcoin/deps
svn checkout http://svn.wxwidgets.org/svn/wx/wxWidgets/trunk wxWidgets-trunk
This will make a wxWidgets-trunk directory in deps.
Use this script snippet, change your prefix to whatever your dir is:
PREFIX=~/bitcoin/deps
SRCDIR="$PREFIX/wxWidgets-trunk"
BUILDDIR="$SRCDIR/macbuild"
cd "$PREFIX" &&
#svn checkout http://svn.wxwidgets.org/svn/wx/wxWidgets/trunk wxWidgets-trunk &&
cd "$SRCDIR" &&
[ -f include/wx/hashmap.h.orig ] || cp include/wx/hashmap.h include/wx/hashmap.h.orig &&
sed 's/if wxUSE_STL/if 0 \&\& wxUSE_STL/g' < include/wx/hashmap.h.orig > include/wx/hashmap.h &&
[ -f include/wx/hashset.h.orig ] || cp include/wx/hashset.h include/wx/hashset.h.orig &&
sed 's/if wxUSE_STL/if 0 \&\& wxUSE_STL/g' < include/wx/hashset.h.orig > include/wx/hashset.h &&
rm -vrf "$BUILDDIR" &&
mkdir "$BUILDDIR" &&
cd "$BUILDDIR" &&
../configure --prefix="$PREFIX" \
--with-osx_cocoa \
--disable-shared \
--disable-debug_flag \
--with-macosx-version-min=10.5 \
--enable-stl \
--enable-utf8 \
--enable-universal_binary \
--with-libjpeg=builtin \
--with-libpng=builtin \
--with-regex=builtin \
--with-libtiff=builtin \
--with-zlib=builtin \
--with-expat=builtin \
--with-macosx-sdk=/Developer/SDKs/MacOSX10.5.sdk &&
find . -name Makefile |
while read i; do
echo $i;
sed 's/-arch i386/-arch i386 -arch x86_64/g' < "$i" > "$i".new &&
mv "$i" "$i".old &&
mv "$i".new "$i";
done
make &&
make install
Now you should be able to build bitcoin
cd ~/bitcoin/trunk
make -f makefile.osx bitcoin
Before you can run it, you need to create an application bundle for Mac OS.
Create the directories in terminal using mkdir and copy the files into place.
They are available at http://heliacal.net/~solar/bitcoin/mac-build/
You need the Info.plist and the .ins file. The Contents/MacOS/bitcoin file is
the output of the build.
Your directory structure should look like this:
Bitcoin.app
Bitcoin.app/Contents
Bitcoin.app/Contents/Info.plist
Bitcoin.app/Contents/MacOS
Bitcoin.app/Contents/MacOS/bitcoin
Bitcoin.app/Contents/Resources
Bitcoin.app/Contents/Resources/BitcoinAppIcon.icns
To run it you can just click the Bitcoin.app in Finder, or just do open
~/bitcoin/Bitcoin.app
If you want to run it with arguments you can just run it without backgrounding
by specifying the full name in terminal:
~/bitcoin/Bitcoin.app/Contents/MacOS/bitcoin -addnode=192.75.207.66
Distributed under the MIT/X11 software license, see the accompanying
file license.txt or http://www.opensource.org/licenses/mit-license.php.
This product includes software developed by the OpenSSL Project for use in
the OpenSSL Toolkit (http://www.openssl.org/). This product includes
cryptographic software written by Eric Young (eay@cryptsoft.com).
Mac OS X build instructions
Laszlo Hanyecz (solar@heliacal.net)
Tested on 10.5 and 10.6 intel. PPC is not supported because it's big-endian.
All of the commands should be executed in Terminal.app.. it's in
/Applications/Utilities
You need to install XCode with all the options checked so that the compiler
and everything is available in /usr not just /Developer
I think it comes on the DVD but you can get the current version from
http://developer.apple.com
1. Pick a directory to work inside.. something like ~/bitcoin works. The
structure I use looks like this:
(~ is your home directory)
~/bitcoin
~/bitcoin/trunk # source code
~/bitcoin/deps # dependencies.. like libraries and headers needed to compile
~/bitcoin/Bitcoin.app # the application bundle where you can run the app
Just execute: mkdir ~/bitcoin
This will create the top dir for you..
WARNING: do not use the ~ notation with the configure scripts.. use the full
name of the directory, for example /Users/james/bitcoin/deps for a user named
'james'. In my examples I am using 'macosuser' so make sure you change that.
2. Check out the trunk version of the bitcoin code from subversion:
cd ~/bitcoin
svn checkout https://bitcoin.svn.sourceforge.net/svnroot/bitcoin/trunk
This will make ~/bitcoin/trunk for you with all the files from subversion.
3. Get and build the dependencies
Boost
-----
Download from http://www.boost.org/users/download/
I'm assuming it ended up in ~/Downloads..
mkdir ~/bitcoin/deps
cd ~/bitcoin/deps
tar xvjf ~/Downloads/boost_1_42_0.tar.bz2
cd boost_1_42_0
./bootstrap.sh
./bjam architecture=combined address-model=32_64 macosx-version=10.6 macosx-version-min=10.5 link=static runtime-link=static --toolset=darwin --prefix=/Users/macosuser/bitcoin/deps install
This part takes a while.. use your judgement and fix it if something doesn't
build for some reason.
Change the prefix to whatever your directory is (my username in this example
is macosuser). I'm also running on 10.6 so i have macosx-version=10.6 change
to 10.5 if you're using leopard.
This is what my output looked like at the end:
...failed updating 2 targets...
...skipped 144 targets...
...updated 8074 targets...
OpenSSL
-------
Download from http://www.openssl.org/source/
We would like to build this as a 32 bit/64 bit library so we actually build it
2 times and join it together here.. If you downloaded with safari it already
uncompressed it so it will just be a tar not a tar.gz
cd ~/bitcoin/deps
tar xvf ~/Downloads/openssl-1.0.0.tar
mv openssl-1.0.0 openssl-1.0.0-i386
tar xvf ~/Downloads/openssl-1.0.0.tar
mv openssl-1.0.0 openssl-1.0.0-x86_64
# build i386 (32 bit intel) binary
cd openssl-1.0.0-i386
./Configure --prefix=/Users/macosuser/bitcoin/deps --openssldir=/Users/macosuser/deps/openssl darwin-i386-cc && make
make install # only do this on one of the architectures, to install the headers
cd ..
# build x86_64 (64 bit intel) binary
cd openssl-1.0.0-x86_64
./Configure --prefix=/Users/macosuser/bitcoin/deps --openssldir=/Users/macosuser/deps/openssl darwin64-x86_64-cc && make
cd ..
# combine the libs
cd ~/bitcoin/deps
lipo -arch i386 openssl-1.0.0-i386/libcrypto.a -arch x86_64 openssl-1.0.0-x86_64/libcrypto.a -o lib/libcrypto.a -create
lipo -arch i386 openssl-1.0.0-i386/libssl.a -arch x86_64 openssl-1.0.0-x86_64/libssl.a -o lib/libssl.a -create
Verify your binaries
file lib/libcrypto.a
output should look like this:
ib/libcrypto.a: Mach-O universal binary with 2 architectures
lib/libcrypto.a (for architecture i386): current ar archive random library
lib/libcrypto.a (for architecture x86_64): current ar archive random library
Berkeley DB
-----------
Download from http://freshmeat.net/projects/berkeleydb/
cd ~/bitcoin/deps
tar xvf ~/Downloads/db-4.8.26.tar
cd db-4.8.26/build_unix
../dist/configure --prefix=/Users/macosuser/bitcoin/deps --enable-cxx && make && make install
wxWidgets
---------
This is the big one..
Check it out from svn
cd ~/bitcoin/deps
svn checkout http://svn.wxwidgets.org/svn/wx/wxWidgets/trunk wxWidgets-trunk
This will make a wxWidgets-trunk directory in deps.
Use this script snippet, change your prefix to whatever your dir is:
PREFIX=~/bitcoin/deps
SRCDIR="$PREFIX/wxWidgets-trunk"
BUILDDIR="$SRCDIR/macbuild"
cd "$PREFIX" &&
#svn checkout http://svn.wxwidgets.org/svn/wx/wxWidgets/trunk wxWidgets-trunk &&
cd "$SRCDIR" &&
[ -f include/wx/hashmap.h.orig ] || cp include/wx/hashmap.h include/wx/hashmap.h.orig &&
sed 's/if wxUSE_STL/if 0 \&\& wxUSE_STL/g' < include/wx/hashmap.h.orig > include/wx/hashmap.h &&
[ -f include/wx/hashset.h.orig ] || cp include/wx/hashset.h include/wx/hashset.h.orig &&
sed 's/if wxUSE_STL/if 0 \&\& wxUSE_STL/g' < include/wx/hashset.h.orig > include/wx/hashset.h &&
rm -vrf "$BUILDDIR" &&
mkdir "$BUILDDIR" &&
cd "$BUILDDIR" &&
../configure --prefix="$PREFIX" \
--with-osx_cocoa \
--disable-shared \
--disable-debug_flag \
--with-macosx-version-min=10.5 \
--enable-stl \
--enable-utf8 \
--enable-universal_binary \
--with-libjpeg=builtin \
--with-libpng=builtin \
--with-regex=builtin \
--with-libtiff=builtin \
--with-zlib=builtin \
--with-expat=builtin \
--with-macosx-sdk=/Developer/SDKs/MacOSX10.5.sdk &&
find . -name Makefile |
while read i; do
echo $i;
sed 's/-arch i386/-arch i386 -arch x86_64/g' < "$i" > "$i".new &&
mv "$i" "$i".old &&
mv "$i".new "$i";
done
make &&
make install
Now you should be able to build bitcoin
cd ~/bitcoin/trunk
make -f makefile.osx bitcoin
Before you can run it, you need to create an application bundle for Mac OS.
Create the directories in terminal using mkdir and copy the files into place.
They are available at http://heliacal.net/~solar/bitcoin/mac-build/
You need the Info.plist and the .ins file. The Contents/MacOS/bitcoin file is
the output of the build.
Your directory structure should look like this:
Bitcoin.app
Bitcoin.app/Contents
Bitcoin.app/Contents/Info.plist
Bitcoin.app/Contents/MacOS
Bitcoin.app/Contents/MacOS/bitcoin
Bitcoin.app/Contents/Resources
Bitcoin.app/Contents/Resources/BitcoinAppIcon.icns
To run it you can just click the Bitcoin.app in Finder, or just do open
~/bitcoin/Bitcoin.app
If you want to run it with arguments you can just run it without backgrounding
by specifying the full name in terminal:
~/bitcoin/Bitcoin.app/Contents/MacOS/bitcoin -addnode=192.75.207.66
Re: [announce] Namecoin - a distributed naming system based on Bitcoin
So im trying to compile it.
i am following the guide for bitcoin that comes with the source code but instead of checking out from the svn as the guide tells me i am putting the namecoin source in the "trunks" folder.
am i doinng it right?
i am following the guide for bitcoin that comes with the source code but instead of checking out from the svn as the guide tells me i am putting the namecoin source in the "trunks" folder.
am i doinng it right?
Namecoin is in a git repository.
how else should this be compiled?? (i am no programmer and have no idea what im doing besides following the manual)
Re: [announce] Namecoin - a distributed naming system based on Bitcoin
So im trying to compile it.
i am following the guide for bitcoin that comes with the source code but instead of checking out from the svn as the guide tells me i am putting the namecoin source in the "trunks" folder.
am i doinng it right?
i am following the guide for bitcoin that comes with the source code but instead of checking out from the svn as the guide tells me i am putting the namecoin source in the "trunks" folder.
am i doinng it right?
Re: [announce] Namecoin - a distributed naming system based on Bitcoin
could someone explain exactly what is this?
is it just a a bitcoin clone using another blockchain or what is it?
also give me a OS X binary so i can run this thing
is it just a a bitcoin clone using another blockchain or what is it?
also give me a OS X binary so i can run this thing
It's a distributed domain name registration system that use bitcoin technology, meant to solve the takedown problem.
this confuses me anymore. what does domain names have to do with anything?
Re: [announce] Namecoin - a distributed naming system based on Bitcoin
could someone explain exactly what is this?
is it just a a bitcoin clone using another blockchain or what is it?
also give me a OS X binary so i can run this thing
is it just a a bitcoin clone using another blockchain or what is it?
also give me a OS X binary so i can run this thing
he means a zacate on a mb...
Lets wait for Llanos APUs... those cpus will make a fine mbs for mining as the integrated igp can me added for extra mhash/s
Lets wait for Llanos APUs... those cpus will make a fine mbs for mining as the integrated igp can me added for extra mhash/s
was also wondering about Llanos speed but didnt ask yet as they are not out yet. But what reasoning would there be to get the better cpu for mining? It will also have a higher power draw making it less ideal to use as a always on home server. The gpu will be better though but enough to compensate for the higher tdp?
I know it's an old thread but with the e350 motherboards with an x4 (but x16 form factor) PCIe slot, could the CPU keep a faster card fed? Say, if I put a 5870/6870 in the slot, would it be a total waste?
I'm looking for low power mining to stick in the cabinet with my surveillance DVR (ooh, wonder what that has inside...) and it would be good if I could pull 250-300Mhash/s out of it.
I'm looking for low power mining to stick in the cabinet with my surveillance DVR (ooh, wonder what that has inside...) and it would be good if I could pull 250-300Mhash/s out of it.
cant really see why it wouldn't work. Mining take next to no cpu so my guess is the e350 should be good enough.
Remember you would then have two gfx cards (the igp and the 5870/6870)
I just installed the 270.61 nvidia drivers, and it seems to make the drivers crash each time I exit poclbm by clicking the x, if I ctrl-c they seem to exit fine most of the time. Nothing serious yet, but I keep getting these in my system event log:
"Display driver nvlddmkm stopped responding and has successfully recovered."
http://i.imgur.com/VrnJn.png
"Display driver nvlddmkm stopped responding and has successfully recovered."
http://i.imgur.com/VrnJn.png
have you done any overclocking?
in a set and forget set-up system preferences should not play any role imo.
I dont like to use BSD in my day to day work but for setting up a file server it is pretty good as it draws next to no idle power.
I think the op is asking if linux would give better hash rates than windows. Also if a non gui linux distro would give better hash rate than a gui dristro.
I dont like to use BSD in my day to day work but for setting up a file server it is pretty good as it draws next to no idle power.
I think the op is asking if linux would give better hash rates than windows. Also if a non gui linux distro would give better hash rate than a gui dristro.
UPDATE/EDIT: If it matters, I may add on a third and/or fourth GPU to the system later. Running a 1k watt PSU in the rig right now with ample space and airflow.
Do you plan to use water cooling ? How else can you fit 4 cards in one MB ? I would recommend mining on Windows, of course. Unless you are going to install more than 2x5970 or 4x5870
why is windows recommended over linux?
if you do your over clocking in windows and then flash the gfx bios then all voltage settings and such works in linux as well
Re: Is it possible to get bitcoins to use like 95% of your GPU?
if flash crashes your card is unstable.
if it is overclocked you have pushed it too far. Try installing 3dmark06 and make it loop the two first test 5-10 times and see if that crashes. If it does you have to lower the clocks
if it is overclocked you have pushed it too far. Try installing 3dmark06 and make it loop the two first test 5-10 times and see if that crashes. If it does you have to lower the clocks
Hi diablod3 I am facing some issues using this miner with dual 6990. With -f 1 the hash rates drop to a whooping 600000 low. I tested out different flags and found that -f 17 to 20 is the best with the highest at 1ghash/s. This is very stable compared to poclbm which fluctuates from 800mhash to 1.2ghash. I am using 11.3 + 2.4 sdk like u recommend. The preview 11.4 drivers + 2.4 sdk yield the same results. I am using windows 7 64 bit. And the only way to get the software to recognise the dual 6990 is to crossfire them. Any advice u could give me?
Thank you =)
Thank you =)
you need a dummy plug in the 2nd card to make the os see it
the new intel igp does support openCL just like nvidia and amd cards do please post your hash rates
This card is in no way new. It's perhaps 4 years old?good luck. you're probably gonna get 5 MH/s, max
@casascius If you think running old hardware is a waste I gladly accept donations to buy better hardware
wow i have a 8800gt that also have a few years on it and it does close to 30mhash/s the same machine have a core 2 duo clocked at about 3.5 and it does 8mhash/s
so that makes your 8600gt SLOWER than my c2d cpu !?