# Orange Pi 5+ should we have switched kernel?

**URL:** https://dietpi.com/forum/t/orange-pi-5-should-we-have-switched-kernel/19929
**Category:** General Discussion
**Created:** [18 April 2024 20:50 UTC](https://dietpi.com/forum/t/orange-pi-5-should-we-have-switched-kernel/19929 "2024-04-18T20:50:04Z")
**Posts on this page:** 1
**Showing post:** 63

<div class="post-metadata">

### Author: ![MichaIng](https://dietpi.com/forum/user_avatar/dietpi.com/michaing/32/7_2.png) [@MichaIng](https://dietpi.com/forum/u/MichaIng)
#### Post date: [19 June 2024 23:19 UTC](https://dietpi.com/forum/t/orange-pi-5-should-we-have-switched-kernel/19929/63 "2024-06-19T23:19:44Z")

</div>

Thanks for verifying. Kernel workers are normal, just that udev-worker that never disappeared, as if a device was detached and re-attached in a loop, was not normal and caused quite some load. IIRC, on each loop, all udev rules were reloaded (parsed and in case applied again), which was the major reason for the load.

> [@b9AcE](#):
>
> There was an issue about me during the upgrade having to revert a bit of dtb-crust leftover from our adventure

I remember. On a quick review of the maintainer scripts, I could not find an issue, but I wanted to add a debug flag to all scripts to find the command and condition which leads to the faulty `dtb-*` directory removal.

---

_[View the full topic](https://dietpi.com/forum/t/orange-pi-5-should-we-have-switched-kernel/19929)._