Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 535. (Read 5806088 times)

cgminer.exe -n
It will show your devices detected by cgminer.
Then run it:
cgminer.exe -d
to mine on proper device.
See 1st post

I have a PC that the display is connected to built in Intel gpu, Intel G620 sandybridge on a Socket 1155 motherboard.
I also have a AMD 7950 installed + amd catalyst + amd SDK 2.7

Is there any way to get cgminer working with the above setup?!

edit--> Making the AMD card primary with vga cable connected to display does not help still

Failed to init GPU thread 0, disabling device 0
restarting the gpu from the menu will not fix this.
Try restarting cgminer.

edit2 ---> I'm able to mine by uninstalling intel driver and disabling intel gpu in motherboard bios
Is there a way to keep using Intel gpu and mining on the AMD?

This sounds like the screen buffer problem many of us have encountered.  Set your console window's default values for screen buffer to higher values.  My pc is set to 580x525 and that seems to work for a large amount of singles.

WFM

http://ck.kolivas.org/
is down

For the first time I've hooked up all 6 of my BFLs to a windoze machine and it does the same. I don't have much time right now to investigate, but I will if I can.

Yes my long post about this and other issues in detail exists in the cairnsmore thread - you should read:
https://bitcointalksearch.org/topic/m.1042648

The cairnsmore1 boards don't work quite as intended with the icarus bitstream. They will only hash on 2 of the 4 FPGAs, so you'll only get half of what cgminer reports. The figure from deepbit is correct, though I'd also recommend switching to a different pool. There's a lot of people working hard on a new bitstream to take full advantage of the cairnsmore1 hardware, so we just have to be a little patient until something better is released. You can keep apprised of all the updates in the enterpoint thread: https://bitcointalksearch.org/topic/cairnsmore1-quad-xc6slx150-board-78239.

Try a different pool first to see if it's deepbit at fault... and then stay away from them for your own sake as you're losing bucketloads of profit due to high fees and hoppers stealing your share of the rewards.

New FPGA miner here with a request for some knowledge help...My config (detailed below) is averaging 1420MHs on cgminer but deepbit is only reporting 1/2 that, ~700MHs. Any ideas on;
1. Why this is happening
2. How can I fix this - mine 1600 and have the pool report 1600?

My FPGA config is
2 * Cairnsmore 1 boards running the Icarus bitstream
Mining using cgminer 2.4.3. -phatk

My GPU miners are disabled
2 * 6770s

Thanks for your insightfulness

Cranky

-T works as well, and gives me enough info to see what's going on, thanks.


Thanks for submitting the request. I tried the debug build of bfgminer you linked and it crashed as well in the same way as cgminer.

I submitted a pull request to attempt to fix this. It works if I overflow with CPU devices, so hopefully it will help you. Here is a (temporary) debug build of BFGMiner with the fix applied (sorry, I can't build CGMiner for Windows with OpenCL support...).

Darn, but yes the displaying library pdcurses is the issue. You can try the old fashioned -T mode which is just plain text. At least you'll have some output.

Quiet mode didn't work. Real-quiet mode did, thanks for the help. Any idea why this is happening? I'd like to be able to see the standard cgminer output. I've tried increasing the prompt defaults gradually to ridiculous sizes (extending off the display on 1920x1080 resolution) with no success. Maybe I'm misunderstanding the cause of the crash still.

Here's the windows error log.

I thought I did (a long time ago), so I went back and checked again and apparently I never modified the defaults, only the current session. That didn't fix the problem, but now I get this (with -D flag):

Tried increasing the size of your dos prompt window before starting it?

Ok, I've been having a somewhat weird problem with cgminer for a while now. I've tried searching but I couldn't find any relevant info. I'm running windows 7 x64. When I start cgminer it crashes immediately. There's no error message shown, even with -D command line option. I get a "cgminer has stopped working" dialog from windows. It doesn't seem to be related to my devices, it happens if I use one or two of my 7970s, or no GPUs and just the two Cairnsmore1's I have connected. I have tried multiple versions of cgminer (2.5.0, 2.3.4(Enterpoint modified)) , and the issue occurs on both of them. I've downloaded a fresh cgminer and the issue occurs with it as well. I have installed multiple AMD driver versions (12.3, 12.4, 12.6, 12.7) and the issue occurs with all of them. To my knowledge nothing has changed since cgminer was working properly.

I can get cgminer to run by restarting windows (I have cgminer included in the startup folder to run automatically) and not touching anything. It'll run properly until I try to move the cgminer window or open a browser or media app. Then it crashes in exactly the same way, and crashes with each subsequent restart.

Now the strangest part is that this happened to me about a month ago out of the blue like now. I tried everything I could think of to fix it, and got frustrated and walked away for a while. I came back (maybe 12 hours later) and ran cgminer and it worked flawlessly up until last night.

I used the debugging option via visual studios and was able to get this, no clue if it'll be of help at all:

Unhandled exception at 0x62209ccc in cgminer.exe: 0xC0000005: Access violation reading location 0x6223efac.

If anyone could help I'd appreciate it, I can't think of anything else I can try to get this working again (other than just waiting it out, for whatever reason that worked before). Thanks guys.

The dialout group gives you full access to the serial ports as normal user using that command added you to that group, it was/still is used for modems among other serial devices.

The modprobe command did not fix it. Running "sudo usermod -a -G dialout USERNAME" did fix it, though. I don't know what this command does, but ostensibly it gives my user account access to this computers virtual serial ports?