Bitcoin Forum
November 16, 2018, 06:10:46 AM *
News: Latest Bitcoin Core release: 0.17.0 [Torrent].
 
   Home   Help Search Login Register More  
Pages: « 1 ... 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 [559] 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 ... 846 »
  Print  
Author Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.1  (Read 5766310 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.
pirate1
Member
**
Offline Offline

Activity: 75
Merit: 10



View Profile
June 22, 2013, 12:06:32 AM
 #11161

Can someone break down for me exactly how you do a configuration file?  Is that all you need to do to compile and enable a BFL ASIC?  I know about changing the driver and have zadig.  I have been mining with my fpga and a couple of video cards with the newest version of cgminer.  cgminer-3.2.2  I just can't get it working with the ASIC.  I know I have to enable bflsc but need to know exactly how to do that.  I realize it is probably something simple but I am at a loss and have gone through all the read me files.  Do I just take the example conf file and change it to a conf file and input my info along with the line "--enable-bflsc" : "enabled"  Huh  As you can tell I need some help.

As long as I wake up breathing it's all a bonus.  Sometimes not much of a bonus but still a bonus.
1542348646
Hero Member
*
Offline Offline

Posts: 1542348646

View Profile Personal Message (Offline)

Ignore
1542348646
Reply with quote  #2

1542348646
Report to moderator
1542348646
Hero Member
*
Offline Offline

Posts: 1542348646

View Profile Personal Message (Offline)

Ignore
1542348646
Reply with quote  #2

1542348646
Report to moderator
1542348646
Hero Member
*
Offline Offline

Posts: 1542348646

View Profile Personal Message (Offline)

Ignore
1542348646
Reply with quote  #2

1542348646
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
Krak
Hero Member
*****
Offline Offline

Activity: 591
Merit: 500



View Profile WWW
June 22, 2013, 01:32:34 AM
 #11162

Can someone break down for me exactly how you do a configuration file?  Is that all you need to do to compile and enable a BFL ASIC?  I know about changing the driver and have zadig.  I have been mining with my fpga and a couple of video cards with the newest version of cgminer.  cgminer-3.2.2  I just can't get it working with the ASIC.  I know I have to enable bflsc but need to know exactly how to do that.  I realize it is probably something simple but I am at a loss and have gone through all the read me files.  Do I just take the example conf file and change it to a conf file and input my info along with the line "--enable-bflsc" : "enabled"  Huh  As you can tell I need some help.
That's a compile option that's already enabled in ckolivas' binaries. You don't need that unless you compile it yourself. With 3.2.2 and the right drivers installed, it should instantly recognize it when you plug it in.

BTC: 1KrakenLFEFg33A4f6xpwgv3UUoxrLPuGn
pirate1
Member
**
Offline Offline

Activity: 75
Merit: 10



View Profile
June 22, 2013, 01:38:30 AM
 #11163

It is giving me the message--  BitForceSc detect (2:1) Warning unknown firmware 'FIRMWARE: 1.2:40x00'     
I did use zadig and changed the driver.

As long as I wake up breathing it's all a bonus.  Sometimes not much of a bonus but still a bonus.
Polyatomic
Sr. Member
****
Offline Offline

Activity: 256
Merit: 250


View Profile
June 22, 2013, 02:14:39 AM
 #11164




Using difficulty 128 is HW value too high . Any feedback would be helpful.
kano
Legendary
*
Offline Offline

Activity: 2632
Merit: 1059


Linux since 1997 RedHat 4


View Profile
June 22, 2013, 04:40:20 AM
 #11165

It is giving me the message--  BitForceSc detect (2:1) Warning unknown firmware 'FIRMWARE: 1.2:40x00'    
I did use zadig and changed the driver.
Coz you are using 3.2.2

We only got to access hardware with the new firmware after 3.2.2 was released

Current git for 1.2.x firmware.

Pool: https://kano.is Here on Bitcointalk: Forum BTC: 1KanoPb8cKYqNrswjaA8cRDk4FAS9eDMLU
FreeNode IRC: irc.freenode.net channel #kano.is Majority developer of the ckpool code
Help keep Bitcoin secure by mining on pools with full block verification on all blocks - and NO empty blocks!
kano
Legendary
*
Offline Offline

Activity: 2632
Merit: 1059


Linux since 1997 RedHat 4


View Profile
June 22, 2013, 04:47:57 AM
 #11166

Run the 3.1.1 one above like you already are but add --usb BAS:0 so it will ignore the BFL SC's - the Jalapeno
Just curious, should that be "BAJ:0" instead of "BAS:0" or does "BA<any letter>" disable all BFL ASICs?

Edit: Of course, where I said <any letter> I really meant the valid choices for BFL ASICs: [J | L | S | M ].  (Is it "M" for minirig?)

The usbutils drivers are BAS, BFL, MMQ, AVA, ICA
The name you use there is the driver abbreviation, not the device abbreviation shown on the screen.
Thus when you say BAS:0 it refers to the BFL SC driver and disables trying to mine on all BAX (X = J, L, S and M)
There were 4 SC ASIC products, Jalapeno, LIttle Single, Single and Minirig - so that answers what the letters stand for.

There are other ways to select with --usb as per the README ...

... where it also says "... with BAS:n you can limit how many BFL ASIC devices will
be checked, but you cannot limit the number of each type of BFL ASIC"

Pool: https://kano.is Here on Bitcointalk: Forum BTC: 1KanoPb8cKYqNrswjaA8cRDk4FAS9eDMLU
FreeNode IRC: irc.freenode.net channel #kano.is Majority developer of the ckpool code
Help keep Bitcoin secure by mining on pools with full block verification on all blocks - and NO empty blocks!
pirate1
Member
**
Offline Offline

Activity: 75
Merit: 10



View Profile
June 22, 2013, 11:08:02 AM
 #11167

Thanks for the answer kano but I am not sure I understand.  I found the "driver-bflsc.c" under your git hub.  Is this what I need?  If not, where do I find the current git for 1.2.x firmware?  Do I need to install git and learn how to use it?  Can I just copy and paste the driver somewhere? 

As long as I wake up breathing it's all a bonus.  Sometimes not much of a bonus but still a bonus.
rsbriggs
Full Member
***
Offline Offline

Activity: 370
Merit: 100



View Profile
June 22, 2013, 05:17:47 PM
 #11168

@Polyatomic

Difficulty being much too high for hash rate.  At 800 Mh/s you should be doing difficulty 2 or 4 only.  

But if determined running at difficulty 128, must remembering only about 1 share in every 128 shares calculating being sent.  At 2% error rate, will be averaging  2.5 HW errors for each share submitting.  Suggesting to lower difficulty much.


rsbriggs
Full Member
***
Offline Offline

Activity: 370
Merit: 100



View Profile
June 22, 2013, 05:19:47 PM
 #11169

Thanks for the answer kano but I am not sure I understand.  I found the "driver-bflsc.c" under your git hub.  Is this what I need?  If not, where do I find the current git for 1.2.x firmware?  Do I need to install git and learn how to use it?  Can I just copy and paste the driver somewhere? 

That being source code file, not driver.  You are wanting compiled version of cgminer using that version unless planning to compile software your own self.

FiatKiller
Sr. Member
****
Offline Offline

Activity: 378
Merit: 250


View Profile
June 22, 2013, 06:07:41 PM
 #11170

Wow, what an ordeal... just got my first Jale and I was caught in a catch-22 because cg 3.2.2 has issues with ASIC Block Eruptors(which I already had). If I ran 3.1.1, it would crash from the Jale. If I ran 3.2.2, it could not start the BEs. After two hours of screwing around with different ideas, I finally came up with calling out the specific devices for each version of cg with --usb 1:31 (in my case) for the Jale with cg 3.2.2 and --usb 1:4,1:6,1:7 etc. for the BEs with 3.1.1

3.1.1 does seem to have issues either randomly or with more than a dozen or so devices with the vcp driver. Certain ones won't initialize randomly. I may move a few to a different system since I have 18 total. I did try the usb driver with 3.2.2 and no go. Went back to vcp driver and only 16 of them show-up. Did not try a reboot yet. Just happy to be hashing with double digits for now.  :-D   Also, noticed on reboot previously that the com port numbers can change(which sucks). Not a biggie since I can just leave the PC on for a week straight between reboots.

LTC: LdxgJQLUdr8hZ79BV5AYbxkBUdaXctXAPi
MoonCoin Gambling: https://coin-horse.com/MON/
Subo1977
Sr. Member
****
Offline Offline

Activity: 344
Merit: 250


Flixxo - Watch, Share, Earn!


View Profile
June 22, 2013, 08:54:44 PM
 #11171

are there somewhere nightly builds of cgminer for win?

X       ▄▄█████████▄▄
    ▄██▀▀         ▀▀██▄
  ▄██▀              ▀██▄
 ▄██     ██▄▄          ██▄
▄██      █████▄▄        ██▄
██       ████████▄▄      ██
██       ███████████▄    ██
██       ██████████▀     ██
▀██      ███████▀       ██▀
 ▀██     ████▀         ██▀
  ▀██▄   █▀          ▄██▀
    ▀██▄▄         ▄▄██▀
       ▀▀█████████▀▀
.flixxo    X▄████████████████████▄
██████████████████████
██████████████████████
████████████▀▀███████
█████▀████░░░░░░▄████
█████░░░░░░░░░░▄█████
█████▄░░░░░░░░░░██████
██████░░░░░░░░░███████
███████░░░░░░▄████████
████▄▄░░░░▄▄██████████
██████████████████████
██████████████████████
▀████████████████████▀
▄████████████████████▄
██████████████████████
█████████▀█▀██████████
██████▀▀▀▀▀████████
██████▄▄░░▄▄▄░░███████
████████░░███░░███████
████████░░░░░░▀███████
████████░░███▄░░██████
██████▀▀░░▀▀▀░░░██████
██████▄▄▄▄▄▄███████
█████████▄█▄██████████
██████████████████████
▀████████████████████▀
X[[]]X
kano
Legendary
*
Offline Offline

Activity: 2632
Merit: 1059


Linux since 1997 RedHat 4


View Profile
June 22, 2013, 09:16:14 PM
 #11172

are there somewhere nightly builds of cgminer for win?
On your computer if you make them Smiley

Pool: https://kano.is Here on Bitcointalk: Forum BTC: 1KanoPb8cKYqNrswjaA8cRDk4FAS9eDMLU
FreeNode IRC: irc.freenode.net channel #kano.is Majority developer of the ckpool code
Help keep Bitcoin secure by mining on pools with full block verification on all blocks - and NO empty blocks!
FiatKiller
Sr. Member
****
Offline Offline

Activity: 378
Merit: 250


View Profile
June 23, 2013, 12:16:06 AM
 #11173

Update... after a couple of reboots and trying another miner and reinstalling the usb driver - I actually got everything working in 3.2.2 together. Has been stable for an hour. see what happens.

LTC: LdxgJQLUdr8hZ79BV5AYbxkBUdaXctXAPi
MoonCoin Gambling: https://coin-horse.com/MON/
vapourminer
Legendary
*
Offline Offline

Activity: 1923
Merit: 1079


what is this "brake pedal" you speak of?


View Profile
June 23, 2013, 03:05:25 PM
 #11174

are there somewhere nightly builds of cgminer for win?

check windows-build.txt in the cgminer folder.

kinda involved to initially install mingw32 and set it up for cgminer but once done compiling for windows from git only takes a couple of minutes.
FiatKiller
Sr. Member
****
Offline Offline

Activity: 378
Merit: 250


View Profile
June 23, 2013, 03:15:12 PM
 #11175

3.2.2 stable overnight with 10 block eruptors & a Jale7. Good job with reducing CPU usage. I can run 3D games no problem now compared to 3.1.1, so CPU usage is way down.  :-D  Total Hashrate ~13.5 G   Sending tips your way.

LTC: LdxgJQLUdr8hZ79BV5AYbxkBUdaXctXAPi
MoonCoin Gambling: https://coin-horse.com/MON/
Queenvio
Hero Member
*****
Offline Offline

Activity: 721
Merit: 513



View Profile
June 23, 2013, 07:41:03 PM
 #11176

Hey guys, I have a questions :

I have cgminer 3.1.1 running on an Rusberry Pi .
What is the best way to update the cgminer to the last version?

Greetings

BitMinerN8
Hero Member
*****
Offline Offline

Activity: 626
Merit: 500


Mining since May 2011.


View Profile
June 23, 2013, 10:45:39 PM
 #11177

Hey guys, I have a questions :

I have cgminer 3.1.1 running on an Rusberry Pi .
What is the best way to update the cgminer to the last version?

Greetings

I have always found this to work, but I don't know what device(s) you're trying to support, this was from a while ago:
https://bitcointalk.org/index.php?topic=138921.msg1509722#msg1509722

But you can always grab Kano's compiled versions he makes:
https://bitcointalk.org/index.php?topic=28402.msg2490901#msg2490901
kibblesnbits
Hero Member
*****
Offline Offline

Activity: 555
Merit: 500


View Profile
June 24, 2013, 01:49:11 AM
 #11178

It is giving me the message--  BitForceSc detect (2:1) Warning unknown firmware 'FIRMWARE: 1.2:40x00'     
I did use zadig and changed the driver.

Got the same message, updated from git hub, recompiled, now it just hangs at "starting 3.2.2".  Using Debian.  Any solutions?

ASICMINERTUBE
   
  The Best $/Gh Bitcoin Miner So Far
   ►►►   DISCOVER NOW !!!   ◄◄◄
kibblesnbits
Hero Member
*****
Offline Offline

Activity: 555
Merit: 500


View Profile
June 24, 2013, 02:22:02 AM
 #11179

It is giving me the message--  BitForceSc detect (2:1) Warning unknown firmware 'FIRMWARE: 1.2:40x00'     
I did use zadig and changed the driver.

Got the same message, updated from git hub, recompiled, now it just hangs at "starting 3.2.2".  Using Debian.  Any solutions?

Disregard.  Fat fingered the port number on stratum.  Carry on.  Grin

ASICMINERTUBE
   
  The Best $/Gh Bitcoin Miner So Far
   ►►►   DISCOVER NOW !!!   ◄◄◄
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2702
Merit: 1145


Ruu \o/


View Profile WWW
June 24, 2013, 03:12:36 AM
 #11180

New release: version 3.3.0, 24th June 2013

ASIC device focused release. Minor version update due to new driver support for BFL SC singles, SC minirigs. Numerous other improvements for existing devices. We don't have those devices so all code for this has been done while working on remote hardware and working blindly. Hopefully kano and I will have singles (or doubles as I call them now) soon to ensure the best possible support for the hardware.

GPU owners should start getting used to the idea that at some stage in the future, GPU mining in cgminer will be deprecated the way it was for CPU mining. Since GPU mining is still just above the waterline profitable for BTC and remains profitable for altcoins at the moment, that time has not yet come. But it will.

USB3 hubs continue to be problematic with USB devices for reasons that are still unclear. Since the devices in question that are problematic are all usb1.1, if you were looking to purchase a hub and use cgminer as your primary mining platform, please go with a USB2 hub instead. The problem only manifests with multiple usb1.1 devices on the USB3 hub (i.e. all icarus based devices). If you wish to use multiple devices on a USB3 hub and cgminer, version 3.1.1 which uses the old driver model works best.

I should point out that besides USB3 hubs, these newer direct USB code versions of cgminer are STABLE for all other devices, operating systems and hardware combinations we have access to. This does not include ztex and cairnsmore since we are coding blind for those devices.

Again: Cgminer uses direct USB on all USB devices, so to work on linux you must set your permissions (Instructions in ASIC/FPGA README) and on windows you must install a WinUSB driver (Instructions in ASIC/FPGA README)
 

Human readable changelog:

- Device support for BFL SC singles and minirigs. Assumed to support little singles, but unknown at this stage.
- Support for the newer firmware in BFL devices and that people are flashing to their devices.
- Numerous improvements to the reliability of USB communications should lead to less lost work, less restarts, and fixes for stale files that prevented devices starting without a reboot, along with more reliable shutdown.
- Significant increase in the hashrate on Avalons, fixing the regression introduced on the 3.2 series, along with more reliability.
- New speeds supported on avalon of 325, 350 and 375; 350 seems the sweet spot for many devices.
- New PID-like fan control for Avalons designed to maintain an ~constant temperature instead of using a static fanspeed to temperature ratio, along with the ability to set the target temperature with --avalon-temp.
- Quieter console output with most of the hw errors no longer showing as regular logging since some hw errors on USB devices are routine, not exceptional.
- More fixes to cope with variations in BFL SC device firmware, including very slow to respond ones.
- Prevention of the hashmeter showing 0 for some devices intermittently along with other hashrate display fixes.
- Fixed the block solve detection on big endian hardware (eg Avalon).
- Updated API for ASIC devices.
- New api-example.py courtesy of Setkeh
- No crashing on resizing when hotplugging devices on windows - simple workaround by not trying to resize windows since pdcurses on windows is buggy.
- Display the difficulty as an integer when it is one with stratum.
- Less chance of devices inappropriately being reported as SICK when pools go down.


Full changelog:

- Add an --avalon-temp option to allow a user specified target temperature.
- Demote no matching work message to verbose logging only on avalon.
- Make the fan control on the avalon a simple PID controller with a target
temperature of 45.
- Demote bflsc hw error messages to verbose logging only.
- bflsc - handle xlink timeouts by having generic IO functions
- Demote the invalid nonce warning to log info.
- Ignore iManufacturer for BFLSC devices since the device name will still match
and some unbinned chips are missing it.
- sc_count shouldn't be +1 in bflsc.
- Use the info timeout for read_nl in getidentify bflsc.
- Add a usb_read_nl_timeout macro.
- bflsc try getinfo twice
- set MSG_ASCUSBNODEV always defined
- Hard code the preferred packet size for AMU, BLT and ICA.
- API V1.26 update ASIC support
- Icarus enable the read buffer for the detect nonce
- Support new overclocking speeds for avalon: 325, 350 and 375
- undo icarus show errno, put it as debug in ubsutils
- icarus add errno to rerr and werr
- Sleep after sending icarus work to emulate working at 115200 baud.
- Use the nusleep function for sleeping after sending work in avalon.
- Show an integer only for diff if it is one.
- Set the avalon preferred packet size to 512.
- Reinstate the maxPacketSize determined by the end descriptor but allow the
driver to override it.
- Only update hashmeter if we have done hashes or haven't updated longer than
the log interval, fixing a us/ms error.
- Use only one cgsem in avalon signalling when the write thread should commit
work by reading the status bytes off during an avalon_read, minimising the
number of usb calls and resetting from only one place.
- Change avalon no valid work message to no matching work to match API
terminology.
- Use low latency usb transfers on the avalon, sleeping up to half a buffer's
worth only if no data is returning to increase hashrate, abolish lost work and
decrease CPU.
- Minimise the sleep times in avalon read to avoid result loss.
- Use a half nonce range before cycling through avalon's scanwork to ensure it
gets a chance to fill work if time is tight for the write thread to signal a
wakeup.
- Temporarily limit usb transfer sizes to 512 till we provide a way for each
driver to choose the upper limit.
- Increase watchdog sick time to longer than it takes for a pool to be detected
dead.
- Limit USB transfers to the max size reported by the descriptors.
- Increase the BFLSC timeout to allow the maximum number of results to be
returned for BAS in time.
- Decrease BAL and BAS latency to be just larger than one result read.
- disable curses device resize that crashes on windows
- BFLSC latest firmware has its own thermal cutoff set to 90, so use the same
value in case we have an old firmware that isn't throttling by itself.
- Drop watermark low limits for bflsc.
- Set the fanspeed on bflsc to max if we don't know the temperature.
- Use a low watermark for queueing mandatory work on bflsc instead of zero.
- Only mandatorily grab the bflsc mutex on submitting work when the queue is
empty.
- Adjust bflsc v2 watermarks.
- Only increase sleep time on bflsc if the queue isn't emptying at all over the
sleep duration.
- Fix warning.
- bflsc yet more API stats
- bflsc add some more API stats
- bflsc correct firmware matching
- bflsc correct comment
- Fixed Commands with No params
- bflsc driver support for v2 firmware
- Odd Issues
- Fixed Python Example
- Added Python Api Example
- Added Python Api Example
- Multiplier fail for microseconds vs milliseconds when updating hashmeter in
hash_queued_work.
- Only make threads report in/out across the actual driver code and update their
status on reporting out as well as in.
- usbutils initialise close key/sem
- usbutils cleanup linux semaphores on release
- Difficulty should be unconditionally byteswapped, not swapped to big endian.
- We should be setting cancelstate, not canceltype when disabling it for usb
locking.
- Pthread cancel state should be set to disable on usb DEVLOCK.
- Fanauto on bflsc is Z9X according to the source code, not 5 as per the draft
protocol document.

Developer/maintainer for cgminer and ckpool/ckproxy.
ZERO FEE Pooled mining at ckpool.org, 1% Fee Solo mining at solo.ckpool.org
-ck
Pages: « 1 ... 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 [559] 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 ... 846 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!