From 8d1be5af57e693b8a80c74ff9b8aef4322cddd7a Mon Sep 17 00:00:00 2001 From: Hyperling Date: Wed, 19 Nov 2025 19:28:52 -0700 Subject: [PATCH] Release the Apple WiFi help guide. --- .../tech/apple-debian-wireless-issues.md | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/content/posts/tech/apple-debian-wireless-issues.md b/content/posts/tech/apple-debian-wireless-issues.md index 249b926..df37c2a 100644 --- a/content/posts/tech/apple-debian-wireless-issues.md +++ b/content/posts/tech/apple-debian-wireless-issues.md @@ -1,6 +1,5 @@ --- -draft: true -title: "Apple Wireless Card Issues on Debian Trixie" +title: "Apple Wireless Card Issues on Debian 13" subtitle: "" author: Hyperling date: "2025-11-19T13:00:00-07:00" @@ -23,6 +22,8 @@ tags: - modprobe - lsmod - lspci + - debian + - trixie series: - sysadmin categories: @@ -45,23 +46,22 @@ broadcom-sta-source/stable 6.30.223.271-26 amd64 I do not have experience with other Mac devices, the Debian wiki and forums are your best bet if this article does not apply to you. -{{< external-link "Debian Wiki: Macbook Wireless" "https://wiki.debian.org/MacBook/Wireless" >}} +- {{< external-link "Debian Wiki: Macbook Wireless" "https://wiki.debian.org/MacBook/Wireless" >}} ## Introduction -- Define the Problem -If your wireless card is no longer being recognized on a Debian device, ensure the latest version of the Linux kernal came with its headers. +If your wireless card is no longer being recognized on a Debian device, ensure the latest version of the Linux kernel came with its headers. -I'm not sure why this happened, but it was when the kernel version jumped from `6.12.41` to `6.12.43` that its symptoms showed up. I had already migrated from Bookworm to Trixie and thought I had went through a few kernel updates since then without issues. +I'm not sure why this happened, but it was when the kernel version jumped from `6.12.41` to `6.12.43` that its symptoms showed up. I had already migrated from Bookworm to Trixie and thought I had went through a few kernel updates since then without issues, but wasn't sure. -Later versions such as `6.12.48` and `6.12.57` continued to get pulled and I'd try them before having to reboot back to `6.12.41`. While booten into the newer kernel versions `/sbin/iwconfig` would show no wireless network and GNOME didn't have a Wi-Fi button listed in the Settings app nor its system menu. Then I tried this: +Later versions such as `6.12.48` and `6.12.57` continued to get pulled and I'd try them before having to reboot back to `6.12.41`. While booted into the newer kernel versions `/sbin/iwconfig` would show no wireless network and GNOME didn't have a Wi-Fi button listed in the Settings app nor its system menu. Then I tried this: ``` $ sudo modprobe wl modprobe: FATAL: Module wl not found in directory /lib/modules/6.12.57+deb13-amd64 -$ ``` -After realizing that the wl module wasn't being loaded I thought maybe there was a packaging issue. I was confused since it said it was not found, even though I knew it was installed since it was still working if I booted to the older installed kernel versions. I saw no error when the new versions were being installed, either. And thus began my discovery... +After realizing that the `wl` module wasn't being loaded I thought maybe there was a packaging issue. I was confused since it said it was not found, even though I knew it was installed since it was still working if I booted to the older installed kernel versions. I saw no error when the new versions were being installed, either. And thus began my discovery... ## Solution -- Install Headers Automagically @@ -71,9 +71,9 @@ Ubuntu provides the packages `linux-image-generic` and `linux headers-generic`. sudo apt install linux-image-amd64 linux-headers-amd64 --reinstall ``` -Some sources say that Debian has no generic/meta package for the kernel and its headers. I can't find any information as to the release date of these to confirm/deny that claim. +Some sources say that Debian has no generic/meta package for the kernel and its headers. I can't find any information as to the release date of these to confirm or deny that claim. -I'm just glad they work to now keep the headers installed automatically! +I'm just glad they work to now keep the headers installed automatically! I've since added the packages to my provisioning setup. ## Still Not Working?