# Kali 7.1.y for the uConsole and DevTerm **URL:** \ **Category:** uConsole\ **Tags:** devterm, uconsole, cm4, cm5\ **Created:** [September 13, 2024, 3:49am UTC](https://forum.clockworkpi.com/t/kali-7-1-y-for-the-uconsole-and-devterm/14463 "2024-09-13T03:49:52Z")\ **Posts on this page:** 15\ **Page:** 9
**Author:** ![arthuring](https://avatars.discourse-cdn.com/v4/letter/a/6de8d8/32.png) [@arthuring](https://forum.clockworkpi.com/u/arthuring)\ **Post date:** [April 17, 2026, 11:55pm UTC](https://forum.clockworkpi.com/t/kali-7-1-y-for-the-uconsole-and-devterm/14463/167 "2026-04-17T23:55:05Z")
It seems on the blog that frame injection is indeed a bit unstable. Maybe running airmon-ng check kill will help? Also there’s a tip and trouble shoot section there but you might have already tried them. PS: I ordered a CM5 board too but it is taking way too long to arrive. ---
**Author:** ![arthuring](https://avatars.discourse-cdn.com/v4/letter/a/6de8d8/32.png) [@arthuring](https://forum.clockworkpi.com/u/arthuring)\ **Post date:** [April 23, 2026, 5:42am UTC](https://forum.clockworkpi.com/t/kali-7-1-y-for-the-uconsole-and-devterm/14463/168 "2026-04-23T05:42:23Z")
Hey Dave, I got the cm5 today, and after some tinkering frame injection is working! Although I haven’t have success with angryoxide yet due to unknown reason, I was able to creating fake access point and with mdk4. The only downside is that I have to keep reloading the kernel module to properly enable monitor mode. I wrote some aliases to make reloading the kernel module and enabling, disabling monitor much quicker. I would say this is quite acceptable level of success! PS: I am on 6.12.67. ---
**Author:** ![firebelcher](https://avatars.discourse-cdn.com/v4/letter/f/cdc98d/32.png) [@firebelcher](https://forum.clockworkpi.com/u/firebelcher)\ **Post date:** [May 14, 2026, 2:58am UTC](https://forum.clockworkpi.com/t/kali-7-1-y-for-the-uconsole-and-devterm/14463/169 "2026-05-14T02:58:45Z")
I just created an account here to say “Thank you!” this was the exact fix I was looking for! Weird that the update sent all the files to /boot/firmware instead /boot.. I had to: 1. Remove the drive from uConsole 2. Plug the drive into another machine 3. Mount it 4. Copy the files from /boot/firmware to /boot 5. Copy the files from /boot/firmware/overlays/ to /boot/overlays/ 6. Umount the drive 7. Put it back into the uConsole. After that it booted right up! Now I just need to figure out how to get meshtasticd installed into kali-linux… 🥴 ---
**Author:** ![yankl](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/yankl/32/16795_2.png) [@yankl](https://forum.clockworkpi.com/u/yankl)\ **Post date:** [June 17, 2026, 11:27am UTC](https://forum.clockworkpi.com/t/kali-7-1-y-for-the-uconsole-and-devterm/14463/170 "2026-06-17T11:27:14Z")
Hi, bro, you’re doing great things! Maybe you can help me figure out my problem? I installed Kali on a uconsole + hackergadgets upgrade kit vs. AIO V2, CM5 on an SSD. Everything was fine, but when I’m working in the terminal, the computer freezes for a few minutes, then runs a couple of commands and freezes again. ---
**Author:** ![Rex](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/rex/32/16852_2.png) [@Rex](https://forum.clockworkpi.com/u/Rex)\ **Post date:** [June 17, 2026, 11:43am UTC](https://forum.clockworkpi.com/t/kali-7-1-y-for-the-uconsole-and-devterm/14463/171 "2026-06-17T11:43:12Z")
Not sure I don’t use Kali I just made the image compatible. Kali isn’t really made to be a daily driver, it’s supposed to be a distro you boot use the tools you need and then go back to your normal OS. Kali has tons of stuff installed and is really bloated. I would say you’re better off installing the tools you need on something like Debian Trixie. ---
**Author:** ![yankl](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/yankl/32/16795_2.png) [@yankl](https://forum.clockworkpi.com/u/yankl)\ **Post date:** [June 17, 2026, 12:04pm UTC](https://forum.clockworkpi.com/t/kali-7-1-y-for-the-uconsole-and-devterm/14463/172 "2026-06-17T12:04:36Z")
I’m using your bookworm image, and everything works! I just thought Kali had a ton of pre-installed software, and I wanted to play with it. ---
**Author:** ![valleytechsolutions](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/valleytechsolutions/32/16969_2.png) [@valleytechsolutions](https://forum.clockworkpi.com/u/valleytechsolutions)\ **Post date:** [June 17, 2026, 3:58pm UTC](https://forum.clockworkpi.com/t/kali-7-1-y-for-the-uconsole-and-devterm/14463/173 "2026-06-17T15:58:03Z")
rex you are such a beautiful person, and your work is amazing! ---
**Author:** ![barry99705](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/barry99705/32/6771_2.png) [@barry99705](https://forum.clockworkpi.com/u/barry99705)\ **Post date:** [June 17, 2026, 4:05pm UTC](https://forum.clockworkpi.com/t/kali-7-1-y-for-the-uconsole-and-devterm/14463/174 "2026-06-17T16:05:52Z")
Not sure why everyone keeps saying “kali is bloated”. Sure it has a bunch of stuff installed, but it has less running processes than a stock debian install. Until recently they had a dedicated developer just for arm devices. > **[kali-linux-large - FAQ - Frequently Asked Questions | Kali Linux](https://www.kali.org/faq/#ive-heard-that-kali-linux-is-slow-and-bloated.-is-this-true)** > > Frequently Asked Questions (FAQ) > Due to the large number of users Kali Linux has, some questions are asked more commonly than others. To help address some of these questions, we have put together this FAQ. After all that is said though, kali is based on debian-testing, so stuff may break. ---
**Author:** ![Codiator](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/codiator/32/15080_2.png) [@Codiator](https://forum.clockworkpi.com/u/Codiator)\ **Post date:** [June 17, 2026, 9:53pm UTC](https://forum.clockworkpi.com/t/kali-7-1-y-for-the-uconsole-and-devterm/14463/175 "2026-06-17T21:53:16Z")
> **[Rex](https://buymeacoffee.com/ak.rex)** > > I'm a passionate open-source programmer, dedicated tinkerer, disabled veteran, and proud father. I served 8 years in the U.S. Army as a truck driver and communications expert.Transitioning to civilian ---
**Author:** ![Rex](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/rex/32/16852_2.png) [@Rex](https://forum.clockworkpi.com/u/Rex)\ **Post date:** [June 17, 2026, 10:10pm UTC](https://forum.clockworkpi.com/t/kali-7-1-y-for-the-uconsole-and-devterm/14463/176 "2026-06-17T22:10:33Z")
Thank you! Appreciate you brother, you’re one beautiful soul! ---
**Author:** ![bechlee7851](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/bechlee7851/32/16172_2.png) [@bechlee7851](https://forum.clockworkpi.com/u/bechlee7851)\ **Post date:** [June 24, 2026, 7:11am UTC](https://forum.clockworkpi.com/t/kali-7-1-y-for-the-uconsole-and-devterm/14463/177 "2026-06-24T07:11:56Z")
When I update your kali image, it fails to properly update and doesn’t boot properly. How should I fix it? ---
**Author:** ![snipeytje](https://avatars.discourse-cdn.com/v4/letter/s/2bfe46/32.png) [@snipeytje](https://forum.clockworkpi.com/u/snipeytje)\ **Post date:** [June 24, 2026, 8:10am UTC](https://forum.clockworkpi.com/t/kali-7-1-y-for-the-uconsole-and-devterm/14463/178 "2026-06-24T08:10:00Z")
If you have a micro hdmi cable you can plug that in, it’s likely the kernel got overwritten so the screen driver is gone You can fix that by reinstalling rex’s kernel package `clockworkpi-kernel` ---
**Author:** ![bechlee7851](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/bechlee7851/32/16172_2.png) [@bechlee7851](https://forum.clockworkpi.com/u/bechlee7851)\ **Post date:** [June 25, 2026, 7:15am UTC](https://forum.clockworkpi.com/t/kali-7-1-y-for-the-uconsole-and-devterm/14463/179 "2026-06-25T07:15:38Z")
Then I should check that when I use kali next time… ---
**Author:** ![zardwi](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/zardwi/32/12076_2.png) [@zardwi](https://forum.clockworkpi.com/u/zardwi)\ **Post date:** [July 9, 2026, 12:06pm UTC](https://forum.clockworkpi.com/t/kali-7-1-y-for-the-uconsole-and-devterm/14463/180 "2026-07-09T12:06:58Z")
[![](https://img.youtube.com/vi/9DO9fZP3z2k/maxresdefault.jpg "ValleyTechSolutions & Bruce-Dev Team SCAMMERS!") ](https://www.youtube.com/watch?v=9DO9fZP3z2k&t=715s) ---
**Author:** ![OchmechmlSVK](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/ochmechmlsvk/32/15920_2.png) [@OchmechmlSVK](https://forum.clockworkpi.com/u/OchmechmlSVK)\ **Post date:** [July 27, 2026, 3:24pm UTC](https://forum.clockworkpi.com/t/kali-7-1-y-for-the-uconsole-and-devterm/14463/181 "2026-07-27T15:24:53Z")
Hi CM5 uConsole - Kernel Panic on NetworkManager restart & APT Upgrade Breaks Bootloader/Kernel **Hardware Configuration:** - **Device:** ClockworkPi uConsole - **Compute Module:** Raspberry Pi CM5 (Wireless version) [pi5] + NVMe - **OS / Distro:** Kali Linux (Rex’s community port for CM5) [pi5] - **Storage:** MicroSD Card * * * **CRUCIAL UPGRADE BUG (APT Upgrade Breaks Boot):** - **Major Issue:** Running a standard system update completely destroys the installation. Every time I execute `sudo apt update && sudo apt upgrade -y`, the system becomes completely unbootable (stuck on a green power LED with a black screen, no HDMI output, no display backlight). - **Cause:** The official Kali ARM repositories overwrite the custom `kalipi-kernel`, `kalipi-bootloader`, and custom overlays provided in Rex’s image with generic Raspberry Pi 5 packages. The new kernel fails to initialize the uConsole hardware. The only way to recover the device after an upgrade is to completely re-flash the MicroSD card with a fresh image. Even pinning the packages via `apt-mark hold` is problematic because the system throws candidate/installation errors for `kalipi-kernel` due to its state. * * * **Description of the Wireless & Kernel Issue:** Even on a completely fresh, un-upgraded installation, the wireless stack is heavily broken and triggers a hard kernel deadlock: 1. **Initial Boot & Peripherals:** On a fresh image, the internal DSI display and keyboard were uninitialized. I patched this in Windows via `config.txt` using `dtoverlay=clockworkpi-uconsole-cm5` and `dwc2,dr_mode=host` [pi5]. 2. **Wi-Fi Authentication Loop:** The desktop environment detects the wireless interface (`wlan0`), but attempting to connect to a 2.4GHz WPA2 network via the GUI `nm-applet` results in an endless prompt loop asking for the password. 3. **NetworkManager Properties Missing Error:** Bypassing the GUI and using `nmcli` to connect (`sudo nmcli device wifi connect "SSID" password "KEY"`) throws this specific error: 4. **Kernel Panic / Hung Task Deadlock:** Attempting to force a restart of the wireless service using `sudo systemctl restart NetworkManager` completely freezes the operating system. The CPU cores enter a permanent deadlock (`blocked for more than 121 seconds`), turning the uConsole into a brick until a hard power-down is forced. * * * **Console Logs & Call Traces:** **1. Wireless Status (`iwconfig`):** **text** ```auto wlan0 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=-31 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off ``` **2. Kernel Stack Trace (Hung Task Dump during NetworkManager restart):** **text** ```auto INFO: task sudo:28223 blocked for more than 121 seconds. Not tainted 6.12.67-v8-16k+ #4 (or similar 6.x re4son kernel) "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:sudo state:D stack:0 pid:28223 tgid:28223 ppid:1 flags:0x00000005 Call Trace: __switch_to+0xf0/0x150 __schedule+0x394/0x860 schedule+0x5c/0x140 __schedule_preempt_disabled+0x2c/0x50 __mutex_lock_constprop.0+0x2ac/0x988 __mutex_lock_slowpath+0x1c/0x30 mutex_lock+0x50/0x58 rtnl_dumpit+0x94/0xd0 netlink_dump+0x134/0x378 netlink_dump_start+0x25c/0x350 rtnetlink_rcv_msg+0x280/0x3b8 netlink_rcv_skb+0x68/0x140 rtnetlink_rcv+0x20/0x30 netlink_unicast+0x330/0x3b8 ... Job session-2.scope/stop running (1min 21s / 1min 30s) ``` **Conclusion:** This image is currently unusable for daily tasks because **1)** standard `apt upgrade` destroys the kernel/bootloader configuration entirely, and **2)** the Broadcom `brcmfmac` wireless stack triggers a hard kernel panic when interacting with NetworkManager security properties. Is there a newer repository layout, a working `apt-preference` blacklist configuration to block the upgrade overwrite, or an updated kernel tree (6.6.y / 6.12.y) that actually works reliably on the CM5? Any advice would be highly appreciated. [Previous page](https://forum.clockworkpi.com/t/kali-7-1-y-for-the-uconsole-and-devterm/14463.md?page=8)