Kernel Module 15.0 Install

R

rpowell47

I've downloaded and burned an ISO image of 15.0 and after the install , I receive the following ERROR when using the startx command:
Code: 
NVRM: API mismatch: the client 'Xorg" (pid 3591)
NVRM: has the version 580.95.95, but this kernel module has
NVRM: the version 580.105.08. Please make sure that this 
NVRM: kernel module and all NVIDIA driver components 
NVRM: have the same version.
I would appreciate any help in how to carry out the issue of changing the kernel module. I used pkg install nvidia-driver and then in the /usr/local/etc/X11/xorg.conf.d file by ee nvidia-driver and placed in that file the following:
Code: 
Section "Device"
   Identifier "Card0"
   Driver "nvidia"
EndSection
Any help will be greatly appreciated.
 
T

Post in thread 'API mismatch on starting xorg'

Are you installing them with pkg?
If so, try deinstalling and install again with restricting repo.

For 15.0, there are 3 repos. One for pkgbase (FreeBSD-base), one for pkg from ports dedicated for kernel modules (FreeBSD-ports-kmods) and for pkg from ports all allowed ones including kernel modules (FreeBSD-ports).
pkg install -r FreeBSD-ports x11/nvidia-driver
could help.

While multiple minor releases are supported for single major release (i.e., 14.3 and 14.2 until the end of September), newer release needs kmods repo, but there can be risks of mis-matching versions, due to...
 
I carried out SirDice's suggestion. But, since I am not able to actually use 15.0, I have to shutdown my 14.3 BSD, then unplug that SSD card and plug in and start the 15.0 SSD card. So, here is what received when I was back to the 15.0 install:
Updtating FreeBSD-ports repository catalogue...
FreeBSD-ports repository is up to date
Checking integrity . . . done (0 conflicting)
The most recent versions of packages are already installed
root@randy:~#
 
rpowell47 said:
I've downloaded and burned an ISO image of 15.0 and after the install , I receive the following ERROR when using the startx command:
Code: 
NVRM: API mismatch: the client 'Xorg" (pid 3591)
NVRM: has the version 580.95.95, but this kernel module has
NVRM: the version 580.105.08. Please make sure that this 
NVRM: kernel module and all NVIDIA driver components 
NVRM: have the same version.
Click to expand...
This is relevant:
Rich (BB code): 
[0-0] #  pkg which /boot/modules/nvidia-modeset.ko /usr/local/lib/xorg/modules/drivers/nvidia_drv.so
/boot/modules/nvidia-modeset.ko was installed by package nvidia-kmod-580.105.08.1500068
/usr/local/lib/xorg/modules/drivers/nvidia_drv.so was installed by package nvidia-driver-580.95.05
[1-0] #
These two need to be of the same version.
nvidia-modeset.ko is referenced by kld_list="nvidia-modeset" in /etc/rc.conf
nvidia-driver.so is referenced by
Rich (BB code): 
Section "Device"
   Identifier "Card0"
   Driver "nvidia"
EndSection
in an appropriate Xorg .conf file.

This may help.
 
Well, by getting the nvida-driver and the same nvidia-kmod the same, I now have mate opening!! BUT, now no mouse??

I’ve added ‘’moused_enable=“YES’ to rc.conf with no luck and added to sysctl.conf “kern.evdev.rcpt_mask=12 - again no mouse. So I shut down 15.0 and tried 14.3 and the mouse works just fine! Again any thoughts will be greatly appreciated!

Also, when I carry out “pciconf -vl” the mouse is not listed? It’s a new Logitech wireless mouse.
 
I installed a new SSD 1TB card and used my DVD 15.0 for installation. After install, I'm dealing with nvidia-driver and nvidia-kmod packages causing a mismatch (driver 580.95 vs kmod 580.119) I carried out the usual freebsd-update fetch and install. The dmesg listing show the mismatch and the /var/xorg/xorg.0.log shows Failed to initialize the NVIDIA kernel module. In my rc.conf file I have kld_list="nvidia-modeset" and in my loader.conf file I have hw.nvidiadrm.modeset=1 - I would appreciate any thoughts about how to remove the mismatch. Every time I introduce the pkg install nvidia-kmod or nvidia-driver it returns the correct 580.95 driver and the 580.95 kmod, but also the 580.119. kmod and I cannot, because of experience, able to delete the 580.119 kmod. Thanks for you thoughts. It seems that pkg repository is causing the issue.
Oh, I also carried out SirDice's suggestion 'pkg install -r FreeBSD-ports x11/nvidia-driver' and his suggestion did not work either. Again Thanks for you thoughts.
 
I suggest disabling the 'FreeBSD-ports-kmods' repository for now. You don't really need it at this point in time. It is likely the cause of the version mismatches.

mkdir -p /usr/local/etc/pkg/repos
echo "FreeBSD-ports-kmods: { enabled: no }" > /usr/local/etc/pkg/repos/FreeBSD.conf
 
In my case, whenever I have Nvidia trouble, I've always been able to fix it (in the last year or so anyway, don't remember before, by doing a port install of nvidia-drm-kmod, whenever I've had an issue after an nvidia update of any sort, e.g., driver, kmod, etc. I generally upgrade with pkg, and I have that set to latest, rather than quarterly. So, if SirDice's advice doesn't work, that would be my next step.
 
Hello SirDice, thank you for your suggestion in #8. The suggestion gave me graphics, thanks, but now I don't have a working mouse. The mouse works on boot-up, after I set it using bsdconfig but not when I load Mate. So I shut down and rebooted and carried out a pkg upgrade -f mate, but still no mouse. What are your thoughts about the issue. Oh, when I reboot to the working SSD with 15.0 the mouse works. However, the SSD I'm trying to setup for a friend, the mouse doesn't work.
 
SirDice said:
Nice :cool:

Remove that moused_enable (you don't need it for USB mice) and that kern.evdev.rcpt_mask=12 sysctl.
Click to expand...
Thanks again SirDice, however, neither of your suggestion gave me a mouse. I removed the mouse_enable and my sysctl.conf didn't have the kern.evdev.rcpt_mask=12 in the my /etc file. I'm pretty sure that you are busy with other issues, so please get back with me whenever you have the time.
 
Post your log, easily done from the command line (assuming the system has internet access): cat /var/log/Xorg.0.log | nc termbin.com 9999

Post the resulting URL here.
 
SirDice said:
Post your log, easily done from the command line (assuming the system has internet access): cat /var/log/Xorg.0.log | nc termbin.com 9999

Post the resulting URL here.
Click to expand...
45.739] (II) config/udev: Adding input device Logitech USB Receiver Mouse (/dev/input/event8)
[ 45.739] (**) Logitech USB Receiver Mouse: Applying InputClass "libinput pointer catchall"
[ 45.739] (II) Using input driver 'libinput' for 'Logitech USB Receiver Mouse'
[ 45.739] (**) Logitech USB Receiver Mouse: always reports core events
[ 45.739] (**) Option "Device" "/dev/input/event8"
[ 45.740] (II) event8 - Logitech USB Receiver Mouse: is tagged by udev as: Mouse
[ 45.741] (II) event8 - Logitech USB Receiver Mouse: device is a pointer
[ 45.742] (II) event8 - Logitech USB Receiver Mouse: device removed
[ 45.743] (II) libinput: Logitech USB Receiver Mouse: Step value 0 was provided, libinput Fallback acceleration function is used.
[ 45.743] (II) libinput: Logitech USB Receiver Mouse: Step value 0 was provided, libinput Fallback acceleration function is used.
[ 45.743] (II) libinput: Logitech USB Receiver Mouse: Step value 0 was provided, libinput Fallback acceleration function is used.
[ 45.743] (**) Option "config_info" "udev:/dev/input/event8"
[ 45.743] (II) XINPUT: Adding extended input device "Logitech USB Receiver Mouse" (type: MOUSE, id 14)
[ 45.743] (**) Option "AccelerationScheme" "none"
[ 45.743] (**) Logitech USB Receiver Mouse: (accel) selected scheme none/0
[ 45.743] (**) Logitech USB Receiver Mouse: (accel) acceleration factor: 2.000
[ 45.743] (**) Logitech USB Receiver Mouse: (accel) acceleration threshold: 4
[ 45.744] (II) event8 - Logitech USB Receiver Mouse: is tagged by udev as: Mouse
[ 45.745] (II) event8 - Logitech USB Receiver Mouse: device is a pointer
[ 45.746] (II) config/udev: Adding input device Logitech USB Receiver Consumer Control (/dev/input/event9)
[ 45.746] (**) Logitech USB Receiver Consumer Control: Applying InputClass "Evdev keyboard"
[ 45.746] (**) Logitech USB Receiver Consumer Control: Applying InputClass "libinput keyboard catchall"
[ 45.746] (II) Using input driver 'libinput' for 'Logitech USB Receiver Consumer Control'
[ 45.746] (**) Logitech USB Receiver Consumer Control: always reports core events
[ 45.746] (**) Option "Device" "/dev/input/event9"
[ 45.747] (II) event9 - Logitech USB Receiver Consumer Control: is tagged by udev as: Keyboard
[ 45.748] (II) event9 - Logitech USB Receiver Consumer Control: device is a keyboard
[ 45.749] (II) event9 - Logitech USB Receiver Consumer Control: device removed
[ 45.750] (**) Option "config_info" "udev:/dev/input/event9"
[ 45.750] (II) XINPUT: Adding extended input device "Logitech USB Receiver Consumer Control" (type: KEYBOARD, id 15)
[ 45.750] (**) Option "xkb_rules" "evdev"
[ 45.751] (II) event9 - Logitech USB Receiver Consumer Control: is tagged by udev as: Keyboard
[ 45.751] (II) event9 - Logitech USB Receiver Consumer Control: device is a keyboard
[ 46.145] (--) NVIDIA(GPU-0): DFP-0: disconnected
[ 46.145] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[ 46.145] (--) NVIDIA(GPU-0): DFP-0: 165.0 MHz maximum pixel clock
[ 46.145] (--) NVIDIA(GPU-0):
[ 46.190] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAGEAR (DFP-1): connected
[ 46.190] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAGEAR (DFP-1): Internal TMDS
[ 46.190] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAGEAR (DFP-1): 600.0 MHz maximum pixel clock
[ 46.190] (--) NVIDIA(GPU-0):
[ 46.191] (--) NVIDIA(GPU-0): DFP-0: disconnected
[ 46.191] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[ 46.191] (--) NVIDIA(GPU-0): DFP-0: 165.0 MHz maximum pixel clock
[ 46.191] (--) NVIDIA(GPU-0):
[ 46.236] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAGEAR (DFP-1): connected
[ 46.236] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAGEAR (DFP-1): Internal TMDS
[ 46.236] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAGEAR (DFP-1): 600.0 MHz maximum pixel clock
[ 46.236] (--) NVIDIA(GPU-0):
[ 46.238] (--) NVIDIA(GPU-0): DFP-0: disconnected
[ 46.238] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[ 46.238] (--) NVIDIA(GPU-0): DFP-0: 165.0 MHz maximum pixel clock
[ 46.238] (--) NVIDIA(GPU-0):
[ 46.282] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAGEAR (DFP-1): connected
[ 46.282] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAGEAR (DFP-1): Internal TMDS
[ 46.282] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAGEAR (DFP-1): 600.0 MHz maximum pixel clock
[ 46.282] (--) NVIDIA(GPU-0):
[ 46.284] (II) NVIDIA(0): Setting mode "HDMI-0: 2560x1440_120 @2560x1440 +0+0 {ViewPortIn=2560x1440, ViewPortOut=2560x1440+0+0}"
[ 46.797] (--) NVIDIA(GPU-0): DFP-0: disconnected
[ 46.797] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[ 46.797] (--) NVIDIA(GPU-0): DFP-0: 165.0 MHz maximum pixel clock
[ 46.797] (--) NVIDIA(GPU-0):
[ 46.842] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAGEAR (DFP-1): connected
[ 46.842] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAGEAR (DFP-1): Internal TMDS
[ 46.842] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAGEAR (DFP-1): 600.0 MHz maximum pixel clock
[ 46.842] (--) NVIDIA(GPU-0):
 
rpowell47 said:
45.739] (II) config/udev: Adding input device Logitech USB Receiver Mouse (/dev/input/event8)
[ 45.739] (**) Logitech USB Receiver Mouse: Applying InputClass "libinput pointer catchall"
[ 45.739] (II) Using input driver 'libinput' for 'Logitech USB Receiver Mouse'
[ 45.739] (**) Logitech USB Receiver Mouse: always reports core events
[ 45.739] (**) Option "Device" "/dev/input/event8"
[ 45.740] (II) event8 - Logitech USB Receiver Mouse: is tagged by udev as: Mouse
[ 45.741] (II) event8 - Logitech USB Receiver Mouse: device is a pointer
[ 45.742] (II) event8 - Logitech USB Receiver Mouse: device removed
[ 45.743] (II) libinput: Logitech USB Receiver Mouse: Step value 0 was provided, libinput Fallback acceleration function is used.
[ 45.743] (II) libinput: Logitech USB Receiver Mouse: Step value 0 was provided, libinput Fallback acceleration function is used.
[ 45.743] (II) libinput: Logitech USB Receiver Mouse: Step value 0 was provided, libinput Fallback acceleration function is used.
[ 45.743] (**) Option "config_info" "udev:/dev/input/event8"
[ 45.743] (II) XINPUT: Adding extended input device "Logitech USB Receiver Mouse" (type: MOUSE, id 14)
[ 45.743] (**) Option "AccelerationScheme" "none"
[ 45.743] (**) Logitech USB Receiver Mouse: (accel) selected scheme none/0
[ 45.743] (**) Logitech USB Receiver Mouse: (accel) acceleration factor: 2.000
[ 45.743] (**) Logitech USB Receiver Mouse: (accel) acceleration threshold: 4
[ 45.744] (II) event8 - Logitech USB Receiver Mouse: is tagged by udev as: Mouse
[ 45.745] (II) event8 - Logitech USB Receiver Mouse: device is a pointer
[ 45.746] (II) config/udev: Adding input device Logitech USB Receiver Consumer Control (/dev/input/event9)
[ 45.746] (**) Logitech USB Receiver Consumer Control: Applying InputClass "Evdev keyboard"
[ 45.746] (**) Logitech USB Receiver Consumer Control: Applying InputClass "libinput keyboard catchall"
[ 45.746] (II) Using input driver 'libinput' for 'Logitech USB Receiver Consumer Control'
[ 45.746] (**) Logitech USB Receiver Consumer Control: always reports core events
[ 45.746] (**) Option "Device" "/dev/input/event9"
[ 45.747] (II) event9 - Logitech USB Receiver Consumer Control: is tagged by udev as: Keyboard
[ 45.748] (II) event9 - Logitech USB Receiver Consumer Control: device is a keyboard
[ 45.749] (II) event9 - Logitech USB Receiver Consumer Control: device removed
[ 45.750] (**) Option "config_info" "udev:/dev/input/event9"
[ 45.750] (II) XINPUT: Adding extended input device "Logitech USB Receiver Consumer Control" (type: KEYBOARD, id 15)
[ 45.750] (**) Option "xkb_rules" "evdev"
[ 45.751] (II) event9 - Logitech USB Receiver Consumer Control: is tagged by udev as: Keyboard
[ 45.751] (II) event9 - Logitech USB Receiver Consumer Control: device is a keyboard
[ 46.145] (--) NVIDIA(GPU-0): DFP-0: disconnected
[ 46.145] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[ 46.145] (--) NVIDIA(GPU-0): DFP-0: 165.0 MHz maximum pixel clock
[ 46.145] (--) NVIDIA(GPU-0):
[ 46.190] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAGEAR (DFP-1): connected
[ 46.190] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAGEAR (DFP-1): Internal TMDS
[ 46.190] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAGEAR (DFP-1): 600.0 MHz maximum pixel clock
[ 46.190] (--) NVIDIA(GPU-0):
[ 46.191] (--) NVIDIA(GPU-0): DFP-0: disconnected
[ 46.191] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[ 46.191] (--) NVIDIA(GPU-0): DFP-0: 165.0 MHz maximum pixel clock
[ 46.191] (--) NVIDIA(GPU-0):
[ 46.236] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAGEAR (DFP-1): connected
[ 46.236] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAGEAR (DFP-1): Internal TMDS
[ 46.236] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAGEAR (DFP-1): 600.0 MHz maximum pixel clock
[ 46.236] (--) NVIDIA(GPU-0):
[ 46.238] (--) NVIDIA(GPU-0): DFP-0: disconnected
[ 46.238] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[ 46.238] (--) NVIDIA(GPU-0): DFP-0: 165.0 MHz maximum pixel clock
[ 46.238] (--) NVIDIA(GPU-0):
[ 46.282] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAGEAR (DFP-1): connected
[ 46.282] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAGEAR (DFP-1): Internal TMDS
[ 46.282] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAGEAR (DFP-1): 600.0 MHz maximum pixel clock
[ 46.282] (--) NVIDIA(GPU-0):
[ 46.284] (II) NVIDIA(0): Setting mode "HDMI-0: 2560x1440_120 @2560x1440 +0+0 {ViewPortIn=2560x1440, ViewPortOut=2560x1440+0+0}"
[ 46.797] (--) NVIDIA(GPU-0): DFP-0: disconnected
[ 46.797] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[ 46.797] (--) NVIDIA(GPU-0): DFP-0: 165.0 MHz maximum pixel clock
[ 46.797] (--) NVIDIA(GPU-0):
[ 46.842] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAGEAR (DFP-1): connected
[ 46.842] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAGEAR (DFP-1): Internal TMDS
[ 46.842] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAGEAR (DFP-1): 600.0 MHz maximum pixel clock
[ 46.842] (--) NVIDIA(GPU-0):
Click to expand...
I'm sorry the above is from my 15.0 install that works. Not the one I'm trying to install for my friend. I tried to get the information on the new drive, but when trying to https://termbin.com/6g9m - not able to connect. However, when I installed FreeBSD 15.0 from my DVD I had the DHCP connected and work just fine.
 
You could try,
cat /etc/rc.conf
kld_list="nvidia-modeset"

Something like,
cat /usr/local/etc/X11/xorg.conf.d/20-nvidia.conf
Code: 
Section "Device"
   Identifier     "Device0"
   Driver         "nvidia"
   Option "PrimaryGPU" "yes"
   Option         "RenderAccel" "true"
   VendorName     "NVIDIA Corporation"
   Option "AccelMethod" "EXA"
EndSection

pkg info | grep -i nvidia
Code: 
nvidia-driver-580.119.02_1     NVidia graphics card binary drivers for hardware OpenGL rendering
nvidia-drm-66-kmod-580.119.02.1500068_2 NVIDIA DRM Kernel Module
nvidia-drm-kmod-580.119.02     NVIDIA DRM Kernel Module
nvidia-kmod-580.119.02.1500068_1 kmod part of NVidia graphics card binary drivers for hardware OpenGL rendering
nvidia-settings-580.119.02     Display Control Panel for X NVidia driver
 
SirDice said:
I suggest disabling the 'FreeBSD-ports-kmods' repository for now. You don't really need it at this point in time. It is likely the cause of the version mismatches.

mkdir -p /usr/local/etc/pkg/repos
echo "FreeBSD-ports-kmods: { enabled: no }" > /usr/local/etc/pkg/repos/FreeBSD.conf
Click to expand...
Yesterday I had to deal with this problem too.
And your suggestion (disabling the 'FreeBSD-ports-kmods' repository) did the trick!
Followed by 'pkg update' + 'pkg upgrade' + 'reboot'...
But now I'm in question why using "FreeBSD-ports-kmods" at all? (If everthing works fine, or with less problems, without it.)
 
blackfoxx said:
But now I'm in question why using "FreeBSD-ports-kmods" at all? (If everthing works fine, or with less problems, without it.)
Click to expand...
It's really only useful during the three month "transition" period when X.Y and X.Y+1 need to be supported. The 'regular' FreeBSD-ports repository will be built for X.Y. Which is fine for 99% of the userland applications. However it's often a problem for kernel modules (like the DRM driver, or Virtualbox kmods). That's where the FreeBSD-ports-kmods should be useful as those will be built specifically for X.Y and X.Y+1 (look at the definition, it's linked to ${VERSION_MINOR) and automatically switches to the correct minor version repository).

FreeBSD 15.0-RELEASE is now EoL and the packages in FreeBSD-ports are specifically built for 15.1. So there's no version discrepancy anymore regarding kernel modules. As there are still a bunch of teething problems with FreeBSD-ports-kmods (not being up to date, or at least not everything in it) you can safely disable it for now, less confusion. It'll become relevant again when 15.2 is released and both 15.1 and 15.2 need to be supported for three months.
 
This summer was awful.
Quarterly had Nvidia userland ( nvidia-driver) for 15.0 and kmods for 15.0
kmods_quarterly_1 had Kmods for 15.1

When you tried to install 15.1 with Nvidia from ONLY Quarterly you got 15.0 kmods. didnt work.
When you tried to install 15.1 with Nvidia and also using kmods_quaterly_1 you got 15.1 kmods and the 15.0 nvidia-driver userland. Again did not work.

You only chans to get it working was using LATEST repository or install from ports.

NOW after 2026-10-10 when Quaterly was upgraded to 15.1 A new installation works !!!! Beautifully.
If you do an upgrade from 15.0 to 15.1 you need to make sure that no old 15.0 kmods is lingering in your installation ,and that Nvidia-driver package is the same version as your kmods.
Also DRM-612-kmod is the default direct rendering module for 15.1
i have already seen some confusion and attempts to install drm-66-kmod on 15.1, This should only be nessesary for the PONTEVECCIOH intel graphics according to https://forums.freebsd.org/threads/intel-gpu-support-matrix.102846/
 
Thanks a lot SirDice and drsnx60 for the most detailed clarification and explaination one could wish!
Thats why I love FreeBSD and especially this forum.
When I was in trouble regarding FreeBSD I found 90% of solutions or helpful hints right here, in the handbook or man-pages. (The remaining 10% in some stack-exchange sites or blogs like vermaden 's.)
So I never had a feeling of standing alone on mars...
You're simply the best!
 
You must log in or register to reply here.
Back
Top