Skip to content
View in the app

A better way to browse. Learn more.

Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (โ‹ฎ) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Does not see eMMC after component change

Featured Replies

Issue found!
Orange PI changed eMMC from KLM8G1GETF to KLM8G1WEPD. The difference is eMMC 5.0 vs 5.1 and maybe more. The key things is that Armbian (checked using 5.35 and the latest one) does not see this memory (fdisk -l)!!
I have noticed it on OPI0 Plus 2 H3. PCB boards are the same, only memory model no. difference. Someone solved it or noticed the same?
Confused ๐Ÿคจ

  • Author

I am sure -ย  I have 100 pcs of this boards. Sold already 1000 with KLM8G1GETF -ย  no issues. The latest batch has different memory chip and I do not see this memory in fdisk -l. The old boards indicate eMMC memory.

  • Author
[    0.000000] Kernel command line: root=UUID=8591b60d-2481-4c21-806f-a9146bdb782f rootwait rootfstype=ext4 console=tty1 console=ttyS0,115200 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 loglevel=1 ubootpart=cd93fc55-01 ubootsource=mmc usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cma=96M  cgroup_enable=memory swapaccount=1
[    1.213356] [mmc]: SD/MMC/SDIO Host Controller Driver(v1.111 2015-4-13 15:24) Compiled in Nov 22 2017 at 13:44:04
[    1.213395] [mmc]: get mmc0's sdc_power is null!
[    1.213424] [mmc]: get mmc1's sdc_power is null!
[    1.213434] [mmc]: get mmc1's 2xmode ok, val = 1
[    1.213443] [mmc]: get mmc1's ddrmode ok, val = 1
[    1.213473] [mmc]: get mmc2's sdc_power is null!
[    1.213483] [mmc]: get mmc2's 2xmode ok, val = 1
[    1.213492] [mmc]: get mmc2's ddrmode ok, val = 1
[    1.213505] [mmc]: MMC host used card: 0x7, boot card: 0x0, io_card 2
[    1.217283] [mmc]: sdc0 power_supply is null
[    1.329173] mmc0: new high speed SDHC card at address aaaa
[    1.329733] mmcblk0: mmc0:aaaa SC16G 14.8 GiB
[    1.332534]  mmcblk0: p1
[    1.333183] mmcblk mmc0:aaaa: Card claimed for testing.
[    1.333199] mmc0:aaaa: SC16G 14.8 GiB
[    1.334782] [mmc]: sdc2 power_supply is null
[    1.472884] mmc2: unrecognised EXT_CSD revision 8
[    1.472905] mmc2: error -22 whilst initialising MMC card
[    1.473035] [mmc]: sdc2 power_supply is null
[    1.477145] [mmc]: sdc2 power_supply is null
[    1.567456] mmc2: unrecognised EXT_CSD revision 8
[    1.567488] mmc2: error -22 whilst initialising MMC card
[    1.567643] [mmc]: sdc2 power_supply is null
[    1.571824] [mmc]: sdc2 power_supply is null
[    1.675883] mmc2: unrecognised EXT_CSD revision 8
[    1.675919] mmc2: error -22 whilst initialising MMC card
[    1.676074] [mmc]: sdc2 power_supply is null
[    1.680111] [mmc]: sdc2 power_supply is null
[    1.804071] mmc2: unrecognised EXT_CSD revision 8
[    1.804109] mmc2: error -22 whilst initialising MMC card
[    1.804260] [mmc]: sdc2 power_supply is null
[    1.808537] [mmc]: sdc1 power_supply is null
[    1.858522] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[    1.860256] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    1.862010] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    1.865025] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[    1.868606] mmc1: queuing unknown CIS tuple 0x81 (9 bytes)
[    1.965277] mmc1: new high speed SDIO card at address 0001
[    8.127876] EXT4-fs (mmcblk0p1): mounted filesystem with writeback data mode. Opts: (null)
[   10.695377] EXT4-fs (mmcblk0p1): re-mounted. Opts: commit=600,errors=remount-ro
[   10.850354] dummy_sdmmc: probe of mmc1:0001:1 failed with error -123
[   10.850409] dummy_sdmmc: probe of mmc1:0001:2 failed with error -123
[   10.850649] mmc1: card 0001 removed
[   10.850954] [mmc]: sdc1 power_supply is null
[   10.855213] [mmc]: sdc1 power_supply is null
[   10.907235] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[   10.908787] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[   10.910345] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[   10.913116] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[   10.916502] mmc1: queuing unknown CIS tuple 0x81 (9 bytes)
[   11.002973] mmc1: new high speed SDIO card at address 0001
[   11.019839] bcmsdh_sdmmc: bcmsdh_sdmmc_probe Enter
[   11.019933] bcmsdh_sdmmc: bcmsdh_sdmmc_probe Enter

Here you go.

  • Author

And the same command on Samsung memory (eMMC was detected):
ย 

[    0.000000] Kernel command line: root=UUID=8591b60d-2481-4c21-806f-a9146bdb782f rootwait rootfstype=ext4 console=tty1 console=ttyS0,115200 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 loglevel=1 ubootpart=cd93fc55-01 ubootsource=mmc usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cma=96M  cgroup_enable=memory swapaccount=1
[    1.223368] [mmc]: SD/MMC/SDIO Host Controller Driver(v1.111 2015-4-13 15:24) Compiled in Nov 22 2017 at 13:44:04
[    1.223406] [mmc]: get mmc0's sdc_power is null!
[    1.223436] [mmc]: get mmc1's sdc_power is null!
[    1.223445] [mmc]: get mmc1's 2xmode ok, val = 1
[    1.223454] [mmc]: get mmc1's ddrmode ok, val = 1
[    1.223484] [mmc]: get mmc2's sdc_power is null!
[    1.223493] [mmc]: get mmc2's 2xmode ok, val = 1
[    1.223502] [mmc]: get mmc2's ddrmode ok, val = 1
[    1.223516] [mmc]: MMC host used card: 0x7, boot card: 0x0, io_card 2
[    1.227308] [mmc]: sdc0 power_supply is null
[    1.339175] mmc0: new high speed SDHC card at address aaaa
[    1.339742] mmcblk0: mmc0:aaaa SC16G 14.8 GiB
[    1.342545]  mmcblk0: p1
[    1.343211] mmcblk mmc0:aaaa: Card claimed for testing.
[    1.343227] mmc0:aaaa: SC16G 14.8 GiB
[    1.344811] [mmc]: sdc2 power_supply is null
[    1.464544] mmc2: new high speed DDR MMC card at address 0001
[    1.465129] mmcblk1: mmc2:0001 8WPD3R 7.28 GiB
[    1.465380] mmcblk1boot0: mmc2:0001 8WPD3R partition 1 4.00 MiB
[    1.465617] mmcblk1boot1: mmc2:0001 8WPD3R partition 2 4.00 MiB
[    1.466642]  mmcblk1: p1
[    1.469477]  mmcblk1boot1: unknown partition table
[    1.471042]  mmcblk1boot0: unknown partition table
[    1.471271] mmcblk mmc2:0001: Card claimed for testing.
[    1.471284] mmc2:0001: 8WPD3R 7.28 GiB
[    1.472856] [mmc]: sdc1 power_supply is null
[    1.528224] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[    1.529882] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    1.531514] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    1.534440] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[    1.631553] mmc1: new high speed SDIO card at address 0001
[    8.337376] EXT4-fs (mmcblk0p1): mounted filesystem with writeback data mode. Opts: (null)
[   11.001099] EXT4-fs (mmcblk0p1): re-mounted. Opts: commit=600,errors=remount-ro
[   11.070301] dummy_sdmmc: probe of mmc1:0001:1 failed with error -123
[   11.070349] dummy_sdmmc: probe of mmc1:0001:2 failed with error -123
[   11.070557] mmc1: card 0001 removed
[   11.070816] [mmc]: sdc1 power_supply is null
[   11.074947] [mmc]: sdc1 power_supply is null
[   11.127956] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[   11.129516] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[   11.131107] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[   11.133882] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[   11.224041] mmc1: new high speed SDIO card at address 0001
[   11.240329] bcmsdh_sdmmc: bcmsdh_sdmmc_probe Enter
[   11.240449] bcmsdh_sdmmc: bcmsdh_sdmmc_probe Enter

ย 

7 hours ago, Robert LabTeam said:

[ 1.472884] mmc2: unrecognised EXT_CSD revision 8

[ 1.472905] mmc2: error -22 whilst initialising MMC card

I think this is the bottom of the issue.

But I don't know how to fix it ...

ย 

EDIT : it seems that it is already fixed : https://github.com/armbian/build/commit/dcedd6c2ec102a9524b140604ce301b67cbbd27a

EDIT2 : This means that you are using a pretty old image since this fix in Legacy is present since more than a year ...

Guest
This topic is now closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions โ†’ Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.