Bitcoin Forum
October 15, 2024, 04:06:45 AM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 [327] 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 ... 573 »
6521  Bitcoin / Mining software (miners) / Re: CGMINER ASIC FPGA miner monitoring RPC linux/win/osx/mips/arm/r-pi 3.12.1 on: February 07, 2014, 08:41:23 PM
WARNING:  There may be a problem with cgminer 3.12.1 that makes it stop retrieving work. I will investigate further and possibly release a fix in the next 24 hours. In the meantime I suggest users do not upgrade.

Sigh.

The Antminer U1 support isn't very stable either, mine all crapped out after an hour or so, I ended up with 50-odd as they dropped out and came back on.  I have 10 of them on a Anker hub, running off a PC running Debian Wheezy.

ANU7: Comms error (werr=-9 something something)

Then it disables, and a few seconds later the miner reappears using Hotplug and gets a new number.  Then I get a load of ANUxx Re-estimate: blah blah spam.

Same hardware runs the U1 on bfg perfectly for weeks on end.

I'll update the error messages when they happen again, I'm on an intermittent SSH connection through my phone from work at the moment.
Hmm I can try reinstating the attempted reset but I'm not sure it's going to fix that... How much were you overclocking them?
6522  Bitcoin / Mining software (miners) / Re: CGMINER ASIC FPGA miner monitoring RPC linux/win/osx/mips/arm/r-pi 3.12.1 on: February 07, 2014, 02:08:57 PM
WARNING:  There may be a problem with cgminer 3.12.1 that makes it stop retrieving work. I will investigate further and possibly release a fix in the next 24 hours. In the meantime I suggest users do not upgrade.

Sigh.
6523  Bitcoin / Hardware / Re: HashFast BabyJet users thread on: February 07, 2014, 08:27:15 AM
This should also fix the windows reliability issues for those poor souls mining with their BlowJobs on windows.

Hey now.  I never thought I'd be the Windows Defender(tm), but in the interest of fairness, the hashrate graph from Eligius for my Blowjobs is hard solid as a rock.  Really.  Cranking along at about 430gh each with no problems to speak of for what, almost 10 days now?  I can't complain a single bit about that aspect of the BlowJob experience.
I'm pleased to hear that. There are two camps with the windows people: everything's hunky dory and everything's funky shit - and that group is more common with 3.12.0. I'm hoping to get more of the former with the latest release.
6524  Bitcoin / Mining support / Re: Best Share (CGMiner) vs Difficulty? on: February 07, 2014, 08:20:48 AM
Well, I don't understand exactly why, but the relation appears to be 65536. So if the network difficulty is 0.063387, that times 65536 is 4154, so a share has to be greater than 4154 to be a block. Or, from a freshly restarted cgminer, the "best share" has to exceed 4154 to have found a block.

With current Bitcoin difficulty of 2,621,404,453.0646, a miner needs a best share of 1.718e14 to find a block, which would probably be represented as 172T (because it's 172 tera-somethings. Terradifficulties?).
65536 has nothing to do with bitcoin - that's altcoin crapulence. If the diff is 2.6 billion, you need a share of 2.6 billion difficulty with bitcoin.
6525  Bitcoin / Hardware / Re: HashFast BabyJet users thread on: February 07, 2014, 05:54:04 AM
I've finally posted an official version that is designed to make the most of the new firmware coming up, cgminer 3.12.1

Announce and details here:
https://bitcointalk.org/index.php?topic=28402.msg4989440#msg4989440

This should also fix the windows reliability issues for those poor souls mining with their BlowJobs on windows.
6526  Bitcoin / Mining software (miners) / Re: CGMINER ASIC FPGA miner monitoring RPC linux/win/osx/mips/arm/r-pi 3.12.1 on: February 07, 2014, 05:40:31 AM
Quote
By default, Antminer U1 devices run at a clockspeed of 200. This command allows
you to specify a chosen frequency to attempt to run all ANU devices at and the
value must be in increments of 25. Note that cgminer reports hashrate ONLY
FROM VALID HASHES so if you increase the frequency but your hashrate does not
increase or it decreases and hardware errors start showing up, you have
overclocked it too much. In the worst case scenario it will fail to start at
too high a speed.

Note that adding --icarus-timing=short is basically mandatory if you overclock them at this stage. The requirement for this should be fixed in a future version.
6527  Bitcoin / Mining software (miners) / CGMINER ASIC FPGA miner monitoring RPC linux/win/osx/mips/arm/r-pi 3.12.1 on: February 07, 2014, 05:26:15 AM
New version: 3.12.1, 7th February 2014

Mostly lots of bugfixes and heaps of new features for hashfast devices with upgraded firmware (due out soon).

Human readable changelog:

- Dynamic temperature based fanspeed and per-die clockspeed control for hashfast devices with the following new commands.

--hfa-fan <arg>     Set fanspeed percentage for hashfast, single value or range (default: 10-85)
--hfa-temp-target <arg> Set the hashfast target temperature (0 to disable) (default: 88)

Defaults chosen are based on extensive discussion with the design engineers responsible for the silicon and boards and basically it will keep your hashfast devices as close to the starting clockspeed as possible while keeping under~95 degrees by initially increasing fanspeed, and then decreasing the clockspeed on the hottest dies discretely. The output can be watched via the API. Enduring sweltering temperatures of up to 44 degrees here has made for an excellent real world test for this code.
- Numerous startup/reset/shutdown reliability improvements for hashfast
- Send a ping to the hashfast device at regular intervals if we don't have any work for it just so it knows cgminer is still alive to try and minimise the dreaded watchdog reboots.
- Lots of extra information in the hashfast API stats output.
- Hashfast serial number is shown as a hex value now.
- Better hashfast flushing of work on restarts - new firmware will build further on this.
- Antminer U1 overclocking support with --anu-freq note:
Quote
By default, Antminer U1 devices run at a clockspeed of 200. This command allows
you to specify a chosen frequency to attempt to run all ANU devices at and the
value must be in increments of 25. Note that cgminer reports hashrate ONLY
FROM VALID HASHES so if you increase the frequency but your hashrate does not
increase or it decreases and hardware errors start showing up, you have
overclocked it too much. In the worst case scenario it will fail to start at
too high a speed.
You basically must use --icarus-timing=short additionally to get the maximum benefit out of the overclocking (at this stage).
- Keep taking a trickle of work even if it's not being used just to keep an eye on pools and to keep the most recent work time up to date
- Make the top "window" wider since hashes these days come in the many millions and don't fit into 80 characters
- In verbose mode, the share above target message shows for which device
- Rolled back to the last good working libusb - the alleged libusb/x merge did not bring improvements and added windows instability with spontaneous exiting
- Handle better numerous non-terminal errors (the cgsem ones) that were leading to cgminer exiting
- BAB improvements courtesy of Kano
- Verbose mode will now show if it takes time to submit a stratum share, or it takes a long time to get a response from pools due to them lagging substantially, to help debug where latencies might be causing high stales.
- Added a way to zero other stats within each driver when the zero stats command is given (though no driver currently uses it).
- Fix one stale work item being passed to drivers after a block change.
- Fix a rare usbutils crash
- Pool diffs that are fractions only show one decimal place now.
- In debug mode a message will show up if there are substantial delays in getting work.
- Fix for massive data over the API
- Other random fixes.


Full changelog:

- Document new features for antminer U1 and hfa devices.
- Add support for ANU overclocking.
- Increase hfa fanspeed by more if we're rising in temp above the target than if
the temp is staying the same.
- Add debug output when get_work() is blocked for an extended period and add
grace time to the device's last valid work to prevent false positives for device
failure.
- Issue a shutdown prior to a reset command for hfa devices and lock access to
reads awaiting the response if the device is already running.
- Do not register as successful a hfa init sequence that reports the clockrate
as zero.
- Show device info in noffset nonce share above target message.
- Widen lines in top menu to fit extra large share values.
- Only show one decimal place if pool diff is not an integer.
- Show serial number as a hex value in hfa verbose startup.
- Slowly remove work even if it's not being used to keep the getwork counter
incrementing even if work is not used and as a test that pools are still
working.
- Increase the maximum diff between hfa dies to 100Mhz.
- Show which hfa die is bringing down all the others when decreasing all the
clock speeds.
- Increase the decrease when temp has increased more and we want to decrease it
on hfa.
- Give device info with share above target message.
- Allow throttling of hfa dies more frequently and increasing of speeds less
frequently.
- Wait after sending a hfa shutdown to allow the device to properly shut down
before possibly sending it more commands.
- Minimise the die clock differences in hfa to no more than 50Mhz.
- Check for when errno is set on windows as well as the windows variant for
errors.
- Revert "Update to libusb-1.0.18"
- Disable fan/die clock control in hfa if the firmware does not support it, with
notification.
- Add ability to enter ANU frequency as a multiple of 25 from 150-500.
- Decrease hfa clock by 10 if a reset is attempted due to the device remaining
idle.
- ifdef out icarus options unused without icarus built in.
- Reorder command line options alphabetically.
- Add no matching work to hfa API output.
- Change various logging message levels in the hfa driver.
- Only adjust clocks if there is no restart in hfa to avoid 2 restarts back to
back.
- Ensure we iterate over all dies adjusting temperate for hfa by starting
iterating after the last die modified.
- Clamp initial hfa fanspeed to min/max if passed as parameters.
- Allow hfa fanspeed to be set via command line.
- Further relax the target temperatures on hfa driver, targetting 88 degrees.
- Try one more time to get the hfa header on init since it can take 2 seconds
for all 3 boards on a sierra.
- Update authors for removal of gpu/scrypt.
- Wait for 5 temperature updates in hfa before adjusting fanspeed.
- Have some leeway before starting to throttle hfa dies.
- Use increments of 10 when increasing hfa clock since it may not have 5 MHz
granularity internally.
- Only perform a hfa fan speed update if we have new temps to work with.
- Correctly measure the hfa max temp and smooth out the changes in its value.
- Choose better defaults for min/max/default fan settings for hfa driver.
- bab - reduce def speed, fix speed staying in ranges and report bank/chips in
ioctl() errors
- bab - add info about number of boards/chips to each Dead Chain
- These may not be longs (eg: OSX)... fo a safe cast to ensure.
- bab - add dead boards and dead chains to stats
- Add fanspeed to hfa api output and set initial fanspeed to 10%
- Add hfa fanspeed control to try and maintain a target temperature.
- API-README correct new text format documentation
- API allow multiple commands/replies in one request
- Add op commands necessary to control hfa fanspeeds.
- Add OP_FAN to hf protocol header.
- Always show the stratum share lag time in debug mode.
- Add stratum share response lag time to verbose output if it's greater than 1
second.
- Add stratum share submission lag time to verbose information if it's over 1
second.
- Check for more interrupted conditions in util.c and handle them gracefully.
- Send a ping to hfa devices if nothing is sent for over 5 seconds.
- Add OP_PING to hfa commands
- Display the hfa serial number as a hexadecimal value.
- Add the ability to display a hexadecimal 32 bit unsigned integer to the API.
- Limit all hfa restarts for temperature control to no closer than 15 seconds
apart.
- Allow the hfa temp target to be disabled by setting it to zero.
- Handle interruptions to various select calls in util.c
- Add sanity check for silly overflows in hfa die temperature readings.
- Add per-die throttling control for hfa driver based on each die's temperature,
issuing a suitable reset to maintain the temperature below a configurable target
temperature.
- Update hf protocol
- Do not memcpy in usbutils unless data was transferred.
- Send a full allotment of jobs to the hfa device after a restart instead of
reading the status.
- Export the flush_queue function for use by drivers.
- Remove wrong goto
- Remove the unqueued work reference when we discard work from get queued as
well.
- Wake the global work scheduler when we remove a work item from the unqueued
work pointer.
- Discard work that is stale in the get_queued() function, returning NULL
instead.
- Add a call to a driver specific zero stats function when zero stats is called
to allow each driver to reset its own stats as well if desired.
6528  Bitcoin / Mining software (miners) / Re: CGminer autoreconnect to primary? on: February 06, 2014, 10:05:41 PM
Yes it's supposed to go back in failover mode.
6529  Bitcoin / Mining software (miners) / Re: CGMINER ASIC FPGA miner monitoring RPC linux/win/osx/mips/arm/r-pi 3.12.0 on: February 06, 2014, 08:09:53 PM
Is the option --anu-freq not enabled in the rest of the code for now?
It's just command line option code with nothing implemented yet.
6530  Bitcoin / Mining software (miners) / Re: CGMINER ASIC FPGA miner monitoring RPC linux/win/osx/mips/arm/r-pi 3.12.0 on: February 06, 2014, 02:11:58 PM
Hello,

Could it be that cgminer-3.12 has a memory leak?

When I run it on my RaspPI for ca. one day, the memory gets swamped like hell, as well as the swap. As soon as I stop cgminer, memory and swap load go down to near zero. I used htop to trace the memory... Also I recognized that, when I don't stop and restart cgminer, it crashes with a segmentation fault at some point (which might be the point, when there is no more memory available).

It would be great if you could check and eventually fix that Smiley


Best Regards

There may well be a memory leak. I have not seen one, but I do not run anything on an RPi. If you can run the most current code from git as a debug build and get output it would be most helpful.
See:
http://ck.kolivas.org/apps/cgminer/debug/README-debug
6531  Bitcoin / Mining software (miners) / Re: CGMINER ASIC FPGA miner monitoring RPC linux/win/osx/mips/arm/r-pi 3.12.0 on: February 06, 2014, 01:08:10 PM
Is there any chance that Keccak (SHA3) mining will work on AMD GPUs?  Smiley
None.

I'm not a skilled programmer, could you explain why? Smiley It seems like the Nvidia guys have found a way to make it work.
cgminer is now bitcoin only mining software with no gpu code
6532  Other / Meta / Re: ckolivas for Moderator on: February 06, 2014, 12:57:39 PM
Quote
You have reported 1061 posts with 99% accuracy
6533  Bitcoin / Mining software (miners) / Re: CGMINER ASIC FPGA miner monitoring RPC linux/win/osx/mips/arm/r-pi 3.12.0 on: February 06, 2014, 12:39:42 PM
Is there any chance that Keccak (SHA3) mining will work on AMD GPUs?  Smiley
None.
6534  Other / Meta / Re: ckolivas for Moderator on: February 06, 2014, 11:16:03 AM
I'm pretty sure that making me a moderator just for cleaning up my own thread is overkill, but that was more sarcasm than anything else. I'd be happy to help out where I could.
Keep those report flying in  Kiss
Yes sir o\
6535  Other / Meta / Re: ckolivas for Moderator on: February 06, 2014, 03:21:36 AM
I'm pretty sure that making me a moderator just for cleaning up my own thread is overkill, but that was more sarcasm than anything else. I'd be happy to help out where I could.
6536  Bitcoin / Hardware / Re: HashFast BabyJet users thread on: February 06, 2014, 03:18:10 AM
[Suspicious link removed]

Thank you for you help minternj. I downloaded 3.12.0 and it looks can see the device, but still gave an error:
[2014-02-04 22:49:28] USB all: found 3 devices - listing known devices
.USB dev 0: Bus 2 Device 127 ID: 297c:0001
  ** dev 0: Failed to open, err -3                   
 [2014-02-04 22:49:28] 1 known USB devices                   
Read the fine document called ASIC-README included with cgminer.

Thank you ckolivas. I figured that it's the permission issue. And I followed the guide and added current user into plugdev group by issuing:
sudo usermod -G plugdev -a `whoami`

But it does not fix the problem. In this case does that mean I can only run cgminer under root user? Or you think it's not the issue of permission? Please kindly point out.
Also I logged into my RB Pi and can see cgminer is running under minepeon user and that user belongs only to minepeon group.

Anyway thank you for you help, I have made my RB Pi working now, so have no chance to test BJ on my linux box for now. Will report when I get a chance.
That wasn't all the instructions that were in the readme, you need the udev file installed. That other command is usually not needed in fact - but I don't know how permissions are set up on minepeon as the instructions revolve around regular PCs running regular PC distributions of linux and I'm no RPi distribution expert. It is always a permissions problem if it goes away as root.
6537  Bitcoin / Mining software (miners) / Re: CGMINER ASIC FPGA miner monitoring RPC linux/win/osx/mips/arm/r-pi 3.12.0 on: February 06, 2014, 01:32:52 AM
was failed to
Code:
 sem_timedwait errno=10060 cgsem=0x044ed2bc sbutils.c callback_wait():2452
one of the expected errors for your test cgminer in the temp folder?
Yes that's addressed in the new code.
6538  Bitcoin / Hardware / Re: HashFast BabyJet users thread on: February 05, 2014, 11:42:06 PM
I don't know how to get a message to ckolivas, but I'm testing the current master branch of cgminer and one feature that was added is fan speed control (OP code 143).  However, I keep getting the error that OP_CODE 143 is unhandled.

Is it possible that I have an older revision of the board/firmware something that doesn't support controlling the fan speed using that op code?
The code in git master needs new firmware which is not out yet.

2 quick questions,

1. is it possible to just disable cgminer from seeing other hardware, for example BFL. I tried the only allowing usb device 1 or something but I have no way of figuring out which device is what number.

2. is there anyway to see each cores temp in windows like on the RPI?
1. Read section on --usb in the README eg --usb HFA:1,BAS:0
2. Via the RPC API stats command which has busloads of information.
eg:
java API stats


Code:
[STATS8] =>
(
   [STATS] => 8
   [ID] => HFS3
   [Elapsed] => 45661
   [Calls] => 0
   [Wait] => 0.000000
   [Max] => 0.000000
   [Min] => 99999999.000000
   [asic count] => 12
   [core count] => 96
   [firmware rev] => 0.3
   [hardware rev] => 1.1
   [serial number] => 0xc10cfe86
   [hash clockrate] => 604
   [inflight target] => 2300
   [sequence modulus] => 8192
   [fan percent] => 56
   [rx preambles] => 2
   [rx rcv byte err] => 0
   [rx bad hcrc] => 0
   [tx attempts] => 0
   [tx packets] => 0
   [tx incompletes] => 0
   [tx ep stalled] => 0
   [tx disconnect] => 0
   [tx suspend] => 0
   [max tx buf] => 0
   [max rx buf] => 0
   [Core] => 0
   [hash clockrate] => 615
   [die temperature] => 79.300781
   [board temperature] => 65.489990
   [core voltage] => 0: 0.79
   [core voltage] => 1: 0.00
   [core voltage] => 2: 0.00
   [core voltage] => 3: 0.00
   [core voltage] => 4: 0.00
   [core voltage] => 5: 0.00
   [rx header crc] => 0
   [rx body crc] => 0
   [rx header to] => 0
   [rx body to] => 0
   [cn fifo full] => 0
   [an fifo full] => 0
   [stats overrun] => 0
   [Core] => 1
   [hash clockrate] => 615
   [die temperature] => 73.968750
   [board temperature] => 65.895256
   [core voltage] => 0: 0.80
   [core voltage] => 1: 0.00
   [core voltage] => 2: 0.00
   [core voltage] => 3: 0.00
   [core voltage] => 4: 0.00
   [core voltage] => 5: 0.00
   [rx header crc] => 0
   [rx body crc] => 0
   [rx header to] => 0
   [rx body to] => 0
   [cn fifo full] => 0
   [an fifo full] => 0
   [stats overrun] => 0
   [Core] => 2
   [hash clockrate] => 615
   [die temperature] => 79.242188
   [board temperature] => 64.298401
   [core voltage] => 0: 0.79
   [core voltage] => 1: 0.00
   [core voltage] => 2: 0.00
   [core voltage] => 3: 0.00
   [core voltage] => 4: 0.00
   [core voltage] => 5: 0.00
   [rx header crc] => 0
   [rx body crc] => 0
   [rx header to] => 0
   [rx body to] => 0
   [cn fifo full] => 0
   [an fifo full] => 0
   [stats overrun] => 0
   [Core] => 3
   [hash clockrate] => 615
   [die temperature] => 81.234375
   [board temperature] => 63.523308
   [core voltage] => 0: 0.78
   [core voltage] => 1: 0.00
   [core voltage] => 2: 0.00
   [core voltage] => 3: 0.00
   [core voltage] => 4: 0.00
   [core voltage] => 5: 0.00
   [rx header crc] => 0
   [rx body crc] => 0
   [rx header to] => 0
   [rx body to] => 0
   [cn fifo full] => 0
   [an fifo full] => 5364
   [stats overrun] => 21
   [Core] => 4
   [hash clockrate] => 615
   [die temperature] => 83.871094
   [board temperature] => 75.037781
   [core voltage] => 0: 0.79
   [core voltage] => 1: 0.00
   [core voltage] => 2: 0.00
   [core voltage] => 3: 0.00
   [core voltage] => 4: 0.00
   [core voltage] => 5: 0.00
   [rx header crc] => 0
   [rx body crc] => 0
   [rx header to] => 0
   [rx body to] => 0
   [cn fifo full] => 0
   [an fifo full] => 0
   [stats overrun] => 0
   [Core] => 5
   [hash clockrate] => 615
   [die temperature] => 80.414062
   [board temperature] => 74.524971
   [core voltage] => 0: 0.79
   [core voltage] => 1: 0.00
   [core voltage] => 2: 0.00
   [core voltage] => 3: 0.00
   [core voltage] => 4: 0.00
   [core voltage] => 5: 0.00
   [rx header crc] => 0
   [rx body crc] => 0
   [rx header to] => 0
   [rx body to] => 0
   [cn fifo full] => 0
   [an fifo full] => 0
   [stats overrun] => 0
   [Core] => 6
   [hash clockrate] => 615
   [die temperature] => 80.589844
   [board temperature] => 69.744179
   [core voltage] => 0: 0.78
   [core voltage] => 1: 0.00
   [core voltage] => 2: 0.00
   [core voltage] => 3: 0.00
   [core voltage] => 4: 0.00
   [core voltage] => 5: 0.00
   [rx header crc] => 0
   [rx body crc] => 0
   [rx header to] => 0
   [rx body to] => 0
   [cn fifo full] => 0
   [an fifo full] => 0
   [stats overrun] => 0
   [Core] => 7
   [hash clockrate] => 615
   [die temperature] => 87.503906
   [board temperature] => 73.768532
   [core voltage] => 0: 0.78
   [core voltage] => 1: 0.00
   [core voltage] => 2: 0.00
   [core voltage] => 3: 0.00
   [core voltage] => 4: 0.00
   [core voltage] => 5: 0.00
   [rx header crc] => 0
   [rx body crc] => 0
   [rx header to] => 0
   [rx body to] => 0
   [cn fifo full] => 0
   [an fifo full] => 0
   [stats overrun] => 0
   [Core] => 8
   [hash clockrate] => 615
   [die temperature] => 78.070312
   [board temperature] => 66.304733
   [core voltage] => 0: 0.79
   [core voltage] => 1: 0.00
   [core voltage] => 2: 0.00
   [core voltage] => 3: 0.00
   [core voltage] => 4: 0.00
   [core voltage] => 5: 0.00
   [rx header crc] => 0
   [rx body crc] => 0
   [rx header to] => 0
   [rx body to] => 0
   [cn fifo full] => 0
   [an fifo full] => 0
   [stats overrun] => 0
   [Core] => 9
   [hash clockrate] => 615
   [die temperature] => 76.429688
   [board temperature] => 69.297256
   [core voltage] => 0: 0.79
   [core voltage] => 1: 0.00
   [core voltage] => 2: 0.00
   [core voltage] => 3: 0.00
   [core voltage] => 4: 0.00
   [core voltage] => 5: 0.00
   [rx header crc] => 0
   [rx body crc] => 0
   [rx header to] => 0
   [rx body to] => 0
   [cn fifo full] => 0
   [an fifo full] => 0
   [stats overrun] => 0
   [Core] => 10
   [hash clockrate] => 615
   [die temperature] => 78.070312
   [board temperature] => 68.855446
   [core voltage] => 0: 0.79
   [core voltage] => 1: 0.00
   [core voltage] => 2: 0.00
   [core voltage] => 3: 0.00
   [core voltage] => 4: 0.00
   [core voltage] => 5: 0.00
   [rx header crc] => 0
   [rx body crc] => 0
   [rx header to] => 0
   [rx body to] => 0
   [cn fifo full] => 0
   [an fifo full] => 0
   [stats overrun] => 0
   [Core] => 11
   [hash clockrate] => 615
   [die temperature] => 75.375000
   [board temperature] => 72.299377
   [core voltage] => 0: 0.79
   [core voltage] => 1: 0.00
   [core voltage] => 2: 0.00
   [core voltage] => 3: 0.00
   [core voltage] => 4: 0.00
   [core voltage] => 5: 0.00
   [rx header crc] => 0
   [rx body crc] => 0
   [rx header to] => 0
   [rx body to] => 0
   [cn fifo full] => 0
   [an fifo full] => 0
   [stats overrun] => 0
   [raw hashcount] => 54752187254833152
   [calc hashcount] => 50974458467488978
   [no matching work] => 675
   [resets] => 0
   [USB Pipe] => 0
   [USB Delay] => r0 0.000000 w0 0.000000
   [USB tmo] => 13598514 0
)
6539  Bitcoin / Mining software (miners) / Re: CGMINER ASIC FPGA miner monitoring RPC linux/win/osx/mips/arm/r-pi 3.12.0 on: February 05, 2014, 11:29:39 PM
So would it be o.k to try this out or did you already clear out the temps? If it works better and doesn't fudge stuff make a 3.12.1 version... right?

Your website is giving me troubles getting to it.

This is where I've been getting releases from you ck.kolivas.org/apps/cgminer/ . Has the page changed or is someone screwing with it?
Try it, that's still the site.
6540  Bitcoin / Mining software (miners) / Re: CGMINER ASIC FPGA miner monitoring RPC linux/win/osx/mips/arm/r-pi 3.12.0 on: February 05, 2014, 10:47:24 PM
ckolivas
2nd temp binary is still running ok yet.
Thanks very much for your testing. This confirms that the upgrade from libusb to the merged libusb/x is at fault. It seems that libusbx is still not up to the task. I will revert to the good working libusb in the next  version again.
Pages: « 1 ... 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 [327] 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 ... 573 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!