Sorry for doing this but is there any chance for me getting an answer?
https://bitcointalksearch.org/topic/m.2359449
Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 310. (Read 5806015 times)
June 05, 2013, 02:24:18 AM
June 04, 2013, 11:59:25 PM
Just to check, on Linux, is 3.2.0 working fine? (Using 1 Ztex, 2 BFL FPGA and a bunch of ASICMINER USB sticks)
Or should I stick on the previous version?
If it initialises the AMU (Asicminer USB Block Erupters) correctly, then yes go with it.Or should I stick on the previous version?
If not, on linux, you simply need to unplug and re-plug in your USB devices before you start 3.1.1
(and use --icarus-timing 3.0=100 --icarus-options 115200:1:1 + the -S device selections)
-S auto on 3.1.1 sufficient? (Saw some post of people listing every single usb device)
June 04, 2013, 11:53:42 PM
You should merged mine btc, nmc, ixc and dvc.
June 04, 2013, 11:22:33 PM
Oohh.. Sorry.. And thank you.
June 04, 2013, 10:50:30 PM
Is there a way to get this Block Erupter working with the litecoin mining -scrypt option?
No, the BE ASIC is a dedicated SHA256 calculation chip. It won't do anything else.
June 04, 2013, 10:49:37 PM
Just to check, on Linux, is 3.2.0 working fine? (Using 1 Ztex, 2 BFL FPGA and a bunch of ASICMINER USB sticks)
Or should I stick on the previous version?
If it initialises the AMU (Asicminer USB Block Erupters) correctly, then yes go with it.Or should I stick on the previous version?
If not, on linux, you simply need to unplug and re-plug in your USB devices before you start 3.1.1
(and use --icarus-timing 3.0=100 --icarus-options 115200:1:1 + the -S device selections)
...aka no
June 04, 2013, 10:48:53 PM
Just to check, on Linux, is 3.2.0 working fine? (Using 1 Ztex, 2 BFL FPGA and a bunch of ASICMINER USB sticks)
Or should I stick on the previous version?
If it initialises the AMU (Asicminer USB Block Erupters) correctly, then yes go with it.Or should I stick on the previous version?
If not, on linux, you simply need to unplug and re-plug in your USB devices before you start 3.1.1
(and use --icarus-timing 3.0=100 --icarus-options 115200:1:1 + the -S device selections)
June 04, 2013, 10:41:18 PM
Does anyone have any suggestions for getting cgminer working for running ztex boards under windows? The precompiled windows binary detects the ztex devices but then crashes (windows says it stopped responding).
I set up the windows build environment per the windows-build.txt file in the repository, and was able to get the same results with my own compiled version.
I noticed that same .txt file mentioned trying the libusbx driver instead of libusb. I followed those instructions, but the cgminer configure step complains about the usb library being missing.
I set up the windows build environment per the windows-build.txt file in the repository, and was able to get the same results with my own compiled version.
I noticed that same .txt file mentioned trying the libusbx driver instead of libusb. I followed those instructions, but the cgminer configure step complains about the usb library being missing.
June 04, 2013, 10:02:25 PM
Yes I click debug and that program comes up. I'm on server 2012.
June 04, 2013, 09:00:23 PM
This CPU FIX crash may be related to the 2 INSTANCE crash. Only the 17 lancelot one crashes.
cgminer-nogpu.exe caused an Access Violation at location 00453209 in module cgminer-nogpu.exe Reading from location 7c105dbd.
Registers:
eax=00000020 ebx=007055d0 ecx=00000058 edx=7c105dbd esi=00000000 edi=00000016
eip=00453209 esp=0692f87c ebp=00000000 iopl=0 nv up ei pl nz na pe nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010202
Call stack:
http://ck.kolivas.org/apps/cgminer/debug/
cgminer-nogpu.exe caused an Access Violation at location 00453209 in module cgminer-nogpu.exe Reading from location 7c105dbd.
Registers:
eax=00000020 ebx=007055d0 ecx=00000058 edx=7c105dbd esi=00000000 edi=00000016
eip=00453209 esp=0692f87c ebp=00000000 iopl=0 nv up ei pl nz na pe nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010202
Call stack:
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/
Hmm.... Are you sure you've installed the ming debugger and are choosing debug on exit? None of your debug traces have given any actual information.
June 04, 2013, 08:31:31 PM
Just to check, on Linux, is 3.2.0 working fine? (Using 1 Ztex, 2 BFL FPGA and a bunch of ASICMINER USB sticks)
Or should I stick on the previous version?
If it initialises the AMU (Asicminer USB Block Erupters) correctly, then yes go with it.Or should I stick on the previous version?
If not, on linux, you simply need to unplug and re-plug in your USB devices before you start 3.1.1
(and use --icarus-timing 3.0=100 --icarus-options 115200:1:1 + the -S device selections)
June 04, 2013, 06:35:08 PM
its just lancelots bro with modded source to change the name
How does Knc device is already in cgminer 3.1.1 ?
Is it true?
Is it true?
June 04, 2013, 06:15:47 PM
How does Knc device is already in cgminer 3.1.1 ?
Is it true?
Is it true?
June 04, 2013, 05:08:53 PM
This CPU FIX crash may be related to the 2 INSTANCE crash. Only the 17 lancelot one crashes.
cgminer-nogpu.exe caused an Access Violation at location 00453209 in module cgminer-nogpu.exe Reading from location 7c105dbd.
Registers:
eax=00000020 ebx=007055d0 ecx=00000058 edx=7c105dbd esi=00000000 edi=00000016
eip=00453209 esp=0692f87c ebp=00000000 iopl=0 nv up ei pl nz na pe nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010202
Call stack:
http://ck.kolivas.org/apps/cgminer/debug/
cgminer-nogpu.exe caused an Access Violation at location 00453209 in module cgminer-nogpu.exe Reading from location 7c105dbd.
Registers:
eax=00000020 ebx=007055d0 ecx=00000058 edx=7c105dbd esi=00000000 edi=00000016
eip=00453209 esp=0692f87c ebp=00000000 iopl=0 nv up ei pl nz na pe nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010202
Call stack:
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, 04:32:25 PM
Just to check, on Linux, is 3.2.0 working fine? (Using 1 Ztex, 2 BFL FPGA and a bunch of ASICMINER USB sticks)
Or should I stick on the previous version?
Or should I stick on the previous version?
June 04, 2013, 04:30:42 PM
2 lines below ... but I haven't put 3.2.0 there yet ... I guess I should 
Edit: added 3.2.0 but I'll probably remove it once we release the next version
(seems I've caused ... a few ... problems in 3.2.0)
If you are having trouble with 3.2.0 use 3.1.1
Edit: added 3.2.0 but I'll probably remove it once we release the next version
(seems I've caused ... a few ... problems in 3.2.0)
If you are having trouble with 3.2.0 use 3.1.1
June 04, 2013, 02:45:38 PM
June 04, 2013, 01:03:01 PM
MSE will chocke any system... Avira better ;]
Then you need to clean up your system or fix whatever is causing MSE to act that way. Of all the antivirus programs I've tried, MSE has been the lightest-weight one I've ever seen, and that goes back over 15 years now.
I'll second that. Every AV program is flawed, in the sense that it is reactionary only. However, know one knows Windows better than Microsoft, and MSE is the best AV program I've used to date. (The furthest back I remember was using a program to scan a 3.5" disk on a laptop with 384k of memory before I used my cousin's disk, and found the Stoned virus on it.)
M
June 04, 2013, 12:52:36 PM
MSE will chocke any system... Avira better ;]
Then you need to clean up your system or fix whatever is causing MSE to act that way. Of all the antivirus programs I've tried, MSE has been the lightest-weight one I've ever seen, and that goes back over 15 years now.
June 04, 2013, 12:27:24 PM
same problem here - would appreciate a mirror
Might wanna check the first post again. It's there already. Jump to: