I have Fedora 20 setup with default kernel configuration, where bridge feature is enabled as a module (CONFIG_BRIDGE=m), and the bridge module loads as the system starts. I don't understand who initiates it, since I have not found anything about bridge.ko in /etc/sysconfig/modules/*. However it ends up in the memory and every time I have to 'rmmod' it. I would like to prohibit loading of the bridge.ko on the start up, yet I still want to manually load/unload bridge.ko whenever necessary. I know it is possible to use the blacklist feature in /etc/modprobe.d/blacklist.conf, but can anybody point out who is loading bridge.ko in default setup of Fedora 20?

I am trying to access SD cards on Fedora 28, but do not have any success. System info is as follows: $ lsb_release -a LSB Version: :core-4.1-amd64:core-4.1-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-4.1-amd64:desktop-4.1-noarch:languages-4.1-amd64:languages-4.1-noarch:printing-4.1-amd64:printing-4.1-noarch Distributor ID: Fedora Description: Fedora release 28 (Twenty Eight) Release: 28 Codename: TwentyEight I was not able to access different SD cards using two different card readers. Despite of being accessible on both macOS and Windows, none of them is shown in the Nautilus file browser, the desktop or elsewhere obvious. The card readers are recognized by the system as per lsusb output: $ lsusb -v # some other USB devices Bus 001 Device 005: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x058f Alcor Micro Corp. idProduct 0x6362 Flash Card Reader/Writer bcdDevice 1.29 iManufacturer 1 iProduct 2 iSerial 3 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 250mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk-Only iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 # some other USB devices Bus 001 Device 006: ID 0dda:2027 Integrated Circuit Solution, Inc. USB 2.0 Card Reader Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x0dda Integrated Circuit Solution, Inc. idProduct 0x2027 USB 2.0 Card Reader bcdDevice 1.6e iManufacturer 1 iProduct 2 iSerial 3 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 4 bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk-Only iInterface 5 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 # some other USB devices I then had a look at the udev events while plugging a card in and out: $ udevadm monitor monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[701.434565] change /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host4/target4:0:0/4:0:0:2/block/sde (block) UDEV [714.263816] change /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host4/target4:0:0/4:0:0:2/block/sde (block) KERNEL[748.477184] change /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host4/target4:0:0/4:0:0:2/block/sde (block) UDEV [761.338940] change /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host4/target4:0:0/4:0:0:2/block/sde (block) In addition, I had a look at the kernel messages: $ dmesg [ 603.846840] usb-storage 1-3:1.0: USB Mass Storage device detected [ 603.847749] scsi host4: usb-storage 1-3:1.0 [ 605.703531] scsi 4:0:0:0: Direct-Access Generic CF 1.6E PQ: 0 ANSI: 0 CCS [ 605.704982] scsi 4:0:0:1: Direct-Access Generic MS 1.6E PQ: 0 ANSI: 0 CCS [ 606.509034] scsi 4:0:0:2: Direct-Access Generic MMC/SD 1.6E PQ: 0 ANSI: 0 CCS [ 606.510387] scsi 4:0:0:3: Direct-Access Generic SM 1.6E PQ: 0 ANSI: 0 CCS [ 606.511519] sd 4:0:0:0: Attached scsi generic sg4 type 0 [ 606.511943] sd 4:0:0:1: Attached scsi generic sg5 type 0 [ 606.512177] sd 4:0:0:2: Attached scsi generic sg6 type 0 [ 606.512408] sd 4:0:0:3: Attached scsi generic sg7 type 0 [ 608.924586] sd 4:0:0:1: [sdd] Attached SCSI removable disk [ 629.830776] sd 4:0:0:2: [sde] Attached SCSI removable disk [ 633.048754] sd 4:0:0:3: [sdf] Attached SCSI removable disk [ 639.490479] sd 4:0:0:0: [sdc] Attached SCSI removable disk Both the output of dmesg and udevadm monitor are telling that the card should be shown as sde. However, fdisk -l does not list sde. Besides that, trying to mount the device manually, raises an error: $ mount -t auto /dev/sde /mnt/ mount: /mnt: no medium found on /dev/sde. I am not sure, whether the needed driver module is loaded properly, since there is no mmc0-like entry in the dmesg output (as I am used to know from Debian-based systems). lsmod does not list the mmc0 kernel module either: $ lsmod | grep mm rtl8192c_common 61440 1 rtl8192cu rtlwifi 98304 3 rtl8192c_common,rtl_usb,rtl8192cu The only mmc-like modules which seems to be available but are not loaded are mmc_block and mmc_core: $ modprobe mm # listing suggestions using tab auto-completion mma7660 mmc_block mmc_core mms114 How could I solve this problem or at least narrow it down?

During compilation of customized distribution (using buildroot v. 11.2018) I have problem with libmount library (the problem appeared after I had included efl package in buildroot menuconfig - *Target packages -> Graphic lib... -> efl* ). I have additionaly installed package libmount-dev with no results. checking for getxattr in -lc... yes checking sys/xattr.h usability... yes checking sys/xattr.h presence... yes checking for sys/xattr.h... yes checking for XATTR_NOFOLLOW... no checking for LIBMOUNT... no configure: error: *** Could not find libmount How to include this library to obtain succesful compilation?

My Arch (3.6.5-1) is exhibiting a rather peculiar problem: when wifi is set up, all logs indicate that the setup was successful and that the interface is up and functional. However, when attempting to access a website (or execute ping) all requests time out (despite that connection is reported as working and signal at 63% strength). This tends to happen randomly after laptop is switched on - after some time the connection usually starts working and does not break until next shutdown/suspend. Relevant dmesg entries (full dmesg output can be found [here](http://pastebin.com/PH7jb8fy)) : [ 13.858528] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 14.024275] r8169 0000:02:00.0: eth0: link down [ 14.024339] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 34.895920] wlan0: authenticate with 00:24:6c:c8:e4:a1 [ 34.900827] wlan0: send auth to 00:24:6c:c8:e4:a1 (try 1/3) [ 34.902963] wlan0: authenticated [ 34.908362] wlan0: associate with 00:24:6c:c8:e4:a1 (try 1/3) [ 34.911153] wlan0: RX AssocResp from 00:24:6c:c8:e4:a1 (capab=0x1431 status=0 aid=9) [ 34.911217] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 34.911294] wlan0: associated ip -s link shows: wlan0: mtu 1500 qdisc mq state UP mode DORMANT qlen 1000 link/ether 50:b7:c3:1e:f4:21 brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped overrun mcast 14970982 50472 0 0 0 0 TX: bytes packets errors dropped carrier collsns 19116 233 0 0 0 0 ip minotor outputs some failure messages: [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED [LINK]3: wlan0: link/ether [LINK]3: wlan0: mtu 1500 qdisc mq state DOWN link/ether 50:b7:c3:1e:f4:21 brd ff:ff:ff:ff:ff:ff [LINK]3: wlan0: mtu 1500 qdisc mq state DORMANT link/ether 50:b7:c3:1e:f4:21 brd ff:ff:ff:ff:ff:ff [LINK]3: wlan0: link/ether [LINK]3: wlan0: link/ether [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED [LINK]3: wlan0: mtu 1500 qdisc mq state UP link/ether 50:b7:c3:1e:f4:21 brd ff:ff:ff:ff:ff:ff [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]ff02::2 dev wlan0 lladdr 33:33:00:00:00:02 NOARP [NEIGH]ff02::1:ff1e:f421 dev wlan0 lladdr 33:33:ff:1e:f4:21 NOARP [NEIGH]ff02::16 dev wlan0 lladdr 33:33:00:00:00:16 NOARP [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.79.218 dev lo lladdr 00:00:00:00:00:00 NOARP [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED [LINK]3: wlan0: link/ether [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED All that should be loaded seem to be ([output of lsmod](http://pastebin.com/zJm1NiX9)) . Any idea on how to solve this or what the problem is?

I was trying to update the drivers of a system with a couple of Nvidia GTX 980 cards but somehow I messed up and now I encounter this error when I run the installer with Nvidia: ERROR: An NVIDIA kernel module 'nvidia-uvm' appears to already be loaded in your kernel. This may be because it is in use (for example, by the X server), but may also happen if your kernel was configured without support for module unloading. Please be sure you have exited X before attempting to upgrade your driver. If you have exited X, know that your kernel supports module unloading, and still receive this message, then an error may have occured that has corrupted the NVIDIA kernel module's usage count; the simplest remedy is to reboot your computer. lsmod | grep -i nvidia gives: nvidia_uvm 77824 0 nvidia 8540160 77 nvidia_uvm drm 344064 4 nvidia So the suggestion that an error may have occured that corrupted the kernel module usage count makes sense, however, the remedy does not help and rebooting does not do a thing. I have tried blacklisting both modules in different ways and no matter what I do they are always back. Doing rmmod or modprobe -r does not help either. In fact with the later I get: modprobe: FATAL: Module nvidia-uvm not found. I have tried everything I found on the net, nothing changed that 77 there. Any ideas? Thanks!

I seem to be having a bizarre problem installing a new custom kernel. update-initramfs fails during dpkg -i with: update-initramfs: Generating /boot/initrd.img-5.15.7-hardened1-test1 find: ‘/tmp/user/0/mkinitramfs_gHxWMQ/lib/modules/5.15.7-hardened1-test1/kernel’: No such file or directory Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.15.7-hardened1-r7 Found initrd image: /boot/initrd.img-5.15.7-hardened1-r7 Found linux image: /boot/vmlinuz-5.15.7-hardened1-test1 Found initrd image: /boot/initrd.img-5.15.7-hardened1-test1 Found linux image: /boot/vmlinuz-5.10.0-10-amd64 Found initrd image: /boot/initrd.img-5.10.0-10-amd64 done The r7 kernel builds and installs perfectly fine, but the test1 installs with a find: ‘/tmp/user/0/mkinitramfs_gHxWMQ/lib/modules/5.15.7-hardened1-test1/kernel’: No such file or directory error. The only difference between the .configs is: 29c29 CONFIG_LOCALVERSION="-test1" 39c39 # CONFIG_KERNEL_GZIP is not set 45c45 CONFIG_KERNEL_ZSTD=y 787c787 CONFIG_MODULE_FORCE_UNLOAD=y 802,803c802,803 # CONFIG_MODULE_COMPRESS_XZ is not set > CONFIG_MODULE_COMPRESS_ZSTD=y I even tried a slightly newer kernel (5.15.27) and older (5.10.104) with the same results. Trying to boot into the kernel drops the boot to a initramfs prompt (without USB keyboard functionality) after failing to find the root LVM. The initrd images also have very different sizes for the minimal changes made: 9.7M initrd.img-5.15.7-hardened1-r7 (working) 9.1M initrd.img-5.15.7-hardened1-test1 (broke) Doing a diff between the two with lsinitrd produces this, suggesting that the initrd does indeed lack a huge number of modules. 346,399c346 5.15.7-hardened1-test1 Anyone seen this before? I found one results through google but a solution was never provided. I'm running Devuan Chimaera (Debian 11 base) with: initramfs-tools=0.140 & dpkg=1.20.9

99% of the time, sudo kill -9 on a user space process will result in a (relatively) successful termination. However, what extra considerations might there be for killing kernel tasks? A sample scenario might be field testing a new device driver where I also have a watchdog process that monitors the driver. If my watchdog detects the driver status API returning a fatal error condition, the driver not responding within a few seconds, excessive CPU usage, corruption of the code segment, etc, how safe is it to just kill and restart the process kernel module, ignoring issues like leaving the device it is driving in an intermediate state? If lsmod shows it is being used by other modules, are there other issues to consider? [This is a related question](https://unix.stackexchange.com/q/152090/46316) as I envisage my driver starting on init.

When trying to run

tc qdisc add dev $INTERFACE root handle 1: prio priomap 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
   tc qdisc add dev $INTERFACE parent 1:1 handle 10: netem loss "${LOSS}"%

I get the error of Specified qdisc not found yum -y install kernel-modules-extra works as a fix, but requires a reboot. In my case, a reboot is not an option Is there a way around a reboot to get qdisk working? RHEL 8.6

*System: Ubuntu MATE 24.04.2* I tried to start a virtual machine under VirtualBox and received the following error: > VirtualBox can't enable the AMD-V extension. Please disable the KVM kernel extension, recompile your kernel and reboot (VERR_SVM_IN_USE). I made no changes to my system (that I am aware) to cause this. Yesterday all was fine, today the problem. Fortunately, a quick search revealed the following article with the solution: Quick Fix VirtualBox can’t enable the AMD-V extension I am assuming that KVM was enabled in a background system update. Questions: 1) How and why were the KVM modules enabled? 2) Can I safely, as per the article, permanently blacklist the kvm and kvm_amd modules?

I am trying to get my Blackmagic Quad HDMI Recorder working on Arch Linux. Since rebooting after the first installation, the device was never recognized by Blackmagic Software on Arch, while it continues to work on Windows. I suspect that this has to do with [the latest version of Desktop Video not released for Windows.](https://www.blackmagicdesign.com/support/family/capture-and-playback) A Fedora user created module patches for the [blackmagic](https://forum.blackmagicdesign.com/viewtopic.php?f=12&t=223633) and [blackmagic-io modules](https://forum.blackmagicdesign.com/viewtopic.php?f=12&t=215626) , but they failed on my PC.

> lspci | grep Blackmagic
05:00.0 Multimedia video controller: Blackmagic Design DeckLink Quad HDMI Recorder

> lsmod | grep blackmagic
blackmagic794624  0
blackmagic_io2424832  4

> dkms status -m blackmagic -k uname -r
blackmagic/14.4.1a4, 6.15.6-arch1-1, x86_64: installed
> dkms status -m blackmagic-io -k uname -r
blackmagic-io/14.4.1a4, 6.15.6-arch1-1, x86_64: installed

> sudo modprobe blackmagic-io

> sudo dkms build -m blackmagic -v 14.4.1a4
Module blackmagic/14.4.1a4 already built for kernel 6.15.6-arch1-1 (x86_64), skip. You may override by specifying --force.
> sudo dkms build -m blackmagic-io -v 14.4.1a4
Module blackmagic-io/14.4.1a4 already built for kernel 6.15.6-arch1-1 (x86_64), skip. You may override by specifying --force.

> cd /usr/src/blackmagic-io-14.4.1a4/
> sudo patch  sudo patch  cd ../blackmagic-14.4.1a4/
> sudo patch  sudo dkms install -m blackmagic-io -v 14.4.1 --all
Error! The action install does not support the --all parameter.

BlackMagic's FAQ in their Linux installer: > > * How do I update the firmware on a device? > > The device's firmware can be updated with the BlackmagicFirmwareUpdater. > See the man page for instructions and examples on how to use the utility. > > * The driver crashed my system > > Look for kernel output messages in dmesg and /var/log/messages. > > * The package installed, but the driver was not loaded > > Try the following command: > > # dkms status -m blackmagic-io -k uname -r > > If the status is 'installed', then the module is installed, but probably > not loaded. It can be loaded with the following command: > > # sudo modprobe blackmagic-io > > If the status is 'added', then the module failed to build. You can issue > the following command to manually run the build and use the output to > determine the problem. > > # sudo dkms build -m blackmagic-io -v 14.4.1 > > The full module version number is in the form 14.4.1aXX. This module number > can be found by running dkms status. > > A common cause is a version mismatch between the installed kernel image, > and the kernel source/headers. If they do not match, simply bring either > the source/headers or the image version up to date, and reboot your system. > Once the system is back up, the driver should be built for you at startup. > The command to install matching headers for your currently running kernel > on CentOS is: > > # sudo yum install "kernel-devel-uname-r == $(uname -r)" > > If the status is 'built', then the module has been built, but not > installed. You can issue the following command to manually install and use > the output to determine the problem. > > # sudo dkms install -m blackmagic-io -v 14.4.1 --all > > Legacy Desktop Video products on x86_64 platforms use an older driver. > Users should build and install this module with the dkms commands above, > replacing -m blackmagic-io option with -m blackmagic. > > > Known Issues > ------------ > > * Kernel module fails to install due to CET/IBT > > Intel 11th Generation and later CPUs and Linux kernels from version 5.18 > have included an Indirect Branch Tracking (IBT) feature. Linux > distributions are gradually enabling this kernel feature. For example > Fedora 40 has enabled it. The Desktop Video kernel module will fail to > load if both the CPU and distribution support IBT, this will result in > "(failed)" messages when installing Desktop Video and lines in dmesg such > as: > Missing ENDBR: nothing+0x0/0x10 [blackmagic_io] > and > kernel BUG at arch/x86/kernel/cet.c:102! > To work around this, disable IBT by adding ibt=off to the kernel command > line. > > * Performance of Nvidia embedded platforms > > Nvidia devices like Jetson may default to a mid-range power/performance > mode, eg. 30W / "mode 2". When using higher-end video modes that require > more processing, you may have to increase this setting. Refer to the > nvpmodel command or other related method in NVidia's documentation. > > * Incompatibility with small memory systems > > Sufficient memory must be available to the driver to support the number of > devices installed and their frame buffering requirements. A 64 bit system > with adequate memory is strongly recommended. In some configurations, > reserving more memory at boot for vmalloc may be necessary. More memory > can be allocated by adding 'vmalloc=' option to the kernel command > line. > > e.g. vmalloc=256M > > * Driver fails to build against certain version of linux-rt > > Some versions of the linux-rt patchset may be incompatible with the > driver. > > * ASPM with some PCI-e cards > > Some PCI-e cards (1x lane cards) do not function properly by default when > ASPM is enabled. When in this state, the device will be listed in lspci > and the BlackmagicFirmwareUpdater status will report version ff. To work > around this please add kernel boot parameter "pcie_aspm=off" to your boot > loader. > > * Settings are not saved on some versions of Fedora > > This issue is caused by the SELinux policies being incorrect on the > preferences file. To fix this issue, ensure the policycoreutils-python-utils > package is installed and run the following commands: > > # sudo rm /etc/blackmagic/BlackmagicPreferences.xml > # sudo semanage fcontext -a -t etc_runtime_t /etc/blackmagic > # sudo restorecon /etc/blackmagic

How can I take snippets from the Linux kernel drivers' code, for example this [drm_fb_helper_hotplug_event](https://github.com/torvalds/linux/blob/6832a9317eee280117cd695fa885b2b7a7a38daf/drivers/gpu/drm/drm_fb_helper.c#L1943) function inside drivers/gpu/drm/drm_fb_helper.c, and compile a binary file that I can run to conveniently achieve a particular action in the kernel? In my case, I'd like to call the function arbitrarily to hopefully force a reset of the list of video connectors detected by the kernel, because of monitor output issues. There are probably better ways of achieving this, such as making an out-of-tree module, but I'm not sure how I can do that here. I want to compile an executable that I run from userspace, which will get my task done. So far as a proof of concept, I have tried to get printk/printfs done using only gcc to compile a binary instead of make: HOSTCC=gcc-11 CC=gcc-11 gcc ../drivers/gpu/drm/testing_printout.c -o printAMessage -I. (Compiling an older version that needs GCC 11, after a cd include using -I as the [equivalent to CPATH](https://stackoverflow.com/questions/558803/how-can-i-add-a-default-include-path-for-gcc-in-linux).) But this comes up with problems.

./linux/atomic.h:7:10: fatal error: asm/atomic.h: No such file or directory

So I made a symlink; ln -s asm-generic asm But I still get other header file related errors and warnings:

./linux/thread_info.h:60:10: fatal error: asm/thread_info.h: No such file or directory

I have tried appending ARCH=x86 to the gcc command but it didn't help. Other errors like

./linux/stddef.h:11:9: error: cannot use keyword ‘false’ as enumeration constant
./linux/stddef.h:11:9: note: ‘false’ is a keyword with ‘-std=c23’ onwards
./linux/types.h:30:33: error: ‘bool’ cannot be defined via ‘typedef’
./linux/types.h:30:33: note: ‘bool’ is a keyword with ‘-std=c23’ onwards
...
./linux/atomic/atomic-arch-fallback.h:2245:35: error: unknown type name ‘atomic64_t’; did you mean ‘atomic_t’?

tell me something is wrong with the include files and the CLAGS. What am I missing? Seeing the -std=c23 note made me look at the Makefile at the root of the source directory:

LINUXINCLUDE    := \
		-I$(srctree)/arch/$(SRCARCH)/include \
		-I$(objtree)/arch/$(SRCARCH)/include/generated \
		$(if $(building_out_of_srctree),-I$(srctree)/include) \
		-I$(objtree)/include \
		$(USERINCLUDE)

KBUILD_AFLAGS   := -D__ASSEMBLY__ -fno-PIE
KBUILD_CFLAGS   := -Wall -Wundef -Werror=strict-prototypes -Wno-trigraphs \
		   -fno-strict-aliasing -fno-common -fshort-wchar -fno-PIE \
		   -Werror=implicit-function-declaration -Werror=implicit-int \
		   -Werror=return-type -Wno-format-security \
		   -std=gnu89

I guess using gcc directly instead of the makefiles is really inconvenient. What is the usual way of achieving my goal?

I am a cybersecurity student with what is seeming like at this point some lofty goals. I’m building an RF detector/locator on a Raspberry Pi 4 (8GB) with a SanDisk 32GB microSD card running Raspberry Pi OS Bookworm (64-bit, Desktop), using XTRX (SDR) and other components. **Problem:** After running sudo apt update and sudo apt upgrade, my kernel is 6.12.34+rpt-v8 (uname -r), and xtrx-dkms (0.0.1+git20190320.5ae3a3e-3.2) fails to compile. **What I Did:**

sudo apt update
sudo apt upgrade
sudo apt install xtrx-dkms

**Error (from /var/lib/dkms/xtrx/*/build/make.log):**

error: ‘vm_flags’ undeclared
error: ‘uart_state’ has no member named ‘xmit’
error: ‘class_create’ undeclared

**Output:**

$ uname -r
6.12.34+rpt-v8
$ dpkg --print-architecture
arm64

**What I Expected:** apt upgrade to maintain a compatible kernel (e.g., 6.1.x), and xtrx-dkms to compile and load (lsmod | grep xtrx). **Actual Behavior:** apt upgrade updated to 6.12.34+rpt-v8, causing xtrx-dkms compilation to fail with: E: Sub-process /usr/bin/dpkg returned an error code (1) **Goal:** Revert to kernel 6.1.63-rpi-v8, pin it, and compile xtrx-dkms (possibly using [https://github.com/myriadrf/xtrx_linux_pcie_drv](https://github.com/myriadrf/xtrx_linux_pcie_drv) patch). **Question:** How do I revert to kernel 6.1.63-rpi-v8, pin it, and compile xtrx-dkms on Raspberry Pi OS Bookworm? Is the GitHub patch sufficient? **Planned Steps:**

sudo apt install linux-image-rpi-v8=1:6.1.63-1+rpt1 linux-headers-rpi-v8=1:6.1.63-1+rpt1
sudo nano /boot/firmware/config.txt

**Add:**

[all]
kernel=vmlinuz-6.1.63-rpi8-rpi-v8
initramfs initrd.img-6.1.63-rpi8-rpi-v8 followkernel
auto_initramfs=1

sudo apt-mark hold linux-image-rpi-v8 linux-headers-rpi-v8
sudo reboot

Any help would be appreciated! Thanks!

I'm aware of Linux softirqs **may** run within specific per-cpu kernel thread context -- ksoftirqd/[cpu_id]. Kernel threads are similar to user-space threads, however they only execute kernel code in kernel mode (they don't have user mode stacks). Suppose that at any given point in time, a ksoftirqd kernel thread is running a softirq (i.e. deferred work from a Top half interrupt handler). As far as I know, kernel threads share the virtual address range to which kernel code (including loaded kernel modules) is mapped to. What would happen if the softirq bottom half kernel code attempted to access a virtual address (VA) within the user space VA range ? I'm not sure an error would actually occur, but I believe the result of such an access would be unpredictable though. Does it make sense ? Thanks. BTW, I run the following trace-cmd command to dig into some details root@eve-ng62-28:~# trace-cmd start -e net:netif_receive_skb_entry root@eve-ng62-28:~# trace-cmd show # tracer: nop # # entries-in-buffer/entries-written: 2/2 #P:48 # # _-----=> irqs-off/BH-disabled # / _----=> need-resched # | / _---=> hardirq/softirq # || / _--=> preempt-depth # ||| / _-=> migrate-disable # |||| / delay # TASK-PID CPU# ||||| TIMESTAMP FUNCTION # | | | ||||| | | qemu-system-x86-2064265 b.... 599782.975041: netif_receive_skb_entry: dev=vunl0_2_0 napi_id=0x0 queue_mapping=1 skbaddr=00000000b36764b3 vlan_tagged=0 vlan_proto=0x0000 vlan_tci=0x0000 protocol=0x0800 ip_summed=0 hash=0x00000000 l4_hash=0 len=84 data_len=0 truesize=768 mac_header_valid=1 mac_header=-14 nr_frags=0 gso_size=0 gso_type=0x0 qemu-system-x86-2064265 b.... 599783.973971: netif_receive_skb_entry: dev=vunl0_2_0 napi_id=0x0 queue_mapping=1 skbaddr=00000000dd8af289 vlan_tagged=0 vlan_proto=0x0000 vlan_tci=0x0000 protocol=0x0800 ip_summed=0 hash=0x00000000 l4_hash=0 len=84 data_len=0 truesize=768 mac_header_valid=1 mac_header=-14 nr_frags=0 gso_size=0 gso_type=0x0 As you can check, netif_receive_skb_entry tracepoint within netif_receive_skb() kernel function/routine is triggered. It has the b value for the irqs-off/BH-disabled field. Does it mean netif_receive_skb() is actually running within a BH softirq with Bottom Half(BH) disabled ?

I'm running Fedora and trying to use make. When I run it, I get the error:

make -C /lib/modules/6.14.5-100.fc40.x86_64/build  M=/home/[my_name]/[folder_of_thing]  
make: Entering directory '/home/[my_name]/[folder_of_thing]'
make: *** /lib/modules/6.14.5-100.fc40.x86_64/build: No such file or directory.  Stop.
make: Leaving directory '/home/[my_name]/[folder_of_thing]'
make: *** [Makefile:5: default] Error 2

As far as I can tell, that build file exists in the /lib/modules/6.14.5-100.fc40.x86_64/ folder. Please advise! Thank you so much for your help! Edit: the issue was a broken symbolic link. The solution was to install the missing files:

dnf install kernel-devel-6.14.5-100.fc40.x86_64

Hope this helps anyone with this issue. I saw other similar posts, but the exact command was slightly different for Fedora.

I have a usb-wifi adapter that shows under lsusb as Bus 001 Device 025: ID 0bda:1a2b Realtek Semiconductor Corp. RTL8188GU 802.11n WLAN Adapter (Driver CDROM Mode) I built https://aur.archlinux.org/packages/rtl8188gu-dkms-git but it did not produce the module expected > modprobe rtl8188gu modprobe: FATAL: Module rtl8188gu not found in directory /lib/modules/6.9.7-arch1-1 so after a comment on that page I installed https://aur.archlinux.org/packages/rtl8xxxu-dkms-git :> lsmod | grep rtl rtl8xxxu 303104 0 btrtl 32768 1 btusb mac80211 1597440 2 iwlmvm,rtl8xxxu bluetooth 1101824 16 btrtl,btmtk,btintel,btbcm,btusb cfg80211 1363968 4 iwlmvm,iwlwifi,mac80211,rtl8xxxu But after reboot it does not associate with the network device.

I'm new to writing Linux modules (drivers) and digital signatures, so please correct me if any of my understanding is incorrect. When I run make modules_install on my module, I get the following error (veikk is the module name): At main.c:160: - SSL error:02001002:system library:fopen:No such file or directory: ../crypto/bio/bss_file.c:72 - SSL error:2006D080:BIO routines:BIO_new_file:no such file: ../crypto/bio/bss_file.c:79 sign-file: certs/signing_key.pem: No such file or directory I was looking up tutorials on signing modules, but I was very confused about how to distribute a signed module. There are tutorials for manually signing modules (e.g., this , this , this ), but these all seem to be post-installation and involve generating and registering a key with the kernel. It seems that the kernel wants to automatically sign the module on installation using certs/signing_key.pem (hence the error). Using the advice provided by this Unix Stack Exchange question , I was able to get rid of the error. This generates the x509.genkey file, and then creates the signing_key.pem and signing_key.x509 files in the certs directory in the kernel directory. printf "[ req ]\ndefault_bits = 4096\ndistinguished_name = req_distinguished_name\nprompt = no\nstring_mask = utf8only\nx509_extensions = myexts\n\n[ req_distinguished_name ]\nCN = Modules\n\n[ myexts ]\nbasicConstraints=critical,CA:FALSE\nkeyUsage=digitalSignature\nsubjectKeyIdentifier=hash\nauthorityKeyIdentifier=keyid" > x509.genkey openssl req -new -nodes -utf8 -sha512 -days 36500 -batch -x509 -config x509.genkey -outform DER -out $(BUILD_DIR)/certs/signing_key.x509 -keyout $(BUILD_DIR)/certs/signing_key.pem After running this and make modules_install, the module seems to install correctly. The output of modinfo veikk seems to show a valid signature: filename: /lib/modules/5.1.5-arch1-2-ARCH/extra/veikk.ko.xz license: GPL srcversion: A82263B16A25C763382D8B9 alias: hid:b0003g*v00002FEBp00000003 alias: hid:b0003g*v00002FEBp00000002 alias: hid:b0003g*v00002FEBp00000001 depends: hid retpoline: Y name: veikk vermagic: 5.1.5-arch1-2-ARCH SMP preempt mod_unload sig_id: PKCS#7 signer: Modules sig_key: 27:E8:FC:4A:4E:15:0C:AF:40:D5:A1:A4:10:E5:B5:55:BF:AF:EB:66 sig_hashalgo: sha512 signature: AC:AF:49:16:D4:AD:D9:7B:C5:52:A5:9F:F8:46:1C:DF:93:71:05:00: 4D:BF:96:96:3C:D1:11:19:6F:AC:D5:27:7D:E3:EE:8D:6C:BB:17:F4: 53:D3:FD:EE:85:22:97:57:BB:27:23:9C:8A:04:79:75:99:C4:A0:E6: 29:AF:20:15:87:EA:41:D2:26:00:2B:A1:39:68:28:FE:05:F5:F1:B1: 42:F8:FF:66:C0:6C:B5:17:A1:E7:F4:65:0A:17:64:99:9E:11:86:C0: 94:E7:D5:83:59:50:BE:0D:33:B8:A2:64:66:4F:70:A3:EB:E4:FB:B4: 52:D9:26:9C:57:CC:0D:D6:53:51:C2:90:D6:51:13:83:B6:22:EC:C9: DF:15:1D:1E:34:BD:7A:2D:8F:13:2D:78:8C:D3:EA:43:0B:6C:8D:DA: 9A:DA:A1:74:03:FC:D8:72:D0:96:54:52:60:AB:7A:BB:3C:D0:F4:8C: B7:92:21:B1:D8:02:01:6B:9B:AD:11:1A:90:5B:21:94:12:B7:5A:15: 10:6B:92:FA:74:F5:49:A2:4A:65:FF:4E:B6:9B:08:7B:BD:E5:85:9D: 98:52:A2:E4:D7:B4:0D:90:0D:62:7E:CE:6B:F8:8B:0C:33:76:1E:01: C7:0D:29:8C:97:BC:E1:35:58:2B:55:3F:6E:D9:36:46:50:76:74:67: 1F:B2:F6:C3:6B:24:4D:C1:7E:8D:14:4D:10:2D:1D:80:3C:82:02:1C: A6:87:14:8B:A0:3C:21:EA:DD:A7:CD:9C:D0:1B:DF:84:53:BF:0A:B6: DA:50:C4:AA:FF:90:44:47:4B:9F:8A:1C:C3:14:5D:A3:B5:A4:5F:6F: E1:E0:E2:51:B1:1E:5C:7E:95:70:72:76:3A:9D:53:10:F5:F0:3F:CD: E5:2B:EF:E4:3D:DB:64:65:9B:AE:E6:23:6E:4E:F1:4B:94:17:FF:FF: 06:A0:79:84:E1:BE:24:9D:93:B9:D4:94:41:76:92:D5:5B:8F:F6:4F: 98:B9:24:6F:01:CD:4F:49:52:15:48:79:4A:F3:46:CF:8A:AC:21:A9: 64:81:AC:01:15:80:06:F4:C3:9D:8A:C0:48:A6:53:C5:81:C2:DD:B1: C6:B9:80:B8:A9:C2:89:B8:20:C5:89:81:90:15:86:78:F7:09:3F:FD: F6:AC:54:57:8C:E0:B4:62:E0:78:CB:59:63:FA:E6:E2:8C:78:59:31: 92:E5:B5:E3:75:FE:F6:8F:82:3B:D6:5B:B1:84:E9:A8:9E:A4:B0:03: 99:8D:41:55:FF:11:A8:B6:A3:B9:EA:1D:5C:58:F7:D2:A6:F4:3A:C9: B1:E6:83:10:B7:E5:E4:15:28:2C:62:96 My question: **Is this a recommended (and safe) way to sign a driver?** Preferably, I would like to have end users not have to worry about the hassle of signing the drivers themselves when installing. Because my understanding is a little muddy, here are a few questions I don't understand: - Is this automatic signing on build as secure as the tutorials above for manually signing a driver after installation? I.e., I'm generating a key to sign it with, but that key never (at least explicitly) is loaded into the kernel. - How are drivers normally distributed and signed? I would expect large companies with proprietary drivers for Linux to have their modules signed some way, such as Nvidia. - Is there a way to pre-sign a module (on my end)? This seems unlikely because the module should be built for any system it's to be used on. I would like to keep Secure Boot on (disabling it allows the unsigned module to load, but clients would prefer to have Secure Boot on).

I'm new to Arch Linux. I installed it on my laptop(LG Gram) it seem fine post installation. I don't remember my wlan works post installation because I used wired. But, when I turned on my laptop today wlan interface load fails. I lastly installed wine 5.1 yesterday but I don't think is the reason. I searched other cases in google but I couldn't find any valid solutions. How can I fix my driver?

❯ lspci -kvnn | sed -n '/Network/,/^$/ p'
00:14.3 Network controller : Intel Corporation Cannon Point-LP CNVi [Wireless-AC] [8086:9df0] (rev 30)
        Subsystem: Intel Corporation Cannon Point-LP CNVi [Wireless-AC] [8086:0034]
        Flags: bus master, fast devsel, latency 0, IRQ 16
        Memory at a2618000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: 
        Kernel driver in use: iwlwifi
        Kernel modules: iwlwifi

❯ dmesg | grep iwlwifi
[    2.746905] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
[    2.756780] iwlwifi 0000:00:14.3: Found debug destination: EXTERNAL_DRAM
[    2.756783] iwlwifi 0000:00:14.3: Found debug configuration: 0
[    2.757082] iwlwifi 0000:00:14.3: loaded firmware version 46.ceaaecdc.0 op_mode iwlmvm
[    3.053411] iwlwifi 0000:00:14.3: Detected Intel(R) Dual Band Wireless AC 9560, REV=0x318
[    3.060880] iwlwifi 0000:00:14.3: Applying debug destination EXTERNAL_DRAM
[    3.061363] iwlwifi 0000:00:14.3: Allocated 0x00400000 bytes for firmware monitor.
[    8.178291] iwlwifi 0000:00:14.3: Failed to load firmware chunk!
[    8.178298] iwlwifi 0000:00:14.3: iwlwifi transaction failed, dumping registers
[    8.178301] iwlwifi 0000:00:14.3: iwlwifi device config registers:
[    8.178445] iwlwifi 0000:00:14.3: 00000000: 9df08086 00100406 02800030 00800000 a2618004 00000000 00000000 00000000
[    8.178450] iwlwifi 0000:00:14.3: 00000020: 00000000 00000000 00000000 00348086 00000000 000000c8 00000000 000001ff
[    8.178453] iwlwifi 0000:00:14.3: 00000040: 00928010 10000ec0 00100c10 00000000 00000000 00000000 00000000 00000000
[    8.178457] iwlwifi 0000:00:14.3: 00000060: 00000000 00080812 00000405 00000000 00000000 00000000 00000000 00000000
[    8.178461] iwlwifi 0000:00:14.3: 00000080: 800f0011 00002000 00003000 00000000 00000000 00000000 00000000 00000000
[    8.178465] iwlwifi 0000:00:14.3: 000000a0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[    8.178469] iwlwifi 0000:00:14.3: 000000c0: 00000000 00000000 c823d001 0d000008 00804005 00000000 00000000 00000000
[    8.178472] iwlwifi 0000:00:14.3: 000000e0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[    8.178476] iwlwifi 0000:00:14.3: 00000100: 14c00000 ff000000 000000ff 00462031 00000000 00002000 00000000 00000000
[    8.178479] iwlwifi 0000:00:14.3: 00000120: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[    8.178483] iwlwifi 0000:00:14.3: 00000140: 00000000 00000000 00000000 16410018 00000000 0001001e 00481e1f 00000000
[    8.178486] iwlwifi 0000:00:14.3: iwlwifi device memory mapped registers:
[    8.178510] iwlwifi 0000:00:14.3: 00000000: 18c89008 00000040 00000000 00000000 00000000 00000000 00000000 00000000
[    8.178514] iwlwifi 0000:00:14.3: 00000020: 00000010 0c000005 00000312 d55555d5 d55555d5 d55555d5 80008040 001f0042
[    8.178523] iwlwifi 0000:00:14.3: Could not load the  uCode section
[    8.178535] iwlwifi 0000:00:14.3: Failed to start INIT ucode: -110
[    8.178540] iwlwifi 0000:00:14.3: Collecting data: trigger 16 fired.
[    8.428342] iwlwifi 0000:00:14.3: Not valid error log pointer 0x00000000 for Init uCode
[    8.428350] iwlwifi 0000:00:14.3: Fseq Registers:
[    8.428352] iwlwifi 0000:00:14.3: 0x6EFC0A0E | FSEQ_ERROR_CODE
[    8.428354] iwlwifi 0000:00:14.3: 0x00000000 | FSEQ_TOP_INIT_VERSION
[    8.428356] iwlwifi 0000:00:14.3: 0x7DC9CAA6 | FSEQ_CNVIO_INIT_VERSION
[    8.428358] iwlwifi 0000:00:14.3: 0x0000A384 | FSEQ_OTP_VERSION
[    8.428360] iwlwifi 0000:00:14.3: 0xA51C1518 | FSEQ_TOP_CONTENT_VERSION
[    8.428362] iwlwifi 0000:00:14.3: 0xC08AE419 | FSEQ_ALIVE_TOKEN
[    8.428364] iwlwifi 0000:00:14.3: 0xF6FC466C | FSEQ_CNVI_ID
[    8.428365] iwlwifi 0000:00:14.3: 0xB1E04F68 | FSEQ_CNVR_ID
[    8.428367] iwlwifi 0000:00:14.3: 0x01000100 | CNVI_AUX_MISC_CHIP
[    8.428371] iwlwifi 0000:00:14.3: 0x01300202 | CNVR_AUX_MISC_CHIP
[    8.428376] iwlwifi 0000:00:14.3: 0x0000485B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[    8.428410] iwlwifi 0000:00:14.3: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[    8.428413] iwlwifi 0000:00:14.3: Firmware not running - cannot dump error
[    8.428582] iwlwifi 0000:00:14.3: Master Disable Timed Out, 100 usec
[    8.441398] iwlwifi 0000:00:14.3: Failed to run INIT ucode: -110

I found someone [similar issue](https://bbs.archlinux.org/viewtopic.php?id=243691) with me but his solution is not working for me. I added

="loglevel=3 quiet intel_iommu=off"

and grub-mkconfig again but it didn't work. My Network Interface is not even loaded so I can't do something like

wlan0 power off

❯ ifconfig -a
enp0s20f0u3: flags=4163  mtu 1500
        inet 192.168.0.28  netmask 255.255.255.0  broadcast 192.168.0.255
        inet6 fe80::5f9b:8d19:a256:b280  prefixlen 64  scopeid 0x20
        ether 00:e0:4c:f1:54:e9  txqueuelen 1000  (Ethernet)
        RX packets 10320  bytes 6390510 (6.0 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 9090  bytes 1341283 (1.2 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 16  bytes 960 (960.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 16  bytes 960 (960.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

I searched some info in google and tried but there was no valid solution.

# /etc/modprobe.d/iwlwifi.conf
options iwlwifi 11n_disable=1

I'm trying to send information via pyusb from host a to host b, the issue is that I can't get my USB crossover cable to show up on either end via lsusb, or even doubly connected to the same host. I don't know how to address/identify the port I've connected to to even send information over. I know its possible to do this, but not how to actually set it up. I would like to make one of the hosts a device, or a slave to the other, as if it was a real USB device, I only care about two way communication in so far as it is needed to set up the device -> host communication I imagine I'm going to have to create my own device description, but that doesn't explain any part of the process to actually get a linux based system to identify it. I guess what I'm looking for is a way to address the hosts on either end or the connection itself, something for me to identify and then use with pyusb so I can actually send information over, and then let me use one as an actual usb device. EDIT: Looking around more it seems like I need to use g_serial some how on the host I intend to make act like a device. That should include the proper drivers and I should be able to hook up both sides that way, however this still seems to require a usb device port, and obviously I'm not using an embedded system on either end, so I don't have access to a device port or both. I'm open for some sort of host hardware converter to device, but I need to make sure bandwidth is not sacrificed. Bandwidth is also the reason I'm not using Ethernet. I'm willing to forgo all that though if I'm able to send information straight over the port some how. Clearly this is also possible because there exists special software with other cables that allow file transfer (and windows recognizes my cable when connected to linux). I need the ability to do this as well. EDIT: dmesg output is too large, but here is something interesting: usb usb4-port1: Cannot enable. Maybe the USB cable is bad? this gets displayed for thousands of lines. also get this from windows side (not actually what I'm trying to do)

I'm using a Lenovo Yoga 7 14ARP8. Currently on NixOS, but this issue seems to happen on other distros including Fedora. ## The issue This laptop has a 360 degree hinge that allows it to become a tablet of sorts. When flipped above 180 degrees on Windows the keyboard and touchpad are disabled (And the backlight turns off). While completly flipping the keyboard around 360 degrees has a similar effect (without turning off backlight) and triggers the "Tablet mode" on KDE Plasma, the keyboard and touchpad continue to be enabled anywhere between 180 and 360 degrees, meaning if I set the keyboard to be facing the ground as a stand, random keys may be pressed. ## Debugging the events The first thing I tried was running a sudo libinput debug-events and flipping the keyboard while it's running. The result is this: As I flip it to 360:\ `-event12 SWITCH_TOGGLE +4294967.295s switch tablet-mode state 1` As I flip it away from 360:\ ` event12 SWITCH_TOGGLE +2.300s switch tablet-mode state 0` Going beyond 180 does not affect the "tablet-mode" state. ## The responsible modules It seems this switch is controlled by the lenovo_ymc module, but there's also a ymc_ec_trigger option in the ideapad_laptop module, however enabling that didn't fix the issue. ideapad_laptop seems to have fixes for the previous gen of this laptop (Yoga 7 14ARP7) but not this one. Within the lenovo_ymc module there is this code:

c
static const struct key_entry lenovo_ymc_keymap[] = {
	/* Laptop */
	{ KE_SW, 0x01, { .sw = { SW_TABLET_MODE, 0 } } },
	/* Tablet */
	{ KE_SW, 0x02, { .sw = { SW_TABLET_MODE, 1 } } },
	/* Drawing Board */
	{ KE_SW, 0x03, { .sw = { SW_TABLET_MODE, 1 } } },
	/* Tent */
	{ KE_SW, 0x04, { .sw = { SW_TABLET_MODE, 1 } } },
	{ KE_END },
};

I'm not sure how it determines when the laptop is in "Tablet" mode, but should be sending the event even in "Tent" mode or "Drawing Board" mode. It seems though those aren't getting triggered or are skipped. I am thinking of reporting this as a bug to the linux kernel, but I wanted to post it here in case anyone can help.

So i bought an usb-c dock (jeswo), i plugged my usb mouse into that and it worked fine. I unplugged the dock, plugged into my steamdeck, played (worked fine) and then plugged back, my laptop did not recognize the mouse. (I tried every port on the dock and every port on my laptop). The led is working, but no input whatsoever.

uname -r
6.6.90-1-MANJARO

lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 04f2:b604 Chicony Electronics Co., Ltd Integrated Camera (1280x720@30)
Bus 001 Device 004: ID 06cb:009a Synaptics, Inc. Metallica MIS Touch Fingerprint Reader
Bus 001 Device 016: ID 05e3:0618 Genesys Logic, Inc. Hub
Bus 001 Device 017: ID 05e3:0752 Genesys Logic, Inc. micros Reader
Bus 001 Device 018: ID 09da:9066 A4Tech Co., Ltd. F3 V-Track Gaming Mouse
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

xinput
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ Synaptics TM3276-022                    	id=9	[slave  pointer  (2)]
⎜   ↳ TPPS/2 IBM TrackPoint                   	id=10	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
↳ Power Button                            	id=6	[slave  keyboard (3)]
↳ Video Bus                               	id=7	[slave  keyboard (3)]
↳ Sleep Button                            	id=8	[slave  keyboard (3)]
↳ AT Translated Set 2 keyboard            	id=11	[slave  keyboard (3)]
↳ ThinkPad Extra Buttons

Right after plugging in

sudo dmesg | tail -n 30
[ 8828.438612] usb 1-4.2: USB disconnect, device number 15
[ 8829.342636] usb 1-4: new high-speed USB device number 16 using xhci_hcd
[ 8829.484666] usb 1-4: New USB device found, idVendor=05e3, idProduct=0618, bcdDevice=87.54
[ 8829.484679] usb 1-4: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 8829.484685] usb 1-4: Product: USB2.0 Hub
[ 8829.487760] hub 1-4:1.0: USB hub found
[ 8829.488026] hub 1-4:1.0: 4 ports detected
[ 8829.772224] usb 1-4.1: new high-speed USB device number 17 using xhci_hcd
[ 8829.865128] usb 1-4.1: New USB device found, idVendor=05e3, idProduct=0752, bcdDevice= 2.33
[ 8829.865137] usb 1-4.1: New USB device strings: Mfr=3, Product=4, SerialNumber=0
[ 8829.865141] usb 1-4.1: Product: USB Storage
[ 8829.865144] usb 1-4.1: Manufacturer: Generic
[ 8829.866637] usb-storage 1-4.1:1.0: USB Mass Storage device detected
[ 8829.866824] scsi host0: usb-storage 1-4.1:1.0
[ 8829.941321] usb 1-4.2: new full-speed USB device number 18 using xhci_hcd
[ 8830.037359] usb 1-4.2: New USB device found, idVendor=09da, idProduct=9066, bcdDevice= 1.02
[ 8830.037367] usb 1-4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 8830.037371] usb 1-4.2: Product: USB Device
[ 8830.037373] usb 1-4.2: Manufacturer: A4TECH
[ 8830.885752] scsi 0:0:0:0: Direct-Access     Generic  STORAGE DEVICE   0233 PQ: 0 ANSI: 0
[ 8830.886041] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 8830.886491] sd 0:0:0:0: [sda] Media removed, stopped polling
[ 8830.886886] sd 0:0:0:0: [sda] Attached SCSI removable disk
[10393.357050] perf: interrupt took too long (2501 > 2500), lowering kernel.perf_event_max_sample_rate to 79800
[10836.412493] usb 1-4.2: USB disconnect, device number 18
[10838.408776] usb 1-4.2: new full-speed USB device number 19 using xhci_hcd
[10838.503789] usb 1-4.2: New USB device found, idVendor=09da, idProduct=9066, bcdDevice= 1.02
[10838.503798] usb 1-4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[10838.503801] usb 1-4.2: Product: USB Device
[10838.503804] usb 1-4.2: Manufacturer: A4TECH

lsmod | grep hid
usbhid                 86016  0
mac_hid                12288  0

usb-devices | grep -A 20 '09da'
P:  Vendor=09da ProdID=9066 Rev=01.02
S:  Manufacturer=A4TECH
S:  Product=USB Device
C:  #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=01 Driver=(none)
E:  Ad=81(I) Atr=03(Int.) MxPS=  12 Ivl=1ms
I:  If#= 1 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=02 Driver=(none)
E:  Ad=82(I) Atr=03(Int.) MxPS=   8 Ivl=1ms

T:  Bus=01 Lev=01 Prnt=19 Port=07 Cnt=01 Dev#=  3 Spd=480  MxCh= 0
D:  Ver= 2.01 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=04f2 ProdID=b604 Rev=00.27
S:  Manufacturer=Chicony Electronics Co.,Ltd.
S:  Product=Integrated Camera
S:  SerialNumber=0001
C:  #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=500mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=0e(video) Sub=01 Prot=00 Driver=uvcvideo
E:  Ad=83(I) Atr=03(Int.) MxPS=  16 Ivl=4ms
I:  If#= 1 Alt= 0 #EPs= 0 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo

T: Bus=01 Lev=01 Prnt=03 Port=08 Cnt=01 Dev#= 4 Spd=12 MxCh= 0 The mouse works just fine with the steamdeck and with other devices too. I tried to use ChatGPT to solve the problem, but got into a loop and did not find any solution. What info do you need?