OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.1

[nowaltcoin]

But this version is complaining about the NFY-Devices ( should consult the readme about the right usb-lib drivers for the devices)

Every single USB device on cgminer uses exactly the same USB driver. Crashes should never happen, and any debugging would be most appreciated as per:
http://ck.kolivas.org/apps/cgminer/debug/README-debug

If you're not interested in helping the developers debug issues with the software you're depending on for free, feel free to read how to use the --usb command (as Kano has suggested) from the readme, to choose only the devices you want it to work on.

Sury i like to help..........but the problem is: Most of the times cgminer crashes when i'am on work (the rig is at home) or in the night when i'am sleeping so i could only see the windows hint (cgminer applikation has an error and has to be closed)


So just tell me how i can help !

stay tuned

[-ck]

But this version is complaining about the NFY-Devices ( should consult the readme about the right usb-lib drivers for the devices)

Every single USB device on cgminer uses exactly the same USB driver. Crashes should never happen, and any debugging would be most appreciated as per:
http://ck.kolivas.org/apps/cgminer/debug/README-debug

If you're not interested in helping the developers debug issues with the software you're depending on for free, feel free to read how to use the --usb command (as Kano has suggested) from the readme, to choose only the devices you want it to work on.

Sury i like to help..........but the problem is: Most of the times cgminer crashes when i'am on work (the rig is at home) or in the night when i'am sleeping so i could only see the windows hint (cgminer applikation has an error and has to be closed)


So just tell me how i can help !

stay tuned

Well I already gave you a link to the instructions on how to help... but by far the easiest thing for you to do is just mine with everything on cgminer as the NF1 devices as they're called by cgminer are fully supported, and you set them up exactly as you set up every other USB device you've used so far on cgminer so it's about 10 seconds' work.

[FalconFly]

Good morning


is there any way to tell cgminer (newest version) not to use some devices?

Story:

I'am using some NFY-Devices with BFGMiner. (stable for now more than 4 month)
But i did not get my BiFury and Redfury running with BFGMiner so i use CGMiner for these.

The last weeks CGMiner is starting crashing constantly every 6-10 hours. (with usblib errors on alternating devices)
So i downloaded the 4.0.1 Version and it is more stable (crash every 18-24 hours)

But this version is complaining about the NFY-Devices ( should consult the readme about the right usb-lib drivers for the devices)

So any hint are very welcome

I ran into a similar problem (3x BlueFury v2 and 1x BiFury).
The RAM usage of cgminer (any version) keeps creeping up on me and at some point (some 400-500MB usage) it will eventually crash.

My solution that worked for me so far :
Installed CGwatcher and set it up simply to auto-restart cgminer every 6 hours and in case it quits/crashes otherwise or drops below a certain threshhold (i.e. a USB device dropped offline).

Except for one single occasion in ~2 months, the system ran without issues ever since (after otherwise crashing almost daily, typically overnight or when I was a work )

[nowaltcoin]

But this version is complaining about the NFY-Devices ( should consult the readme about the right usb-lib drivers for the devices)

Every single USB device on cgminer uses exactly the same USB driver. Crashes should never happen, and any debugging would be most appreciated as per:
http://ck.kolivas.org/apps/cgminer/debug/README-debug

If you're not interested in helping the developers debug issues with the software you're depending on for free, feel free to read how to use the --usb command (as Kano has suggested) from the readme, to choose only the devices you want it to work on.

Sury i like to help..........but the problem is: Most of the times cgminer crashes when i'am on work (the rig is at home) or in the night when i'am sleeping so i could only see the windows hint (cgminer applikation has an error and has to be closed)


So just tell me how i can help !

stay tuned

Well I already gave you a link to the instructions on how to help... but by far the easiest thing for you to do is just mine with everything on cgminer as the NF1 devices as they're called by cgminer are fully supported, and you set them up exactly as you set up every other USB device you've used so far on cgminer so it's about 10 seconds' work.

Ok i will try out your link these evening at home.

Yes i can move the NF1 devices to cgminer but the crashing of it  will be the same and i do not have access to my home-rig any given time (so that will cost a lot of hashpower for me).

Debugging cgminer and having it stable and than moving the NF1 to it would be my preferable way

[-ck]

Ok i will try out your link these evening at home.

Yes i can move the NF1 devices to cgminer but the crashing of it  will be the same and i do not have access to my home-rig any given time (so that will cost a lot of hashpower for me).

Debugging cgminer and having it stable and than moving the NF1 to it would be my preferable way

Unless the crashing is because the software is fighting over the device in which case it will go away.

[-ck]

Guys, if you get a crash, debugging information will help everyone long term since that's how I'll actually get to fix the bugs. This is not a closed source proprietary piece of hidden software, it is a community project  despite the fact there are only a very small number of developers, and we need information from the users as much as they need our code. While I'm forever developing code for new features and drivers, I am seriously interested in stability over anything else. My rigs run for months without a crash and that's how I want it to be for the other users, but I don't have all hardware combinations on all operating systems (nor do I even want that). I've debugged a LOT of issues courtesy of debug traces, logins into other people's machines and bug reports and so on that would never have been fixed otherwise.

[nowaltcoin]

Ok i will try out your link these evening at home.

Yes i can move the NF1 devices to cgminer but the crashing of it  will be the same and i do not have access to my home-rig any given time (so that will cost a lot of hashpower for me).

Debugging cgminer and having it stable and than moving the NF1 to it would be my preferable way

Unless the crashing is because the software is fighting over the device in which case it will go away.

I tried Version 3.8.5/3.9/3.12.3 ----> these version did not complain about NF1-Devices (but maybee fighting anyway for that devices)

the charm of the NF1 devices (you do not need a spezial driver for it for BFGMiner) they will be install as a USB-Hid devices by windows 7 and BFGMiner just grab them.

[-ck]

Ok i will try out your link these evening at home.

Yes i can move the NF1 devices to cgminer but the crashing of it  will be the same and i do not have access to my home-rig any given time (so that will cost a lot of hashpower for me).

Debugging cgminer and having it stable and than moving the NF1 to it would be my preferable way

Unless the crashing is because the software is fighting over the device in which case it will go away.

I tried Version 3.8.5/3.9/3.12.3 ----> these version did not complain about NF1-Devices (but maybee fighting anyway for that devices)

the charm of the NF1 devices (you do not need a spezial driver for it for BFGMiner) they will be install as a USB-Hid devices by windows 7 and BFGMiner just grab them.

That is not charm, everything uses the WinUSB driver on windows on cgminer - you install one driver for everything and just associate it with your device if you ever get a different type of device. Saying a driver happens to work for a piece of software is not really something special...

And coincidentally, I happen to have all the devices you're describing.

Code:

 0: NF1  0:                         | 2.577G/2.565Gh/s | A:  16140 R:    0 HW:     0 WU:   35.9/m
  3: NF1  1:                         | 2.111G/2.099Gh/s | A:   8070 R:    0 HW:     0 WU:   29.4/m
  4: BXF  0:  44.8C                  | 5.036G/5.010Gh/s | A:  52596 R:    0 HW:     0 WU:   70.2/m
  8: BF1  0:                         | 2.368G/2.368Gh/s | A:  15375 R:    0 HW:  1640 WU:   33.1/m

And they all work fine on my rig.

Once the drivers are set up on cgminer, you can plug and unplug as many of those same devices as you like and cgminer will hotplug and unplug them without any further intervention.

[nowaltcoin]

Hi

ok i will do like i did for the BiFury and redfury.

I will install the winusb-driver with zadig to point to the nanofurys and will than have all devices in the 4.0.1 Cgminer
Then we can see if it crashes again, if so i will send you the debug information! D'accord ?

stay tuned

[nowaltcoin]

up and running with all devices

did not get the --nfu-bits working in cgminer.conf
so i give it in commandline

Now i have to have a look whats about the hashpower compare to bfgminer
and how long it will run   

thanks for help

[d574kerr]

Im trying to get a mining rig for under $1000 is that possible?

[nowaltcoin]

cgminer 4.1.0 crashed....  (and i hoped not) after 7 hours... something with bxf1 usb-lib device is already in use.

I installed the debugger  and the debugger version (4.0.0 i hope that does not matter) and wait for the next crash...

Have a nice night

[kano]

Im trying to get a mining rig for under $1000 is that possible?

RPi, powered USB hub, ASIC USB thumb ... under $100 ?
Though it is a waste of time and money ... it costs more BTC than it will ever mine

[coretechs]

EDIT: Also, cpu usage by cgminer seems to have greatly increased. I noticed these things with two machines running Windows 7.

I wanted to post the same observation.  I've been upgrading every few releases and had been on 3.8-3.9 for a long time with a few BFL units.  In 3.9 the CPU usually averages around 15%-16%.  Going to 4.0.1 the CPU usage slowly increases and levels off at ~35%.

Ubuntu 12.04.4 x64, 3.11 kernel, gcc 4.6.3
CFLAGS="-O2 -Wall -march=native" ./configure --enable-bflsc

[-ck]

EDIT: Also, cpu usage by cgminer seems to have greatly increased. I noticed these things with two machines running Windows 7.

I wanted to post the same observation.  I've been upgrading every few releases and had been on 3.8-3.9 for a long time with a few BFL units.  In 3.9 the CPU usually averages around 15%-16%.  Going to 4.0.1 the CPU usage slowly increases and levels off at ~35%.

Ubuntu 12.04.4 x64, 3.11 kernel, gcc 4.6.3
CFLAGS="-O2 -Wall -march=native" ./configure --enable-bflsc

Yes that's almost certainly the queue increasing in size automatically, which I will likely remove next version.

[loshia]

EDIT: Also, cpu usage by cgminer seems to have greatly increased. I noticed these things with two machines running Windows 7.

I wanted to post the same observation.  I've been upgrading every few releases and had been on 3.8-3.9 for a long time with a few BFL units.  In 3.9 the CPU usually averages around 15%-16%.  Going to 4.0.1 the CPU usage slowly increases and levels off at ~35%.

Ubuntu 12.04.4 x64, 3.11 kernel, gcc 4.6.3
CFLAGS="-O2 -Wall -march=native" ./configure --enable-bflsc

Yes that's almost certainly the queue increasing in size automatically, which I will likely remove next version.

Probably CPU increase is due to define LOCK_TRACKING 1
Or at least disabling it is reducing CPU usage for me
In 3.8-3.9 it was disabled if i remember correctly


@@ -690,7 +711,7 @@
  * So, e.g. use it to track down a deadlock - after a reproducable deadlock occurs
  * ... Of course if the API code itself deadlocks, it wont help
  */
-#define LOCK_TRACKING 1
+#define LOCK_TRACKING 0

[-ck]

EDIT: Also, cpu usage by cgminer seems to have greatly increased. I noticed these things with two machines running Windows 7.

I wanted to post the same observation.  I've been upgrading every few releases and had been on 3.8-3.9 for a long time with a few BFL units.  In 3.9 the CPU usually averages around 15%-16%.  Going to 4.0.1 the CPU usage slowly increases and levels off at ~35%.

Ubuntu 12.04.4 x64, 3.11 kernel, gcc 4.6.3
CFLAGS="-O2 -Wall -march=native" ./configure --enable-bflsc

Yes that's almost certainly the queue increasing in size automatically, which I will likely remove next version.

Probably CPU increase is due to define LOCK_TRACKING 1
Or at least disabling it is reducing CPU usage for me
In 3.8-3.9 it was disabled if i remember correctly


@@ -690,7 +711,7 @@
  * So, e.g. use it to track down a deadlock - after a reproducable deadlock occurs
  * ... Of course if the API code itself deadlocks, it wont help
  */
-#define LOCK_TRACKING 1
+#define LOCK_TRACKING 0

Crap, good pickup. I must have enabled it by mistake during debugging and it ended up in one of my commits.

[loshia]

For sure that will reduce overall cpu usage with 20-30% that is what i observe on my tplinks

[rallasnackbar]

Anyone knows what causes this error, running raspberry pi with newest version of cgminer, and mining with bi*fury's


cgminer version 4.0.1 - Started: [2014-03-07 13:45:35]
(5s):10.43G (avg):10.29Gh/s I A:35532 R:84 HW:1 WU:145.7/m ST: 59 SS: 0 MB: 27 LW: 113898 GF: 0 RF: 0
Connected to uk1.ghash.io diff 12 with stratum as user
Block: 44170d05... Diff:3.81G Started: [17:40:01] Best share: 26.4X
[USB device management [P]ool management [Settings [D]isplay options [Q]uit

0: BXF 0: 41.5C I 5.299G/5.245Gh/s I A:18084 R:36 HW:0 WU:74.0/m
1: BXF 1: 38.4C I 5.130[14433.599787] Unable to handle kernel paging request at uirtual address 20626f6a
[14433.608374] pgd = d9e58000
[14433.611216] [20626f6a] *pgd=000000007 Diff 15/12 BXF 1
[14433.615990] Internal error: Dops: 5 [111] PREEMPT ARM 1
[2014-03-07 17:41:22] Accepted 08cd5d8a Diff 29/12 BXF 1
Entering kdb (current=0xd9e68000, pid 233) Oops: (null) 0
due to pops @ Oxc00eabd4ccepted Obf0c68e Diff 21/12 BXF 1
[2014-03-07 17:41:32] Accepted 12c87979 Diff 14/12 BXF 0
2dCPU: 0 PID: 233 Comm: wicd-monitor Not tainted 3.10.32-1-ARCH #1
Eldtask: d9e68000 ti: d9dce000 task.ti: d9dce0004/12 BXF 1
PC is at kmalloc_track_caller+Ox6c/OxlcOiff 14/12 BXF 1
LR is at kmalloctrack_ca11er+Ox50/0x1c0iff 20/12 BXF 1
pc : [<c00eabd4>] lr : [<c00eabb8>1 psr: 20000013 1
sp : d9dcfc80 ip : 00069c9b fp : 00053b7cff 29/12 BXF 1
r10: d9dce000 r9 : cO4de2c8 r8 : d9dce000ff 12/12 BXF 1
r7 : 00000140 r6 : 000106d0 r5 : 20626f6a r4 : da801c00
r3 : 00000000 r2 : 00000001 rl : 000106d0 1.0 : 00000000
Flags: nzCu IRQs on Figs on Mode SVC_32 ISA ARM Segment user
Control: 00c5387d Table: 19e58008 DAC: 00000015/12 BXF 1
dCPU: 0 ND: 233 Comm: wicd-monitor Not tainted 3.10.32-1-ARCH #1
[<c0013428>] (unwind_backtrace+Ox0/0xec) from [<c00112d0>] (show_stack+0x10/0x14) [<c00112d0] (show_stack+Ox10/0x14) from [<c007fbfc>] (kdb_dumpregs+0x28/0x50) [<c007fbfc>] (kdb_dumpregs+0x28/0x50) from [<c0082cfc>] (kdb_main_loop+Ox370/0x6bc) [<c0082cfc>] (kdb_main_loop+Ox370/0x6bc) from [<c00854c8>] (kdb_stub+0x164/0x380) more> =03-07 17:42:49] Accepted 113371b7 Diff 15/12 BXF 1
[2014-03-07 17:42:50] Accepted Oed5e5c0 Diff 17/12 BXF 1
[2014-03-07 17:42:57] Accepted Ocl2f819 Diff 21/12 BXF 0

Picture for better text. https://i.imgur.com/8muciXP.jpg

[-ck]

Anyone knows what causes this error, running raspberry pi with newest version of cgminer, and mining with bi*fury's

Code:

1: BXF 1: 38.4C I 5.130[14433.599787] Unable to handle kernel paging request at uirtual address 20626f6a
[14433.608374] pgd = d9e58000
[14433.611216] [20626f6a] *pgd=000000007 Diff 15/12 BXF 1
[14433.615990] Internal error: Dops: 5 [111] PREEMPT ARM 1
[2014-03-07 17:41:22] Accepted 08cd5d8a Diff 29/12 BXF 1
Entering kdb (current=0xd9e68000, pid 233) Oops: (null) 0
due to pops @ Oxc00eabd4ccepted Obf0c68e Diff 21/12 BXF 1
[2014-03-07 17:41:32] Accepted 12c87979 Diff 14/12 BXF 0
2dCPU: 0 PID: 233 Comm: wicd-monitor Not tainted 3.10.32-1-ARCH #1
Eldtask: d9e68000 ti: d9dce000 task.ti: d9dce0004/12 BXF 1
PC is at kmalloc_track_caller+Ox6c/OxlcOiff 14/12 BXF 1
LR is at kmalloctrack_ca11er+Ox50/0x1c0iff 20/12 BXF 1
pc : [<c00eabd4>] lr : [<c00eabb8>1 psr: 20000013 1
sp : d9dcfc80 ip : 00069c9b fp : 00053b7cff 29/12 BXF 1
r10: d9dce000 r9 : cO4de2c8 r8 : d9dce000ff 12/12 BXF 1
r7 : 00000140 r6 : 000106d0 r5 : 20626f6a r4 : da801c00
r3 : 00000000 r2 : 00000001 rl : 000106d0 1.0 : 00000000
Flags: nzCu IRQs on Figs on Mode SVC_32 ISA ARM Segment user
Control: 00c5387d Table: 19e58008 DAC: 00000015/12 BXF 1
dCPU: 0 ND: 233 Comm: wicd-monitor Not tainted 3.10.32-1-ARCH #1
[<c0013428>] (unwind_backtrace+Ox0/0xec) from [<c00112d0>] (show_stack+0x10/0x14) [<c00112d0] (show_stack+Ox10/0x14) from [<c007fbfc>] (kdb_dumpregs+0x28/0x50) [<c007fbfc>] (kdb_dumpregs+0x28/0x50) from [<c0082cfc>] (kdb_main_loop+Ox370/0x6bc) [<c0082cfc>] (kdb_main_loop+Ox370/0x6bc) from [<c00854c8>] (kdb_stub+0x164/0x380) more> =03-07 17:42:49] Accepted 113371b7 Diff 15/12 BXF 1

That is a linux kernel, aka operating system, crash message unrelated to the cgminer code but mixed in with the cgminer output. Only an operating system upgrade/downgrade/kernel package fix can make it better.