I have searched the existing open and closed issues
Required Information
DietPi version | latest version
Distro version | Bookworm
Kernel version | uname --all
SBC model | Orange Pi 3B (4Gb Ram)
SD card used | emmc (but now a HP SD Card
Dear friends, I ran the update command (via dietpi-launcher) and after restarting the SBC it no longer boots.
Apparently, the emmc somehow got corrupted, from that point on I created a new SD card with the latest version of Dietpi to try to restore my emmc.
The problem is that when doing the first boot, the board does not show any signs of life (the LED does not blink at any time) and the following message appears on the screen.
The strangest thing is that with all the other distributions I tested, none of them had this network problem, on all of them the network works perfectly
(I tested with the official OrangePi images, with Ubuntu desktop and also with Raspi OS, they all worked)
Hmm, so it reaches the dietpi-firstboot script and tries to bring up the network. But even if that fails, it should continue and bring you to a login prompt . Also when you give it some more time, nothing else shows up on the HDMI? In case, do you have a USB-UART adapter to access the serial console?
I think Armbian has a problem with their kernel. Do you have the old version of 3B board (v1.1.1)? I had many troubles with it on Armbian and I guess dietpi uses their kernel and configs.
You also did not actually run the uname -a command but I guess it was not possible.
@Jappe this won’t work. Networking is broken with the mainline edge Armbian kernel or Orange Pi 3B. Nothing that you suggest will fix this, it seems to be a dtb issue.
I only ever got wifi to work with new mainline kernels on Opi 3b v1.1.1 but it was unstable.
I understand that you want to do troubleshooting properly and step by step but I am offering a shortcut because I already tried these things…
Mainline kernels on the old 3b were broken for me at least since Linux 6.11. Some time before this ethernet and other things actually worked but I don’t know which kernel version this was because I reflashed the board since then, and lost the image. It’s been like this for at least 2 months.
On the BSP or “vendor” kernel the board works fine.
There is no BIOS on ARM (those without EFI at least).
Everything broke when they added support for the v2.1 board version, they allegedly kept support for the old one but I guess nobody bothered to check. It’s an upstream (so, armbian) problem.
I think you’ll need to ask the Armbian people, but be very careful not to mention anything about DietPi because they get very angry for some reason. The dietpi forum is quite friendly. Just install armbian, verify the problem is the same and try to get them to fix this.
Again never mention DietPi because they hate it (lol)