I am having a new problem. I just switched to a thin client that only uses 36 watts. I have 2 other thin clients running with Ubuntu 11.04 on them. Only on this one cgminer looks different. It is just one line and everything is flying by and it is hard to see what is going on.
Is this a different view? Did I set it somehow in the conf file maybe?
How do i get the normal cgminer status window where I can see all my miners in a row?
Thanks
Bo
Topic: [BOUNTY 5 BTC] Clear instructions for cgminer's --scan-serial option (Read 9026 times)
May 22, 2012, 03:15:31 PM
It took me about 4 hours last night to figure this out.
I wish you would have posted this 24 hours ago.
I wish you would have posted this 24 hours ago.
Dang, if I only knew that sooner!
Then I hope it will be helpful to someone else
May 22, 2012, 03:07:34 PM
It took me about 4 hours last night to figure this out.
I wish you would have posted this 24 hours ago.
I wish you would have posted this 24 hours ago.
May 22, 2012, 01:55:17 PM
I have determined that BAMT does not contain the proper serial support needed to create the ttyUSB* files.
Just want to note the solution to that issue here (this has been posted by somebody elsewhere too), since I searched for it a while ago and it's somewhat frustrating to find this thread without the obvious solution for the generic Linux user without automatic ttyUSB mapping:
Depending on yourLinux distro your BFL might not show as a ttyUSB* device.
If you do a
Code:
ls /dev/ttyUSB*
and nothing shows up thenCode:
sudo modprobe ftdi_sio vendor=0x0403 product=0x6014
sudo chmod a+rw /dev/ttyUSB*
sudo chmod a+rw /dev/ttyUSB*
This reqires that you have general USB device support installed.
I got the vendor/product pair from dmesg (after plugging in the Single)
Code:
dmesg | grep -i bitforce
to find the USB device numberCode:
dmesg | grep -i vendor
to find the vendor/product codes (use the one with the matching USB device number)compile cgminer with
Code:
./configure --enable-bitforce
and then
Code:
cgminer -S auto
and all the usual other parameters, should find your BFL Single. 
March 08, 2012, 05:58:58 PM
Yep there are issues with --scan-serial
If you have both Icarus and Bitforce enabled and plug in an Icarus, the "auto" will hang.
Luke-jr posted a hack pull (well I consider it a hack) to work around that.
But it needs some work still as I have mentioned in 2 other threads.
Clearly specifying --scan-serial each device is the most reliable method at the moment.
If you have both Icarus and Bitforce enabled and plug in an Icarus, the "auto" will hang.
Luke-jr posted a hack pull (well I consider it a hack) to work around that.
But it needs some work still as I have mentioned in 2 other threads.
Clearly specifying --scan-serial each device is the most reliable method at the moment.
March 08, 2012, 04:48:55 PM
Just got 3 BFL Singles working.
I'm on ubuntu.
--scan-serial auto only detected the first device.
So for the cgminer command line you should expect somthing like this:
Happy hashing.
I'm on ubuntu.
--scan-serial auto only detected the first device.
So for the cgminer command line you should expect somthing like this:
Code:
CGMCMD="./cgminer \
-o $MINERPOOL1:$MINERPORT1 -u $MINERUSER1 -p $MINERPASS1 \
-o $MINERPOOL2:$MINERPORT2 -u $MINERUSER2 -p $MINERPASS2 \
-o $MINERPOOL3:$MINERPORT3 -u $MINERUSER3 -p $MINERPASS3 \
--scan-serial /dev/ttyUSB0 \
--scan-serial /dev/ttyUSB1 \
--scan-serial /dev/ttyUSB2 \
--failover-only \
--disable-gpu \
--submit-stale \
"
echo $CGMCMD
cd $HOME/bfl
exec gnome-terminal --command="$CGMCMD" --title="BFL" --geometry=104x44-0+0 &
Disclaimer: This may have been fixed recently, but I don't think anyone has been working on this. Luke-Jr may have, I'll check out the most recent source later. But I KNOW this works.-o $MINERPOOL1:$MINERPORT1 -u $MINERUSER1 -p $MINERPASS1 \
-o $MINERPOOL2:$MINERPORT2 -u $MINERUSER2 -p $MINERPASS2 \
-o $MINERPOOL3:$MINERPORT3 -u $MINERUSER3 -p $MINERPASS3 \
--scan-serial /dev/ttyUSB0 \
--scan-serial /dev/ttyUSB1 \
--scan-serial /dev/ttyUSB2 \
--failover-only \
--disable-gpu \
--submit-stale \
"
echo $CGMCMD
cd $HOME/bfl
exec gnome-terminal --command="$CGMCMD" --title="BFL" --geometry=104x44-0+0 &
Happy hashing.
February 28, 2012, 07:06:35 PM
I have not written API support yet - no bounty oh well I'll consider it some time in the future 
Well I don't have one yet, but I'll contribute 5 BTC to you to write in the support.
https://bitcointalksearch.org/topic/bounty-35-btc-integrate-support-for-other-devices-in-the-cgminer-api-66699
February 28, 2012, 06:48:42 PM
I have not written API support yet - no bounty oh well I'll consider it some time in the future
Well I don't have one yet, but I'll contribute 5 BTC to you to write in the support.
February 28, 2012, 03:09:57 PM
I have not written API support yet - no bounty oh well I'll consider it some time in the future
Luke-jr wrote the BFL support but didn't bother adding the API code (even after I pointed that out to him)
(The first post says "LINUX" not BAMT - thus my last post was actually correct)
Edit: ...
https://bitcointalksearch.org/topic/m.738661
Luke-jr wrote the BFL support but didn't bother adding the API code (even after I pointed that out to him)
(The first post says "LINUX" not BAMT - thus my last post was actually correct
)Edit: ...
https://bitcointalksearch.org/topic/m.738661
February 28, 2012, 10:55:45 AM
We are close.... I can smell it.
That's good to know. I spent some time without BAMT on my rigs...never again.
I know the feeling. Compiling shit and trying to find everything to get ubuntu setup with cgminer is quite a chore. BAMT is my friend.
February 28, 2012, 10:47:15 AM
We are close.... I can smell it.
That's good to know. I spent some time without BAMT on my rigs...never again.
February 28, 2012, 10:32:08 AM
Hey gigavps I saw in the cgminer thread you got this mostly working?? Would you mind sharing what was needed for BAMT + cgminer + BFL? (given there was bounty, no would be a perfectly reasonable answer here)
Hi gnar1ta$,
The bounty has gone to lodcrappo (the creator of BAMT) as he was able to log into my rig and figure out what was needed to get the debian OS to recognize the single. There kernel mod was there but not enabled and there were a couple other things he did to get it working.
Lodcrappo created fix #7 for BAMT 0.5 to distribute this to the masses.
I now have the single plugged into a BAMT rig and cgminer recognizes it and runs it. Unfortunately, the gpumon and mgpumon tools are based on gpus and not devices and the cgminer api call "devs" does not return the BFL device, so no monitoring.
We are close.... I can smell it.
February 28, 2012, 10:21:31 AM
Hey gigavps I saw in the cgminer thread you got this mostly working?? Would you mind sharing what was needed for BAMT + cgminer + BFL? (given there was bounty, no would be a perfectly reasonable answer here)
February 27, 2012, 08:25:51 PM
Thanks for the help. I have determined that BAMT does not contain the proper serial support needed to create the ttyUSB* files. Moving on to ubuntu this evening....
I am interested to know how this was "determined" ?
By my non existent linux skills..... hence the bounty for some help.
February 27, 2012, 05:18:39 PM
Thanks for the help. I have determined that BAMT does not contain the proper serial support needed to create the ttyUSB* files. Moving on to ubuntu this evening....
I am interested to know how this was "determined" ?
February 27, 2012, 02:48:01 PM
gigavps,
I'm not familiar with BAMT, but assuming it is a typical Linux distro try this to narrow down the problem:
1) ensure that you have common module usbserial installed:
2) post output of
3) post output of
4) ensure that your cgminer supports FPGAs:
If any of those fail, you'll have to try with a standard Ubuntu and cgminer built with BitForce support.
I'm not familiar with BAMT, but assuming it is a typical Linux distro try this to narrow down the problem:
1) ensure that you have common module usbserial installed:
Code:
lsmod | grep serial
should display usbserial2) post output of
Code:
dmesg
shortly after you plugged in the BitForce. Code:
dmesg | grep tty
should contain 'ttyUSBx'3) post output of
Code:
lsusb -v
4) ensure that your cgminer supports FPGAs:
Code:
./cgminer -h | grep Built | grep bitforce
If any of those fail, you'll have to try with a standard Ubuntu and cgminer built with BitForce support.
Thanks for the help. I have determined that BAMT does not contain the proper serial support needed to create the ttyUSB* files. Moving on to ubuntu this evening....
February 27, 2012, 02:35:53 PM
Had a try at this over the weekend but nothing yet....
Found this post from BFL stating that they find BFL singles with ttyUSB* in the /dev folder in linux.
https://bitcointalksearch.org/topic/m.692304
I am guessing my problem is that BAMT doesn't have any ttyUSB* files in the /dev folder. Can anyone elaborate how this can be fixed? Looks like I have the following tty files...
tty*
ttyS*
gigavps,Found this post from BFL stating that they find BFL singles with ttyUSB* in the /dev folder in linux.
https://bitcointalksearch.org/topic/m.692304
I am guessing my problem is that BAMT doesn't have any ttyUSB* files in the /dev folder. Can anyone elaborate how this can be fixed? Looks like I have the following tty files...
tty*
ttyS*
I'm not familiar with BAMT, but assuming it is a typical Linux distro try this to narrow down the problem:
1) ensure that you have common module usbserial installed:
Code:
lsmod | grep serial
should display usbserial2) post output of
Code:
dmesg
shortly after you plugged in the BitForce. Code:
dmesg | grep tty
should contain 'ttyUSBx'3) post output of
Code:
lsusb -v
4) ensure that your cgminer supports FPGAs:
Code:
./cgminer -h | grep Built | grep bitforce
If any of those fail, you'll have to try with a standard Ubuntu and cgminer built with BitForce support.
February 27, 2012, 01:46:22 PM
Had a try at this over the weekend but nothing yet....
Found this post from BFL stating that they find BFL singles with ttyUSB* in the /dev folder in linux.
https://bitcointalksearch.org/topic/m.692304
I am guessing my problem is that BAMT doesn't have any ttyUSB* files in the /dev folder. Can anyone elaborate how this can be fixed? Looks like I have the following tty files...
tty*
ttyS*
Found this post from BFL stating that they find BFL singles with ttyUSB* in the /dev folder in linux.
https://bitcointalksearch.org/topic/m.692304
I am guessing my problem is that BAMT doesn't have any ttyUSB* files in the /dev folder. Can anyone elaborate how this can be fixed? Looks like I have the following tty files...
tty*
ttyS*
February 26, 2012, 08:43:28 AM
My friend in China that I have been helping a little bit with the Icarus code is posting my two Icarus' to me tomorrow.
So I'll try to sort out the 'auto' for Icarus after I get them
However, I'm not sure there is a tidy and quick way to auto detect an Icarus, among many devices, with it's current firmware.
Had a look at the Icarus code/protocol and got an idea on what you mean. Basically you could screw an Icarus' state machine by sending a BFL ID request command. If you knew that the BitForces are ignoring the Icarus work commands, you could just scan for Icarus devices first and then look for BitForces.So I'll try to sort out the 'auto' for Icarus after I get them
However, I'm not sure there is a tidy and quick way to auto detect an Icarus, among many devices, with it's current firmware.
Anyone started working on X6500 support? Maybe the FPGA miner devs need to agree on a common protocol if they want to get natively supported by cgminer...
February 26, 2012, 06:45:42 AM
My friend in China that I have been helping a little bit with the Icarus code is posting my two Icarus' to me tomorrow.
So I'll try to sort out the 'auto' for Icarus after I get them
However, I'm not sure there is a tidy and quick way to auto detect an Icarus, among many devices, with it's current firmware.
So I'll try to sort out the 'auto' for Icarus after I get them
However, I'm not sure there is a tidy and quick way to auto detect an Icarus, among many devices, with it's current firmware.
Jump to: