First time messing with Linux version on Raspberry Pi does it just cancel out if not mining devices are found? Its 2-3 months before my Avalon devices come in.
Not in the latest version. 
Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 322. (Read 5805537 times)
May 31, 2013, 03:57:53 PM
May 31, 2013, 03:56:16 PM
Strange things happened here on my rpi (Raspbian wheezy). 3.2.0 detected my Lancelot (BLT), plug and pray is working fine. 
But no luck with any of my Block Erupter USBs, not detected, no plug and play at all. 
All devices connected using the same powered usb 2.0 hub. These are working fine with 3.1.1 using -S options.
Whenever I quit 3.2.0 and try running 3.1.1 again, it can't access the USB devices anymore, have to reboot the rpi...
Any hints are welcome.
pastebin (don't paste here) the output of the end of 'dmesg' when you plug the AMU in But no luck with any of my Block Erupter USBs, not detected, no plug and play at all. All devices connected using the same powered usb 2.0 hub. These are working fine with 3.1.1 using -S options.
Whenever I quit 3.2.0 and try running 3.1.1 again, it can't access the USB devices anymore, have to reboot the rpi...
Any hints are welcome.
also 2 cgminer outputs:
1) cgminer -n
2) cgminer -D -T -verbose ... your options ... 2> debug.log
and let that run for about 30 seconds - and pastebin it or upload the log somewhere
I don't have a powered hub, I guess I better get one to see what's happening myself
(tried to get one last week and oddly none of the shops I went to had one ... except one that was crap)
One other thing to try is to leave it unplugged for about a minute then see if that fixes it
I had mine go into a weird state not being recognised after using different OSs and being left unplugged for a while fixed it for me
The error I got when this happened in the debug log was an error 4 setting the baud
I might try see if that is reproduceable - the error and the unplug fix, and if so, when it happens print a message to do that.
May 31, 2013, 03:28:07 PM
First time messing with Linux version on Raspberry Pi does it just cancel out if not mining devices are found? Its 2-3 months before my Avalon devices come in.
May 31, 2013, 03:17:03 PM
Strange things happened here on my rpi (Raspbian wheezy). 3.2.0 detected my Lancelot (BLT), plug and pray is working fine. But no luck with any of my Block Erupter USBs, not detected, no plug and play at all.
All devices connected using the same powered usb 2.0 hub. These are working fine with 3.1.1 using -S options.
Whenever I quit 3.2.0 and try running 3.1.1 again, it can't access the USB devices anymore, have to reboot the rpi...
Any hints are welcome.
But no luck with any of my Block Erupter USBs, not detected, no plug and play at all. All devices connected using the same powered usb 2.0 hub. These are working fine with 3.1.1 using -S options.
Whenever I quit 3.2.0 and try running 3.1.1 again, it can't access the USB devices anymore, have to reboot the rpi...
Any hints are welcome.
I am having exactly the same problem on the pi. My ZTEXs Quads are recognised without problems but the Eruptor Gizmodos won't show up.
libusb-1.0.0 is installed.
Perhaps it is working with Kano because he is using the Fedora dist on the Raspberry instead of Wheezy?
May 31, 2013, 02:25:12 PM
I'm getting errors in os x 10.8.3. Any ideas how to fix it?
./configure --enable-scrypt --enable-icarus PKG_CONFIG_PATH=/usr/local/opt/curl/lib/pkgconfig CFLAGS="-g -O2 -Wall"
sudo make install
"
<..>
usbutils.c:2576: error: redefinition of ‘union semun’
usbutils.c: In function ‘resource_unlock’:
usbutils.c:2878: warning: implicit declaration of function ‘semtimedop’
make[1]: *** [cgminer-usbutils.o] Error 1
make: *** [install-recursive] Error 1
"
Thank you!
./configure --enable-scrypt --enable-icarus PKG_CONFIG_PATH=/usr/local/opt/curl/lib/pkgconfig CFLAGS="-g -O2 -Wall"
sudo make install
"
<..>
usbutils.c:2576: error: redefinition of ‘union semun’
usbutils.c: In function ‘resource_unlock’:
usbutils.c:2878: warning: implicit declaration of function ‘semtimedop’
make[1]: *** [cgminer-usbutils.o] Error 1
make: *** [install-recursive] Error 1
"
Thank you!
May 31, 2013, 01:56:18 PM
Strange things happened here on my rpi (Raspbian wheezy). 3.2.0 detected my Lancelot (BLT), plug and pray is working fine. But no luck with any of my Block Erupter USBs, not detected, no plug and play at all.
All devices connected using the same powered usb 2.0 hub. These are working fine with 3.1.1 using -S options.
Whenever I quit 3.2.0 and try running 3.1.1 again, it can't access the USB devices anymore, have to reboot the rpi...
Any hints are welcome.
But no luck with any of my Block Erupter USBs, not detected, no plug and play at all. All devices connected using the same powered usb 2.0 hub. These are working fine with 3.1.1 using -S options.
Whenever I quit 3.2.0 and try running 3.1.1 again, it can't access the USB devices anymore, have to reboot the rpi...
Any hints are welcome.
May 31, 2013, 01:31:08 PM
I wrote a bash script that will check to see if a newer version of cgminer is available. If there is a newer version the script will download the pre-built version and extract it.
Here is the script if anybody is interrested:
Here is the script if anybody is interrested:
Code:
#!/bin/bash
server=http://ck.kolivas.org
path=/apps/cgminer/
#; Get the file name for the latest version
cgminer=`wget -q -O- $server$path | egrep -o cgminer-[0-9\.]+-x86_64-built.tar.bz2 | sort -V | tail -1`
#; Get the folder name that the downloaded file should be extracted to
folder="${cgminer%.tar.bz2}"
version="${folder%-x86_64-built}"
version="cgminer ${version##*-}"
echo "Latest version is $version"
#; Check to see if this version is already installed.
if [ ! -d $folder ]
then
echo "Downloading $version..."
#; Download the file
wget -q $server$path$cgminer
echo "Installing $version..."
#; Extract cgminer
tar -xjf $cgminer
#; Create a symbolic link to the new folder so we can keep older versions and the latest version can always be found in "cgminer"
if [ -L cgminer ]
then
rm cgminer
fi
ln -s $folder cgminer
#; Remove the downloaded file
rm $cgminer
else
echo "Already have $version"
fi
May 31, 2013, 11:43:41 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
May 31, 2013, 11:36:55 AM
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"
Those aren't settings for BTC mining.
Thanks for trying to help, anyone else?
What you're looking for is going to be ages old when gpu mining first started. Search for those keywords and settings vs "guide"
settings for mining BTC? ... thread concurrency, shaders, ...
Those aren't settings for BTC mining.
Thanks for trying to help, anyone else?
May 31, 2013, 11:35:41 AM
settings for mining BTC? ... thread concurrency, shaders, ...
Those aren't settings for BTC mining.
Thanks for trying to help, anyone else?
May 31, 2013, 11:28:40 AM
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.
May 31, 2013, 11:16:21 AM
... and yes this is all Windows ... just in case anyone else was wondering.
Linux should hopefully be rock solid.
Linux should hopefully be rock solid.
May 31, 2013, 11:14:09 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 beforeif 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.
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.
May 31, 2013, 11:10:44 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.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.
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.
May 31, 2013, 11: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.
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.
May 31, 2013, 10:58:39 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.
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.
May 31, 2013, 10:57:10 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.
For 3.2.0 (and later) you need to use the WinUSB driver as I mentioned above.
May 31, 2013, 10:56:11 AM
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
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
May 31, 2013, 10:55:19 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: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?)
"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
May 31, 2013, 10:48:58 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.
Jump to: