OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.1

[bitpop]

Well you do need xp at least

well it may be funny, but i have a terribly old pc wich i'm thinking of turning into miner's helper and run cgminer on it. That's why...

[1542095530]

1542095530

[1542095530]

1542095530

[1542095530]

1542095530

[stepkrav]

Well you do need xp at least

well it may be funny, but i have a terribly old pc wich i'm thinking of turning into miner's helper and run cgminer on it. That's why...

i'd prefer using linux.

[bitpop]

You'd be surprised, most old processors have x64.
But if you run linux, you have to build your own x86 like he said.

[stepkrav]

ok building a binary for 32bit was pretty straight-forward. Cool! 

[Trongersoll]

LOL

can i run cgminer on a 32bit pc?  Thanks.

I don't think it works on the Amiga ... or the PS3 ... but which 32 bit PC were you referring to?

Yes it was a joke - however there is a relevant question in there too
For windows, ther binary of course is already 32bit so works on both 32bit and 64bit
For RPi, my binaries git has a 32 bit binary (only) but I've not put 3.2.0 in there yet - only 3.1.1
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)

ok, this is something i was wondering about. Since you just openned the door, just what would be the advantage of running 64 bit Linux over 32 bit Linux for a mining rig?

[-ck]

ok, this is something i was wondering about. Since you just openned the door, just what would be the advantage of running 64 bit Linux over 32 bit Linux for a mining rig?

For mining there is no advantage apart from the GPU driver allowing more devices. However, 64 bit linux is very mature and run everywhere and all CPUs of the last decade on PCs and laptops are 64 bit capable so it's unusual to see anyone consciously use 32 bit on linux except for hardware that is 32 bit. The difference between this and creating binaries on windows is the windows 32 bit binaries will work everywhere, but linux binaries are very distribution and architecture specific, and x86_64 Ubuntu is the most common desktop linux in use. It is also eleventy billion times easier to compile it for yourself on linux than windows.

[Trongersoll]

ok, this is something i was wondering about. Since you just openned the door, just what would be the advantage of running 64 bit Linux over 32 bit Linux for a mining rig?

For mining there is no advantage apart from the GPU driver allowing more devices. However, 64 bit linux is very mature and run everywhere and all CPUs of the last decade on PCs and laptops are 64 bit capable so it's unusual to see anyone consciously use 32 bit on linux except for hardware that is 32 bit. The difference between this and creating binaries on windows is the windows 32 bit binaries will work everywhere, but linux binaries are very distribution and architecture specific, and x86_64 Ubuntu is the most common desktop linux in use. It is also eleventy billion times easier to compile it for yourself on linux than windows.

Thanks for the answer. I'm currrently running cgminer on 32 bit linux mainly because I didn't want to keep track of which of my machines had 32 bit and which had 64. I'm of the opinion that unless you need the accuracy of 64 bit there isn't really any advantage. I might be wrong, but i remember reading that 32 bit linux can use more than the 4 gig RAM that windows is restricted to.  64 bit may be the future, but i live in the present.

[bitpop]

I just noticed, cgminer 3.2 uses massive CPU. I'm runing 20 lancelots and cgminer is using over 70% on a i7-3770.

[kano]

I just noticed, cgminer 3.2 uses massive CPU. I'm runing 20 lancelots and cgminer is using over 70% on a i7-3770.

Windows or linux?

[bitpop]

Windows of course

[-ck]

I just noticed, cgminer 3.2 uses massive CPU. I'm runing 20 lancelots and cgminer is using over 70% on a i7-3770.

What did 3.1.1 use, and is there a way on windows to see what system time the (ftdi) driver is using? The CPU usage of drivers is often hidden from you.

[bitpop]

3.1.1 used very little and confirmed it by seeing total cpu usage.
3.2 looks like its using 50% by itself with another 20% by system interrupts or drivers of some sort

I just noticed, cgminer 3.2 uses massive CPU. I'm runing 20 lancelots and cgminer is using over 70% on a i7-3770.

What did 3.1.1 use, and is there a way on windows to see what system time the (ftdi) driver is using? The CPU usage of drivers is often hidden from you.

[Rant2112]

Got it working!

I went back to cgminer 3.1.1 and used the -S option to tell it where to look.

I'll play with the other settings now and see if I can get it running without root, etc.
...

As per the ASIC-README for 3.2.0

LINUX:

On linux, the direct USB support requires no drivers at all. However due to
permissions issues, you may not be able to mine directly on the devices as a
regular user without giving the user access to the device or by mining as
root (administrator). In order to give your regular user access, you can make
him a member of the plugdev group with the following commands:
...

Read the rest

Edit: there's a bit about "sudo cp 01-cgminer.rules /etc/udev/rules.d/" further down to complete the solution to solve permission problems

I'm fairly certain that I understand the permission issue.

As I said in a later post I have set the udev rules so that the USB device is owned by the plugdev group (and I'm in plugdev as well).

My later post has some more details with the --usb-dump output:
https://bitcointalk.org/index.php?topic=28402.msg2353037#msg2353037

It isn't showing a permission issue now - ttyUSB0 is removed when cgminer starts and cgminer 3.2 doesn't find any devices to mine with.

If I start cgminer 3.2 and then plug in the miner afterwards it is disconnected immediately and cgminer doesn't see it.

[-ck]

It isn't showing a permission issue now - ttyUSB0 is removed when cgminer starts and cgminer 3.2 doesn't find any devices to mine with.

If I start cgminer 3.2 and then plug in the miner afterwards it is disconnected immediately and cgminer doesn't see it.

Not that this is the cause of your problems, but it's worth nothing that ttyUSB0 is being removed by 3.2.0 because cgminer doesn't want that driver there any more, so it being removed is normal.

[Rant2112]

Also, cgminer 3.2 does NOT work if I 'su root' either.  I don't think it is the permission problem.

[-ck]

Also, cgminer 3.2 does NOT work if I 'su root' either.  I don't think it is the permission problem.

USB3 ?

[Rant2112]

Also, cgminer 3.2 does NOT work if I 'su root' either.  I don't think it is the permission problem.

USB3 ?

99% no.  My computer is too old for that.

How do I check?

[Krak]

Also, cgminer 3.2 does NOT work if I 'su root' either.  I don't think it is the permission problem.

USB3 ?

99% no.  My computer is too old for that.

How do I check?

Is the flat piece inside of the port blue? USB 2.0 is usually black or red, USB 3.0 is always (as far as I know) blue.

[-ck]

3.1.1 used very little and confirmed it by seeing total cpu usage.
3.2 looks like its using 50% by itself with another 20% by system interrupts or drivers of some sort

I just noticed, cgminer 3.2 uses massive CPU. I'm runing 20 lancelots and cgminer is using over 70% on a i7-3770.

What did 3.1.1 use, and is there a way on windows to see what system time the (ftdi) driver is using? The CPU usage of drivers is often hidden from you.

Windows normally uses low resolution timers and perhaps it's related to us trying to use high resolution timers with these new drivers. Can you try one of the .exes in:
http://ck.kolivas.org/apps/cgminer/temp/
to see if it makes any difference to CPU usage please?

[bitpop]

About 5-10% better still over 60%
Also I have problems with 2 instances. Running the 17 fpga instance before a 3 crashes the 3.

3.1.1 used very little and confirmed it by seeing total cpu usage.
3.2 looks like its using 50% by itself with another 20% by system interrupts or drivers of some sort

I just noticed, cgminer 3.2 uses massive CPU. I'm runing 20 lancelots and cgminer is using over 70% on a i7-3770.

What did 3.1.1 use, and is there a way on windows to see what system time the (ftdi) driver is using? The CPU usage of drivers is often hidden from you.

Windows normally uses low resolution timers and perhaps it's related to us trying to use high resolution timers with these new drivers. Can you try one of the .exes in:
http://ck.kolivas.org/apps/cgminer/temp/
to see if it makes any difference to CPU usage please?