Change:
Newer kernels (4.15+) can look for wireless regulatory info from (for us this is I think?), replacing the need for user-space helper like . (at least in the common case, I believe) <-- latest CRDA git adds note about this Not the same as the regdb, although I'm not sure the difference is as important for NiXOS'ers compared to other distributions. Info on internal:
I don't want to hijack the thread but my problem may be related. Recently, not sure why, I can't connect to an AP I previously could connect to so I suspect it's my machne (my phone can still access it), thus I've been looking at wifi information. I used to have a plain error then I while now it at least attempt to connect: so I wonder if it's expected on nixos ? NB: it's annoying all these errors when building kernels. do others have it too (I should probably look at hydras rather...
To get the file loaded, you need to add to . ` to see the files. Then you should see the following in : I haven't quite figured out what the best way to set the correct regulatory domain is however... short of just using .
oh great thanks ! that was not obvious. I was looking for a setting to set on boot as a kernel parameter but haven't found it yet. Some interesting read suggests one can embed the kernel in the db as well ?!
Something like this should work: Admittedly not ideal since it only works at module load time though.
Thanks Setting the following gives me the correct wifi config (check with ): Looking through the documents on: It seems to be a bit of a mess.... is an 'old' option, but NetworkManager has no support for setting the reg domain. I think having a module (?) might be a very good idea, and such an option should be to. ArchLinux deals with it by using a custom rule to run when is loaded ([source][al]). [al]: Another idea would be to a option, though that doesn't fix NetworkManager.
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . on the on .
This should not be stale I think. Should NixOS just add to as default?
cc
This issue has been mentioned on NixOS Discourse. There might be relevant details there:

Discussion:
''; }; <ins> hardware.wirelessRegulatoryDatabase = mkOption { default = false; type = types.bool; description = '' Load the wireless regulatory database at boot. ''; }; </ins> };

++ optionals (versionOlder config.boot.kernelPackages.kernel.version "4.13") [ rtl8723bs-firmware ]; <ins> hardware.wirelessRegulatoryDatabase = true; </ins> }) (mkIf cfg.enableAllFirmware { assertions = [{

b43FirmwareCutter ] ++ optional (pkgs.stdenv.hostPlatform.isi686 || pkgs.stdenv.hostPlatform.isx86_64) facetimehd-firmware; }) <ins> (mkIf cfg.wirelessRegulatoryDatabase { hardware.firmware = [ pkgs.wireless-regdb ]; }) </ins> ]; }

cfg = config.networking.networkmanager; basePackages = with pkgs; [ <del> crda </del> modemmanager networkmanager networkmanager-fortisslvpn

} ]; <ins> hardware.wirelessRegulatoryDatabase = true; </ins> environment.etc = with pkgs; { "NetworkManager/NetworkManager.conf".source = configFile;

environment.systemPackages = [ package ]; services.dbus.packages = [ package ]; <del> services.udev.packages = [ pkgs.crda ]; </del> <ins> hardware.wirelessRegulatoryDatabase = true; </ins> # FIXME: start a separate wpa_supplicant instance per interface. systemd.services.wpa_supplicant = let