Hi, Dave, Regarding iwlwifi and for future reference, this driver is part of the kernel, not something external, which means that the version of the driver is tied to the version of the kernel to some extent. I have a system, for example, running 4.19.x and using iwlwifi without issue: $ lsmod | grep iwl iwlmvm 290816 0 led_class 16384 2 input_leds,iwlmvm mac80211 446464 1 iwlmvm iwlwifi 225280 1 iwlmvm cfg80211 339968 3 iwlmvm,iwlwifi,mac80211 $ ip l show dev wlan0 | head -1 4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000 $ uname -r 4.19.132 $ dmesg | grep firmw | grep iwl [ 1.582232] iwlwifi 0000:07:00.0: loaded firmware version 38.755cfdd8.0 op_mode iwlmvm It's possible that your hardware is so new that the 4.19.x kernel doesn't support it, I suppose. Just providing some reference. Regarding grub, your grub config file has no menuentry for a linux kernel, which is probably because it's not named in a way that grub-mkcofnig expects. grub-mkconfig looks for these patterns: '/boot/vmlinuz-*', '/vmlinuz-*', '/boot/kernel-*'. If you named the file simply 'vmlinuz' or 'kernel' it wouldn't work, but 'vmlinuz-5.4.49' would. If you write your own config you can call it whatever you like, but this is what grub-mkconfig expects. You can find these patterns in /etc/grub.d/10_linux if you want to verify. The 'grub-install' command only installs the bootloader into your MBR or UEFI but doesn't create a config file, hence the need for 'grub-mkconfig'. If you get a grub menu like you said, that means grub is installed and booting, just doesn't have a correct (or fully populated) config file. Regards, Matt