|
203
|
Bitcoin / Mining software (miners) / Re: Linux mining distro for the Raspberry PI - MinePeon
|
on: September 23, 2013, 07:08:01 PM
|
At first I thought the same, however my bfgminer.service has it in there with both // and works fine.
Not double slashes - that does work fine. He was pointing out that bfgminer is listed twice in the path: ExecStart=/usr/bin/screen -dmS bfgminer /opt/minepeon/bin//bfgminer/bfgminer -S erupter:all -c /opt/minepeon/etc/miner.conf |
|
|
|
|
205
|
Bitcoin / Mining support / Re: First mining setup, two major issues. Assistance please
|
on: September 17, 2013, 11:15:43 AM
|
I've mentioned this a couple of times on different threads. The core reason is that the RPi doesn't have a real-time clock. So, every time you power up the RPi, it resets its date to Jan. 1, 1970. After a few minutes of running, there's a background process in Minepeon that updates the date/time to the current date and time. However, in that interval, cgminer has kicked off. So cgminer thinks that it started on Jan. 1, 1970, and has been running continuously for over 43 years. It's also the reason your average hash rate drops to near zero - it's not your hash rate divided by the runtime over the last few minutes/hours, it's that hash rate over the last 43 years. So yeah, it will drop.  |
|
|
|
|
206
|
Bitcoin / Mining software (miners) / Re: Linux mining distro for the Raspberry PI - MinePeon
|
on: September 14, 2013, 10:39:59 AM
|
nice explanation here we go: OK, now I'm confused. On the one hand, you've managed to set up all your erupters such that they only sit on one logical hub per physical hub. (Looking at the D-Link, it seems that plugs 1, 3, 5, and 7 form one logical hub, and plugs 2, 4, and 6 are on the other logical hub.) On the other hand, you have six logical hubs showing up -- something I haven't been able to accomplish. Like you, I have the Wifi plugged directly into one of the Pi's ports, and my hubs are in a star config off the other port. Here's the same output from one of my Pis: minepeon@minepeon ~ $ lsusb | grep hub
Bus 001 Device 014: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 007: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 010: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 006: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 005: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
minepeon@minepeon ~ $ lsusb -t
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/3p, 480M
|__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=smsc95xx, 480M
|__ Port 2: Dev 4, If 0, Class=Vendor Specific Class, Driver=rtl8192cu, 480M
|__ Port 3: Dev 5, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 1: Dev 6, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 1: Dev 10, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 2: Dev 22, If 0, Class=Vendor Specific Class, Driver=usbfs, 12M
|__ Port 3: Dev 23, If 0, Class=Vendor Specific Class, Driver=usbfs, 12M
|__ Port 4: Dev 24, If 0, Class=Vendor Specific Class, Driver=usbfs, 12M
|__ Port 2: Dev 11, If 0, Class=Vendor Specific Class, Driver=usbfs, 12M
|__ Port 3: Dev 12, If 0, Class=Vendor Specific Class, Driver=usbfs, 12M
|__ Port 4: Dev 13, If 0, Class=Vendor Specific Class, Driver=usbfs, 12M
|__ Port 2: Dev 7, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 1: Dev 14, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 2: Dev 25, If 0, Class=Vendor Specific Class, Driver=usbfs, 12M
|__ Port 3: Dev 26, If 0, Class=Vendor Specific Class, Driver=usbfs, 12M
|__ Port 4: Dev 27, If 0, Class=Vendor Specific Class, Driver=usbfs, 12M
|__ Port 2: Dev 15, If 0, Class=Vendor Specific Class, Driver=usbfs, 12M
|__ Port 3: Dev 16, If 0, Class=Vendor Specific Class, Driver=usbfs, 12M
|__ Port 4: Dev 17, If 0, Class=Vendor Specific Class, Driver=usbfs, 12M
|__ Port 3: Dev 8, If 0, Class=Vendor Specific Class, Driver=usbfs, 12M
|__ Port 4: Dev 9, If 0, Class=Vendor Specific Class, Driver=usbfs, 12M
No matter what I do, I can't get the Pi to recognize any additional hubs; in fact, I can't get it to recognize erupters plugged into logical hub 2 on my last physical hub. Anyone have any ideas? |
|
|
|
|
207
|
Bitcoin / Mining software (miners) / Re: Linux mining distro for the Raspberry PI - MinePeon
|
on: September 13, 2013, 09:33:11 PM
|
I know thats some list command, but as I am a Linux noob, what exactly do they do?
And yes, but you will have to wait until tomorrow morning, as I am in bed now *g*
lsusb lists all the USB items connected to your Pi. The command filters the output through grep, which searches for the word "hub". This gives me a count of how many logical hubs your Pi is seeing. The second command, with -t, asks the Pi to give a tree listing of the hubs. That shows how the logical hubs are connected to each other. The output includes every USB device connected, which might show that some logical hubs are in fact empty on your system. You can find out more about lsusb by using the man ("manual", as in instruction manual) command: man lsusb |
|
|
|
|
208
|
Bitcoin / Mining software (miners) / Re: Linux mining distro for the Raspberry PI - MinePeon
|
on: September 13, 2013, 08:59:50 PM
|
thats 4 hubs, 1 Belkin (without powersupply because I could not find it) with 3 D-Link 7 Port Hubs with 3 USB Miners each. The Belkin is plugged into the Pi, the 2nd port on the Pi is used by the wifi dongle
Interesting. Could you do me a favor, please, and run these commands on your Pi? I'd love to see the output. lsusb | grep hub lsusb -t Maybe that will give me some clues as to why both my Pi's only see five hubs each. |
|
|
|
|
209
|
Bitcoin / Mining software (miners) / Re: Linux mining distro for the Raspberry PI - MinePeon
|
on: September 13, 2013, 08:42:26 PM
|
|
I have the exact same problem. The Pi has a limitation that it can only see five logical hubs, not including the root hub on the Pi itself. The problem is, each D-Link physical hub is in fact two logical four-port hubs. The "second" four-port hub is plugged into one of the ports on the "first" hub, which exposes seven ports for you to use. If you plug three D-Link hubs into the Pi, it will see two logical hubs for each of the first two physical ones, but only one logical hub on the third physical one. Attaching additional hubs won't do anything; the Pi won't see them at all.
I don't know if the limitation is five hubs per USB port on the Pi, or five hubs total -- I can't test this. I use the second USB port on the Pi for Wifi access. Though in retrospect, I guess I could just plug the Wifi dongle into a hub port and see if I can connect additional hubs to the other USB port...
|
|
|
|
|
211
|
Bitcoin / Mining software (miners) / Re: CGMINER ASIC FPGA GPU overc monit fanspd RPC linux/win/osx/mip/r-pi 3.4.3
|
on: September 13, 2013, 04:25:06 PM
|
Win7 x64, just like the PCs.
I could see them being underpowered. But cgminer doesn't see them. It's not like it sees them and they don't work, it's like they aren't there.
M
I had the same issue. By any chance, is it a very recent PC, with a Z87 chipset? In my case, the conclusion was that my particular chipset or USB port wasn't supported by the libusb that cgminer uses. Windows was seeing the BE fine and loading the right drivers, but they still appeared invisible to cgminer. Ultimately I had to find a different platform to mine on. |
|
|
|
|
213
|
Bitcoin / Mining software (miners) / Re: Linux mining distro for the Raspberry PI - MinePeon
|
on: September 12, 2013, 11:06:36 AM
|
|
The drop in long-term average hash rate to near zero is specific to the Pi, and probably to MinePeon. At boot time, the Pi's date starts at Jan 1, 1970. After a few minutes, a background task updates it to the right time. But in the interim, cgminer has started. So to get the average, it calculates your total hashes divided by run time. Since the apparent run time is over 43 years, the average is near zero.
|
|
|
|
|
214
|
Bitcoin / Mining software (miners) / Re: Linux mining distro for the Raspberry PI - MinePeon
|
on: September 10, 2013, 09:23:26 PM
|
If you get an error when doing git pull, try this. It should fix it. Log in, then run these commands: sudo -i
find /opt/minepeon -user root | xargs chmod a+w
exit Type your password when prompted by sudo. Ignore the error message that gets spit out from the find command. Then do git pull as normal, and it works. |
|
|
|
|
215
|
Bitcoin / Hardware / Re: Liquid Synergy Designs Inc. -ASIC mining hardware
|
on: September 09, 2013, 09:30:43 PM
|
I'd be irritated if the only difference is that they produce less heat and use less energy, for example.
Less heat and Less energy could be substantial. Extends overclocking abilities if they produce less heat and makes them profitable for longer if they use less energy. I'm of two minds about that. The hacker in me loves the idea of tinkering and seeing how far we can push the hardware. Extra speed, whether from lower heat and overclocking, or from better internals, is always desired. On the other hand, the businessman in me doesn't care how payback is improved, so long as it *is* improved. What I meant by my comment was that, say, a 5% improvement in hash rate, whether from overclocking or from intrinsically better chips, is mostly useless. A 500% improvement would have us dancing with joy. Anything inbetween would have to be evaluated. Same for cost, heat, etc. |
|
|
|
|
216
|
Bitcoin / Hardware / Re: Liquid Synergy Designs Inc. -ASIC mining hardware
|
on: September 09, 2013, 08:37:07 PM
|
Also it's likely only the first 10,000 chips requested will be refunded (no partial batch refunds). Possibly the first 20,000 chips, but it doesn't seem like 1/3 want a refund.
At this point, I don't think I can reasonably ROI on my K16s. However, I haven't asked for a refund yet as I want to hear what Steamboat has to propose regarding the assembly costs. I'm hoping he's trying to swing some sort of deal with Yifu regarding the Gen2 chips so that we can either switch our order to Gen2 instead of Gen1, or salvage the materials and get some sort of cash for the mats/assembly. Having said that, this whole discussion is predicated on the assumption that the Gen2 chips are better than the Gen1s, by a substantial margin. I'd be irritated if the only difference is that they produce less heat and use less energy, for example. |
|
|
|
|
217
|
Bitcoin / Mining software (miners) / Re: Linux mining distro for the Raspberry PI - MinePeon
|
on: September 09, 2013, 05:20:54 PM
|
My install keeps getting stuck at
[ok] reached target graphical interface
Any ideas why it stops loading here?
Thanks in advance
It's not stuck, it's waiting for you to log in. Just type "minepeon" without the quotes, hit enter, then type your password. The reason this happens is that the login prompt appears earlier in the process, but background processes continue to run and print output to the screen. So, unless you're watching carefully, you don't realize it's waiting for you. This only happens when you're using a screen and keyboard; you don't see this problem if you SSH in. |
|
|
|
|
218
|
Bitcoin / Hardware / Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
|
on: September 07, 2013, 07:32:12 AM
|
Interesting, it's not showing up an AMU at all... nothing matches AMU 10c4:ea60
I checked the BE device properties in Device Manager, and I did see those bytes (10c4:ea60) in the various device setting strings. So Windows itself is identifying the device correctly and loading the right driver. If it helps you debug this further, the motherboard I'm using is a Gigabyte GA-Z87X-UD4H. Is there anything further I can do to help resolve this, or do we just have to wait for whoever is in charge of libusb development to add support for this motherboard/chipset/whatever the root cause is? Hmm there are some usb3 ports that are apparently not working with libusb, perhaps you have some. Try different ports or a hub or something to see if that's it? Unfortunately, I've tried with both the USB 2 and USB 3 ports on my PC, as well as a USB 2 hub plugged into both ports. No joy  I don't have a USB 3 hub to test with, but I doubt it matters at this point. I'm shifting my efforts towards mining with a Raspberry Pi, but that has its own issues - the Pi doesn't seem to recognize all the Erupters, and the whole Pi seems to freeze up after about five minutes. Still trying to figure out why and get a reproducible crash before I ask for help on that. Still, if I can get all 30+ Erupters mining successfully off an RPi, that would be the ideal scenario. |
|
|
|
|
220
|
Bitcoin / Hardware / Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
|
on: September 06, 2013, 10:34:50 PM
|
Interesting, it's not showing up an AMU at all... nothing matches AMU 10c4:ea60
I checked the BE device properties in Device Manager, and I did see those bytes (10c4:ea60) in the various device setting strings. So Windows itself is identifying the device correctly and loading the right driver. If it helps you debug this further, the motherboard I'm using is a Gigabyte GA-Z87X-UD4H. Is there anything further I can do to help resolve this, or do we just have to wait for whoever is in charge of libusb development to add support for this motherboard/chipset/whatever the root cause is? |
|
|
|
|
Show Posts
