According to the file list https://packages.ubuntu.com/impish-updates/arm64/linux- modules-5.13.0-1017-raspi/filelist
module ipv4/netfilter/ip_tables.ko et. al. are also provided by package linux-modules-5.13.0-1017-raspi and linux-modules-5.13.0-1016-raspi and probably all the previous versions back to 5.13.0-1008-raspi I did re-install linux-modules-5.13.0-1008-raspi as suggested and the missing modules were replaced See below sudo apt install --reinstall linux-modules-5.13.0-1008-raspi Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: linux-image-5.13.0-1008-raspi Suggested packages: fdutils linux-raspi-doc-5.13.0 | linux-raspi-source-5.13.0 linux-raspi-tools linux-headers-5.13.0-1008-raspi linux-modules-extra-5.13.0-1008-raspi The following NEW packages will be installed: linux-image-5.13.0-1008-raspi linux-modules-5.13.0-1008-raspi 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 35.8 MB of archives. After this operation, 152 MB of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://ports.ubuntu.com/ubuntu-ports impish/main arm64 linux-modules-5.13.0-1008-raspi arm64 5.13.0-1008.9 [26.3 MB] Get:2 http://ports.ubuntu.com/ubuntu-ports impish/main arm64 linux-image-5.13.0-1008-raspi arm64 5.13.0-1008.9 [9479 kB] Fetched 35.8 MB in 5s (7393 kB/s) Selecting previously unselected package linux-modules-5.13.0-1008-raspi. (Reading database ... 118169 files and directories currently installed.) Preparing to unpack .../linux-modules-5.13.0-1008-raspi_5.13.0-1008.9_arm64.deb ... Unpacking linux-modules-5.13.0-1008-raspi (5.13.0-1008.9) ... Selecting previously unselected package linux-image-5.13.0-1008-raspi. Preparing to unpack .../linux-image-5.13.0-1008-raspi_5.13.0-1008.9_arm64.deb .. . Unpacking linux-image-5.13.0-1008-raspi (5.13.0-1008.9) ... Setting up linux-image-5.13.0-1008-raspi (5.13.0-1008.9) ... I: /boot/vmlinuz.old is now a symlink to vmlinuz-5.13.0-1017-raspi I: /boot/initrd.img.old is now a symlink to initrd.img-5.13.0-1017-raspi I: /boot/vmlinuz is now a symlink to vmlinuz-5.13.0-1008-raspi I: /boot/initrd.img is now a symlink to initrd.img-5.13.0-1008-raspi Setting up linux-modules-5.13.0-1008-raspi (5.13.0-1008.9) ... Processing triggers for linux-image-5.13.0-1008-raspi (5.13.0-1008.9) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.13.0-1008-raspi Using DTB: bcm2711-rpi-4-b.dtb Installing /lib/firmware/5.13.0-1008-raspi/device-tree/broadcom/bcm2711-rpi-4-b. dtb into /boot/dtbs/5.13.0-1008-raspi/./bcm2711-rpi-4-b.dtb Installing new bcm2711-rpi-4-b.dtb. Ignoring old or unknown version 5.13.0-1008-raspi (latest is 5.13.0-1017-raspi) /etc/kernel/postinst.d/zz-flash-kernel: Using DTB: bcm2711-rpi-4-b.dtb Installing /lib/firmware/5.13.0-1008-raspi/device-tree/broadcom/bcm2711-rpi-4-b. dtb into /boot/dtbs/5.13.0-1008-raspi/./bcm2711-rpi-4-b.dtb Taking backup of bcm2711-rpi-4-b.dtb. Installing new bcm2711-rpi-4-b.dtb. Ignoring old or unknown version 5.13.0-1008-raspi (latest is 5.13.0-1017-raspi) Scanning processes... Scanning processor microcode... Scanning linux images... Running kernel seems to be up-to-date. Failed to check for processor microcode upgrades. No services need to be restarted. No containers need to be restarted. No user sessions are running outdated binaries. ubuntu@aitu20pi42:~$ ls /lib/modules 5.13.0-1008-raspi 5.13.0-1017-raspi ubuntu@aitu20pi42:~$ ls /lib/modules/5.13.0-1008-raspi/ initrd modules.builtin.alias.bin modules.devname kernel modules.builtin.bin modules.order modules.alias modules.builtin.modinfo modules.softdep modules.alias.bin modules.dep modules.symbols modules.builtin modules.dep.bin modules.symbols.bin ubuntu@aitu20pi42:~$ ls /lib/modules/5.13.0-1008-raspi/kernel/net/ipv4 ah4.ko ipcomp.ko tcp_highspeed.ko tcp_westwood.ko esp4.ko ipip.ko tcp_htcp.ko tcp_yeah.ko esp4_offload.ko netfilter tcp_hybla.ko tunnel4.ko fou.ko raw_diag.ko tcp_illinois.ko udp_diag.ko gre.ko tcp_bbr.ko tcp_lp.ko udp_tunnel.ko inet_diag.ko tcp_bic.ko tcp_nv.ko xfrm4_tunnel.ko ip_gre.ko tcp_cdg.ko tcp_scalable.ko ip_tunnel.ko tcp_dctcp.ko tcp_vegas.ko ip_vti.ko tcp_diag.ko tcp_veno.ko ubuntu@aitu20pi42:~$ ls /lib/modules/5.13.0-1008-raspi/kernel/net/ipv4/netfilter/ Accord arp_tables.ko ipt_SYNPROXY.ko iptable_security.ko nf_socket_ipv4.ko arpt_mangle.ko ipt_ah.ko nf_defrag_ipv4.ko nf_tproxy_ipv4.ko arptable_filter.ko ipt_rpfilter.ko nf_dup_ipv4.ko nft_dup_ipv4.ko ip_tables.ko iptable_filter.ko nf_nat_h323.ko nft_fib_ipv4.ko ipt_CLUSTERIP.ko iptable_mangle.ko nf_nat_pptp.ko nft_reject_ipv4.ko ipt_ECN.ko iptable_nat.ko nf_nat_snmp_basic.ko ipt_REJECT.ko iptable_raw.ko nf_reject_ipv4.ko ubuntu@aitu20pi42:~$ ======================= reboot ============================================= ubuntu@aitu20pi42:~$ uname -r 5.13.0-1017-raspi ubuntu@aitu20pi42:~$ modinfo ip_tables modinfo: ERROR: Module ip_tables not found. ubuntu@aitu20pi42:~$ modprobe ip_tables modprobe: FATAL: Module ip_tables not found in directory /lib/modules/5.13.0-1017-raspi ubuntu@aitu20pi42:~$ ls /lib/modules/5.13.0-1008-raspi/ ls: cannot access '/lib/modules/5.13.0-1008-raspi/': No such file or directory But as you can see in the installation process there is the line "Ignoring old or unknown version 5.13.0-1008-raspi (latest is 5.13.0-1017-raspi)" and following a reboot the directory has gone and all those modules along with it. I think this is just as was alluded to in Bug #1942691 - "after update modules are gone..." Further even if the files had remained on disk I don't think it would have helped because reading the error message from modprobe it states modprobe: FATAL: Module ip_tables not found in directory /lib/modules/5.13.0-1017-raspi it is specifically looking in the '1017 directory for modules - and to my mind this makes sense - why would it look in old versions of the kernel modules and why would you keep old versions of kenrel modules hanging around? To be clear I don't normally do anything more that apt update / apt full-upgrade (i didn't in this instance) I have been known to occasionally do apt autoremove but I know versions '1011, '1016 were on this machine and and '1017 (the current one) still is. I don't/haven't specifically done anything to remove these directories myself - something in the update/upgrade process does this. It seems to me that either the package authors are expecting these update packages to be applied as some sort of patch process and that patch process isn't working or there is no patch process - all files are replaced on subsequent updates and the actual package is broken and despite the file list saying these modules are present, they're not or they are present in the package but they're not being written to disk. To reiterate I don't believe I've done anything to cause this to break I think there is something either in the update/upgrade process which breaks this or perhaps something in the circumstance of the update - I can't remember what version I started with I think 20.04 and upgraded to 21.10 I'm not sure - I do remember trying to install several times before being successful. But going back to Bug #1942691 I think the reporter says they found their issue in all three versions. Please let me know what you want me try next. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962053 Title: Modules missing from package install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1962053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
