#1 Bitcoin on Linux
Posted: Tue Oct 14, 2014 1:38 am
Well I tried to get Bitcoin to run on Linux. What I did was
I already have Boinc 7.2.42 install from the ubuntu repository, plus the 32 bit libs etc. and running primegrid. I plugged in the miner ( BFL Jalapeno ) then
To check if the drivers are loaded (tutorial derived from here: http://ftdi-usb-sio.sourceforge.net/),
run this command
lsusb | grep -i ft
and you should see a readout like this:
Bus 001 Device 031: ID 0403:6014 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
where the 0403 is the vendor ID and 6014 is the product ID or at least in the case of my Jalapeno
run this command to manually probe for the device
modprobe ftdi_sio vendor=0x403 product=0x6014 (you may have to change the vendor or product ID for your device)
to test that it worked run this
dmesg | tail
and you should see a readout similar to this:
USB Serial support registered for FTDI USB Serial Device
ftdi_sio 1-5.6:1.0: FTDI USB Serial Device converter detected
usb 1-5.6: Detected FT8U232AM
usb 1-5.6: Number of endpoints 2
usb 1-5.6: Endpoint 1 MaxPacketSize 64
usb 1-5.6: Endpoint 2 MaxPacketSize 64
usb 1-5.6: Setting MaxPacketSize 64
usb 1-5.6: FTDI USB Serial Device converter now attached to ttyUSB0
usbcore: registered new interface driver ftdi_sio
ftdi_sio: v1.5.0:USB FTDI Serial Converters Driver
once you've loaded the drivers properly,
check to see that your device is listed under connected USB devices by running:
ls -l /dev/ttyUSB*
If it is listed, which by now there should be no chance it is not you need to change the USB permissions of the device by running:
chmod 666 /dev/ttyUSB*
I couldn't change permission so I did
So far the user 'boinc' is not allowed to access the USB devices, we will change that now. To do so we need to change the udev rules (or better add one)
As root (sudo....) create a file in the directory /etc/udev/rules.d/ the filename is 50-group.rules, with the following content
# /etc/udev/rules.d/50-group.rules
SUBSYSTEM!="usb", GOTO="skip_rule"
ACTION=="add", GROUP="plugdev"
LABEL="skip_rule"
This will add a rule that whenever a usb device is added the group for the device-file is set to 'plugdev'. This group already exists on ubuntu .
To activate the rule the 'udev' service needs to be restarted
sudo service udev restart
Now unplug the miner devices, wait a little bit and replug them
Now we need to add the user 'boinc' to the group 'plugdev'
sudo usermod -a -G plugdev boinc
to check the group has been added I did
sudo apt-get install members
once installed I did
members plugdev and checked that it returned my account and boinc.
I then attached to Bitcoin through BAMStats.
It successfully attached to the project and downloaded the master file etc. but so far I have not managed to get a unit to crunch. Update simply returns no units available, so I guess I am fighting the Boinc scheduler but as I already have Boinc installed and all set up I have no desire to download the latest beta from berkley and install separately. I don't run Boinc with the plan class for ASICs on windows so I don't see why I would get this to work the same on windows.
Any comments on what might be wrong please let me know.
more info here https://forums.butterflylabs.com/showwi ... ux+distros
and
http://www.bitcoinutopia.net/bitcoinuto ... php?id=473
I already have Boinc 7.2.42 install from the ubuntu repository, plus the 32 bit libs etc. and running primegrid. I plugged in the miner ( BFL Jalapeno ) then
To check if the drivers are loaded (tutorial derived from here: http://ftdi-usb-sio.sourceforge.net/),
run this command
lsusb | grep -i ft
and you should see a readout like this:
Bus 001 Device 031: ID 0403:6014 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
where the 0403 is the vendor ID and 6014 is the product ID or at least in the case of my Jalapeno
run this command to manually probe for the device
modprobe ftdi_sio vendor=0x403 product=0x6014 (you may have to change the vendor or product ID for your device)
to test that it worked run this
dmesg | tail
and you should see a readout similar to this:
USB Serial support registered for FTDI USB Serial Device
ftdi_sio 1-5.6:1.0: FTDI USB Serial Device converter detected
usb 1-5.6: Detected FT8U232AM
usb 1-5.6: Number of endpoints 2
usb 1-5.6: Endpoint 1 MaxPacketSize 64
usb 1-5.6: Endpoint 2 MaxPacketSize 64
usb 1-5.6: Setting MaxPacketSize 64
usb 1-5.6: FTDI USB Serial Device converter now attached to ttyUSB0
usbcore: registered new interface driver ftdi_sio
ftdi_sio: v1.5.0:USB FTDI Serial Converters Driver
once you've loaded the drivers properly,
check to see that your device is listed under connected USB devices by running:
ls -l /dev/ttyUSB*
If it is listed, which by now there should be no chance it is not you need to change the USB permissions of the device by running:
chmod 666 /dev/ttyUSB*
I couldn't change permission so I did
So far the user 'boinc' is not allowed to access the USB devices, we will change that now. To do so we need to change the udev rules (or better add one)
As root (sudo....) create a file in the directory /etc/udev/rules.d/ the filename is 50-group.rules, with the following content
# /etc/udev/rules.d/50-group.rules
SUBSYSTEM!="usb", GOTO="skip_rule"
ACTION=="add", GROUP="plugdev"
LABEL="skip_rule"
This will add a rule that whenever a usb device is added the group for the device-file is set to 'plugdev'. This group already exists on ubuntu .
To activate the rule the 'udev' service needs to be restarted
sudo service udev restart
Now unplug the miner devices, wait a little bit and replug them
Now we need to add the user 'boinc' to the group 'plugdev'
sudo usermod -a -G plugdev boinc
to check the group has been added I did
sudo apt-get install members
once installed I did
members plugdev and checked that it returned my account and boinc.
I then attached to Bitcoin through BAMStats.
It successfully attached to the project and downloaded the master file etc. but so far I have not managed to get a unit to crunch. Update simply returns no units available, so I guess I am fighting the Boinc scheduler but as I already have Boinc installed and all set up I have no desire to download the latest beta from berkley and install separately. I don't run Boinc with the plan class for ASICs on windows so I don't see why I would get this to work the same on windows.
Any comments on what might be wrong please let me know.
more info here https://forums.butterflylabs.com/showwi ... ux+distros
and
http://www.bitcoinutopia.net/bitcoinuto ... php?id=473