I am running Buster on a Raspberry pi 3B and trying to install linpac-0.28. Here is where it stops after ./configure.
pi@bagiw:~/Downloads/linpac-0.28 $ ./configure
checking build system type... armv7l-unknown-linux-gnueabi
checking host system type... armv7l-unknown-linux-gnueabi
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for ar... ar
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking whether we are using the GNU C++ compiler... (cached) yes
checking whether g++ accepts -g... (cached) yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking dependency style of g++... (cached) gcc3
checking whether ln -s works... yes
checking for perl... /usr/bin/perl
checking for listen... no
checking for axlisten... /usr/bin/axlisten
checking for ANSI C header files... (cached) yes
checking linux/ax25.h usability... yes
checking linux/ax25.h presence... yes
checking for linux/ax25.h... yes
checking for socklen_t... present
checking the AX.25 implementation... old AX.25
checking for main in -lncurses... no
configure: error: ncurses library not found !
pi@bagiw:~/Downloads/linpac-0.28 $
I am not a linux guy. Just trying to follow some instruction from the net to get it working.
Many thanks for any help to get it running on a raspberry pi 3B.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Update: Looks like I got the linpac installed and working. How did I do it? Well, I followed different sites on installing linpac on raspberry pi until I got what I need to install BEFORE compiling linpac 0.29, or even 0.28.
Having said that, I am still having problems keying my IC-7100.
I am using Hamlib for rig control (not sure if I need it but as I said, I followed some instruction on other site), Direwolf as a software TNC, and Linpac. It looks like Direwolf is not used as I don't see any activity when trying to connect to my bbs via the linpac.
I might be doing something wrong but I can't figure out what might be.
Again, any help is really appreciated.
Max
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Maximo,
You are mixing discussions and your keying issue has nothing to do with LInpac. I would recommend to join the direwolf@groups.io email list at https://github.com/wb2osz/direwolf where myself and others can better help you and stay on topic. In that post, please mention how your Linux computer is connected to your IC-7100, etc.
--David
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It's looking like the README needs a cleanup as it's giving some misleading detail.
The issue you're seeing here is that you're in the "~/Downloads/linuxax25" directory used for the AX25 stuff but then you're trying to follow the Linpac compilation instructions. They are very different things! The missing line is it was assumed you already have the Linpac sources and you're in that directory. That makes sense if you're reading the README from within the downloaded Linpac source directory but not if you're reading from say https://sourceforge.net/p/linpac/linpac/ci/master/tree/README .
So.. what you want to do is run:
git clone git://git.code.sf.net/p/linpac/linpac linpac
cd linpac
autoreconf --install
./configure
--David
--David
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That is correct. For your previous post above stating :
"I am using Hamlib for rig control (not sure if I need it but as I said, I followed some instruction on other site), Direwolf as a software TNC, and Linpac. It looks like Direwolf is not used as I don't see any activity when trying to connect to my bbs via the linpac."
To use Linpac, you must configure Linux's AX.25 stack for it to function. The setup is radio --> direwolf --> Linux AX.25 stack --> Linpac.
If you're looking for a complete setup guide, you can see my Packet Radio on Raspberry Pi documentation which applies for any Debian-style OS:
I thought I have AX.25 stack installed. I edited /etc/ax25/axports;
vhfp DU2UXH-2 9600 255 2 VHF Packet 1200 bps
I did also run kissattach:
$ sudo kissattach /dev/pts/2 vhfp
AX.25 port vhfp bound to device ax0
$ sudo kissparms -p radio -t 100 -s 100 -r 25
Running direwolf:
$ direwolf -t 0 -p
Dire Wolf DEVELOPMENT version 1.7 E (Jun 14 2022)
Includes optional support for: hamlib cm108-ptt
Reading config file direwolf.conf
Audio input device for receive: stdin (channel 0)
Audio out device for transmit: plughw:2,0 (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate / 3.
Hamlib error: Unknown rig model 3070. Run "rigctl --list" for a list of model numbers.
Ready to accept AGW client application 0 on port 8000 ...
Ready to accept KISS TCP client application 0 on port 8001 ...
Virtual KISS TNC is available on /dev/pts/2
Created symlink /tmp/kisstnc -> /dev/pts/2
Invalid transmit channel 8 from KISS client app.
Are you using AX.25 for Linux? It might be trying to use a modified
version of KISS which uses the channel field differently than the
original KISS protocol specification. The solution might be to use
a command like "kissparms -c 1 -p radio" to set CRC none mode.
Another way of doing this is pre-loading the "kiss" kernel module with CRC disabled:
sudo /sbin/modprobe -q mkiss crc_force=1
<<< Data frame from KISS client application, port 8, total length = 18
000: 80 88 b0 64 86 82 a4 e2 88 aa 64 aa b0 90 61 3f ...d......d...a?
010: b4 f0 ..
Invalid transmit channel 2 from KISS client app.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Your newest post has nothing to due with Linpac and is a general Direwolf question. Please post that on the direwolf@groups.io email list and the team can help resolve that issue.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am running Buster on a Raspberry pi 3B and trying to install linpac-0.28. Here is where it stops after ./configure.
pi@bagiw:~/Downloads/linpac-0.28 $ ./configure
checking build system type... armv7l-unknown-linux-gnueabi
checking host system type... armv7l-unknown-linux-gnueabi
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for ar... ar
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking whether we are using the GNU C++ compiler... (cached) yes
checking whether g++ accepts -g... (cached) yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking dependency style of g++... (cached) gcc3
checking whether ln -s works... yes
checking for perl... /usr/bin/perl
checking for listen... no
checking for axlisten... /usr/bin/axlisten
checking for ANSI C header files... (cached) yes
checking linux/ax25.h usability... yes
checking linux/ax25.h presence... yes
checking for linux/ax25.h... yes
checking for socklen_t... present
checking the AX.25 implementation... old AX.25
checking for main in -lncurses... no
configure: error: ncurses library not found !
pi@bagiw:~/Downloads/linpac-0.28 $
I am not a linux guy. Just trying to follow some instruction from the net to get it working.
Many thanks for any help to get it running on a raspberry pi 3B.
Howdy.
I recently loaded this on a Raspberry Pi 4B. Ran into the same problem.
Hit this link and read this install guide. It will tell you what Ncurses Library you need.
https://sourceforge.net/p/linpac/linpac/ci/develop/tree/README
Jeb
Hi.
Thank you for the reply. It's past 9PM here and I will try it tomorrow and update you.
Max
Right.. per the README, you need to install the following other packages:
libax25 ax25-apps libncurses5-dev perl
I think I should also delete the INSTALL file as it's not very helpful here.
--David
Ok. I have read the README many times and, I did the following:
pi@linpac:~$ git clone https://github.com/ve7fet/linuxax25.git. Then,
pi@linpac:~/Downloads $ sudo apt install libax25 ax25-apps libncurses5-dev perl
That went ok. Then, install of automake autoconf - done.
Then,
sudo apt-get install libtool
libtoolize
autoreconf --install
pi@linpac:~/Downloads/linuxax25 $ autoreconf --install
autoreconf: 'configure.ac' or 'configure.in' is required
Question, am I installing only dependencies? Where is linpac-0.29? Sorry to ask. As I said, I am not a linux guy. I am learning the hard way.
Max
Ok, I think I am getting there. It's trial and error process.
So bear with me. Trying to learn.
Max
Update: Looks like I got the linpac installed and working. How did I do it? Well, I followed different sites on installing linpac on raspberry pi until I got what I need to install BEFORE compiling linpac 0.29, or even 0.28.
Having said that, I am still having problems keying my IC-7100.
I am using Hamlib for rig control (not sure if I need it but as I said, I followed some instruction on other site), Direwolf as a software TNC, and Linpac. It looks like Direwolf is not used as I don't see any activity when trying to connect to my bbs via the linpac.
I might be doing something wrong but I can't figure out what might be.
Again, any help is really appreciated.
Max
Hello Maximo,
You are mixing discussions and your keying issue has nothing to do with LInpac. I would recommend to join the direwolf@groups.io email list at https://github.com/wb2osz/direwolf where myself and others can better help you and stay on topic. In that post, please mention how your Linux computer is connected to your IC-7100, etc.
--David
It's looking like the README needs a cleanup as it's giving some misleading detail.
The issue you're seeing here is that you're in the "~/Downloads/linuxax25" directory used for the AX25 stuff but then you're trying to follow the Linpac compilation instructions. They are very different things! The missing line is it was assumed you already have the Linpac sources and you're in that directory. That makes sense if you're reading the README from within the downloaded Linpac source directory but not if you're reading from say https://sourceforge.net/p/linpac/linpac/ci/master/tree/README .
So.. what you want to do is run:
git clone git://git.code.sf.net/p/linpac/linpac linpac
cd linpac
autoreconf --install
./configure
--David
--David
Thanks David.
Ok, let me try that. Thanks again.
That is correct. For your previous post above stating :
"I am using Hamlib for rig control (not sure if I need it but as I said, I followed some instruction on other site), Direwolf as a software TNC, and Linpac. It looks like Direwolf is not used as I don't see any activity when trying to connect to my bbs via the linpac."
To use Linpac, you must configure Linux's AX.25 stack for it to function. The setup is radio --> direwolf --> Linux AX.25 stack --> Linpac.
If you're looking for a complete setup guide, you can see my Packet Radio on Raspberry Pi documentation which applies for any Debian-style OS:
I thought I have AX.25 stack installed. I edited /etc/ax25/axports;
vhfp DU2UXH-2 9600 255 2 VHF Packet 1200 bps
I did also run kissattach:
$ sudo kissattach /dev/pts/2 vhfp
AX.25 port vhfp bound to device ax0
$ sudo kissparms -p radio -t 100 -s 100 -r 25
Running direwolf:
$ direwolf -t 0 -p
Dire Wolf DEVELOPMENT version 1.7 E (Jun 14 2022)
Includes optional support for: hamlib cm108-ptt
Reading config file direwolf.conf
Audio input device for receive: stdin (channel 0)
Audio out device for transmit: plughw:2,0 (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate / 3.
Hamlib error: Unknown rig model 3070. Run "rigctl --list" for a list of model numbers.
Ready to accept AGW client application 0 on port 8000 ...
Ready to accept KISS TCP client application 0 on port 8001 ...
Virtual KISS TNC is available on /dev/pts/2
Created symlink /tmp/kisstnc -> /dev/pts/2
Invalid transmit channel 8 from KISS client app.
Are you using AX.25 for Linux? It might be trying to use a modified
version of KISS which uses the channel field differently than the
original KISS protocol specification. The solution might be to use
a command like "kissparms -c 1 -p radio" to set CRC none mode.
Another way of doing this is pre-loading the "kiss" kernel module with CRC disabled:
sudo /sbin/modprobe -q mkiss crc_force=1
<<< Data frame from KISS client application, port 8, total length = 18
000: 80 88 b0 64 86 82 a4 e2 88 aa 64 aa b0 90 61 3f ...d......d...a?
010: b4 f0 ..
Invalid transmit channel 2 from KISS client app.
Your newest post has nothing to due with Linpac and is a general Direwolf question. Please post that on the direwolf@groups.io email list and the team can help resolve that issue.