[Nix-dev] how to install load kernel module wl?
Hello NixOS-ers, I try to install and load the wl.ko kernel module on my fresh install of Nixos, but I seem to be doing something wrong. Please let me show you first what I tried: I installed the broadcom-sta package: $ nix-env -i broadcom-sta installing `broadcom-sta-_5_100_82_112-3.6' The module is now indeed the store: $ find / -name wl.ko /nix/store/.../3.6.0/kernel/net/wireless/wl.ko Though all other modules seem to be in 3.2.30/kernel/... which seems to corresponds with the kernel I am currently running: $ uname -r 3.2.30 When I try to load the module, this fails: $ modprobe wl.ko FATAL: Module wl.ko not found I also added wl to boot.kernelModules, and when I run: $ nixos-rebuild test no errors are reported. But iwconfig does not show my wireless card. My conclusion is that I either need to upgrade my kernel or need to install an older version of the broadcom-sta package, am I right? How should I do this? My second question is, why do I not see an error when I test my configuration? Thanks, Maarten Faddegon ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] how to install load kernel module wl?
man configuration.nix There is a system option 'extraKernelPackages' or such (boot section). Why doesn't nix-env -i work? Because modprobe is a wrapper which is passed a module directory which is assembled by nixos. And that module directory is always represented by /var/run/booted-system only (AFAIK) for good reasons. The booted kernel should always match the modules available. So maybe you even have to restart (or manually change such a symlink). cat `which modprobe` should make you understand if you follow the MDULE_DIR path to the store. Marc Weber ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] how to install load kernel module wl?
Hi. On 10/10/2012 04:10 PM, Marc Weber wrote: man configuration.nix There is a system option 'extraKernelPackages' or such (boot section). Why doesn't nix-env -i work? Because modprobe is a wrapper which is passed a module directory which is assembled by nixos. And that module directory is always represented by /var/run/booted-system only (AFAIK) for good reasons. The booted kernel should always match the modules available. So maybe you even have to restart (or manually change such a symlink). cat `which modprobe` should make you understand if you follow the MDULE_DIR path to the store. Yes, extraKernelPackages + kernelModules is the preferred way. Modprobing may also work if you specify somehow the absolute path. Vlada smime.p7s Description: S/MIME Cryptographic Signature ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
