Came here to report the site/release files are down, but I see that's already been taken care of.
So instead I'll just thank the developer for this fine project. Thanks!
Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 311. (Read 5806015 times)
June 04, 2013, 12:23:16 PM
June 04, 2013, 11:56:27 AM
same problem here - would appreciate a mirror
June 04, 2013, 11:52:41 AM
I currently can´t access
http://ck.kolivas.org/apps/cgminer
does anyone else have this problem ?
best regards
http://ck.kolivas.org/apps/cgminer
does anyone else have this problem ?
best regards
June 04, 2013, 11:48:58 AM
I just can't figure out why 3.2.0 is so difficult to get working.
With 3.2.0 (using modprobe or not using modprobe) -- I get the following when running cgminer --usb-dump 0
I'm running as root, so permissions aren't a problem though I've done the udev rules as well.
If I run cgminer 3.1.X I am able to get them to mine via the /dev/ttyUSBX interfaces though the problem I have there is a couple units will only show 1 or 2 accepted shares while other units will have 60... and the MH/s rating is the same on all of them and shows up in cgminer like they are all working, just some aren't producing shares... very strange.
These are Cairnsmore1's.
With 3.2.0 (using modprobe or not using modprobe) -- I get the following when running cgminer --usb-dump 0
Code:
[2013-06-04 11:46:37] Started cgminer 3.2.0
[2013-06-04 11:46:37] USB all: found 11 devices - listing known devices
.USB dev 0: Bus 1 Device 8 ID: 0403:8350
Manufacturer: 'FTDI'
Product: 'Cairnsmore1'
.USB dev 1: Bus 1 Device 9 ID: 0403:8350
Manufacturer: 'FTDI'
Product: 'Cairnsmore1'
.USB dev 2: Bus 1 Device 10 ID: 0403:8350
Manufacturer: 'FTDI'
Product: 'Cairnsmore1'
.USB dev 3: Bus 1 Device 11 ID: 0403:8350
Manufacturer: 'FTDI'
Product: 'Cairnsmore1'
.USB dev 4: Bus 1 Device 5 ID: 0403:8350
Manufacturer: 'FTDI'
Product: 'Cairnsmore1'
.USB dev 5: Bus 1 Device 6 ID: 0403:8350
Manufacturer: 'FTDI'
Product: 'Cairnsmore1'
[2013-06-04 11:46:37] 6 known USB devices
[2013-06-04 11:46:37] USB init, set config 1 in use - CMR device 1:8
[2013-06-04 11:46:37] Icarus detect (1:8) failed to initialise (incorrect device?)
[2013-06-04 11:46:37] USB init, set config 1 in use - CMR device 1:9
[2013-06-04 11:46:37] Icarus detect (1:9) failed to initialise (incorrect device?)
[2013-06-04 11:46:37] USB init, set config 1 in use - CMR device 1:10
[2013-06-04 11:46:37] Icarus detect (1:10) failed to initialise (incorrect device?)
[2013-06-04 11:46:37] USB init, set config 1 in use - CMR device 1:11
[2013-06-04 11:46:37] Icarus detect (1:11) failed to initialise (incorrect device?)
[2013-06-04 11:46:37] USB init, set config 1 in use - CMR device 1:5
[2013-06-04 11:46:37] Icarus detect (1:5) failed to initialise (incorrect device?)
[2013-06-04 11:46:37] USB init, set config 1 in use - CMR device 1:6
[2013-06-04 11:46:37] Icarus detect (1:6) failed to initialise (incorrect device?)
[2013-06-04 11:46:37] No devices detected!
[2013-06-04 11:46:37] Waiting for USB hotplug devices or press q to quit
[2013-06-04 11:46:37] Need to specify at least one pool server.
[2013-06-04 11:46:37] USB all: found 11 devices - listing known devices
.USB dev 0: Bus 1 Device 8 ID: 0403:8350
Manufacturer: 'FTDI'
Product: 'Cairnsmore1'
.USB dev 1: Bus 1 Device 9 ID: 0403:8350
Manufacturer: 'FTDI'
Product: 'Cairnsmore1'
.USB dev 2: Bus 1 Device 10 ID: 0403:8350
Manufacturer: 'FTDI'
Product: 'Cairnsmore1'
.USB dev 3: Bus 1 Device 11 ID: 0403:8350
Manufacturer: 'FTDI'
Product: 'Cairnsmore1'
.USB dev 4: Bus 1 Device 5 ID: 0403:8350
Manufacturer: 'FTDI'
Product: 'Cairnsmore1'
.USB dev 5: Bus 1 Device 6 ID: 0403:8350
Manufacturer: 'FTDI'
Product: 'Cairnsmore1'
[2013-06-04 11:46:37] 6 known USB devices
[2013-06-04 11:46:37] USB init, set config 1 in use - CMR device 1:8
[2013-06-04 11:46:37] Icarus detect (1:8) failed to initialise (incorrect device?)
[2013-06-04 11:46:37] USB init, set config 1 in use - CMR device 1:9
[2013-06-04 11:46:37] Icarus detect (1:9) failed to initialise (incorrect device?)
[2013-06-04 11:46:37] USB init, set config 1 in use - CMR device 1:10
[2013-06-04 11:46:37] Icarus detect (1:10) failed to initialise (incorrect device?)
[2013-06-04 11:46:37] USB init, set config 1 in use - CMR device 1:11
[2013-06-04 11:46:37] Icarus detect (1:11) failed to initialise (incorrect device?)
[2013-06-04 11:46:37] USB init, set config 1 in use - CMR device 1:5
[2013-06-04 11:46:37] Icarus detect (1:5) failed to initialise (incorrect device?)
[2013-06-04 11:46:37] USB init, set config 1 in use - CMR device 1:6
[2013-06-04 11:46:37] Icarus detect (1:6) failed to initialise (incorrect device?)
[2013-06-04 11:46:37] No devices detected!
[2013-06-04 11:46:37] Waiting for USB hotplug devices or press q to quit
[2013-06-04 11:46:37] Need to specify at least one pool server.
I'm running as root, so permissions aren't a problem though I've done the udev rules as well.
If I run cgminer 3.1.X I am able to get them to mine via the /dev/ttyUSBX interfaces though the problem I have there is a couple units will only show 1 or 2 accepted shares while other units will have 60... and the MH/s rating is the same on all of them and shows up in cgminer like they are all working, just some aren't producing shares... very strange.
These are Cairnsmore1's.
June 04, 2013, 10:50:31 AM
For Linux, there is no 32 bit binary so he'd have to build it himself (and this begs the question why anyone would use a 32bit linux on any normal desktop, if that's what he is doing ... but he may not be)
1) hardware doesn't support it (not that I run cgminer on it, but the Core Solo in my notebook only supports x86)
2) x86 is more suitable for memory-constrained systems than amd64 (x32 is supposed to provide most of the advantages of amd64 with the smaller memory footprint of x86, but I haven't tried it yet)...my VPS is x86 for this reason
June 04, 2013, 10:32:09 AM
with the same settings version 3.1.1 I have fan speed about 2500rpm
with version 3.2.0 gpu fan speed is full 3600rpm
with version 3.2.0 gpu fan speed is full 3600rpm
June 04, 2013, 09:59:54 AM
You are allowed to not quote everything again here...
You didn't even mention that he had top-posted. Then again, top-posting and not trimming quotes seem to go together like gonorrhea and crabs.
June 04, 2013, 09:38:04 AM
Permissions problem potentially. Follow the same udev file procedure as documented for BFL devices in ASIC-README.
Those instructions were already followed. Still no-go.
June 04, 2013, 09:27:15 AM
One of the symptoms is that after running 3.2.0, the device in /dev/ttyUSB0 disappears.
As Kano has said multiple times, this is correct!!!
cgminer is no longer using the usbserial module to talk to the device, so I would expect it's unbinding the device from the usbserial module which is why /dev/ttyUSB0 vanishes.
Do an lsusb and see if the device is still on the USB bus.
Sorry, this is news to me. I haven't seen the posts you are talking about. Even so, the devices still don't show up on the ncurses display. Anything else that needs to be done to get them recognized?
June 04, 2013, 09:26:27 AM
Kano, it seems that most everyone in this forum: https://bitcointalk.org/index.php?topic=195052.1760 has not been able to get cgminer 3.2.0 to work with the little USB block erupters. The people that have been successful are using 3.1.1. You seemed so confident that it would work and I assume you have one of these devices too. Given that it worked fine for you and for none of us (that I am aware of), it's probably something simple to fix, like a missing library or something?
We're investigating. For the time being, consider 3.1.1 the stable release for that hardware as 3.2 is still under heavy development. TTY devices/COM ports are supposed to disappear with our direct USB implementation code in 3.2+. June 04, 2013, 09:25:36 AM
One of the symptoms is that after running 3.2.0, the device in /dev/ttyUSB0 disappears.
As Kano has said multiple times, this is correct!!!
cgminer is no longer using the usbserial module to talk to the device, so I would expect it's unbinding the device from the usbserial module which is why /dev/ttyUSB0 vanishes.
Do an lsusb and see if the device is still on the USB bus.
Sorry, this is news to me. I haven't seen the posts you are talking about. Even so, the devices still don't show up on the ncurses display. Anything else that needs to be done to get them recognized?
June 04, 2013, 09:18:17 AM
One of the symptoms is that after running 3.2.0, the device in /dev/ttyUSB0 disappears.
As Kano has said multiple times, this is correct!!!
cgminer is no longer using the usbserial module to talk to the device, so I would expect it's unbinding the device from the usbserial module which is why /dev/ttyUSB0 vanishes.
Do an lsusb and see if the device is still on the USB bus.
June 04, 2013, 09:07:35 AM
Of course
Here you go:oops do u have a debug, cpu fixed?
Not today, at work... gimme another day.http://ck.kolivas.org/apps/cgminer/debug/
June 04, 2013, 08:54:32 AM
3.2.0. crashes at any of my gpu only rigs (win7) but works fine at computer with BFL FPGA device
June 04, 2013, 08:46:17 AM
Kano, it seems that most everyone in this forum: https://bitcointalk.org/index.php?topic=195052.1760 has not been able to get cgminer 3.2.0 to work with the little USB block erupters. The people that have been successful are using 3.1.1. You seemed so confident that it would work and I assume you have one of these devices too. Given that it worked fine for you and for none of us (that I am aware of), it's probably something simple to fix, like a missing library or something?
One of the symptoms is that after running 3.2.0, the device in /dev/ttyUSB0 disappears.
Edit: did you get one of the original block erupters and ours are the new Sapphire version?
One of the symptoms is that after running 3.2.0, the device in /dev/ttyUSB0 disappears.
Edit: did you get one of the original block erupters and ours are the new Sapphire version?
June 04, 2013, 08:46:09 AM
MSE will chocke any system... Avira better ;]
June 04, 2013, 08:44:46 AM
I am using Avast, but it seems to be detecting the program as a virus, does it matter?
Well, AVAST sucks for a start. Use Microsoft Security Essentials.
Second, as long as you downloaded cgminer from the correct place, it won't be a virus. Use only the links in the first post on this thread. I've seen cgminer packages hosted on Rapidshare and the likes, and they have had a virus in them.
June 04, 2013, 07:15:35 AM
screen -dmS cgminer
June 04, 2013, 07:06:24 AM
You can use "screen" too
Definitely, but this means that you need to (after a system reboot) remember, or be available, to log in and start everything up.
I have my systems PXE booting, automatically starting X under tty12 and cgminer under daemontools. It means that my miners can reboot at any time and they'll come up mining. Throw in puppet for managing the config files and it's fairly well automated.
You can automate the starting of 'screen' also. My machines automatically resume mining (with 'screen') after a reboot as well.
Would you mind sharing your code for this? I can't seem to get mine up & running... It's a pain having to re-type everything on a restart....
June 04, 2013, 05:52:07 AM
I would assume so since what else could they have used to test the board?
Jump to: