Re: linux-gpib-4.3.0 on Ubuntu 18..04 LTS with multiple NI-GPIB-HS (help please)

dave penkler <[email protected]>
Newsgroups gmane.linux.hardware.gpib.general
Message-ID <CAL=kjP02wWQzDBb=sNPEvOwm1jTKpqBC0_zXC8H3UumfSVvE0g@mail.gmail.com>
Hi Ron,
Your build steps look fine.
To see whether the udev scripts are being run: sudo grep gpib
/var/log/messages
If you do: lsmod | grep gpib
do you see the modules gpib_common and ni_usb_gpib ?
If not there was probably an issue with the build of the kernel modules in
which case please send the kernel module build console log.
cheers,
-Dave

On Tue, 17 Sep 2019 at 08:35, <[email protected]> wrote:

> Greetings,
>
> My apologies in advance for asking a general question. I'm struggling with
> installing linux-gpib-4.3.0 on Ubuntu-18.04LTS and getting a single
> NI-GPIB-HS controller to work (and I need to run two at the same time). Has
> anyone had success doing this? If so, I'm hoping you can help me figure out
> what I'm doing wrong.
>
> I've had linux-gpib-4.2.0 running in the past on Ubuntu 16.04 LTS with a
> single NI-GPIB-HS, but it has been a long time since I set that up, and my
> notes of that installation process aren't the best.
>
> The general outline of what I have done for this 4.3.0 attempt is:
>
> 1) tar -zxvf linux-gpib-4.3.0.tar.gz, and then changed to the created
> directory and performed similar tar operation for the kernel and user files
>
> 2) in the kernel directory: make followed by sudo make install. I saw
> something on the output about SSL errors, but things were created in the
> /lib/modules/kernel_version/gpib directory so I thought I was okay. Maybe
> that is a false assumption
>
> 3) in the user directory: ./configure --sysconfdir=/etc then make followed
> by sudo make install
>
> 4) created the gpib group and added myself to that group
>
> 5) Edited the contents of the 98-gpib-generic.rules file to set the serial
> number for the first NI-GPIB-HS controller
>
> 6) rebooted the computer
>
> I've tried the gpib_config command with the NI-GPIB-HS plugged in, and I
> get the following: failed to open device file '/dev/gpib0'
> main: No such file or directory
>
> I've tried using "udevadm monitor -e"  and I can see when the device gets
> plugged in, but I'm not sure what I should be seeing that shows me that the
> udev rules were processed correctly.
>
> Any suggestions on how to further diagnose what I've done wrong are
> greatly appreciated. If attachments are allowed, I will gladly send the
> contents of the configuration files and the captured output from my attempt
> at monitoring udev.
>
> Regards,
>
> Ron
>
>
> _______________________________________________
> Linux-gpib-general mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>

_______________________________________________
Linux-gpib-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.