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

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"

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.

Using difficulty 128 is HW value too high . Any feedback would be helpful.

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.

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.

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"    As you can tell I need some help.

I was using that one:

1 )Starting Installation of AMD APPSDK v2.8 ....
2 )64-bit Operating System Found..
3 )Version Information Available in VersionInfo.txt
4 )Untar command executed succesfully, The SDK package available
5 )Untar command executed succesfully, The ICD package available
6 )SDK Binaries/Source/Samples/Other files copying to  = /opt/AMDAPP
7 )SDK files copied successfully at /opt/AMDAPP/
8 )Copying the OpenCL runtime files to System...  
9 )Updating Environment vairables...
10 )Updating LD_LIBRARY_PATH in /etc/profile
11 )Environment vairables updated successfully
12 )Initialize global environment vairables...
13 )Global environment vairables Initialized
14 )AMD APP installation Completed
15 )Reboot required to reflect the changes

is there a command line setting that i need to make? I'm just using: ./cgminer

or do i need to set something with aticonfig?

or do i need a dummy plug to enable the board?

SDK 2.8

It's BAS because you're disabling that whole brand of ASICs. Also, I believe the minirig is recognized as several (8?) singles; so that's still BAS. Not sure what the L would stand for.

I am experiencing similer problems with the bfl asic jalapeno device
Posted on the bfgminer thread as well, this thing baffles me.

Now to make it even more interresting i do have 5 pc's in the house and all are somewhat different machines
The weirdest of all is on some of them do work without messing with winusb driver crap
Well as long as i use easyminer or bitminter client they run.

Ofcourse this would be good if i really wanted to mine on these pools.

Now if i want to run cgminer or bfgminer from command line they fail, giving messages device not found or timed out messages.
To be precise i use the same pools to test to see if it actually wants to run.

My main intel pc which i want to run the miner on simply does not work, i tried installing the winusb v6 driver which caused me numerous problems with attached usb devices as well.
I also tried another similar usb driver which gave me the same problems and not finding usb devices for mining problem
Do not get me wrong windows even with its own driver finds the device and reports it connected.

Just cgminer does not find it or times out for some reason. I get the same with bfgminer
I do however not want the programs to use any of my gpu's simply because they eat too much juice.

ok, cgminer -n gets the following:

./cgminer -n
 [2013-06-21 15:10:01] CL Platform 0 vendor: Advanced Micro Devices, Inc.                    
 [2013-06-21 15:10:01] CL Platform 0 name: AMD Accelerated Parallel Processing                    
 [2013-06-21 15:10:01] CL Platform 0 version: OpenCL 1.2 AMD-APP (1113.2)                    
 [2013-06-21 15:10:01] Platform 0 devices: 1                    
 [2013-06-21 15:10:01]    0   Tahiti                    
 [2013-06-21 15:10:01] Failed to ADL_Adapter_ID_Get. Error -10                    
 [2013-06-21 15:10:01] This error says the device is not enabled                    
 [2013-06-21 15:10:01] Failed to ADL_Adapter_ID_Get. Error -10                    
 [2013-06-21 15:10:01] This error says the device is not enabled                    
 [2013-06-21 15:10:01] GPU 0 AMD Radeon HD 7900 Series  hardware monitoring enabled                    
 [2013-06-21 15:10:01] 1 GPU devices max detected                    
 [2013-06-21 15:10:01] USB all: found 7 devices - listing known devices                    
 [2013-06-21 15:10:01] No known USB devices

aticonfig --lsa
* 0. 01:00.0 AMD Radeon HD 7900 Series
  1. 04:00.0 AMD Radeon HD 7900 Series


There is a Sapphire 7970 in the PCIe X16  slot and a GigaByte  7950 on a PCIe X16 PCIe X16 extender which is plugged into a PCIe X16 connector on the MB which is actually X4. any ideas why I'm only seeing one card? this is running on 64 bit ubuntu 12.whatever LTS i didn't see anything specific to this in README or GPU-README

Just curious, should that be "BAJ:0" instead of "BAS:0" or does "BA" disable all BFL ASICs?

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

That's where I found it, just trying to help someone who didn't RTFM.   

Yeah with 3.1.1 you need to use \\.\COM10 etc for COM numbers > 9
... it's in the readme

Wow great advice thanks again, I've bookmarked this in case I run in to any problems in the future.

cgminer 3.1.1 absolutely works with higher # com ports - I _start_ my numbering at Com10.

If you go to 3.2.2 you need to switch to the WinUSB driver - this depreciates the com ports (and thus the -S switch).

Thanks

There's been quite a few changes since 3.1.1 so if you are having trouble with 3.1.1 and the Jalapeno then you can easily get around it by running 2 cgminers as follows:

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

Run a second one but 3.2.2 with a different usb setting --usb ICA:0 so it will ignore all Icarus devices (the Asicminer USB is an Icarus device)

The two wont attempt to touch the other's devices.

OR you could search / read the thread / read the manual instead of reposting questions...

Update: I left this machine mining for about an hour, with that error continuing (as the ASICMINERs where running), and it seems to have corrected itself. So far it looks like it is hashing at almost exactly 5GH/s, hopefully the error won't persist.

I've very grateful everyone who read my post and/or offered help!

0.075 tip sent with thanks to each -Redacted- and kano, spend it in good health.   

I currently run 37 miners on one PC and 11 on another (this one) under win-7 64 bit.  Com ports above 9 work just fine:

--api-listen --api-allow W:127.0.0.1 --icarus-options 115200:1:1 --icarus-timing 3.0=100 -S //./COM4 -S //./COM5 -S //./COM6 -S  //./COM9 -S //./COM10 -S //./COM11 -S //./COM12 -S //./COM14 -S //./COM16  -S //./COM17  -S //./COM18

cgminer versions past 3.1.1 don't use com ports, they use the WinUSB driver.  Lots of information available about that over the last few forum pages.