Creating a bug report/issue
I have searched the existing open and closed issues
Required Information
- DietPi version |
- root@DietPi:~# cat /boot/dietpi/.version
G_DIETPI_VERSION_CORE=9
G_DIETPI_VERSION_SUB=8
G_DIETPI_VERSION_RC=0
G_GITBRANCH=‘master’
G_GITOWNER=‘MichaIng’
root@DietPi:~# - Distro version |
echo $G_DISTRO_NAME $G_RASPBIAN - root@DietPi:~#
echo $G_DISTRO_NAME $G_RASPBIAN
-bash: bookworm: command not found - Kernel version |
uname --all - Linux DietPi 6.1.75-vendor-rk35xx #1 SMP Thu Jul 25 14:36:35 UTC 2024 aarch64 GNU/Linux
- Architecture |
dpkg --print-architecture - arm64
- SBC model |
echo $G_HW_MODEL_NAMEor (EG: RPi3) - Orange Pi 5 Plus (aarch64)
- Power supply used | (EG: 5V 1A RAVpower)
- I forget, but n/a because it has always worked and worked fine just prior to my attempting a fresh dietpi install
- SD card used | (EG: SanDisk ultra)
- Sandisk 32GB
Additional Information (if applicable)
- Software title | (EG: Nextcloud)
- Was the software title installed freshly or updated/migrated?
- Can this issue be replicated on a fresh installation of DietPi?
← If you sent a “dietpi-bugreport”, please paste the ID here → - Bug report ID |
echo $G_HW_UUID
Steps to reproduce
- …
- …
Expected behaviour
- …
Actual behaviour
I’m aware that this topic has been covered, but I keep running into it with this board and this time nothing seems to be working for me this time around.
My ultimate goal is to have the machine boot from and run Dietpi OS directly from the emmc drive installed on my board. I’d previously gotten it working with this exact same board and hardware setup, so I know it’s possible, or at least was with the state of the tools available a couple of years ago.
Extra details
I’ve tried:
- Using DD to clone the entire SD card system (running live) from he SD card to emmc and simply rebooting there
- Using DD to clone the entire system from the SD card to the emmc, as above, but then also swapping the drve that “dietpiEnv.txt” references to by UUID to that of the emmc on the emmc boot instance
- Manually creating partitions that DietPi is expecting and rsyncing all of it from the sd card and attemptIng to boot without referencing the UUID of the drive and with.
- Connecting to the Orange pi console using usb c to A cable and rkdevtool on my laptop with orange pi in mask mode. RKdevtool sees the device, but it seems unable to perform any operations on it like clearing the SPI flash ir writing a new bootloader. All attempts to read from or write to SPI chip seem to fail. It is worht mentioning that the SPI flash drive does show up inside of dietpi as mtdblk0, so the problem is not that the OS is not seeing it.
- I’ve tried updating both the spi bootloader and emmc bootloader from the dietpi-config tools, with no change.
I suspect the SPI bootloader is my problem, but I see no more direct way of interacting with it than the RKdevtool connection, but those all fail.
Would anybody at all have any suggestions as what to try or where to go next? It’s furstrating because the system runs fine from the SD Card, and t seems I’m so close and yet obviously a bit too far away from the ultimate solution.
Any help would be greatly appreciated. I’m losing my mind over this and it’s keeping me from getting to the rest of my setup.
Thank you so very much in advance.
Kind Regards,
Adam B
P.s. I can pretty much rule out a hardware issue or power supply issue. The machine had literally been running with the very configuration I’ve described up until 2 day ago when I tried just do a fresh install of dietpi.