You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the existing open and closed issues
Required Information
DietPi version | G_DIETPI_VERSION_CORE=9 G_DIETPI_VERSION_SUB=7 G_DIETPI_VERSION_RC=1 G_GITBRANCH='master' G_GITOWNER='MichaIng'
Distro version | bookworm
Kernel version | Linux DietPi 6.1.75-vendor-rk35xx #1 SMP Thu Jul 25 14:36:35 UTC 2024 aarch64 GNU/Linux
SBC model | Orange Pi 5 Plus (aarch64)
Power supply used | 5V 4A power source
SD card used | kingston 16gb
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?
yes
Bug report ID | bc1d3cee-51d7-475d-98f0-cc521f079dbe
Steps to reproduce
Install dietpi
boot
Expected behaviour
eMMC card detected
Actual behaviour
eMMC card is not detected
Extra details
it doesn't seem to be a faulty card, booting official image "Orangepi5plus_1.0.8_debian_bookworm_server_linux6.1.43" does detect the eMMC card, kernel Linux orangepi5plus 6.1.43-rockchip-rk3588 #1.0.8 SMP Sat Feb 3 00:04:38 CST 2024 aarch64 GNU/Linux
dietpi dmesg and lsblk
root@DietPi:~# dmesg|grep mmc
[ 14.844738] dwmmc_rockchip fe2c0000.mmc: No normal pinctrl state
[ 14.844763] dwmmc_rockchip fe2c0000.mmc: No idle pinctrl state
[ 14.844829] dwmmc_rockchip fe2c0000.mmc: IDMAC supports 32-bit address mode.
[ 14.844868] dwmmc_rockchip fe2c0000.mmc: Using internal DMA controller.
[ 14.844887] dwmmc_rockchip fe2c0000.mmc: Version ID is 270a
[ 14.844948] dwmmc_rockchip fe2c0000.mmc: DW MMC controller at irq 105,32 bit host data width,256 deep fifo
[ 14.845037] dwmmc_rockchip fe2c0000.mmc: Looking up vmmc-supply from device tree
[ 14.846046] sdhci-dwcmshc fe2e0000.mmc: Looking up vmmc-supply from device tree
[ 14.846061] sdhci-dwcmshc fe2e0000.mmc: Looking up vmmc-supply property in node /mmc@fe2e0000 failed
[ 14.855478] sdhci-dwcmshc fe2e0000.mmc: Looking up vqmmc-supply from device tree
[ 14.855491] sdhci-dwcmshc fe2e0000.mmc: Looking up vqmmc-supply property in node /mmc@fe2e0000 failed
[ 14.855566] dwmmc_rockchip fe2c0000.mmc: Looking up vqmmc-supply from device tree
[ 14.861432] mmc0: CQHCI version 5.10
[ 14.884021] mmc_host mmc1: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)
[ 14.894516] mmc0: SDHCI controller on fe2e0000.mmc [fe2e0000.mmc] using ADMA
[ 14.931096] mmc_host mmc1: Bus speed (slot 0) = 49500000Hz (slot req 50000000Hz, actual 49500000HZ div = 0)
[ 14.931819] mmc1: new high speed SDHC card at address 1234
[ 14.932962] mmcblk1: mmc1:1234 SA16G 14.4 GiB
[ 14.943460] mmcblk1: p1
[ 15.799661] EXT4-fs (mmcblk1p1): mounted filesystem with ordered data mode. Quota mode: none.
[ 17.587316] EXT4-fs (mmcblk1p1): re-mounted. Quota mode: none.
root@DietPi:/boot# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
mtdblock0 31:0 0 16M 0 disk
mmcblk1 179:0 0 14,4G 0 disk
└─mmcblk1p1 179:1 0 14,4G 0 part /
nvme0n1 259:0 0 953,9G 0 disk
└─nvme0n1p1 259:1 0 953,9G 0 part
Yes, this issue still is there but I figured out what is the problem and it's the u-boot.
Booting the orange pi with dietpi default uboot (vendor) leads to eMMC card detection failure.
Switching to u-boot-orangepi5-plus-legacy and installing it solves the problem.
So, in order to solve the issue it is necessary to do:
apt install u-boot-orangepi5-plus-legacy
cd /usr/lib/linux-u-boot-legacy-orangepi5-plus
dd if=idbloader.img of=/dev/mmcblk1 seek=64 conv=notrunc
588+0 records in
588+0 records out
301056 bytes (301 kB, 294 KiB) copied, 0.00487433 s, 61.8 MB/s
dd if=u-boot.itb of=/dev/mmcblk1 seek=16384 conv=notrunc
2740+0 records in
2740+0 records out
1402880 bytes (1.4 MB, 1.3 MiB) copied, 0.0183882 s, 76.3 MB/s
Attached both boot logs, maybe there is some voltage failure there
vendor:
DM: v2
mmc@fe2c0000: 1, mmc@fe2e0000: 0
Card did not respond to voltage select!
Thanks for the info. Hmm good to know and bad. Actually I thought that both U-Boot packages use the same source. But the versions are different, if course. I'll test our as well, and see whether I can identify the related change in the source code.
Creating a bug report/issue
Required Information
DietPi version |
G_DIETPI_VERSION_CORE=9 G_DIETPI_VERSION_SUB=7 G_DIETPI_VERSION_RC=1 G_GITBRANCH='master' G_GITOWNER='MichaIng'
Distro version |
bookworm
Kernel version |
Linux DietPi 6.1.75-vendor-rk35xx #1 SMP Thu Jul 25 14:36:35 UTC 2024 aarch64 GNU/Linux
SBC model |
Orange Pi 5 Plus (aarch64)
Power supply used |
5V 4A power source
SD card used |
kingston 16gb
Additional Information (if applicable)
yes
bc1d3cee-51d7-475d-98f0-cc521f079dbe
Steps to reproduce
Expected behaviour
Actual behaviour
Extra details
it doesn't seem to be a faulty card, booting official image "Orangepi5plus_1.0.8_debian_bookworm_server_linux6.1.43" does detect the eMMC card, kernel
Linux orangepi5plus 6.1.43-rockchip-rk3588 #1.0.8 SMP Sat Feb 3 00:04:38 CST 2024 aarch64 GNU/Linux
dietpi dmesg and lsblk
orange pi 1.0.8 dietpi dmesg and lsblk
eMMC detected
[ 6.776179] mmcblk0: mmc0:0001 A3A551 28.9 GiB
I also tried to boot with the orangepi kernel, but the result was the same, eMMC card not detected.
The text was updated successfully, but these errors were encountered: