## Problem I have conflicting drivers: xpad which comes standard with Arch, and [xone](https://github.com/medusalix/xone) which I installed from [AUR](https://aur.archlinux.org/packages/xone-dkms-git) . Both claim to support my Xbox One wireless controller even though only the xone driver knows what to do with it.

$ modprobe -R usb:v045Ep02F9d0114dcFFdscFFdpFFicFFisc5Dip01in00
xpad
xone_dongle

AFAIU, the culprit is the alias: usb:v045Ep*d*dc*dsc*dp*icFFisc5Dip01in* in the xpad driver which is too inclusive. I want only the xone_dongle loaded for the modalias above. But I don't want to disable the xpad driver completely, because I also use a wired Xbox 360 controller usb:v045Ep028Ed0114dcFFdscFFdpFFicFFisc5Dip01in00 which I still want to be handled by xpad. I don't need them to work at the same time, but at least if I plug one of them after a clean boot, either should work. ## Attempted solution The manual page for modprobe.d states: > the blacklist keyword indicates that all of that particular module's internal aliases are to be ignored. Which sounds like if I blacklist xpad and then define my own alias for it, it should work the way I want: /etc/modprobe.d/gamepad.conf

blacklist xpad
alias usb:v045Ep028Ed0114dcFFdscFFdpFFicFFisc5Dip01in00 xpad

But instead it completely prevents the xpad driver from loading, even though the alias is correct. Also, even though I've blacklisted xpad in the configuration, modprobe -R still finds it for the modalias of the wireless dongle. ## Non-conclusion Can someone please shed some light on how this actually works? Is there a bug in modprobe? Is modprobe.d documentation incomplete? Which aspects of modprobe should be affected by the modprobe.d configuration and which shouldn't?

This is for Linux Mint. On my laptop, I have tried many *many* different methods in fixing this problem, the problem impacts my boot speed too as now it takes like 4 minutes to boot. During shutdown, the same error pops up. Hell, even when I go to a different TTY like TTY6 instead of my GUI in TTY7, the same message appears, it's everywhere. Specifically, after I type in dmesg to display messages during startup I get this: :d6:07:41:e8 [ 14.449973] usb 1-4: new full-speed USB device number 13 using xhci_hcd [ 14.450114] usb 1-4: Device not responding to setup address. [ 14.659080] usb 1-4: Device not responding to setup address. [ 14.866957] usb 1-4: device not accepting address 13, error -71 [ 14.867011] usb 1-4: WARN: invalid context state for evaluate context command. [ 15.182924] usb 1-4: new full-speed USB device number 14 using xhci_hcd [ 15.183137] usb 1-4: Device not responding to setup address. [ 15.387200] usb 1-4: Device not responding to setup address. [ 15.594975] usb 1-4: device not accepting address 14, error -71 [ 15.595048] usb 1-4: WARN: invalid context state for evaluate context command. [ 15.595096] usb usb1-port4: attempt power cycle [ 15.974932] usb 1-4: new full-speed USB device number 15 using xhci_hcd [ 16.088968] usb 1-4: device descriptor read/64, error -71 [ 16.309007] usb 1-4: device descriptor read/64, error -71 [ 16.524986] usb 1-4: new full-speed USB device number 16 using xhci_hcd [ 16.638952] usb 1-4: device descriptor read/64, error -71 [ 16.860890] usb 1-4: device descriptor read/64, error -71 [ 16.962940] usb usb1-port4: unable to enumerate USB device I tried a couple of solution (I say most of them are quite old), one was this https://urukrama.wordpress.com/2009/01/27/usb-drive-not-recognised-error-71/ , that I found in this forum , which did nothing since there was no options.conf in my /etc/modprobe.d/ directory, even after making it, nothing happened. Next solution I tried was this forum solution which also did not work. For now i'm just waiting and trying my best to debug this with only like 3 months experience using Linux, got any tips or guides? lsusb Produces this result: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 036: ID 062a:5918 MosArt Semiconductor Corp. 2.4G Keyboard Mouse Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Creating a udev.rules file (so far): Update after I tried setting a udev file: Status of dmesg currently (23/05/2025): [ 6.691017] usb 1-4: device not accepting address 9, error -71 [ 6.691164] usb 1-4: WARN: invalid context state for evaluate context command. [ 7.006924] usb 1-4: new full-speed USB device number 10 using xhci_hcd [ 7.007139] usb 1-4: Device not responding to setup address. [ 7.212243] usb 1-4: Device not responding to setup address. [ 7.419012] usb 1-4: device not accepting address 10, error -71 [ 7.419168] usb 1-4: WARN: invalid context state for evaluate context command. [ 7.419290] usb usb1-port4: attempt power cycle [ 7.687218] systemd[1] : systemd-rfkill.service: Deactivated successfully. [ 7.798993] usb 1-4: new full-speed USB device number 11 using xhci_hcd [ 7.914183] usb 1-4: device descriptor read/64, error -71 [ 8.134176] usb 1-4: device descriptor read/64, error -71 [ 8.358922] usb 1-4: new full-speed USB device number 12 using xhci_hcd [ 8.474175] usb 1-4: device descriptor read/64, error -71 [ 8.694175] usb 1-4: device descriptor read/64, error -71 [ 8.803197] usb usb1-port4: unable to enumerate USB device Some other outputs from dmesg (could be totally unrelated): [ 0.134524] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20230628/dswload2-326) [ 0.134535] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220) [ 0.134537] ACPI: Skipping parse of AML opcode: Method (0x0014) [ 0.134540] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS01._PLD], AE_ALREADY_EXISTS (20230628/dswload2-326) [ 0.134543] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220) [ 0.134545] ACPI: Skipping parse of AML opcode: Method (0x0014) [ 0.134669] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS02._UPC], AE_ALREADY_EXISTS (20230628/dswload2-326) [ 0.134672] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220) [ 0.134673] ACPI: Skipping parse of AML opcode: Method (0x0014) [ 0.134675] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS02._PLD], AE_ALREADY_EXISTS (20230628/dswload2-326) [ 0.134678] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220) [ 0.134679] ACPI: Skipping parse of AML opcode: Method (0x0014) [ 0.134682] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS03._UPC], AE_ALREADY_EXISTS (20230628/dswload2-326) [ 0.134685] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220) [ 0.134686] ACPI: Skipping parse of AML opcode: Method (0x0014) [ 0.134688] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS03._PLD], AE_ALREADY_EXISTS (20230628/dswload2-326) [ 0.134690] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220) BIOS HP Utility Setup:

I'm trying to disable kernel module for my motherboard's bluetooth chip: btintel. I've added a blacklist entry to /etc/modprobe.d/blacklist-btintel.conf (I also tried blacklist.conf, this didn't make a difference):

blacklist btintel

I have also symlinked this file to /usr/lib/modprobe.d/ because of [this](https://bugzilla.redhat.com/show_bug.cgi?id=873220) possible issue. Furthermore, I've edited /etc/sysconfig/grub, to include the module in both rd.driver.blacklist as well as modprobe.blacklist:

$ grep 'GRUB_CMDLINE_LINUX' /etc/sysconfig/grub
GRUB_CMDLINE_LINUX="rd.driver.blacklist=nouveau,btintel modprobe.blacklist=nouveau,btintel nvidia-drm.modeset=1 resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv=fedora_localhost-live/root rd.lvm.lv=fedora_localhost-live/swap rhgb quiet"

Afterwards, I've tried running both:

sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg

as well as

sudo dracut -fv

But after rebooting, I'm still presented with a loaded module:

$ lsmod | grep btintel
btintel                28672  1 btusb
bluetooth             626688  48 btrtl,btintel,btbcm,bnep,btusb,rfcomm

Anyone have a suggestion?

I have an embedded Linux device (Ubiquiti EdgeRouter-X, see [this thread](https://community.ui.com/questions/SCTP-support-for-EdgeOSv2/7b50504f-8966-45f2-a1dd-f5571d3a7873#answer/cf43a3bd-d7e5-4eda-a31f-73be9f434e9f) for more detail) for which I cross-compiled the kernel module nf_conntrack.ko (part of netfilter) to support a protocol that was not built into the inbox module. This module is loaded and being used as soon as the device becomes accessible over SSH. The OS is debian-based, FWIW. I want to try out this version of the module, but it could be faulty and crash the kernel (happened in another module I compiled at the same time). If I could reload at runtime, then a crash would merely result in a reboot, which is fine. But I can't find a way to load a different version side-by-side with the running module. Or else, I'd have to unload the running module, and load the new one, but I'm just unable to do that with rmmod or modprobe -r or even rmmod -f. I've checked multiple questions like [this](https://unix.stackexchange.com/questions/645427/remove-kernel-module-in-use) and none of the subtle variants helped. But if I modify the boot configuration to load this module and reboot to test it, I'm scared that it might be stuck in a bootloop. The device does not have a physical console port so it really does need to boot up fully to be accessible. Is there a way to set the OS to load a module only once, and skip if it doesn't work, or else load the known-working version? Any way I can avoid saving a risky boot configuration to disk but still find out if the module can be loaded?

My distribution is Fedora 17 Gnome. Every time I reboot/restart my computer I need to run this command as root: modprobe rt2800usb How can I make it permanent and enable this module at boot ?

**My situation:** I have a prebuilt kernel running fedora already installed and running. Now, I want to install the mcp251x and mcp25xfd driver modules, which depends on the can-dev driver module, so I need to install that one too. Apparently, the source code for these modules existed in the kernel source for this version, but my guess is that they were not "enabled" via the .config file during the kernel compilation. So this is an after-the-fact driver module installation attempt. I've never done this, so please guide me if there is an easier way. **What I've tried:** I first went into the /lib/modules directory and looked to see if my 3 modules already existed, ready to be installed. I found one of them: can-dev.ko.xz So I install it: $ sudo insmod can-dev.ko.xz This completes, no error message. For the other 2 modules, I see the source code for them and a makefile, but calling "make" just says "No targets" and fails to build. I then looked at the version using uname -a: Linux fedora 5.11.3-300.fc34.x86_64 So I go and download the source code for 5.11.3 from: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/refs/tags I check my current compiler version: $ gcc --version $ gcc (GCC) 11.0.0 20210210 (Red Hat 11.0.0-0) I verify that this is the same gcc version used to build the kernel: $ cat /proc/version $ gcc (GCC) 11.0.0 20210210 (Red Hat 11.0.0-0) So apparently I can't just go into the driver folder and call "make", even though it has a makefile. The driver makefile is all tangled together with the kernel makefile, so I go into the kernel source code root directory and modify the Makefile: EXTRAVERSION = -300.fc34.x86_64 This ensures the "vermagic" string in the module is compatible with the currently installed OS version. Then, in the kernel source code root directory, I call: $ make oldconfig This generates a .config file. I manually edit the .config file to add these lines: CONFIG_CAN_MCP251X=m CONFIG_CAN_MCP251XFD=m This tells the kernel to build MCP251x and MCP251xfd as modules (they were defaulted to not build at all). I then call $ make prepare Then, I cd into the specific driver directory I am trying to build (which contains c code and a Makefile), and call: $ make -C ~/linux-5.11.3 M=pwd modules Which calls the kernel-source-root Makefile with some special arguments instructing to only build the kernel modules in the current directory. This works, and it generates the files mcp251xfd.ko and mcp251x.ko. I try to install these modules: $ sudo insmod mcp251x.ko $ sudo insmod mcp251xfd.ko But both return the following error message: insmod: ERROR: could not insert module mcp251xfd.ko: Invalid module format and a call to $ dmesg Returns: module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000abe7d4fb, val ffffffffc10b3a77 The only thing I know left to check is that the magic number matches to uname -r number: $ uname -r 5.11.3-300.fc34.x86_64 Check against module: $ modinfo mcp251xfd.ko vermagic: 5.11.3-300.fc34.x86_64 So I'm out of ideas on what to do or try to get these drivers installed.

I need to create a second separate virtual interface on Linux. I choose dummy. And do these steps: $ cat /etc/modules-load.d/dummy.conf # Load dummy.ko at boot dummy $ cat /etc/sysconfig/network-scripts/ifcfg-ethdummy1 NAME=ethdummy1 DEVICE=ethdummy1 MACADDR=00:22:22:ff:ff:ff IPADDR=10.10.10.1 NETMASK=255.255.255.0 ONBOOT=yes TYPE=Ethernet NM_CONTROLLED=no Seems like everything works. But on the net I see that people do these lines also: $ cat /etc/modprobe.d/dummy.conf install dummy /sbin/modprobe --ignore-install dummy; /sbin/ip link set name ethdummy1 dev dummy0 What's the point of this line ? Thanks.

I have a Gigabyte X570 GAMING X motherboard and want to control the fans from my XUbuntu 24.04, but it has issues detecting the fans. There is [a suggested solution](https://github.com/lm-sensors/lm-sensors/issues/154) , but modprobe it87 force_id=0x8628 only works on the console (I don't want to use dkms). Now I want this to work directly after a reboot. So I now have: root@runlikehell:~# cat /etc/modprobe.d/fans.conf options it87 force_id=0x8628 root@runlikehell:~# and added these to the "[Unit]"-section in /usr/lib/systemd/system/lm-sensors.service: Requires=systemd-modules-load.service After=systemd-modules-load.service Note that I asked AI and it halucinates as it suggests this: After=modprobe@*.service Wants=modprobe@*.service but [systemd doesn't allow wildcards there](https://github.com/systemd/systemd/issues/5388) . After a reboot I see this, so the conf-file was loaded: root@runlikehell:~# modprobe -c | grep it87 blacklist it8712f_wdt blacklist it87_wdt blacklist it8712f_wdt blacklist it87_wdt blacklist it8712f_wdt blacklist it87_wdt blacklist it8712f_wdt blacklist it87_wdt blacklist it8712f_wdt blacklist it87_wdt blacklist it8712f_wdt blacklist it87_wdt blacklist it8712f_wdt blacklist it87_wdt blacklist it8712f_wdt blacklist it87_wdt options it87 force_id=0x8628 alias dmi*:rvn*GigabyteTechnologyCo.,Ltd.*:rn*AB350*: it87 alias dmi*:rvn*GigabyteTechnologyCo.,Ltd.*:rn*AX370*: it87 alias dmi*:rvn*GigabyteTechnologyCo.,Ltd.*:rn*B550AORUSPROAC*: it87 alias dmi*:rvn*GigabyteTechnologyCo.,Ltd.*:rn*TRX40AORUSXTREME*: it87 alias dmi*:rvn*GigabyteTechnologyCo.,Ltd.*:rn*X570AORUSMASTER*: it87 alias dmi*:rvn*GigabyteTechnologyCo.,Ltd.*:rn*X570AORUSPRO*: it87 alias dmi*:rvn*GigabyteTechnologyCo.,Ltd.*:rn*X570AORUSPROWIFI*: it87 alias dmi*:rvn*GigabyteTechnologyCo.,Ltd.*:rn*X570SAEROG*: it87 alias dmi*:rvn*GigabyteTechnologyCo.,Ltd.*:rn*Z390AORUSULTRA_CF*: it87 alias dmi*:rvn*GigabyteTechnologyCo.,Ltd.*:rn*Z690AORUSPRO*: it87 alias dmi*:rvn*GigabyteTechnologyCo.,Ltd.*:rn*Z690AORUSPRODDR4*: it87 alias dmi*:rvn*GigabyteTechnologyCo.,Ltd.*:rn*Z97X_GamingG1*: it87 alias dmi*:rvn*nVIDIA*:rn*FN68PT*: it87 root@runlikehell:~# The lm-sensors.service is running, but it didn't find the it87-related stuff: root@runlikehell:~# journalctl -b 0 -u lm-sensors.service ... systemd: Starting lm-sensors.service - Initialize hardware monitoring sensors... ... sensors: k10temp-pci-00c3 ... sensors: Adapter: PCI adapter ... sensors: Tctl: +48.4°C ... sensors: Tccd1: +56.5°C ... sensors: acpitz-acpi-0 ... sensors: Adapter: ACPI interface ... sensors: temp1: +16.8°C ... sensors: temp2: +16.8°C ... sensors: temp3: +16.8°C ... sensors: gigabyte_wmi-virtual-0 ... sensors: Adapter: Virtual device ... sensors: temp1: +25.0°C ... sensors: temp2: +26.0°C ... sensors: temp3: +48.0°C ... sensors: temp4: +26.0°C ... sensors: temp5: +28.0°C ... sensors: temp6: +39.0°C ... sensors: nvme-pci-0300 ... sensors: Adapter: PCI adapter ... sensors: Composite: +40.9°C (low = -0.1°C, high = +74.8°C) ... sensors: (crit = +79.8°C) ... systemd: Finished lm-sensors.service - Initialize hardware monitoring sensors. root@runlikehell:~# So to me it means that the configuration of modprobe hasn't been read or applied when lm-sensors.service starts. journalctl -b 0 doesn't contain "it87" at all (I don't know if it should). How do I run the lm-sensors.service after the modprobe-stuff properly?

Debian GNU/Linux 12 (bookworm) x86_64 Kernel: 6.1.0-28-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.119-1 (2024-11-22) x86_64 GNU/Linux Installed 10G AQtion Ethernet Controller with AQC113C chip @ pcie x4. Can't enable driver for AQC113. Here is AQC111 but not AQC113. Modprobe atlantic doesn't help. # uname -a Linux ***** 6.1.0-28-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.119-1 (2024-11-22) x86_64 GNU/Linux # lsmod | grep atlantic atlantic 245760 0 macsec 61440 1 atlantic # modinfo aqc113 modinfo: ERROR: Module aqc113 not found. # modinfo aqc111 filename: /lib/modules/6.1.0-28-amd64/kernel/drivers/net/usb/aqc111.ko license: GPL description: Aquantia AQtion USB to 5/2.5GbE Controllers alias: usb:v1C04p0015d*dc*dsc*dp*ic02isc06ip00in* alias: usb:v1C04p0015d*dc*dsc*dp*icFFisc*ip*in* alias: usb:v20F4pE05Ad*dc*dsc*dp*ic02isc06ip00in* alias: usb:v20F4pE05Ad*dc*dsc*dp*icFFisc*ip*in* alias: usb:v0B95p2791d*dc*dsc*dp*ic02isc06ip00in* alias: usb:v0B95p2791d*dc*dsc*dp*icFFisc*ip*in* alias: usb:v0B95p2790d*dc*dsc*dp*ic02isc06ip00in* alias: usb:v0B95p2790d*dc*dsc*dp*icFFisc*ip*in* alias: usb:v2ECApC101d*dc*dsc*dp*ic02isc06ip00in* alias: usb:v2ECApC101d*dc*dsc*dp*icFFisc*ip*in* depends: usbnet,usbcore retpoline: Y intree: Y name: aqc111 vermagic: 6.1.0-28-amd64 SMP preempt mod_unload modversions sig_id: PKCS#7 signer: Debian Secure Boot CA sig_key: 32:A0:28:7F:84:1A:03:6F:A3:93:C1:E0:65:C4:3A:E6:B2:42:26:43 sig_hashalgo: sha256 signature: 17:5F:68:C5:6F:6E:F3:F8:2D:78:C4:8A:6C:EC:37:E0:4A:E9:41:CE: 43:94:53:5E:BE:E6:7C:85:99:48:E0:43:E6:B3:0F:76:F8:47:E6:CF: 8B:B1:A7:03:68:AB:BC:51:0C:1B:82:99:CC:24:65:32:24:B5:8E:91: 0F:BA:3E:73:F3:C7:6B:09:AF:FC:9F:1B:A7:6E:21:5A:50:98:99:A9: 66:CF:95:88:BF:6B:31:FB:2D:7C:42:68:D8:92:DF:18:15:82:63:59: E7:55:3E:AF:4C:BE:D6:D1:09:79:83:AD:CA:8A:F4:6E:A4:E5:D4:2F: 8C:59:1E:D9:F1:7E:43:4E:F0:D6:7B:0A:C8:04:79:5A:96:EB:61:AC: A3:65:42:2E:D3:86:F5:DE:18:C4:71:52:C6:5D:82:6B:19:4B:CA:99: 4F:F8:53:2C:B0:C8:EE:0D:38:74:C1:3D:D9:19:58:57:B6:BE:9A:ED: DC:BD:03:4E:A3:B2:9B:79:16:92:7D:47:61:F4:9C:44:67:E9:05:58: B1:1B:E5:E8:DF:EA:2C:18:BD:E1:30:9C:69:B3:E4:CF:DA:A4:79:BA: 4C:35:14:54:06:8B:E2:6F:79:DB:9B:72:C4:C7:B9:CD:AC:7A:89:DC: AC:4B:6B:8D:8B:76:4A:DC:83:F9:F7:C9:A8:E4:84:E1 Building drivers have some building error issues AQtion-2.5.5 "too many arguments to function ‘netif_napi_add'" . Tried Kernel 6.13.0-rc5-custom and it's have same problems. How can I run AQC113 ethernet controller? Build driver v2.5.12 (07-18-24) downloaded from official Marvell site. root@debvm:/# cd /opt/ root@debvm:/opt# wget https://www.marvell.com/content/dam/marvell/en/drivers/07-18-24_Marvell_Linux_2.5.12.zip --2025-01-02 15:14:29-- https://www.marvell.com/content/dam/marvell/en/drivers/07-18-24_Marvell_Linux_2.5.12.zip Resolving www.marvell.com (www.marvell.com)... 104.94.100.138, 104.94.100.99 Connecting to www.marvell.com (www.marvell.com)|104.94.100.138|:443... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [application/zip] Saving to: ‘07-18-24_Marvell_Linux_2.5.12.zip’ 07-18-24_Marvell_Linux_2.5.12.zip [ ] 242.83K --.-KB/s in 0.1s 2025-01-02 15:14:30 (2.41 MB/s) - ‘07-18-24_Marvell_Linux_2.5.12.zip’ saved root@debvm:/opt# 7zz x 07-18-24_Marvell_Linux_2.5.12.zip 7-Zip (z) 22.01 (x64) : Copyright (c) 1999-2022 Igor Pavlov : 2022-07-15 64-bit locale=en_US.UTF-8 Threads:128 Scanning the drive for archives: 1 file, 248654 bytes (243 KiB) Extracting archive: 07-18-24_Marvell_Linux_2.5.12.zip -- Path = 07-18-24_Marvell_Linux_2.5.12.zip Type = zip Physical Size = 248654 Everything is Ok Folders: 1 Files: 3 Size: 280443 Compressed: 248654 root@debvm:/opt# ls -l total 248 drwxr-xr-x 2 root root 4096 Sep 19 05:00 07-18-24_Marvell_Linux_2.5.12 -rw-r--r-- 1 root root 248654 Dec 6 08:34 07-18-24_Marvell_Linux_2.5.12.zip root@debvm:/opt# cd ./07-18-24_Marvell_Linux_2.5.12/ root@debvm:/opt/07-18-24_Marvell_Linux_2.5.12# ls atlantic.tar.gz README.txt Release_Notes_Linux_2.5.12.txt root@debvm:/opt/07-18-24_Marvell_Linux_2.5.12# tar -zxf atlantic.tar.gz root@debvm:/opt/07-18-24_Marvell_Linux_2.5.12# root@debvm:/opt/07-18-24_Marvell_Linux_2.5.12# uname -a Linux debvm 6.1.0-28-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.119-1 (2024-11-22) x86_64 GNU/Linux root@debvm:/opt/07-18-24_Marvell_Linux_2.5.12# root@debvm:/opt/07-18-24_Marvell_Linux_2.5.12# apt install apt linux-headers-6.1.0-28-amd64 build-essential Reading package lists... Done Building dependency tree... Done Reading state information... Done apt is already the newest version (2.6.1). linux-headers-6.1.0-28-amd64 is already the newest version (6.1.119-1). build-essential is already the newest version (12.9). The following package was automatically installed and is no longer required: linux-image-6.1.0-27-amd64 Use 'apt autoremove' to remove it. 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. root@debvm:/opt/07-18-24_Marvell_Linux_2.5.12# cd ./Linux/ root@debvm:/opt/07-18-24_Marvell_Linux_2.5.12/Linux# ls aq_cfg.h aq_dash.c aq_drvinfo.h aq_filters.h aq_macsec.c aq_nic.c aq_phy.c aq_ring.c aq_sysfs.h aq_tsn.h build-deb.sh Kbuild kunit release_notes.txt aq_common.h aq_dash.h aq_ethtool.c aq_hw.h aq_macsec.h aq_nic.h aq_phy.h aq_ring.h aq_trace.c aq_utils.h dkms.sh Kbuild.cflags macsec rpm-src.spec aq_compat.c aq_dash_internal.h aq_ethtool.h aq_hw_utils.c aq_main.c aq_pci_func.c aq_ptp.c aq_rss.h aq_trace.h aq_vec.c hw_atl Kbuild.kunit Makefile ver.h aq_compat.h aq_drvinfo.c aq_filters.c aq_hw_utils.h aq_main.h aq_pci_func.h aq_ptp.h aq_sysfs.c aq_tsn.c aq_vec.h hw_atl2 Kconfig README.txt root@debvm:/opt/07-18-24_Marvell_Linux_2.5.12/Linux# make make -j4 -C /lib/modules/6.1.0-28-amd64/build M="/opt/07-18-24_Marvell_Linux_2.5.12/Linux" modules make[1] : Entering directory '/usr/src/linux-headers-6.1.0-28-amd64' CC [M] /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_main.o CC [M] /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_nic.o CC [M] /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_pci_func.o CC [M] /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_vec.o CC [M] /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_ring.o CC [M] /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_ptp.o CC [M] /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_filters.o CC [M] /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_hw_utils.o CC [M] /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_ethtool.o CC [M] /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_drvinfo.o CC [M] /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_trace.o CC [M] /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_phy.o CC [M] /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_compat.o CC [M] /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_tsn.o CC [M] /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_sysfs.o CC [M] /opt/07-18-24_Marvell_Linux_2.5.12/Linux/hw_atl/hw_atl_a0.o CC [M] /opt/07-18-24_Marvell_Linux_2.5.12/Linux/hw_atl/hw_atl_b0.o CC [M] /opt/07-18-24_Marvell_Linux_2.5.12/Linux/hw_atl/hw_atl_utils.o CC [M] /opt/07-18-24_Marvell_Linux_2.5.12/Linux/hw_atl/hw_atl_utils_fw2x.o CC [M] /opt/07-18-24_Marvell_Linux_2.5.12/Linux/hw_atl/hw_atl_llh.o CC [M] /opt/07-18-24_Marvell_Linux_2.5.12/Linux/hw_atl/hw_atl_fw_hostboot.o CC [M] /opt/07-18-24_Marvell_Linux_2.5.12/Linux/hw_atl/hw_atl_fw_image.o CC [M] /opt/07-18-24_Marvell_Linux_2.5.12/Linux/hw_atl2/hw_atl2_llh.o CC [M] /opt/07-18-24_Marvell_Linux_2.5.12/Linux/hw_atl2/hw_atl2.o CC [M] /opt/07-18-24_Marvell_Linux_2.5.12/Linux/hw_atl2/hw_atl2_utils.o CC [M] /opt/07-18-24_Marvell_Linux_2.5.12/Linux/hw_atl2/hw_atl2_utils_fw.o CC [M] /opt/07-18-24_Marvell_Linux_2.5.12/Linux/hw_atl2/hw_atl2_fw_hostboot.o CC [M] /opt/07-18-24_Marvell_Linux_2.5.12/Linux/macsec/macsec_api.o CC [M] /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_dash.o CC [M] /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.o /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.c: In function ‘aq_mdo_dev_open’: /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.c:297:16: error: ‘struct macsec_context’ has no member named ‘prepare’ 297 | if (ctx->prepare) | ^~ /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.c: In function ‘aq_mdo_dev_stop’: /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.c:312:16: error: ‘struct macsec_context’ has no member named ‘prepare’ 312 | if (ctx->prepare) | ^~ /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.c: In function ‘aq_mdo_add_secy’: /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.c:475:16: error: ‘struct macsec_context’ has no member named ‘prepare’ 475 | if (ctx->prepare) | ^~ /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.c: In function ‘aq_mdo_upd_secy’: /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.c:502:16: error: ‘struct macsec_context’ has no member named ‘prepare’ 502 | if (ctx->prepare) | ^~ /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.c: In function ‘aq_mdo_del_secy’: /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.c:554:16: error: ‘struct macsec_context’ has no member named ‘prepare’ 554 | if (ctx->prepare) | ^~ /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.c: In function ‘aq_mdo_add_txsa’: /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.c:617:16: error: ‘struct macsec_context’ has no member named ‘prepare’ 617 | if (ctx->prepare) | ^~ /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.c: In function ‘aq_mdo_upd_txsa’: /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.c:648:16: error: ‘struct macsec_context’ has no member named ‘prepare’ 648 | if (ctx->prepare) | ^~ /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.c: In function ‘aq_mdo_del_txsa’: /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.c:699:16: error: ‘struct macsec_context’ has no member named ‘prepare’ 699 | if (ctx->prepare) | ^~ /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.c: In function ‘aq_mdo_add_rxsc’: /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.c:799:16: error: ‘struct macsec_context’ has no member named ‘prepare’ 799 | if (ctx->prepare) | ^~ /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.c: In function ‘aq_mdo_upd_rxsc’: /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.c:829:16: error: ‘struct macsec_context’ has no member named ‘prepare’ 829 | if (ctx->prepare) | ^~ /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.c: In function ‘aq_mdo_del_rxsc’: /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.c:897:16: error: ‘struct macsec_context’ has no member named ‘prepare’ 897 | if (ctx->prepare) | ^~ /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.c: In function ‘aq_mdo_add_rxsa’: /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.c:974:16: error: ‘struct macsec_context’ has no member named ‘prepare’ 974 | if (ctx->prepare) | ^~ /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.c: In function ‘aq_mdo_upd_rxsa’: /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.c:1005:16: error: ‘struct macsec_context’ has no member named ‘prepare’ 1005 | if (ctx->prepare) | ^~ /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.c: In function ‘aq_mdo_del_rxsa’: /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.c:1057:16: error: ‘struct macsec_context’ has no member named ‘prepare’ 1057 | if (ctx->prepare) | ^~ /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.c: In function ‘aq_mdo_get_dev_stats’: /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.c:1073:16: error: ‘struct macsec_context’ has no member named ‘prepare’ 1073 | if (ctx->prepare) | ^~ /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.c: In function ‘aq_mdo_get_tx_sc_stats’: /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.c:1103:16: error: ‘struct macsec_context’ has no member named ‘prepare’ 1103 | if (ctx->prepare) | ^~ /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.c: In function ‘aq_mdo_get_tx_sa_stats’: /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.c:1137:16: error: ‘struct macsec_context’ has no member named ‘prepare’ 1137 | if (ctx->prepare) | ^~ /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.c: In function ‘aq_mdo_get_rx_sc_stats’: /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.c:1179:16: error: ‘struct macsec_context’ has no member named ‘prepare’ 1179 | if (ctx->prepare) | ^~ /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.c: In function ‘aq_mdo_get_rx_sa_stats’: /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.c:1229:16: error: ‘struct macsec_context’ has no member named ‘prepare’ 1229 | if (ctx->prepare) | ^~ make: *** [/usr/src/linux-headers-6.1.0-28-common/scripts/Makefile.build:255: /opt/07-18-24_Marvell_Linux_2.5.12/Linux/aq_macsec.o] Error 1 make: *** Waiting for unfinished jobs.... make[1] : *** [/usr/src/linux-headers-6.1.0-28-common/Makefile:2034: /opt/07-18-24_Marvell_Linux_2.5.12/Linux] Error 2 make[1] : Leaving directory '/usr/src/linux-headers-6.1.0-28-amd64' make: *** [Makefile:36: all] Error 2 Build driver v2.5.5 from git (ignore errors) root@debvm:/opt# git clone https://github.com/Aquantia/AQtion Cloning into 'AQtion'... remote: Enumerating objects: 597, done. remote: Counting objects: 100% (55/55), done. remote: Compressing objects: 100% (12/12), done. remote: Total 597 (delta 47), reused 43 (delta 43), pack-reused 542 (from 1) Receiving objects: 100% (597/597), 586.56 KiB | 2.33 MiB/s, done. Resolving deltas: 100% (451/451), done. root@debvm:/opt# cd ./AQtion/ root@debvm:/opt/AQtion# ls aq_cfg.h aq_dash.c aq_drvinfo.h aq_filters.h aq_macsec.c aq_nic.c aq_phy.c aq_ring.c aq_sysfs.h aq_tsn.h build-deb.sh Kbuild kunit README.txt aq_common.h aq_dash.h aq_ethtool.c aq_hw.h aq_macsec.h aq_nic.h aq_phy.h aq_ring.h aq_trace.c aq_utils.h dkms.sh Kbuild.cflags macsec rpm-src.spec aq_compat.c aq_dash_internal.h aq_ethtool.h aq_hw_utils.c aq_main.c aq_pci_func.c aq_ptp.c aq_rss.h aq_trace.h aq_vec.c hw_atl Kbuild.kunit Makefile ver.h aq_compat.h aq_drvinfo.c aq_filters.c aq_hw_utils.h aq_main.h aq_pci_func.h aq_ptp.h aq_sysfs.c aq_tsn.c aq_vec.h hw_atl2 Kconfig README.md root@debvm:/opt/AQtion# make -i make -j4 -C /lib/modules/6.1.0-28-amd64/build M="/opt/AQtion" modules make[1] : Entering directory '/usr/src/linux-headers-6.1.0-28-amd64' CC [M] /opt/AQtion/aq_vec.o CC [M] /opt/AQtion/aq_ring.o CC [M] /opt/AQtion/aq_ptp.o CC [M] /opt/AQtion/aq_filters.o /opt/AQtion/aq_ptp.c: In function ‘aq_ptp_init’: /opt/AQtion/aq_ptp.c:2130:9: error: too many arguments to function ‘netif_napi_add’ 2130 | netif_napi_add(aq_nic_get_ndev(aq_nic), &aq_ptp->napi, | ^~~~~~~~~~~~~~ In file included from /usr/src/linux-headers-6.1.0-28-common/include/linux/etherdevice.h:21, from /opt/AQtion/aq_common.h:14, from /opt/AQtion/aq_hw_utils.h:15, from /opt/AQtion/aq_ptp.c:19: /usr/src/linux-headers-6.1.0-28-common/include/linux/netdevice.h:2575:1: note: declared here 2575 | netif_napi_add(struct net_device *dev, struct napi_struct *napi, | ^~~~~~~~~~~~~~ make: [/usr/src/linux-headers-6.1.0-28-common/scripts/Makefile.build:255: /opt/AQtion/aq_ptp.o] Error 1 (ignored) /usr/src/linux-headers-6.1.0-28-common/scripts/check-local-export: nm failed Terminated make: [/usr/src/linux-headers-6.1.0-28-common/scripts/Makefile.build:255: /opt/AQtion/aq_ptp.o] Error 143 (ignored) CC [M] /opt/AQtion/aq_hw_utils.o /opt/AQtion/aq_vec.c: In function ‘aq_vec_alloc’: /opt/AQtion/aq_vec.c:126:9: error: too many arguments to function ‘netif_napi_add’ 126 | netif_napi_add(aq_nic_get_ndev(aq_nic), &self->napi, | ^~~~~~~~~~~~~~ In file included from /usr/src/linux-headers-6.1.0-28-common/include/linux/etherdevice.h:21, from /opt/AQtion/aq_common.h:14, from /opt/AQtion/aq_vec.h:15, from /opt/AQtion/aq_vec.c:12: /usr/src/linux-headers-6.1.0-28-common/include/linux/netdevice.h:2575:1: note: declared here 2575 | netif_napi_add(struct net_device *dev, struct napi_struct *napi, | ^~~~~~~~~~~~~~ make: [/usr/src/linux-headers-6.1.0-28-common/scripts/Makefile.build:255: /opt/AQtion/aq_vec.o] Error 1 (ignored) /usr/src/linux-headers-6.1.0-28-common/scripts/check-local-export: nm failed Terminated make: [/usr/src/linux-headers-6.1.0-28-common/scripts/Makefile.build:255: /opt/AQtion/aq_vec.o] Error 143 (ignored) CC [M] /opt/AQtion/aq_ethtool.o CC [M] /opt/AQtion/aq_drvinfo.o CC [M] /opt/AQtion/aq_trace.o CC [M] /opt/AQtion/aq_phy.o CC [M] /opt/AQtion/aq_compat.o CC [M] /opt/AQtion/aq_tsn.o CC [M] /opt/AQtion/aq_sysfs.o CC [M] /opt/AQtion/hw_atl/hw_atl_a0.o CC [M] /opt/AQtion/hw_atl/hw_atl_b0.o CC [M] /opt/AQtion/hw_atl/hw_atl_utils.o CC [M] /opt/AQtion/hw_atl/hw_atl_utils_fw2x.o CC [M] /opt/AQtion/hw_atl/hw_atl_llh.o CC [M] /opt/AQtion/hw_atl/hw_atl_fw_hostboot.o CC [M] /opt/AQtion/hw_atl/hw_atl_fw_image.o CC [M] /opt/AQtion/hw_atl2/hw_atl2_llh.o CC [M] /opt/AQtion/hw_atl2/hw_atl2.o CC [M] /opt/AQtion/hw_atl2/hw_atl2_utils.o CC [M] /opt/AQtion/hw_atl2/hw_atl2_utils_fw.o CC [M] /opt/AQtion/hw_atl2/hw_atl2_fw_hostboot.o CC [M] /opt/AQtion/macsec/macsec_api.o CC [M] /opt/AQtion/aq_dash.o CC [M] /opt/AQtion/aq_macsec.o /opt/AQtion/aq_macsec.c: In function ‘aq_mdo_dev_open’: /opt/AQtion/aq_macsec.c:296:16: error: ‘struct macsec_context’ has no member named ‘prepare’ 296 | if (ctx->prepare) | ^~ /opt/AQtion/aq_macsec.c: In function ‘aq_mdo_dev_stop’: /opt/AQtion/aq_macsec.c:310:16: error: ‘struct macsec_context’ has no member named ‘prepare’ 310 | if (ctx->prepare) | ^~ /opt/AQtion/aq_macsec.c: In function ‘aq_mdo_add_secy’: /opt/AQtion/aq_macsec.c:472:16: error: ‘struct macsec_context’ has no member named ‘prepare’ 472 | if (ctx->prepare) | ^~ /opt/AQtion/aq_macsec.c: In function ‘aq_mdo_upd_secy’: /opt/AQtion/aq_macsec.c:498:16: error: ‘struct macsec_context’ has no member named ‘prepare’ 498 | if (ctx->prepare) | ^~ /opt/AQtion/aq_macsec.c: In function ‘aq_mdo_del_secy’: /opt/AQtion/aq_macsec.c:549:16: error: ‘struct macsec_context’ has no member named ‘prepare’ 549 | if (ctx->prepare) | ^~ /opt/AQtion/aq_macsec.c: In function ‘aq_mdo_add_txsa’: /opt/AQtion/aq_macsec.c:611:16: error: ‘struct macsec_context’ has no member named ‘prepare’ 611 | if (ctx->prepare) | ^~ /opt/AQtion/aq_macsec.c: In function ‘aq_mdo_upd_txsa’: /opt/AQtion/aq_macsec.c:641:16: error: ‘struct macsec_context’ has no member named ‘prepare’ 641 | if (ctx->prepare) | ^~ /opt/AQtion/aq_macsec.c: In function ‘aq_mdo_del_txsa’: /opt/AQtion/aq_macsec.c:691:16: error: ‘struct macsec_context’ has no member named ‘prepare’ 691 | if (ctx->prepare) | ^~ /opt/AQtion/aq_macsec.c: In function ‘aq_mdo_add_rxsc’: /opt/AQtion/aq_macsec.c:790:16: error: ‘struct macsec_context’ has no member named ‘prepare’ 790 | if (ctx->prepare) | ^~ /opt/AQtion/aq_macsec.c: In function ‘aq_mdo_upd_rxsc’: /opt/AQtion/aq_macsec.c:819:16: error: ‘struct macsec_context’ has no member named ‘prepare’ 819 | if (ctx->prepare) | ^~ /opt/AQtion/aq_macsec.c: In function ‘aq_mdo_del_rxsc’: /opt/AQtion/aq_macsec.c:886:16: error: ‘struct macsec_context’ has no member named ‘prepare’ 886 | if (ctx->prepare) | ^~ /opt/AQtion/aq_macsec.c: In function ‘aq_mdo_add_rxsa’: /opt/AQtion/aq_macsec.c:962:16: error: ‘struct macsec_context’ has no member named ‘prepare’ 962 | if (ctx->prepare) | ^~ /opt/AQtion/aq_macsec.c: In function ‘aq_mdo_upd_rxsa’: /opt/AQtion/aq_macsec.c:992:16: error: ‘struct macsec_context’ has no member named ‘prepare’ 992 | if (ctx->prepare) | ^~ /opt/AQtion/aq_macsec.c: In function ‘aq_mdo_del_rxsa’: /opt/AQtion/aq_macsec.c:1043:16: error: ‘struct macsec_context’ has no member named ‘prepare’ 1043 | if (ctx->prepare) | ^~ /opt/AQtion/aq_macsec.c: In function ‘aq_mdo_get_dev_stats’: /opt/AQtion/aq_macsec.c:1058:16: error: ‘struct macsec_context’ has no member named ‘prepare’ 1058 | if (ctx->prepare) | ^~ /opt/AQtion/aq_macsec.c: In function ‘aq_mdo_get_tx_sc_stats’: /opt/AQtion/aq_macsec.c:1087:16: error: ‘struct macsec_context’ has no member named ‘prepare’ 1087 | if (ctx->prepare) | ^~ /opt/AQtion/aq_macsec.c: In function ‘aq_mdo_get_tx_sa_stats’: /opt/AQtion/aq_macsec.c:1120:16: error: ‘struct macsec_context’ has no member named ‘prepare’ 1120 | if (ctx->prepare) | ^~ /opt/AQtion/aq_macsec.c: In function ‘aq_mdo_get_rx_sc_stats’: /opt/AQtion/aq_macsec.c:1161:16: error: ‘struct macsec_context’ has no member named ‘prepare’ 1161 | if (ctx->prepare) | ^~ /opt/AQtion/aq_macsec.c: In function ‘aq_mdo_get_rx_sa_stats’: /opt/AQtion/aq_macsec.c:1210:16: error: ‘struct macsec_context’ has no member named ‘prepare’ 1210 | if (ctx->prepare) | ^~ make: [/usr/src/linux-headers-6.1.0-28-common/scripts/Makefile.build:255: /opt/AQtion/aq_macsec.o] Error 1 (ignored) /usr/src/linux-headers-6.1.0-28-common/scripts/check-local-export: nm failed Terminated make: [/usr/src/linux-headers-6.1.0-28-common/scripts/Makefile.build:255: /opt/AQtion/aq_macsec.o] Error 143 (ignored) LD [M] /opt/AQtion/atlantic.o ld: cannot find /opt/AQtion/aq_vec.o: No such file or directory ld: cannot find /opt/AQtion/aq_ptp.o: No such file or directory ld: cannot find /opt/AQtion/aq_macsec.o: No such file or directory make: [/usr/src/linux-headers-6.1.0-28-common/scripts/Makefile.build:468: /opt/AQtion/atlantic.o] Error 1 (ignored)

Debian bookworm, kernel 6.8.0-rc5, kmod version 30 I'm working with a constrained system and need to unbind some unused PCIe ports to free up IRQs for downstream devices before they load. I am using an install command in modprobe.d/mpt3sas.conf (then rebuilding with `update-initramfs -u`)

softdep mpt3sas pre: i40e
install mpt3sas /bin/sh /usr/bin/unbind_pcieport.sh; /sbin/modprobe --ignore-install mpt3sas $CMDLINE_OPTS

but unbind_pcieport.sh doesn't fire. I've included `echos` in unbind_pcieport.sh, outputting to a log file, but no log file is ever created, indicating the script is not running at all. The unbinding works as expected if I put everything inside mpt3sas.conf like this:

install mpt3sas echo "0000:02:08.0" > /sys/bus/pci/drivers/pcieport/unbind; echo "0000:02:09.0" > /sys/bus/pci/drivers/pcieport/unbind; echo "0000:02:0a.0" > /sys/bus/pci/drivers/pcieport/unbind; /sbin/modprobe --ignore-install mpt3sas $CMDLINE_OPTS

but I'd like to have some logic in my script and it's just cleaner to not have it all in one line of the .conf This is the script body:

#!/bin/sh
# Space-separated list of PCI devices to unbind
PCI_DEVICES="0000:02:08.0 0000:02:09.0 0000:02:0a.0"
# Unbind each specified device if it exists
for DEVICE in $PCI_DEVICES; do
    if [ -e "/sys/bus/pci/drivers/pcieport/$DEVICE" ]; then
        echo "$DEVICE" > /sys/bus/pci/drivers/pcieport/unbind
        echo "Unbound $DEVICE from pcieport driver"
    else
        echo "$DEVICE not found or already unbound"
    fi
done

I've tried using /bin/bash instead of sh, and omitting /bin/bash in the .conf and just using "unbind_pcieport.sh" (with the script in $PATH) The .sh script is world executable and readable EDIT: Loking through the modprobe manual I haven't found why my script isn't executing, but I did find that you can break lines with `\, so I at least cleaned up the working mpt3sas.conf` for now:

softdep mpt3sas pre: i40e
install mpt3sas \
echo "0000:02:08.0" > /sys/bus/pci/drivers/pcieport/unbind;\
echo "0000:02:09.0" > /sys/bus/pci/drivers/pcieport/unbind;\
echo "0000:02:0a.0" > /sys/bus/pci/drivers/pcieport/unbind;\
/sbin/modprobe --ignore-install mpt3sas $CMDLINE_OPTS

I am trying to modprobe wireguard as root, and it fails with: modprobe: ERROR: could not insert 'wireguard': Operation not permitted Adding verbose I get one more line: [root@localhost ben]# insmod /lib/modules/5.2.11-100.fc29.x86_64/extra/wireguard.ko.xz insmod: ERROR: could not insert module /lib/modules/5.2.11-100.fc29.x86_64/extra/wireguard.ko.xz: Operation not permitted dkms runs fine without error. I've also disabled selinux and that made no difference. I don't see anything in the journalctl logs. Looking through man pages and Google have not turned anything up. I did find this helpful line in dmesg: Lockdown: modprobe: Loading of unsigned module is restricted; see man kernel_lockdown.7 However that man page does not exist. How can I debug this? Any pointers on where to go next?

I'm trying to make a service to load/unload a kernel module (wifi module to be specific) this is my service file:

[Unit]
Description=Wifi control
After=network.target

[Service]
Type=simple
RemainAfterExit=no

ExecStart=/sbin/modprobe brcmfmac
ExecStop=/sbin/modprobe -r brcmfmac

I have added blacklist brcmfmac to /etc/modprobe.d/brcmfmac.conf enabling/starting/disabling works perfectly But when I run systemctl stop myservice the ExecStop command will fail saying that "Module brcmfmac is in use." But when I run this command manually it works perfectly fine, I have tried a bunch of different options, running it through su or bash -c but nothing changes the outcome. I can just make it a oneshot service and instead of systemctl stop, run modprobe -r. But I like knowing why the behaviour is different here. Does anyone know why this is happening?

I have certain Broadcom drivers clearly blacklisted in 50-broadcom-wl-blacklist.conf file in /etc/modprobe.d/: # modules blacklisted for broadcom-wl blacklist bcm43xx blacklist ssb blacklist b43 blacklist b43legacy blacklist ndiswrapper blacklist brcm80211 blacklist bcma blacklist brcmsmac But they are still being loaded! $ lsmod | grep b43 b43legacy 151552 0 b43 450560 0 bcma 61440 1 b43 mac80211 888832 2 b43,b43legacy ssb 86016 2 b43,b43legacy mmc_core 163840 2 b43,ssb cfg80211 696320 4 wl,b43,mac80211,b43legacy OS: openSUSE Leap 15 Some other posts mention running mkinitrd or dracut. When is this relevant for blacklisting modules? Note, 50-broadcom-wl-blacklist.conf was probably created by some openSUSE tool, I don't remember creating it. Strange that tool wouldn't call a mkinitrd if it was necessary. We are living in systemd era, but I don't think systemd is not relevant for blacklisting modules (yet). I am blacklisting this modules because I have to use Broadcom proprietary STA driver with my bcm4360 chipset card.

I installed ZFS on Debian, but can not get it working. --- I try to install zfs this way: 1. I added this to /etc/apt/sources.list :

deb http://deb.debian.org/debian/  buster main contrib non-free
deb http://deb.debian.org/debian  buster-backports main contrib

2. apt update and apt upgrade 3. I installed these packages: buster-backports, zfsutils-linux, zfs-dkms, dpkg-dev, linux-headers-$(uname -r), linux-image-amd64 4. And at this point problems accured. --- I get these error when calling modprobe:

root@server /dev# modprobe zfs
modprobe: FATAL: **Module zfs not found in directory /lib/modules/4.19.0-14-amd64**

` This is in my journalctl:

Feb 19 13:33:46 bytserver systemd: Starting Install ZFS kernel module...
Feb 19 13:33:46 bytserver modprobe: modprobe: FATAL: Module zfs not found in directory /lib/modules/4.19.0-14-amd64
Feb 19 13:33:46 bytserver systemd: zfs-load-module.service: Main process exited, code=exited, status=1/FAILURE
Feb 19 13:33:46 bytserver systemd: zfs-load-module.service: Failed with result 'exit-code'.
Feb 19 13:33:46 bytserver systemd: Failed to start Install ZFS kernel module.
Feb 19 13:33:46 bytserver systemd: Dependency failed for Import ZFS pools by cache file.
Feb 19 13:33:46 bytserver systemd: zfs-import-cache.service: Job zfs-import-cache.service/start failed with result 'dependency'.
Feb 19 13:33:46 bytserver systemd: Reached target ZFS pool import target.
Feb 19 13:33:46 bytserver systemd: Condition check resulted in Mount ZFS filesystems being skipped.
Feb 19 13:33:46 bytserver systemd: Starting Wait for ZFS Volume (zvol) links in /dev...
Feb 19 13:33:46 bytserver zvol_wait: The ZFS modules are not loaded.
Feb 19 13:33:46 bytserver zvol_wait: Try running '/sbin/modprobe zfs' as root to load them.
Feb 19 13:33:46 bytserver systemd: Started Wait for ZFS Volume (zvol) links in /dev.
Feb 19 13:33:46 bytserver systemd: Reached target ZFS volumes are ready.
Feb 19 13:33:46 bytserver systemd: Starting ZFS file system shares...
Feb 19 13:33:46 bytserver zfs: The ZFS modules are not loaded.
Feb 19 13:33:46 bytserver zfs: Try running '/sbin/modprobe zfs' as root to load them.
Feb 19 13:33:46 bytserver systemd: zfs-share.service: Main process exited, code=exited, status=1/FAILURE
Feb 19 13:33:46 bytserver systemd: zfs-share.service: Failed with result 'exit-code'.
Feb 19 13:33:46 bytserver systemd: Failed to start ZFS file system shares.
Feb 19 13:33:46 bytserver systemd: Reached target ZFS startup target.
Feb 19 13:33:47 bytserver containerd: time="2021-02-19T13:33:47.608958319+01:00" level=info msg="loading plugin \"io.containerd.snapshotter.v1.zfs\"..." type=io.containerd.snapshotter.v1
Feb 19 13:33:47 bytserver containerd: time="2021-02-19T13:33:47.609214490+01:00" level=info msg="skip loading plugin \"io.containerd.snapshotter.v1.zfs\"..." error="path /var/lib/containerd/io.containerd.snapshotter.v1.zfs must be a zfs filesystem to be used with the zfs snapshotter: skip plugin" type=io.containerd.snapshotter.v1
Feb 19 14:27:39 bytserver sudo:     john : TTY=pts/1 ; PWD=/dev/disk/by-label ; USER=root ; COMMAND=/usr/bin/apt install zfs
Feb 19 14:27:53 bytserver sudo:     john : TTY=pts/1 ; PWD=/dev/disk/by-label ; USER=root ; COMMAND=/usr/bin/apt install zfs
Feb 19 14:30:58 bytserver sudo:     john : TTY=pts/1 ; PWD=/dev/disk/by-label ; USER=root ; COMMAND=/usr/bin/apt-get install zfs-dkms
Feb 19 14:31:21 bytserver sudo:     john : TTY=pts/1 ; PWD=/dev/disk/by-label ; USER=root ; COMMAND=/usr/sbin/modprobe zfs
Feb 19 14:31:29 bytserver sudo:     john : TTY=pts/1 ; PWD=/dev/disk/by-label ; USER=root ; COMMAND=/usr/bin/apt install zfs
Feb 19 14:34:21 bytserver sudo:     john : TTY=pts/1 ; PWD=/dev/disk/by-label ; USER=root ; COMMAND=/usr/bin/add-apt-repository ppa:zfs-native/stable
Feb 19 14:52:35 bytserver sudo:     john : TTY=pts/1 ; PWD=/home/john/openzfs-docs ; USER=root ; COMMAND=/usr/bin/vi /etc/apt/sources.list
Feb 19 14:53:47 bytserver sudo:     john : TTY=pts/1 ; PWD=/home/john/openzfs-docs ; USER=root ; COMMAND=/usr/bin/apt update
Feb 19 14:53:59 bytserver sudo:     john : TTY=pts/1 ; PWD=/home/john/openzfs-docs ; USER=root ; COMMAND=/usr/bin/vi /etc/apt/sources.list
Feb 19 14:54:08 bytserver sudo:     john : TTY=pts/1 ; PWD=/home/john/openzfs-docs ; USER=root ; COMMAND=/usr/bin/apt update
Feb 19 14:54:54 bytserver sudo:     john : TTY=pts/1 ; PWD=/home/john/openzfs-docs ; USER=root ; COMMAND=/usr/bin/su
Feb 19 14:56:22 bytserver sudo:     root : TTY=pts/1 ; PWD=/home/john/openzfs-docs ; USER=root ; COMMAND=/usr/bin/apt upgrade
Feb 19 14:56:59 bytserver sudo:    john : TTY=pts/1 ; PWD=/home/john/openzfs-docs ; USER=root ; COMMAND=/usr/bin/apt install --yes -t buster-backports --no-install-recommends zfs-dkms
Feb 19 14:57:20 bytserver sudo:     john : TTY=pts/1 ; PWD=/home/john/openzfs-docs ; USER=root ; COMMAND=/usr/bin/apt install --yes -t buster-backports zfsutils-linux
Feb 19 14:57:39 bytserver sudo:     john : TTY=pts/1 ; PWD=/home/john/openzfs-docs ; USER=root ; COMMAND=/usr/bin/apt install --yes mdadm
Feb 19 15:03:10 bytserver sudo:     john : TTY=pts/1 ; PWD=/home/john ; USER=root ; COMMAND=/usr/bin/apt install -t buster-backports zfsutils-linux
Feb 19 15:03:23 bytserver sudo:     john : TTY=pts/1 ; PWD=/home/john ; USER=root ; COMMAND=/usr/bin/apt install -t buster-backports zfsutils-linu
Feb 19 15:03:33 bytserver sudo:     john : TTY=pts/1 ; PWD=/home/john ; USER=root ; COMMAND=/usr/bin/apt install zfs-dkms
Feb 19 15:05:36 bytserver systemd-udevd: Process '/sbin/modprobe zfs' failed with exit code 1.
Feb 19 15:07:20 bytserver systemd-udevd: Process '/sbin/modprobe zfs' failed with exit code 1.
Feb 19 15:10:51 bytserver sudo:     john : TTY=pts/1 ; PWD=/home/john ; USER=root ; COMMAND=/usr/bin/apt-get -y install zfs-dkms
Feb 19 15:11:58 bytserver sudo:     john : TTY=pts/1 ; PWD=/home/john ; USER=root ; COMMAND=/usr/bin/systemctl restart zfs-import-cache
Feb 19 15:11:58 bytserver systemd: Starting Install ZFS kernel module...
Feb 19 15:11:58 bytserver modprobe: modprobe: FATAL: Module zfs not found in directory /lib/modules/4.19.0-14-amd64
Feb 19 15:11:58 bytserver systemd: zfs-load-module.service: Main process exited, code=exited, status=1/FAILURE
Feb 19 15:11:58 bytserver systemd: zfs-load-module.service: Failed with result 'exit-code'.
Feb 19 15:11:58 bytserver systemd: Failed to start Install ZFS kernel module.
Feb 19 15:11:58 bytserver systemd: Dependency failed for Import ZFS pools by cache file.
Feb 19 15:11:58 bytserver systemd: zfs-import-cache.service: Job zfs-import-cache.service/start failed with result 'dependency'.
Feb 19 15:15:56 bytserver sudo:     john : TTY=pts/1 ; PWD=/home/john ; USER=root ; COMMAND=/usr/bin/apt-get install zfsutils-linux

What could I do diagnoze and to fix it? Thank you for help

In my new installed Centos 9 stream, I try to install virtualbox guest addition and it fails with error:

sudo tail /var/log/vboxadd-setup.log

modprobe vboxguest fail

Here is my setup:

uname -r
5.14.0-467.el9.x86_64

and the kernel headers:

sudo yum list | grep kernel

And the status of the other dependencies: The rebooting also does not help. I cannot think of any other solution. Please help.

In order to run a virtual machine, VirtualBox tells me to disable the KVM kernel module. I googled around and found out that KVM is included in the qemu-*-packages, but none of them is/was installed on my system (Debian Wheezy). After that I simply tried to unload the module, but this doesn't want to work because it is in use: # modprobe -r kvm_intel FATAL: Module kvm_intel is in use. # modprobe -r kvm FATAL: Module kvm is in use. I don't know what program is using it and I have really no idea what that could be. I also tried with the -f option but I get the same result. My question is: How can I remove or disable the KVM Kernel module? ***Update:*** Here is the output of the lsmod command: # lsmod | grep kvm kvm_intel 138825 3 kvm 404853 1 kvm_intel

man modprobe says in the ENVIRONMENT section: > The MODPROBE_OPTIONS environment variable can also be used to pass > arguments to modprobe. But this is unclear. Suppose for example that I want to force the module search path by faking the kernel version string. That is the -S option. Should it be: - MODPROBE_OPTIONS='-S fake-version' or - MODPROBE_OPTIONS='-Sfake-version' or - MODPROBE_OPTIONS='--set-version fake-version' or - MODPROBE_OPTIONS='--set-version=fake-version' or maybe - MODPROBE_OPTIONS='set-version=fake-version' ?? This is a situation where a single example would have made all the difference. Thanks, -- Ian

I recently bought a new keyboard, it was cheap and of an unknown brand but i wasn't particularly worried. I found out that on linux pressing __shift, super, left-ctrl or left-alt with this keyboard__ made no difference, it always take it __as shift__. I made some researches and it turns out the problem is the chipset used by the keyboard. I read that the only way to solve the problem is to write a driver for the keyboard, but, while working on it i found out that running __sudo modprobe usbmon__ and then __opening wireshark as sudo__, unexpectedly __fixes the problem__... someone knows why this happen? and if there is a simpler way to trigger this change? to be more specific: - i'm on xubuntu 18.04 - dmyco is the brand of the keyboard - the result of lsusb is >> Bus 001 Device 004: ID 1c4f:0056 SiGma Micro

So normaly during boot or when a device is hotplugged Linux loads kernel modules for hardware based on modaliases. Is there a way to manually trigger this for a specific device or a general "rescan" for the whole system? e.g. I have a pci device which had no matching driver during boot. Then I install a driver package with several modules. Now I want the system the automatically pick the right one based on modaliases and load it like it would on a reboot, without actually rebooting.

I'm trying to load the fuse kernel module but for some reason it seems like it's not getting loaded. But I also don't get any error message. Can someone explain to me what's going on?

root@my-host:~# modprobe fuse
root@my-host:~# echo $?
0
root@my-host:~# lsmod | grep fuse 
root@my-host:~# modinfo fuse
modinfo: ERROR: Module fuse not found.
root@my-host:~# ls /lib/modules/$(uname -r)/kernel/fs/fuse/
cuse.ko
root@my-host:~#

I'm on a cloud VM:

root@my-host:~# uname -r
4.15.0-213-generic
root@my-host:~# lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.6 LTS
Release:	18.04
Codename:	bionic

I also rebooted the host before I ran these commands to make sure the correct kernel is running. ---- EDIT: In response to the comments I ran these commands:

root@my-host:~# grep fuse /lib/modules/$(uname -r)/modules.builtin
kernel/fs/fuse/fuse.ko
root@my-host:~# systemd-detect-virt
kvm