Jump to content

g00d

Members
  • Posts

    35
  • Joined

  • Last visited

Everything posted by g00d

  1. I understand now. https://forum.odroid.com/viewtopic.php?f=93&t=36213 thanks for clarification
  2. Hello everybody, is it possible in u-boot (boot.ini) to make a user input and let the user choose from A or B and according to the choice load a particular uInitrd? In case a non-valid answer is given a default answer should be used. Best of all would be if I could implement a time-out. When user does not make input answer B should be selected. I would know how to do this in bash but is that also possible in boot.ini somehow?
  3. Well, according to the mentioned links to check WOL support my board returns: ethtool eth0 and nmcli c show "Wired Connection 1" so shouldn't it be supported then? What else do I need to make this auto-poweroff auto-resume stuff work? any tools, scripts you can suggest to try? is there any alternative like using suspend/hibernate instead of shutdown? how could I save energy on the ODROID-HC2 while not used, any helpful hints?
  4. I've found the Debian Wiki about WOL but I am missing information on how auto-shutdown/auto-suspend etc. works on Armbian. Whick packages, configuration files are needed for setting up energy power save mode in Armbian Bullseye on ODROID-HC2 ? Is Debian Suspend Wiki to go for? I'd like my ODROID-HC2 to power-off somehow to save energy, especially during night periods where the NAS isn't used usually. My ODROIC-HC2 runs as a NAS with samba setup. Can anyone point me to the right direction, please? thank you.
  5. Hello everybody, I am not using OpenMediaVault but I am trying to implement some of its feautures into my existing system based on Armbian Bullseye, running on ODROID HC-2. Is there any tutorial or HowTo available that explains steb-by-step how to install and setup auto-shutdown feauture and WOL? I'd like my odroid hc-2 shut-down when not in use (especially over night) and let it auto-start again whenever I access it via \\myhost\share or \\192.168.0.1\someshare. If that's not possible then I can live with sending a WOL magic packet manually. Any known tutorial avaible for doing this on a ODROID-HC2 ?
  6. g00d

    overlays

    thanks for all the information provided. Honestly said I am not familiar in decompiling and reading such code. If anyone else can provide some more answers to my previous questions related to the ODROID-HC2 board in this matter, please let me know. Thanks in advance. As I am not using a special housing like cloudshell and unless there is no advantage, I will leave the settings cs2 to default off so the mentioned overlay are not loaded at system boot.
  7. g00d

    overlays

    Hi tparys, thanks for the link that was kinda helpful but I still have some questions. As I showed in my initial posting my boot.ini loads three overlay files when variable cs2enable is set to true. Those three overlay are setenv overlays "i2c0 i2c1 hktft-cs-ogst" A) how do I know what these overlay are good for and used for? The default boot.ini does NOT load them. They are loaded only if I set cs2enable=true, the comments in boot.ini says that this is only needed when using a CloudShell2 enclosure to enable TFT LCD and FAN control via i2c bus. Well, in my case I don't have a CloudShell2 because I am using simply a ODROID-HC2 (equivalent to odroidxu4 board). If understood correctly I can leave cs2enable to default setting "false" and thus don't need loading those overlay. Is this correct? the boot.ini of my ODROID-HC2 installation does not match any more lines with search pattern "overlay". Does that mean that none of the rest overlay files are important in my case? dtb-5.4.151-odroidxu4/overlays: insgesamt 40K -rw-r--r-- 1 root root 1,7K 8. Okt 21:52 ads7846.dtbo -rw-r--r-- 1 root root 1,3K 8. Okt 21:52 hktft32.dtbo -rw-r--r-- 1 root root 1,8K 8. Okt 21:52 hktft35.dtbo -rw-r--r-- 1 root root 1,5K 8. Okt 21:52 hktft-cs-ogst.dtbo -rw-r--r-- 1 root root 224 8. Okt 21:52 i2c0.dtbo -rw-r--r-- 1 root root 226 8. Okt 21:52 i2c1.dtbo -rw-r--r-- 1 root root 417 8. Okt 21:52 onewire.dtbo -rw-r--r-- 1 root root 691 8. Okt 21:52 spi0.dtbo -rw-r--r-- 1 root root 792 8. Okt 21:52 sx865x-i2c1.dtbo -rw-r--r-- 1 root root 227 8. Okt 21:52 uart0.dtbo - how do I know what the rest of the overlays are good for? I wasn't able to find any hint in the link you posted or on the comments. There is also no README.<soc-id>-overlays on my installation under /boot/dtb/overlay/ (32-bit SoCs) or /boot/dtb/allwinner/overlay/ (64-bit SoCs) and this link doesn't reveal any information about the overlays and what they are useful for for which boards, etc. Can anyone tell me please, which overlays are possibly interesting for the ODROID-HC2 ? thanks to all!
  8. g00d

    overlays

    Hello all, my boot partition contains following file structure: # ls -lh insgesamt 20M drwxr-xr-x 3 root root 4,0K 11. Nov 16:27 ./ drwxr-xr-x 3 root root 4,0K 16. Nov 09:24 ../ -rw-r--r-- 1 root root 38K 8. Okt 22:10 boot.bmp -rw-r--r-- 1 root root 14K 27. Okt 16:52 boot.ini lrwxrwxrwx 1 root root 21 8. Okt 22:10 dtb -> dtb-5.4.151-odroidxu4/ drwxr-xr-x 3 root root 4,0K 8. Okt 22:10 dtb-5.4.151-odroidxu4/ -rw-r--r-- 1 root root 0 8. Okt 22:10 .next lrwxrwxrwx 1 root root 25 27. Okt 16:58 uInitrd -> uInitrd-5.4.151-odroidxu4 -rw-r--r-- 1 root root 13M 27. Okt 16:58 uInitrd-5.4.151-odroidxu4 -rwxr-xr-x 1 root root 7,0M 8. Okt 21:52 vmlinuz-5.4.151-odroidxu4* lrwxrwxrwx 1 root root 25 8. Okt 22:10 zImage -> vmlinuz-5.4.151-odroidxu4* # ls -lh dtb-5.4.151-odroidxu4/* -rw-r--r-- 1 root root 41K 8. Okt 21:52 dtb-5.4.151-odroidxu4/exynos3250-artik5-eval.dtb -rw-r--r-- 1 root root 52K 8. Okt 21:52 dtb-5.4.151-odroidxu4/exynos3250-monk.dtb -rw-r--r-- 1 root root 57K 8. Okt 21:52 dtb-5.4.151-odroidxu4/exynos3250-rinato.dtb -rw-r--r-- 1 root root 59K 8. Okt 21:52 dtb-5.4.151-odroidxu4/exynos4210-origen.dtb -rw-r--r-- 1 root root 56K 8. Okt 21:52 dtb-5.4.151-odroidxu4/exynos4210-smdkv310.dtb -rw-r--r-- 1 root root 61K 8. Okt 21:52 dtb-5.4.151-odroidxu4/exynos4210-trats.dtb -rw-r--r-- 1 root root 63K 8. Okt 21:52 dtb-5.4.151-odroidxu4/exynos4210-universal_c210.dtb -rw-r--r-- 1 root root 100K 8. Okt 21:52 dtb-5.4.151-odroidxu4/exynos4412-i9300.dtb -rw-r--r-- 1 root root 100K 8. Okt 21:52 dtb-5.4.151-odroidxu4/exynos4412-i9305.dtb -rw-r--r-- 1 root root 74K 8. Okt 21:52 dtb-5.4.151-odroidxu4/exynos4412-itop-elite.dtb -rw-r--r-- 1 root root 97K 8. Okt 21:52 dtb-5.4.151-odroidxu4/exynos4412-n710x.dtb -rw-r--r-- 1 root root 72K 8. Okt 21:52 dtb-5.4.151-odroidxu4/exynos4412-odroidu3.dtb -rw-r--r-- 1 root root 72K 8. Okt 21:52 dtb-5.4.151-odroidxu4/exynos4412-odroidx2.dtb -rw-r--r-- 1 root root 72K 8. Okt 21:52 dtb-5.4.151-odroidxu4/exynos4412-odroidx.dtb -rw-r--r-- 1 root root 71K 8. Okt 21:52 dtb-5.4.151-odroidxu4/exynos4412-origen.dtb -rw-r--r-- 1 root root 63K 8. Okt 21:52 dtb-5.4.151-odroidxu4/exynos4412-smdk4412.dtb -rw-r--r-- 1 root root 62K 8. Okt 21:52 dtb-5.4.151-odroidxu4/exynos4412-tiny4412.dtb -rw-r--r-- 1 root root 100K 8. Okt 21:52 dtb-5.4.151-odroidxu4/exynos4412-trats2.dtb -rw-r--r-- 1 root root 62K 8. Okt 21:52 dtb-5.4.151-odroidxu4/exynos5250-arndale.dtb -rw-r--r-- 1 root root 58K 8. Okt 21:52 dtb-5.4.151-odroidxu4/exynos5250-smdk5250.dtb -rw-r--r-- 1 root root 63K 8. Okt 21:52 dtb-5.4.151-odroidxu4/exynos5250-snow.dtb -rw-r--r-- 1 root root 63K 8. Okt 21:52 dtb-5.4.151-odroidxu4/exynos5250-snow-rev5.dtb -rw-r--r-- 1 root root 60K 8. Okt 21:52 dtb-5.4.151-odroidxu4/exynos5250-spring.dtb -rw-r--r-- 1 root root 23K 8. Okt 21:52 dtb-5.4.151-odroidxu4/exynos5260-xyref5260.dtb -rw-r--r-- 1 root root 44K 8. Okt 21:52 dtb-5.4.151-odroidxu4/exynos5410-odroidxu.dtb -rw-r--r-- 1 root root 33K 8. Okt 21:52 dtb-5.4.151-odroidxu4/exynos5410-smdk5410.dtb -rw-r--r-- 1 root root 78K 8. Okt 21:52 dtb-5.4.151-odroidxu4/exynos5420-arndale-octa.dtb -rw-r--r-- 1 root root 86K 8. Okt 21:52 dtb-5.4.151-odroidxu4/exynos5420-peach-pit.dtb -rw-r--r-- 1 root root 72K 8. Okt 21:52 dtb-5.4.151-odroidxu4/exynos5420-smdk5420.dtb -rw-r--r-- 1 root root 81K 8. Okt 21:52 dtb-5.4.151-odroidxu4/exynos5422-odroidhc1.dtb -rw-r--r-- 1 root root 87K 8. Okt 21:52 dtb-5.4.151-odroidxu4/exynos5422-odroidxu3.dtb -rw-r--r-- 1 root root 87K 8. Okt 21:52 dtb-5.4.151-odroidxu4/exynos5422-odroidxu3-lite.dtb -rw-r--r-- 1 root root 86K 8. Okt 21:52 dtb-5.4.151-odroidxu4/exynos5422-odroidxu4.dtb -rw-r--r-- 1 root root 87K 8. Okt 21:52 dtb-5.4.151-odroidxu4/exynos5800-peach-pi.dtb dtb-5.4.151-odroidxu4/overlays: insgesamt 40K -rw-r--r-- 1 root root 1,7K 8. Okt 21:52 ads7846.dtbo -rw-r--r-- 1 root root 1,3K 8. Okt 21:52 hktft32.dtbo -rw-r--r-- 1 root root 1,8K 8. Okt 21:52 hktft35.dtbo -rw-r--r-- 1 root root 1,5K 8. Okt 21:52 hktft-cs-ogst.dtbo -rw-r--r-- 1 root root 224 8. Okt 21:52 i2c0.dtbo -rw-r--r-- 1 root root 226 8. Okt 21:52 i2c1.dtbo -rw-r--r-- 1 root root 417 8. Okt 21:52 onewire.dtbo -rw-r--r-- 1 root root 691 8. Okt 21:52 spi0.dtbo -rw-r--r-- 1 root root 792 8. Okt 21:52 sx865x-i2c1.dtbo -rw-r--r-- 1 root root 227 8. Okt 21:52 uart0.dtbo the boot.ini contains following part: if test "${cs2enable}" = "true"; then fdt resize 8192 setenv overlays "i2c0 i2c1 hktft-cs-ogst" for overlay in ${overlays}; do ext4load mmc 0:1 0x60000000 /boot/dtb/overlays/${overlay}.dtbo fdt apply 0x60000000 done fi can anyone explain to me in simple words what these overlays are good for? are they needed, what is their job? I tried commenting out the line here # ext4load mmc 0:1 0x60000000 /boot/dtb/overlays/${overlay}.dtbo and the system still booted normally without any noticeable difference during boot and operation. Can anyone shed some light onto, please? thanks
  9. Hi Werner, yes of course HIM. The kind of that script is absolutely inacceptable. No warning, no checks, nothing, he's just wiping! even with CTRL+C at script termination. But I wrote this topic to warn the armbian community and hopefully the developers behind it. This script was never downloaded and installed by myself into my Armbian OS. It is shipped with Armbian. That is why I wrote here so the devs can check and remove this irresponsible script from Armbian Bullseye image. The image I am using is Armbian_21.08.3_Odroidxu4_bullseye_current_5.4.151.img and I just checked the content. The mentioned bad script is located in /usr/bin/wireguard-manager @devs: please check and decide if you wanna keep or remove this dangerous script from your nice Armbian work.
  10. Dear all, on my ODROID-HC2 Armbian Bullseye installation there is a script /usr/bin/wireguard-manager and I'm curious what this is about at all. In my opinion only wireguard-tools is "ok" to setup a wireguard VPN configuration but no "wireguard" package or such a script which installs a bunch of stuff and weird things. Unfortunately I was new to wireguard and this was my 1st configuration and setup I did. I discovered the mentioned script and executed "wireguard-manager --help" which against my expectation started an installation of different stuff. I didn't cancel this because I was afraid in ending in half-baked misconfigured states. It did "apt update" and also installed some packages on my system and even apt-get install linux-headers-"$(uname -r)" -y which failed because the kernel on my ODROID-HC2 is linux-image-current-odroidxu4. It removed chrony, installed ntp, gawk, and various other packages and it also modified or added some systemd/sysv scripts (don't remember exactly). While progressing I realized that I never ever needed this script and now I'm afraid about the systemd modifications. Can anyone shed some light into this script, why it is there and how I can revert all modifications made by that script? It's really annoying that it didn't interprete the --help argument as expected and started the installation and configuration any helpful answer appreciated EDIT: WTF ?!?!?!?! according to the script arguments as shown on the GIT repo I wanted to try another argument, this time I used the neutral --list argument. It didn't list anything but it throwed an input. I didn't enter 1 or 2 but I pressed CTRL+C and returned to the bash prompt. And what the hell do I see ?? /etc/wireguard is WIPED !!! the folder is gone with all my configs and keys. It was there seconds ago and I did not execute any other commands meanwhile. History proves this and also "locate wireguard" which is still displaying /etc/wireguard in the cache db. This is ridigoulous, what the f*** is this script doing? This is broken and needs to get removed. I'm really really PIS*** !!!!! root@host:/# wireguard-manager --list Do you want the interface (server) or peer (client) to be installed? 1) Interface 2) Peer Interface Or Peer [1-2]: 1^C root@host:/# cd /etc/wireguard NOT FOUND !!! EDIT: this is reproducable. This sucks! And there is NO backup folder created under /var/backups with variable WIREGUARD_OLD_BACKUP or SYSTEM_BACKUP_PATH variable. Damn it, REMOVE THIS SCRIPT! this script is irresponsible and belongs removed from Armbian ! rm -rf /usr/bin/wireguard-manager
  11. Well, I made some progression and want to share it with the community: Related to question 1) still unresolved because I don't know if I am missing something or this could possibly be a bug? Related to question 2) the culprit lies inside the function storage_info() because I am not using simply /dev/sda1 but an encrypted drive. My disk *is* /dev/sda1 but it's LUKS encrypted and so my device for the system is /dev/mapper/rootfs or even more /dev/mapper/volumeGroup1-rootfs because I am also using LVM. The storage_info() function does not take this into account. I had to modify the function to this here: function storage_info() { # storage info RootInfo=$(df -h /) root_usage=$(awk '/\// {print $(NF-1)}' <<<${RootInfo} | sed 's/%//g') root_total=$(awk '/\// {print $(NF-4)}' <<<${RootInfo}) StorageInfo=$(df -h $STORAGE 2>/dev/null | grep $STORAGE) #if [[ -n "${StorageInfo}" && ${RootInfo} != *$STORAGE* ]]; then if [[ -n "${StorageInfo}" ]]; then storage_usage=$(awk '/\// {print $(NF-1)}' <<<${StorageInfo} | sed 's/%//g') storage_total=$(awk '/\// {print $(NF-4)}' <<<${StorageInfo}) if [[ -n "$(command -v smartctl)" ]]; then #DISK="${STORAGE::-1}" storage_temp+=$(smartctl -l scttempsts $DISK 2> /dev/null | grep -i 'Current Temperature:' | awk '{print $(NF-1)}') storage_pwroff_retract_count=$(smartctl -a $DISK | grep Power-Off_Retract | awk '{print $10}') fi fi } # storage_info in detail: it needs to comment out the originally line #if [[ -n "${StorageInfo}" && ${RootInfo} != *$STORAGE* ]]; then and change it to: if [[ -n "${StorageInfo}" ]]; then it needs to comment the following line here inside the if clause: #DISK="${STORAGE::-1}" and it needs a definition in the top of the script where we need to add a DISK variable. Simply said, we need to separate DISK and STORAGE in case of encrypted systems and/or LVM used. The top of the script 30-armbian-sysinfo looks like that in my case: DISK=/dev/sda1 STORAGE=/dev/mapper/volumeGroup1-rootfs that way the script works fine and outputs the correct values. Related to question 3) solved also according to question 2. I added the threshold 50 for the power-off retract count in the beginning for the script: [...] CPU_TEMP_OFFSET=0 HDD_TEMP_LIMIT=60 PWROFF_WARN=25 [...] The variable and display command should look like that: disk_pwroff_retract_count=$(smartctl -a $DISK | grep Power-Off_Retract | awk '{print $10}') [...] # display info display "HDD PWRoff Retract Count" "$disk_pwroff_retract_count" $PWROFF_WARN "0" "times" "" ; a=$((a+$?)) [...]
  12. Hello community, when I SSH into my ODROID-HC2 I get the nice coloured MOTD which I really like. Question 1) I found the configuration file /etc/default/armbian-motd and the directory /etc/update-motd.d and after reading the bash code I lack in understanding why some information lines are suppressed in the MOTD banner when the scripts get executed. For example: I would expect to see some net traffic stats because /etc/default/armbian-motd uses the default setting PRIMARY_DIRECTION="rx" and the package "vnstat" is installed and "vnstat -i eth0" return correct output. I also tried changing PRIMARY_DIRECTION line to ="both" but I don't get any net status displayed in that MOTD banner. Why? EDIT: I found the culprit which lies in /etc/update-motd.d/30-armbian-sysinfo script. My PRIMARY_INTERFACE is eth0 and as such also defined in /etc/default/armbian-motd. But that line here: # Check whether PRIMARY_INTERFACE exist in /var/lib/vnstat/ PRIMARY_INTERFACE=$(comm -12 <(ls -1 /var/lib/vnstat/ 2> /dev/null) <(echo "$PRIMARY_INTERFACE" | sed 's/+/\n/g') | sed -n -e 'H;${x;s/\n/+/g;s/^+//;p;}') sets that variable to "blank" because the command shown above will fail. The content of /var/lib/vnstat in my case is only one single file called "vnstat.db". When I comment out that line, I get the expected output of RX and TX when running the 30-armbian-sysinfo script. Is anything known about this and can provide more information? Question 2) I don't get various stuff displayed, for example the disk temperature. It's not displayed when running the 30-armbian-sysinfo script although the command provided in the script for the variable "storage_temp" inside the function storage_info() works fine when executed at the bash prompt. Why does the command display "storage temp" "$storage_temp" $HDD_TEMP_LIMIT "0" "°C" "" ; a=$((a+$?)) not output the storage temperature ? Question 3) I also wanna display the last and current value of smartmontool for my SATA disk for ID#192 which corresponds to "Power-Off_Retract_Count". The command therefore is smartctl -a /dev/sda | grep Power-Off_Retract | awk '{ print $10 }' but where do I add this? I think it's not advised to modify /etc/update-motd.d/30-armbian-sysinfo file because on the next upgrade it will get overwritten, is it? My idea was modifying that file /etc/update-motd.d/30-armbian-sysinfo by adding a new line after line:162 in the function storage_info which stores the current desired value into the variable name storage_poff_retract : function storage_info() { # storage info RootInfo=$(df -h /) root_usage=$(awk '/\// {print $(NF-1)}' <<<${RootInfo} | sed 's/%//g') root_total=$(awk '/\// {print $(NF-4)}' <<<${RootInfo}) StorageInfo=$(df -h $STORAGE 2>/dev/null | grep $STORAGE) if [[ -n "${StorageInfo}" && ${RootInfo} != *$STORAGE* ]]; then storage_usage=$(awk '/\// {print $(NF-1)}' <<<${StorageInfo} | sed 's/%//g') storage_total=$(awk '/\// {print $(NF-4)}' <<<${StorageInfo}) if [[ -n "$(command -v smartctl)" ]]; then DISK="${STORAGE::-1}" storage_temp+=$(smartctl -l scttempsts $DISK 2> /dev/null | grep -i 'Current Temperature:' | awk '{print $(NF-1)}') storage_poff_retract=$(smartctl -a $STORAGE | grep Power-Off_Retract | awk '{print $10}') fi fi } # storage_info and the also after line 234 adding a new line to display this value: display "storage temp" "$storage_temp" $HDD_TEMP_LIMIT "0" "°C" "" ; a=$((a+$?)) display "storage Power-Off Retract Count" "$storage_poff_retract" "" ; a=$((a+$?)) though I am not sure if that would be correct because it doesn't work as expected and not displayed, same issue as in question 2. What do you think? Please point me to the right direction. Thanks!
  13. @Igor: I have one more question, maybe you can answer this, too? Is it possible to have u-boot look for 'foo.bar' instead of 'boot.ini' ? Is there any HowTo how this could be accomplished ?
  14. Me again. I figured out what the problem was and I was able to solve this like that: the original /boot structure contains three symbolic links, in my case on the ODROID-HC2 (which is equal to odroidxu4): dtb -> dtb-5.4.151-odroidxu4 uInitrd -> uInitrd-5.4.151-odroidxu4 zImage -> vmlinuz-5.4.151-odroidxu4 The default boot.ini is seeking for that link names but on the fat system it's not possible to have symbolic links. I just renamed (or one can simply copy) the existing three files like that: dtb-5.4.151-odroidxu4 ---to---> dtb uInitrd-5.4.151-odroidxu4 ---to---> uInitrd vmlinuz-5.4.151-odroidxu4 ---to---> zImage I also found out that /boot folder is NOT being red by boot process, it looks at the root folder for those files. So I "mv /boot/* /" moved the complete content of the /boot folder into the root. That way the boot process works like a charm. Thank you Igor for assistance. Have a nice weekend
  15. Hi Igor, thanks for the information provided. I have done several tests by starting with a functional uSD card. The bootloader is on the uSD card but I have problems with the first partition. I tried several partition types and file system combinations. When the first partition is formatted as ext4 or ext2 and containing the /boot folder the boot process finishes successfully. However when I format this partition with 'mkfs.vfat' or 'mkfs.fat' or 'mkfs.fat -F 16' the boot process will fail. According to the boot log it seems that U-Boot is expecting a ext* file system. I check boot.ini and to be sure I not only copied /boot folder to the partition 1 but also all the files additionally to the root of that partition. That way u-boot can look for the necessary files in / or in /boot but it didn't help. What am I missing here, how can I make the boot work successful by using vfat or fat16 ? thanks a bunch Did I miss anything or what else do I need to configure so
  16. Hi all, can anyone explain to me how the boot process of an ODROID-HC2 looks in detail, please? for example, my microSD card is /dev/mmcblk1 and it contains only one partition /dev/mmcbl1p1. Questions: a) I think the ODROID-HC2 can exclusively boot from a microSD card, is this correct? Without sdCard the boot process is not possible, right? b) where exactly sits the bootloader? is it in a certain sector of the microSD card and if so where exactly and how long? or does the ODROID-HC2 trying to read at specific addresses and if so where? c) can u-boot only process the first partition of the block device or would it be theoretically possible to have the /boot directory on /dev/mmcbl1p4 ? d) does the partition that u-boot is looking for need to be formatted as ext4 or will ext3, ext2, vfat or even ntfs work, too ? Looking for any helpful information. Thanks a bunch!
  17. /var/log/syslog Oct 28 13:28:12 myhost kernel: [ 1380.296918] audit: type=1326 audit(1635420492.803:57): auid=4294967295 uid=0 gid=0 ses=4294967295 subj==unconfined pid=2575 comm="haveged" exe="/usr/sbin/haveged" sig=31 arch=40000028 syscall=122 compat=0 ip=0xb6f57e98 code=0x80000000 Oct 28 13:28:13 myhost systemd[1]: haveged.service: Scheduled restart job, restart counter is at 1. Oct 28 13:28:13 myhost systemd[1]: Stopped Entropy Daemon based on the HAVEGE algorithm. Oct 28 13:28:13 myhost systemd[1]: Started Entropy Daemon based on the HAVEGE algorithm. Oct 28 13:28:13 myhost systemd[1]: haveged.service: Main process exited, code=killed, status=31/SYS Oct 28 13:28:13 myhost kernel: [ 1380.577192] audit: type=1326 audit(1635420493.083:58): auid=4294967295 uid=0 gid=0 ses=4294967295 subj==unconfined pid=2584 comm="haveged" exe="/usr/sbin/haveged" sig=31 arch=40000028 syscall=122 compat=0 ip=0xb6f7de98 code=0x80000000 Oct 28 13:28:13 myhost systemd[1]: haveged.service: Failed with result 'signal'. Oct 28 13:28:13 myhost systemd[1]: haveged.service: Scheduled restart job, restart counter is at 2. Oct 28 13:28:13 myhost systemd[1]: Stopped Entropy Daemon based on the HAVEGE algorithm. Oct 28 13:28:13 myhost systemd[1]: Started Entropy Daemon based on the HAVEGE algorithm. Oct 28 13:28:13 myhost systemd[1]: haveged.service: Main process exited, code=killed, status=31/SYS Oct 28 13:28:13 myhost systemd[1]: haveged.service: Failed with result 'signal'. Oct 28 13:28:13 myhost kernel: [ 1380.829670] audit: type=1326 audit(1635420493.343:59): auid=4294967295 uid=0 gid=0 ses=4294967295 subj==unconfined pid=2587 comm="haveged" exe="/usr/sbin/haveged" sig=31 arch=40000028 syscall=122 compat=0 ip=0xb6f78e98 code=0x80000000 Oct 28 13:28:13 myhost systemd[1]: haveged.service: Scheduled restart job, restart counter is at 3. Oct 28 13:28:13 myhost systemd[1]: Stopped Entropy Daemon based on the HAVEGE algorithm. Oct 28 13:28:13 myhost systemd[1]: Started Entropy Daemon based on the HAVEGE algorithm. Oct 28 13:28:13 myhost systemd[1]: haveged.service: Main process exited, code=killed, status=31/SYS Oct 28 13:28:13 myhost systemd[1]: haveged.service: Failed with result 'signal'. Oct 28 13:28:13 myhost kernel: [ 1381.079713] audit: type=1326 audit(1635420493.593:60): auid=4294967295 uid=0 gid=0 ses=4294967295 subj==unconfined pid=2590 comm="haveged" exe="/usr/sbin/haveged" sig=31 arch=40000028 syscall=122 compat=0 ip=0xb6fbce98 code=0x80000000 Oct 28 13:28:13 myhost systemd[1]: haveged.service: Scheduled restart job, restart counter is at 4. Oct 28 13:28:13 myhost systemd[1]: Stopped Entropy Daemon based on the HAVEGE algorithm. Oct 28 13:28:13 myhost systemd[1]: Started Entropy Daemon based on the HAVEGE algorithm. Oct 28 13:28:13 myhost systemd[1]: haveged.service: Main process exited, code=killed, status=31/SYS Oct 28 13:28:13 myhost systemd[1]: haveged.service: Failed with result 'signal'. Oct 28 13:28:13 myhost kernel: [ 1381.329773] audit: type=1326 audit(1635420493.843:61): auid=4294967295 uid=0 gid=0 ses=4294967295 subj==unconfined pid=2593 comm="haveged" exe="/usr/sbin/haveged" sig=31 arch=40000028 syscall=122 compat=0 ip=0xb6f86e98 code=0x80000000 Oct 28 13:28:14 myhost systemd[1]: haveged.service: Scheduled restart job, restart counter is at 5. Oct 28 13:28:14 myhost systemd[1]: Stopped Entropy Daemon based on the HAVEGE algorithm. Oct 28 13:28:14 myhost systemd[1]: haveged.service: Start request repeated too quickly. Oct 28 13:28:14 myhost systemd[1]: haveged.service: Failed with result 'signal'. Oct 28 13:28:14 myhost systemd[1]: Failed to start Entropy Daemon based on the HAVEGE algorithm. what is sig=31 and is this related to the kernel ? any clues how to debug the failing haveged.service ? I'm really stuck here :/ -- Boot 7f29c5436e05479595fb657fef877bc8 -- Okt 28 13:05:55 myhost systemd[1]: Started Entropy Daemon based on the HAVEGE algorithm. Okt 28 13:05:55 myhost systemd[1]: haveged.service: Main process exited, code=killed, status=31/SYS Okt 28 13:05:55 myhost systemd[1]: haveged.service: Failed with result 'signal'. Okt 28 13:05:55 myhost systemd[1]: haveged.service: Scheduled restart job, restart counter is at 1. Okt 28 13:05:56 myhost systemd[1]: Stopped Entropy Daemon based on the HAVEGE algorithm. Okt 28 13:05:56 myhost systemd[1]: Started Entropy Daemon based on the HAVEGE algorithm. Okt 28 13:05:56 myhost systemd[1]: haveged.service: Main process exited, code=killed, status=31/SYS Okt 28 13:05:56 myhost systemd[1]: haveged.service: Failed with result 'signal'. Okt 28 13:05:57 myhost systemd[1]: haveged.service: Scheduled restart job, restart counter is at 2. Okt 28 13:05:57 myhost systemd[1]: Stopped Entropy Daemon based on the HAVEGE algorithm. Okt 28 13:05:57 myhost systemd[1]: Started Entropy Daemon based on the HAVEGE algorithm. Okt 28 13:05:57 myhost systemd[1]: haveged.service: Main process exited, code=killed, status=31/SYS Okt 28 13:05:57 myhost systemd[1]: haveged.service: Failed with result 'signal'. Okt 28 13:05:57 myhost systemd[1]: haveged.service: Scheduled restart job, restart counter is at 3. Okt 28 13:05:57 myhost systemd[1]: Stopped Entropy Daemon based on the HAVEGE algorithm. Okt 28 13:05:57 myhost systemd[1]: Started Entropy Daemon based on the HAVEGE algorithm. Okt 28 13:05:57 myhost systemd[1]: haveged.service: Main process exited, code=killed, status=31/SYS Okt 28 13:05:57 myhost systemd[1]: haveged.service: Failed with result 'signal'. Okt 28 13:05:57 myhost systemd[1]: haveged.service: Scheduled restart job, restart counter is at 4. Okt 28 13:05:57 myhost systemd[1]: Stopped Entropy Daemon based on the HAVEGE algorithm. Okt 28 13:05:57 myhost systemd[1]: Started Entropy Daemon based on the HAVEGE algorithm. Okt 28 13:05:57 myhost systemd[1]: haveged.service: Main process exited, code=killed, status=31/SYS Okt 28 13:05:57 myhost systemd[1]: haveged.service: Failed with result 'signal'. Okt 28 13:05:58 myhost systemd[1]: haveged.service: Scheduled restart job, restart counter is at 5. Okt 28 13:05:58 myhost systemd[1]: Stopped Entropy Daemon based on the HAVEGE algorithm. Okt 28 13:05:58 myhost systemd[1]: haveged.service: Start request repeated too quickly. Okt 28 13:05:58 myhost systemd[1]: haveged.service: Failed with result 'signal'. Okt 28 13:05:58 myhost systemd[1]: Failed to start Entropy Daemon based on the HAVEGE algorithm.
  18. A. thanks for the hint. I did set ENABLE=false in /etc/default/armbian-zram-config and vm.swappiness=25 in /etc/sysctl.conf B. I wasn't able to find helpful information under /var/log.hdd/armbian-ramlog.log but after some more research I found the file /etc/default/armbian-ramlog so I'm pretty sure this is the file you wanted to point me at I increased the default file size of 50MB to 100MB. Now the initial issue with sysstat.service is solved. But haveged.service still fails
  19. Hi Werner, I realized already that my armbian install has 1GB swap assigned to zram and I was not clear where this originates from :-) After examining /etc/default/armbian-zram-config I understand that this corresponds to the default value of 50% of my existing RAM (2GB on the ODROID-HC2). Thanks for that information and pointing to that direction. A) I have configured 4GB swap space on my own (hard disk), actually I have 5GB in summary. Do I really need zram-config at all or can I disable it in the mentioned configuration file and what the pro/con ? B) I do not understand yet where the 50MB for my /var/log mount comes from? How can I adjust/extend this size, didn't find anything related to /var/log in /etc/default/armbian-zram-config ? thank you in advance.
  20. Well, I was wrong about the remaining free space in file systems. I did some more research with those services and the logs revealed that they cannot write to /var/log/foo.log df -h shows: udev 925M 0 925M 0% /dev tmpfs 200M 8,0M 192M 4% /run /dev/mapper/rootfs 32G 1,3G 29G 5% / tmpfs 996M 0 996M 0% /dev/shm tmpfs 5,0M 4,0K 5,0M 1% /run/lock tmpfs 996M 0 996M 0% /tmp /dev/zram1 49M 48M 0 100% /var/log tmpfs 200M 0 200M 0% /run/user/1000 what is zram1 and why is it so small (50MB) ? how can I correct this? can you share some information about this strange zram1 filesystem that is mounted to /var/log ? I also see a /var/log.hdd on my system, what's that and what's the difference between those?
  21. Hello everybody, I am using Armbian Bullseye image on an ODROID-HC2 and I moved the root filesystem to an encrypted SATA drive. During boot in UART / USB serial console I see that two services fail to start: Resets System Activity Logs and Haveged [...] [ OK ] Reached target Sockets. Starting Armbian hardware monitoring... Starting Armbian hardware optimization... [ OK ] Started RPC bind portmap service. [ OK ] Finished Armbian hardware monitoring. [ OK ] Reached target Remote File Systems (Pre). [ OK ] Reached target Remote File Systems. [ OK ] Reached target RPC Port Mapper. [ OK ] Stopped Entropy Daemon based on the HAVEGE algorithm. [ OK ] Started Entropy Daemon based on the HAVEGE algorithm. [ OK ] Finished Armbian hardware optimization. [ OK ] Reached target Basic System. Starting Save/Restore Sound Card State... [ OK ] Started Regular background program processing daemon. [ OK ] Started D-Bus System Message Bus. Starting Network Manager... Starting Remove Stale Onli…t4 Metadata Check Snapshots... Starting LSB: Load kernel …d to enable cpufreq scaling... Starting Dispatcher daemon for systemd-networkd... Starting System Logging Service... Starting Self Monitoring a…g Technology (SMART) Daemon... Starting Resets System Activity Logs... Starting User Login Management... Starting WPA supplicant... [ OK ] Started System Logging Service. [ OK ] Finished Save/Restore Sound Card State. [ OK ] Reached target Sound Card. [ OK ] Stopped Entropy Daemon based on the HAVEGE algorithm. [ OK ] Started Entropy Daemon based on the HAVEGE algorithm. [ OK ] Started WPA supplicant. [FAILED] Failed to start Resets System Activity Logs. See 'systemctl status sysstat.service' for details. [ OK ] Stopped Entropy Daemon based on the HAVEGE algorithm. [ OK ] Started Entropy Daemon based on the HAVEGE algorithm. [ OK ] Started Self Monitoring an…ing Technology (SMART) Daemon. [ OK ] Started User Login Management. [ OK ] Stopped Entropy Daemon based on the HAVEGE algorithm. [ OK ] Started Entropy Daemon based on the HAVEGE algorithm. [ OK ] Finished Remove Stale Onli…ext4 Metadata Check Snapshots. [ OK ] Started LSB: Load kernel m…ded to enable cpufreq scaling. Starting LSB: set CPUFreq kernel parameters... [ OK ] Stopped Entropy Daemon based on the HAVEGE algorithm. [FAILED] Failed to start Entropy Da…based on the HAVEGE algorithm. See 'systemctl status haveged.service' for details. [ OK ] Started LSB: set CPUFreq kernel parameters. Starting LSB: Set sysfs variables from /etc/sysfs.conf... [ OK ] Started LSB: Set sysfs variables from /etc/sysfs.conf. [ OK ] Started Network Manager. [ OK ] Reached target Network. [ OK ] Reached target Network is Online. Starting chrony, an NTP client/server... [...] the logs saying... The line "Okt 27 18:09:02 myhost sa1[992]: Daten können nicht in die Systemaktivitätendatei geschrieben werden: Auf dem Gerät ist kein Sp>" is truncated but it says, that there is no space available (german language). I have no idea which process and service (sa1??) that is and where it tries to output any data. Possibly that this is causing the error. It seems I can manually start sysstat.service successfully ... systemctl start haveged.service && systemctl status haveged.service haveged.service cannot be restarted manually, it still fails ... but it seems I can start the haveged process manually, I see no errors here and the process runs until I abort with keypress CTRL+C root@myhostname:~# /usr/sbin/haveged --Foreground --verbose=1 haveged: command socket is listening at fd 3 haveged starting up haveged: ver: 1.9.14; arch: generic; vend: ; build: (gcc 10.2.1 CTV); collect: 128K haveged: cpu: (VC); data: 16K (D); inst: 16K (D); idx: 12/40; sz: 15006/57790 haveged: tot tests(BA8): A:1/1 B:1/1 continuous tests(B): last entropy estimate 8.00131 haveged: fills: 0, generated: 0 Question 1) Why does the sysstat.service fail in starting at the boot process but works ok when manually initiiated ? Question 2) Why does haveged.service fail at all in starting ? df -h shows plenty of free space available on all my mounts and partitions. I have absolutely no clue where to begin to dig. Any clues?
  22. Hi Steven, thanks for your feedback and thanks again for your suggestion that led me to the right direction. Yeah, the .next file was missing after I did the encryption stuff mentioned here, no clue why. So I wrote everything in detail, maybe the devs can look over it and tell us more and even fix it if there's something to fix. Thanks for the hint about net.ifnames=0 I will try that and report back. I'm happy right now.
  23. Hi Steven, my /boot partition contains following files: root@myhost:/boot# ls -lh insgesamt 40760 -rw-r--r-- 1 root root 69 24. Okt 10:12 armbianEnv.txt -rw-r--r-- 1 root root 1536 8. Okt 22:11 armbian_first_run.txt.template lrwxrwxrwx 1 root root 1 23. Okt 18:49 boot -> . -rw-r--r-- 1 root root 38518 8. Okt 22:10 boot.bmp -rw-r--r-- 1 root root 13370 8. Okt 22:11 boot.ini -rw-r--r-- 1 root root 169628 8. Okt 21:52 config-5.4.151-odroidxu4 lrwxrwxrwx 1 root root 21 8. Okt 22:10 dtb -> dtb-5.4.151-odroidxu4 drwxr-xr-x 3 root root 3072 8. Okt 22:10 dtb-5.4.151-odroidxu4 -rw------- 1 root root 11083111 23. Okt 19:07 initrd.img-5.4.151-odroidxu4 -rw-r--r-- 1 root root 8796913 8. Okt 22:12 initrd.img-5.4.151-odroidxu4.bak drwx------ 2 root root 12288 23. Okt 18:49 lost+found -rw-r--r-- 1 root root 3193792 8. Okt 21:52 System.map-5.4.151-odroidxu4 lrwxrwxrwx 1 root root 25 23. Okt 19:07 uInitrd -> uInitrd-5.4.151-odroidxu4 -rw-r--r-- 1 root root 11083175 23. Okt 19:07 uInitrd-5.4.151-odroidxu4 -rwxr-xr-x 1 root root 7337840 8. Okt 21:52 vmlinuz-5.4.151-odroidxu4 lrwxrwxrwx 1 root root 25 8. Okt 22:10 zImage -> vmlinuz-5.4.151-odroidxu4 the original boot.ini of the Armbian Bullseye image at the end looks like that: [...] # this is for mainline only if test "${board_name}" = "xu4"; then setenv fdtfile "exynos5422-odroidxu4.dtb"; fi if test "${board_name}" = "xu3"; then setenv fdtfile "exynos5422-odroidxu3.dtb"; fi if test "${board_name}" = "xu3l"; then setenv fdtfile "exynos5422-odroidxu3-lite.dtb"; fi if test "${board_name}" = "hc1"; then setenv fdtfile "exynos5422-odroidhc1.dtb"; fi # legacy shares a single DT for all boards if ext4load mmc 0:1 0x00000000 "/boot/.next" || fatload mmc 0:1 0x00000000 ".next" || ext4load mmc 0:1 0x00000000 ".next"; then echo "Found mainline kernel configuration"; else setenv fdtfile "exynos5422-odroidxu3.dtb"; fi ext4load mmc 0:1 0x44000000 /boot/dtb/${fdtfile} || fatload mmc 0:1 0x44000000 dtb/${fdtfile} || ext4load mmc 0:1 0x44000000 dtb/${fdtfile} # set FDT address fdt addr 0x44000000 As I understand the above code it should detect the correct board and assign the corresponding dtb to the boot process. Nevertheless, to ensure the correct .dtb file is used during the boot process I did following. First I backed up the original ./dtb folder that contained following files and folder: -rw-r--r-- 1 root root 40978 8. Okt 21:52 exynos3250-artik5-eval.dtb -rw-r--r-- 1 root root 52553 8. Okt 21:52 exynos3250-monk.dtb -rw-r--r-- 1 root root 58000 8. Okt 21:52 exynos3250-rinato.dtb -rw-r--r-- 1 root root 60049 8. Okt 21:52 exynos4210-origen.dtb -rw-r--r-- 1 root root 56580 8. Okt 21:52 exynos4210-smdkv310.dtb -rw-r--r-- 1 root root 62387 8. Okt 21:52 exynos4210-trats.dtb -rw-r--r-- 1 root root 63638 8. Okt 21:52 exynos4210-universal_c210.dtb -rw-r--r-- 1 root root 101479 8. Okt 21:52 exynos4412-i9300.dtb -rw-r--r-- 1 root root 101479 8. Okt 21:52 exynos4412-i9305.dtb -rw-r--r-- 1 root root 75175 8. Okt 21:52 exynos4412-itop-elite.dtb -rw-r--r-- 1 root root 99301 8. Okt 21:52 exynos4412-n710x.dtb -rw-r--r-- 1 root root 73351 8. Okt 21:52 exynos4412-odroidu3.dtb -rw-r--r-- 1 root root 73348 8. Okt 21:52 exynos4412-odroidx2.dtb -rw-r--r-- 1 root root 73159 8. Okt 21:52 exynos4412-odroidx.dtb -rw-r--r-- 1 root root 72354 8. Okt 21:52 exynos4412-origen.dtb -rw-r--r-- 1 root root 64137 8. Okt 21:52 exynos4412-smdk4412.dtb -rw-r--r-- 1 root root 62778 8. Okt 21:52 exynos4412-tiny4412.dtb -rw-r--r-- 1 root root 101532 8. Okt 21:52 exynos4412-trats2.dtb -rw-r--r-- 1 root root 62905 8. Okt 21:52 exynos5250-arndale.dtb -rw-r--r-- 1 root root 58414 8. Okt 21:52 exynos5250-smdk5250.dtb -rw-r--r-- 1 root root 64437 8. Okt 21:52 exynos5250-snow.dtb -rw-r--r-- 1 root root 64474 8. Okt 21:52 exynos5250-snow-rev5.dtb -rw-r--r-- 1 root root 60444 8. Okt 21:52 exynos5250-spring.dtb -rw-r--r-- 1 root root 22636 8. Okt 21:52 exynos5260-xyref5260.dtb -rw-r--r-- 1 root root 44973 8. Okt 21:52 exynos5410-odroidxu.dtb -rw-r--r-- 1 root root 33750 8. Okt 21:52 exynos5410-smdk5410.dtb -rw-r--r-- 1 root root 78923 8. Okt 21:52 exynos5420-arndale-octa.dtb -rw-r--r-- 1 root root 87616 8. Okt 21:52 exynos5420-peach-pit.dtb -rw-r--r-- 1 root root 73226 8. Okt 21:52 exynos5420-smdk5420.dtb -rw-r--r-- 1 root root 82592 8. Okt 21:52 exynos5422-odroidhc1.dtb -rw-r--r-- 1 root root 88701 8. Okt 21:52 exynos5422-odroidxu3.dtb -rw-r--r-- 1 root root 88210 8. Okt 21:52 exynos5422-odroidxu3-lite.dtb -rw-r--r-- 1 root root 87877 8. Okt 21:52 exynos5422-odroidxu4.dtb -rw-r--r-- 1 root root 88102 8. Okt 21:52 exynos5800-peach-pi.dtb drwxr-xr-x 2 root root 1024 8. Okt 22:10 overlays then I wiped the /boot/dtb content except the correct .dtb which is the odroidxu4.dtb for my board ODROID-HC2, I also kept the overlay folder in that directory. That being said, my /boot/dtb looks like that: root@myhost:/boot/dtb]# ls -lh * -rw-r--r-- 1 root root 86K 24. Okt 10:31 exynos5422-odroidxu4.dtb overlays: -rw-r--r-- 1 root root 1,7K 24. Okt 10:33 ads7846.dtbo -rw-r--r-- 1 root root 1,3K 24. Okt 10:33 hktft32.dtbo -rw-r--r-- 1 root root 1,8K 24. Okt 10:33 hktft35.dtbo -rw-r--r-- 1 root root 1,5K 24. Okt 10:33 hktft-cs-ogst.dtbo -rw-r--r-- 1 root root 224 24. Okt 10:33 i2c0.dtbo -rw-r--r-- 1 root root 226 24. Okt 10:33 i2c1.dtbo -rw-r--r-- 1 root root 417 24. Okt 10:33 onewire.dtbo -rw-r--r-- 1 root root 691 24. Okt 10:33 spi0.dtbo -rw-r--r-- 1 root root 792 24. Okt 10:33 sx865x-i2c1.dtbo -rw-r--r-- 1 root root 227 24. Okt 10:33 uart0.dtbo now when I boot the u-boot serial log throws these errors: U-Boot 2017.05-armbian (Oct 08 2021 - 19:51:17 +0000) for ODROID-XU4 CPU: Exynos5422 @ 800 MHz Model: Odroid XU4 based on EXYNOS5422 Board: Odroid XU4 based on EXYNOS5422 Type: unknown DRAM: 2 GiB MMC: EXYNOS DWMMC: 0, EXYNOS DWMMC: 1 MMC Device 0 ( SD ): 29.8 GiB Card did not respond to voltage select! mmc_init: -95, time 11 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: No ethernet found. Press quickly 'Enter' twice to stop autoboot: 0 13370 bytes read in 45 ms (290 KiB/s) ## Executing script at 43e00000 69 bytes read in 86 ms (0 Bytes/s) 7337840 bytes read in 813 ms (8.6 MiB/s) 11083175 bytes read in 1149 ms (9.2 MiB/s) ** File not found /boot/.next ** ** Unrecognized filesystem type ** ** File not found .next ** ** File not found /boot/dtb/exynos5422-odroidxu3.dtb ** ** Unrecognized filesystem type ** ** File not found dtb/exynos5422-odroidxu3.dtb ** libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! Kernel image @ 0x40008000 [ 0x000000 - 0x6ff770 ] ## Loading init Ramdisk from Legacy Image at 42000000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 11083111 Bytes = 10.6 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree 13370 bytes read in 62 ms (210 KiB/s) ## Executing script at 43e00000 69 bytes read in 86 ms (0 Bytes/s) 7337840 bytes read in 815 ms (8.6 MiB/s) 11083175 bytes read in 1178 ms (9 MiB/s) ** File not found /boot/.next ** ** Unrecognized filesystem type ** ** File not found .next ** ** File not found /boot/dtb/exynos5422-odroidxu3.dtb ** ** Unrecognized filesystem type ** ** File not found dtb/exynos5422-odroidxu3.dtb ** libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! Kernel image @ 0x40008000 [ 0x000000 - 0x6ff770 ] ## Loading init Ramdisk from Legacy Image at 42000000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 11083111 Bytes = 10.6 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree ** File not found /boot.scr ** ## Executing script at 43e00000 69 bytes read in 86 ms (0 Bytes/s) 7337840 bytes read in 813 ms (8.6 MiB/s) 11083175 bytes read in 1149 ms (9.2 MiB/s) ** File not found /boot/.next ** ** Unrecognized filesystem type ** ** File not found .next ** ** File not found /boot/dtb/exynos5422-odroidxu3.dtb ** ** Unrecognized filesystem type ** ** File not found dtb/exynos5422-odroidxu3.dtb ** libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! Kernel image @ 0x40008000 [ 0x000000 - 0x6ff770 ] ## Loading init Ramdisk from Legacy Image at 42000000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 11083111 Bytes = 10.6 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree Unknown command '�ኧ' - try 'help' Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** ## Executing script at 43e00000 69 bytes read in 87 ms (0 Bytes/s) 7337840 bytes read in 811 ms (8.6 MiB/s) 11083175 bytes read in 1147 ms (9.2 MiB/s) ** File not found /boot/.next ** ** Unrecognized filesystem type ** ** File not found .next ** ** File not found /boot/dtb/exynos5422-odroidxu3.dtb ** ** Unrecognized filesystem type ** ** File not found dtb/exynos5422-odroidxu3.dtb ** libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! Kernel image @ 0x40008000 [ 0x000000 - 0x6ff770 ] ## Loading init Ramdisk from Legacy Image at 42000000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 11083111 Bytes = 10.6 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree Unknown command '�ኧ' - try 'help' Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** ## Executing script at 43e00000 69 bytes read in 87 ms (0 Bytes/s) 7337840 bytes read in 817 ms (8.6 MiB/s) 11083175 bytes read in 1151 ms (9.2 MiB/s) ** File not found /boot/.next ** ** Unrecognized filesystem type ** ** File not found .next ** ** File not found /boot/dtb/exynos5422-odroidxu3.dtb ** ** Unrecognized filesystem type ** ** File not found dtb/exynos5422-odroidxu3.dtb ** libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! Kernel image @ 0x40008000 [ 0x000000 - 0x6ff770 ] ## Loading init Ramdisk from Legacy Image at 42000000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 11083111 Bytes = 10.6 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree Unknown command '�ኧ' - try 'help' Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** ## Executing script at 43e00000 69 bytes read in 86 ms (0 Bytes/s) 7337840 bytes read in 815 ms (8.6 MiB/s) 11083175 bytes read in 1148 ms (9.2 MiB/s) ** File not found /boot/.next ** ** Unrecognized filesystem type ** ** File not found .next ** ** File not found /boot/dtb/exynos5422-odroidxu3.dtb ** ** Unrecognized filesystem type ** ** File not found dtb/exynos5422-odroidxu3.dtb ** libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! Kernel image @ 0x40008000 [ 0x000000 - 0x6ff770 ] ## Loading init Ramdisk from Legacy Image at 42000000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 11083111 Bytes = 10.6 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree Unknown command '�ኧ' - try 'help' mmc_init: -110, time 121 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... starting USB... USB0: USB EHCI 1.00 USB1: Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.00 USB2: Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 1 for devices... cannot reset port 1!? 1 USB Device(s) found scanning bus 2 for devices... 2 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found scanning usb for ethernet devices... 1 Ethernet Device(s) found USB device 0: unknown device Waiting for Ethernet connection... done. BOOTP broadcast 1 Now it's clear, that it is trying to find the wrong odroidxu3 although my board ODROID-HC2 should be discovered as an odroidxu4. Well, I compared the u-boot serial log of the unencrypted initial Armbian Bullseye image which outputs the string "Found mainline kernel configuration". This string is generated by the boot.ini script, means that the board was discovered correctly and the correct image file was set as result. However, after the encryption it looks to me that this test fails somehow and the legacy image odroidxu3 is assigned, which is wrong of course. I modified the boot.ini and manually assigned the odroidxu4.dtb file to see what happens: # this is for mainline only #if test "${board_name}" = "xu4"; then setenv fdtfile "exynos5422-odroidxu4.dtb"; fi #if test "${board_name}" = "xu3"; then setenv fdtfile "exynos5422-odroidxu3.dtb"; fi #if test "${board_name}" = "xu3l"; then setenv fdtfile "exynos5422-odroidxu3-lite.dtb"; fi #if test "${board_name}" = "hc1"; then setenv fdtfile "exynos5422-odroidhc1.dtb"; fi setenv fdtfile "exynos5422-odroidxu4.dtb" # legacy shares a single DT for all boards #if ext4load mmc 0:1 0x00000000 "/boot/.next" || fatload mmc 0:1 0x00000000 ".next" || ext4load mmc 0:1 0x00000000 ".next"; then echo "Found mainline kernel configuration"; else setenv fdtfile "exynos5422-odroidxu3.dtb"; fi if ext4load mmc 0:1 0x00000000 "/boot/.next" || fatload mmc 0:1 0x00000000 ".next" || ext4load mmc 0:1 0x00000000 ".next"; then echo "Found mainline kernel configuration"; else echo "manually set fdtfile to exynos5422-odroidxu4.dtb"; fi ext4load mmc 0:1 0x44000000 /boot/dtb/${fdtfile} || fatload mmc 0:1 0x44000000 dtb/${fdtfile} || ext4load mmc 0:1 0x44000000 dtb/${fdtfile} Now see here, seems we have the correct .dtb file loaded. Looks good... U-Boot 2017.05-armbian (Oct 08 2021 - 19:51:17 +0000) for ODROID-XU4 CPU: Exynos5422 @ 800 MHz Model: Odroid XU4 based on EXYNOS5422 Board: Odroid XU4 based on EXYNOS5422 Type: unknown DRAM: 2 GiB MMC: EXYNOS DWMMC: 0, EXYNOS DWMMC: 1 MMC Device 0 ( SD ): 29.8 GiB Card did not respond to voltage select! mmc_init: -95, time 11 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: No ethernet found. Press quickly 'Enter' twice to stop autoboot: 0 13651 bytes read in 44 ms (302.7 KiB/s) ## Executing script at 43e00000 69 bytes read in 86 ms (0 Bytes/s) 7337840 bytes read in 813 ms (8.6 MiB/s) 11083175 bytes read in 1149 ms (9.2 MiB/s) ** File not found /boot/.next ** ** Unrecognized filesystem type ** ** File not found .next ** manually set fdtfile to exynos5422-odroidxu4.dtb 87877 bytes read in 107 ms (801.8 KiB/s) libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND Kernel image @ 0x40008000 [ 0x000000 - 0x6ff770 ] ## Loading init Ramdisk from Legacy Image at 42000000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 11083111 Bytes = 10.6 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 44000000 Booting using the fdt blob at 0x44000000 Using Device Tree in place at 44000000, end 44018744 Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x100 [ 0.000000] Linux version 5.4.151-odroidxu4 (root@big-37) (gcc version 8.3.0 (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36))) #21.08.3 SMP PREEMPT Fri Oct 8 19:1 [ 0.000000] CPU: ARMv7 Processor [410fc073] revision 3 (ARMv7), cr=10c5387d [ 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 0xb6800000 [ 0.000000] Samsung CPU ID: 0xe5422001 [ 0.000000] Running under secure firmware. [ 0.000000] percpu: Embedded 20 pages/cpu s51852 r8192 d21876 u81920 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 516928 [ 0.000000] Kernel command line: console=ttySAC2,115200n8 consoleblank=0 loglevel=7 root=/dev/mapper/rootfs rootfstype=ext4 rootwait rw smsc95xx.macaddr=00:1e:06:61:7a:55 governor=perf [ 0.000000] hdmi: using HDMI mode [ 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:on, heap free:off [ 0.000000] Memory: 1895308K/2074624K available (11264K kernel code, 719K rwdata, 3020K rodata, 1024K init, 297K bss, 48244K reserved, 131072K cma-reserved, 1157120K highmem) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1 [ 0.000000] rcu: Preemptible hierarchical RCU implementation. [ 0.000000] 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] random: get_random_bytes called from start_kernel+0x36c/0x540 with crng_init=0 [ 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.000007] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns [ 0.000031] genirq: irq_chip COMBINER did not update eff. affinity mask of irq 49 [ 0.001683] arch_timer: cp15 timer(s) running at 24.00MHz (phys). [ 0.001704] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns [ 0.001725] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns [ 0.001738] Ignoring duplicate/late registration of read_current_timer delay [ 0.002325] Console: colour dummy device 80x30 [ 0.002374] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=240000) [ 0.002390] pid_max: default: 32768 minimum: 301 [ 0.002560] LSM: Security Framework initializing [ 0.002608] Yama: becoming mindful. [ 0.002986] AppArmor: AppArmor initialized [ 0.003064] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes, linear) [ 0.003087] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes, linear) [ 0.003179] *** VALIDATE tmpfs *** [ 0.003929] *** VALIDATE proc *** [ 0.004297] *** VALIDATE cgroup1 *** [ 0.004312] *** VALIDATE cgroup2 *** [ 0.004372] CPU: Testing write buffer coherency: ok [ 0.005015] CPU0: thread -1, cpu 0, socket 1, mpidr 80000100 [ 0.005964] Setting up static identity map for 0x40100000 - 0x40100060 [ 0.006277] ARM CCI driver probed [ 0.006875] Exynos MCPM support installed [ 0.007185] rcu: Hierarchical SRCU implementation. [ 0.009710] soc soc0: Exynos: CPU[EXYNOS5800] PRO_ID[0xe5422001] REV[0x1] Detected [ 0.010387] smp: Bringing up secondary CPUs ... [ 0.011449] CPU1: thread -1, cpu 1, socket 1, mpidr 80000101 [ 0.012686] CPU2: thread -1, cpu 2, socket 1, mpidr 80000102 [ 0.013838] CPU3: thread -1, cpu 3, socket 1, mpidr 80000103 [ 0.014989] CPU4: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.014998] CPU4: detected I-Cache line size mismatch, workaround enabled [ 0.015005] CPU4: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable [ 0.016272] CPU5: thread -1, cpu 1, socket 0, mpidr 80000001 [ 0.016279] CPU5: detected I-Cache line size mismatch, workaround enabled [ 0.016286] CPU5: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable [ 0.017529] CPU6: thread -1, cpu 2, socket 0, mpidr 80000002 [ 0.017537] CPU6: detected I-Cache line size mismatch, workaround enabled [ 0.017543] CPU6: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable [ 0.018756] CPU7: thread -1, cpu 3, socket 0, mpidr 80000003 [ 0.018764] CPU7: detected I-Cache line size mismatch, workaround enabled [ 0.018770] CPU7: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable [ 0.018971] smp: Brought up 1 node, 8 CPUs [ 0.018989] SMP: Total of 8 processors activated (384.00 BogoMIPS). [ 0.018998] CPU: All CPU(s) started in HYP mode. [ 0.019005] CPU: Virtualization extensions available. [ 0.020050] devtmpfs: initialized [ 0.041271] VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0 [ 0.041633] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns [ 0.041696] futex hash table entries: 2048 (order: 5, 131072 bytes, linear) [ 0.044334] xor: measuring software checksum speed [ 0.139951] arm4regs : 1515.600 MB/sec [ 0.239955] 8regs : 1237.200 MB/sec [ 0.339955] 32regs : 1231.600 MB/sec [ 0.439953] neon : 2208.000 MB/sec [ 0.439964] xor: using function: neon (2208.000 MB/sec) [ 0.440014] pinctrl core: initialized pinctrl subsystem [ 0.442413] NET: Registered protocol family 16 [ 0.445901] DMA: preallocated 2048 KiB pool for atomic coherent allocations [ 0.447421] audit: initializing netlink subsys (disabled) [ 0.447665] audit: type=2000 audit(0.440:1): state=initialized audit_enabled=0 res=1 [ 0.448507] cpuidle: using governor menu [ 0.449204] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers. [ 0.449216] hw-breakpoint: maximum watchpoint size is 8 bytes. [ 0.555213] EXYNOS5420 PMU initialized [ 0.653846] random: fast init done [ 0.787353] cryptd: max_cpu_qlen set to 1000 [ 0.959977] raid6: neonx8 gen() 1468 MB/s [ 1.129983] raid6: neonx8 xor() 1187 MB/s [ 1.299984] raid6: neonx4 gen() 1342 MB/s [ 1.469975] raid6: neonx4 xor() 1193 MB/s [ 1.639973] raid6: neonx2 gen() 1051 MB/s [ 1.809979] raid6: neonx2 xor() 1335 MB/s [ 1.979993] raid6: neonx1 gen() 719 MB/s [ 2.149981] raid6: neonx1 xor() 1001 MB/s [ 2.320084] raid6: int32x8 gen() 378 MB/s [ 2.490081] raid6: int32x8 xor() 269 MB/s [ 2.660062] raid6: int32x4 gen() 368 MB/s [ 2.830047] raid6: int32x4 xor() 283 MB/s [ 3.000146] raid6: int32x2 gen() 267 MB/s [ 3.170037] raid6: int32x2 xor() 263 MB/s [ 3.340124] raid6: int32x1 gen() 180 MB/s [ 3.510061] raid6: int32x1 xor() 204 MB/s [ 3.510072] raid6: using algorithm neonx8 gen() 1468 MB/s [ 3.510082] raid6: .... xor() 1187 MB/s, rmw enabled [ 3.510092] raid6: using neon recovery algorithm [ 3.512153] iommu: Default domain type: Translated [ 3.512549] usbcore: registered new interface driver usbfs [ 3.512609] usbcore: registered new interface driver hub [ 3.512667] usbcore: registered new device driver usb [ 3.513291] s3c-i2c 12c80000.i2c: slave address 0x00 [ 3.513309] s3c-i2c 12c80000.i2c: bus frequency set to 65 KHz [ 3.513580] s3c-i2c 12c80000.i2c: i2c-2: S3C I2C adapter [ 3.514044] mc: Linux media interface: v0.10 [ 3.514087] videodev: Linux video capture interface: v2.00 [ 3.514572] Advanced Linux Sound Architecture Driver Initialized. [ 3.515155] NetLabel: Initializing [ 3.515167] NetLabel: domain hash size = 128 [ 3.515177] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO [ 3.515251] NetLabel: unlabeled traffic allowed by default [ 3.515858] clocksource: Switched to clocksource mct-frc [ 3.616211] *** VALIDATE bpf *** [ 3.616390] VFS: Disk quotas dquot_6.6.0 [ 3.616467] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 3.616577] *** VALIDATE ramfs *** [ 3.617320] AppArmor: AppArmor Filesystem Enabled [ 3.630635] thermal_sys: Registered thermal governor 'step_wise' [ 3.633044] NET: Registered protocol family 2 [ 3.633206] IP idents hash table entries: 16384 (order: 5, 131072 bytes, linear) [ 3.634376] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear) [ 3.634422] TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear) [ 3.634524] TCP bind hash table entries: 8192 (order: 4, 65536 bytes, linear) [ 3.634681] TCP: Hash tables configured (established 8192 bind 8192) [ 3.634817] UDP hash table entries: 512 (order: 2, 16384 bytes, linear) [ 3.634867] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear) [ 3.635119] NET: Registered protocol family 1 [ 3.635387] Trying to unpack rootfs image as initramfs... [ 4.306869] Freeing initrd memory: 10824K [ 4.308804] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 5 counters available [ 4.309649] hw perfevents: enabled with armv7_cortex_a15 PMU driver, 7 counters available [ 4.311610] Initialise system trusted keyrings [ 4.311660] Key type blacklist registered [ 4.311893] workingset: timestamp_bits=14 max_order=19 bucket_order=5 [ 4.321163] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 4.322205] fuse: init (API version 7.31) [ 4.322330] *** VALIDATE fuse *** [ 4.322346] *** VALIDATE fuse *** [ 4.323623] Platform Keyring initialized [ 4.355450] Key type asymmetric registered [ 4.355464] Asymmetric key parser 'x509' registered [ 4.355608] bounce: pool size: 64 pages [ 4.355655] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247) [ 4.355903] io scheduler mq-deadline registered [ 4.355915] io scheduler kyber registered [ 4.355963] io scheduler bfq registered [ 4.358539] samsung-usb2-phy 12130000.phy: 12130000.phy supply vbus not found, using dummy regulator [ 4.359548] exynos5_usb3drd_phy 12100000.phy: 12100000.phy supply vbus not found, using dummy regulator [ 4.359638] exynos5_usb3drd_phy 12100000.phy: 12100000.phy supply vbus-boost not found, using dummy regulator [ 4.360037] exynos5_usb3drd_phy 12500000.phy: 12500000.phy supply vbus not found, using dummy regulator [ 4.360123] exynos5_usb3drd_phy 12500000.phy: 12500000.phy supply vbus-boost not found, using dummy regulator [ 4.369469] dma-pl330 121a0000.pdma: Loaded driver for PL330 DMAC-241330 [ 4.369486] dma-pl330 121a0000.pdma: DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32 [ 4.372235] dma-pl330 121b0000.pdma: Loaded driver for PL330 DMAC-241330 [ 4.372251] dma-pl330 121b0000.pdma: DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32 [ 4.373141] dma-pl330 10800000.mdma: Loaded driver for PL330 DMAC-241330 [ 4.373156] dma-pl330 10800000.mdma: DBUFF-64x8bytes Num_Chans-8 Num_Peri-1 Num_Events-32 [ 4.445675] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [ 4.448097] 12c20000.serial: ttySAC2 at MMIO 0x12c20000 (irq = 62, base_baud = 0) is a S3C6400/10 [ 5.486059] printk: console [ttySAC2] enabled [ 5.492027] exynos-trng 10830600.rng: Exynos True Random Number Generator. [ 5.498946] exynos-mixer 14450000.mixer: Adding to iommu group 0 [ 5.524639] brd: module loaded [ 5.526974] libphy: Fixed MDIO Bus: probed [ 5.530626] usbcore: registered new interface driver r8152 [ 5.535790] usbcore: registered new interface driver cdc_ether [ 5.541661] usbcore: registered new interface driver cdc_subset [ 5.549702] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 5.554761] ehci-exynos: EHCI EXYNOS driver [ 5.559315] exynos-ehci 12110000.usb: EHCI Host Controller [ 5.564384] exynos-ehci 12110000.usb: new USB bus registered, assigned bus number 1 [ 5.572398] exynos-ehci 12110000.usb: irq 79, io mem 0x12110000 [ 5.598026] dma-pl330 3880000.adma: Loaded driver for PL330 DMAC-241330 [ 5.603154] dma-pl330 3880000.adma: DBUFF-4x8bytes Num_Chans-6 Num_Peri-16 Num_Events-6 [ 5.605969] exynos-ehci 12110000.usb: USB 2.0 started, EHCI 1.00 [ 5.617498] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04 [ 5.625423] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 5.632655] usb usb1: Product: EHCI Host Controller [ 5.636423] dma-pl330 3880000.adma: PM domain MAU will not be powered off [ 5.637509] usb usb1: Manufacturer: Linux 5.4.151-odroidxu4 ehci_hcd [ 5.650583] usb usb1: SerialNumber: 12110000.usb [ 5.655772] hub 1-0:1.0: USB hub found [ 5.658961] hub 1-0:1.0: 3 ports detected [ 5.663812] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 5.669062] ohci-exynos: OHCI EXYNOS driver [ 5.673365] exynos-ohci 12120000.usb: USB Host Controller [ 5.678589] exynos-ohci 12120000.usb: new USB bus registered, assigned bus number 2 [ 5.687077] exynos-ohci 12120000.usb: irq 79, io mem 0x12120000 [ 5.760139] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.04 [ 5.766950] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 5.774103] usb usb2: Product: USB Host Controller [ 5.778906] usb usb2: Manufacturer: Linux 5.4.151-odroidxu4 ohci_hcd [ 5.785194] usb usb2: SerialNumber: 12120000.usb [ 5.790400] hub 2-0:1.0: USB hub found [ 5.793548] hub 2-0:1.0: 3 ports detected [ 5.799834] mousedev: PS/2 mouse device common for all mice [ 5.805735] i2c /dev entries driver [ 5.830650] vdd_ldo9: Bringing 3300000uV into 3000000-3000000uV [ 5.847421] vddq_mmc2: Bringing 3300000uV into 2800000-2800000uV [ 5.867605] vdd_sd: Bringing 3300000uV into 2800000-2800000uV [ 5.947748] s5m-rtc s2mps14-rtc: registered as rtc0 [ 5.951700] s2mps11-clk s2mps11-clk: DMA mask not set [ 5.967904] s3c2410-wdt 101d0000.watchdog: watchdog inactive, reset disabled, irq disabled [ 5.975316] device-mapper: uevent: version 1.0.3 [ 5.979703] device-mapper: ioctl: 4.41.0-ioctl (2019-09-16) initialised: dm-devel@redhat.com [ 6.000736] sdhci: Secure Digital Host Controller Interface driver [ 6.005430] sdhci: Copyright(c) Pierre Ossman [ 6.010026] Synopsys Designware Multimedia Card Interface Driver [ 6.016434] dwmmc_exynos 12200000.mmc: IDMAC supports 32-bit address mode. [ 6.022654] dwmmc_exynos 12200000.mmc: Using internal DMA controller. [ 6.029035] dwmmc_exynos 12200000.mmc: Version ID is 250a [ 6.034419] dwmmc_exynos 12200000.mmc: DW MMC controller at irq 81,64 bit host data width,64 deep fifo [ 6.043924] dwmmc_exynos 12200000.mmc: allocated mmc-pwrseq [ 6.066076] mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63) [ 6.087379] dwmmc_exynos 12220000.mmc: IDMAC supports 32-bit address mode. [ 6.092923] dwmmc_exynos 12220000.mmc: Using internal DMA controller. [ 6.099354] dwmmc_exynos 12220000.mmc: Version ID is 250a [ 6.104710] dwmmc_exynos 12220000.mmc: DW MMC controller at irq 82,64 bit host data width,64 deep fifo [ 6.132708] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63) [ 6.156260] s5p-secss 10830000.sss: s5p-sss driver registered [ 6.161030] hidraw: raw HID events driver (C) Jiri Kosina [ 6.179340] exynos-nocp: new NoC Probe device registered: 10ca1000.nocp [ 6.184654] exynos-nocp: new NoC Probe device registered: 10ca1400.nocp [ 6.191266] exynos-nocp: new NoC Probe device registered: 10ca1800.nocp [ 6.197823] exynos-nocp: new NoC Probe device registered: 10ca1c00.nocp [ 6.204665] exynos-ppmu: new PPMU device registered 10d00000.ppmu (ppmu-event3-dmc0_0) [ 6.212830] exynos-ppmu: new PPMU device registered 10d10000.ppmu (ppmu-event3-dmc0_1) [ 6.220382] exynos-ppmu: new PPMU device registered 10d60000.ppmu (ppmu-event3-dmc1_0) [ 6.228121] exynos-ppmu: new PPMU device registered 10d70000.ppmu (ppmu-event3-dmc1_1) [ 6.239867] exynos5-dmc 10c20000.memory-controller: DMC initialized, in irq mode: 0 [ 6.246857] exynos-adc 12d10000.adc: IRQ index 1 not found [ 6.256216] samsung-i2s 3830000.i2s-sec: DMA channels sourced from device 3830000.i2s [ 6.262099] mmc_host mmc1: Bus speed (slot 0) = 200000000Hz (slot req 200000000Hz, actual 200000000HZ div = 0) [ 6.270342] NET: Registered protocol family 17 [ 6.275185] mmc1: new ultra high speed SDR104 SDHC card at address 59b4 [ 6.277067] NET: Registered protocol family 15 [ 6.285110] mmcblk1: mmc1:59b4 EB2MW 29.8 GiB [ 6.288026] Key type dns_resolver registered [ 6.295639] mmcblk1: p1 p2 [ 6.297407] Registering SWP/SWPB emulation handler [ 6.304296] registered taskstats version 1 [ 6.308242] Loading compiled-in X.509 certificates [ 6.317358] Loaded X.509 cert 'Build time autogenerated kernel key: 58f88920dc5a2eb8aefa1a83381c42bc4c4ae8b7' [ 6.326160] Key type ._fscrypt registered [ 6.329760] Key type .fscrypt registered [ 6.336676] Btrfs loaded, crc32c=crc32c-generic [ 6.432044] Key type big_key registered [ 6.455404] Key type encrypted registered [ 6.458007] AppArmor: AppArmor sha1 policy hashing enabled [ 6.516643] exynos-asv 10000000.chipid: cpu0 opp0, freq: 1500 missing [ 6.521639] exynos-asv 10000000.chipid: cpu4 opp0, freq: 2100 missing [ 6.530480] OF: graph: no port node found in /soc/hdmi@14530000 [ 6.536160] [drm] Exynos DRM: using 14450000.mixer device for DMA mapping operations [ 6.542710] exynos-drm exynos-drm: bound 14450000.mixer (ops 0xc0cb2b28) [ 6.549391] exynos-drm exynos-drm: bound 14530000.hdmi (ops 0xc0cb31ac) [ 6.555932] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 6.562470] [drm] No driver support for vblank timestamp query. [ 6.568432] [drm] Cannot find any crtc or sizes [ 6.573522] [drm] Cannot find any crtc or sizes [ 6.577584] [drm] Initialized exynos 1.1.0 20180330 for exynos-drm on minor 0 [ 6.586452] dwc3 12000000.dwc3: Failed to get clk 'ref': -2 [ 6.591389] xhci-hcd xhci-hcd.8.auto: xHCI Host Controller [ 6.596068] xhci-hcd xhci-hcd.8.auto: new USB bus registered, assigned bus number 3 [ 6.604001] xhci-hcd xhci-hcd.8.auto: hcc params 0x0220f04c hci version 0x100 quirks 0x0000000002010010 [ 6.613119] xhci-hcd xhci-hcd.8.auto: irq 159, io mem 0x12000000 [ 6.619316] xhci-hcd xhci-hcd.8.auto: xHCI Host Controller [ 6.624428] xhci-hcd xhci-hcd.8.auto: new USB bus registered, assigned bus number 4 [ 6.632085] xhci-hcd xhci-hcd.8.auto: Host supports USB 3.0 SuperSpeed [ 6.638778] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04 [ 6.646816] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 6.653970] usb usb3: Product: xHCI Host Controller [ 6.658856] usb usb3: Manufacturer: Linux 5.4.151-odroidxu4 xhci-hcd [ 6.665148] usb usb3: SerialNumber: xhci-hcd.8.auto [ 6.670624] hub 3-0:1.0: USB hub found [ 6.673756] hub 3-0:1.0: 1 port detected [ 6.678089] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM. [ 6.685820] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.04 [ 6.693955] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 6.701137] usb usb4: Product: xHCI Host Controller [ 6.705996] usb usb4: Manufacturer: Linux 5.4.151-odroidxu4 xhci-hcd [ 6.712288] usb usb4: SerialNumber: xhci-hcd.8.auto [ 6.717868] hub 4-0:1.0: USB hub found [ 6.720902] hub 4-0:1.0: 1 port detected [ 6.727603] dwc3 12400000.dwc3: Failed to get clk 'ref': -2 [ 6.732559] xhci-hcd xhci-hcd.9.auto: xHCI Host Controller [ 6.737219] xhci-hcd xhci-hcd.9.auto: new USB bus registered, assigned bus number 5 [ 6.745190] xhci-hcd xhci-hcd.9.auto: hcc params 0x0220f04c hci version 0x100 quirks 0x0000000002010010 [ 6.754291] xhci-hcd xhci-hcd.9.auto: irq 160, io mem 0x12400000 [ 6.760557] xhci-hcd xhci-hcd.9.auto: xHCI Host Controller [ 6.765582] xhci-hcd xhci-hcd.9.auto: new USB bus registered, assigned bus number 6 [ 6.773242] xhci-hcd xhci-hcd.9.auto: Host supports USB 3.0 SuperSpeed [ 6.779961] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04 [ 6.787978] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 6.795122] usb usb5: Product: xHCI Host Controller [ 6.800028] usb usb5: Manufacturer: Linux 5.4.151-odroidxu4 xhci-hcd [ 6.806337] usb usb5: SerialNumber: xhci-hcd.9.auto [ 6.811922] hub 5-0:1.0: USB hub found [ 6.814916] hub 5-0:1.0: 1 port detected [ 6.819340] usb usb6: We don't know the algorithms for LPM for this host, disabling LPM. [ 6.827069] usb usb6: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.04 [ 6.835070] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 6.842308] usb usb6: Product: xHCI Host Controller [ 6.847154] usb usb6: Manufacturer: Linux 5.4.151-odroidxu4 xhci-hcd [ 6.853440] usb usb6: SerialNumber: xhci-hcd.9.auto [ 6.859569] hub 6-0:1.0: USB hub found [ 6.862053] hub 6-0:1.0: 1 port detected [ 6.867494] s3c-rtc 101e0000.rtc: rtc disabled, re-enabling [ 6.871824] rtc rtc1: invalid alarm value: 1900-01-01T00:00:00 [ 6.877679] s3c-rtc 101e0000.rtc: registered as rtc1 [ 6.885788] exynos-bus: new bus device registered: soc:bus_wcore ( 84000 KHz ~ 400000 KHz) [ 6.893781] exynos-bus: new bus device registered: soc:bus_noc ( 67000 KHz ~ 100000 KHz) [ 6.901518] exynos-bus: new bus device registered: soc:bus_fsys_apb (100000 KHz ~ 200000 KHz) [ 6.909693] exynos-bus: new bus device registered: soc:bus_fsys (100000 KHz ~ 200000 KHz) [ 6.918301] exynos-bus: new bus device registered: soc:bus_fsys2 ( 75000 KHz ~ 150000 KHz) [ 6.926886] exynos-bus: new bus device registered: soc:bus_mfc ( 96000 KHz ~ 333000 KHz) [ 6.934676] exynos-bus: new bus device registered: soc:bus_gen ( 89000 KHz ~ 267000 KHz) [ 6.942716] exynos-bus: new bus device registered: soc:bus_peri ( 67000 KHz ~ 67000 KHz) [ 6.951101] exynos-bus: new bus device registered: soc:bus_g2d ( 84000 KHz ~ 333000 KHz) [ 6.959012] exynos-bus: new bus device registered: soc:bus_g2d_acp ( 67000 KHz ~ 267000 KHz) [ 6.967348] exynos-bus: new bus device registered: soc:bus_jpeg ( 75000 KHz ~ 300000 KHz) [ 6.975531] exynos-bus: new bus device registered: soc:bus_jpeg_apb ( 84000 KHz ~ 167000 KHz) [ 6.983792] exynos-bus: new bus device registered: soc:bus_disp1_fimd (120000 KHz ~ 200000 KHz) [ 6.992521] exynos-bus: new bus device registered: soc:bus_disp1 (120000 KHz ~ 300000 KHz) [ 7.000804] exynos-bus: new bus device registered: soc:bus_gscl_scaler (150000 KHz ~ 300000 KHz) [ 7.009829] exynos-bus: new bus device registered: soc:bus_mscl ( 84000 KHz ~ 400000 KHz) [ 7.020000] odroid-audio sound: snd-soc-dummy-dai <-> samsung-i2s mapping ok [ 7.025651] odroid-audio sound: i2s-hifi <-> snd-soc-dummy-dai mapping ok [ 7.034398] odroid-audio sound: snd-soc-dummy-dai <-> samsung-i2s-sec mapping ok [ 7.045782] s5m-rtc s2mps14-rtc: setting system clock to 2021-10-24T08:53:25 UTC (1635065605) [ 7.114040] ALSA device list: [ 7.115545] #0: Odroid-XU4 [ 7.120282] Freeing unused kernel memory: 1024K [ 7.167798] Run /init as init process Loading, please wait... Starting version 247.3-6 [ 7.826339] usb 4-1: new SuperSpeed Gen 1 USB device number 2 using xhci-hcd [ 7.858202] usb 4-1: New USB device found, idVendor=152d, idProduct=0578, bcdDevice=31.02 [ 7.864907] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 7.872351] usb 4-1: Product: USB to ATA/ATAPI Bridge [ 7.877154] usb 4-1: Manufacturer: JMicron [ 7.881130] usb 4-1: SerialNumber: 0123456789ABCDEF [ 7.899000] SCSI subsystem initialized [ 7.905981] usbcore: registered new interface driver usb-storage [ 7.921246] scsi host0: uas [ 7.922973] usbcore: registered new interface driver uas [ 7.924229] scsi 0:0:0:0: Direct-Access JMicron Generic 3102 PQ: 0 ANSI: 6 [ 7.994115] gpiomem-exynos 13400000.gpiomem: Initialised: GPIO register area is 3 [ 8.000409] gpiomem-exynos 13400000.gpiomem: Initialised: Registers at 0x13400000 [ 8.007615] gpiomem-exynos 13400000.gpiomem: Initialised: Registers at 0x14010000 [ 8.015015] gpiomem-exynos 13400000.gpiomem: Initialised: Registers at 0x03860000 [ 8.020226] input: gpio_keys as /devices/platform/gpio_keys/input/input0 [ 8.026675] usb 6-1: new SuperSpeed Gen 1 USB device number 2 using xhci-hcd [ 8.067280] usb 6-1: New USB device found, idVendor=0bda, idProduct=8153, bcdDevice=30.00 [ 8.073980] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [ 8.081156] usb 6-1: Product: USB 10/100/1000 LAN [ 8.085795] usb 6-1: Manufacturer: Realtek [ 8.089989] usb 6-1: SerialNumber: 000001000000 [ 8.333169] usb 6-1: reset SuperSpeed Gen 1 USB device number 2 using xhci-hcd [ 8.427393] r8152 6-1:1.0 eth0: v1.10.11 [ 13.905832] sd 0:0:0:0: [sda] Unit Not Ready [ 13.908731] sd 0:0:0:0: [sda] Sense Key : 0x4 [current] [ 13.913941] sd 0:0:0:0: [sda] ASC=0x44 <<vendor>>ASCQ=0x81 [ 13.921040] sd 0:0:0:0: [sda] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=0x08 [ 13.928171] sd 0:0:0:0: [sda] Sense Key : 0x4 [current] [ 13.933371] sd 0:0:0:0: [sda] ASC=0x44 <<vendor>>ASCQ=0x81 [ 13.940043] sd 0:0:0:0: [sda] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=0x08 [ 13.947462] sd 0:0:0:0: [sda] Sense Key : 0x4 [current] [ 13.952695] sd 0:0:0:0: [sda] ASC=0x44 <<vendor>>ASCQ=0x81 [ 13.959185] sd 0:0:0:0: [sda] 0 512-byte logical blocks: (0 B/0 [ 13.964392] sd 0:0:0:0: [sda] 0-byte physical blocks [ 13.970345] sd 0:0:0:0: [sda] Test WP failed, assume Write Enabled [ 13.975808] sd 0:0:0:0: [sda] Asking for cache data failed [ 13.981023] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 13.988112] sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes not a multiple of physical block size (0 bytes) [ 14.097183] sd 0:0:0:0: [sda] Unit Not Ready [ 14.100005] sd 0:0:0:0: [sda] Sense Key : 0x4 [current] [ 14.105289] sd 0:0:0:0: [sda] ASC=0x44 <<vendor>>ASCQ=0x81 [ 14.112257] sd 0:0:0:0: [sda] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=0x08 [ 14.119362] sd 0:0:0:0: [sda] Sense Key : 0x4 [current] [ 14.124600] sd 0:0:0:0: [sda] ASC=0x44 <<vendor>>ASCQ=0x81 [ 14.131381] sd 0:0:0:0: [sda] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=0x08 [ 14.138739] sd 0:0:0:0: [sda] Sense Key : 0x4 [current] [ 14.143963] sd 0:0:0:0: [sda] ASC=0x44 <<vendor>>ASCQ=0x81 [ 14.153152] sd 0:0:0:0: [sda] Attached SCSI disk [ 14.166228] random: crng init done [ 14.268414] s5p-jpeg 11f50000.jpeg: Adding to iommu group 1 [ 14.270695] s5p-mfc 11000000.codec: Adding to iommu group 2 [ 14.279505] s5p-jpeg 11f50000.jpeg: encoder device registered as /dev/video0 [ 14.289846] s5p-jpeg 11f50000.jpeg: decoder device registered as /dev/video1 [ 14.290503] mali 11800000.gpu: GPU identified as 0x0620 r0p1 status 0 [ 14.295438] s5p-jpeg 11f50000.jpeg: Samsung S5P JPEG codec [ 14.302333] mali 11800000.gpu: Protected mode not available [ 14.308586] s5p-jpeg 11f60000.jpeg: Adding to iommu group 3 [ 14.319227] s5p-jpeg 11f60000.jpeg: encoder device registered as /dev/video2 [ 14.319428] exynos-gsc 13e00000.video-scaler: Adding to iommu group 4 [ 14.320070] mali 11800000.gpu: Probed as mali0 [ 14.326194] s5p-jpeg 11f60000.jpeg: decoder device registered as /dev/video3 [ 14.331369] s5p-mfc 11000000.codec: preallocated 8 MiB buffer for the firmware and context buffers [ 14.331447] s5p-mfc 11000000.codec: Direct firmware load for s5p-mfc-v8.fw failed with error -2 [ 14.331454] s5p_mfc_load_firmware:69: Firmware is not present in the /lib/firmware directory nor compiled in kernel [ 14.331608] s5p-mfc 11000000.codec: decoder registered as /dev/video4 [ 14.331702] s5p-mfc 11000000.codec: encoder registered as /dev/video5 [ 14.342766] exynos-gsc 13e10000.video-scaler: Adding to iommu group 5 [ 14.343277] s5p-jpeg 11f60000.jpeg: Samsung S5P JPEG codec [ 14.748723] usb 6-1: reset SuperSpeed Gen 1 USB device number 2 using xhci-hcd [ 14.832905] r8152 6-1:1.0 eth0: v1.10.11 [ 14.871564] r8152 6-1:1.0 enx001e06380848: renamed from eth0 Begin: Loading essential drivers ... [ 15.872455] loop: module loaded [ 16.027989] zram: Added device: zram0 [ 16.059202] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 16.280580] RPC: Registered named UNIX socket transport module. [ 16.285013] RPC: Registered udp transport module. [ 16.289789] RPC: Registered tcp transport module. [ 16.294372] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 16.369570] NET: Registered protocol family 10 [ 16.373465] Segment Routing with IPv6 done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Waiting up to 180 secs for eth0 to become available ... Begin: Running /scripts/local-top ... Please unlock disk rootfs: Failure: Interface eth0 e done. ipconfig: eth0: SIOCGIFINDEX: No such device ipconfig: no devices to configure ipconfig: eth0: SIOCGIFINDEX: No such device ipconfig: no devices to configure ipconfig: eth0: SIOCGIFINDEX: No such device ipconfig: no devices to configure ipconfig: eth0: SIOCGIFINDEX: No such device ipconfig: no devices to configure ipconfig: eth0: SIOCGIFINDEX: No such device ipconfig: no devices to configure ipconfig: eth0: SIOCGIFINDEX: No such device ipconfig: no devices to configure ipconfig: eth0: SIOCGIFINDEX: No such device ipconfig: no devices to configure ipconfig: eth0: SIOCGIFINDEX: No such device ipconfig: no devices to configure ipconfig: eth0: SIOCGIFINDEX: No such device ipconfig: no devices to configure ipconfig: eth0: SIOCGIFINDEX: No such device ipconfig: no devices to configure /scripts/init-premount/dropbear: .: line 329: can't open '/run/net-eth0.conf': No such file or directory as you see the network is trying to get initialized: but the pre-init scripts are looking for a device called eth0. The armbian image however changed the NIC name from eth0 to enx001e06380848. I guess that is the next issue because the network is not initialized correctly and timed-out? how to solve this? Well, to overcome this in the configuration file /etc/initramfs-tools/initramfs.conf I changed DEVICE=eth0 to DEVICE=enx001e06380848 and then executed in the chroot'ed environment "update-initramfs -u". After this it works like a charm, YES!!!!!! [...] [ 14.371201] s5p-mfc 11000000.codec: decoder registered as /dev/video4 [ 14.380114] exynos-gsc 13e10000.video-scaler: Adding to iommu group 5 [ 14.383972] s5p-mfc 11000000.codec: encoder registered as /dev/video6 [ 14.767167] usb 6-1: reset SuperSpeed Gen 1 USB device number 2 using xhci-hcd [ 14.870308] r8152 6-1:1.0 eth0: v1.10.11 [ 14.915306] r8152 6-1:1.0 enx001e06380848: renamed from eth0 Begin: Loading essential drivers ... [ 15.870227] loop: module loaded [ 16.030971] zram: Added device: zram0 [ 16.046077] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 16.272513] RPC: Registered named UNIX socket transport module. [ 16.276980] RPC: Registered udp transport module. [ 16.281628] RPC: Registered tcp transport module. [ 16.286343] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 16.343674] NET: Registered protocol family 10 [ 16.367678] Segment Routing with IPv6 done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Waiting up to 180 secs for enx001e06380848 to become available ... Begin: Running /scripts/local-top ... done. Please unlock disk rootfs: IP-Config: enx001e06380848 hardware address 00:1e:06:36:09:49 mtu 1500 DHCP RARP IP-Config: no response after 2 secs - giving up IP-Config: enx001e06380848 hardware address 00:1e:06:36:09:49 mtu 1500 DHCP RARP IP-Config: enx001e06380848 complete (dhcp from 192.168.0.1): address: 192.168.0.123 broadcast: 192.168.0.255 netmask: 255.255.255.0 gateway: 192.168.0.1 dns0 : 192.168.0.1 dns1 : 0.0.0.0 domain : my.domain rootserver: 192.168.0.1 rootpath: filename : Begin: Starting dropbear ... Now I can ssh -p222 root@192.168.0.123 into the temporary dropbear sheel and enter my LUKS password. Then the boot process continues ... [...] Begin: Starting dropbear ... cryptsetup: rootfs: set up successfully done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Will now check root file system ... fsck from util-linux 2.36.1 [ 324.064270] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63) [ 324.124907] mmc_host mmc1: Bus speed (slot 0) = 200000000Hz (slot req 200000000Hz, actual 200000000HZ div = 0) [/sbin/fsck.ext4 (1) -- /dev/mapper/rootfs] fsck.ext4 -a -C0 /dev/mapper/rootfs /dev/mapper/rootfs: recovering journal /dev/mapper/rootfs: clean, 42398/1941504 files, 442853/7762688 blocks done. [ 325.557610] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null) done. [ 325.715647] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63) [ 325.777619] mmc_host mmc1: Bus speed (slot 0) = 200000000Hz (slot req 200000000Hz, actual 200000000HZ div = 0) [ 326.226748] blk_update_request: I/O error, dev mmcblk1, sector 451552 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0 Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... Begin: Stopping dropbear ... done. Begin: Bringing down enx001e06380848 ... done. Begin: Bringing down lo ... done. [ 326.482381] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63) [ 326.546330] mmc_host mmc1: Bus speed (slot 0) = 200000000Hz (slot req 200000000Hz, actual 200000000HZ div = 0) [ 327.117351] blk_update_request: I/O error, dev mmcblk1, sector 62551488 op 0x0:(READ) flags 0x80700 phys_seg 8 prio class 0 done. [ 327.657825] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63) [ 327.720084] mmc_host mmc1: Bus speed (slot 0) = 200000000Hz (slot req 200000000Hz, actual 200000000HZ div = 0) [...] [...]and so on [...] [ OK ] Started Network Manager. [ OK ] Reached target Network. [ OK ] Reached target Network is Online. Starting chrony, an NTP client/server... Starting LSB: Advanced IEEE 802.11 management daemon... Starting OpenVPN service... Starting /etc/rc.local Compatibility... Starting OpenBSD Secure Shell server... Starting Permit User Sessions... [ OK ] Started Unattended Upgrades Shutdown. [ OK ] Started vnStat network traffic monitor. [ OK ] Started chrony, an NTP client/server. [ OK ] Started LSB: Advanced IEEE 802.11 management daemon. [ OK ] Finished OpenVPN service. [ OK ] Started /etc/rc.local Compatibility. [FAILED] Failed to start OpenBSD Secure Shell server. See 'systemctl status ssh.service' for details. [ OK ] Finished Permit User Sessions. [ OK ] Reached target System Time Synchronized. [ OK ] Started Daily apt download activities. [ OK ] Started Daily apt upgrade and clean activities. [ OK ] Started Periodic ext4 Onli…ata Check for All Filesystems. [ OK ] Started Discard unused blocks once a week. [ OK ] Started Daily rotation of log files. [ OK ] Started Daily man-db regeneration. [ OK ] Started Run system activit…ounting tool every 10 minutes. [ OK ] Started Generate summary o…esterday's process accounting. [ OK ] Reached target Timers. [ OK ] Started Getty on tty1. [ OK ] Started Serial Getty on ttySAC2. [ OK ] Reached target Login Prompts. Starting Hostname Service... [ 419.494756] proc: Bad value for 'hidepid' [ OK ] Started Dispatcher daemon for systemd-networkd. [ OK ] Stopped OpenBSD Secure Shell server. Starting OpenBSD Secure Shell server... [FAILED] Failed to start OpenBSD Secure Shell server. See 'systemctl status ssh.service' for details. [ OK ] Started Hostname Service. [ OK ] Reached target Multi-User System. [ OK ] Reached target Graphical Interface. Starting Update UTMP about System Runlevel Changes... [ OK ] Stopped OpenBSD Secure Shell server. Starting OpenBSD Secure Shell server... [FAILED] Failed to start OpenBSD Secure Shell server. See 'systemctl status ssh.service' for details. [ 420.014917] IPv6: ADDRCONF(NETDEV_CHANGE): enx001e06380848: link becomes ready [ 420.021531] r8152 6-1:1.0 enx001e06380848: carrier on [ OK ] Finished Update UTMP about System Runlevel Changes. Starting Network Manager Script Dispatcher Service... [ OK ] Stopped OpenBSD Secure Shell server. Starting OpenBSD Secure Shell server... [FAILED] Failed to start OpenBSD Secure Shell server. See 'systemctl status ssh.service' for details. [ OK ] Started Network Manager Script Dispatcher Service. Armbian 21.08.3 Bullseye ttySAC2 odroidxu4 login: But ... as you see in the log, the OpenSSH server is not up. I cannot login "ssh root@192.168.0.1" although the device is reachable through network via ICMP ping. I have no idea why the OpenSSH server is failing now. Well, made some steps to mitigate the issue. Here's the conclusion so far: Issue 1) After introducing the encryption setup as shown here on that tutorial the boot.ini discovering mechanism for the correct board and corresponding image seems to fail. As I suspect the ODROID-HC2 board is not discovered correctly during the test/board_name commands in boot.ini. The default Armbian<foo>.img containt the hidden flag file .next in the boot partition, that's why the boot.ini assigns the correct exynos5422-odroidxu4.dtb for the boot process. However, after introducing the encryption as shown here on the tutorial, this flag file .next was not in the boot partition any more that's why the recognition and aassignment of the needed dtb file fails. Workaround: either by manually forcing boot.ini to load the odroidxu4.dtb image which will work for the ODROID-HC2 board or better and simple --> don't touch the boot.ini at all and leave it as it is, but simply touch a new zero-byte hidden file called .next into the boot partition. If filename /boot/.next exists it will trigger as mainline configuration and the legacy odroidxu3 won't start and conflict with the HC-2 board thus as result the correct odroidxu4.dtb is loaded which is the correct one for the ODROID-HC2 board. Issue 2) The configuration line DEVICE=eth0 initially configured as instructed by the tutorial in "/etc/initramfs-tools/initramfs.conf" will fail, because Armbian OS changes the device name in boot process from "eth0" to "enx<mac-address>" Workaround: changing the configuration line "DEVICE=eth0" to "DEVICE=enx<mac-address-being-used-in-boot-process>" Issue 3) As first instance the Dropbear SSH server is executed through initramfs. You can login to it through port 2222 and you're prompted to enter the LUKS password for decrypting /dev/mapper/rootfs. Right after you enter the correct keyphrase, the network interface enx... gets dropped and the dropbear ssh connection is resetted as result. The boot process continues, but OpenSSH won't start. Workaround: the journal of ssh.service said that no hostkeys were available. I had to use the USB serial UART console for the first initial root login on the ODROID-HC2. After that I was prompted to change the root password and the Armbian setup was finished. I guess this was important, so the hostkeys were generated. After that, the OpenSSH were accessible as expected. Here's the output of the ssh.service journal: -- Journal begins at Sun 2021-10-24 09:28:27 UTC, ends at Sun 2021-10-24 10:18:52 UTC. -- Okt 24 09:29:09 odroidxu4 systemd[1]: Starting OpenBSD Secure Shell server... Okt 24 09:29:10 odroidxu4 sshd[1782]: sshd: no hostkeys available -- exiting. Okt 24 09:29:10 odroidxu4 systemd[1]: ssh.service: Control process exited, code=exited, status=1/FAILURE Okt 24 09:29:10 odroidxu4 systemd[1]: ssh.service: Failed with result 'exit-code'. Okt 24 09:29:10 odroidxu4 systemd[1]: Failed to start OpenBSD Secure Shell server. Okt 24 09:29:11 odroidxu4 systemd[1]: ssh.service: Scheduled restart job, restart counter is at 1. Okt 24 09:29:11 odroidxu4 systemd[1]: Stopped OpenBSD Secure Shell server. Okt 24 09:29:11 odroidxu4 systemd[1]: Starting OpenBSD Secure Shell server... Okt 24 09:29:11 odroidxu4 sshd[1793]: sshd: no hostkeys available -- exiting. Okt 24 09:29:11 odroidxu4 systemd[1]: ssh.service: Control process exited, code=exited, status=1/FAILURE Okt 24 09:29:11 odroidxu4 systemd[1]: ssh.service: Failed with result 'exit-code'. Okt 24 09:29:11 odroidxu4 systemd[1]: Failed to start OpenBSD Secure Shell server. Okt 24 09:29:11 odroidxu4 systemd[1]: ssh.service: Scheduled restart job, restart counter is at 2. Okt 24 09:29:11 odroidxu4 systemd[1]: Stopped OpenBSD Secure Shell server. Okt 24 09:29:11 odroidxu4 systemd[1]: Starting OpenBSD Secure Shell server... Okt 24 09:29:11 odroidxu4 sshd[1795]: sshd: no hostkeys available -- exiting. Okt 24 09:29:11 odroidxu4 systemd[1]: ssh.service: Control process exited, code=exited, status=1/FAILURE Okt 24 09:29:11 odroidxu4 systemd[1]: ssh.service: Failed with result 'exit-code'. Okt 24 09:29:11 odroidxu4 systemd[1]: Failed to start OpenBSD Secure Shell server. Okt 24 09:29:11 odroidxu4 systemd[1]: ssh.service: Scheduled restart job, restart counter is at 3. Okt 24 09:29:11 odroidxu4 systemd[1]: Stopped OpenBSD Secure Shell server. Okt 24 09:29:11 odroidxu4 systemd[1]: Starting OpenBSD Secure Shell server... Okt 24 09:29:11 odroidxu4 sshd[1800]: sshd: no hostkeys available -- exiting. Okt 24 09:29:11 odroidxu4 systemd[1]: ssh.service: Control process exited, code=exited, status=1/FAILURE Okt 24 09:29:11 odroidxu4 systemd[1]: ssh.service: Failed with result 'exit-code'. Okt 24 09:29:11 odroidxu4 systemd[1]: Failed to start OpenBSD Secure Shell server. Okt 24 09:29:11 odroidxu4 systemd[1]: ssh.service: Scheduled restart job, restart counter is at 4. Okt 24 09:29:11 odroidxu4 systemd[1]: Stopped OpenBSD Secure Shell server. Okt 24 09:29:11 odroidxu4 systemd[1]: Starting OpenBSD Secure Shell server... Okt 24 09:29:11 odroidxu4 sshd[1808]: sshd: no hostkeys available -- exiting. Okt 24 09:29:11 odroidxu4 systemd[1]: ssh.service: Control process exited, code=exited, status=1/FAILURE Okt 24 09:29:11 odroidxu4 systemd[1]: ssh.service: Failed with result 'exit-code'. Okt 24 09:29:11 odroidxu4 systemd[1]: Failed to start OpenBSD Secure Shell server. Okt 24 09:29:12 odroidxu4 systemd[1]: ssh.service: Scheduled restart job, restart counter is at 5. Okt 24 09:29:12 odroidxu4 systemd[1]: Stopped OpenBSD Secure Shell server. Okt 24 09:29:12 odroidxu4 systemd[1]: ssh.service: Start request repeated too quickly. Okt 24 09:29:12 odroidxu4 systemd[1]: ssh.service: Failed with result 'exit-code'. Okt 24 09:29:12 odroidxu4 systemd[1]: Failed to start OpenBSD Secure Shell server. Okt 24 09:29:40 odroidxu4 systemd[1]: Starting OpenBSD Secure Shell server... Okt 24 09:29:40 odroidxu4 sshd[2278]: Server listening on 0.0.0.0 port 22. Okt 24 09:29:40 odroidxu4 sshd[2278]: Server listening on :: port 22. Okt 24 09:29:40 odroidxu4 systemd[1]: Started OpenBSD Secure Shell server. Okt 24 09:29:40 odroidxu4 sshd[2278]: Received signal 15; terminating. Okt 24 09:29:40 odroidxu4 systemd[1]: Stopping OpenBSD Secure Shell server... Okt 24 09:29:40 odroidxu4 systemd[1]: ssh.service: Succeeded. Okt 24 09:29:40 odroidxu4 systemd[1]: Stopped OpenBSD Secure Shell server. Okt 24 09:29:40 odroidxu4 systemd[1]: Starting OpenBSD Secure Shell server... Okt 24 09:29:40 odroidxu4 sshd[2285]: Server listening on 0.0.0.0 port 22. Okt 24 09:29:40 odroidxu4 sshd[2285]: Server listening on :: port 22. Okt 24 09:29:40 odroidxu4 systemd[1]: Started OpenBSD Secure Shell server. Are issues 1+2 a bug in the current release or is this a bug somewhere happen during this FDE tutorial? If so, do you think they are addressable? Maybe there are some devs in here watching this thread and hopefully can give some insight? Hope the provided u-boot serial console log can assist if needed. Thanks to Steven, who showed me the right direction to nail down the issue(s)
  24. in u-boot process with encrypted rootfs I cannot find anything with the string "dts" but I've found the byte size of 88701 in there: U-Boot 2017.05-armbian (Oct 08 2021 - 19:51:17 +0000) for ODROID-XU4 CPU: Exynos5422 @ 800 MHz Model: Odroid XU4 based on EXYNOS5422 Board: Odroid XU4 based on EXYNOS5422 Type: unknown DRAM: 2 GiB MMC: EXYNOS DWMMC: 0, EXYNOS DWMMC: 1 MMC Device 0 ( SD ): 29.8 GiB Card did not respond to voltage select! mmc_init: -95, time 12 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: No ethernet found. Press quickly 'Enter' twice to stop autoboot: 0 13370 bytes read in 44 ms (295.9 KiB/s) ## Executing script at 43e00000 68 bytes read in 84 ms (0 Bytes/s) 7337840 bytes read in 818 ms (8.6 MiB/s) 11083175 bytes read in 1156 ms (9.1 MiB/s) ** File not found /boot/.next ** ** Unrecognized filesystem type ** ** File not found .next ** 88701 bytes read in 185 ms (467.8 KiB/s) libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND Kernel image @ 0x40008000 [ 0x000000 - 0x6ff770 ] ## Loading init Ramdisk from Legacy Image at 42000000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 11083111 Bytes = 10.6 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 44000000 Booting using the fdt blob at 0x44000000 Using Device Tree in place at 44000000, end 44018a7c Starting kernel ... That was the serial log after I configured the full-disk-encryption as shown here in the tutorial. As reference in the following you see the serial u-boot log after 1st boot after I flashed the Armbian bullseye: U-Boot 2017.05-armbian (Oct 08 2021 - 19:51:17 +0000) for ODROID-XU4 CPU: Exynos5422 @ 800 MHz Model: Odroid XU4 based on EXYNOS5422 Board: Odroid XU4 based on EXYNOS5422 Type: unknown DRAM: 2 GiB MMC: EXYNOS DWMMC: 0, EXYNOS DWMMC: 1 MMC Device 0 ( SD ): 29.7 GiB Card did not respond to voltage select! mmc_init: -95, time 11 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: No ethernet found. Press quickly 'Enter' twice to stop autoboot: 0 ** File not found /boot.ini ** ## Executing script at 43e00000 Wrong image format for "source" command 13370 bytes read in 27 ms (483.4 KiB/s) ## Executing script at 43e00000 ** File not found /boot/armbianEnv.txt ** ** Unrecognized filesystem type ** ** File not found armbianEnv.txt ** 7337840 bytes read in 581 ms (12 MiB/s) 8796977 bytes read in 700 ms (12 MiB/s) 0 bytes read in 20 ms (0 Bytes/s) Found mainline kernel configuration 87877 bytes read in 79 ms (1.1 MiB/s) libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND Kernel image @ 0x40008000 [ 0x000000 - 0x6ff770 ] ## Loading init Ramdisk from Legacy Image at 42000000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 8796913 Bytes = 8.4 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 44000000 Booting using the fdt blob at 0x44000000 Using Device Tree in place at 44000000, end 44018744 Starting kernel ... And for better insight, this is the u-boot log with the failing encrypted rootfs at u-boot verbosity=7 configured, so the log level is 7 (maximum): U-Boot 2017.05-armbian (Oct 08 2021 - 19:51:17 +0000) for ODROID-XU4 CPU: Exynos5422 @ 800 MHz Model: Odroid XU4 based on EXYNOS5422 Board: Odroid XU4 based on EXYNOS5422 Type: unknown DRAM: 2 GiB MMC: EXYNOS DWMMC: 0, EXYNOS DWMMC: 1 MMC Device 0 ( SD ): 29.8 GiB Card did not respond to voltage select! mmc_init: -95, time 12 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: No ethernet found. Press quickly 'Enter' twice to stop autoboot: 0 13370 bytes read in 44 ms (295.9 KiB/s) ## Executing script at 43e00000 68 bytes read in 84 ms (0 Bytes/s) 7337840 bytes read in 818 ms (8.6 MiB/s) 11083175 bytes read in 1156 ms (9.1 MiB/s) ** File not found /boot/.next ** ** Unrecognized filesystem type ** ** File not found .next ** 88701 bytes read in 185 ms (467.8 KiB/s) libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND Kernel image @ 0x40008000 [ 0x000000 - 0x6ff770 ] ## Loading init Ramdisk from Legacy Image at 42000000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 11083111 Bytes = 10.6 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 44000000 Booting using the fdt blob at 0x44000000 Using Device Tree in place at 44000000, end 44018a7c Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x100 [ 0.000000] Linux version 5.4.151-odroidxu4 (root@big-37) (gcc version 8.3.0 (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36))) #21.08.3 SMP PREEMPT Fri Oct 8 19:1 [ 0.000000] CPU: ARMv7 Processor [410fc073] revision 3 (ARMv7), cr=10c5387d [ 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 XU3 [ 0.000000] Memory policy: Data cache writealloc [ 0.000000] cma: Reserved 128 MiB at 0xb6800000 [ 0.000000] Samsung CPU ID: 0xe5422001 [ 0.000000] Running under secure firmware. [ 0.000000] percpu: Embedded 20 pages/cpu s51852 r8192 d21876 u81920 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 516928 [ 0.000000] Kernel command line: bootsplash.bootfile=bootsplash.armbian console=ttySAC2,115200n8 consoleblank=0 loglevel=7 root=/dev/mapper/rootfs rootfstype=ext4 rootwait rw smsc95xx. [ 0.000000] hdmi: using HDMI mode [ 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:on, heap free:off [ 0.000000] Memory: 1895308K/2074624K available (11264K kernel code, 719K rwdata, 3020K rodata, 1024K init, 297K bss, 48244K reserved, 131072K cma-reserved, 1157120K highmem) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1 [ 0.000000] rcu: Preemptible hierarchical RCU implementation. [ 0.000000] 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] random: get_random_bytes called from start_kernel+0x36c/0x540 with crng_init=0 [ 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.000007] 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 49 [ 0.001698] arch_timer: cp15 timer(s) running at 24.00MHz (phys). [ 0.001719] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns [ 0.001740] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns [ 0.001753] Ignoring duplicate/late registration of read_current_timer delay [ 0.002347] Console: colour dummy device 80x30 [ 0.002396] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=240000) [ 0.002411] pid_max: default: 32768 minimum: 301 [ 0.002580] LSM: Security Framework initializing [ 0.002628] Yama: becoming mindful. [ 0.003008] AppArmor: AppArmor initialized [ 0.003086] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes, linear) [ 0.003108] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes, linear) [ 0.003201] *** VALIDATE tmpfs *** [ 0.003960] *** VALIDATE proc *** [ 0.004321] *** VALIDATE cgroup1 *** [ 0.004336] *** VALIDATE cgroup2 *** [ 0.004398] CPU: Testing write buffer coherency: ok [ 0.005042] CPU0: thread -1, cpu 0, socket 1, mpidr 80000100 [ 0.005989] Setting up static identity map for 0x40100000 - 0x40100060 [ 0.006306] ARM CCI driver probed [ 0.006898] Exynos MCPM support installed [ 0.007209] rcu: Hierarchical SRCU implementation. [ 0.009734] soc soc0: Exynos: CPU[EXYNOS5800] PRO_ID[0xe5422001] REV[0x1] Detected [ 0.010409] smp: Bringing up secondary CPUs ... [ 0.011472] CPU1: thread -1, cpu 1, socket 1, mpidr 80000101 [ 0.012699] CPU2: thread -1, cpu 2, socket 1, mpidr 80000102 [ 0.013818] CPU3: thread -1, cpu 3, socket 1, mpidr 80000103 [ 0.014961] CPU4: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.014970] CPU4: detected I-Cache line size mismatch, workaround enabled [ 0.014977] CPU4: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable [ 0.016243] CPU5: thread -1, cpu 1, socket 0, mpidr 80000001 [ 0.016250] CPU5: detected I-Cache line size mismatch, workaround enabled [ 0.016257] CPU5: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable [ 0.017499] CPU6: thread -1, cpu 2, socket 0, mpidr 80000002 [ 0.017506] CPU6: detected I-Cache line size mismatch, workaround enabled [ 0.017513] CPU6: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable [ 0.018723] CPU7: thread -1, cpu 3, socket 0, mpidr 80000003 [ 0.018731] CPU7: detected I-Cache line size mismatch, workaround enabled [ 0.018738] CPU7: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable [ 0.018940] smp: Brought up 1 node, 8 CPUs [ 0.018959] SMP: Total of 8 processors activated (384.00 BogoMIPS). [ 0.018967] CPU: All CPU(s) started in HYP mode. [ 0.018974] CPU: Virtualization extensions available. [ 0.020013] devtmpfs: initialized [ 0.041439] VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0 [ 0.041804] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns [ 0.041869] futex hash table entries: 2048 (order: 5, 131072 bytes, linear) [ 0.044501] xor: measuring software checksum speed [ 0.139954] arm4regs : 1518.000 MB/sec [ 0.239956] 8regs : 1238.000 MB/sec [ 0.339958] 32regs : 1233.200 MB/sec [ 0.439955] neon : 2214.000 MB/sec [ 0.439966] xor: using function: neon (2214.000 MB/sec) [ 0.440017] pinctrl core: initialized pinctrl subsystem [ 0.442449] NET: Registered protocol family 16 [ 0.445947] DMA: preallocated 2048 KiB pool for atomic coherent allocations [ 0.447457] audit: initializing netlink subsys (disabled) [ 0.447704] audit: type=2000 audit(0.440:1): state=initialized audit_enabled=0 res=1 [ 0.448546] cpuidle: using governor menu [ 0.449261] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers. [ 0.449273] hw-breakpoint: maximum watchpoint size is 8 bytes. [ 0.555203] EXYNOS5420 PMU initialized [ 0.653826] random: fast init done [ 0.787471] cryptd: max_cpu_qlen set to 1000 [ 0.960001] raid6: neonx8 gen() 1470 MB/s [ 1.129996] raid6: neonx8 xor() 1185 MB/s [ 1.299987] raid6: neonx4 gen() 1342 MB/s [ 1.469980] raid6: neonx4 xor() 1195 MB/s [ 1.640017] raid6: neonx2 gen() 1055 MB/s [ 1.809969] raid6: neonx2 xor() 1335 MB/s [ 1.979980] raid6: neonx1 gen() 719 MB/s [ 2.149970] raid6: neonx1 xor() 1000 MB/s [ 2.319985] raid6: int32x8 gen() 373 MB/s [ 2.490063] raid6: int32x8 xor() 269 MB/s [ 2.660079] raid6: int32x4 gen() 368 MB/s [ 2.830043] raid6: int32x4 xor() 283 MB/s [ 3.000111] raid6: int32x2 gen() 261 MB/s [ 3.170240] raid6: int32x2 xor() 137 MB/s [ 3.340134] raid6: int32x1 gen() 199 MB/s [ 3.510080] raid6: int32x1 xor() 204 MB/s [ 3.510091] raid6: using algorithm neonx8 gen() 1470 MB/s [ 3.510101] raid6: .... xor() 1185 MB/s, rmw enabled [ 3.510112] raid6: using neon recovery algorithm [ 3.512248] iommu: Default domain type: Translated [ 3.512652] usbcore: registered new interface driver usbfs [ 3.512713] usbcore: registered new interface driver hub [ 3.512772] usbcore: registered new device driver usb [ 3.513456] s3c-i2c 12c60000.i2c: slave address 0x00 [ 3.513473] s3c-i2c 12c60000.i2c: bus frequency set to 65 KHz [ 3.514367] s3c-i2c 12c60000.i2c: i2c-5: S3C I2C adapter [ 3.514548] s3c-i2c 12c80000.i2c: slave address 0x00 [ 3.514565] s3c-i2c 12c80000.i2c: bus frequency set to 65 KHz [ 3.514808] s3c-i2c 12c80000.i2c: i2c-2: S3C I2C adapter [ 3.515294] mc: Linux media interface: v0.10 [ 3.515336] videodev: Linux video capture interface: v2.00 [ 3.515832] Advanced Linux Sound Architecture Driver Initialized. [ 3.516401] NetLabel: Initializing [ 3.516413] NetLabel: domain hash size = 128 [ 3.516423] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO [ 3.516498] NetLabel: unlabeled traffic allowed by default [ 3.517142] clocksource: Switched to clocksource mct-frc [ 3.617818] *** VALIDATE bpf *** [ 3.618013] VFS: Disk quotas dquot_6.6.0 [ 3.618089] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 3.618194] *** VALIDATE ramfs *** [ 3.618938] AppArmor: AppArmor Filesystem Enabled [ 3.632235] thermal_sys: Registered thermal governor 'step_wise' [ 3.634662] NET: Registered protocol family 2 [ 3.634821] IP idents hash table entries: 16384 (order: 5, 131072 bytes, linear) [ 3.636004] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear) [ 3.636051] TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear) [ 3.636152] TCP bind hash table entries: 8192 (order: 4, 65536 bytes, linear) [ 3.636309] TCP: Hash tables configured (established 8192 bind 8192) [ 3.636450] UDP hash table entries: 512 (order: 2, 16384 bytes, linear) [ 3.636498] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear) [ 3.636739] NET: Registered protocol family 1 [ 3.637010] Trying to unpack rootfs image as initramfs... [ 4.306349] Freeing initrd memory: 10824K [ 4.308659] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 5 counters available [ 4.309518] hw perfevents: enabled with armv7_cortex_a15 PMU driver, 7 counters available [ 4.311464] Initialise system trusted keyrings [ 4.311516] Key type blacklist registered [ 4.311902] workingset: timestamp_bits=14 max_order=19 bucket_order=5 [ 4.321136] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 4.322217] fuse: init (API version 7.31) [ 4.322344] *** VALIDATE fuse *** [ 4.322359] *** VALIDATE fuse *** [ 4.323632] Platform Keyring initialized [ 4.354192] Key type asymmetric registered [ 4.354205] Asymmetric key parser 'x509' registered [ 4.354356] bounce: pool size: 64 pages [ 4.354422] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247) [ 4.354595] io scheduler mq-deadline registered [ 4.354608] io scheduler kyber registered [ 4.354654] io scheduler bfq registered [ 4.357328] samsung-usb2-phy 12130000.phy: 12130000.phy supply vbus not found, using dummy regulator [ 4.358351] exynos5_usb3drd_phy 12100000.phy: 12100000.phy supply vbus not found, using dummy regulator [ 4.358441] exynos5_usb3drd_phy 12100000.phy: 12100000.phy supply vbus-boost not found, using dummy regulator [ 4.358836] exynos5_usb3drd_phy 12500000.phy: 12500000.phy supply vbus not found, using dummy regulator [ 4.358926] exynos5_usb3drd_phy 12500000.phy: 12500000.phy supply vbus-boost not found, using dummy regulator [ 4.368454] dma-pl330 121a0000.pdma: Loaded driver for PL330 DMAC-241330 [ 4.368471] dma-pl330 121a0000.pdma: DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32 [ 4.371230] dma-pl330 121b0000.pdma: Loaded driver for PL330 DMAC-241330 [ 4.371246] dma-pl330 121b0000.pdma: DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32 [ 4.372128] dma-pl330 10800000.mdma: Loaded driver for PL330 DMAC-241330 [ 4.372144] dma-pl330 10800000.mdma: DBUFF-64x8bytes Num_Chans-8 Num_Peri-1 Num_Events-32 [ 4.450863] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [ 4.453288] 12c00000.serial: ttySAC0 at MMIO 0x12c00000 (irq = 62, base_baud = 0) is a S3C6400/10 [ 4.453707] 12c10000.serial: ttySAC1 at MMIO 0x12c10000 (irq = 63, base_baud = 0) is a S3C6400/10 [ 4.454115] 12c20000.serial: ttySAC2 at MMIO 0x12c20000 (irq = 64, base_baud = 0) is a S3C6400/10 [ 5.529074] printk: console [ttySAC2] enabled [ 5.533769] 12c30000.serial: ttySAC3 at MMIO 0x12c30000 (irq = 65, base_baud = 0) is a S3C6400/10 [ 5.543928] exynos-trng 10830600.rng: Exynos True Random Number Generator. [ 5.550902] exynos-mixer 14450000.mixer: Adding to iommu group 0 [ 5.577062] brd: module loaded [ 5.579537] libphy: Fixed MDIO Bus: probed [ 5.583049] usbcore: registered new interface driver r8152 [ 5.588245] usbcore: registered new interface driver cdc_ether [ 5.594012] usbcore: registered new interface driver cdc_subset [ 5.602256] dma-pl330 3880000.adma: Loaded driver for PL330 DMAC-241330 [ 5.607419] dma-pl330 3880000.adma: DBUFF-4x8bytes Num_Chans-6 Num_Peri-16 Num_Events-6 [ 5.612190] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 5.621991] ehci-exynos: EHCI EXYNOS driver [ 5.626466] exynos-ehci 12110000.usb: EHCI Host Controller [ 5.631608] exynos-ehci 12110000.usb: new USB bus registered, assigned bus number 1 [ 5.637272] dma-pl330 3880000.adma: PM domain MAU will not be powered off [ 5.639662] exynos-ehci 12110000.usb: irq 84, io mem 0x12110000 [ 5.677192] exynos-ehci 12110000.usb: USB 2.0 started, EHCI 1.00 [ 5.681986] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04 [ 5.689994] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 5.697179] usb usb1: Product: EHCI Host Controller [ 5.701991] usb usb1: Manufacturer: Linux 5.4.151-odroidxu4 ehci_hcd [ 5.708348] usb usb1: SerialNumber: 12110000.usb [ 5.713525] hub 1-0:1.0: USB hub found [ 5.716679] hub 1-0:1.0: 3 ports detected [ 5.721615] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 5.726793] ohci-exynos: OHCI EXYNOS driver [ 5.731197] exynos-ohci 12120000.usb: USB Host Controller [ 5.736321] exynos-ohci 12120000.usb: new USB bus registered, assigned bus number 2 [ 5.744079] exynos-ohci 12120000.usb: irq 84, io mem 0x12120000 [ 5.821418] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.04 [ 5.828235] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 5.835386] usb usb2: Product: USB Host Controller [ 5.840190] usb usb2: Manufacturer: Linux 5.4.151-odroidxu4 ohci_hcd [ 5.846477] usb usb2: SerialNumber: 12120000.usb [ 5.851676] hub 2-0:1.0: USB hub found [ 5.854834] hub 2-0:1.0: 3 ports detected [ 5.861182] mousedev: PS/2 mouse device common for all mice [ 5.867224] i2c /dev entries driver [ 5.891776] vdd_ldo9: Bringing 3300000uV into 3000000-3000000uV [ 5.908577] vddq_mmc2: Bringing 3300000uV into 2800000-2800000uV [ 5.929307] vdd_sd: Bringing 3300000uV into 2800000-2800000uV [ 6.008868] s5m-rtc s2mps14-rtc: registered as rtc0 [ 6.012808] s2mps11-clk s2mps11-clk: DMA mask not set [ 6.022333] ina2xx 5-0040: error configuring the device: -6 [ 6.026879] ina2xx 5-0041: error configuring the device: -6 [ 6.032468] ina2xx 5-0044: error configuring the device: -6 [ 6.038015] ina2xx 5-0045: error configuring the device: -6 [ 6.051295] s3c2410-wdt 101d0000.watchdog: watchdog inactive, reset disabled, irq disabled [ 6.058760] device-mapper: uevent: version 1.0.3 [ 6.063000] device-mapper: ioctl: 4.41.0-ioctl (2019-09-16) initialised: dm-devel@redhat.com [ 6.084203] sdhci: Secure Digital Host Controller Interface driver [ 6.088925] sdhci: Copyright(c) Pierre Ossman [ 6.093424] Synopsys Designware Multimedia Card Interface Driver [ 6.099866] dwmmc_exynos 12200000.mmc: IDMAC supports 32-bit address mode. [ 6.106110] dwmmc_exynos 12200000.mmc: Using internal DMA controller. [ 6.112502] dwmmc_exynos 12200000.mmc: Version ID is 250a [ 6.117902] dwmmc_exynos 12200000.mmc: DW MMC controller at irq 86,64 bit host data width,64 deep fifo [ 6.127382] dwmmc_exynos 12200000.mmc: allocated mmc-pwrseq [ 6.150356] mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63) [ 6.171777] dwmmc_exynos 12220000.mmc: IDMAC supports 32-bit address mode. [ 6.177261] dwmmc_exynos 12220000.mmc: Using internal DMA controller. [ 6.183585] dwmmc_exynos 12220000.mmc: Version ID is 250a [ 6.189040] dwmmc_exynos 12220000.mmc: DW MMC controller at irq 87,64 bit host data width,64 deep fifo [ 6.216799] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63) [ 6.241257] s5p-secss 10830000.sss: s5p-sss driver registered [ 6.246173] hidraw: raw HID events driver (C) Jiri Kosina [ 6.269277] exynos-nocp: new NoC Probe device registered: 10ca1000.nocp [ 6.274569] exynos-nocp: new NoC Probe device registered: 10ca1400.nocp [ 6.281189] exynos-nocp: new NoC Probe device registered: 10ca1800.nocp [ 6.287782] exynos-nocp: new NoC Probe device registered: 10ca1c00.nocp [ 6.294715] exynos-ppmu: new PPMU device registered 10d00000.ppmu (ppmu-event3-dmc0_0) [ 6.302262] exynos-ppmu: new PPMU device registered 10d10000.ppmu (ppmu-event3-dmc0_1) [ 6.310518] exynos-ppmu: new PPMU device registered 10d60000.ppmu (ppmu-event3-dmc1_0) [ 6.318039] exynos-ppmu: new PPMU device registered 10d70000.ppmu (ppmu-event3-dmc1_1) [ 6.328059] exynos5-dmc 10c20000.memory-controller: DMC initialized, in irq mode: 0 [ 6.334736] exynos-adc 12d10000.adc: IRQ index 1 not found [ 6.345201] samsung-i2s 3830000.i2s-sec: DMA channels sourced from device 3830000.i2s [ 6.353349] mmc_host mmc1: Bus speed (slot 0) = 200000000Hz (slot req 200000000Hz, actual 200000000HZ div = 0) [ 6.364539] mmc1: new ultra high speed SDR104 SDHC card at address 59b4 [ 6.364591] NET: Registered protocol family 17 [ 6.371330] mmcblk1: mmc1:59b4 EB2MW 29.8 GiB [ 6.374116] NET: Registered protocol family 15 [ 6.381453] mmcblk1: p1 p2 [ 6.382960] Key type dns_resolver registered [ 6.390570] Registering SWP/SWPB emulation handler [ 6.394873] registered taskstats version 1 [ 6.398808] Loading compiled-in X.509 certificates [ 6.405808] Loaded X.509 cert 'Build time autogenerated kernel key: 58f88920dc5a2eb8aefa1a83381c42bc4c4ae8b7' [ 6.414536] Key type ._fscrypt registered [ 6.418241] Key type .fscrypt registered [ 6.424961] Btrfs loaded, crc32c=crc32c-generic [ 6.497234] Key type big_key registered [ 6.521892] Key type encrypted registered [ 6.524431] AppArmor: AppArmor sha1 policy hashing enabled [ 6.590261] exynos-asv 10000000.chipid: cpu0 opp0, freq: 1500 missing [ 6.595267] exynos-asv 10000000.chipid: cpu4 opp0, freq: 2100 missing [ 6.604303] OF: graph: no port node found in /soc/hdmi@14530000 [ 6.610111] [drm] Exynos DRM: using 14450000.mixer device for DMA mapping operations [ 6.616539] exynos-drm exynos-drm: bound 14450000.mixer (ops 0xc0cb2b28) [ 6.623183] exynos-drm exynos-drm: bound 14530000.hdmi (ops 0xc0cb31ac) [ 6.629732] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 6.636292] [drm] No driver support for vblank timestamp query. [ 6.642252] [drm] Cannot find any crtc or sizes [ 6.647498] [drm] Cannot find any crtc or sizes [ 6.651360] [drm] Initialized exynos 1.1.0 20180330 for exynos-drm on minor 0 [ 6.660136] dwc3 12000000.dwc3: Failed to get clk 'ref': -2 [ 6.664913] xhci-hcd xhci-hcd.8.auto: xHCI Host Controller [ 6.669727] xhci-hcd xhci-hcd.8.auto: new USB bus registered, assigned bus number 3 [ 6.677618] xhci-hcd xhci-hcd.8.auto: hcc params 0x0220f04c hci version 0x100 quirks 0x0000000002010010 [ 6.686752] xhci-hcd xhci-hcd.8.auto: irq 165, io mem 0x12000000 [ 6.692910] xhci-hcd xhci-hcd.8.auto: xHCI Host Controller [ 6.698136] xhci-hcd xhci-hcd.8.auto: new USB bus registered, assigned bus number 4 [ 6.705733] xhci-hcd xhci-hcd.8.auto: Host supports USB 3.0 SuperSpeed [ 6.712424] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04 [ 6.720498] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 6.727686] usb usb3: Product: xHCI Host Controller [ 6.732505] usb usb3: Manufacturer: Linux 5.4.151-odroidxu4 xhci-hcd [ 6.738857] usb usb3: SerialNumber: xhci-hcd.8.auto [ 6.744154] hub 3-0:1.0: USB hub found [ 6.747477] hub 3-0:1.0: 1 port detected [ 6.751954] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM. [ 6.759589] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.04 [ 6.767657] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 6.774794] usb usb4: Product: xHCI Host Controller [ 6.779691] usb usb4: Manufacturer: Linux 5.4.151-odroidxu4 xhci-hcd [ 6.785972] usb usb4: SerialNumber: xhci-hcd.8.auto [ 6.791572] hub 4-0:1.0: USB hub found [ 6.794584] hub 4-0:1.0: 1 port detected [ 6.801348] dwc3 12400000.dwc3: Failed to get clk 'ref': -2 [ 6.805954] dwc3 12400000.dwc3: changing max_speed on rev 5533200a [ 6.819902] s3c-rtc 101e0000.rtc: rtc disabled, re-enabling [ 6.824216] rtc rtc1: invalid alarm value: 1900-01-01T00:00:00 [ 6.830310] s3c-rtc 101e0000.rtc: registered as rtc1 [ 6.838340] exynos-bus: new bus device registered: soc:bus_wcore ( 84000 KHz ~ 400000 KHz) [ 6.846242] exynos-bus: new bus device registered: soc:bus_noc ( 67000 KHz ~ 100000 KHz) [ 6.854073] exynos-bus: new bus device registered: soc:bus_fsys_apb (100000 KHz ~ 200000 KHz) [ 6.862267] exynos-bus: new bus device registered: soc:bus_fsys (100000 KHz ~ 200000 KHz) [ 6.870809] exynos-bus: new bus device registered: soc:bus_fsys2 ( 75000 KHz ~ 150000 KHz) [ 6.879392] exynos-bus: new bus device registered: soc:bus_mfc ( 96000 KHz ~ 333000 KHz) [ 6.887256] exynos-bus: new bus device registered: soc:bus_gen ( 89000 KHz ~ 267000 KHz) [ 6.894891] exynos-bus: new bus device registered: soc:bus_peri ( 67000 KHz ~ 67000 KHz) [ 6.903952] exynos-bus: new bus device registered: soc:bus_g2d ( 84000 KHz ~ 333000 KHz) [ 6.911730] exynos-bus: new bus device registered: soc:bus_g2d_acp ( 67000 KHz ~ 267000 KHz) [ 6.920114] exynos-bus: new bus device registered: soc:bus_jpeg ( 75000 KHz ~ 300000 KHz) [ 6.928342] exynos-bus: new bus device registered: soc:bus_jpeg_apb ( 84000 KHz ~ 167000 KHz) [ 6.936463] exynos-bus: new bus device registered: soc:bus_disp1_fimd (120000 KHz ~ 200000 KHz) [ 6.945301] exynos-bus: new bus device registered: soc:bus_disp1 (120000 KHz ~ 300000 KHz) [ 6.953534] exynos-bus: new bus device registered: soc:bus_gscl_scaler (150000 KHz ~ 300000 KHz) [ 6.962562] exynos-bus: new bus device registered: soc:bus_mscl ( 84000 KHz ~ 400000 KHz) [ 6.971554] max98090 1-0010: Failed to reset codec: -6 [ 6.975416] max98090 1-0010: Failed to read device revision: -1 [ 6.981181] max98090 1-0010: ASoC: failed to probe component -1 [ 6.987097] odroid-audio sound: ASoC: failed to instantiate card -1 [ 6.993587] odroid-audio sound: snd_soc_register_card() failed: -1 [ 6.999484] odroid-audio: probe of sound failed with error -1 [ 7.008618] s5m-rtc s2mps14-rtc: setting system clock to 2021-10-24T07:20:51 UTC (1635060051) [ 7.069595] ALSA device list: [ 7.071146] No soundcards found. [ 7.078979] Freeing unused kernel memory: 1024K [ 7.108334] Run /init as init process Loading, please wait... Starting version 247.3-6 [ 7.915917] gpiomem-exynos 13400000.gpiomem: Initialised: GPIO register area is 3 [ 7.924047] input: gpio_keys as /devices/platform/gpio_keys/input/input0 [ 7.924083] gpiomem-exynos 13400000.gpiomem: Initialised: Registers at 0x13400000 [ 7.937414] gpiomem-exynos 13400000.gpiomem: Initialised: Registers at 0x14010000 [ 7.937991] usb 4-1: new SuperSpeed Gen 1 USB device number 2 using xhci-hcd [ 7.947536] gpiomem-exynos 13400000.gpiomem: Initialised: Registers at 0x03860000 [ 7.987314] s5p-jpeg 11f50000.jpeg: Adding to iommu group 1 [ 7.992579] s5p-jpeg 11f50000.jpeg: encoder device registered as /dev/video0 [ 7.994408] mali 11800000.gpu: GPU identified as 0x0620 r0p1 status 0 [ 7.994817] usb 4-1: New USB device found, idVendor=152d, idProduct=0578, bcdDevice=31.02 [ 7.994824] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 7.994829] usb 4-1: Product: USB to ATA/ATAPI Bridge [ 7.994833] usb 4-1: Manufacturer: JMicron [ 7.994838] usb 4-1: SerialNumber: 0123456789ABCDEF [ 7.999310] s5p-mfc 11000000.codec: Adding to iommu group 2 [ 8.004945] s5p-jpeg 11f50000.jpeg: decoder device registered as /dev/video1 [ 8.005771] mali 11800000.gpu: Protected mode not available [ 8.007479] mali 11800000.gpu: Probed as mali0 [ 8.034044] exynos-gsc 13e00000.video-scaler: Adding to iommu group 3 [ 8.039863] s5p-jpeg 11f50000.jpeg: Samsung S5P JPEG codec [ 8.052286] exynos-gsc 13e10000.video-scaler: Adding to iommu group 4 [ 8.056844] s5p-jpeg 11f60000.jpeg: Adding to iommu group 5 [ 8.060393] s5p-mfc 11000000.codec: preallocated 8 MiB buffer for the firmware and context buffers [ 8.060499] s5p-mfc 11000000.codec: Direct firmware load for s5p-mfc-v8.fw failed with error -2 [ 8.060506] s5p_mfc_load_firmware:69: Firmware is not present in the /lib/firmware directory nor compiled in kernel [ 8.060672] s5p-mfc 11000000.codec: decoder registered as /dev/video3 [ 8.060763] s5p-mfc 11000000.codec: encoder registered as /dev/video4 [ 8.122053] s5p-jpeg 11f60000.jpeg: encoder device registered as /dev/video6 [ 8.128431] s5p-jpeg 11f60000.jpeg: decoder device registered as /dev/video7 [ 8.135245] s5p-jpeg 11f60000.jpeg: Samsung S5P JPEG codec [ 8.225646] SCSI subsystem initialized [ 8.238568] usbcore: registered new interface driver usb-storage [ 8.252322] scsi host0: uas [ 8.254009] usbcore: registered new interface driver uas [ 8.254934] scsi 0:0:0:0: Direct-Access JMicron Generic 3102 PQ: 0 ANSI: 6 [ 14.230640] sd 0:0:0:0: [sda] Unit Not Ready [ 14.233462] sd 0:0:0:0: [sda] Sense Key : 0x4 [current] [ 14.239087] sd 0:0:0:0: [sda] ASC=0x44 <<vendor>>ASCQ=0x81 [ 14.245456] sd 0:0:0:0: [sda] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=0x08 [ 14.252846] sd 0:0:0:0: [sda] Sense Key : 0x4 [current] [ 14.258078] sd 0:0:0:0: [sda] ASC=0x44 <<vendor>>ASCQ=0x81 [ 14.264371] sd 0:0:0:0: [sda] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=0x08 [ 14.272113] sd 0:0:0:0: [sda] Sense Key : 0x4 [current] [ 14.277400] sd 0:0:0:0: [sda] ASC=0x44 <<vendor>>ASCQ=0x81 [ 14.283539] sd 0:0:0:0: [sda] 0 512-byte logical blocks: (0 B/0 B) [ 14.289098] sd 0:0:0:0: [sda] 0-byte physical blocks [ 14.294770] sd 0:0:0:0: [sda] Test WP failed, assume Write Enabled [ 14.300461] sd 0:0:0:0: [sda] Asking for cache data failed [ 14.305626] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 14.312474] sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes not a multiple of physical block size (0 bytes) [ 14.314864] random: crng init done [ 14.398777] sd 0:0:0:0: [sda] Unit Not Ready [ 14.401605] sd 0:0:0:0: [sda] Sense Key : 0x4 [current] [ 14.406884] sd 0:0:0:0: [sda] ASC=0x44 <<vendor>>ASCQ=0x81 [ 14.413925] sd 0:0:0:0: [sda] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=0x08 [ 14.421021] sd 0:0:0:0: [sda] Sense Key : 0x4 [current] [ 14.426261] sd 0:0:0:0: [sda] ASC=0x44 <<vendor>>ASCQ=0x81 [ 14.432906] sd 0:0:0:0: [sda] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=0x08 [ 14.440348] sd 0:0:0:0: [sda] Sense Key : 0x4 [current] [ 14.445584] sd 0:0:0:0: [sda] ASC=0x44 <<vendor>>ASCQ=0x81 [ 14.454464] sd 0:0:0:0: [sda] Attached SCSI disk Begin: Loading essential drivers ... [ 15.480815] loop: module loaded [ 15.635118] zram: Added device: zram0 [ 15.650444] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 15.878131] RPC: Registered named UNIX socket transport module. [ 15.882566] RPC: Registered udp transport module. [ 15.887285] RPC: Registered tcp transport module. [ 15.891926] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 15.952890] NET: Registered protocol family 10 [ 15.956652] Segment Routing with IPv6 done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Waiting up to 180 secs for eth0 to become available ... Begin: Running /scripts/local-top ... Please unlock disk rootfs: Failure: Interface eth0 did not appear in time done. ipconfig: eth0: SIOCGIFINDEX: No such device ipconfig: no devices to configure ipconfig: eth0: SIOCGIFINDEX: No such device ipconfig: no devices to configure ipconfig: eth0: SIOCGIFINDEX: No such device ipconfig: no devices to configure ipconfig: eth0: SIOCGIFINDEX: No such device ipconfig: no devices to configure ipconfig: eth0: SIOCGIFINDEX: No such device ipconfig: no devices to configure ipconfig: eth0: SIOCGIFINDEX: No such device ipconfig: no devices to configure ipconfig: eth0: SIOCGIFINDEX: No such device ipconfig: no devices to configure ipconfig: eth0: SIOCGIFINDEX: No such device ipconfig: no devices to configure ipconfig: eth0: SIOCGIFINDEX: No such device ipconfig: no devices to configure ipconfig: eth0: SIOCGIFINDEX: No such device ipconfig: no devices to configure /scripts/init-premount/dropbear: .: line 329: can't open '/run/net-eth0.conf': No such file or directory
  25. want to add that I purchased and received the USB UART module kit. I am able to see what is happening while booting in u-boot. My issue is related not to hardware but to the setup/boot config. I have already posted that in the Full-Disk-Encryption thread. Thanks to all so far.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines