#72 wrong(?) install path for the kernel directori

[Zoltan T]

make install failes on my Ubuntu 18.04.3 LTS machine. Sample output below. The same error recurs for every(?)/many files. I think the path where the kernel is has been changed in Ubuntu 18.04. On the other hand I have some doubts, since the base distro is almost two years old.

The script created /lib/modules/4.15.0-74-generic/gpib directory. The crypto directory resides under /lib/modules/4.15.0-74-generic/kernel/crypto. Its relative path is ../kernel/crypto, not ../crypto.

I've got similar results with setting LINUX_SRCDIR. It is not 100% clear what path should I give here.

At main.c:160:
- SSL error:02001002:system library:fopen:No such file or directory: ../crypto/bio/bss_file.c:72
- SSL error:2006D080:BIO routines:BIO_new_file:no such file: ../crypto/bio/bss_file.c:79
sign-file: certs/signing_key.pem: No such file or directory
[...]
  DEPMOD  4.15.0-74-generic
make[1]: Leaving directory '/usr/src/linux-headers-4.15.0-74-generic'

[Frank Mori Hess]

External modules aren't supposed to be installed under the kernel/ subdirectory. They default to going under extra/ but we change that to gpib/ That said, you could try changing INSTALL_MOD_DIR in linux-gpib-kernel/Makefile if you want to change the install location. I don't think the install location is the problem though.

Also, they are external modules so signing isn't expected to work. You could look at /lib/modules/4.15.0-74-generic/build/scripts/Makefile.modinst and Makefile.modsign if you want to figure out what is broken in your distro build system.

[Zoltan T]

I did not want to change the install location. I just wanted to use GPIB
under linux. The default installation settings did not work. I've attached
the output, which has shown that the default settings are not consistent
with the Ubuntu 18.04 LTS environment. I am a simple user, a lab engineer
who wanted to use GPIB under linux. I am not sysadmin, programmer nor linux
guru. The README give me little understanding even after searching the web.
I am afraid that solving this problem is beyond my capabilities for the
tight timeframe I had to make it work. I gave a feedback about an issue,
what seemed unusual to me, because I believe it is necessary to improve
anyhting.

On Mon, Jan 27, 2020 at 8:12 PM Frank Mori Hess fmhess@users.sourceforge.net wrote:

External modules aren't supposed to be installed under the kernel/
subdirectory. They default to going under extra/ but we change that to
gpib/ That said, you could try changing INSTALL_MOD_DIR in
linux-gpib-kernel/Makefile if you want to change the install location. I
don't think the install location is the problem though.

Also, they are external modules so signing isn't expected to work. You
could look at /lib/modules/4.15.0-74-generic/build/scripts/Makefile.modinst
and Makefile.modsign if you want to figure out what is broken in your
distro build system.

---

[bugs:#72] wrong(?) install path for the kernel directori

Status: open
Group: v1.0 (example)
Labels: make install kernel path
Created: Sun Jan 26, 2020 08:20 PM UTC by Zoltan T
Last Updated: Sun Jan 26, 2020 08:20 PM UTC
Owner: nobody

make install failes on my Ubuntu 18.04.3 LTS machine. Sample output
below. The same error recurs for every(?)/many files. I think the path
where the kernel is has been changed in Ubuntu 18.04. On the other hand I
have some doubts, since the base distro is almost two years old.

The script created /lib/modules/4.15.0-74-generic/gpib directory. The
crypto directory resides under
/lib/modules/4.15.0-74-generic/kernel/crypto. Its relative path is
../kernel/crypto, not ../crypto.

I've got similar results with setting LINUX_SRCDIR. It is not 100% clear
what path should I give here.

~~~
At main.c:160:
- SSL error:02001002:system library:fopen:No such file or directory:
../crypto/bio/bss_file.c:72
- SSL error:2006D080:BIO routines:BIO_new_file:no such file:
../crypto/bio/bss_file.c:79
sign-file: certs/signing_key.pem: No such file or directory
[...]
DEPMOD 4.15.0-74-generic
make[1]: Leaving directory '/usr/src/linux-headers-4.15.0-74-generic'
~~~

---

Sent from sourceforge.net because you indicated interest in <
https://sourceforge.net/p/linux-gpib/bugs/72/>

To unsubscribe from further messages, please visit <
https://sourceforge.net/auth/subscriptions/>

[Dieter Herbst]

Hi Zoltan,

I recently had the same problem with my set up. The following link helped me a lot to get my system running:

https://sourceforge.net/p/linux-gpib/code/1862/

The following recipe, which is based on the content the above link points to, is for Linux Mint 19.3 running on an old desktop (i7 CPU 860 and 8GByte RAM and 500GB SSD ).The GPIB controller is a National Instruments GPIB PCI card from 1998. I run successful tests using pyvisa and python3.8.1. Device under test was an Arbitrary Waveform Generator (HP33120A).

To be honest, the procedure does not work on my laptop using a NI GPIB PCMCIA card as controller. After two week of intense work I am nearly convinced that there is something wrong either with the driver or / and with the PCMCIA part of the description (see INSTALL file e.g. cardmgr does not exist in newer kernels).

1. Python
   If you want to use python, you have to install the desired version of python first. (I used python3.8.1)

2. Download the GPIB software
   Download and extract the file linux-gpib-4.3.0.tar.gz from
   https://sourceforge.net/projects/linux-gpib/files/linux-gpib%20for%203.x.x%20and%202.6.x%20kernels/

3. Kernel
   Move to the directory: /linux-gpib-kernel-4.3.0 and change the "Makefile" as follows:

In row 9 of the Makefile remove the leading minus (-) sign:
before: -$(MAKE) -C $(LINUX_SRCDIR) V=$(VERBOSE) modules \
after: $(MAKE) -C $(LINUX_SRCDIR) V=$(VERBOSE) modules \

Save the file and run
$ make
$ sudo make install

You will get several pages of error messages. The trick is to ignore these messages and simply run
$ sudo /sbin/depmod -A

1. User
   Move to /linux-gpib-user-4.3.0 and enter:
   $ ./configure --sysconfdir=/etc PYTHON=python3.8

If you intend to use another version of python you have to adjust PYTHON accordingly.
If you don't care about the version, just run ./configure --sysconfdir=/etc.
Then execute:
$ make
$ sudo make install

Now you have to add the group gpib and make yourself a member of the group
$ sudo groupadd gpib
$ sudo usermod -aG gpib YOUR_USER_NAME

Afterwards you should edit /etc/gpib.conf to set defaults for gpib_config program.

1. Final actions: Loading the driver and running gpib_config.

This of course depends on the type of interface board you use.
$ sudo modprobe tnt4882
$ sudo ldconfig

Finally issue the following command:
$ sudo /gpib_config --minor 0
You are done if this command runs without error.

I hope this recipe will help you to overcome your problem. But use it on your own risk.

dieter

[Pantxo Diribarne]

I don't understand how the answers are related to the original issue which is that make install fails with a bunch or errors related to the module not being signed:

At main.c:160:
- SSL error:02001002:system library:fopen:No such file or directory: ../crypto/bio/bss_file.c:72
- SSL error:2006D080:BIO routines:BIO_new_file:no such file: ../crypto/bio/bss_file.c:79

In order to solve that issue, and to have the modules rebuilt at the next kernel updade, I used dkms, as described here :

## Download the linux gpib source and the attached dkms.conf to 
## e.g. ~/Downloads

## Untar linux gpib
cd ~/Downloads
tar -xf ./linux-gpib-4.3.4.tar.gz -C ./

## Untar linux gpib kernel, add dkms.conf file, and copy the whole 
## directory to /usr/src
cd linux-gpib-4.3.4
tar -xf ./linux-gpib-kernel-4.3.4.tar.gz -C ./
cp ~/Downloads/dkms.conf ./linux-gpib-kernel-4.3.4/
sudo mv ./linux-gpib-kernel-4.3.4 /usr/src/

## Add,build and install the module
sudo dkms add -m linux-gpib-kernel -v 4.3.4
sudo dkms build -m linux-gpib-kernel -v 4.3.4
sudo dkms install -m linux-gpib-kernel -v 4.3.4

## Check the status of the module
dkms status | grep gpib
## -> linux-gpib-kernel, 4.3.4, 5.4.0-99-generic, x86_64: installed

Note that the attached dkms.conf only lists default modules, and one should probably adapt it for building e.g. isa board modules.