My upgrade from Fedora 38 to 39 was smooth. The only thing is that when I tried to install linux-gpib-4.3.6 it complained that the compiler used to build the kernel was different from the gcc that came with the installation. The Fedora upgrade using “cat /proc/version” shows that it was compiled with (gcc (GCC) 13.2.1 20230918 (Red Hat 13.2.1-3) and “gcc -v” shows gcc version 13.2.1 20231011 (Red Hat 13.2.1-4) (GCC). Note the mismatch between 13.2.1-3 for the kernel and 13.2.1-4 for the gcc compiler. I had to revert the gcc compiler to 13.2.1-3 and run ‘make clean’ to fix it. Otherwise I got the “modprobe: ERROR: could not insert ‘agilent_82350b’: Exec format error” when I tried to run “sudo modprobe agilent_82350b”. I’m new to this and assumed that the compiler versions should match with the upgrade done using “Upgrading Fedora Using DNF System Plugin” from fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline. Is this normal?
I cannot find that package in the fedora repos. Where did you retrieve it from?
Is it possibly a typo in the package name?
I did find references to it for debian, ubuntu, and raspios but nowhere was I able to find an rpm version.
I did find this GitHub - vddvss/linux-gpib-packaging: RPM specfiles and patches to install linux-gpib on Fedora related to the 82350B board and it specifically requires firmware before the driver may be loaded.
When installing software that is outside the fedora tree it is often upon the user to carefully read the documentation and follow instructions in the hope that the new software will work properly.
Only when the software is provided within the fedora repos or locally compiled can one be assured the proper compiler and kernel libraries will match. It is certainly unrealistic to expect 3rd party software will match the fedora 39 kernel and packages when it is only 2 days after final release of 39.
You also had a typo in the link provided. It should have been ‘docs.fedoraproject.org’
NVIDIA’s kernel module apparently has a similar requirement that is overridden by RPM Fusion, but I don’t know if it’s this strict.
Your kernel was built during the final freeze, while a gcc update was also waiting for the freeze to end. The next kernel update will use this gcc version, but the next gcc update will make it mismatch again, and so on.
Thank you - I didn’t realize that the gcc versions could be different than the kernel build version. I will pay much closer attention to that for sure! BTW the “Linux GPIB Support” project is hosted on Linux GPIB Support download | SourceForge.net and has been a valuable resource since it started in 2001. I was following the included ‘Install’ instructions when I ran into the ‘Exec format error’ problem and as a novice Fedora user it took me a few days to figure out why.
You could try my repo on Copr to install RPMs for the linux GPIB driver.
I’m using DKMS (Dynamic Kernel Module Support) which will mean that the driver updates with the Kernel.
Thanks Michael - If I have already installed it from the https://sourceforge.net/projects/linux-gpib/files/linux-gpib%20for%203.x.x%20and%202.6.x%20kernels/ do I have to do a ’ ‘make clean’ and reinstall from Copr ? I would really like a DKMS version.
Yes, you should uninstall the autotools version. (keep a copy of /etc/gpib.conf if you’ve customized it)
The package that I made (derivative work of others!) is a lot more convenient in that it automates not only the rebuilding of the kernel module but also the loading of the firmware onto the Agilent/Keysight USB GPIB dongle (using systemd) … see GitHub - VK2BEA/linux-gpib files.
It appears that “vssvdd” (the other GPIB Copr repo) has not updated his package in many years (and there is no build for current Fedora versions).
This is why I decided to “pick up the torch” for Fedora GPIB users!
The version that is currently available is from the latest SVN trunk (as of Friday).
Let me know if you have any problems…