Running Under Linux » History » Version 17
Tony Fuller, 03/06/2022 03:41 AM
1 | 1 | Dan Smith | h1. Running CHIRP Under Linux |
---|---|---|---|
2 | |||
3 | {{>toc}} |
||
4 | |||
5 | CHIRP's preferred platform is Linux. By far the best way to get CHIRP running is to use one of the binary package repositories provided and maintained by volunteers. If you are running an obscure or old distribution, you may need to install it manually from the source tarball. |
||
6 | |||
7 | h2. Ubuntu package via PPA |
||
8 | |||
9 | This is super quick and easy if you're running a reasonably new version of Ubuntu. Simply run the following in a terminal: |
||
10 | |||
11 | 10 | Tom Hayward | sudo apt-add-repository ppa:dansmith/chirp-snapshots |
12 | 15 | Tony Fuller | sudo add-apt-repository ppa:nrbrtx/python2-stuff # Older installations of Ubuntu do not need this (20.04 and earlier) |
13 | 1 | Dan Smith | sudo apt-get update |
14 | 11 | Tom Hayward | sudo apt-get install chirp-daily |
15 | 1 | Dan Smith | |
16 | 12 | Tom Hayward | Look for CHIRP under your distribution's applications menu. |
17 | 1 | Dan Smith | |
18 | h2. Fedora package via the D-RATS RPM repository |
||
19 | |||
20 | This too is quite easy. First, we install the repository RPM and then CHIRP itself. From a terminal: |
||
21 | |||
22 | 3 | Dan Smith | rpm -Uvfh http://d-rats.com/yum/f11/d-rats-repo-0.1.2-1.fc11.noarch.rpm |
23 | 1 | Dan Smith | yum install chirp |
24 | |||
25 | 2 | Dan Smith | Look for CHIRP under your distribution's applications menu. |
26 | 15 | Tony Fuller | |
27 | h2. Installing the flatpak (Ubuntu/Debian example) |
||
28 | |||
29 | 17 | Tony Fuller | First you will need the flatpak package from your distribution. Check https://www.flatpak.org/setup/ for other distribution instructions |
30 | 15 | Tony Fuller | |
31 | sudo apt install flatpak |
||
32 | sudo flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo |
||
33 | |||
34 | Next download the latest flatpak bundle from https://trac.chirp.danplanet.com/chirp_daily/LATEST/ |
||
35 | It will probably be saved in your Downloads directory so |
||
36 | |||
37 | cd ~/Downloads |
||
38 | sudo flatpak install chirp-daily-*.flatpak |
||
39 | |||
40 | 16 | Tony Fuller | You may need to log in and log out to see CHIRP in your distribution's applications menu. |
41 | If you can't wait to start CHIRP run |
||
42 | 15 | Tony Fuller | |
43 | flatpak run com.danplanet.chirp |
||
44 | 2 | Dan Smith | |
45 | 1 | Dan Smith | h2. Manual installation from source |
46 | |||
47 | 2 | Dan Smith | If you are here, you are probably running an old or obscure distribution, or you want to run from source for some other reason (such as testing a daily build). Before you start, make sure that the required python modules are installed on your system. Some suggestions on how to do this are: |
48 | |||
49 | 16 | Tony Fuller | * Ubuntu/Debian: @apt-get install python-gtk python-serial python-libxml2 python-future@ |
50 | * Fedora/RedHat: @yum install pyserial pygtk2 libxml2-python python2-futures@ |
||
51 | 2 | Dan Smith | |
52 | Next, grab the source tarball from the [[Download]] page and save it somewhere like your home directory and then unpack it: |
||
53 | 1 | Dan Smith | |
54 | tar xzf chirp-0.1.12.tar.gz |
||
55 | cd chirp-0.1.12 |
||
56 | |||
57 | From here, the easiest thing is to just launch CHIRP directly without installing it onto your system. Don't worry, this works just fine and CHIRP will be fully functional. Simply run the following: |
||
58 | |||
59 | ./chirpw |
||
60 | |||
61 | Once you've tested that it runs on your system, you may want to install it permanently. To do this, run the setup routine by doing: |
||
62 | |||
63 | sudo python setup.py install |
||
64 | |||
65 | When finished, you should be able to run "chirpw" from anywhere on your system, and (with luck) you'll also have an item in your distribution's applications menu. |
||
66 | 4 | Jeff Otterson | |
67 | 6 | Jens Jensen | h2. serial port permissions |
68 | 7 | Jens Jensen | |
69 | 16 | Tony Fuller | Note that you may need to adjust permissions on the /dev/tty(something) device, or add your users who want to use CHIRP to the "dialout" group in order to let non-privileged users access the serial device. |
70 | 8 | Jens Jensen | |
71 | This issue is often indicated by an "access denied" error when accessing serial port. |
||
72 | 9 | Jens Jensen | |
73 | 14 | Pavel Milanes | On most Linux distros this is accomplished with: |
74 | 9 | Jens Jensen | <pre> |
75 | 13 | Pavel Milanes | sudo addgroup "$USERNAME" dialout |
76 | 1 | Dan Smith | </pre> |
77 | 13 | Pavel Milanes | |
78 | You will then need to log out and back in for it to take effect. |