OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 307.

The00Dustin

hero member

Activity: 807

Merit: 500

Quote from: Lucko on June 07, 2013, 12:07:05 PM

Whatever... I figure it out but I don't know why this works... I have changed difficulty from 2 to 8 and now I can set intensity to whatever I like. And I got back missing 150MH by seting cards to 10 and 12. So I'm on full speed now. I know it is not the internet since I have tested the cards on another computer before installing it and they worked... I still think it is a bug...

EDIT: So that much about getting slower over 8...

Sounds like the CPU (or 100% CPU utilization AMD driver bug) is your bottleneck and not the bus. If you have a dual core or hyperthreading, 50% CPU = 100% CPU Utilization because cgminer is single-threaded. I apologize if that last (italicized) statement isn't true, because I don't know it to be fact from reviewing any code. To clarify, I haven't run cgminer in Windows in a long time, but when I did, it seemed to be the case (it might be something else related to the drivers that is single threaded). Regardless, the point is that by increasing the difficulty, you reduced the number of shares that cgminer had to use the processor to validate, allowing more processor time to generate and distribute work. That having been said, if cgminer is still using 50% CPU, that is still wasting a lot of electricity and may not be worth the additional 150MH/s and/or the additional variance the higher difficulty will bring.

Trongersoll

hero member

Activity: 490

Merit: 501

Quote from: Lucko on June 07, 2013, 12:36:33 PM

Quote from: Trongersoll on June 07, 2013, 12:34:00 PM

Is there any performance benefits to 3.2.1 over 3.1.1? yeah, i know ya changed how the drivers work, but i'm wondering if i really need to upgrade a dedicated rig with ASICminers and one small GPU since i currently have 3.1.1 working. I'm kind of thinking "if it ain't broke, doen't fix it.".

It spouse to be less HW errors... So yes...

Ok, thanks. i'm not seeing many hardware errors, maybe 1 per 15 minutes, if that.

Lucko

hero member

Activity: 826

Merit: 1000

Quote from: Trongersoll on June 07, 2013, 12:34:00 PM

Is there any performance benefits to 3.2.1 over 3.1.1? yeah, i know ya changed how the drivers work, but i'm wondering if i really need to upgrade a dedicated rig with ASICminers and one small GPU since i currently have 3.1.1 working. I'm kind of thinking "if it ain't broke, doen't fix it.".

It spouse to be less HW errors and CPU usage... So yes... More shares and less power consumption...

Trongersoll

hero member

Activity: 490

Merit: 501

Is there any performance benefits to 3.2.1 over 3.1.1? yeah, i know ya changed how the drivers work, but i'm wondering if i really need to upgrade a dedicated rig with ASICminers and one small GPU since i currently have 3.1.1 working. I'm kind of thinking "if it ain't broke, doen't fix it.".

Naelr

full member

Activity: 231

Merit: 100

I am running Ubuntu 12.04 LTS.... Have 1 GPU, 1 BFL single fpga and 8 Block Erupters plugged into this machine.

Using cgminer 64 bit 3.2.1 the block erupters keep going zombie, after about an hour I have 21 zombies.. the good thing is they keep getting reset and keep right on hashing... but this can't be a good thing.... Kano, should I get and try your patch 3.2.1a? can I help add some more info....

The BLF and the GPU are fine and stable.

Naelr

Lucko

hero member

Activity: 826

Merit: 1000

Quote from: The00Dustin on June 07, 2013, 09:14:56 AM

Quote from: Lucko on June 03, 2013, 04:47:57 AM

This happened when I added 5970 and 5770 to my miner. With only 5 cores I didn't have problems. But I do have a mix of cards if that might be a problem. 6790, 6870, 5850, 2x5970, 5770. Running 2.11.4, but the same problem is on 3.2.0(3.x has problems with my pool. I get disconnected all the time).

Quote from: The00Dustin on June 07, 2013, 06:04:38 AM

You've been told not to use -I 9 or higher for sha256 mining like 3 times now. Don't do it. When you decide to scrypt mine, which you seemed to imply you would at some point, you can try again, the -I levels are totally different for scrypt.

-I 9 is included in "-I 9 or higher". Run at -I 8. None of the cards in your original quote start with a 7 and I'm pretty sure there has been much discussion (again, 2 or 3 hundred pages ago [and again, this may be an especially on Windows situation]) about -I 9 or higher only being useful for 7xxx cards. Running at too high of an intensity will cause the cards to go slower, which is what you are experiencing. I don't know how to test the bus, but I don't think you need to worry about testing the bus. If you were running at higher than -I 8 before, and nothing changed but an additional card on the bus, that seems like a pretty good test/indicator that the bus is overloaded. If anything else changed at the same time, then you can troubleshoot what else changed by trying to change it back and/or starting from scratch. If you were running a higher intensity on a different program before, then the numbers don't necessarily mean the same thing on a different program.

Whatever... I figure it out but I don't know why this works... I have changed difficulty from 2 to 8 and now I can set intensity to whatever I like. And I got back missing 150MH by seting cards to 10 and 12. So I'm on full speed now. I know it is not the internet since I have tested the cards on another computer before installing it and they worked... I still think it is a bug...

EDIT: So that much about getting slower over 8...

turtle83

sr. member

Activity: 322

Merit: 250

Supersonic

Quote from: ewibit on June 07, 2013, 10:00:49 AM

Quote from: Dunkelheit667 on June 07, 2013, 09:10:57 AM

First of all, thank you for taking care!

And here you go. Good news, my AMUs were detected on the rpi. Bad news, declared sick after 60 seconds hashing:

Code:

[2013-06-07 15:56:49] AMU1: Idle for more than 60 seconds, declaring SICK!
 [2013-06-07 15:56:49] AMU1: Attempting to restart
 [2013-06-07 15:57:05] AMU0: Idle for more than 60 seconds, declaring SICK!
 [2013-06-07 15:57:05] AMU0: Attempting to restart
 [2013-06-07 15:57:32] AMU2: invalid nonce - HW error
 [2013-06-07 15:57:37] Accepted c3f18eac Diff 1/1 AMU 2
 [2013-06-07 15:57:42] AMU2: invalid nonce - HW error
 [2013-06-07 15:58:06] Stratum from pool 0 detected new block
 [2013-06-07 15:58:19] AMU0: Idle for more than 60 seconds, declaring SICK!
 [2013-06-07 15:58:19] AMU0: Attempting to restart
 [2013-06-07 15:58:19] AMU1: Idle for more than 60 seconds, declaring SICK!
 [2013-06-07 15:58:19] AMU1: Attempting to restart

same here...

Same issue with Ubintu. downgraded to 3.1.1 again.

sLide.

full member

Activity: 170

Merit: 100

Quote from: sLide. on June 06, 2013, 09:48:45 PM

Quote from: Lucko on June 06, 2013, 07:55:50 PM

Quote from: sLide. on June 06, 2013, 07:53:45 PM

I'm experiencing a issue with CGminer.

I recently moved my XFX 6870 from my gaming machine which was used to mine when I wasn't gaming to my first rig. I keep getting error's from windows saying it had to stop the program from running.

MoBo: msi x58A-GD45
Proc: I7 920
Memory : 2GB
Video Card: 6870 XFX HD - CCC Version - 13.4 Direct3D Version 9.14.10.0969

Not entirely sure what the problem could be. I've tried running as admin. Any help? Thanks!

I had same problem with incompatible OpenCL driver combination... Changing it might help

In event log, I'm getting this error -

- System

- Provider

[ Name] Application Error

- EventID 1000

[ Qualifiers] 0

Level 2

Task 100

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2013-06-07T14:03:10.000000000Z

EventRecordID 1752

Channel Application

Computer Miner1-PC

Security

- EventData

cgminer.exe
0.0.0.0
518e20db
cgminer.exe
0.0.0.0
518e20db
c0000005
000265be
12a0
01ce6387bbccda57
C:\Users\Miner1\Desktop\cgminer\cgminer-3.1.1-windows\cgminer.exe
C:\Users\Miner1\Desktop\cgminer\cgminer-3.1.1-windows\cgminer.exe
fc31de57-cf7a-11e2-8d68-6c626de9cc51

Any help on this. Google is saying that some of these error's happen when the Proc trys to access "No-Mans Land" in the memory. It's pretty much a dump spot. Any advice?

ewibit

legendary

Activity: 2955

Merit: 1049

Quote from: Dunkelheit667 on June 07, 2013, 09:10:57 AM

First of all, thank you for taking care!

And here you go. Good news, my AMUs were detected on the rpi. Bad news, declared sick after 60 seconds hashing:

Code:

[2013-06-07 15:56:49] AMU1: Idle for more than 60 seconds, declaring SICK!
 [2013-06-07 15:56:49] AMU1: Attempting to restart
 [2013-06-07 15:57:05] AMU0: Idle for more than 60 seconds, declaring SICK!
 [2013-06-07 15:57:05] AMU0: Attempting to restart
 [2013-06-07 15:57:32] AMU2: invalid nonce - HW error
 [2013-06-07 15:57:37] Accepted c3f18eac Diff 1/1 AMU 2
 [2013-06-07 15:57:42] AMU2: invalid nonce - HW error
 [2013-06-07 15:58:06] Stratum from pool 0 detected new block
 [2013-06-07 15:58:19] AMU0: Idle for more than 60 seconds, declaring SICK!
 [2013-06-07 15:58:19] AMU0: Attempting to restart
 [2013-06-07 15:58:19] AMU1: Idle for more than 60 seconds, declaring SICK!
 [2013-06-07 15:58:19] AMU1: Attempting to restart

same here...

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: pengoau on June 07, 2013, 09:53:11 AM

Quote from: -ck on June 07, 2013, 05:27:25 AM

Quote from: pengoau on June 07, 2013, 05:23:14 AM

hey guys

I have 3 gpus in my system 1 apu and 2 dedicated gpus, how can i startup cgminer with the third gpu (gpu 2) turned off? I tried setting intensity to 0 but that doesn't work.

Do I specify it via the -d switch? If so what is the syntax?

Thanks

-d 0-1 --remove-disabled

I added that to my bat file and i get "invalid device number"

fyi:
GPU 0 = 6950
GPU 1 = 5770
GPU 2 = APU

Thanks for your help

What is the output of 'cgminer -n' ?

pengoau

full member

Activity: 208

Merit: 100

Quote from: -ck on June 07, 2013, 05:27:25 AM

Quote from: pengoau on June 07, 2013, 05:23:14 AM

hey guys

I have 3 gpus in my system 1 apu and 2 dedicated gpus, how can i startup cgminer with the third gpu (gpu 2) turned off? I tried setting intensity to 0 but that doesn't work.

Do I specify it via the -d switch? If so what is the syntax?

Thanks

-d 0-1 --remove-disabled

I added that to my bat file and i get "invalid device number"

fyi:
GPU 0 = 6950
GPU 1 = 5770
GPU 2 = APU

Thanks for your help

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: FiatKiller on June 07, 2013, 09:50:39 AM

Thanks, and no one is reporting issues running the normal usb devices(keyboard, mouse, printers, etc.) using the zadig driver? Planning on running them on my main desktop, so I don't want any problems with normal activities. :-D

Zadig is a tool to associate your choice of driver with the device you want, it is not a driver. Only associate WinUSB with the mining device and don't touch any other USB devices...

FiatKiller

sr. member

Activity: 378

Merit: 250

Thanks, and no one is reporting issues running the normal usb devices(keyboard, mouse, printers, etc.) using the zadig driver? Planning on running them on my main desktop, so I don't want any problems with normal activities. :-D

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: FiatKiller on June 07, 2013, 09:42:01 AM

Quote from: kano on June 07, 2013, 09:05:43 AM

Quote from: FiatKiller on June 07, 2013, 09:03:07 AM

I should be getting some eruptors next week. Are you saying with 3.2.1, I don't
need any special USB drivers or settings? I know things are constantly in flux
with these new devices...

thanks

On linux, nothing to do, just plug them in and run 3.2.1

On windows, you need to install the WinUSB driver with Zadig, not the default windows driver, then run 3.2.1

What do you think about using the VCP driver mentioned here: (works with 3.1.1)

http://rdmsnippets.com/tag/block-erupter-usb/

That is using the now-defunct serial interface which cgminer 3.2+ no longer uses, much like the ftdi_sio driver did. We use direct USB code.

twmz

hero member

Activity: 737

Merit: 500

Quote from: kano on June 07, 2013, 06:03:07 AM

...
Though I will add, anyone who has a few of them and uses them could they report how it's going?
Thanks.
...

I only have one, but it is working fine with 3.2.1 on linux. Showing up as AMU 0 and hashing normally. The very first time I launched 3.2.1, it didn't show up right away and then appeared 10 seconds later as a hotplug device even though it had been plugged in all along. I assume this was just from the delay in the device getting fully initialized. If I quit and restart cgminer, it appears right away from then on.

So, no problems yet (and I don't have the SICK problem reported by Dunkelheit667).

FiatKiller

sr. member

Activity: 378

Merit: 250

Quote from: kano on June 07, 2013, 09:05:43 AM

Quote from: FiatKiller on June 07, 2013, 09:03:07 AM

I should be getting some eruptors next week. Are you saying with 3.2.1, I don't
need any special USB drivers or settings? I know things are constantly in flux
with these new devices...

thanks

On linux, nothing to do, just plug them in and run 3.2.1

On windows, you need to install the WinUSB driver with Zadig, not the default windows driver, then run 3.2.1

What do you think about using the VCP driver mentioned here: (works with 3.1.1)

http://rdmsnippets.com/tag/block-erupter-usb/

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

Quote from: Dunkelheit667 on June 07, 2013, 09:10:57 AM

Quote from: kano on June 07, 2013, 06:03:07 AM

...
Though I will add, anyone who has a few of them and uses them could they report how it's going?
Thanks.
...

First of all, thank you for taking care!

And here you go. Good news, my AMUs were detected on the rpi. Bad news, declared sick after 60 seconds hashing:

...

Hmm - OK I'll try the AMU on my RPi, I've not plugged it into that due to it needing power.
I've run the Jalapeno, BFL FPGA and BLT (Black Arrow Lancelot) without any trouble at all so far.
Though I have heard of issues in general due to power making it back to the RPi from a powered hub.
I'll see how mine goes ... yep seeing that happen here also.
OK time to track down what's happening.

The00Dustin

hero member

Activity: 807

Merit: 500

Quote from: Lucko on June 03, 2013, 04:47:57 AM

This happened when I added 5970 and 5770 to my miner. With only 5 cores I didn't have problems. But I do have a mix of cards if that might be a problem. 6790, 6870, 5850, 2x5970, 5770. Running 2.11.4, but the same problem is on 3.2.0(3.x has problems with my pool. I get disconnected all the time).

Quote from: The00Dustin on June 07, 2013, 06:04:38 AM

You've been told not to use -I 9 or higher for sha256 mining like 3 times now. Don't do it. When you decide to scrypt mine, which you seemed to imply you would at some point, you can try again, the -I levels are totally different for scrypt.

-I 9 is included in "-I 9 or higher". Run at -I 8. None of the cards in your original quote start with a 7 and I'm pretty sure there has been much discussion (again, 2 or 3 hundred pages ago [and again, this may be an especially on Windows situation]) about -I 9 or higher only being useful for 7xxx cards. Running at too high of an intensity will cause the cards to go slower, which is what you are experiencing. I don't know how to test the bus, but I don't think you need to worry about testing the bus. If you were running at higher than -I 8 before, and nothing changed but an additional card on the bus, that seems like a pretty good test/indicator that the bus is overloaded. If anything else changed at the same time, then you can troubleshoot what else changed by trying to change it back and/or starting from scratch. If you were running a higher intensity on a different program before, then the numbers don't necessarily mean the same thing on a different program.

Dunkelheit667

legendary

Activity: 1045

Merit: 1157

no degradation

Quote from: kano on June 07, 2013, 06:03:07 AM

...
Though I will add, anyone who has a few of them and uses them could they report how it's going?
Thanks.
...

First of all, thank you for taking care!

And here you go. Good news, my AMUs were detected on the rpi. Bad news, declared sick after 60 seconds hashing:

Code:

 AMU 0:                | SICK  /7.402Mh/s | A:1 R:0 HW:0 U: 0.62/m
 AMU 1:                | SICK  / 0.000h/s | A:0 R:0 HW:0 U: 0.00/m
 AMU 2:                | 296.8M/130.5Mh/s | A:5 R:0 HW:0 U: 3.11/m <- got SICK two seconds later
 BLT 0:                | 388.6M/365.3Mh/s | A:4 R:0 HW:0 U: 2.49/m
 AMU 3:                | SICK  / 0.000h/s | A:0 R:0 HW:0 U: 0.00/m

And this happend unplugging and plugging them back:

Code:

 BLT 0:                | 396.0M/380.6Mh/s | A:26 R:0 HW:0 U: 6.64/m
 AMU 4:                | SICK  /2.484Mh/s | A: 1 R:0 HW:0 U: 0.26/m
 AMU 5:                | SICK  /19.96Mh/s | A: 3 R:0 HW:0 U: 0.77/m
 AMU 6:                | SICK  /36.54Mh/s | A: 4 R:0 HW:0 U: 1.02/m
 AMU 7:                | SICK  / 0.000h/s | A: 0 R:0 HW:0 U: 0.00/m
 AMU 0:                | ZOMBIE/41.13Mh/s | A: 3 R:0 HW:0 U: 0.77/m
 AMU 1:                | ZOMBIE/26.55Mh/s | A: 3 R:0 HW:0 U: 0.77/m
 AMU 2:                | ZOMBIE/ 0.000h/s | A: 0 R:0 HW:0 U: 0.00/m
 AMU 3:                | ZOMBIE/18.95Mh/s | A: 2 R:0 HW:0 U: 0.51/m

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

Quote from: FiatKiller on June 07, 2013, 09:03:07 AM

I should be getting some eruptors next week. Are you saying with 3.2.1, I don't
need any special USB drivers or settings? I know things are constantly in flux
with these new devices...

thanks

On linux, nothing to do, just plug them in and run 3.2.1

On windows, you need to install the WinUSB driver with Zadig, not the default windows driver, then run 3.2.1

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