I do not know what are advantages?
Did not try it yet.

I am new to mining.

Started this week.

You're missing a space between your workername and "-p"

This:


Should look like this:

Trying to run it on my laptop, and cgminer crashes.

Catalyst mobility 13.9; cgminer any version I've tried... tried as far back as 2.10.1

Any help on what drivers to use to not crash cgminer?

Problem Event Name:   APPCRASH
  Application Name:   cgminer.exe
  Application Version:   0.0.0.0
  Application Timestamp:   50c5c2b3
  Fault Module Name:   cgminer.exe
  Fault Module Version:   0.0.0.0
  Fault Module Timestamp:   50c5c2b3
  Exception Code:   c0000005
  Exception Offset:   00022c9e
  OS Version:   6.1.7601.2.1.0.768.3
  Locale ID:   1033
  Additional Information 1:   bff4
  Additional Information 2:   bff41f1be3cd4d1bb87c59a3b18ce19f
  Additional Information 3:   b59a
  Additional Information 4:   b59a7986763d996ceaff15c0752ec258

You don't have any hardware for cgminer to mine with. It is no longer a cpu or gpu miner.

What need it else?

EDIT: ok i saw it asic fpga never heard before from it^^

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.

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.

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.

Thank you for the update.

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

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