xNiux

Just apt update | apt upgrade But now there is nothing after "Starting kernel ..." even if I connect USB key and with toothstick 😬

So, I renamed the files in the extlinux.conf on /dev/mmcblkp1 .... and know : 0 card out (Re)start USB... USB0: USB3.0 XHCI init start Register 3000140 NbrPorts 2 Starting the controller USB XHCI 1.10 scanning bus 0 for devices... 3 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found ** Bad device usb 0 ** ** Bad device usb 1 ** ** Bad device usb 2 ** ** Bad device usb 3 ** reading emmc_autoscript 174 bytes read in 3 ms (56.6 KiB/s) ## Executing script at 01020000 ## Error: "bootfromsd" not defined reading u-boot.emmc 798672 bytes read in 25 ms (30.5 MiB/s) ## Starting application at 0x01000000 ... U-Boot 2023.10-ge0534f47 (Jan 28 2024 - 06:23:01 +0000) armbian-sm1 Model: Armbian aml-s9xx-box u-boot s905x3 SoC: Amlogic Meson SM1 (S905X3) Revision 2b:c (10:2) DRAM: 1 GiB (effective 3.8 GiB) Core: 396 devices, 26 uclasses, devicetree: separate MMC: sd@ffe03000: 0, sd@ffe05000: 1, mmc@ffe07000: 2 Loading Environment from MMC... *** Warning - bad CRC, using default environment In: usbkbd,serial Out: vidconsole,serial Err: vidconsole,serial Model: Armbian aml-s9xx-box u-boot s905x3 SoC: Amlogic Meson SM1 (S905X3) Revision 2b:c (10:2) Net: eth0: ethernet@ff3f0000 Hit any key to stop autoboot: 0 Card did not respond to voltage select! : -110 Card did not respond to voltage select! : -110 switch to partitions #0, OK mmc2(part 0) is current device Scanning mmc 2:1... Found /extlinux/extlinux.conf Retrieving file: /extlinux/extlinux.conf 1: Armbian 25.5.0-trunk.97 bookworm 6.12.16-current-meson64 Retrieving file: /Image Retrieving file: /uInitrd append: root=/dev/root ro quiet Moving Image from 0x8080000 to 0x8200000, end=a430000 ## Loading init Ramdisk from Legacy Image at 13000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 24643484 Bytes = 23.5 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at eaf21540 Booting using the fdt blob at 0xeaf21540 Working FDT set to eaf21540 Loading Ramdisk to 3e87f000, end 3ffff79c ... OK Loading Device Tree to 000000003e869000, end 000000003e87e85f ... OK Working FDT set to 3e869000 Starting kernel ... [ 0.000000] OF: reserved mem: OVERLAP DETECTED! [ 0.000000] secmon@5300000 (0x0000000005300000--0x0000000007300000) overlaps with bl32@5000000 (0x0000000005300000--0x0000000007300000) [ 0.903103] meson-gx-socinfo-sm ff800140.ao-secure: no secure-monitor node found [ 0.903135] meson-gx-socinfo-sm ff800140.ao-secure: probe with driver meson-gx-socinfo-sm failed with error -22 [ 1.052307] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000c8 [ 1.055449] Mem abort info: [ 1.058231] ESR = 0x0000000096000004 [ 1.061931] EC = 0x25: DABT (current EL), IL = 32 bits [ 1.067266] SET = 0, FnV = 0 [ 1.070230] EA = 0, S1PTW = 0 [ 1.073406] FSC = 0x04: level 0 translation fault [ 1.078164] Data abort info: [ 1.080989] ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000 [ 1.086431] CM = 0, WnR = 0, TnD = 0, TagAccess = 0 [ 1.091447] GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 [ 1.096728] [00000000000000c8] user address but active_mm is swapper [ 1.103018] Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP [ 1.109179] Modules linked in: [ 1.112197] CPU: 0 UID: 0 PID: 49 Comm: kworker/u16:2 Tainted: G W 6.12.16-current-meson64 #1 [ 1.122032] Tainted: [W]=WARN [ 1.124960] Hardware name: Armbian aml-s9xx-box u-boot s905x3 (DT) [ 1.131086] Workqueue: events_unbound deferred_probe_work_func [ 1.136865] pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 1.143763] pc : meson_dw_hdmi_unbind+0x10/0x24 [ 1.148250] lr : component_unbind+0x38/0x60 [ 1.152388] sp : ffff80008276b9c0 [ 1.155662] x29: ffff80008276b9c0 x28: ffff000007482300 x27: 0000000000000000 [ 1.162736] x26: ffff000001253010 x25: ffff8000811d2868 x24: ffff0000011ff800 [ 1.169810] x23: 0000000000000001 x22: ffff0000011ff800 x21: ffffffffffffffff [ 1.176882] x20: ffff000007482340 x19: ffff0000000f0d80 x18: ffffffffffffffff [ 1.183954] x17: 00000000c75c09e9 x16: 0000000000000000 x15: 0000000000000001 [ 1.191027] x14: 0000000000000019 x13: ffff800082077360 x12: 0000000000000000 [ 1.198098] x11: ffff000000402328 x10: ffff000000402238 x9 : 0000000000000000 [ 1.205171] x8 : ffff8000821fc000 x7 : ffff80008276b820 x6 : ffff80008276b870 [ 1.212243] x5 : ffff8000809a346c x4 : fffffdffc0047e20 x3 : ffff800080a00a40 [ 1.219315] x2 : ffff0000011ff800 x1 : ffff000001253010 x0 : 0000000000000000 [ 1.226390] Call trace: [ 1.228802] meson_dw_hdmi_unbind+0x10/0x24 [ 1.232947] component_unbind+0x38/0x60 [ 1.236738] component_unbind_all+0xc8/0xd4 [ 1.240877] meson_drv_bind_master+0x204/0x500 [ 1.245277] meson_drv_bind+0x14/0x20 [ 1.248898] try_to_bring_up_aggregate_device+0x1f0/0x2f8 [ 1.254249] component_master_add_with_match+0xb0/0xf8 [ 1.259336] meson_drv_probe+0x10c/0x1a8 [ 1.263215] platform_probe+0x68/0xdc [ 1.266841] really_probe+0xc0/0x38c [ 1.270374] __driver_probe_device+0x7c/0x15c [ 1.274687] driver_probe_device+0x40/0x114 [ 1.278826] __device_attach_driver+0xbc/0x158 [ 1.283227] bus_for_each_drv+0x80/0xdc [ 1.287021] __device_attach+0xa8/0x1d4 [ 1.290815] device_initial_probe+0x14/0x20 [ 1.294955] bus_probe_device+0xac/0xb0 [ 1.298750] deferred_probe_work_func+0x9c/0xec [ 1.303236] process_one_work+0x168/0x2b8 [ 1.307205] worker_thread+0x2dc/0x3dc [ 1.310914] kthread+0x118/0x11c [ 1.314103] ret_from_fork+0x10/0x20 [ 1.317647] Code: d503233f a9bf7bfd 910003fd f9403c00 (f9406400) [ 1.323684] ---[ end trace 0000000000000000 ]--- [ 1.544519] Freeing initrd memory: 24064K

In first case, it looking for 2 files : /Image and /uInitrd This 2 files is existing …. And after update : /vmlinuz-6.12.16-current-meson64 This file doesn't exist … But, /Image and /uInitrd is existing so ….

And juste after kernel update : In: usbkbd,serial Out: vidconsole,serial Err: vidconsole,serial Model: Armbian aml-s9xx-box u-boot s905x3 SoC: Amlogic Meson SM1 (S905X3) Revision 2b:c (10:2) Net: eth0: ethernet@ff3f0000 Hit any key to stop autoboot: 0 Card did not respond to voltage select! : -110 Card did not respond to voltage select! : -110 switch to partitions #0, OK mmc2(part 0) is current device Scanning mmc 2:1... Found /extlinux/extlinux.conf Retrieving file: /extlinux/extlinux.conf 1: Armbian 25.5.0-trunk.97 bookworm 6.12.16-current-meson64 Retrieving file: /vmlinuz-6.12.16-current-meson64 Skipping l0 for failure retrieving kernel 2: Armbian 25.5.0-trunk.97 bookworm 6.12.16-current-meson64 (rescue target) Retrieving file: /vmlinuz-6.12.16-current-meson64 Skipping l0r for failure retrieving kernel EXTLINUX FAILED: continuing...

mmmh that interesting ... I log the start after a fresh installation on MMC : U-Boot 2023.10-ge0534f47 (Jan 28 2024 - 06:23:01 +0000) armbian-sm1 Model: Armbian aml-s9xx-box u-boot s905x3 SoC: Amlogic Meson SM1 (S905X3) Revision 2b:c (10:2) DRAM: 1 GiB (effective 3.8 GiB) Core: 396 devices, 26 uclasses, devicetree: separate MMC: sd@ffe03000: 0, sd@ffe05000: 1, mmc@ffe07000: 2 Loading Environment from MMC... *** Warning - bad CRC, using default environment In: usbkbd,serial Out: vidconsole,serial Err: vidconsole,serial Model: Armbian aml-s9xx-box u-boot s905x3 SoC: Amlogic Meson SM1 (S905X3) Revision 2b:c (10:2) Net: eth0: ethernet@ff3f0000 Hit any key to stop autoboot: 0 Card did not respond to voltage select! : -110 Card did not respond to voltage select! : -110 switch to partitions #0, OK mmc2(part 0) is current device Scanning mmc 2:1... Found /extlinux/extlinux.conf Retrieving file: /extlinux/extlinux.conf 1: Armbian_community Retrieving file: /Image Retrieving file: /uInitrd append: root=LABEL=ROOT_EMMC rootflags=data=writeback console=ttyAML0,115200n8 console=tty0 rw no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 splash plymouth.ignore-serial-consoles cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 Retrieving file: /dtb/amlogic/meson-sm1-x96-air.dtb Moving Image from 0x8080000 to 0x8200000, end=9cd0000 ## Loading init Ramdisk from Legacy Image at 13000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 22998274 Bytes = 21.9 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 08008000 Booting using the fdt blob at 0x8008000 Working FDT set to 8008000 Loading Ramdisk to 3ea11000, end 3ffffd02 ... OK Loading Device Tree to 000000003e9fb000, end 000000003ea100ff ... OK Working FDT set to 3e9fb000 Starting kernel ...

Yes, agree with that ... but why .... that's the really question, I will do more test

OK, previous problem come from the command u-boot-refresh, which erased extlinux.conf. So, I reinstall properly the system on emmc. And after the upgrade and reboot, I have more detail.... First : I have a black screen, and the only possibility is to put the USB key with armbian and restart the box with the toothstick. I joined to this message the debug COM log when I have the black screen. debugUsb.txt

Ok, I successfully mounted the /dev/mmblk1p1 partition. And I understand the problem : extlinux.conf is incomplete, it missing labels ... I will try to install a cleanly system on emmc, and trace the problem on next kernel upgrade

Yes for sure, and the installation on emmc work perfectly. I don't know if it's normal, but starting with a USB system, I can't mount any emmc partition .... So, I can't get my datas, or try to restore emmc boot 😢

Hi started a fresh amrbian system from USB, and I hopped the command u-boot-refresh detect emmc system and add it to the boot choice.

Hum no ... I tried a u-boot-refresh from usb system ... But it break the usb boot ...

Hi, I installed armbian on the emmc of Magicsee N5+, it work very well. But after kernel update, I'm unable to restart the emmc system .... I tried 5x on the 3 last month, and I always have the same issue .... Is there any solution ? Maybe it links with this error message after update :

More precision : 1. Install all u-boot packagés 2. Connect your boot USB stick or sdcard 3. Exécuté 'dudo u-boot-refresh' 4. Reboot And hop, it start on USB or sdcard

hum, I just install it and execute it : Installation : sudo apt-get -y install u-boot-menu Execution (I'm not sure) : sudo u-boot-menu ... And reboot

Ok,I now Can start with sdhc : I installed and executed u-boot-menu.

Hi ! I started from SDHC armbian-24.08 on my Magicsee N5+ (s905x3). I installed system on the eMMC. But now, the system can only start on the eMMC, but only with the toothstick method ... And I can't start again on the SDHC to try the 24.11 for example. Is that any solution : 1. to make start on eMMD without toothstick 2. to start system with SDHC Thanks for your help

And after some test on USB flash : - WIFI : OK - ETH : OK - IR : OK - BT : OK - CPU : High temperature (65°C), box heating a lot .... USB powering ?

Ok, I tried some test. - Good news : I start Armbian on USB Drive !!! - Bad news : On SD card, Armbian doesn't start !!! Please see the 2 logs, have you and Idea ? ==> Before each test, I reflash the stock firmware before flash Armbian ==> But in fact, my test revealed there is no really importance ==> The USB drive could be start Armbian on USB2 port, but also on the USB3 port ... ArmbianBootUSB.log ArmbianBootSD.log

Thanks for your answer ^^ It's a learning opportunity for me, I like this kind of challenge ... And I'm not user of Arch Linux ... I'm definitevely a Debian user ! I will try your recommendation.

I'm trying the Manjaro distribution .... It start !!! (meson-sm1-x96-air.dtb) So, the .img it a little different .... - First, I tried to use the Manjaro meson-sm1-x96-air.dtb on Armbian : Failed, with same issue reboot in loop - 2nD, I tried to replace le linux main partition from Manjaro img with the Armbian one (Keep the Manjaro boot partition) : Failed, I have the Manjaro boot logo but ... that's all .....

Mmmh I see 3 potential problems : First : 2nd : And the third : After that, U-Boot seems to restart ....

There is clearly a bad things on the sdcard ... I think the real problem is here : ## Error: "bootfromsd" not defined reading boot_android ** Unable to read file boot_android ** ** Bad device usb 0 **

Ok so, I connect the debug UART. But I can't what I think about the result (Joined to this post) .... Is it here where I have to post the log ? or there is another one more adapted ? multiboot_magicsee_n5plus.log

On other box, I found this connection, I will try it : https://www.youtube.com/watch?v=uSuFVntxRg0

Is it the same pins on all S905X3 ? I have 2 connectors : - 1 with 4 pins (closed to AV and SPDIF connectors) - 1with 2x12 pins (External Flash ? same on all S905X3 ?)