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

os2sam

legendary

Activity: 3586

Merit: 1099

Think for yourself

Quote from: Schland on May 31, 2013, 08:13:12 AM

Does anyone have the link to the CGmimer fine tuning settings for mining BTC? I used the search but could not find it. It's the one around thread concurrency, shaders, worksizes and their factors.

I used this, two years ago.

https://en.bitcoin.it/wiki/Mining_hardware_comparison

bitpop

legendary

Activity: 2912

Merit: 1060

I dont get it. What the hell could they be for then? LTC?
What you're looking for is going to be ages old when gpu mining first started. Search for those keywords and settings vs "guide"

Quote from: Schland on May 31, 2013, 10:35:41 AM

Quote from: os2sam on May 31, 2013, 08:41:04 AM

Quote from: Schland on May 31, 2013, 08:13:12 AM

settings for mining BTC? ... thread concurrency, shaders, ...

Those aren't settings for BTC mining.

Thanks for trying to help, anyone else?

Schland

newbie

Activity: 19

Merit: 0

Quote from: os2sam on May 31, 2013, 08:41:04 AM

Quote from: Schland on May 31, 2013, 08:13:12 AM

settings for mining BTC? ... thread concurrency, shaders, ...

Those aren't settings for BTC mining.

Thanks for trying to help, anyone else?

bitpop

legendary

Activity: 2912

Merit: 1060

I reported USB 3 issues, but it was mostly when using more than a few devices. 1-2 should work fine. But usb 3 is unreliable at this time. Especially with things like mobo drivers trying to add stupid shit like UASP and USB SCSI.

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

... and yes this is all Windows ... just in case anyone else was wondering.

Linux should hopefully be rock solid.

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: arklan on May 31, 2013, 10:07:39 AM

did i correctly see that cgminer doesn't like usb 3.0 hubs?

if so, that is likely the explination why, when i just sucessfully installed the winusb driver, it gave no errors, but ALSO said no devices found.

wait, no... cause if that was the case it wouldn't find them ever, regardless of driver...

argh.

No, someone did report a problem with USB 3.0 once before
It may indeed be, that this is causing your problem also.
OK USB 3.0 also now added to the top of the todo list also.

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: bitpop on May 31, 2013, 09:34:49 AM

crap got another after restarting
http://screencast.com/t/8K88aK1xwNky
I guess i have to only watch the ghs. But i still dont trust it was hotplugged
and no i didnt unplug them.

Yes windows seems to sometimes get an error that on linux means to drop the device.
On windows it may just mean I need to reinitialise it.
It's at the top of the todo list now.

Anyway once it does drop the device (ZOMBIE), hotplug will pick it up again within 5 seconds.
You can see in the API ... the number of devices will grow by 1 each time this happens (and also each time, a new ZOMBIE will appear with nodev = true)
The ZOMBIE name comes from the fact that I will (soon?) come up with a way to map the hotplug devices back onto the old matching ZOMBIE device ... and revive it ... it's not completely dead yet

Anyway, this is all display related, the total hashing power should still be the same with a small loss per device (of between 0 and 5 seconds) each time one goes ZOMBIE and then hotplugs.
The 'going ZOMBIE' process is immediate - no delay at all, as soon as a short list of errors occurs, it a slam dunk on the head, ZOMBIE straight away.
If I work out a tidy way to revive it before giving up on it, the only gain will be the time from ZOMBIE to hotplug that is currently lost.
It will simply be the underlying usbutils code that makes the ZOMBIE flag, intercepting the ZOMBIE happening and trying to revive it before giving up on it.

arklan

legendary

Activity: 1778

Merit: 1008

did i correctly see that cgminer doesn't like usb 3.0 hubs?

if so, that is likely the explination why, when i just sucessfully installed the winusb driver, it gave no errors, but ALSO said no devices found.

wait, no... cause if that was the case it wouldn't find them ever, regardless of driver...

argh.

arklan

legendary

Activity: 1778

Merit: 1008

Quote from: kano on May 31, 2013, 09:57:10 AM

Quote from: arklan on May 31, 2013, 09:48:58 AM

Quote from: bitpop on May 31, 2013, 09:37:54 AM

go through each device on zadig ensuring its on winusb

did that. they are. also followed the steps here:
https://bitcointalksearch.org/topic/how-to-use-asicminer-block-erupters-with-cgminer-on-windows-7-220450

everything has a comport. after following those steps (including a reboot) bfgminer's working again, but cgminer remains with the same error.

That page is for the old serial-USB driver for 3.1.1 and before.

For 3.2.0 (and later) you need to use the WinUSB driver as I mentioned above.

i now see that zadig did infact... not do it's job. it's running now, as admin. waiting on completion.

thanks for the help. i feel like an idiot.

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: arklan on May 31, 2013, 09:48:58 AM

Quote from: bitpop on May 31, 2013, 09:37:54 AM

go through each device on zadig ensuring its on winusb

did that. they are. also followed the steps here:
https://bitcointalksearch.org/topic/how-to-use-asicminer-block-erupters-with-cgminer-on-windows-7-220450

everything has a comport. after following those steps (including a reboot) bfgminer's working again, but cgminer remains with the same error.

That page is for the old serial-USB driver for 3.1.1 and before.

For 3.2.0 (and later) you need to use the WinUSB driver as I mentioned above.

Xialla

legendary

Activity: 1036

Merit: 1001

/dev/null

haah, next reason, why I'm not using windows at all. to much complicated for me.)

on linux (debian) works all like a charm, I just need to install:

sudo apt-get install libusb-1.0-0-dev and remove timing option and -S /dev/ttyUSBXXX

thanks guys for great work

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: arklan on May 31, 2013, 09:16:01 AM

call me an idiot, but i still can't get this working. i downloaded the latest cgminer, used zadig to change to winusb... but for the life of me i can't figure out how to remove the ftdi driver.

getting these messages:
[2013-05-31 08:16:34] USB init, open device failed, err -12, you need to install a Windows USB driver for - AMU device 2:11
[2013-05-31 08:16:34] Icarus detect (2:11) failed to initialise (incorrect device?)

That error means exactly what it says:
"you need to install a Windows USB driver for"

It means that zadig hasn't set the driver to WinUSB (or you didn't)
As per FPGA-README, you need to run zadig as administrator,
use the Menu: Options -> List All Devices
then set the device drivers to WinUSB

arklan

legendary

Activity: 1778

Merit: 1008

Quote from: bitpop on May 31, 2013, 09:37:54 AM

go through each device on zadig ensuring its on winusb

did that. they are. also followed the steps here:
https://bitcointalksearch.org/topic/how-to-use-asicminer-block-erupters-with-cgminer-on-windows-7-220450

everything has a comport. after following those steps (including a reboot) bfgminer's working again, but cgminer remains with the same error.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: bitpop on May 31, 2013, 09:34:49 AM

crap got another after restarting
http://screencast.com/t/8K88aK1xwNky
I guess i have to only watch the ghs. But i still dont trust it was hotplugged
and no i didnt unplug them.

Well it is a major code update so we knew there might be problems, and windows was always going to be an issue (when isn't it?). We're probably too trigger happy at calling usb errors as being the same as disconnecting it. For now you might be more comfortable running the display in compact mode so you don't see it unplugging and hotplugging them every so often...

bitpop

legendary

Activity: 2912

Merit: 1060

go through each device on zadig ensuring its on winusb

arklan

legendary

Activity: 1778

Merit: 1008

Quote from: bitpop on May 31, 2013, 09:33:10 AM

check your mhs, they dont always display all devices right now

Quote from: arklan on May 31, 2013, 09:31:27 AM

i THINK the drivers were replaced sucessfully, but cgminer's still throwing the same message.

and now bfgminer doesn't work either - which makes me think two things: oh god i broke it, or yea, the driver is installed.

except bfgminer DOES recognize one of them... which makes no sense to me...

cgminer isn't displaying ANY devices, and the green LED on the sticks isn't doing the usual blinky-when-found-a-share thing. it's just solid green.

bitpop

legendary

Activity: 2912

Merit: 1060

crap got another after restarting
http://screencast.com/t/8K88aK1xwNky
I guess i have to only watch the ghs. But i still dont trust it was hotplugged
and no i didnt unplug them.

bitpop

legendary

Activity: 2912

Merit: 1060

check your mhs, they dont always display all devices right now

Quote from: arklan on May 31, 2013, 09:31:27 AM

i THINK the drivers were replaced sucessfully, but cgminer's still throwing the same message.

and now bfgminer doesn't work either - which makes me think two things: oh god i broke it, or yea, the driver is installed.

except bfgminer DOES recognize one of them... which makes no sense to me...

arklan

legendary

Activity: 1778

Merit: 1008

i THINK the drivers were replaced sucessfully, but cgminer's still throwing the same message.

and now bfgminer doesn't work either - which makes me think two things: oh god i broke it, or yea, the driver is installed.

except bfgminer DOES recognize one of them... which makes no sense to me...

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: bitpop on May 31, 2013, 09:20:53 AM

Weird I got a BLT 18 ZOMBIE
http://screencast.com/t/F7DSaeslTtVg

A zombie happens when a device is unplugged. However I suspect you didn't actually unplug it based on your surprise? When you hotplug one in, it unfortunately does not appear in the list at the top since that window is (currently) rigidly set at startup. Your average hashrate of 8GH suggests that all 20 are still working so it looks like for whatever reason BLT 18 got unplugged and then hotplugged itself back again. So not sure why it happened here.

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