Search the Community

@ebin-dev thanks for the script, i will try it. But you have 3 different UUID in the script... first one 7268e76f-3e1b-4e01-a6be-123456789012 ... mount --uuid 7268e76f-3e1b-4e01-a6be-123456789012 /mnt/emmc the second b790c4d7-5709-4000-91ac-123456789012 and the third 7268e76f-3e1b-4e01-a6be-987654321098 ... sed -e 's/UUID=b790c4d7-5709-4000-91ac-123456789012/UUID=7268e76f-3e1b-4e01-a6be-987654321098/g' -i /mnt/emmc/etc/fstab the mount one is the "to device" or it is an another? here are my uuid's... root@helios64:~# blkid /dev/sdd: UUID="29f2832b-d95d-3e76-0375-3b2b0f0xxxxx" UUID_SUB="e187038d-7022-19b6-ac81-2f7dd80b2dae" LABEL="helios64:0" TYPE="linux_raid_member" /dev/md127: LABEL="nas" UUID="b5c52051-e75f-408c-a7af-4a5d0daxxxxx" BLOCK_SIZE="4096" TYPE="ext4" /dev/sdb: UUID="29f2832b-d95d-3e76-0375-3b2b0fxxxxx" UUID_SUB="914413d8-94a7-a983-6c96-7ae639f85ad2" LABEL="helios64:0" TYPE="linux_raid_member" /dev/mmcblk0p1: LABEL="armbi_root" UUID="b790c4d7-5709-4000-91ac-099eeefxxxxx" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="188abe42-01" /dev/sdc: UUID="29f2832b-d95d-3e76-0375-3b2b0fxxxxx" UUID_SUB="dbef45c4-9262-371c-fa47-b5efccc1b384" LABEL="helios64:0" TYPE="linux_raid_member" /dev/mmcblk1p1: UUID="e4d8315e-aeb2-4e95-becf-88aaed8xxxxx" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="f11f8806-01" /dev/sda1: UUID="902f758f-240c-4f5a-b802-5ab5d35xxxxx" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="0182fc84-01" /dev/zram1: LABEL="log2ram" UUID="299a178d-7269-46e4-988c-f691813xxxxx" BLOCK_SIZE="4096" TYPE="ext4" /dev/zram0: UUID="cab32334-75a4-4fda-b539-b17a55dxxxxx" TYPE="swap"

no WiFi Adapter after fresh installation. usbcore.autosuspend=-1 fixes it: ___ _ _ _ ____ ____ / _ \ __| |_ __ ___ (_) __| | / ___|___ \ | | | |/ _` | '__/ _ \| |/ _` | | | __) | | |_| | (_| | | | (_) | | (_| | | |___ / __/ \___/ \__,_|_| \___/|_|\__,_| \____|_____| Welcome to Armbian 24.2.1 Bookworm with Linux 6.6.16-current-meson64 System load: 46% Up time: 0 min Memory usage: 7% of 1.82G IP: 192.168.25.252 CPU temp: 28°C Usage of /: 66% of 3.0G [ Menu-driven system configuration (beta): sudo apt update && sudo apt install armbian-config ] root@odroid:~# cat /boot/armbianEnv.txt verbosity=1 console=both overlay_prefix=meson rootdev=UUID=1cf10f1a-aa21-4ff0-875d-c59f57c87173 rootfstype=ext4 extraboardargs=fastboot noswap isolcpus=3 usbcore.autosuspend=-1 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u root@odroid:~# lsusb Bus 001 Device 007: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T Bus 001 Device 006: ID 7392:7822 Edimax Technology Co., Ltd EW-7612UAn V2 802.11n Wireless Adapter [Realtek RTL8192CU] Bus 001 Device 005: ID 05e3:0610 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I am using the following script to transfer a system to another volume (in this case the running system to emmc) (UUIDs to be adapted to your case (sed -e 's/UUID=<from device>/UUID=<to device>/g' -i /mnt/emmc/etc/fstab) #!/bin/bash # Check if user is root if [ $(id -u) != "0" ]; then echo "Error: You must be root to run this script." exit 1 fi cat > install-exclude <<EOF /dev/* /proc/* /sys/* /run/* # /tmp/* # /root/* EOF exec 2>/dev/null umount /mnt/emmc exec 2>&1 mount --uuid 7268e76f-3e1b-4e01-a6be-987654321098 /mnt/emmc rsync -avxSE --delete --exclude-from="install-exclude" / /mnt/emmc # change fstab sed -e 's/UUID=b790c4d7-5709-4000-91ac-123456789012/UUID=7268e76f-3e1b-4e01-a6be-987654321098/g' -i /mnt/emmc/etc/fstab sed -e 's/UUID=b790c4d7-5709-4000-91ac-123456789012/UUID=7268e76f-3e1b-4e01-a6be-987654321098/g' -i /mnt/emmc/boot/armbianEnv.txt umount /mnt/emmc rm install-exclude echo "All done." On top of that you may wish to manually rsync /var/log and /var/log.hdd to the other device. The segmentation fault is probably caused by the wrong bootloader on emmc. Armbian tools might overwrite it. So install again the recommended bootloader to emmc. Good luck.

Hi everyone! I didn't expect this post to be active again after almost a year without replies, so thanks for the revival! After writing this "article," I stopped investigating the problem. However, the post being active again piqued my curiosity to see if the issue was resolved. Unfortunately, the problem persists on Armbian 23.11.1 (bookworm). I tried the same steps as before, but encountered a major issue. After recompiling and compiling the dts and rebooting, my device wouldn't boot anymore. It kept showing "UUID does not exist" (and I don't know why, so if anybody knows, please tell me). I really appreciate your efforts @usual user for providing the .dts, but I think the problem lies in the overlay file of Armbian, which seems to be out of date. It seems they forgot to update the overlay, as @robertoj mentioned that this isn't a problem in the boot process; the original dts that boots on the OPi 3 LTS is correct. I followed the same steps as before: sudo armbian-config -> System -> Dtc, and in the spi@5011000 section, they updated the phandle of the pins. spi1-pins { pins = "PH4\0PH5\0PH6"; function = "spi1"; phandle = <0x32>; }; spi1-cs-pin { pins = "PH3"; function = "spi1"; phandle = <0x33>; }; But when we checked the sun50i-h6-spi-spidev1.dtbo, it remained the same. fragment@1 { target = <0xffffffff>; __overlay__ { pinctrl-names = "default"; pinctrl-0 = <0xffffffff>; status = "okay"; #address-cells = <0x01>; #size-cells = <0x00>; spidev@0 { compatible = "armbian,spi-dev"; reg = <0x00>; spi-max-frequency = <0xf4240>; }; }; }; Notice that the "pinctrl-0" is <0xffffffff>, which seems more like a placeholder than a real id of a node. The problem here is that we have a working device tree in the system, but when I activate the overlay using overlays=spi-spidev1 in /boot/armbianEnv.txt, it overwrites the correct dts and puts the wrong node id. Before adding the overlay in your boot config, you can check this by going to /sys/firmware/devicetree/base/soc/spi@5011000 and using cat on pinctrl-0: $> /sys/firmware/devicetree/base/soc/spi@5011000# cat pinctrl-0 23 What are these 2 and 3? If we look at the original device tree source, it's pinctrl-0 = <0x32 0x33>;, where 32 refers to the node spi1-pins and 33 to spi1-cs-pin. By using an ASCII to hex converter, we find that 2 corresponds to 0x32 and 3 to 0x33. You can also confirm which pins are assigned to these IDs by: $> /sys/firmware/devicetree/base/soc/pinctrl@300b000/spi1-pins# cat phandle 2 $> /sys/firmware/devicetree/base/soc/pinctrl@300b000/spi1-cs-pin# cat phandle 3 So, what happens when we add the overlay? /sys/firmware/devicetree/base/soc/spi@5011000# cat pinctrl-0 2 We see that we have 2 (MOSI.1, MISO.1, and SCLK.1) but not 3 (CE.1). In other words, we don't have CE.1 activated as WiringOP showed us. But how can I simply fix that, given that (at least to me) recompiling and compiling aren't working more? It's simple: Copy the spidev@0 part from the overlay. Access sudo armbian-config -> System -> Dtc and find spi@5011000. Put the spidev@0 inside it and set the status of this node to "okay" instead of "disabled". The final result will be: spi@5011000 { compatible = "allwinner,sun50i-h6-spi\0allwinner,sun8i-h3-spi"; reg = <0x5011000 0x1000>; interrupts = <0x00 0x0b 0x04>; clocks = <0x06 0x53 0x06 0x51>; clock-names = "ahb\0mod"; dmas = <0x2f 0x17 0x2f 0x17>; dma-names = "rx\0tx"; pinctrl-names = "default"; pinctrl-0 = <0x32 0x33>; resets = <0x06 0x20>; status = "okay"; #address-cells = <0x01>; #size-cells = <0x00>; phandle = <0x7a>; spidev@0 { compatible = "armbian,spi-dev"; reg = <0x00>; spi-max-frequency = <0xf4240>; }; }; Save the modifications and now use this command to remove the wrong overlay: $> cd /boot/dtb/allwinner/overlay/ $> mv sun50i-h6-spi-spidev1.dtbo .sun50i-h6-spi-spidev1.dtbo After the reboot, you'll see: $> ls /dev/ | grep spi spidev0.0 Using gpio readall: $> sudo gpio readall +------+-----+----------+--------+---+ OPi 3 +---+--------+----------+-----+------+ | GPIO | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | GPIO | +------+-----+----------+--------+---+----++----+---+--------+----------+-----+------+ | | | 3.3V | | | 1 || 2 | | | 5V | | | | 122 | 0 | SDA.0 | OFF | 0 | 3 || 4 | | | 5V | | | | 121 | 1 | SCL.0 | OFF | 0 | 5 || 6 | | | GND | | | | 118 | 2 | PWM.0 | OFF | 0 | 7 || 8 | 0 | OFF | PL02 | 3 | 354 | | | | GND | | | 9 || 10 | 0 | OFF | PL03 | 4 | 355 | | 120 | 5 | RXD.3 | OFF | 0 | 11 || 12 | 0 | OFF | PD18 | 6 | 114 | | 119 | 7 | TXD.3 | OFF | 0 | 13 || 14 | | | GND | | | | 362 | 8 | PL10 | OFF | 0 | 15 || 16 | 0 | OFF | PD15 | 9 | 111 | | | | 3.3V | | | 17 || 18 | 0 | OFF | PD16 | 10 | 112 | | 229 | 11 | MOSI.1 | ALT2 | 0 | 19 || 20 | | | GND | | | | 230 | 12 | MISO.1 | ALT2 | 0 | 21 || 22 | 0 | OFF | PD21 | 13 | 117 | | 228 | 14 | SCLK.1 | ALT2 | 0 | 23 || 24 | 0 | ALT2 | CE.1 | 15 | 227 | | | | GND | | | 25 || 26 | 0 | OFF | PL08 | 16 | 360 | +------+-----+----------+--------+---+----++----+---+--------+----------+-----+------+ | GPIO | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | GPIO | +------+-----+----------+--------+---+ OPi 3 +---+--------+----------+-----+------+ You should see CE.1 working. Now, use spidev-test to see if SPI is working: $> ./spidev_test -v -D /dev/spidev0.0 spi mode: 0x0 bits per word: 8 max speed: 500000 Hz (500 KHz) TX | FF FF FF FF FF FF 40 00 00 00 00 95 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@.... .................. . RX | FF FF FF FF FF FF 40 00 00 00 00 95 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@.... .................. . It's working! In the end, it seems that the overlay is incorrect (perhaps someone forgot to remove or update the "pinctrl-0 = <0xffffffff>") and needs to be updated. I don't know if the solution I created is the best way, but it's working in the recent images. If anyone has a hint to improve this solution or knows why I'm getting "UUID does not exist" when I recompile my .dtbo file, please let me know to improve my knowledge PS: You don't need to remove the overlay if you didn't add it to your armbianEnv.txt.

@Joel @amazingfate Just tried the 6.1 image (Armbian_24.2.4_Orangepi5-plus_jammy_vendor_6.1.43_kde-neon-amazingfated_desktop.img.xz) and installed to the NVME (with only 1 ext4 partition) with armbian-install. Initially it didn't boot, there are no files in /boot. After copying the files from the boot partition of the SD-card to the /boot folder of the NVME and changing the UUID in armbianEnv.txt to the UUID of the NVME it boots.

What device ${entire-device-to-be-used}. Do i put here /dev/zram1: LABEL="log2ram" UUID="f669e3f4-c37a-47e0-9427-9839ee24afeb" BLOCK_SIZE="4096" TYPE="ext4" /dev/mmcblk1p1: LABEL="armbi_root" UUID="de04b6b8-a4ac-493b-bee1-92d2eaff5ff0" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="586ce220-01" /dev/zram0: UUID="9a68dd65-2939-47d0-a8a7-cb19f1afe9d8" TYPE="swap" /dev/sda is externe ubs its pluged out otherwise no boot

Nicely done! Yes, I would encourage you to customize variables and bootcmd to suit your specific purpose and avoid using the confusing and bloated scripts/commands that are often found in the default settings. Yes, you are right, boot.scr overwrites the root kernel parameter. Do you know if you were using UUID before to boot? I've found the /dev names to be stable especially if it's mmc. There is the possibility for problems if you use both USB and SATA drives for example, but unless that is your case I would probably just use the /dev device name. Arch Linux ARM has some much simpler u-boot settings you could probably use/adapt for your situation: https://github.com/archlinuxarm/PKGBUILDs/blob/master/alarm/uboot-espressobin/uEnv.txt By default u-boot runs the value of bootcmd. So for example, a simpler approach like this could work for you: get_images=ext4load mmc 0:1 $kernel_addr_r boot/Image && ext4load mmc 0:1 $fdt_addr_r boot/${fdt_name} get_ramdisk=ext4load mmc 0:1 $initrd_addr boot/uInitrd bootargs=console=ttyMV0,115200 earlycon=ar3700_uart,0xd0012000 root=/dev/mmcblk0p1 rw rootwait bootcmd=mmc dev 0; if run get_images; then if run get_ramdisk; then booti $kernel_addr_r $initrd_addr $fdt_addr_r; else booti $kernel_addr_r - $fdt_addr_r; fi; fi Saving the values you want (and that you have confirmed work) to permanent storage with saveenv will then bypass boor.scr and armbianEnv.txt entirely. Be warned that this does have tradeoffs though because if Armbian developers decide they want to change the location/name of the kernel (for example) or any of the other values you have coded into a u-boot environment variable then a simple upgrade could mean boot fails again until you go and figure out what was done. Having seen how Arch does things and here how Armbian does things for these devices, my opinion is that both are super clunky. Modern U-Boot supports EFI stub booting so that's the approach I use. The result is: => printenv arch=arm baudrate=115200 board=mvebu_armada-37xx board_name=mvebu_armada-37xx bootcmd=bootflow scan bootdelay=2 cpu=armv8 ethact=ethernet@30000 ethprime=eth0 fdt_addr_r=0x6f00000 fdtcontroladdr=3faf8900 filesize=722 kernel_addr_r=0x7000000 loadaddr=0x6000000 netdev=eth0 pcb_rev=1.2.0 pcb_sn=CPE-2247-000050 ramdisk_addr_r=0xb000000 soc=mvebu stderr=serial@12000 stdin=serial@12000 stdout=serial@12000 vendor=Marvell and then I can use systemd-boot (or GRUB or whatever) to manage where kernels get installed, which get booted, etc. I wanted to be able to update the device kernel remotely (without having to use the USB console). Needing to change u-boot settings at all is problematic for that situation. With EFI boot there's also no need to load an initramfs nor a device tree to memory either, though there can be use cases (e.g. full disk encryption) where you would still need an initramfs.

Now I installed it from official sources and inserted in a linux machine to modify the extlinux.conf file. But it say problem with the history. I am copying the file content from the previous file that was open in my notepad. Does the root=UUID=UUID-number-here would be the same as the one from unofficial sources of the armbian? Or how can I find the actual UUID?

The image contain in the boot/ directory: Marvell >> ls mmc 0:1 boot/ <DIR> 4096 . <DIR> 4096 .. <SYM> 32 Image <SYM> 28 dtb <DIR> 4096 dtb-5.15.149-current-mvebu64 38518 boot.bmp 0 .next <SYM> 32 uInitrd 1592 boot.cmd 4198770 System.map-5.15.149-current-mvebu64 95 armbianEnv.txt 1536 armbian_first_run.txt.template 1664 boot.scr 9681576 uInitrd-5.15.149-current-mvebu64 193310 config-5.15.149-current-mvebu64 21899776 vmlinuz-5.15.149-current-mvebu64 9681512 initrd.img-5.15.149-current-mvebu64 <SYM> 39 fdt.dtb 16578860 espressobin.itb and the content of armbianEnv.txt is board_version=v5 verbosity=1 rootdev=UUID=eb19bd31-6e1d-40ca-b936-d2823be614de rootfstype=ext4 The boot.cmd or boot.scr is "# Some tests to try to keep compatibility with old variables if test -z "${kernel_addr_r}"; then setenv kernel_addr_r $kernel_addr fi if test -z "${ramdisk_addr_r}"; then setenv ramdisk_addr_r $initrd_addr fi if test -z "${fdt_addr_r}"; then setenv fdt_addr_r $fdt_addr fi if test -z "${distro_bootpart}"; then setenv distro_bootpart 1 fi if test -z "${devtype}"; then setenv devtype $boot_interface fi load ${devtype} ${devnum}:${distro_bootpart} ${scriptaddr} ${prefix}armbianEnv.txt env import -t ${scriptaddr} ${filesize} setenv bootargs "$console root=${rootdev} rootfstype=${rootfstype} rootwait loglevel=${verbosity} usb-storage.quirks=${usbstoragequirks} ${extraargs}" load $devtype ${devnum}:${distro_bootpart} $ramdisk_addr_r ${prefix}espressobin.itb bootm ${ramdisk_addr_r}#$board_version # fallback to non-FIT image if test -z "${image_name}"; then setenv image_name "Image" fi if test -z "${initrd_image}"; then setenv initrd_image "uInitrd" fi if test -z "${fdt_name}"; then if test -z "${fdtfile}"; then setenv fdt_name "dtb/marvell/armada-3720-espressobin.dtb" else setenv fdt_name "dtb/$fdtfile" fi fi load $devtype ${devnum}:$distro_bootpart $kernel_addr_r ${prefix}$image_name load $devtype ${devnum}:$distro_bootpart $ramdisk_addr_r ${prefix}$initrd_image load $devtype ${devnum}:$distro_bootpart $fdt_addr_r ${prefix}$fdt_name booti $kernel_addr_r $ramdisk_addr_r $fdt_addr_r # mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr When trying to load in memory boot.scr and source it it fails, so to locate the problem I rather walk through the script step by step. I can load espressobin.itb: Marvell>> load $devtype ${devnum}:${distro_bootpart} $ramdisk_addr_r ${prefix}espressobin.itb 16578860 bytes read in 730 ms (21.7 MiB/s) but when trying to boot: Marvell>> bootm ${ramdisk_addr_r}#$board_version Wrong Image Format for bootm command ERROR: can't get kernel image! I don't understand why I get this wrong image format. The following fallback script does not work either, everything go well until the booti command then Marvell>> booti $kernel_addr_r $ramdisk_addr_r $fdt_addr_r ## Loading init Ramdisk from Legacy Image at 08000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 9681512 Bytes = 9.2 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 06f00000 Booting using the fdt blob at 0x6f00000 Loading Ramdisk to 7ecf0000, end 7f62ba68 ... OK Using Device Tree in place at 0000000006f00000, end 0000000006f05d61 Starting kernel ... "Synchronous Abort" handler, esr 0x02000000

Nice to know about your fork of globalscale boot loader, I may go further deeper in your project later on. For today I have no longer access to my board, I will post tomorrow the two files. For specifying the device the ArmbianEnv.txt use an UUID, so it does not dépend of the location of the device.

When I run the Linux kernel on the Odroid XU4 board, it enters a loop with this error during boot: U-Boot 2017.05-00008-g6a9ddb8303-dirty (May 19 2020 - 19:48:01 +0900) for ODROID-XU4 CPU: Exynos5422 @ 800 MHz Model: Odroid XU4 based on EXYNOS5422 Board: Odroid XU4 based on EXYNOS5422 Type: xu4 DRAM: 2 GiB MMC: EXYNOS DWMMC: 0, EXYNOS DWMMC: 1 MMC Device 0 ( SD ): 29.7 GiB mmc_init: -5, time 4 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: No ethernet found. Press quickly 'Enter' twice to stop autoboot: 0 reading /boot.ini 2401 bytes read in 4 ms (585.9 KiB/s) ## Executing script at 43e00000 reading config.ini 6911 bytes read in 5 ms (1.3 MiB/s) ini: Imported macaddr as 00:1e:06:61:7a:39 ini: Imported vout as hdmi ini: Imported HPD as true ini: Imported cecenable as false ini: Imported disable_vu7 as false ini: Imported ddr_freq as 825 ini: Imported overlay_resize as 16384 ini: Imported overlay_profile as ini: Imported overlays as spi0 i2c0 i2c1 uart0 No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! reading zImage 7299952 bytes read in 490 ms (14.2 MiB/s) reading exynos5422-odroidxu4.dtb 88559 bytes read in 11 ms (7.7 MiB/s) reading overlays/spi0.dtbo 691 bytes read in 5 ms (134.8 KiB/s) reading overlays/i2c0.dtbo 224 bytes read in 5 ms (43 KiB/s) reading overlays/i2c1.dtbo 226 bytes read in 5 ms (43.9 KiB/s) reading overlays/uart0.dtbo 227 bytes read in 6 ms (36.1 KiB/s) Kernel image @ 0x40008000 [ 0x000000 - 0x6f6370 ] ## Flattened Device Tree blob at 44000000 Booting using the fdt blob at 0x44000000 reserving fdt memory region: addr=44000000 size=2c000 Using Device Tree in place at 44000000, end 4402efff Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x100 [ 0.000000] Linux version 6.1.77+ (odroid@odroid) (gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #1 SMP PREEMPT Wed Mar 6 17:56:35 -03 2024 [ 0.000000] CPU: ARMv7 Processor [410fc073] revision 3 (ARMv7), cr=30c5387d [ 0.000000] CPU: div instructions available: patching division code [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] OF: fdt: Machine model: Hardkernel ODROID XU4 [ 0.000000] Memory policy: Data cache writealloc [ 0.000000] cma: Reserved 128 MiB at 0x00000000b6800000 [ 0.000000] Samsung CPU ID: 0xe5422001 [ 0.000000] Zone ranges: [ 0.000000] Normal [mem 0x0000000040000000-0x000000006fffffff] [ 0.000000] HighMem [mem 0x0000000070000000-0x00000000be9fffff] [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x0000000040000000-0x00000000be9fffff] [ 0.000000] Initmem setup node 0 [mem 0x0000000040000000-0x00000000be9fffff] [ 0.000000] Running under secure firmware. [ 0.000000] percpu: Embedded 17 pages/cpu s39124 r8192 d22316 u69632 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 516928 [ 0.000000] Kernel command line: console=tty1 console=ttySAC2,115200n8 root=UUID=e139ce78-9841-40fe-8823-96a304a09859 rootwait ro fsck.repair=yes net.ifnames=0 HPD=true vout=hdmi e [ 0.000000] hdmi: using HDMI mode [ 0.000000] Unknown kernel command line parameters "false HPD=true vout=hdmi", will be passed to user space. [ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes, linear) [ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes, linear) [ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off [ 0.000000] Memory: 1903668K/2074624K available (12288K kernel code, 1139K rwdata, 2940K rodata, 2048K init, 363K bss, 39884K reserved, 131072K cma-reserved, 1157120K highmem) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1 [ 0.000000] trace event string verifier disabled [ 0.000000] rcu: Preemptible hierarchical RCU implementation. [ 0.000000] Trampoline variant of Tasks RCU enabled. [ 0.000000] Tracing variant of Tasks RCU enabled. [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies. [ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16 [ 0.000000] GIC: Using split EOI/Deactivate mode [ 0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention. [ 0.000000] Switching to timer-based delay loop, resolution 41ns [ 0.000000] clocksource: mct-frc: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns [ 0.000002] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns [ 0.000032] genirq: irq_chip COMBINER did not update eff. affinity mask of irq 57 [ 0.001509] arch_timer: cp15 timer(s) running at 24.00MHz (phys). [ 0.001535] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns [ 0.001555] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns [ 0.001572] Ignoring duplicate/late registration of read_current_timer delay [ 0.002351] Console: colour dummy device 80x30 [ 0.003109] printk: console [tty1] enabled [ 0.003176] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=240000) [ 0.003223] CPU: Testing write buffer coherency: ok [ 0.003313] pid_max: default: 32768 minimum: 301 [ 0.003464] LSM: Security Framework initializing [ 0.003658] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes, linear) [ 0.003711] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes, linear) [ 0.005467] CPU0: thread -1, cpu 0, socket 1, mpidr 80000100 [ 0.006882] cblist_init_generic: Setting adjustable number of callback queues. [ 0.006928] cblist_init_generic: Setting shift to 3 and lim to 1. [ 0.007116] cblist_init_generic: Setting adjustable number of callback queues. [ 0.007151] cblist_init_generic: Setting shift to 3 and lim to 1. [ 0.007359] Setting up static identity map for 0x40200000 - 0x40200060 [ 0.007711] ARM CCI driver probed [ 0.008305] Exynos MCPM support installed [ 0.008707] rcu: Hierarchical SRCU implementation. [ 0.008734] rcu: Max phase no-delay instances is 1000. [ 0.010012] smp: Bringing up secondary CPUs ... [ 0.011171] CPU1: thread -1, cpu 1, socket 1, mpidr 80000101 [ 0.012478] CPU2: thread -1, cpu 2, socket 1, mpidr 80000102 [ 0.013707] CPU3: thread -1, cpu 3, socket 1, mpidr 80000103 [ 0.014902] CPU4: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.014919] CPU4: detected I-Cache line size mismatch, workaround enabled [ 0.014927] CPU4: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable [ 0.015018] CPU4: Spectre BHB: enabling loop workaround for all CPUs [ 0.016286] CPU5: thread -1, cpu 1, socket 0, mpidr 80000001 [ 0.016300] CPU5: detected I-Cache line size mismatch, workaround enabled [ 0.016307] CPU5: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable [ 0.017624] CPU6: thread -1, cpu 2, socket 0, mpidr 80000002 [ 0.017638] CPU6: detected I-Cache line size mismatch, workaround enabled [ 0.017645] CPU6: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable [ 0.018922] CPU7: thread -1, cpu 3, socket 0, mpidr 80000003 [ 0.018937] CPU7: detected I-Cache line size mismatch, workaround enabled [ 0.018945] CPU7: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable [ 0.019180] smp: Brought up 1 node, 8 CPUs [ 0.019244] SMP: Total of 8 processors activated (384.00 BogoMIPS). [ 0.019276] CPU: All CPU(s) started in HYP mode. [ 0.019297] CPU: Virtualization extensions available. [ 0.020752] devtmpfs: initialized [ 0.042523] VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0 [ 0.042807] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns [ 0.042850] futex hash table entries: 2048 (order: 5, 131072 bytes, linear) [ 0.045974] pinctrl core: initialized pinctrl subsystem [ 0.048866] NET: Registered PF_NETLINK/PF_ROUTE protocol family [ 0.052562] DMA: preallocated 2048 KiB pool for atomic coherent allocations [ 0.054296] audit: initializing netlink subsys (disabled) [ 0.054571] audit: type=2000 audit(0.050:1): state=initialized audit_enabled=0 res=1 [ 0.055157] thermal_sys: Registered thermal governor 'step_wise' [ 0.055436] cpuidle: using governor menu [ 0.055910] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers. [ 0.055941] hw-breakpoint: maximum watchpoint size is 8 bytes. [ 0.185987] EXYNOS5420 PMU initialized [ 0.292725] kprobes: kprobe jump-optimization is enabled. All kprobes are optimized if possible. [ 0.294707] fbcon: Taking over console [ 0.296476] iommu: Default domain type: Translated [ 0.296501] iommu: DMA domain TLB invalidation policy: lazy mode [ 0.296909] usbcore: registered new interface driver usbfs [ 0.296979] usbcore: registered new interface driver hub [ 0.297050] usbcore: registered new device driver usb [ 0.297807] s3c-i2c 12c70000.i2c: slave address 0x00 [ 0.297837] s3c-i2c 12c70000.i2c: bus frequency set to 378 KHz [ 0.298170] s3c-i2c 12c70000.i2c: i2c-0: S3C I2C adapter [ 0.298383] s3c-i2c 12c80000.i2c: slave address 0x00 [ 0.298412] s3c-i2c 12c80000.i2c: bus frequency set to 65 KHz [ 0.298719] s3c-i2c 12c80000.i2c: i2c-2: S3C I2C adapter [ 0.299209] mc: Linux media interface: v0.10 [ 0.299295] videodev: Linux video capture interface: v2.00 [ 0.299921] Advanced Linux Sound Architecture Driver Initialized. [ 0.301010] clocksource: Switched to clocksource mct-frc [ 0.301481] VFS: Disk quotas dquot_6.6.0 [ 0.301559] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 0.315803] NET: Registered PF_INET protocol family [ 0.316073] IP idents hash table entries: 16384 (order: 5, 131072 bytes, linear) [ 0.317886] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear) [ 0.317937] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear) [ 0.318036] TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear) [ 0.318132] TCP bind hash table entries: 8192 (order: 5, 131072 bytes, linear) [ 0.318434] TCP: Hash tables configured (established 8192 bind 8192) [ 0.318557] UDP hash table entries: 512 (order: 2, 16384 bytes, linear) [ 0.318617] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear) [ 0.318871] NET: Registered PF_UNIX/PF_LOCAL protocol family [ 0.318931] NET: Registered PF_XDP protocol family [ 0.320817] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 5 counters available [ 0.322010] hw perfevents: enabled with armv7_cortex_a15 PMU driver, 7 counters available [ 0.324097] Initialise system trusted keyrings [ 0.324437] workingset: timestamp_bits=14 max_order=19 bucket_order=5 [ 0.333908] romfs: ROMFS MTD (C) 2007 Red Hat, Inc. [ 0.421548] NET: Registered PF_ALG protocol family [ 0.421584] Key type asymmetric registered [ 0.421605] Asymmetric key parser 'x509' registered [ 0.421839] bounce: pool size: 64 pages [ 0.421992] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247) [ 0.422397] io scheduler mq-deadline registered [ 0.422425] io scheduler kyber registered [ 0.422681] io scheduler bfq registered [ 0.424520] samsung-pinctrl 13400000.pinctrl: Failed to create device link (0x180) with soc [ 0.426837] samsung-usb2-phy 12130000.phy: supply vbus not found, using dummy regulator [ 0.427839] exynos5_usb3drd_phy 12100000.phy: supply vbus not found, using dummy regulator [ 0.428032] exynos5_usb3drd_phy 12100000.phy: supply vbus-boost not found, using dummy regulator [ 0.428460] exynos5_usb3drd_phy 12500000.phy: supply vbus not found, using dummy regulator [ 0.428634] exynos5_usb3drd_phy 12500000.phy: supply vbus-boost not found, using dummy regulator [ 0.436864] dma-pl330 3880000.dma-controller: Loaded driver for PL330 DMAC-241330 [ 0.436898] dma-pl330 3880000.dma-controller: DBUFF-4x8bytes Num_Chans-6 Num_Peri-16 Num_Events-6 [ 0.439976] dma-pl330 121a0000.dma-controller: Loaded driver for PL330 DMAC-241330 [ 0.440008] dma-pl330 121a0000.dma-controller: DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32 [ 0.443083] dma-pl330 121b0000.dma-controller: Loaded driver for PL330 DMAC-241330 [ 0.443116] dma-pl330 121b0000.dma-controller: DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32 [ 0.444270] dma-pl330 10800000.dma-controller: Loaded driver for PL330 DMAC-241330 [ 0.444300] dma-pl330 10800000.dma-controller: DBUFF-64x8bytes Num_Chans-8 Num_Peri-1 Num_Events-32 [ 0.461998] dma-pl330 3880000.dma-controller: PM domain MAU will not be powered off [ 0.533568] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [ 0.536218] 12c00000.serial: ttySAC0 at MMIO 0x12c00000 (irq = 124, base_baud = 0) is a S3C6400/10 [ 0.536771] 12c20000.serial: ttySAC2 at MMIO 0x12c20000 (irq = 125, base_baud = 0) is a S3C6400/10 [ 1.553526] printk: console [ttySAC2] enabled [ 1.560131] exynos-trng 10830600.rng: Exynos True Random Number Generator. [ 1.567245] exynos-mixer 14450000.mixer: Adding to iommu group 0 [ 1.574772] exynos-drm-g2d 10850000.g2d: Adding to iommu group 1 [ 1.581147] exynos-rotator 11c00000.rotator: Adding to iommu group 2 [ 1.587248] exynos-scaler 12800000.scaler: Adding to iommu group 3 [ 1.593888] exynos-scaler 12810000.scaler: Adding to iommu group 4 [ 1.600295] exynos-scaler 12820000.scaler: Adding to iommu group 5 [ 1.607009] exynos-drm-gsc 13e00000.video-scaler: Adding to iommu group 6 [ 1.613211] exynos-drm-gsc 13e00000.video-scaler: drm gsc registered successfully. [ 1.620298] exynos-drm-gsc 13e10000.video-scaler: Adding to iommu group 7 [ 1.627466] exynos-drm-gsc 13e10000.video-scaler: drm gsc registered successfully. [ 1.652020] brd: module loaded [ 1.654773] usbcore: registered new device driver r8152-cfgselector [ 1.659902] usbcore: registered new interface driver r8152 [ 1.665405] usbcore: registered new interface driver cdc_ether [ 1.671186] usbcore: registered new interface driver cdc_subset [ 1.677065] usbcore: registered new interface driver r8153_ecm [ 1.685749] phy phy-12130000.phy.6: phy_power_on was called before phy_init [ 1.691276] exynos-ehci 12110000.usb: EHCI Host Controller [ 1.696714] exynos-ehci 12110000.usb: new USB bus registered, assigned bus number 1 [ 1.704845] exynos-ehci 12110000.usb: irq 133, io mem 0x12110000 [ 1.731064] exynos-ehci 12110000.usb: USB 2.0 started, EHCI 1.00 [ 1.735818] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01 [ 1.743876] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.751068] usb usb1: Product: EHCI Host Controller [ 1.755880] usb usb1: Manufacturer: Linux 6.1.77+ ehci_hcd [ 1.761370] usb usb1: SerialNumber: 12110000.usb [ 1.766665] hub 1-0:1.0: USB hub found [ 1.769693] hub 1-0:1.0: 3 ports detected [ 1.774988] phy phy-12130000.phy.6: phy_power_on was called before phy_init [ 1.780583] exynos-ohci 12120000.usb: USB Host Controller [ 1.786000] exynos-ohci 12120000.usb: new USB bus registered, assigned bus number 2 [ 1.793806] exynos-ohci 12120000.usb: irq 133, io mem 0x12120000 [ 1.865293] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 6.01 [ 1.872132] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.879280] usb usb2: Product: USB Host Controller [ 1.884074] usb usb2: Manufacturer: Linux 6.1.77+ ohci_hcd [ 1.889502] usb usb2: SerialNumber: 12120000.usb [ 1.894774] hub 2-0:1.0: USB hub found [ 1.897855] hub 2-0:1.0: 3 ports detected [ 1.904077] UDC core: dbgp: couldn't find an available UDC [ 1.908531] mousedev: PS/2 mouse device common for all mice [ 1.915382] i2c_dev: i2c /dev entries driver [ 1.943247] vdd_ldo9: Bringing 3300000uV into 3000000-3000000uV [ 1.960292] vddq_mmc2: Bringing 3300000uV into 2800000-2800000uV [ 1.979785] vdd_sd: Bringing 3300000uV into 2800000-2800000uV [ 2.049199] s5m-rtc s2mps14-rtc: registered as rtc0 [ 2.054487] s5m-rtc s2mps14-rtc: setting system clock to 2000-01-01T00:00:08 UTC (946684808) [ 2.061844] s2mps11-clk s2mps11-clk: DMA mask not set [ 2.076557] exynos-tmu 10060000.tmu: More trip points than supported by this TMU. [ 2.082622] exynos-tmu 10060000.tmu: 2 trip points should be configured in polling mode. [ 2.092426] exynos-tmu 10064000.tmu: More trip points than supported by this TMU. [ 2.098440] exynos-tmu 10064000.tmu: 2 trip points should be configured in polling mode. [ 2.108348] exynos-tmu 10068000.tmu: More trip points than supported by this TMU. [ 2.114407] exynos-tmu 10068000.tmu: 2 trip points should be configured in polling mode. [ 2.124320] exynos-tmu 1006c000.tmu: More trip points than supported by this TMU. [ 2.130338] exynos-tmu 1006c000.tmu: 2 trip points should be configured in polling mode. [ 2.140250] exynos-tmu 100a0000.tmu: More trip points than supported by this TMU. [ 2.146302] exynos-tmu 100a0000.tmu: 6 trip points should be configured in polling mode. [ 2.155544] s3c2410-wdt 101d0000.watchdog: watchdog inactive, reset disabled, irq disabled [ 2.163331] device-mapper: uevent: version 1.0.3 [ 2.167537] device-mapper: ioctl: 4.47.0-ioctl (2022-07-28) initialised: dm-devel@redhat.com [ 2.191451] sdhci: Secure Digital Host Controller Interface driver [ 2.196199] sdhci: Copyright(c) Pierre Ossman [ 2.201064] Synopsys Designware Multimedia Card Interface Driver [ 2.208067] dwmmc_exynos 12220000.mmc: IDMAC supports 32-bit address mode. [ 2.208115] dwmmc_exynos 12200000.mmc: IDMAC supports 32-bit address mode. [ 2.220477] dwmmc_exynos 12220000.mmc: Using internal DMA controller. [ 2.224492] s5p-secss 10830000.sss: s5p-sss driver registered [ 2.226796] dwmmc_exynos 12220000.mmc: Version ID is 250a [ 2.232750] dwmmc_exynos 12200000.mmc: Using internal DMA controller. [ 2.234102] hid: raw HID events driver (C) Jiri Kosina [ 2.238124] dwmmc_exynos 12220000.mmc: DW MMC controller at irq 144,64 bit host data width,64 deep fifo [ 2.244291] dwmmc_exynos 12200000.mmc: Version ID is 250a [ 2.264162] dwmmc_exynos 12200000.mmc: DW MMC controller at irq 145,64 bit host data width,64 deep fifo [ 2.268759] mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63) [ 2.275936] dwmmc_exynos 12200000.mmc: allocated mmc-pwrseq [ 2.292675] exynos-nocp: new NoC Probe device registered: 10ca1000.nocp [ 2.297970] exynos-nocp: new NoC Probe device registered: 10ca1400.nocp [ 2.304571] exynos-nocp: new NoC Probe device registered: 10ca1800.nocp [ 2.305514] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63) [ 2.312086] exynos-nocp: new NoC Probe device registered: 10ca1c00.nocp [ 2.327451] exynos-ppmu: new PPMU device registered 10d00000.ppmu (ppmu-event3-dmc0-0) [ 2.335102] exynos-ppmu: new PPMU device registered 10d10000.ppmu (ppmu-event3-dmc0-1) [ 2.342974] exynos-ppmu: new PPMU device registered 10d60000.ppmu (ppmu-event3-dmc1-0) [ 2.350839] exynos-ppmu: new PPMU device registered 10d70000.ppmu (ppmu-event3-dmc1-1) [ 2.361081] exynos5-dmc 10c20000.memory-controller: error -ENXIO: IRQ drex_0 not found [ 2.367518] exynos5-dmc 10c20000.memory-controller: error -ENXIO: IRQ drex_1 not found [ 2.375591] exynos5-dmc 10c20000.memory-controller: DMC initialized, in irq mode: 0 [ 2.384755] mmc_host mmc0: Bus speed (slot 0) = 200000000Hz (slot req 200000000Hz, actual 200000000HZ div = 0) [ 2.394797] samsung-i2s 3830000.i2s-sec: DMA channels sourced from device 3830000.i2s [ 2.397011] mmc0: new ultra high speed SDR104 SDHC card at address aaaa [ 2.407340] NET: Registered PF_PACKET protocol family [ 2.409624] mmcblk0: mmc0:aaaa SE32G 29.7 GiB [ 2.412797] NET: Registered PF_KEY protocol family [ 2.422627] Key type dns_resolver registered [ 2.426187] mmcblk0: p1 p2 [ 2.426754] Registering SWP/SWPB emulation handler [ 2.434051] registered taskstats version 1 [ 2.437817] Loading compiled-in X.509 certificates [ 2.443116] Key type .fscrypt registered [ 2.446464] Key type fscrypt-provisioning registered [ 2.457336] Key type encrypted registered [ 2.588749] exynos-chipid 10000000.chipid: cpu0 opp0, freq: 1500 missing [ 2.594193] exynos-chipid 10000000.chipid: cpu4 opp0, freq: 2100 missing [ 2.600762] exynos-chipid 10000000.chipid: Exynos: CPU[EXYNOS5800] PRO_ID[0xe5422000] REV[0x1] Detected [ 2.617722] OF: graph: no port node found in /soc/hdmi@14530000 [ 2.624147] [drm] Exynos DRM: using 14450000.mixer device for DMA mapping operations [ 2.630520] exynos-drm exynos-drm: bound 14450000.mixer (ops 0xc0e7bc8c) [ 2.637165] exynos-drm exynos-drm: bound 14530000.hdmi (ops 0xc0e7c26c) [ 2.643884] exynos-drm-g2d 10850000.g2d: The Exynos G2D (ver 4.1) successfully registered. [ 2.651958] exynos-drm exynos-drm: bound 10850000.g2d (ops 0xc0e7d27c) [ 2.658441] exynos-rotator 11c00000.rotator: The exynos rotator has been probed successfully [ 2.666855] exynos-drm exynos-drm: bound 11c00000.rotator (ops 0xc0e7db08) [ 2.673723] exynos-scaler 12800000.scaler: The exynos scaler has been probed successfully [ 2.681842] exynos-drm exynos-drm: bound 12800000.scaler (ops 0xc0e7e250) [ 2.688607] exynos-scaler 12810000.scaler: The exynos scaler has been probed successfully [ 2.696755] exynos-drm exynos-drm: bound 12810000.scaler (ops 0xc0e7e250) [ 2.703526] exynos-scaler 12820000.scaler: The exynos scaler has been probed successfully [ 2.711662] exynos-drm exynos-drm: bound 12820000.scaler (ops 0xc0e7e250) [ 2.718396] exynos-drm-gsc 13e00000.video-scaler: The exynos gscaler has been probed successfully [ 2.727314] exynos-drm exynos-drm: bound 13e00000.video-scaler (ops 0xc0e7eb24) [ 2.734594] exynos-drm-gsc 13e10000.video-scaler: The exynos gscaler has been probed successfully [ 2.743425] exynos-drm exynos-drm: bound 13e10000.video-scaler (ops 0xc0e7eb24) [ 2.791131] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 300000Hz, actual 297619HZ div = 84) [ 2.838676] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 200000Hz, actual 200000HZ div = 125) [ 2.878753] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 100000Hz, actual 100000HZ div = 250) [ 2.907827] Console: switching to colour frame buffer device 180x56 [ 2.973325] exynos-drm exynos-drm: [drm] fb0: exynosdrmfb frame buffer device [ 2.984476] [drm] Initialized exynos 1.1.0 20180330 for exynos-drm on minor 0 [ 3.004351] mali 11800000.gpu: GPU identified as 0x0620 r0p1 status 0 [ 3.010719] mali 11800000.gpu: Protected mode not available [ 3.018316] mali 11800000.gpu: Probed as mali0 [ 3.026735] xhci-hcd xhci-hcd.8.auto: xHCI Host Controller [ 3.030849] xhci-hcd xhci-hcd.8.auto: new USB bus registered, assigned bus number 3 [ 3.039677] xhci-hcd xhci-hcd.8.auto: hcc params 0x0220f04c hci version 0x100 quirks 0x0000000002010010 [ 3.048138] xhci-hcd xhci-hcd.8.auto: irq 153, io mem 0x12000000 [ 3.054235] xhci-hcd xhci-hcd.8.auto: xHCI Host Controller [ 3.059294] xhci-hcd xhci-hcd.8.auto: new USB bus registered, assigned bus number 4 [ 3.066981] xhci-hcd xhci-hcd.8.auto: Host supports USB 3.0 SuperSpeed [ 3.073679] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01 [ 3.081733] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.088855] usb usb3: Product: xHCI Host Controller [ 3.093692] usb usb3: Manufacturer: Linux 6.1.77+ xhci-hcd [ 3.099147] usb usb3: SerialNumber: xhci-hcd.8.auto [ 3.105733] hub 3-0:1.0: USB hub found [ 3.108240] hub 3-0:1.0: 1 port detected [ 3.113412] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM. [ 3.120627] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.01 [ 3.128666] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.135843] usb usb4: Product: xHCI Host Controller [ 3.140461] usb usb4: Manufacturer: Linux 6.1.77+ xhci-hcd [ 3.148036] usb usb4: SerialNumber: xhci-hcd.8.auto [ 3.153685] hub 4-0:1.0: USB hub found [ 3.157741] hub 4-0:1.0: 1 port detected [ 3.169399] xhci-hcd xhci-hcd.9.auto: xHCI Host Controller [ 3.175224] xhci-hcd xhci-hcd.9.auto: new USB bus registered, assigned bus number 5 [ 3.183781] xhci-hcd xhci-hcd.9.auto: hcc params 0x0220f04c hci version 0x100 quirks 0x0000000002010010 [ 3.193572] xhci-hcd xhci-hcd.9.auto: irq 154, io mem 0x12400000 [ 3.200100] xhci-hcd xhci-hcd.9.auto: xHCI Host Controller [ 3.205886] xhci-hcd xhci-hcd.9.auto: new USB bus registered, assigned bus number 6 [ 3.213785] xhci-hcd xhci-hcd.9.auto: Host supports USB 3.0 SuperSpeed [ 3.220664] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01 [ 3.229213] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.236762] usb usb5: Product: xHCI Host Controller [ 3.241897] usb usb5: Manufacturer: Linux 6.1.77+ xhci-hcd [ 3.247575] usb usb5: SerialNumber: xhci-hcd.9.auto [ 3.253145] hub 5-0:1.0: USB hub found [ 3.257072] hub 5-0:1.0: 1 port detected [ 3.261543] usb usb6: We don't know the algorithms for LPM for this host, disabling LPM. [ 3.269904] usb usb6: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.01 [ 3.278421] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.285801] usb usb6: Product: xHCI Host Controller [ 3.290803] usb usb6: Manufacturer: Linux 6.1.77+ xhci-hcd [ 3.292505] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63) [ 3.294925] usb usb6: SerialNumber: xhci-hcd.9.auto [ 3.314476] hub 6-0:1.0: USB hub found [ 3.318373] hub 6-0:1.0: 1 port detected [ 3.324905] s3c-rtc 101e0000.rtc: rtc disabled, re-enabling [ 3.330709] s3c-rtc 101e0000.rtc: registered as rtc1 [ 3.340796] exynos-bus: new bus device registered: soc:bus-wcore ( 88700 KHz ~ 532000 KHz) [ 3.345656] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 300000Hz, actual 297619HZ div = 84) [ 3.348273] exynos-bus: new bus device registered: soc:bus-noc ( 66600 KHz ~ 111000 KHz) [ 3.370263] exynos-bus: new bus device registered: soc:bus-fsys-apb (111000 KHz ~ 222000 KHz) [ 3.379488] exynos-bus: new bus device registered: soc:bus-fsys2 ( 75000 KHz ~ 200000 KHz) [ 3.388608] exynos-bus: new bus device registered: soc:bus-mfc ( 83250 KHz ~ 333000 KHz) [ 3.397524] exynos-bus: new bus device registered: soc:bus-gen ( 88700 KHz ~ 266000 KHz) [ 3.406667] exynos-bus: new bus device registered: soc:bus-peri ( 66600 KHz ~ 66600 KHz) [ 3.411109] usb 3-1: new high-speed USB device number 2 using xhci-hcd [ 3.419851] exynos-bus: new bus device registered: soc:bus-g2d ( 83250 KHz ~ 333000 KHz) [ 3.431814] exynos-bus: new bus device registered: soc:bus-g2d-acp ( 66500 KHz ~ 266000 KHz) [ 3.440249] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 200000Hz, actual 200000HZ div = 125) [ 3.440969] exynos-bus: new bus device registered: soc:bus-jpeg ( 75000 KHz ~ 300000 KHz) [ 3.460397] exynos-bus: new bus device registered: soc:bus-jpeg-apb ( 83250 KHz ~ 166500 KHz) [ 3.469573] exynos-bus: new bus device registered: soc:bus-disp1-fimd (120000 KHz ~ 200000 KHz) [ 3.478997] exynos-bus: new bus device registered: soc:bus-disp1 (120000 KHz ~ 300000 KHz) [ 3.487932] exynos-bus: new bus device registered: soc:bus-gscl-scaler (150000 KHz ~ 300000 KHz) [ 3.497582] exynos-bus: new bus device registered: soc:bus-mscl ( 84000 KHz ~ 666000 KHz) [ 3.508589] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 100000Hz, actual 100000HZ div = 250) [ 3.535680] ALSA device list: [ 3.539420] #0: ODROID-XU4 [ 3.544075] Waiting for root device UUID=e139ce78-9841-40fe-8823-96a304a09859... [ 3.605856] usb 3-1: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice=22.23 [ 3.615230] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 3.623491] usb 3-1: Product: USB2.0 Hub [ 3.628491] usb 3-1: Manufacturer: GenesysLogic [ 3.682358] hub 3-1:1.0: USB hub found [ 3.689564] hub 3-1:1.0: 2 ports detected [ 3.751499] usb 4-1: new SuperSpeed USB device number 2 using xhci-hcd [ 3.794759] usb 4-1: New USB device found, idVendor=05e3, idProduct=0616, bcdDevice=22.23 [ 3.805887] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 3.815965] usb 4-1: Product: USB3.0 Hub [ 3.822775] usb 4-1: Manufacturer: GenesysLogic [ 3.858309] hub 4-1:1.0: USB hub found [ 3.863915] hub 4-1:1.0: 2 ports detected [ 4.061238] usb 3-1.1: new low-speed USB device number 3 using xhci-hcd [ 4.206144] usb 3-1.1: New USB device found, idVendor=046d, idProduct=c077, bcdDevice=72.00 [ 4.221958] usb 3-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 4.233307] usb 3-1.1: Product: USB Optical Mouse [ 4.238474] usb 3-1.1: Manufacturer: Logitech [ 4.371238] usb 6-1: new SuperSpeed USB device number 2 using xhci-hcd [ 4.391069] usb 3-1.2: new low-speed USB device number 4 using xhci-hcd [ 4.412822] usb 6-1: New USB device found, idVendor=0bda, idProduct=8153, bcdDevice=30.00 [ 4.422627] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [ 4.431336] usb 6-1: Product: USB 10/100/1000 LAN [ 4.437514] usb 6-1: Manufacturer: Realtek [ 4.443094] usb 6-1: SerialNumber: 000001000000 [ 4.536824] usb 3-1.2: New USB device found, idVendor=1a2c, idProduct=2d23, bcdDevice= 1.10 [ 4.549773] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 4.559722] usb 3-1.2: Product: USB Keyboard [ 4.564096] usb 3-1.2: Manufacturer: USB [ 4.677461] r8152-cfgselector 6-1: reset SuperSpeed USB device number 2 using xhci-hcd [ 4.733246] r8152 6-1:1.0: Direct firmware load for rtl_nic/rtl8153a-3.fw failed with error -2 [ 4.742982] r8152 6-1:1.0: unable to load firmware patch rtl_nic/rtl8153a-3.fw (-2) [ 4.793138] r8152 6-1:1.0 eth0: v1.12.13 [ 4.939315] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63) [ 5.000498] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 300000Hz, actual 297619HZ div = 84) [ 5.060339] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 200000Hz, actual 200000HZ div = 125) [ 5.119528] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 100000Hz, actual 100000HZ div = 250) [ 5.459354] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63) [ 5.522765] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 300000Hz, actual 297619HZ div = 84) [ 5.578951] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 200000Hz, actual 200000HZ div = 125) [ 5.635751] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 100000Hz, actual 100000HZ div = 250) [ 5.979379] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63) [ 6.042260] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 300000Hz, actual 297619HZ div = 84) [ 6.098485] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 200000Hz, actual 200000HZ div = 125) [ 6.157505] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 100000Hz, actual 100000HZ div = 250) [ 6.498761] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63) [ 6.556671] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 300000Hz, actual 297619HZ div = 84) [ 6.612113] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 200000Hz, actual 200000HZ div = 125) [ 6.668707] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 100000Hz, actual 100000HZ div = 250) [ 7.009370] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63) [ 7.070667] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 300000Hz, actual 297619HZ div = 84) [ 7.126100] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 200000Hz, actual 200000HZ div = 125) [ 7.183829] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 100000Hz, actual 100000HZ div = 250)

Hello .. I have tested both current release 24.2.1 (jammy and bookworm) on OPiZero, and usb otg not working .. on both .. Kernel is 6.6.20-current-sunxi module g_serial is loaded ttyGS0 exist serial-getty@ttyGS0.service is runing dtc overlays are usbhost0 - 3 ..all looks good on opizero side ... but on "computer side" not.. nothing happened when usb cable is plugged in .. no ttyAMC0 device was created .. no new usb hardware can be found in system log ... ..nothing.. Buster version works well... (my old installation) any advice ..? or it is any "actual kernel problem" .. ?? have somebody the same problem .. ??

Description When trying to build an image with FIXED_IMAGE_SIZE=3000 ROOTFS_TYPE=f2fs with WSL2 as build host, I stumbled on an error pretty late in the build process when trying to mount the rootfs: [💲|🌿] Creating rootfs [ f2fs on /dev/loop2p2 ] [💲|🔨] [💲|🔨] F2FS-tools: mkfs.f2fs Ver: 1.14.0 (2020-08-24) [💲|🔨] [💲|🔨] Info: Disable heap-based policy [💲|🔨] Info: Debug level = 0 [💲|🔨] Info: Label = armbi_root [💲|🔨] Info: Trim is enabled [💲|🔨] Info: Segments per section = 1 [💲|🔨] Info: Sections per zone = 1 [💲|🔨] Info: sector size = 512 [💲|🔨] Info: total sectors = 5586911 (2727 MB) [💲|🔨] Info: zone aligned segment0 blkaddr: 512 [💲|🔨] Info: format version with [💲|🔨] "Linux version 6.1.21.2-microsoft-standard-WSL2+ (flash@DESKTOP-2VA4T55) (gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #1 SMP Wed Jan 31 20:29:07 CET 2024" [💲|🔨] Info: [/dev/loop2p2] Discarding device [💲|🔨] Info: This device doesn't support BLKSECDISCARD [💲|🔨] Info: Discarded 2727 MB [💲|🔨] Info: Overprovision ratio = 3.860% [💲|🔨] Info: Overprovision segments = 108 (GC reserved = 59) [💲|🔨] Info: format successful [💲|🌿] Mounting rootfs [ /dev/loop2p2 (UUID=02dfb13e-172d-44b1-b71c-25164f29cc0b) ] [💲|🔨] mount: /home/user/build-fork/.tmp/mount-bfedd4e1-02f1-4bac-99c1-88d420d40809: unknown filesystem type 'f2fs'. [💲|💥] Error 32 occurred in main shell [ at /home/flash/build-fork/lib/functions/logging/runners.sh:211 run_host_command_logged_raw() --> lib/functions/logging/runners.sh:211 run_host_command_logged() --> lib/functions/logging/runners.sh:193 prepare_partitions() --> lib/functions/image/partitioning.sh:275 do_with_logging() --> lib/functions/logging/section-logging.sh:81 build_rootfs_and_image() --> lib/functions/main/rootfs-image.sh:86 full_build_packages_rootfs_and_image() --> lib/functions/main/default-build.sh:36 do_with_default_build() --> lib/functions/main/default-build.sh:42 cli_standard_build_run() --> lib/functions/cli/cli-build.sh:25 armbian_cli_run_command() --> lib/functions/cli/utils-cli.sh:136 cli_entrypoint() --> lib/functions/cli/entrypoint.sh:176 main() --> compile.sh:50 ] [💲|💥] Cleaning up [ please wait for cleanups to finish ] I found out that this is because the WSL2 kernel does not have support for the F2FS filesystem. f2fs-tools could be installed normally though. To make the build script exit at the beginning instead of at a late stage and to tell the user a more exact reason why it failed, I added a check if the chosen ROOTFS_TYPE is supported by the host the build script is running on. The check checks /proc/filesystems which should be present in all Linux distros. But just in case /proc/filesystems is not present, the build won't fail and instead print a warning that the build might fail just like if it can't install python2. How Has This Been Tested? Build host: Linux version 6.1.21.2-microsoft-standard-WSL2+ (no F2FS support, but BTRFS and EXT4 support) Command: ./compile.sh build BOARD=nanopi-r5c BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no KERNEL_CONFIGURE=no RELEASE=bookworm FIXED_IMAGE_SIZE=3000 ROOTFS_TYPE=f2fs [x] Ran build with FIXED_IMAGE_SIZE=3000 ROOTFS_TYPE=f2fs --> build exits at an early stage with [💲|💥] error! [ Filesystem type unsupported by build host: f2fs ] [x] Ran build with ROOTFS_TYPE=btrfs --> build success [x] Ran build without ROOTFS_TYPE option --> build success Might need some testing with other more exotic build hosts like Docker. Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [x] My changes generate no new warnings View the full article

cli: introduce inventory-boards cli command, for hopefully painless & useful one-board-per-line CSV output cli: introduce inventory-boards cli command, for hopefully painless & useful one-board-per-line CSV output inventory-boards-csv.py: moar Python atrocities done to data; idea here is to output one line per board, with <> for fields that, well, vary (mainly across BRANCH'es) inventory-boards sets TARGETS_FILE to something that doesn't exist, so the default-targets.yaml is used (so same list for everyone, save for userpatched-boards) View the full article

I think it's the other way around (MBR vs GPT). Using grub f.ex, with GPT you can have the boot partition wherever you want, as long as you define it with UUID, but it USUALLY is the first partition. With MBR this is not a choice EVEN if you use uefi, I think you MUST have the partition first (and leave 5MiB or smthn before the partition).

label Armbian_community kernel /Image initrd /uInitrd fdtdir /dtb/amlogic/meson-gxm-q200.dtb append root=UUID=212049b6-44a7-4741-9789-815d023561d0 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 I talked about it, I do not indicate this dtb, he takes from somewhere himself

@amazingfate Thank you, i'm sorry about my clumsiness... finally i could install the mali g610 firmware, but now 'startx' can't start: X.Org X Server 1.21.1.7 X Protocol Version 11, Revision 0 Current Operating System: Linux rock-5b 6.8.0-rc1-edge-rockchip-rk3588 #1 SMP PREEMPT Sun Jan 21 22:11:32 UTC 2024 aarch64 Kernel command line: root=UUID=fb37e203-0f28-4a83-8200-4d1b92192ca3 rootwait rootfstype=ext4 splash=verbose console=ttyS2,1500000 console=tty1 consoleblank=0 loglevel=1 ubootpart=dbfff1e9-1afa-704c-8661-c1a273d2de36 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 xorg-server 2:21.1.7-3+deb12u5 (https://www.debian.org/support) Current version of pixman: 0.42.2 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Sat Mar 2 15:45:43 2024 (==) Using config directory: "/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/share/X11/xorg.conf.d" free(): double free detected in tcache 2 (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x188) [0xaaaae1ffb7e8] (EE) unw_get_proc_info failed: no unwind info found [-10] (EE) (EE) Fatal server error: (EE) Caught signal 6 (Aborted). Server aborting (EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. (EE) (EE) Server terminated with error (1). Closing log file. i gave up at this point 😕

In general I would expect the root parameter to look like: root=UUID=997635c3-00f2-4eca-aa3d-1bf187651ea3 or root=LABEL=armbi_root (obviously with the correct LABEL or UUID for your root partition)

I made some progress with booting Armbian from USB on my Mochabin. I've been teaching myself U-boot cli. I downloaded Armbian_community_24.5.0-trunk.93_Espressobin_jammy_current_5.15.149.img.xz and used dd to write it to a USB stick. Marvell>> usb start starting USB... USB0: Register 2000120 NbrPorts 2 Starting the controller USB XHCI 1.00 USB1: Register 2000120 NbrPorts 2 Starting the controller USB XHCI 1.00 scanning bus 0 for devices... 4 USB Device(s) found scanning bus 1 for devices... 1 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found Marvell>> usb dev IDE device 0: Vendor: Rev: PMAP Prod: USB DISK 3.0 Type: Removable Hard Disk Capacity: 29604.0 MB = 28.9 GB (60628992 x 512) Marvell>> usb part Partition Map for USB device 0 -- Partition Type: DOS Part Start Sector Num Sectors UUID Type 1 8192 4644864 1806f7be-01 83 Then to boot from the USB I use: setenv bootargs 'console=ttyS0,115200' 'earlycon=uart8250,mmio32,0xf0512000' 'root=/dev/sdb1' 'rootfstype=ext2' rootwait setenv bootcmd 'true; usb start; ext2load usb 0:1 $kernel_addr_r $image_name; ext2load usb 0:1 $fdt_addr_r boot/dtb/marvell/armada-7040-db.dtb; booti $kernel_addr_r - $fdt_addr_r' boot The image boots but the kernel reports that it is waiting for /dev/sdb1 What should: root= be set to, please? Thanks, Butch xx

Meanwhile, I managed to do it another way: - "Boot from eMMC / system on eMMC" via armbian-install -> that creates two partitions on eMMC, one boot, one rootfs - fdisk, mkfs.ext4 on nvme, rsync all files from rootfs eMMC partition to nvme - note down UUID of nvme partition from blkid, replace it in /etc/fstab and /boot/armbianEnv.txt, reboot - nuke rootfs partition on eMMC as it's not used anymore Did you boot from eMMC? You mention no SD card, yet somehow you could run armbian prior to install it; or PXE boot?

DMESG; https://paste.debian.net/1308388/ Wifi / Bluetooth patrick@bananapim4zero:~$ ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host noprefixroute valid_lft forever preferred_lft forever 3: wlx9803cf623b3f: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 98:03:cf:62:3b:3f brd ff:ff:ff:ff:ff:ff inet 10.0.0.172/24 brd 10.0.0.255 scope global dynamic noprefixroute wlx9803cf623b3f valid_lft 172331sec preferred_lft 172331sec inet6 2601:586:4d00:3580::9b29/128 scope global dynamic noprefixroute valid_lft 345134sec preferred_lft 345134sec inet6 2601:586:4d00:3580:26d0:ba9c:10af:4de9/64 scope global dynamic noprefixroute valid_lft 345601sec preferred_lft 345601sec inet6 fe80::2cd1:8a57:ec6f:1336/64 scope link noprefixroute valid_lft forever preferred_lft forever 4: usb0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether f6:b7:9a:22:59:54 brd ff:ff:ff:ff:ff:ff patrick@bananapim4zero:~$ bluetoothctl Agent registered [CHG] Controller 98:03:CF:62:3B:40 Pairable: yes [bluetooth]# show Controller 98:03:CF:62:3B:40 (public) Name: bananapim4zero Alias: bananapim4zero Class: 0x00000000 Powered: yes Discoverable: no DiscoverableTimeout: 0x000000b4 Pairable: yes UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb) UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb) UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb) UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0542 Discovering: no Roles: central Roles: peripheral Advertising Features: ActiveInstances: 0x00 (0) SupportedInstances: 0x05 (5) SupportedIncludes: appearance SupportedIncludes: local-name Connected to PC with g_ether enabled; [2788714.157345] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [2788714.157348] usb 6-1: Product: RNDIS/Ethernet Gadget [2788714.157351] usb 6-1: Manufacturer: Armbian Linux 6.6.18-current-sunxi64 with musb-hdrc [2788714.158370] cdc_subset 6-1:1.0 usb0: register 'cdc_subset' at usb-0000:00:1d.7-1, Linux Device, 32:5f:82:14:13:48 [2788714.186937] usbcore: registered new interface driver cdc_eem lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mmcblk0 179:0 0 29.7G 0 disk └─mmcblk0p1 179:1 0 29.4G 0 part /var/log.hdd / mmcblk1 179:32 0 7.3G 0 disk ├─mmcblk1p1 179:33 0 508M 0 part └─mmcblk1p2 179:34 0 6.8G 0 part mmcblk1boot0 179:64 0 4M 1 disk mmcblk1boot1 179:96 0 4M 1 disk zram0 251:0 0 961.7M 0 disk [SWAP] zram1 251:1 0 50M 0 disk /var/log zram2 251:2 0 0B 0 disk I haven't tested to make sure eMMC boot works yet with Armbian, but it does on my personal builds, with the same patches in place. NOTE: WIFI and BT can sometimes be sketchy. Currently the Armbian img is using RTW88. There is the morrownr option, which runs stable, but I also find to not be 100%. Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Hey, I'm trying to boot Armbian 27 Feb bullseye for Odroid C4 from microSD card and I get dropped to initramfs console because root UUID is not found. I fsck'd the card and it seems okay. Read that I should say to the kernel to wait for root to be found with rootdelay, added a line to armbianEnv.txt to no avail (didn't run any update command, though). What are your thoughts? Any other ideas? Thanks!

Good day to you))) I have a TV BOX TX9Pro. Chassis (Main Board): H616/H313mini84 V2.0 kernel 4.9.170 I would like to run one of the armbian builds on it. But I can’t figure out how to do this, here are the logs when starting the console... Is there support for this device? tell me what to do and how... Thanks in advance. U-Boot SPL 2021.04 (May 25 2023 - 13:03:46 +0200) DRAM:This DRAM setup is currently not supported. resetting ... [70]HELLO! BOOT0 is starting! [73]BOOT0 commit : 803d783 [75]set pll start [78]periph0 has been enabled [81]set pll end [83]unknow PMU [84]unknow PMU [86]PMU: AXP1530 [88]dram return write ok [90]board init ok [92]DRAM BOOT DRIVE INFO: V0.645 [96]the chip id is 0x5d00 [98]chip id check OK [103]DRAM_VCC set to 1500 mv [106]DRAM CLK =600 MHZ [108]DRAM Type =3 (3:DDR3,4:DDR4,7:LPDDR3,8:LPDDR4) [116]Actual DRAM SIZE =1024 M [118]DRAM SIZE =1024 MBytes, para1 = 30eb, para2 = 4000000, dram_tpr13 = 6041 [132]DRAM simple test OK. [134]rtc standby flag is 0x0, super standby flag is 0x0 [140]dram size =1024 [143]card no is 2 [145]sdcard 2 line count 8 [147][mmc]: mmc driver ver 2020-09-10 15:32 [157][mmc]: Wrong media type 0x0, but host sdc2, try mmc first [163][mmc]: ***Try MMC card 2*** [202][mmc]: RMCA OK! [204][mmc]: bias 4 [207][mmc]: MMC 5.0 [209][mmc]: HSSDR52/SDR25 8 bit [212][mmc]: 50000000 Hz [214][mmc]: 7456 MB [216][mmc]: ***SD/MMC 2 init OK!!!*** [291]Loading boot-pkg Succeed(index=0). [294]Entry_name = u-boot [304]Entry_name = monitor [307]Entry_name = dtbo [310]Entry_name = dtb [314]tunning data addr:0x4a0003e8 [317]Jump to second Boot. NOTICE: BL3-1: v1.0(debug):a0d3abd NOTICE: BL3-1: Built : 17:32:02, 2020-10-20 NOTICE: BL3-1 commit: 8 ERROR: Error initializing runtime service tspd_fast NOTICE: BL3-1: Preparing for EL3 exit to normal world NOTICE: BL3-1: Next image address = 0x4a000000 NOTICE: BL3-1: Next image spsr = 0x1d3 U-Boot 2018.05 (Feb 15 2023 - 17:22:04 +0800) Allwinner Technology [00.391]CPU: Allwinner Family [00.394]Model: sun50iw9 I2C: ready [00.398]DRAM: 1 GiB [00.401]Relocation Offset is: 35ebf000 [00.442]secure enable bit: 0 [00.444]pmu_axp152_probe pmic_bus_read fail [00.448]PMU: AXP1530 [00.454]CPU=1008 MHz,PLL6=600 Mhz,AHB=200 Mhz, APB1=100Mhz MBus=400Mhz [00.462]drv_disp_init [00.492]__clk_enable: clk is null. [00.497]drv_disp_init finish [00.500]gic: sec monitor mode [00.522]flash init start [00.524]workmode = 0,storage type = 2 [00.528]MMC: 2 [00.529][mmc]: mmc driver ver uboot2018:2021-07-19 14:09:00 [00.535][mmc]: get sdc_type fail and use default host:tm4. [00.546][mmc]: SUNXI SDMMC Controller Version:0x40502 [00.590][mmc]: Best spd md: 4-HS400, freq: 3-100000000, Bus width: 8 [00.596]sunxi flash init ok [00.600]Loading Environment from SUNXI_FLASH... OK [00.609]usb burn from boot delay time 0 weak:otg_phy_config [00.623]usb prepare ok [01.426]overtime [01.430]do_burn_from_boot usb : no usb exist [01.434]boot_gui_init:start FAT: Misaligned buffer address (7be7be58) 32 bytes read in 4 ms (7.8 KiB/s) tcon_de_attach:de=0,tcon=2[01.567]boot_gui_init:finish [01.570]bmp_name=bootlogo.bmp 2764854 bytes read in 40 ms (65.9 MiB/s) [01.633]update dts ** Unrecognized filesystem type ** [01.642]load file(ULI/factory/rootwait init.txt) error. ** Unrecognized filesystem type ** [01.655]load file(ULI/factory/snum.txt) error. [01.659]name in map mac ** Unrecognized filesystem type ** [01.668]load file(ULI/factory/wifi_mac.txt) error. ** Unrecognized filesystem type ** [01.680]load file(ULI/factory/bt_mac.txt) error. ** Unrecognized filesystem type ** [01.692]load file(ULI/factory/selinux.txt) error. ** Unrecognized filesystem type ** [01.704]load file(ULI/factory/specialstr.txt) error. [01.713]update part info [01.738]update bootcmd [01.740]No ethernet found. Hit any key to stop autoboot: 0 [02.050]Starting kernel ... [02.053][mmc]: mmc exit start [02.101][mmc]: mmc 2 exit ok [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.9.170 (akrd6@R740XD) (gcc version 5.3.1 20160412(Linaro GCC 5.3-2016.05) ) #80 SMP PREEMPT Wed Feb 15 17:22:30 CST 2023 [ 0.000000] Boot CPU: AArch64 Processor [410fd034] [ 0.000000] bootconsole [earlycon0] enabled [ 0.027874] BOOTEVENT: 27.858249: ON [ 0.242175] sunxi_i2c_probe()2209 - [i2c3] warning: failed to get regulator d [ 0.243164] sunxi_i2c_probe()2209 - [i2c5] warning: failed to get regulator d [ 0.244517] axp2101-regulator axp2101-regulator.0: Setting DCDC frequency fo unsupported AXP variant [ 0.244601] axp2101-regulator axp2101-regulator.0: Error setting dcdc frequecy: -22 [ 0.279245] [ac200] get ave_regulator_name failed! [ 0.279751] [ac200] pwm enable [ 0.363211] gpio_pin_4(229) gpio_request fail [ ▒[ 0.369727] uart uart1: get regulator failed [ 0.402346] [NAND][NE] Not found valid nand node on dts [ 0.411005] sunxi-wlan soc@03000000:wlan: get gpio chip_en failed [ 0.417894] sunxi-wlan soc@03000000:wlan: get gpio power_en failed [ 0.550010] hci: request ohci1-controller gpio:232 [ 0.742282] axp2101_pek: axp2101-pek can not register without irq [ 0.752785] sunxi_ir_startup: get ir protocol failed [ 0.761135] VE: get debugfs_mpp_root is NULL, please check mpp [ 0.761135] [ 0.769395] VE: sunxi ve debug register driver failed! [ 0.769395] [ 0.784659] mmc:failed to get gpios [ 0.865627] mmc:failed to get gpios [ 0.901895] FD655: ==fd655_driver_probe==================== [ 0.908284] FD655: : (null) [ 0.909038] sunxi-mmc sdc1: smc 2 p1 err, cmd 52, RTO !! [ 0.912260] sunxi-mmc sdc1: smc 2 p1 err, cmd 52, RTO !! [ 0.926757] FD655: : (null) [ 0.929915] sunxi-mmc sdc1: smc 2 p1 err, cmd 5, RTO !! [ 0.935814] sunxi-mmc sdc1: smc 2 p1 err, cmd 5, RTO !! [ 0.941713] sunxi-mmc sdc1: smc 2 p1 err, cmd 5, RTO !! [ 0.947606] sunxi-mmc sdc1: smc 2 p1 err, cmd 5, RTO !! [ 0.953859] FD655: register_fd655_driver: Successed to add fd655 module [ 0.973520] failed get gpio-spdif gpio from dts,spdif_gpio:-2 [ 0.983217] [audio-codec]dachpf_cfg configurations missing or invalid. [ 0.990865] lineout_vol:26, linein_gain:3, fmin_gain:3, digital_vol:0, adcdr_cfg:0, adchpf_cfg:0, dacdrc_cfg:0, dachpf_cfg:0, ramp_func_used:1, pa_msleep_tme:160, pa_ctl_level:0, gpio-spk:0 [ 1.014903] sndhdmi sndhdmi: ASoC: CPU DAI (null) not registered [ 1.021698] sndhdmi sndhdmi: snd_soc_register_card() failed: -517 [ 1.035293] sunxi-ahub-cpudai 5097000.cpudai3-controller: ahub cpudai id invlid [ 1.068733] ERROR: pinctrl_get for HDMI2.0 DDC fail [ 1.078344] tv_probe()1435 - of_property_read_string tv_power failed! [ 1.174637] cpu cpu1: opp_list_debug_create_link: Failed to create link [ 1.182156] cpu cpu1: _add_opp_dev: Failed to register opp debugfs (-12) [ 1.189771] cpu cpu2: opp_list_debug_create_link: Failed to create link [ 1.197234] cpu cpu2: _add_opp_dev: Failed to register opp debugfs (-12) [ 1.204828] cpu cpu3: opp_list_debug_create_link: Failed to create link [ 1.212279] cpu cpu3: _add_opp_dev: Failed to register opp debugfs (-12) [ 1.684491] selinux: avc: denied { set } for scontext=u:r:vendor_init:s0 context=u:object_r:default_prop:s0 tclass=property_service permissive=1 [ 1.684491] [ 1.702686] selinux: avc: denied { set } for scontext=u:r:vendor_init:s0 context=u:object_r:dalvik_prop:s0 tclass=property_service permissive=1 [ 1.702686] [ 2.576915] FAT-fs (mmcblk0p15): bogus number of reserved sectors console:/ $ [ 8.720978] apexd: Failed to walk /product/apex : Can't open /prduct/apex for reading : No such file or directory ^C 130|console:/ $ [ 22.711942] sunxi-mmc sdc1: smc 2 p1 err, cmd 52, RTO !! [ 22.913822] SSV6XXX_SDIO mmc2:0001:1: vendor = 0x3030 device = 0x3030 [ 22.947618] SSV6XXX_SDIO mmc2:0001:1: dataIOPort 0x10000 regIOPort 0x10020 [ 22.958352] sunxi-mmc sdc1: smc 2 p1 err, cmd 52, RE RCE !! [ 23.030814] SSV6XXX_SDIO mmc2:0001:1: dataIOPort 0x10000 regIOPort 0x10020 [ 23.057388] SSV6XXX HCI TX Task started. [ 23.135876] Enable HCI TX aggregation [ 24.042450] SSV WLAN driver SSV6006C: Set new macaddr [ 24.060821] SSV WLAN driver SSV6006C: VIF 08:1a:1e:fd:85:e4 of type 2 is added. [ 25.361805] SSV WLAN driver SSV6006C: Set new macaddr [ 25.386662] SSV WLAN driver SSV6006C: VIF 08:1a:1e:fd:85:e5 of type 2 is added. [ 27.173711] selinux: avc: denied { set } for property=sys.config.rootservice pid=2978 uid=0 gid=0 scontext=u:r:rootservice:s0 tcontext=u:object_r:system_prop:s0 tclass=property_service permissive=1 [ 27.173711] [ 27.207603] audit: rate limit exceeded [ 30.214797] apexd: Can't open /product/apex for reading : No such file or directory U-Boot SPL 2021.04 (May 25 2023 - 13:03:46 +0200) /system/bin/sh: syntax error: unexpected '(' 1|console:/ $ DRAM:This DRAM setup is currently not supported. /system/bin/sh: DRAM:This: inaccessible or not found 127|console:/ $ [ 34.750480] selinux: avc: denied { set } for property=supolicy.loaded pid=3902 uid=0 gid=0 scontext=u:r:toolbox:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service permissive=1 [ 34.750480] U-Boot SPL 2021.04 (May 25 2023 - 13:03:46 +0200) /system/bin/sh: syntax error: unexpected '(' 1|console:/ $ DRAM:This DRAM setup is currently not supported. /system/bin/sh: DRAM:This: inaccessible or not found 127|console:/ $

This is a key importance for me and for you. Perhaps some hints exist in man fstrim On my SSD, which is 50% full, the slowdown is observed after about 2 months. I just run the command in this case and wait (do nothing). This repeats itself when I start to observe a slowdown. To be honest, I do not know of any other tool for this functionality than dmesg messages when mounting a file system.

Okay, let's move on. When I mount an ext4 FS, sudo mount -v -o rw,noatime,nodiratime,discard,errors=remount-ro,commit=600 /dev/sdf1 /mnt dmesg reports: [28422.686388] EXT4-fs (sdf1): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none. [28422.717550] EXT4-fs (sdf1): mounted filesystem with ordered data mode. Opts: errors=remount-ro. Quota mode: none. [28612.985794] EXT4-fs (sdf1): mounting with "discard" option, but the device does not support discard [28612.985800] EXT4-fs (sdf1): mounted filesystem with ordered data mode. Opts: discard,errors=remount-ro,commit=600. Quota mode: none. When I mount an btrfs FS, sudo mount -o rw,relatime,ssd,space_cache,subvolid=5,subvol=/ /dev/sdf /mnt dmesg reports: [35708.200591] BTRFS: device label test-btrfs devid 1 transid 5 /dev/sdf scanned by mkfs.btrfs (24307) [35708.283831] BTRFS info (device sdf): disk space caching is enabled [35708.283837] BTRFS info (device sdf): has skinny extents [35708.283839] BTRFS info (device sdf): flagging fs with big metadata feature [35708.286642] BTRFS info (device sdf): checking UUID tree [36135.461701] BTRFS info (device sdf): disk space caching is enabled [36135.461706] BTRFS info (device sdf): has skinny extents [36268.307315] BTRFS info (device sdf): enabling ssd optimizations [36268.307322] BTRFS info (device sdf): disk space caching is enabled [36268.307324] BTRFS info (device sdf): has skinny extents EXT4 reports that there is no trim support. BTRFS informs you that everything is included. Perhaps I am mistaken and this is the presence/absence of support in the kernel drivers. I have two more devices, adapters for SATA. One is directly soldered to the BPI-M3. The other is an external PCIe-SATA. I'll check them later.