Thanks for providing your results! My 3 units are still running without human intervention for 4 days. The script is just checking for zombies, then restarting cgminer or rebooting the R1 if necessarry, so it shouldn't increase the zombie rate. I'm thinking the script is just more efficient at catching them than we are  Also, you can check /tmp/cgminer-u3.log for historic data on hashrate and restarts. The log is cleared on reboot though. Reboots are tracked in /var/log/cgmine-u3-reboot.log |
|
|
|
I do not understand why these produce hardware that are useless.
you can never, ever find a block,
it takes maybe 1 year to get to 1 btc,
bhòòòòòò I will never understand this crap
1 BTC a year from an R1 would be pretty amazing. It's a wifi router/ wireless access point that can mine and also act as a controller for larger miners. The Compac and U3 are both geared towards beginners and those looking to lotto mine. One of the great things about free will is that no one can ever force you to buy something you don't want or don't understand.  |
|
|
|
CFW 0.94 has been uploaded for my customers.
The previous updates to cgminer-monitor were missing U3 zombies where the device was still showing as active through the API. I've reworked the function to compare "Last Valid Work" before and after a specific interval for all connected devices. This should catch and handle all zombies, and just in time for Halloween! The new monitor has kept my 3 U3s running without human intervention for the past 2 days.
bought my U3 through u and constant issues. Is there a way to get the update? Sure, check your PM |
|
|
|
I just picked up a couple of U3s. I'm having the same frustrations with zombie miners as others report on here. I'm running 2 U3s with Minera on an RPi. I'm using BFGminer 5.4.0 to mine which maybe is slightly more reliable than CGminer but I'm not entirely sure. I've tried different configurations, including putting the U3s on a powered USB hub but to no avail. The U3s are powered off the PCI-E connectors on an Antec 500W PSU, so they should have plenty of juice. I've read through some of the suggestions in this thread but none have helped. Does anybody have some new ideas or things that they think might help alleviate the zombie problem?  Using a non-bitmain PSU has lengthened the amount of time between zombies for me, but unfortunately there doesn't appear to be a way to stop them. However, I am now automatically handling zombies on the R1 with a monitor script that restarts cgminer/udev when necessary. This should be easy to port to the Rpi or any other linux based system. |
|
|
|
|
CFW 0.94 has been uploaded for my customers.
The previous updates to cgminer-monitor were missing U3 zombies where the device was still showing as active through the API. I've reworked the function to compare "Last Valid Work" before and after a specific interval for all connected devices. This should catch and handle all zombies, and just in time for Halloween! The new monitor has kept my 3 U3s running without human intervention for the past 2 days.
|
|
|
|
after following guide and everything says no devices detected.
Here's one that's worked for me in the past: Prime the pump.... Unplug and replug the usb cord a few times. Keep doing it until it gets recognized. |
|
|
|
I finally got a chance to hook multiple U3s up. I couldn't connect more than 3 units without a powered hub, but that's been the case with every controller I've ever used with U3s. Updated cgminer-monitor script is running and I'll let everyone know how well it handles zombies over the next few days.  |
|
|
|
tried going through computer wont even register as a device. Tried multiple usb cables and such.
May be a bad power supply... If you bought it from me, just send me a PM. |
|
|
|
downloaded that and still not working. I reset and it worked for an hour now its on but not hashing again.
The script runs every 3 minutes, so you could have a zombie for that length of time.Try running it manually and send me the output if it doesn't work. /usr/bin/cgminer-monitor |
|
|
|
Having issues with my U3 still. Having to reset R1 everytime I come home from work to get the U3 to start back up. The R1 is hashing away fine and wifi working great but the U3 keeps dying.
Im using the standard U3 settings. Any recommended settings to keep it running that has worked for others? (volts, etc..)
The R1 is great at recovering from zombies with a cgminer restart(via the init.d script) and in some instances it requires a reboot. I have never had to replug my U3 in when using the R1 as a controller. The problem is, the R1 has no script monitoring for U3 zombies and restarting cgminer. I've taken one step to resolve this issue and so far it's kept my U3 running for 2 days. Add the following to the end of your cgminer-monitor script(/usr/bin/cgminer-monitor), and let me know how it works out for you: numU3MinersInactive=`/usr/bin/cgminer-api devs localhost 4029 | grep "\[No Device\] => true" | wc -l`
if [ "$numU3MinersInactive" -gt "0" ]; then
echo "$numU3MinersInactive miners have gone inactive, restarting cgminer-u3"
/etc/init.d/cgminer-u3 stop
sleep 5
/etc/init.d/cgminer-u3 start
sleep 20
noASCMsgCount=`/usr/bin/cgminer-api devs localhost 4029 | grep "\[Msg\] => No ASCs" | wc -l`
if [ "$noASCMsgCount" -gt "0" ]; then
echo "No Miners Detected, trying one more cgminer restart"
/etc/init.d/cgminer-u3 stop
sleep 5
/etc/init.d/cgminer-u3 start
sleep 20
noASCMsgCount=`/usr/bin/cgminer-api devs localhost 4029 | grep "\[Msg\] => No ASCs" | wc -l`
if [ "$noASCMsgCount" -gt "0" ]; then
currentDate=`date`
echo "$currentDate - No Miners Detected after 2 restarts, rebooting" > /tmp/cgminer-u3_reboot.log
reboot
fi
fi
fi Brief description of what cgminer-monitor and this snippet are doing: - cgminer-monitor runs every 3 minutes via cron. Its main purpose was to keep the integrated R1 ASIC up and running. - The snippet uses cgminer-api to get a list of inactive miners under the cgminer-u3 instance. - If an inactive(zombie) miner is detected, cgminer is restarted. - If cgminer comes back up with no miners attached, it tries one more restart - After second restart, if no miners are attached, it reboots the R1. |
|
|
|
I've uploaded Custom Firmware 0.93 for my customers. 0.93 contains an update which should mitigate, if not completely resolve, the issue of U3 zombies on the R1 controller! If you've purchased through the website or group buy and don't have the download link, please contact me via PM.
Any chance we can get it if we didn't buy it from you ? Thanks I'll provide the updates to the community once I'm sold out. There are exceptions for those who have purchased from me in the past, just contact me via PM. |
|
|
|
|
I've uploaded Custom Firmware 0.93 for my customers. 0.93 contains an update which should mitigate, if not completely resolve, the issue of U3 zombies on the R1 controller! If you've purchased through the website or group buy and don't have the download link, please contact me via PM.
|
|
|
|
Somebody with an R1 should check to see if /usr/bin/cgminer-monitor is a real program, or just some kind of script. If it's a script, it might provide some useful guidance to folks with U3's on how to "work around" the zombie issue. While they might still go zombie, maybe the "hand holding" could be reduced.
i just checked this script and all it does for the cgminer-u3 is stop it if it cant reach the internet.. it wont do anything for zero hash or zombie condition.. it does stop and restart the internal chip if it doesnt send a share in x amount of time.. it woudlnt be hard to make a new script to do the same for the u3. You can use their cgminer-api binary for the u3 instance and retrieve stats with the following commands: cgminer-api stats localhost 4029
cgminer-api devs localhost 4029 The only issue is that you could be dealing with multiple devices, so the U3 check will need to be a little more complex. |
|
|
|
my U3 worked for a day now wont hash like the chip is dead. have reset and unplugged for a while but nothing. any ideas?
it is plugged into my R1 which is working fine.
Try a computer and see what it shows when you try to mine with it. That or possibly try restarting R1. I think it will be easier to make sure it's all working troubleshooting on computer then move to R1 after making sure it's working. It should work though it would be odd for it to die if your running at normal speeds Yeh, I just got in a state where restarting cgminer and udev wasn't enough to get the U3 back up, but a reboot of the system did. I'm working on an update to the firmware to automatically restart cgminer/udev and reboot if necessary. |
|
|
|
The Lepa is crap in my opinion. It would trip any time I tried to push over 100 watts to a single pcie cable. It did run 8 New rboxes just fine though. Thermaltake ran a few Neptune cubes for over a year. The Logisys PSUs are brand new and unused, so I can not attest to their usefulness, although they should handle a few U3s just fine. Buyer pays shipping or sends a label .4 BTC .9 BTC .05 BTC (15 available)  |
|
|
|
Anyone happen to notice it reset like three hours? Mine I have tried a few things to but seems like every 3 hours it resets, but starts back in like 30 second.
I'm thinking maybe try less U3's next I have 3 right now. So thinking about trying 1 today. Just wondered if anyone else has seen this.
Have not seen that, but have not run with U3's. Does it do it without a U3 attached? Mine stopped again after 25 Mins at 300MHz, so have upped the Core Voltage to 0.68V which gives 0 HW errors, has now run for 40 Mins, we will see? Rich I will test without and with just one. So far have been trying to use 3 as it does it very well. It seems to work pretty good. Just odd on the 3 hour reset. So going to do some more testing of different variables. I was able to confirm 3 hour reset stop's once down to one U3. With 3 U3's mine reset's every 3 hour's. Tried a lot of different hubs, and before finding this out. If someone else could please try 3 if they have it and see what happens. There's a cron job setup to run a binary called cgminer-monitor every 3 minutes. */3 * * * * /usr/bin/cgminer-monitor I'm not certain, but my guess is that the monitor application probably restarts cgminer if it detects a zombie. Perhaps it also reboots the R1 if cgminer restart doesn't work. I'm thinking that as you plug in more U3s you have a better chance of hitting a zombie.. |
|
|
|
For those of you running on Linux, it appears there may be an easy solution for restarting your U3 without unplugging the USB cable. With the antrouter, Bitmain's cgminer-u3 init.d script stops the udev daemon(linux device manager) when it stops cgminer, and then starts it back up in the cgminer start function, if it is not already running. This allows me to restart cgminer when a unit goes zombie, through the init.d script or UI, and not have to unplug the device. You should be able to port this command to another linux based system and monitor cgminer then restart cgminer/udevd when needed. On cgminer stop start-stop-daemon -K -n udevd -s TERM On cgminer start ps |grep -v grep|grep udevd > /dev/null
if [ $? -eq 0 ];then
echo detect hotpluging USB miners
else
/sbin/udevd --daemon
echo start detecting
fi |
|
|
|
I've got R1's in stock and available for purchase. Custom firmware is optional. R1 Custom Firmware available!I've delivered my first custom firmware release to existing customers, which can be loaded on new orders upon request. However, please note that loading custom firmware will void all warranties. Custom firmware includes: - Configuration for up to 4 pools with full Bitmain solo mining support. - R1 Frequency and Voltage modulation (Use at your own risk) - Detailed R1 stats page, including pool statistics    |
|
|
|
|
I've listed the R1 on ASICPuppy.net. Firmware mod is free and optional. You must select the option at checkout.
I've also updated RPis and Cubies with the latest Minera build (0.6.1) and builds of cgminer-gekko and ckpool, along with ckpool shell scripts for running as pool and proxy.
|
|
|
|
|
Show Posts
