Bitcoin Forum
February 09, 2026, 11:35:17 PM *
News: Community awards 2025
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 2 3 4 5 6 7 [8]
141  Bitcoin / Mining support / Re: First mining setup, two major issues. Assistance please on: September 17, 2013, 08:12:06 PM
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. Smiley
   
Thanks
142  Bitcoin / Mining software (miners) / Re: Linux mining distro for the Raspberry PI - MinePeon on: September 17, 2013, 04:08:28 PM
its been ok since i powered it with the ubec.

So my cairnsmore fgpa's are plugged in straight out of the box, but dont seem to be detected.
I will confirm they have a bitstream on them but do i need to do anything else to detect them
lsusb >
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp. LAN9500 Ethernet 10/100 Adapter / SMSC9512/9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 004: ID 050d:0307 Belkin Components USB 2.0 - 7 ports Hub [FSU307]
Bus 001 Device 005: ID 0403:8350 Future Technology Devices International, Ltd
Bus 001 Device 006: ID 0403:8350 Future Technology Devices International, Ltd
Bus 001 Device 007: ID 0403:8350 Future Technology Devices International, Ltd
Bus 001 Device 008: ID 0403:8350 Future Technology Devices International, Ltd
Bus 001 Device 009: ID 0403:8350 Future Technology Devices International, Ltd
143  Bitcoin / Mining software (miners) / Re: Akbash 1.0.11: Open Source cgminer watchdog (H/W monitoring, emails, HTTP) on: September 17, 2013, 03:04:54 PM
I'm interested in using akbash to monitor cgminer while mining litecoins; it looks like a great program. However, I get the following every time I use it:

04/11/13 18:03:12 0x1558 INF main(): checking miner status...
04/11/13 18:03:12 0x1558 ERR net_recvBytes(): WSARecv failed with error: 10053
04/11/13 18:03:12 0x1558 ERR sendCommand(): net_recvBytes() failed: -11
04/11/13 18:03:12 0x1558 ERR net_recvBytes(): WSARecv failed with error: 10053
04/11/13 18:03:12 0x1558 ERR sendCommand(): net_recvBytes() failed: -11
04/11/13 18:03:12 0x1558 ERR net_recvBytes(): WSARecv failed with error: 10053
04/11/13 18:03:12 0x1558 ERR sendCommand(): net_recvBytes() failed: -11
04/11/13 18:03:12 0x1558 SVR main(): unable to retrieve number of devices (GPU/PGA), waiting 30 seconds for

Akbash starts properly, detects that cgminer isn't running, properly starts cgminer up, but then this happens - looks like it's unable to properly communicate with cgminer. Akbash then kills cgminer, starts up a new instance, and the whole thing repeats.

I have the following in my cgminer startup script:

--api-listen --api-allow -W:127.0.0.1 --api-network

Anyone have any ideas what might be causing the problem? Is it because I'm using the --scrypt option to mine litecoins? I know this was intended as a monitor for bitcoin mining, but the cgminer output is pretty much the same...

Thanks!
144  Bitcoin / Mining support / Re: Erupter Blade not submitting work at the expected rate on: September 16, 2013, 03:52:46 PM
Quote from: pidge on September 15, 2013, 01:30:38 PM
I have two BE Blades running, but at around 2013-09-16 08:30 UTC they stopped regularly completing work - the would ask for work, but not submitt many completed shares

I've done the following, with no change to the behaviour:
- Restarting the blades (from web page and power cycle)
- Restarted mining_proxy
- Factory reset of a blade and reconfigured
- Ran with just one blade (to try to eliminate power issues)
- Swapped in another new blade.

Voltage from the PSU is still good (12.4V), but I've got no means of checking for excess noise on the power.  The PSU is a re-purposed HP Proliant G4 hot-swap PSU (12V, 47A).

I'm down to either the PSU has gone faulty, or there's something odd with the work being supplied. I might have a look at the output on the debug port, which will be interesting as I've only got a logic analyzer, not a USB to serial TTL 3.3V to hand.

Any ideas?




Observations:
- The "chips" status is all O's, no X's
- The blades request 8 shares to work on at a time, and may submit a completed share every now and then.
- Example mining_proxy output below, normally the screen just scrolls and scrolls past.

Code:
2013-09-16 00:20:31,878 INFO proxy getwork_listener._on_authorized # Worker '<user>' asks for new work
2013-09-16 00:20:31,953 INFO proxy jobs.submit # Submitting 25251d53
2013-09-16 00:20:31,969 INFO proxy getwork_listener._on_authorized # Worker '<user>' asks for new work
2013-09-16 00:20:32,019 INFO proxy getwork_listener._on_authorized # Worker '<user>' asks for new work
2013-09-16 00:20:32,036 INFO proxy getwork_listener._on_authorized # Worker '<user>' asks for new work
2013-09-16 00:20:32,112 INFO proxy getwork_listener._on_authorized # Worker '<user>' asks for new work
2013-09-16 00:20:32,135 INFO proxy getwork_listener._on_authorized # Worker '<user>' asks for new work
2013-09-16 00:20:32,174 INFO proxy getwork_listener._on_authorized # Worker '<user>' asks for new work
2013-09-16 00:20:32,190 WARNING proxy getwork_listener._on_submit # [230ms] Share from '<user>' accepted, diff 1
2013-09-16 00:20:32,288 INFO proxy getwork_listener._on_authorized # Worker '<user>' asks for new work
2013-09-16 00:20:32,303 INFO proxy getwork_listener._on_authorized # Worker '<user>' asks for new work
2013-09-16 00:20:32,319 INFO proxy getwork_listener._on_authorized # Worker '<user>' asks for new work
2013-09-16 00:20:32,394 INFO proxy getwork_listener._on_authorized # Worker '<user>' asks for new work
2013-09-16 00:20:32,418 INFO proxy getwork_listener._on_authorized # Worker '<user>' asks for new work
2013-09-16 00:20:32,437 INFO proxy getwork_listener._on_authorized # Worker '<user>' asks for new work
2013-09-16 00:20:32,513 INFO proxy getwork_listener._on_authorized # Worker '<user>' asks for new work
2013-09-16 00:20:32,536 INFO proxy getwork_listener._on_authorized # Worker '<user>' asks for new work
2013-09-16 00:20:32,624 INFO proxy getwork_listener._on_authorized # Worker '<user>' asks for new work
2013-09-16 00:20:32,755 INFO proxy jobs.submit # Submitting f226d12f
2013-09-16 00:20:32,792 INFO proxy jobs.submit # Submitting def7eb60
2013-09-16 00:20:32,806 INFO proxy jobs.submit # Submitting 837ac763
2013-09-16 00:20:32,816 INFO proxy jobs.submit # Submitting 9db12769
2013-09-16 00:20:32,990 WARNING proxy getwork_listener._on_submit # [227ms] Share from '<user>' accepted, diff 1
2013-09-16 00:20:33,414 WARNING proxy getwork_listener._on_submit # [615ms] Share from '<user>' accepted, diff 1
2013-09-16 00:20:33,421 WARNING proxy getwork_listener._on_submit # [606ms] Share from '<user>' accepted, diff 1
2013-09-16 00:20:33,433 WARNING proxy getwork_listener._on_submit # [609ms] Share from '<user>' accepted, diff 1
2013-09-16 00:20:48,844 INFO proxy client_service.handle_event # New job 22520 for prevhash b9303f27, clean_jobs=False
2013-09-16 00:21:18,857 INFO proxy client_service.handle_event # New job 22528 for prevhash b9303f27, clean_jobs=False
2013-09-16 00:21:48,489 INFO proxy getwork_listener._on_authorized # Worker 'pjnield_5' asks for new work
2013-09-16 00:21:48,558 INFO proxy getwork_listener._on_authorized # Worker 'pjnield_5' asks for new work
2013-09-16 00:21:49,503 INFO proxy client_service.handle_event # New job 22532 for prevhash b9303f27, clean_jobs=False
2013-09-16 00:22:18,858 INFO proxy client_service.handle_event # New job 22540 for prevhash b9303f27, clean_jobs=False
2013-09-16 00:22:48,861 INFO proxy client_service.handle_event # New job 22556 for prevhash b9303f27, clean_jobs=False

Seems the problem may be in the devices as btcguild is usually on par with things like this.

They have a warranty with free shipping if the devices is in fact flawed.
145  Other / Beginners & Help / Re: Hey there on: June 22, 2013, 01:12:48 AM
Hey. I am sorry it here that you lost some coins. Mind telling us how you think that happened? You should try cold storage for your bitcoins, its much safer.
Pages: « 1 2 3 4 5 6 7 [8]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!