Hi all,
I've been configuring my Raspberry Pi this weekend in anticipation of receiving my DualMiners on Monday. The instructions are really good, but I did run into a few bumps that I thought I'd let people know about.
First, I found that the "configure" script did not have execute permissions. The current instructions show setting execute permissions for the autogen.sh script, but you also have to do it for the configure script as well. It's kind of strange that these don't have the correct permissions in the git repository. That should probably be fixed to reduce friction for new users while setting up.
Second, after building cgminer from the git sources, I kept getting a "Unexpected extra commandline arguments" when calling the binary with a config file. At first I thought that the config file might have a problem in it, but after trial and error I found that there was nothing wrong with it.
It turns out that I the real problem was that cgminer was not happy unless I set the current directory to be the "bin" folder where it was installed. If I cd'd to the installed bin folder, it worked with the same config.
That's when I remembered that the build instructions indicated that the "configure" command should have a --prefix option, overriding the usual install location to sub folders in the source tree. I thought that was odd at the time, and different than the usual "configure/make/sudo make install" pattern, but I followed along anyway.
CruzCoins, did you specify the prefix folder for a reason? Maybe you're a developer and you need to manage multiple versions of cgminer? That would explain the need to control where it gets installed.
I think for an average user like me, who is only going to need a single copy of cgminer running on a dedicated Raspberry Pi that will only talk to DualMiners, it makes more sense to configure the sources to install in the usual "/usr/local" locations, which means leaving off the --prefix option.
Here's the steps that I used to build, with the above changes:
git clone git://github.com/dualminer/dualminer-cgminer.git cgminer
cd cgminer
sudo chmod +x autogen.sh
sudo chmod +x configure
./autogen.sh
./configure --enable-dualminer --enable-scrypt --disable-opencl
make
sudo make install
Note that the "sudo" for the "make install" is required and normal because it will install the binary and libraries in the root owned /usr/local.
Once built and installed, you should be able to call cgminer from any directory, assuming that /usr/local/bin is on your path. I'm not a Raspberry Pi expert, but I think that this is included in your path by default. At least it was on my system.
Third, while setting up mineninja using the instructions from the DualMiner support website, I noticed that in several cases the HTML instructions had curly quotes. I think that if you copy these directly from the website, they probably won't work when pasted to your command line. So I replaced the curly quotes with regular ones before using any copied commands.
In particular, here's the mysql line granting privileges to the "anubis" user with non-curly quotes:
GRANT ALL PRIVILEGES ON anubis.* TO 'anubis'@'localhost' IDENTIFIED BY 'your password here my passwd is root';
If use of curly quotes is a real problem, and not just imagined by me, then maybe the site author could consider straightening the quotes so that other people won't have problems copying the commands.
Lastly, once I got mineninja running I used it to change the config. But when the web app saved the config file, it nuked the custom config settings that I had manually placed via text editor. I guess it did a complete replace of the config file rather than reading the existing config and extending it.
I assume that this is a mineninja "feature" and nothing to do with DualMiner or their port of the web app. I have to admit that I know next to nothing about mineninja at this point.
I just mention it here in case anyone tries using this mineninja and have manually edited their config (perhaps to set the --dualminer-pll option to your desired frequency, which I suspect is a pretty common thing to do). Instead, you'll probably have to pass this on the command line in the script you use to launch cgminer and keep it out of the config file.
That's about all that I ran into so far. Most of the issues are just nits anyway. I'm pretty impressed as to how easy this setup has been.
Looking forward to receiving my DualMiners so that I can get started doing some actual mining ;-)
