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

Beastlymac

hero member

Activity: 630

Merit: 501

Miner Setup And Reviews. WASP Rep.

Quote from: -ck on October 02, 2013, 10:14:25 AM

Quote from: Beastlymac on October 02, 2013, 10:09:19 AM

3.5.0 on raspbian wheezy. Crashed. Any ideas on what I can do to fix it?

Eh, but that's a kernel crash, not a cgminer crash... and while I am a kernel developer, I had nothing to do with this one Tongue

Kernel upgrade, either the package provided for raspbian, or migrating to another distribution is the only way unless you want to help the raspbian maintainers debug this crash.

Ok I will give upgrading a shot. Thanks.
Edit: updated everything so lets se how it goes...

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: Beastlymac on October 02, 2013, 10:09:19 AM

3.5.0 on raspbian wheezy. Crashed. Any ideas on what I can do to fix it?

Eh, but that's a kernel crash, not a cgminer crash... and while I am a kernel developer, I had nothing to do with this one Tongue

Kernel upgrade, either the package provided for raspbian, or migrating to another distribution is the only way unless you want to help the raspbian maintainers debug this crash.

Beastlymac

hero member

Activity: 630

Merit: 501

Miner Setup And Reviews. WASP Rep.

3.5.0 on raspbian wheezy. Crashed. Any ideas on what I can do to fix it?

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: Rant2112 on October 02, 2013, 10:05:30 AM

Quote from: -ck on October 01, 2013, 04:08:31 PM

If you know how to build from git, can you try building the latest libusbx branch and see if it helps?

Do I need to put the libusbx code in the cgminer libusb directory? Is that still there or can I just install the latest libusbx and then build cgminer?

It's called the libusbx branch because the libusb included in there is the latest libusbx version. You don't need to do anything different than a regular git compile (i.e. you only need ./autogen.sh in addition to a normal build procedure).

Rant2112

newbie

Activity: 70

Merit: 0

Quote from: -ck on October 01, 2013, 04:08:31 PM

Quote from: Rant2112 on October 01, 2013, 10:32:55 AM

I'm still having trouble getting my Block Erupter to work on anything besides 3.1.1

With 3.5.0 I get:

AMU0: TIMEOUT GetResults took 659ms but was 100ms
...
AMU0: TIMEOUT GetResults took 659ms but was 100ms

AMU0: Comms error (werr=-7 amt=0)
...
AMU0: Comms error (werr=-7 amt=0)

I think this is a known problem but posting just to be sure. I'll continue to use 3.1.1 as it is working fine. Cool

FYI - I'm mining using a recent Ubuntu release running under VMWare Fusion on a Mac. The Block Erupter is plugged into a USB2 D-Link HUB. It is connected to a 'high speed' USB port on the Mac which should mean it is USB2.

If you know how to build from git, can you try building the latest libusbx branch and see if it helps?

Do I need to put the libusbx code in the cgminer libusb directory? Is that still there or can I just install the latest libusbx and then build cgminer?

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: zamot on October 02, 2013, 01:02:42 AM

Quote from: -ck on October 01, 2013, 08:20:23 PM

Youch. That does not spell good news since I can't even imagine what other libusb feature is not supported. While it won't make it any better, could you start it with the following extra parameters:
-D -T 2>log.txt
and then stop it after a minute or so and see what's in the log.txt file?

EDIT: I mean trying it with that new executable of course.

I made the log file. It was running for about 2 minutes.
Log file can be found here.

Thanks very much for doing that. That was all working fine there... I was trying to figure out what happens when you have a problem and it doesn't appear to have had a problem in that time?

zamot

member

Activity: 122

Merit: 10

Quote from: -ck on October 01, 2013, 08:20:23 PM

Youch. That does not spell good news since I can't even imagine what other libusb feature is not supported. While it won't make it any better, could you start it with the following extra parameters:
-D -T 2>log.txt
and then stop it after a minute or so and see what's in the log.txt file?

EDIT: I mean trying it with that new executable of course.

I made the log file. It was running for about 2 minutes.
Log file can be found here.

Askit2

hero member

Activity: 981

Merit: 500

DIV - Your "Virtual Life" Secured and Decentralize

Quote from: CrazyGuy on October 01, 2013, 01:28:45 AM

This was a move from 3.4 to 3.5 for me and I had to install the libudev-devel package to get cgminer to compile again. Perhaps there's an issue with the centos implementation of libudev-devel.

Thank You!
You pointed out why I was having seg faults. It doesn't fix it per se but I can at least run the current version. I wish I would have seen this info before I messed up my building.

Since I stopped limiting my usb devices and only am running one instance I am able to run 3.5.0. I could start the limited ones first and just catch the remainder with the new version but I really want to see if it locks up using quotas.

EDIT: am running a log file now on Raspberry pi as I can't seem to get the monitor to stop shutting off. When I can see it dying it is always one instance first, then the second then a while later the third. Printed on TOP is failure to read from swap. I assume it is caching some data in a swap file cgminer or some system process I am unsure. TOP only shows before things go horribly wrong 0 virtual memory use, but if I run X I can use task manager and it shows some Virtual memory use. The previous data is from 3.4.3 and before nothing on 3.5.0 yet.

It seems to me like (as a windows user mostly) if I am using virtual memory there should be data in the swap file. But the two different tools seem to have conflicting data to me. I am sure that there is something I am missing.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: zamot on October 01, 2013, 04:45:49 PM

Quote from: -ck on October 01, 2013, 03:58:52 PM

Quote from: zamot on October 01, 2013, 10:40:07 AM

So, i tried with cgminer-nogpu.exe from ( http://ck.kolivas.org/apps/cgminer/temp/cgminer-nogpu.exe ) and i got this :
[2013-10-01 11:36:13] Started cgminer 3.5.0 [2013-10-01 11:36:13] Loaded configuration file cgminer.conf [2013-10-01 11:36:14] AMU 0 usb write error: LIBUSB_ERROR_NOT_SUPPORTED
This was try with just one BE. Cry

Ok, try redownloading again please (remember I don't have this hardware/OS combination to test for myself).

I made test with newly downloaded ( http://ck.kolivas.org/apps/cgminer/temp/cgminer-nogpu.exe ) and the result was:
- Timeout message after 10-15 seconds
- after a while there was also an write error: LIBUSB_ERROR_NOT_SUPPORTED
- cgminer only recognized 4 BE's ( even if they were added one by one )

If you have any other idea i willing to try and to report is this issue is solved.

Youch. That does not spell good news since I can't even imagine what other libusb feature is not supported. While it won't make it any better, could you start it with the following extra parameters:
-D -T 2>log.txt
and then stop it after a minute or so and see what's in the log.txt file?

EDIT: I mean trying it with that new executable of course.

zamot

member

Activity: 122

Merit: 10

Quote from: techman05 on October 01, 2013, 04:49:30 PM

If it wasn't for the fact you had 25 of these I'd think to uninstall the drivers and re install them but if its like my pc it will grump at every one of them. You are using a new folder with the new install right?

I expand reset the shortcut and point to my config file in the new folder.

I can't imagine how much might have changed between 3.3 and 3.5 . It just keep things cleaner to start a new folder with all the nooks that came with it.

CKOlivias too bad you can't just remote connect since windows xp had a token to send out to share your desktop with I thought.

Yeah, i done this all before but it doesn't helped. Bad luck ...

techman05

hero member

Activity: 546

Merit: 500

If it wasn't for the fact you had 25 of these I'd think to uninstall the drivers and re install them but if its like my pc it will grump at every one of them. You are using a new folder with the new install right?

I expand reset the shortcut and point to my config file in the new folder.

I can't imagine how much might have changed between 3.3 and 3.5 . It just keep things cleaner to start a new folder with all the nooks that came with it.

CKOlivias too bad you can't just remote connect since windows xp had a token to send out to share your desktop with I thought.

zamot

member

Activity: 122

Merit: 10

Quote from: -ck on October 01, 2013, 03:58:52 PM

Quote from: zamot on October 01, 2013, 10:40:07 AM

So, i tried with cgminer-nogpu.exe from ( http://ck.kolivas.org/apps/cgminer/temp/cgminer-nogpu.exe ) and i got this :
[2013-10-01 11:36:13] Started cgminer 3.5.0 [2013-10-01 11:36:13] Loaded configuration file cgminer.conf [2013-10-01 11:36:14] AMU 0 usb write error: LIBUSB_ERROR_NOT_SUPPORTED
This was try with just one BE. Cry

Ok, try redownloading again please (remember I don't have this hardware/OS combination to test for myself).

I made test with newly downloaded ( http://ck.kolivas.org/apps/cgminer/temp/cgminer-nogpu.exe ) and the result was:
- Timeout message after 10-15 seconds
- after a while there was also an write error: LIBUSB_ERROR_NOT_SUPPORTED
- cgminer only recognized 4 BE's ( even if they were added one by one )

If you have any other idea i willing to try and to report is this issue is solved.

I understand you, that you can not simulate every possible combination of HW/OS configuration.
Like i write before, cgminer 3.5.0 works and BE's make minig, but there are this timeout warnings. I will try to port ASAP to linux and then we will see if there will be some surprises or not.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: Rant2112 on October 01, 2013, 10:32:55 AM

I'm still having trouble getting my Block Erupter to work on anything besides 3.1.1

With 3.5.0 I get:

AMU0: TIMEOUT GetResults took 659ms but was 100ms
...
AMU0: TIMEOUT GetResults took 659ms but was 100ms

AMU0: Comms error (werr=-7 amt=0)
...
AMU0: Comms error (werr=-7 amt=0)

I think this is a known problem but posting just to be sure. I'll continue to use 3.1.1 as it is working fine. Cool

FYI - I'm mining using a recent Ubuntu release running under VMWare Fusion on a Mac. The Block Erupter is plugged into a USB2 D-Link HUB. It is connected to a 'high speed' USB port on the Mac which should mean it is USB2.

If you know how to build from git, can you try building the latest libusbx branch and see if it helps?

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: zamot on October 01, 2013, 10:40:07 AM

So, i tried with cgminer-nogpu.exe from ( http://ck.kolivas.org/apps/cgminer/temp/cgminer-nogpu.exe ) and i got this :
[2013-10-01 11:36:13] Started cgminer 3.5.0 [2013-10-01 11:36:13] Loaded configuration file cgminer.conf [2013-10-01 11:36:14] AMU 0 usb write error: LIBUSB_ERROR_NOT_SUPPORTED
This was try with just one BE. Cry

Ok, try redownloading again please (remember I don't have this hardware/OS combination to test for myself).

zamot

member

Activity: 122

Merit: 10

Quote from: techman05 on October 01, 2013, 12:15:21 PM

You have the right driver? WinUsb is what I'm using from the list of installable drivers for cgminer . Thats what I think the unsupported error is about.

If all your using your xp machine is for mining, kill it and install umbuntu or windows 7. Make ckolivias life alot easier fixing whats going on.

Yes, i am using WinUSB driver, and regular cgminer 3.5.0 recognize BE's and they are doing thei job, but there are tons of timeout messages which were not on cgminer 3.3.0 which i used before and in mean time ther ewas no change of drivers or something else.
And yes, i am doing to install an linux on one of laptops. Hope it will be dome till weekend Cheesy

PatMan

hero member

Activity: 924

Merit: 1000

Watch out for the "Neg-Rep-Dogie-Police".....

Xubuntu = YES!

~~winblows 7~~ = NO!

Cheesy

ADIT: ~~winblows 8/prism~~ = OH NONONONONO!!

techman05

hero member

Activity: 546

Merit: 500

You have the right driver? WinUsb is what I'm using from the list of installable drivers for cgminer . Thats what I think the unsupported error is about.

If all your using your xp machine is for mining, kill it and install umbuntu or windows 7. Make ckolivias life alot easier fixing whats going on.

zamot

member

Activity: 122

Merit: 10

Quote from: zamot on October 01, 2013, 12:33:58 AM

Quote from: -ck on September 30, 2013, 05:41:21 PM

Quote from: zamot on September 30, 2013, 10:54:52 AM

Hello,

i have the same problem with Timeout messages for all BE.
AMU1: TIMEOUT GetResults took 1531ms but was 100ms AMU0: TIMEOUT GetResults took 1531ms but was 100ms AMU3: TIMEOUT GetResults took 1531ms but was 100ms AMU2: TIMEOUT GetResults took 1531ms but was 100ms
Timeout variates from few 100ms to 2000ms or more. Angry

Till nowi used cgminer 3.3.0 and there was no problem, when i tried 3.4.0 and now currently 3.5.0 version i got this messagess.
I run cgminer in Windows XP SP2.
Zadig drivers are installed ( otherwise i couldn't run cgminer 3.3.0 ).
USB HUB has 3.5A max output, so there is no under power problem.
I also rebooted XP before i started cgminer 3.5.0.

A number of things potentially going on. We have problems with some usb implementations on certain OSs and the libusb library we use.

How long does it normally take before you see these errors and do all of them have it at the same time?

XP is a bit limited for USB. Try starting with just 2 BEs and increase it by one at a time (waiting long enough for the errors to normally appear) till you see the errors reappear.
If possible, try windows7 or ideally a linux to see if they go away.

This timeout messages appears randomly time based, but around 10 - 15 seconds after starting of cgminer. I tried with one BE and then i added one per one other BE's, but timeout appears with one attached BE also.
I will try with cgminer that you posted link with next post.
Unfortunaly i can not try directly on Windows 7, because i do not have all privileges to install something into.
the next ry ist with linux, but i must first install it.

So, i tried with cgminer-nogpu.exe from ( http://ck.kolivas.org/apps/cgminer/temp/cgminer-nogpu.exe ) and i got this :
[2013-10-01 11:36:13] Started cgminer 3.5.0 [2013-10-01 11:36:13] Loaded configuration file cgminer.conf [2013-10-01 11:36:14] AMU 0 usb write error: LIBUSB_ERROR_NOT_SUPPORTED [2013-10-01 11:36:14] AMU 0 usb write error: LIBUSB_ERROR_NOT_SUPPORTED [2013-10-01 11:36:14] AMU 0 usb write error: LIBUSB_ERROR_NOT_SUPPORTED [2013-10-01 11:36:14] AMU 0 usb write error: LIBUSB_ERROR_NOT_SUPPORTED [2013-10-01 11:36:14] AMU 0 usb write error: LIBUSB_ERROR_NOT_SUPPORTED [2013-10-01 11:36:14] AMU 0 usb write error: LIBUSB_ERROR_NOT_SUPPORTED [2013-10-01 11:36:14] AMU 0 usb write error: LIBUSB_ERROR_NOT_SUPPORTED [2013-10-01 11:36:14] AMU 0 usb write error: LIBUSB_ERROR_NOT_SUPPORTED [2013-10-01 11:36:16] No devices detected! [2013-10-01 11:36:16] Waiting for USB hotplug devices or press q to quit [2013-10-01 11:36:16] Probing for an alive pool
This was try with just one BE. Cry

Rant2112

newbie

Activity: 70

Merit: 0

I'm still having trouble getting my Block Erupter to work on anything besides 3.1.1

With 3.5.0 I get:

AMU0: TIMEOUT GetResults took 659ms but was 100ms
...
AMU0: TIMEOUT GetResults took 659ms but was 100ms

AMU0: Comms error (werr=-7 amt=0)
...
AMU0: Comms error (werr=-7 amt=0)

I think this is a known problem but posting just to be sure. I'll continue to use 3.1.1 as it is working fine. Cool

FYI - I'm mining using a recent Ubuntu release running under VMWare Fusion on a Mac. The Block Erupter is plugged into a USB2 D-Link HUB. It is connected to a 'high speed' USB port on the Mac which should mean it is USB2.

Photon939

sr. member

Activity: 452

Merit: 250

Quote from: -ck on September 30, 2013, 10:11:46 AM

Quote from: Photon939 on September 30, 2013, 10:05:03 AM

Quote from: -ck on September 30, 2013, 09:16:14 AM

Quote from: Photon939 on September 30, 2013, 08:08:55 AM

Initial results for 3.5.0 on Raspberry Pi with Bitfury BF1 and BFL gear are underwhelming. Running overnight I woke up to the BF1s running anywhere from 0 to about 1.2 Gh/s. I restarted cgminer and things seem to pick back up. Will report the status when I get home from work

The BF1 draws power entirely from USB. How are you connecting it to an RPi ?

It is running on a powered USB hub (albeit a cheap one) with an external 4A supply running five BF1s, it ran stable fine from Ubuntu and BFGminer for a few days so the hub shouldn't be a problem

Edit - Pi is running new Raspbian release

Well that sounds nasty and you should stop using cgminer for now with that combo.

After running another day this problem has happened again. I guess I'll switch to BFGminer for a bit and see if that works better. Also the system seems to crash quite frequently. My arduino watchdog has been doing its job but it seems sometimes the BF1s don't come back online after a reboot. The BFL gear has been running perfectly, only the BF1s seem to get stuck.

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