Author

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

sr. member
Activity: 658
Merit: 250
I tried building the newest git version, and noticed that my linux scrypt miners no longer worked properly. Hashrates were minimal because intensity was only 8. cgminer was complaining about the config being broken, and after starting with -T I saw the error was "Invalid config option --intensity: Invalid value passed to set intensity". This was introduced in commit 2b171f7fae19a451abefd5189ecad64fbd08d8a0, everything still works fine with commit cb6d62de08995cb3ce2ae906dfa629f42d382c21. I'm using intensity 17 on the linux rigs, I don't have the problem on my Windows rigs with a lower intensity.
Try telling it --scrypt before setting the intensity?

Nope, that didn't help. The windows rigs also have intensity set before scrypt in the config, and it works.

EDIT: --scrypt on the command line makes it works on linux too, though. So you seem to be on the right track. The intensity sanity check just doesn't detect that scrypt is being enabled from the config on linux.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
I tried building the newest git version, and noticed that my linux scrypt miners no longer worked properly. Hashrates were minimal because intensity was only 8. cgminer was complaining about the config being broken, and after starting with -T I saw the error was "Invalid config option --intensity: Invalid value passed to set intensity". This was introduced in commit 2b171f7fae19a451abefd5189ecad64fbd08d8a0, everything still works fine with commit cb6d62de08995cb3ce2ae906dfa629f42d382c21. I'm using intensity 17 on the linux rigs, I don't have the problem on my Windows rigs with a lower intensity.
Try telling it --scrypt before setting the intensity?
sr. member
Activity: 658
Merit: 250
I tried building the newest git version, and noticed that my linux scrypt miners no longer worked properly. Hashrates were minimal because intensity was only 8. cgminer was complaining about the config being broken, and after starting with -T I saw the error was "Invalid config option --intensity: Invalid value passed to set intensity". This was introduced in commit 2b171f7fae19a451abefd5189ecad64fbd08d8a0, everything still works fine with commit cb6d62de08995cb3ce2ae906dfa629f42d382c21. I'm using intensity 17 on the linux rigs, I don't have the problem on my Windows rigs with a lower intensity.
legendary
Activity: 952
Merit: 1000
Would it be possible that this could get CUDA support in the future.
Just wondering if its been planned or something as I am using cudaminer currently and it brings my
660 ti upto 200kh/s (I think thats right) on ltc and this has a few features I would love
to be able to have but alas are not available in cudaminer
No, no one could afford to pay me to do that.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Would it be possible that this could get CUDA support in the future.
Just wondering if its been planned or something as I am using cudaminer currently and it brings my
660 ti upto 200kh/s (I think thats right) on ltc and this has a few features I would love
to be able to have but alas are not available in cudaminer
No, no one could afford to pay me to do that.
newbie
Activity: 2
Merit: 0
Would it be possible that this could get CUDA support in the future.
Just wondering if its been planned or something as I am using cudaminer currently and it brings my
660 ti upto 200kh/s (I think thats right) on ltc and this has a few features I would love
to be able to have but alas are not available in cudaminer
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Tried the new version with my GPU/usb erupter mix.  Didn't recognize the GPU and the "-I" switch. Command worked before new version.

BTW running 5870 with 2.4 sdk cat is at 11.12


*update*
tried the new version with my 7970 and the same issue
As my build environment had to be rebuilt from scratch when I returned from overseas, I was missing some stuff which accidentally built the windows binary without GPU support. I've reuploaded a new binary which should work now.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
OK it's missing Avalon - that's the problem
you need --enable-avalon when you configure it.
Do you build it or someone else?
Ah, I see. I just downloaded 3.3.2 (Windows) from here and thought this would be working out of the box.
So I guess I have to build it again with the avalon option enabled?
Previously no one in their right mind would have run a full avalon device on windows so I wasn't including the avalon driver, but the bitburner devices are a little different. So I've uploaded a new binary with the avalon driver built in (includes a last minute bugfix that also would only affect windows users).
hero member
Activity: 574
Merit: 501
Would static linking a fixed libusb also work for producing a Raspian version?   I'm, umm, not particularly fond of the Arch distro...
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Okay I have a laptop with a usb3.0 port and it's all running fine. That's good but now I have doubts that a pi will work... Sad

Unfortunately, the Raspberry Pi is known not to work well with USB 3.0 hubs. I believe it's a hardware limitation of the Pi, not an issue with any particular software or drivers.
My RPi works fine with a USB3.0 hub with 3 AMUs

Maybe some USB3.0 hubs have problems?

However, Rasbian has a bad version of libusb in it - if you have that - yes it will screw up.

If you use RPi Arch http://www.kano-kun.net/?p=87 the libusb problem is gone.
Minepeon also uses Arch: https://bitcointalksearch.org/topic/linux-mining-distro-for-the-raspberry-pi-minepeon-137934

Edit: and of course as I've posted in here many times over the last week - libusb verisons are screwed for AMU/ICA
Here's something like how to rebuild for windows and linux (though it's not the final version of the doc)
https://dpaste.de/a5TvN/

Oh, maybe that's been the problem. I remember there being a lot of angst about RPis and USB 3.0 early on, but maybe nobody had tried Arch at that point.
Updated version of that rebuild info is now in the main README with 3.3.2
My Arch binary in https://github.com/kanoi/cgminer-binaries is statically linked with the working libusb also.
sr. member
Activity: 456
Merit: 250
Okay I have a laptop with a usb3.0 port and it's all running fine. That's good but now I have doubts that a pi will work... Sad

Unfortunately, the Raspberry Pi is known not to work well with USB 3.0 hubs. I believe it's a hardware limitation of the Pi, not an issue with any particular software or drivers.
My RPi works fine with a USB3.0 hub with 3 AMUs

Maybe some USB3.0 hubs have problems?

However, Rasbian has a bad version of libusb in it - if you have that - yes it will screw up.

If you use RPi Arch http://www.kano-kun.net/?p=87 the libusb problem is gone.
Minepeon also uses Arch: https://bitcointalksearch.org/topic/linux-mining-distro-for-the-raspberry-pi-minepeon-137934

Edit: and of course as I've posted in here many times over the last week - libusb verisons are screwed for AMU/ICA
Here's something like how to rebuild for windows and linux (though it's not the final version of the doc)
https://dpaste.de/a5TvN/

Oh, maybe that's been the problem. I remember there being a lot of angst about RPis and USB 3.0 early on, but maybe nobody had tried Arch at that point.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
OK it's missing Avalon - that's the problem
you need --enable-avalon when you configure it.
Do you build it or someone else?
Ah, I see. I just downloaded 3.3.2 (Windows) from here and thought this would be working out of the box.
So I guess I have to build it again with the avalon option enabled?
Odd he must have missed adding --enable-avalon - will be sorted shortly ...
hero member
Activity: 700
Merit: 500
OK it's missing Avalon - that's the problem
you need --enable-avalon when you configure it.
Do you build it or someone else?
Ah, I see. I just downloaded 3.3.2 (Windows) from here and thought this would be working out of the box.
So I guess I have to build it again with the avalon option enabled?
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
You'll need to pastebin a debug run log so I can see what's going on.
cgminer ..options.. -D --verbose 2> log.log

Also, the first 2 lines of cgminer -h will say what options are in your version you are running

Thanks kano, cgminer -h gives this 2 lines:

Quote
cgminer 3.3.2
Built with bflsc bitforce icarus modminer ztex mining support.

Debug pastebin: http://pastebin.com/KKU4mbE7

OK it's missing Avalon - that's the problem
you need --enable-avalon when you configure it.
Do you build it or someone else?
hero member
Activity: 700
Merit: 500
You'll need to pastebin a debug run log so I can see what's going on.
cgminer ..options.. -D --verbose 2> log.log

Also, the first 2 lines of cgminer -h will say what options are in your version you are running

Thanks kano, cgminer -h gives this 2 lines:

Quote
cgminer 3.3.2
Built with bflsc bitforce icarus modminer ztex mining support.

Debug pastebin: http://pastebin.com/KKU4mbE7
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Did you re-flash the firmware according to Burnin's instructions?
Yes
You'll need to pastebin a debug run log so I can see what's going on.
cgminer ..options.. -D --verbose 2> log.log

Also, the first 2 lines of cgminer -h will say what options are in your version you are running
newbie
Activity: 43
Merit: 0
Tried the new version with my GPU/usb erupter mix.  Didn't recognize the GPU and the "-I" switch. Command worked before new version.

BTW running 5870 with 2.4 sdk cat is at 11.12


*update*
tried the new version with my 7970 and the same issue
hero member
Activity: 700
Merit: 500
Did you re-flash the firmware according to Burnin's instructions?
Yes
hero member
Activity: 574
Merit: 501
Did you re-flash the firmware according to Burnin's instructions?
hero member
Activity: 700
Merit: 500
I just tried 3.3.2 on a brand new BitBurner board, but I'm not able to get it working.
cgminer seems to be detecting my hardware correctly (cgminer -n):

Quote
[2013-08-09 20:33:00] USB all: found 6 devices - listing known devices
.USB dev 0: Bus 2 Device 4 ID: 0403:6001
  Manufacturer: 'Burnin Electronics'
  Product: 'BitBurner'
 [2013-08-09 20:33:00] 1 known USB devices

But when running, I get this error:
Quote
No devices detected

Any ideas what could be causing this?
Jump to: