Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 168. (Read 5805527 times)

Well here's a screen capture.

I had moved the Jalapeno to an old low power machine and got this.  On my normal rig it works fine.  So I'm not sure it's not a problem on my old machine.

That's bad, mmkay. Some code screw up on my part. Got some more output so I can figure out where the fuckage happened?

What does

hex2bin scan failed

mean?  Using 3.8.3 with my Jalapeno.
Sam

I'm trying the same commands as I did with version 3.8.1 like "pools", "summary", and others

This version of cgminer takes 10-15 seconds to boot up, because of the enabling of cores beforehand (presumably)...  'screen -rd' works, you just have to wait a while for it to launch.

Also, ckolivas, would it be possible to make available the previous kncminer 3.8.2 (without the tuning)? I was getting better hashrates overall on both of my machines with that one, for whatever reason. Thanks.

Is there a way to force cgminer to ignore a specific device? I use a FTDI based USB to serial convertor to control an RS232 Power Distribution Unit. It doesn't seem to affect the mining, but it's pretty annoying to have constant Incorrect Driver messages scroll across the screen.

Did you try a valid command?

Seems like API is disabled in this version with the following message:
Invalid command
cgminer 3.8.2

Was it done on purpose? Can we get it back, please?

Just curious as to if anyone has tried this with Klondike units. The change log didn't provide specific references to them and I'm not home to test it out.

So, having returned from holiday leaving "ymmv" running unattended for 2 weeks, I found 1 reported zombie and another 4 or 5 AMUs which had a very low WU, and had obviously been doing nothing for a while.  While I was away I was monitoring my pool hash rate and noticed that it slowly dropped from an expected 11 Gh/s to around 9.x over the two weeks which ties in with the above findings.

I restarted "ymmv" but got several random LEDs coming full on for a few seconds at a time then going off again. Obviously not happy, so I then reverted to running 3.5.1 which ran perfectly and has been doing so all night with no zombies and all WU's between 4.6 - 4.8.  This build is so stable!

I guess I will try 3.8.3 next unless there are other suggestions?

No scrypt support any more.

Is the non working port blue?  I have yet to get cgminer to work with a usb minor on a usb 3.0 (blue) port.

M

Wasn't there a scrypt readme somewhere? I can't find it anymore 

Thank you for the update.

Do you think this version should help with my USB device in use issue?

USB 3 drivers on windows are inconsistent and have conflicts with the usb1.1 devices (like BEs) and the libusb library we use to talk to them. USB2 slots are infinitely more compatible (or use linux).

In two my laptops (Samsung and Toshiba) the BEs in Tecknet USB 3.0 10 port hub works stable only if hub is connected to one of USB port and does not using another.
Write timeouts appears there. What it can be the difference in laptops USB ports?
WinUSB driver 6.1.7600.16385 is in use, set up by zadig utility. OSes are different, win 8 x64 and win 7 x64.

Sorry, I should have given more details, it is on a begelbone black running Arch;-

uname -a
Linux minepeon 3.12.1-1-ARCH #1 SMP Wed Nov 20 20:27:04 MST 2013 armv7l GNU/Linux

I have enabled the spi's and i2c,  I am also looking through their firmware to see what needs to be done, I was just wondering if you had a sort of 'cheat sheat' to get them going.

Neil

Based on your config file info, you seem to be running that binary on an RPi? The KnC devices come with a beaglebone built in, so what is this combination? Have you built a custom one plugging the GPIO pins of an RPi to the KnC hardware? There's an awful lot more to running those devices than just cgminer, if I'm not mistaken. The firmware does a lot more than just run cgminer on a beaglebone.

Hi Guys,

Are there any "tricks" to the KnC Driver?  This is my frist play with it and I am unsure if I should be doing any i2cset's.

What I am getting is;-


Any notes you have on running these things would be appreciated.

Neil

New release: Version 3.8.3, 23rd November 2013

Minor driver update and bugfixes.

Human readable changelog:

- Average hashrate shown for BF1 and BXF devices will now rise quickly on startup.
- The bi*fury device in its release form had different firmware from my development one so the driver has been updated to work with it.
- Fixed the bxf device to align in the display column if temperature went above 100 degrees.
- Don't keep displaying json auth failed on stratum pools that are misbehaving except at verbose logging level.
- Very small improvement in hardware error rate on some USB devices due to the way return messages are handled.
- Fix a memory leak when json is used to communicate with the RPC API
- Avalon improvements to fix the sudden drops in hashrate (these fixes are all already in the last avalon firmware I uploaded).
- Unlimited re-hotplugging of devices that have USB failures and turn into zombies but have had their USB reset by the operating system.


Full changelog:

- Set the bitfury device start times from when we first get valid work.
- Fix stack corruption of zeroing too much in bf1 driver.
- Make usb_detect return the cgpu associated with it to check if it succeeds to
decide on whether to increment the device count or not.
- Set tv work start time for bxf driver.
- Age the bxf work items over 90 seconds, not the bf1 work items.
- Zero the read buffer in _usb_read to avoid stale data and only use stack
memory instead of using the bulkbuf since it is only used in _usb_read.
- Leave room for temperatures above 100 degrees and pad consistently for bxf
statline.
- Drop json stratum auth failed message log level to verbose.
- Change the processed value not the bufsiz in response to an end of message
marker.
- Don't lose data beyond the end of message in a usb read.
- Silence irrelevant warning.
- Only check strlen on end if end exists.
- Simplify the end of message detection in _usb_read and allow it to return
without doing another read if the message is already in the buffer.
- Increase work ageing time to 90 seconds for bxf driver to account for firmware
changes.
- Use the age_queued_work function in the bitfury driver.
- Provide a function to discard queued work based on age.
- The json_val in api.c is a borrowed reference, not a new one so don't decref
it.
- Decrement json references in api.c to not leak memory.
- line 2913 added urlencode
- With reliable writes to the avalon there is no need for the sleep delays
between writes.
- There is no need to limit usb write transfers to maxpacketsize and it's
harmful for large transfers on slow devices such as wrt routers.
- Disable USB stats which were not meant to be enabled by default and add extra
memory for a memory error when stats are enabled.
- Set limit and count to integers to not overflow during failed hotplug attempts
and then not trying again.
- Update api example compilation instructions.