Stop faffing about with Windblows and start putting that "use-bins" thing in Linux 2.2.7 
It already does use the bins anyway... I just need to change the message so people know how to create new bins if desired. 
Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 644. (Read 5805983 times)
February 18, 2012, 05:00:40 PM
February 18, 2012, 04:39:52 PM
Well I believe I've fixed this in my git tree, and I've uploaded an exe into that temp directory as always. If someone is brave enough to try the latest driver 12.2 with its sdk on 64 bit windows with this executable I'd be mighty grateful:
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe
Worked for me on latest drivers (12.2) with 7970. http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe
Awesome awesome, thanks. This is big enough a fix to warrant yet another quick release. How did it perform compared to the older sdk 2.6 ?
Just about even.
February 18, 2012, 04:34:34 PM
Well I believe I've fixed this in my git tree, and I've uploaded an exe into that temp directory as always. If someone is brave enough to try the latest driver 12.2 with its sdk on 64 bit windows with this executable I'd be mighty grateful:
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe
Worked for me on latest drivers (12.2) with 7970. http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe
Awesome awesome, thanks. This is big enough a fix to warrant yet another quick release. How did it perform compared to the older sdk 2.6 ?
February 18, 2012, 03:00:39 PM
More AMD breakage coming up. As Diapolo hinted earlier, there is a new AMD driver 12.2 with an SDK that claims to be sdk 2.6 but comes up with the version number 898.1. It breaks cgminer completely making it unable to build any binaries. 
I have yet to investigate why but please do not upgrade unless you already have .bin files that work. I'm going to start a collection of bin files that people may be able to download and they'll be housed here:
Alternatively you could install upgrade but (in windows) select custom install and UNCHECK SDK. Not sure if 12.2 has any notable changes compared to 12.1 but if it does that is way to get "improved" ( I have yet to investigate why but please do not upgrade unless you already have .bin files that work. I'm going to start a collection of bin files that people may be able to download and they'll be housed here:
with AMD deproved) and keep existing SDK installation.My first look made me scream on another fact, they did heavy work on their OpenCL compiler, which tends to behave again very differently compared to former versions ... seems like more work in the future
(it looks like they preffer vector GPRs over scalar GPRs with the new runtime as there are massive shifts in GPR usage).http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe
Worked for me on latest drivers (12.2) with 7970.
February 18, 2012, 02:05:26 PM
Reverted to Nvidia 280.26 drivers and CGMiner works without crashing again. Sad to see the loss of CPU mining from it though.
February 18, 2012, 12:45:50 PM
I have Windows 7 x64, AMD Catalyst 12.2 Pre-Certified Driver, 2 x 6970.
When starting cgminer 2.2.6 I get this error message:
DiabloMiner works fine on this machine.
When starting cgminer 2.2.6 I get this error message:
Code:
[2012-02-18 18:41:15] Started cgminer 2.2.6
[2012-02-18 18:41:15] Probing for an alive pool
[2012-02-18 18:41:15] Long-polling activated for http://127.0.0.1:9332/long-polling
[2012-02-18 18:41:15] Error: Building Program (clBuildProgram)
[2012-02-18 18:41:15] Failed to init GPU thread 0, disabling device 0
[2012-02-18 18:41:15] Restarting the GPU from the menu will not fix this.
[2012-02-18 18:41:15] Try restarting cgminer.
DiabloMiner works fine on this machine.
February 18, 2012, 12:31:44 PM
Stop faffing about with Windblows and start putting that "use-bins" thing in Linux 2.2.7
My kernel is version 3.2.x, so wouldn't it be kinda late for 2.2.7?
February 18, 2012, 10:11:45 AM
Stop faffing about with Windblows and start putting that "use-bins" thing in Linux 2.2.7
February 18, 2012, 09:44:46 AM
Yes, I do have it change the settings. Here's my command line:
cgminer -o http://127.0.0.1:9332 -u xxx-p xxx--auto-gpu --gpu-engine 750-960 --gpu-memclock 250 --temp-target 80 --gpu-vddc 1.1 -g 1
But did you reboot or manually set them back after using the previous version that didn't set them back due to the crash? CGMINER sets them back to where they were when it started, it doesn't know the defaults.cgminer -o http://127.0.0.1:9332 -u xxx-p xxx--auto-gpu --gpu-engine 750-960 --gpu-memclock 250 --temp-target 80 --gpu-vddc 1.1 -g 1
Hmmm. Not sure what that means in this context.
February 18, 2012, 09:24:15 AM
You're not wrong. I'm the windows n00b here. I didn't realise he was running it from a .bat file without opening the dos prompt manually first.
It could also just be a shortcut (as opposed to a batch file), however, I don't know if he is either, but I don't think command prompt would close if he wasn't, which was more my point. The behavior of the command prompt window probably only indicates that the program terminated after being launched from a shortcut (or a batch file with an exit command) and not evidence as to whether or not the termination was clean. So it might be best to have users try again without a shortcut (or even to just uncheck close on exit in the shortcut) to see what the final output was and whether or not it looks like a clean termination. Another option might be to check errorlevel, but I haven't done that in so long I don't remember how or if it is possible in such a scenario. February 18, 2012, 09:12:45 AM
It should not be closing the dos window... there's still something going wrong.
Correct me if I'm wrong, but wouldn't the command prompt window close if cgminer was launched from a shortcut? I don't see how cgminer could prevent that, as it is normal behavior. OTOH, I'm not sure the command prompt window would close even if cgminer crashed out when the command line was fed to an open window. IOW, I'm not sure that it is relevant whether the command prompt window closes or not. February 18, 2012, 09:11:45 AM
It should not be closing the dos window... there's still something going wrong.
Correct me if I'm wrong, but wouldn't the command prompt window close if cgminer was launched from a shortcut? I don't see how cgminer could prevent that, as it is normal behavior. OTOH, I'm not sure the command prompt window would close even if cgminer crashed out when the command line was fed to an open window. IOW, I'm not sure that it is relevant whether the command prompt window closes or not. February 18, 2012, 09:10:40 AM
Yes, I do have it change the settings. Here's my command line:
cgminer -o http://127.0.0.1:9332 -u xxx-p xxx--auto-gpu --gpu-engine 750-960 --gpu-memclock 250 --temp-target 80 --gpu-vddc 1.1 -g 1
But did you reboot or manually set them back after using the previous version that didn't set them back due to the crash? CGMINER sets them back to where they were when it started, it doesn't know the defaults.cgminer -o http://127.0.0.1:9332 -u xxx-p xxx--auto-gpu --gpu-engine 750-960 --gpu-memclock 250 --temp-target 80 --gpu-vddc 1.1 -g 1
February 18, 2012, 09:08:02 AM
Yes, I do have it change the settings. Here's my command line:
cgminer -o http://127.0.0.1:9332 -u xxx-p xxx--auto-gpu --gpu-engine 750-960 --gpu-memclock 250 --temp-target 80 --gpu-vddc 1.1 -g 1
But did you reboot or manually set them back after using the previous version that didn't set them back due to the crash? CGMINER sets them back to where they were when it started, it doesn't know the defaults.cgminer -o http://127.0.0.1:9332 -u xxx-p xxx--auto-gpu --gpu-engine 750-960 --gpu-memclock 250 --temp-target 80 --gpu-vddc 1.1 -g 1
February 18, 2012, 09:07:51 AM
Yes, I do have it change the settings. Here's my command line:
cgminer -o http://127.0.0.1:9332 -u xxx-p xxx--auto-gpu --gpu-engine 750-960 --gpu-memclock 250 --temp-target 80 --gpu-vddc 1.1 -g 1
But did you reboot or manually set them back after using the previous version that didn't set them back due to the crash? CGMINER sets them back to where they were when it started, it doesn't know the defaults.cgminer -o http://127.0.0.1:9332 -u xxx-p xxx--auto-gpu --gpu-engine 750-960 --gpu-memclock 250 --temp-target 80 --gpu-vddc 1.1 -g 1
February 18, 2012, 09:03:13 AM
Yes, I do have it change the settings. Here's my command line:
cgminer -o http://127.0.0.1:9332 -u xxx-p xxx--auto-gpu --gpu-engine 750-960 --gpu-memclock 250 --temp-target 80 --gpu-vddc 1.1 -g 1
But did you reboot or manually set them back after using the previous version that didn't set them back due to the crash? CGMINER sets them back to where they were when it started, it doesn't know the defaults. cgminer -o http://127.0.0.1:9332 -u xxx-p xxx--auto-gpu --gpu-engine 750-960 --gpu-memclock 250 --temp-target 80 --gpu-vddc 1.1 -g 1
February 18, 2012, 08:47:22 AM
Okay I've just uploaded a windows exe that *might* have fixed the long term crash on shutdown problem.
Anyone want to try it please?
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe
Put into a 2.2.6 directory.
Anyone want to try it please?
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe
Put into a 2.2.6 directory.
I started and stopped it like 10 times and it didn't crash.
Isn't supposed to restore the GPU settings though? It still leaves the GPU at its mining settings (a minor inconvenience).
Yes, I do have it change the settings. Here's my command line:
cgminer -o http://127.0.0.1:9332 -u xxx-p xxx--auto-gpu --gpu-engine 750-960 --gpu-memclock 250 --temp-target 80 --gpu-vddc 1.1 -g 1
February 18, 2012, 08:45:07 AM
More AMD breakage coming up. As Diapolo hinted earlier, there is a new AMD driver 12.2 with an SDK that claims to be sdk 2.6 but comes up with the version number 898.1. It breaks cgminer completely making it unable to build any binaries. I have yet to investigate why but please do not upgrade unless you already have .bin files that work. I'm going to start a collection of bin files that people may be able to download and they'll be housed here:
Alternatively you could install upgrade but (in windows) select custom install and UNCHECK SDK. Not sure if 12.2 has any notable changes compared to 12.1 but if it does that is way to get "improved" ( I have yet to investigate why but please do not upgrade unless you already have .bin files that work. I'm going to start a collection of bin files that people may be able to download and they'll be housed here: with AMD deproved) and keep existing SDK installation.My first look made me scream on another fact, they did heavy work on their OpenCL compiler, which tends to behave again very differently compared to former versions ... seems like more work in the future
(it looks like they preffer vector GPRs over scalar GPRs with the new runtime as there are massive shifts in GPR usage).http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe
February 18, 2012, 07:03:04 AM
Okay I've just uploaded a windows exe that *might* have fixed the long term crash on shutdown problem.
Anyone want to try it please?
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe
Put into a 2.2.6 directory.
Anyone want to try it please?
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe
Put into a 2.2.6 directory.
I started and stopped it like 10 times and it didn't crash.
Isn't supposed to restore the GPU settings though? It still leaves the GPU at its mining settings (a minor inconvenience).
February 18, 2012, 07:01:47 AM
Okay I've just uploaded a windows exe that *might* have fixed the long term crash on shutdown problem.
Anyone want to try it please?
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe
Put into a 2.2.6 directory.
Anyone want to try it please?
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe
Put into a 2.2.6 directory.
I started and stopped it like 10 times and it didn't crash.
Isn't supposed to restore the GPU settings though? It still leaves the GPU at its mining settings (a minor inconvenience).
Jump to: