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?
Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 646. (Read 5805546 times)
February 18, 2012, 01:31:44 PM
My kernel is version 3.2.x, so wouldn't it be kinda late for 2.2.7?
February 18, 2012, 11:11:45 AM
Stop faffing about with Windblows and start putting that "use-bins" thing in Linux 2.2.7
February 18, 2012, 10: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, 10: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, 10: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, 10: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, 10: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, 10: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, 10: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, 10: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, 09: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, 09: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, 08: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, 08: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).
February 18, 2012, 01:54:41 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.
February 18, 2012, 01:11:45 AM
What does long4 vs. long8 mean in the .bin filename?
Sam
Sam
Notably there are Tahiti (7970) .bins for 32 bit (long4) and 64 bit (long8)
February 18, 2012, 01:07:10 AM
What does long4 vs. long8 mean in the .bin filename?
Sam
Sam
February 18, 2012, 12:03:26 AM
cgminer sets clocks all back to default on exit... if it exits cleanly, and of course on windows it's a miracle when it does.
Sadly this is not the case.
windows machine, pair of 6950's, set to 850/1300 for normal operation, in cgminer they are set to 700-880/300... when cgminer exits it leaves the cards at 880/300.
even updated to 12.1 drivers, both 2.4 and 2.6 SDK.
Is it exiting or crashing?
I run cgminer from a .bat file in windows, and when I hit the "Q" button, it gives me the 2-page summary of stats, then sits for about 3 seconds and then closes the dos window. I'm not getting any complaints from windows about it crashing/hanging/etc.
ckolivas: I know you have the impossible task of trying to make an app play nice with windows. I'm HAPPY to run any sort of debug load/options you might have to give better/more-detailed information.
Try the experimental binary
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe
This one tries to reset GPU settings before trying to shut down so that even if it crashes/hangs on exit, your GPUs should go to default values.
February 17, 2012, 11:28:02 PM
I'm trying to get together a collection of binaries for different hardware from different SDKs. If anyone has binaries for the different SDKs, please check http://ck.kolivas.org/apps/cgminer/bins/ to see if they exist and if not, can you send me a copy?
Thanks everyone who promptly sent me their binaries! I now have a collection in the cgminer directory that people can download if they're having issues with their SDKs. How do people feel about me providing "optimal bins" included as a separate "full package" with cgminer?
I figure 2.4/2.5 bins for vliw4 (R6xxx), 2.1 bins for vliw5 (R5xxx) and 2.6 bins for GCN (R7xxx).
this would be good, especially with a flag "use-bins" : true,
February 17, 2012, 10:27:55 PM
How do people feel about me providing "optimal bins" included as a separate "full package" with cgminer?
I figure 2.4/2.5 bins for vliw4 (R6xxx), 2.1 bins for vliw5 (R5xxx) and 2.6 bins for GCN (R7xxx).
If you do this and cgminer automatically uses the best one, you might get lonely when newbs stop posting about how the latest update slowed them down...I figure 2.4/2.5 bins for vliw4 (R6xxx), 2.1 bins for vliw5 (R5xxx) and 2.6 bins for GCN (R7xxx).
Jump to: