I have searched the existing open and closed issues
Required Information
DietPi version | 9.13
Distro version | ``
Kernel version | Latest branch 25.xx
Architecture | arm64
SBC model | Odroid HC4
Additional Information (if applicable)
It happens before this version too, when latest kernel update, jump on apt
Steps to reproduce
Updating to latest version and fresh install, tested
Few weeks ago, I was on 9.12 and I saw that there was new versions of (I don’t know what the proper name) packages something like linux-current-image-meson64 version 25.05.0-trunk-dietpi1 and another package with dtb in it, I updated and after a reboot, I had no usb nor ethernet connection, I connected a monitor and it was on terminal login, so it boot right.
I had another SD with the previous packages (24.11.0-trunk-dietpi2) I copied them over the old, and I could recover.
After that until today I saw packages update for armbian-firmware and other maybe related with the kernel and I thought that maybe it was solved, I have updated and same problem again.
I know the kernel is armbian thing, but if you know some fix…
I saw some threads on armbian forum, maybe helpful..
Do you know the right way to go back without ssh, I was going to install and old Dietpi version with 24.11.0 and copy over the boot folder…
Thanks for the report and the links. The boot issue on Odroid C2 is unrelated, though thinkable that older DietPi systems are affected as well. New U-Boot builds are not flashed automatically. Maybe we should change that in DietPi, to assure the bootloader is always the latest version tested to work fine with the kernel. E.g. on ROCK Pi S I also needed to flash a new bootloader to boot Linux 6.12, but no idea how old it (the previously flashed U-Boot) was prior to that.
The kernel headers topic is also runrelated.
Not sure whether the C2 USB issue and the HC4 one are the same, but we can test that. It is the same kernel for both boards at least. Let me create a build with this change.
cd /tmp
wget https://dietpi.com/downloads/binaries/testing/linux-{image,dtb}-current-meson64.deb
sudo dpkg -i linux-{image,dtb}-current-meson64.deb
sudo reboot
Let’s see whether it helps. USB issues indeed were very common on all Odroid boards, for whatever reason. Maybe this can help.
However, on my Odroid N2+, which is very similar to the Odroid C4/HC4, USB and Ethernet both works fine. Also I could not find any hint elsewhere that this USB2 setting is not compatible with USB1.1 support enabled. And as this disables USB1.1 support, such devices would probably fallback to USB1.0 (UHCI) or not work at all, not sure.
Until build is done etc, before you test the new kernel, can you show below commands out with a USB device attached:
lsusb
ip a
dmesg -l 0,1,2,3
I know might be difficult without SSH, maybe you have a USB-UART adapter to get the output via serial console.