So I got a kinda weird issue.
I started mining on my Raspberry Pi (O/S: Raspian) with 5 Block Eruptors on a DLink DUB-7 on August 19th using cgminer 3.3.4 and followed the included instructions on how to compile the libusb libraries myself. It worked great and it ran non-stop for a few weeks. The other day I decided to update cgminer to 3.4.2. After mining for about 20 minutes the Pi seemed to locked up. My SSH session died and I couldn't ping the Pi anymore. I figured it was just a fluke so I restarted the Pi but, again, after mining for about 20 minutes the Pi locks up.
I figured that this must have just been an issue with the newest version of cgminer so I went back to 3.3.4 with no luck. 3.3.4 now causes the Pi to lock up as well. I thought that maybe the Pi was overheating so I tried doing something else intensive; watching a 1080p movie over my LAN for 2hrs+ but it worked great and never locked up. I also tried mining just with 1 miner but the Pi still locked up.
Perhaps there is an issue with the newest packages for the Pi? How can I provide some more detailed info to see what is going on? Anything else I can try to resolve the issue?
If going back to the previous version doesn't resolve the issue, how can the new version be responsible? |
|
|
|
is it possible to connect a avalon to a laptop and mine using laptop cgminer or bfgminer?
Sure, I've been mining to mine from my PC since the router broke in mine. Almost a week of mining with cgminer 3.4.2: AVA 0: 21C/ 45C 2160R | 76.62G/82.88Gh/s | A:12151796 R:21075 HW:245816 WU:1157.9/m
Just open the top, pull the usb cable out and plug in a (printer type) usb cable from there to your PC. |
|
|
|
I want to mine on a gpu on the same pc in a different pool that my asics are on but I try --disable-Icarus it crashes is there another command??
That's cause there is no such command. Try --usb :0 |
|
|
|
|
cgminer has no limit on the number of devices it is happy to work with. However the display was designed from the GPU era where no more than 7 devices would be on the screen and was never designed with tens of devices in mind, so it tries to resize and crashes when it's too big. That's why the --compact mode was invented and would work, and why the API for remote monitoring of what cgminer is doing is there, to allow you to deal with any number of devices.
|
|
|
|
|
The 14+ device issue on windows is due to not resizing the command prompt.
|
|
|
|
Did Kano already saw this?  Maybe he will stop bashing USB erupters now You're kidding right? Sigh... |
|
|
|
yeah when to upgrade is always a tough call.
Strictly speaking, I move to the latest Ubuntu 3 months after it is released, and 2 releases are usually binary compatible, which means they get a year of binary compatibility before I move on. 13.04 came out in April and 13.10 is due out in a month (as per the .04 .10 nomenclature). |
|
|
|
is there a reason that you moved from ubuntu 12.04 to 13.04? it seems like every time i try and do something simple, like upgrade cgminer, i have to jump through hoops. I'm running cgminer 3.3.1. i'm having trouble adding a new Hub and more ASICminer erupters. i've got about 34 running, one in the new hub works but any more gets errors and not recognised. at one point i had 3 working in the new hub, but repowering it dropped me down to one. I figured if i asked for help you would just tell me to use the latest cgminer. so i downloaded your prebuilt one. I noticed the 13.04 but figured it was a typo. So now i have to upgrade my Ubuntu version or rebuild the package for 12.04? If i try and rebuild it am i going to run into another "gotcha". I was so happy with 3.3.1, i just downloaded it and it worked.  I've been building with 13.04 for ages. It just so happens that previous builds worked on 12.04->13.04 simply because all the libraries matched and now do not that I added the latest version of libusb. When exactly should I upgrade to a newer operating system? Well that's the nature of heavy development. If you find a version that works for you and your hardware, stick with it, but mining is a very fluid environment that is still in massive flux and development where the hardware, protocol and expectations continue to change. If you're on linux, you'll always be much better off building it for yourself, and I only reluctantly offer binaries - it is actually not hard to build it yourself. Windows is a totally different world where building the binary is hard work, so I try to make one binary work on as many different versions as possible. People newer to the linux world use their windows experience but that's not the best way to use linux. |
|
|
|
SOLVED! (sort of, eventually) Conclusion: Nvidia should stick to GFX chipsets. Xubuntu 13.04 performed poorly compared to 12.04 (I reinstalled 12.04) I need to learn more  Thanks for investigating. Having coded parts of kernels that report CPU usage, I should point out that the CPU usage is not as clear as you may think, so while it appears that 13.04 is worse than 12.04 (37 vs 33% you said), it may be a measuring artefact difference, whereas 12% vs 33% is more likely to be significant. |
|
|
|
Latest git fail to compile on windows: cgminer-util.o:util.c:(.text+0xd87): undefined reference to `inet_network'
Noted and fixed, thanks. |
|
|
|
I've noticed that there are times when my block erupter's light flashes, but there's no activity in CGMiner. Shouldn't every flash be accompanied by either accepted shares, rejected shares, or hardware errors being incremented?
Not if you're mining at a diff greater than 1. The device returns diff1 shares. |
|
|
|
What configure option do you have to enable for CGMiner to support mining with Block Erupters? I noticed there's no "--enable-asicminer" option...
They use the icarus driver. |
|
|
|
Does anyone know a good way to cross compile libudev, so I could keep on cross compiling cgminer for ARM? I had no trouble compiling libncurses and libusb previously, but it looks like libudev has been integrated to the massive systemd project. Obviously I don't need to compile the whole systemd, but I just can't figure out how to compile libudev only.
You can't just install libudev development library? I tried that first, but the configure script doesn't pick it up, presumably because I need to have a version compiled for arm. I'm no cross compilation expert, but that's what worked for me with libusb and libncurses. I downloaded those libraries, cross compiled them for arm and installed them to a specific directory. After pointing the configure script to search for libs and headers from that directory, the dependencies were detected. If you have managed to cross compile cgminer without having to cross compile libudev too, I'm obviously doing something wrong here. I only cross compile for windows, and windows does not use udev. The latest libusb requires udev on linux unfortunately. |
|
|
|
I'd try Arch, I heard it has decent support for rPi and it's a pretty stable distro. Also I think the proper command is "./cgminer -o stratum.bitcoin.cz:3333 -u xxxxxx - p xxxxxx" while in the cgminer folder.
I tried that from the cgminer directory and got the same error. The exact error is "Pool 0 JSON auth failed: (null)" As a work around I guess I might try setting up miner.conf with all of my pool information in there. Maybe that would take care of things. I should probably add that just using cgminer says I don't have permission to access the devices. I've been starting it with sudo cgminer. Should I continue to do it this way or change some kind of user permissions? Thanks! Chad Read ASIC-README. You have not installed the udev rules that give regular users access to the devices. |
|
|
|
Does anyone know a good way to cross compile libudev, so I could keep on cross compiling cgminer for ARM? I had no trouble compiling libncurses and libusb previously, but it looks like libudev has been integrated to the massive systemd project. Obviously I don't need to compile the whole systemd, but I just can't figure out how to compile libudev only.
You can't just install libudev development library? |
|
|
|
By the way, are you using a socks4 or 5 proxy?
Socks 4 currently. Ok, I've coded up socks4 support as well now. |
|
|
|
|
If you buy 1 bitcoin now and the value of bitcoin rises, you have made a profit. Not so if you pay with the usb miner and you never recoup the same amount. Doesn't make sense using that as an argument.
|
|
|
|
sudo apt-get install libudev1
This is my error output with that command: @-Ubuntu1:~/Desktop$ sudo apt-get install libudev1 [sudo] password for : Reading package lists... Done Building dependency tree Reading state information... Done Package libudev1 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'libudev1' has no installation candidate I have tried to run this beforehand: sudo apt-get update No luck On another note, ckolivas, I wanted to thank you for the windows version of 3.4.2. I installed it onto my HP N40L Microserver and have a tonne of block erupters running without a hitch. I only had to install Windows 7, then that WinUSB driver utility which didn't take long at all. It detects and starts mining with the block erupters so quickly and without error. 3.4.0 used to crash every couple of days, but 3.4.2 doesn't seem to have that crash any more. Thanks so much! You're welcome. Actually you're on an older ubuntu. That build is for ubuntu13.04, so you'll either have to upgrade ubuntu or build it yourself. The latter option is likely going to be less work. |
|
|
|
install ..... libudev
hey mate Thanks for the advice But after installing it I still get the same error. Is there a specific version I need? Sorry, I am a linux noob. What command should I be using to install it? I used: sudo apt-get install libudev-dev It installed but cgminer still says: ./cgminer: error while loading shared libraries: libudev.so.1: cannot open shared object file: No such file or directory sudo apt-get install libudev1 |
|
|
|
|
Show Posts
