Menu
▾
▴
Re: [Linux-gpib-general] linux-gpib-4.3.0 on Ubuntu 18..04 LTS with multiple NI-GPIB-HS (help please)
|
From: Rob L. <ro...@pd...> - 2019-09-17 18:33:15
|
Hi, For your information, this was my issue: My libgpib stuff is located in /usr/local/lib and file /etc/ld.so.conf.d/libc.conf was available and refers to /usr/local/lib, but I did not run ldconfig and logout/login! Greetings, Rob Lassche On 9/17/19 2:37 PM, ron...@uf... wrote: > > Dave and Roel, > > Thank you very much for your quick and informative responses. > > Dave: I ran the lsmod | grep gpib command, and didn't see anything. > > Roel: In conjunction with Dave's response about looking at the console > log, and your keying in on the depmod issue, I paid better attention > when I ran the sudo make install command on the linux-kernel stuff. I > missed an important error about a missing System.map file > > After poking around a bit, I found out I had the two following > directories: > > /usr/src/linux-headers-5.0.0-27 and > /usr/src/linux-headers-5.0.0-27-generic > > The first one had a symbolic link from System.map back to > /boot/System.map-5.0.0-27-generic, while the second directory did not. > So, not really knowing if it would work, I created the symbolic link > in the /usr/src/linux-headers-5.0.0-27-generic directory. > > I then did the make, sudo make install on the linux-gpib-kernel stuff > and that error went away. I now get the following when I run the > lsmod command > > lsmod | grep gpib > ni_usb_gpib 36864 1 > gpib_common 45056 3 ni_usb_gpib > > I have edited the 98-gpib-generic.rules file for the two different > NI-USB-HS devices that I have based on serial number, and when I watch > the logs they are attaching to the correct bus interfaces (0 or 1 > depending on the serial number). > > From what I can tell, things appear to be working. I wouldn't have > reached this step without your assistance. Thank you! > > Ron > > On 2019-09-17 06:37, Roel Jordans wrote: > >> Hi Ron >> >> If your modules are missing see if it helps to run depmod as root >> again. I've seen some cases where the module dependency list of the >> kernel wasn't properly updated on Ubuntu 18.04 after an install which >> resulted in it not being able to load the modules. >> >> Cheers, >> >> Roel >> >> On 17-09-19 11:33, dave penkler wrote: >>> 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, <ron...@uf... >>> <mailto:ron...@uf...>> 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 >>> Lin...@li... >>> <mailto:Lin...@li...> >>> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general >>> >>> >>> >>> _______________________________________________ >>> Linux-gpib-general mailing list >>> Lin...@li... >>> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general >> >> _______________________________________________ >> Linux-gpib-general mailing list >> Lin...@li... >> <mailto:Lin...@li...> >> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general > > > _______________________________________________ > Linux-gpib-general mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linux-gpib-general |
