Arch Linux User Repository

The pkgver and _srcver variables changed in the main linux package:

pkgver=5.3.8.1
_srcver=${pkgver%.*}-arch${pkgver##*.}

@sir_lucjan - Good catch, thanks. Fixed in 5.3.8-4.

@graysky

As far as I can see, you forgot to change one line.

-  echo "$_kernelname" > localversion.20-pkgname
+  echo "${pkgbase#linux}" > localversion.20-pkgname

@graysky,

It was interesting to see how much 'heat' my wireguard-dkms post generated, and perhaps several of us wireguard-dkms and -ck users have learned some important tips.

Bottom line = tldr version - no action is required provided that: the fou, ip_tunnel and wire modules are found within lsmod and/or modprobed-db list if you run modprobed-db.

Those 3 modules were NOT loaded within MY modprobed-db list, which was quite surprising, given that I have run wireguard-dkms and modprobed-db for a VERY LONG time!

However, once I re-ran: modprobed-db store, it found the three new modules.

Of course, during a subsequent, clean, rebuild of linux-ck, wireguard-dkms was successfully installed.

Thanks for your input graysky, and to the others who offered their comments.

@kwe: OK. I'll try to explain.

1. localmodconfig disables every module, that not exactly listed in provided file

2. the file modprobed.db filling automatically only by modules that are in memory when modprobed-db service runs.

3. fou module did not get into the modprobed.db for some reason

4. But it is needed as indirect dependency for wireguard-dkms

5. when you build kernel with localmodconfig - fou module become disabled

6. And consequent build of wireguard-dkms fails.

As I can see - the most simple way to fix such a problem - is to add fou/fou6 modules into modprobed.db manually.

Or - load them and run modprobed-db.service for the same thing.

Blame me, if I wrong, cause there is more coffee than blood in veins)

@laenco: Either I'm misunderstanding you or I have to disagree.
When digging though lsmod AFTER HAVING USED WIREGUARD (so I assume all the required modules have been loaded), I can't seem to find any specific modules that are NOT in modprobed.db. It seems to me like the part where .config is configured for the kernel compilation process is assembled in a wrong way, missing out on the loaded (!) modules. This doesn't seem to have anything to do with modprobed-db as far as I can tell (?).

@kwe: so it's look like wireguard needs fou module for dkms build/install, but does not load it during routine operations, so modprobed-db did not detect it.

You could try to add fou and fou6 modules to modprobed.db manually and rebuild.

@laenco: Here is my current system state:

$ grep -i fou ~/.config/modprobed.db
$ lsmod | grep -i fou
$ lsmod | grep -i wire
wireguard             233472  0
ip6_udp_tunnel         16384  1 wireguard
udp_tunnel             16384  1 wireguard
$ grep -i tun ~/.config/modprobed.db
ip6_udp_tunnel
tun
udp_tunnel

When I run makepkg to extract the linux-ck src directory, I end up with this .config diff against the current running kernel config:

$ zdiff /proc/config.gz config.last 
1069d1068
< CONFIG_NET_IP_TUNNEL=m
1077,1078c1076
< CONFIG_NET_UDP_TUNNEL=m
< CONFIG_NET_FOU=m
---
> # CONFIG_NET_FOU is not set
1116d1113
< CONFIG_IPV6_FOU=m

@kwe could you check ~/.config/modprobed.db for presence of "fou"/"fou6" modules?

The question is "If localmodconfig is unable to detect fou or is it a modprobed-db detection problem"?.

@graysky I am building linux-ck with modprobed-db, and for some reason, I always end up with those configuration options being disabled. I have to re-enable them manually every single time.