Bitcoin Forum
May 24, 2024, 05:12:16 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1] 2 3 »
1  Bitcoin / Hardware / Re: [ANN] Introduction to DualMiner USB (could mine both BTC and LTC) on: March 17, 2014, 08:16:12 PM
Please just follow my guide as it would have prevented all of the errors you are encountering. Go through the guide in my signature step by step before reporting back more problems.
2  Bitcoin / Hardware / Re: [ANN] Introduction to DualMiner USB (could mine both BTC and LTC) on: March 17, 2014, 07:02:26 PM
Got to Step 3-3:
But get the following error ... any thoughts?

pi@raspberrypi ~ $ cd cgminer
pi@raspberrypi ~/cgminer $ sudo chmod +x autogen.sh
pi@raspberrypi ~/cgminer $ ./autogen.sh
./autogen.sh: 6: ./autogen.sh: autoreconf: not found
Configuring...
./autogen.sh: 10: ./autogen.sh: /home/pi/cgminer/configure: Permission denied




-----------------------------------------
Step 3-3:
Install some packages  needed by dualminer source code
sudo apt-get update
sudo apt-get install libudev-dev libcurl4-openssl-dev
sudo apt-get install vim(Optinal : edit file tool )
Then you can get dualminer https://github.com/dualminer
git clone git://github.com/dualminer/dualminer-cgminer.git cgminer
cd cgminer
sudo chmod +x autogen.sh
./autogen.sh

------------------------------
pi@raspberrypi ~ $ git clone git://github.com/dualminer/dualminer-cgminer.git cgminer
Cloning into 'cgminer'...
remote: Reusing existing pack: 254, done.
remote: Total 254 (delta 0), reused 0 (delta 0)
Receiving objects: 100% (254/254), 3.88 MiB | 1.24 MiB/s, done.
Resolving deltas: 100% (27/27), done.
Checking out files: 100% (221/221), done.
pi@raspberrypi ~ $ cd cgminer
pi@raspberrypi ~/cgminer $ sudo chmod +x autogen.sh
pi@raspberrypi ~/cgminer $ ./autogen.sh
./autogen.sh: 6: ./autogen.sh: autoreconf: not found
Configuring...
./autogen.sh: 10: ./autogen.sh: /home/pi/cgminer/configure: Permission denied


Code:
sudo chmod +x /home/pi/cgminer/autogen.sh
will probably need to do the same for configure. that should fix your problem.
3  Bitcoin / Hardware / Re: [ANN] Introduction to DualMiner USB (could mine both BTC and LTC) on: March 17, 2014, 02:57:22 AM
has anyone successfully been able to get 10 dualminers on an orico or etekcity 10 port powered hub?

also has anyone been able to get more than 4 dualminers working with the modified cgminer that's out for these things? I can get it working with 4 but any more than that and cgminer crashes
Please follow the guide in my signature if you are having trouble running your DMs. Only 9 DMs are stable on orico p10-u2 hubs. Using the cgminer build from github I am running 99 units.

so you changed all the ports to the USB ports using Zadig and can get more than 4 units to launch in cgminer?

hmm, maybe its because im on windows.. aren't you un raspberry pi?
I have had success with dualminer's github custom cgminer in Raspbian and Ubuntu. I have had success running larger arrays in Windows but I have only found stability for very large arrays in linux. Are you using the windows client with cgminer and a GUI from dualminer.com, or are you using the cgminer from dualminer github?
4  Bitcoin / Hardware / Re: [ANN] Introduction to DualMiner USB (could mine both BTC and LTC) on: March 16, 2014, 11:34:35 PM
has anyone successfully been able to get 10 dualminers on an orico or etekcity 10 port powered hub?

also has anyone been able to get more than 4 dualminers working with the modified cgminer that's out for these things? I can get it working with 4 but any more than that and cgminer crashes
Please follow the guide in my signature if you are having trouble running your DMs. Only 9 DMs are stable on orico p10-u2 hubs. Using the cgminer build from github I am running 99 units.
5  Bitcoin / Hardware / Re: [ANN] Introduction to DualMiner USB (could mine both BTC and LTC) on: March 12, 2014, 04:36:15 PM
The HW error is expected, especially, when DM works above 850Mhz.
The HW error means a returned nonce result does NOT meet the mining target requirement (if you know some mining theory) . This could happen in some cases:
1. The chip could do a wrong calculation. If it is overclocked, the chip could generate more error. That's why 850MHz will give more errors than 800Mhz.
2. Some errors could happen in the communication between DM device and cgminer. Something like uart buffer overflow.

Since higher clock frequency could introduce instability of the electronic signal, most of HW error is caused by the first reason.

HW error is different to the reject error. Reject error is caused by mining pool. If a new block had been generated and DM was still working on previous job, some nonces of previous job maybe still queued in a buffer of cgminer. If cgminer submit these old result to pool, the pool will reject them.

Thanks for getting back to me dualminer_3. I realize that rejects are different than hardware errors. And I also realize that some number of hardware errors is expected with Dual Miners. I'm just interested in whether I'm seeing an expected hardware error rate.

I've been running cgminer for 20 hours without the "--dualminer-pll 850" command line and have had a total of 53 errors across 20 units. If I assume that this rate is fairly consistent, then I can estimate that I would see an average of 3 hardware errors per unit per day.

Is that a reasonable and expected rate?

If it isn't, then what can I do to diagnose and fix this?

Remember that I mentioned that I have two fans plugged into the same USB hubs where I have Dual Miners. Could these be making electrical noise or cause power fluctuations? If so, I can move them to a dedicated hub.

Thanks in advance for any further advice you might have.
From my experience as long as your error are spread about, it seems to be a reasonable/expected rate currently. If you have a spare hub it may not be a bad idea to separate your DMs from fans that may pull lots of energy/create lots of vibration.
6  Bitcoin / Hardware / Re: [ANN] Introduction to DualMiner USB (could mine both BTC and LTC) on: March 11, 2014, 03:55:40 PM
After running 20 DualMiner 2 units for about 12 hours, I've seen a total of 46 hardware errors as reported by mineninja. The errors are roughly distributed across the units. Only one of them had no errors.

Is this a normal error rate?

Note that I've got fans blowing over the units so I doubt this is a heat problem.

When I grep'd the log, the errors are all like the following example:

Code:
 [2014-03-10 19:17:25] DM11: invalid nonce - HW error

Note that when I count the error lines from the grep of the log, it shows twice as many hardware errors as reported by mineninja. Maybe cwminer double outputs the errors? I'm not clear which error total is more accurate.

In case it's relevant, I am running with the following command line because I wanted to try to increase the hash rate: --dualminer-pll 850

Should I stop using that frequency option? I don't see an appreciable increase in hash rate anyway. I'm seeing an average of around 66.5 KHs across the units currently.

I would remove the -pll 850 parameter. I am getting appropriate hashrate without using the -dualminer-pll parameter, and I have noticed instability when using this parameter on previous versions of cgminer. Regarding your invalid nonce error, I get those too occasionally, though you should see less once you drop your pll parameter.  Are you mining over a wifi connection? This would be the next thing I investigate if removing the non-necessary parameters doesn't help and you are using 9 DMs per p10-u2.
7  Bitcoin / Bitcoin Technical Support / Re: Avoiding One Person in Control of Company [btc] Wallet's Password? on: March 08, 2014, 09:38:41 PM
Suppose I am working with a company that wants to accept Bitcoin for international trades.

The company, for security reasons, would not want a single one of its employees to have access to the company BTC wallet's password. Any transaction would have to meet the approval of more than one employee.

Is this possible already? If not, how could it be implemented with public-key cryptography?

thanks
Maybe you would be looking for a threshold scheme. http://en.wikipedia.org/wiki/Secret_sharing
8  Bitcoin / Hardware / Re: [ANN] Introduction to DualMiner USB (could mine both BTC and LTC) on: March 08, 2014, 05:06:16 PM
I like the new offering for your DualMiner 2 ASIC but can you tell me when you intend to create a mining app to run this ASIC on my Mac?

Also when I see a new revision no in the name,I usually expect higher performance or reduced energy use if hashrate is the same.Is it even possible to increase the scrypt hashrate of the DualMiner or would running off a USB port prove too difficult (as there's not much of a power envelope)?

I'm just curious to know.Thanks Smiley

I believe these questions have already been answered: someone has compiled a version for Mac from git which should work on both sticks. This can be found with search. Regarding running more gc3355's per USB slot:

Is it possible to put 2 chips on 1 usb?

140KH/s @ 3 watts?

Making a 2-chip USB miner is not difficult at all, but the tricky part is how do you provide the power required by this miner? Our DM miners was designed using BUS power scheme, which means the miner is powered from USB2.0 bus (or USB2.0 cable). Now, the USB2.0 specification only provides up to 2.5W (or 500ma current at 5V) power to one USB device, so that will put 2-chip USB miner out of the power supply range of USB2.0 bus.
This was found on the thread one page back..
9  Bitcoin / Hardware / Re: [ANN] Introduction to DualMiner USB (could mine both BTC and LTC) on: March 06, 2014, 08:07:19 AM
Hello,

I am new on this forum and have a problem with dualminer with PI.

When I connect the dualminer, then this will appear in the list with ls /dev/ttyUSB*, but cgminer does not find USB hardware.
After exiting cgminer also the dual miner has disappeared from the list.

The hub and dualminer work under Windows without problems.

Has an idea where the problem is?

Thanks.

Hi, epcoin

   Did you use sudo to get required privilege for running cgminer? Would you please take a photo of your screen and post it here or forum.dualminer.com? Our engineer will track your issue closely.

   Thanks.

-----------------
dmsp
DualMiner Support

Hi, dmsp

here are the screen printing

https://drive.google.com/file/d/0B743ny4TD6NvbVdrd29oRTJXVlE/edit?usp=sharing

After the end cgminer no more /dev/ttyUSB* are available

You need more informations?

Thanks for help.

It seems problem related to usb bus power or usb driver from -D information. Please confirm the DIP switched to L mode and check your PM. We will help you to find the difference between your rig and CruzCoins'.

-----------------
dmsp
DualMiner Support

The DIP is switched to L and I use TeckNet HU10 10 Port USB 3.0 Hub. This hub looks exactly like orico p10-u2.
When I connect this HUB and dualminer to a Windows PC and run DualMiner (download from dualminer.com) is't run without problems.

Your problem most likely is that raspberry pi notoriously does not work well with usb 3.0 hubs. See this link for more information about compatible hubs with Pis: http://elinux.org/RPi_Powered_USB_Hubs I recommend using nothing above usb 2.0 when trying to mine with Raspberry Pi for now. Also please be aware of this from the above link:
Quote
..if the HUB tries to feed the Raspberry Pi through their interconnect cable, due to the 100 mA limiting fuse in the Raspberry Pi, the Raspberry Pi will be partially powered which may cause problems (unwanted writes to the SD card).
10  Bitcoin / Hardware / Re: [ANN] Introduction to DualMiner USB (could mine both BTC and LTC) on: March 06, 2014, 08:02:51 AM
Hello,

I am new on this forum and have a problem with dualminer with PI.

When I connect the dualminer, then this will appear in the list with ls /dev/ttyUSB*, but cgminer does not find USB hardware.
After exiting cgminer also the dual miner has disappeared from the list.

The hub and dualminer work under Windows without problems.

Has an idea where the problem is?

Thanks.
What is the exact hub you are using? Did you follow my guide here roughly for your software install?
11  Bitcoin / Hardware / Re: [ANN] Introduction to DualMiner USB (could mine both BTC and LTC) on: March 04, 2014, 06:50:11 PM
Can anyone with a similar rig comment on stability? How often do you need physical access to your rig, and why?

Software updates will bring more stability. Stay away from windows. I currently have 99 DMs running on a Pi for over 72 hours without any failures. I was having issues for a while where a DM or two would go down and I would have to have physical access to the hubs to fix the issue. After running only 9 DMs per orico p10-u2 and some new software (still testing, should be committed to git soon) I haven't had any fail. My only downtimes have been me moving pools. Once everything is configured properly you shouldn't need physical access often.
12  Bitcoin / Hardware / Re: [ANN] Introduction to DualMiner USB (could mine both BTC and LTC) on: March 01, 2014, 08:15:20 PM
Here are the results my pool is reporting after running 99 DMs on Raspberry Pi for a few days: https://i.imgur.com/CEPbINT.jpg
13  Bitcoin / Hardware / Re: [ANN] Introduction to DualMiner USB (could mine both BTC and LTC) on: February 28, 2014, 03:41:25 AM
Last question, I swear.  Does anyone else that is running the dualminer-cgminer on linux have a problem when switching to a different pool, and when doing so lose a couple usb miners that will not connect.  For example I am running 16 dualminers, when I switch from pool A close cgminer, load pool B .sh file now only 12 of the dualminers show up.  So I have to unplug all of them from the hubs, run dmesg then plug them all back in, run dmesg now connect again and all 16 show up and start mining.  But when I decide to switch to another pool, not all 16 show up and I have to repeat the above step to get the all online again?
How are you closing your previous pool connection? Pressing 'Q' or just closing the terminal/ctrl+c? I have noticed this but usually when improperly stopping cgminer. When this occurs I just power cycle the hubs/reboot the machine. You could try to make a script that reboots in between switching pools if you want it automated.

Which is better?  I use ctrl+c, thank you for the reply too and all the help.  I will try using Q and report back if that helped.
I recommend 'Q' to safely end the cgminer process before starting a new one. This should prevent DMs from not wanting to restart with another session. You can always run
Code:
ls /dev/ttyUSB*
to make sure that all of your DMs are connected before starting cgminer. Note that for each DM you will have a pair of ttyUSB's. For example with 2 DMs, ls /dev/ttyUSB* would look like /dev/ttyUSB0 /dev/ttyUSB1 /dev/ttyUSB2 /dev/ttyUSB3. So, if you have 10 DMs you should have /dev/ttyUSB0 to /dev/ttyUSB19 listed. Not shutting down cgminer properly can cause DMs to not show up in /dev/ttyUSB*, and therefore not register with cgminer when it is restarted.

your command to show if they are connected is off.
Code:
ls /dev/*USB*
that is the correct one.
They are both producing the same outputs for me on raspbian and ubuntu. Would there be any instance of the DMs not being assigned to a ttyUSB* where *USB* is necessary? Just curious if it's possible for them to register otherwise. If so, I will change my post to make it more accurate.
14  Bitcoin / Hardware / Re: [ANN] Introduction to DualMiner USB (could mine both BTC and LTC) on: February 28, 2014, 01:00:22 AM
Last question, I swear.  Does anyone else that is running the dualminer-cgminer on linux have a problem when switching to a different pool, and when doing so lose a couple usb miners that will not connect.  For example I am running 16 dualminers, when I switch from pool A close cgminer, load pool B .sh file now only 12 of the dualminers show up.  So I have to unplug all of them from the hubs, run dmesg then plug them all back in, run dmesg now connect again and all 16 show up and start mining.  But when I decide to switch to another pool, not all 16 show up and I have to repeat the above step to get the all online again?
How are you closing your previous pool connection? Pressing 'Q' or just closing the terminal/ctrl+c? I have noticed this but usually when improperly stopping cgminer. When this occurs I just power cycle the hubs/reboot the machine. You could try to make a script that reboots in between switching pools if you want it automated.

Which is better?  I use ctrl+c, thank you for the reply too and all the help.  I will try using Q and report back if that helped.
I recommend 'Q' to safely end the cgminer process before starting a new one. This should prevent DMs from not wanting to restart with another session. You can always run
Code:
ls /dev/ttyUSB*
to make sure that all of your DMs are connected before starting cgminer. Note that for each DM you will have a pair of ttyUSB's. For example with 2 DMs, ls /dev/ttyUSB* would look like /dev/ttyUSB0 /dev/ttyUSB1 /dev/ttyUSB2 /dev/ttyUSB3. So, if you have 10 DMs you should have /dev/ttyUSB0 to /dev/ttyUSB19 listed. Not shutting down cgminer properly can cause DMs to not show up in /dev/ttyUSB*, and therefore not register with cgminer when it is restarted.
15  Bitcoin / Hardware / Re: [ANN] Introduction to DualMiner USB (could mine both BTC and LTC) on: February 28, 2014, 12:34:52 AM
Last question, I swear.  Does anyone else that is running the dualminer-cgminer on linux have a problem when switching to a different pool, and when doing so lose a couple usb miners that will not connect.  For example I am running 16 dualminers, when I switch from pool A close cgminer, load pool B .sh file now only 12 of the dualminers show up.  So I have to unplug all of them from the hubs, run dmesg then plug them all back in, run dmesg now connect again and all 16 show up and start mining.  But when I decide to switch to another pool, not all 16 show up and I have to repeat the above step to get the all online again?
How are you closing your previous pool connection? Pressing 'Q' or just closing the terminal/ctrl+c? I have noticed this but usually when improperly stopping cgminer. When this occurs I just power cycle the hubs/reboot the machine. You could try to make a script that reboots in between switching pools if you want it automated.
16  Bitcoin / Hardware / Re: [ANN] Introduction to DualMiner USB (could mine both BTC and LTC) on: February 27, 2014, 09:33:08 AM
CruzCoins after step 9 do you need to leave the  pc on with the vnc//SSH running? The whole point for me to setup this is to not have th mega WATTS pc on 24/7. Hope you don't need it on Tongue
Good question. I updated the guide to reflect these concerns.
To answer your question: no you do not need to keep your pc on.
17  Bitcoin / Hardware / Re: [ANN] Introduction to DualMiner USB (could mine both BTC and LTC) on: February 27, 2014, 02:46:48 AM
Can someone please post a rpi image for everyone?  I will offer a .025btc bounty.
Hi, I have an rpi image created for you that is already configured and will happily collect bounty. However, I recommend that people make the build themselves following the guide. If I create an image for you and you run it, you have no way of know that I did nothing malicious and hid it in the image. If you build it yourself you can sha1sum your original image and get packages for yourself. Again, I'll happily collect but I wouldn't run unknown custom pre-built images on your money printing device ;p
18  Bitcoin / Hardware / Re: [ANN] Introduction to DualMiner USB (could mine both BTC and LTC) on: February 26, 2014, 05:36:22 AM
in step 4, how I install tightvncserver on raspberry pi ? Copy it to usb or sd....if you can make youtube video...thanks   
To install run the following commands from your SSH session:
    >sudo aptitude install tightvncserver

This was taken from the guide. Just run the command.

CruzCoins: Does this work with the 49 port hub?
I do not have a 49 port hub to test with.
19  Bitcoin / Hardware / Re: [ANN] Introduction to DualMiner USB (could mine both BTC and LTC) on: February 26, 2014, 04:03:01 AM
With 99 DM's IMHO I would invest in some usb fans for that 10th slot to be safer. Nice rig setup it's clear you have trust in the coins future Tongue
Everything stays cool to the touch with the current setup. Thanks.
20  Bitcoin / Hardware / Re: [ANN] Introduction to DualMiner USB (could mine both BTC and LTC) on: February 26, 2014, 02:47:50 AM
This guide (v0.3) is using Raspberry Pi Model B and 2014-01-07-wheezy-raspbian flavor of Linux. If you already have your Pi running how you want, your may skip to step 5 for information specific to the dualminer cgminer build.

1. Begin with fresh install of 2014-01-07-wheezy-raspbian. Instructions here: http://elinux.org/RPi_Easy_SD_Card_Setup

2. Insert SD card into Pi, insert ethernet cable connected to your network, and insert power supply cable to boot up your Pi. If you only see a red light and no green flashing you probably messed up somewhere installing Raspbian to your SD card. Try it again.

3. SSH is enabled by default, so SSH into the Pi.
   a. To SSH first you need the local IP of your Pi device. The easiest way for most is to go to your router's config page (usually 192.168.1.1 or 192.168.1.2 with default login usually admin/admin- just google your specific router to find this info).
      Look for devices connected to your home network, locate device called 'raspberrypi' and note the IP address it had. Example: https://i.imgur.com/tnQkxcw.jpg
   b. Once you have local ip, use PuTTY (http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html?) if running windows or your kernel if Linux to SSH to the IP belonging to your Pi.
      Agree to the alert that will popup. Login with default credentials: username= pi password= raspberry
   c.Change default login info for security if you wish. You can lookup these details yourself or I may add later if there is need.
   d.Run the following commands after you have successfully logged in:
      
Code:
      sudo aptitude update
      sudo aptitude upgrade
      sudo reboot
  e.If you wish run the following command to expand filesystem, change language or hostname etc.
    
Code:
sudo raspi-config 

4. Originally in the guide I use tightvnc but I am going with another solution to free up CPU resources. We are going to disable X at startup (no GUI) and we are going to set SSH up to continue the process after we terminate the SSH session. To disable x ui run the following command:
Code:
sudo raspi-config
Then select choose boot option like in the picture I provide and make sure graphical desktop is not enabled.
https://i.imgur.com/x1rsDkS.jpg
https://i.imgur.com/J3692nT.jpg

Now we are ready to get a program to allow us to continue the cgminer process after ending the SSH session (thanks to demonmaestro for this advice). Run:
Code:
sudo apt-get install screen

5.Install dependencies for cgminer:
  
Code:
sudo aptitude install git autoconf libtool libcurl4-openssl-dev libncurses5-dev pkg-config yasm make libusb-1.0-0-dev libudev-dev 
 #all of these may not be completely necessary but it's what I used and it works

6.Grab dualminer cgminer code from git:
Code:
  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  --prefix=/home/pi/cgminer  
  #replace 'pi' with your username if step 3c taken.
Code:
  make && make install 

7.Now your Pi is configured. It is time to plug in hardware and make sure it is done in the proper cycle. Also I highly recommend that before you attempt connecting large arrays you test your units, hubs, power supplies etc individually to eliminate problems.
If you are sure your hardware is all good plug in your hubs like in the diagram or however yours array. Remember to make sure the DMs are getting enough power from your hubs (check power supply of hubs to calculate if they can provide for your miners- there are many threads on this).
https://i.imgur.com/np9DJGO.jpg
Power hubs on following the diagram. You will not have to do this every time you reboot, but it is still best to follow the cycle to eliminate problems.
Note: while the orico p10-u2 hubs should technically support 10 DMs per hub, I have only been able to find stability with 9 DMs per hub.

8.Login to a new SSH session with your user. Run
Code:
sudo screen -R myminer

9.Run the following commands after creating a 'screen' to run cgminer in:  
Code:
cd /home/pi/cgminer   
     #where pi is your username from step 2c.
 
Code:
sudo ./cgminer --scrypt -o stratum+tcp://yourfavoritepool.com:3333 -u yourusername -p x 
     #replace 'yourfavoritepool.com:3333' and 'yourusername' with your pool/worker information

This should get you mining. Now you can press Ctrl+A then Ctrl+D to close your screen and then you may end you SSH session to continue mining after you power off your computer. To reopen your cgminer process, simply run:
Code:
sudo screen -R myminer
Please let me know if I have left out anything crucial. I have been running this setup for over a week with 99 DMs.
https://i.imgur.com/7QJS8yA.jpg
https://i.imgur.com/CEPbINT.jpg

-CruzCoins

If this was helpful, please consider donating to the Litecoin Core Development Fund 2014: LcUP7ZU3Xpk1BUR3qut3dTjC3aK5JoZMYx
Pages: [1] 2 3 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!