Rötti

Members
  • Posts

    18
  • Joined

  • Last visited

Rötti's Achievements

  1. To whom it may concern. Here is the link to the pull request: https://github.com/armbian/build/pull/3376 This is hopefully going to solve a lot of problems for all the SBC-users trying to get their NFSv3 stuff mounted on NextCloud.
  2. Hi @fallen_aarch64 thank you for sharing the information. It would be very nice if you could provide a pull request for the files you changed. So everybody having that board would benefit from that. Since some people are not too much into "sed"ing. Thanks in advance!
  3. Hi @Werner now over the holidays I've found some spare time to do the testing. The work is done and NFSD v4 is now included on all configs across all boards. I tested it and it worked: root@espressobin:~# rpcinfo -p localhost | grep nfs 100003 3 tcp 2049 nfs 100003 4 tcp 2049 nfs 100003 3 udp 2049 nfs Be aware that I could only test it on my EspressoBin board, so I can't make any promises for all other boards. Because of the fact that I'm avoiding Micro$oft products at all costs I don't own a Github account and don't intend in doing so. So I asked my Rakudo (Perl6) friends and one of them created the branch: https://github.com/patrickbkr/build/tree/unify-nfs-config That means that you'll receive a pull request on my behalf today evening. Happy new year 2022!
  4. Ok, will do. One question on that: In which config? - /config/kernel/linux-mvebu64-current.config - /config/kernel/linux-mvebu64-edge.config In legacy it's already enabled...
  5. Hello, I just installed Armbian on my SBC based on Ubuntu 20.04.3 LTS (Focal Fossa). > cat /etc/os-release NAME="Ubuntu" VERSION="20.04.3 LTS (Focal Fossa)" PRETTY_NAME="Armbian 21.08.2 Focal" VERSION_ID="20.04" VERSION_CODENAME=focal UBUNTU_CODENAME=focal Installed NFSD server via apt-get install nfs-kernel-server and checked which version of NFS is supported: > cat /proc/fs/nfsd/versions -2 +3 > rpcinfo -u localhost nfs program 100003 version 3 ready and waiting Indicating NFSD is not supporting v4. That might be because of: > zcat /proc/config.gz | grep NFS # CONFIG_USB_FUNCTIONFS is not set CONFIG_XENFS=m CONFIG_XEN_COMPAT_XENFS=y CONFIG_KERNFS=y CONFIG_NFS_FS=m CONFIG_NFS_V2=m CONFIG_NFS_V3=m CONFIG_NFS_V3_ACL=y CONFIG_NFS_V4=m # CONFIG_NFS_SWAP is not set # CONFIG_NFS_V4_1 is not set # CONFIG_NFS_USE_LEGACY_DNS is not set CONFIG_NFS_USE_KERNEL_DNS=y CONFIG_NFS_DISABLE_UDP_SUPPORT=y CONFIG_NFSD=y CONFIG_NFSD_V3=y # CONFIG_NFSD_V3_ACL is not set # CONFIG_NFSD_V4 is not set CONFIG_NFS_ACL_SUPPORT=m CONFIG_NFS_COMMON=y Question: Why is CONFIG_NFSD_V4 is not set by default?
  6. Hello @Werner, you have been right. The patch was not included even if I updated the repo which was strange. So started over, deleted everything, cloned it and compiled it with with: sudo ./compile.sh BOARD=espressobin BRANCH=current RELEASE=focal BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no COMPRESS_OUTPUTIMAGE=sha,gpg,img This time I could find the patch in "cache/sources/linux-mainline/linux-5.10.y/drivers/pci/quirks.c" and guess what. I could use the SATA-Controller card with all HDDs connected and no kernel panic appeared! So everything is working. Thank you a lot! But I guess this bug is now only patched for espressobin, right? Basically it's a kernel bug which affects nearly all SBCs offering mPCI-E slots, when using SATA-Controller cards. Since AS-Media is the only vendor I could find offering such chips it might be good to have this patch in all board patch-sets until the latest linux kernel where the bug has been fixed lands in Armbian base.
  7. The new patch got into the current branch. I compiled Armbian with: sudo ./compile.sh BOARD=espressobin BRANCH=current RELEASE=focal BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no COMPRESS_OUTPUTIMAGE=sha,gpg,img And can confirm that the bug is gone now and the AS-Media based SATA controller chips are now working again. @PaliThank you for organizing the patch. @WernerThank you for you support and help getting the patch into Armbian.
  8. Hello @Werner unfortunately this did not work either. Tried with two boards, two separate SD-Cards and the following images: - Armbian_21.08.0-trunk_Espressobin_focal_current_5.10.53.img Build with: sudo ./compile.sh BOARD=espressobin BRANCH=current RELEASE=focal BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no COMPRESS_OUTPUTIMAGE=sha,gpg,img resulting in the same error as already mentioned. - Armbian_21.08.0-trunk_Espressobin_focal_current_5.10.55_minimal.img Build with: sudo ./compile.sh BOARD=espressobin BRANCH=current RELEASE=focal BUILD_MINIMAL=yes BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no COMPRESS_OUTPUTIMAGE=sha,gpg,img resulting in: TIM-1.0 WTMI-devel-18.12.0-a0a1cb8 WTMI: system early-init SVC REV: 3, CPU VDD voltage: 1.155V NOTICE: Booting Trusted Firmware NOTICE: BL1: v1.5(release):1f8ca7e (Marvell-devel-18.12.2) NOTICE: BL1: Built : 09:48:09, Feb 20 2019 NOTICE: BL1: Booting BL2 NOTICE: BL2: v1.5(release):1f8ca7e (Marvell-devel-18.12.2) NOTICE: BL2: Built : 09:48:10, Feb 20 2019 NOTICE: BL1: Booting BL31 NOTICE: BL31: v1.5(release):1f8ca7e (Marvell-devel-18.12.2) NOTICE: BL31: Built : 09:4 U-Boot 2018.03-devel-18.12.3-gc9aa92c-armbian (Feb 20 2019 - 09:45:04 +0100) Model: Marvell Armada 3720 Community Board ESPRESSOBin CPU 1000 [MHz] L2 800 [MHz] TClock 200 [MHz] DDR 800 [MHz] DRAM: 2 GiB Comphy chip #0: Comphy-0: USB3 5 Gbps Comphy-1: PEX0 2.5 Gbps Comphy-2: SATA0 6 Gbps Target spinup took 0 ms. AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl SATA mode flags: ncq led only pmp fbss pio slum part sxs PCIE-0: Link up MMC: sdhci@d0000: 0, sdhci@d8000: 1 Loading Environment from SPI Flash... SF: Detected w25q32dw with page size 256 Bytes, erase size 4 KiB, total 4 MiB OK Model: Marvell Armada 3720 Community Board ESPRESSOBin Net: eth0: neta@30000 [PRIME] Hit any key to stop autoboot: 0 starting USB... USB0: Register 2000104 NbrPorts 2 Starting the controller USB XHCI 1.00 USB1: USB EHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 1 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found ## Loading init Ramdisk from Legacy Image at 01100000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 9551184 Bytes = 9.1 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 06000000 Booting using the fdt blob at 0x6000000 Loading Ramdisk to 7ed0f000, end 7f62ad50 ... OK Using Device Tree in place at 0000000006000000, end 0000000006005b76 Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] [ 0.000000] Linux version 5.10.55-mvebu64 (root@mint-pc) (aarch64-linux-gnu-gcc (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 8.3.0, GNU ld (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 2.32.0.20190321) #trunk SMP PREEMPT Sat Jul 31 23:22:09 CEST 2021 [ 0.000000] Machine model: Globalscale Marvell ESPRESSOBin Board [ 0.000000] earlycon: ar3700_uart0 at MMIO 0x00000000d0012000 (options '') [ 0.000000] printk: bootconsole [ar3700_uart0] enabled Loading, please wait... Starting version 245.4-4ubuntu3.11 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... done. Begin: Will now check root file system ... fsck from util-linux 2.34 [/usr/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1 /dev/mmcblk0p1: clean, 23897/61184 files, 210185/244736 blocks done. done. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... done. /sbin/init: error while loading s[ 2.982575] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00 [ 2.993359] CPU: 0 PID: 1 Comm: init Not tainted 5.10.55-mvebu64 #trunk [ 3.000187] Hardware name: Globalscale Marvell ESPRESSOBin Board (DT) [ 3.006837] Call trace: [ 3.009380] dump_backtrace+0x0/0x1b0 [ 3.013168] show_stack+0x18/0x68 [ 3.016600] dump_stack+0xd8/0x134 [ 3.020116] panic+0x174/0x33c [ 3.023275] do_exit+0x9fc/0xa30 [ 3.026612] do_group_exit+0x44/0xa0 [ 3.030309] __wake_up_parent+0x0/0x30 [ 3.034188] el0_svc_common.constprop.3+0x8c/0x170 [ 3.039139] do_el0_svc+0x24/0x90 [ 3.042568] el0_svc+0x14/0x20 [ 3.045727] el0_sync_handler+0x90/0xb8 [ 3.049690] el0_sync+0x160/0x180 [ 3.053119] SMP: stopping secondary CPUs [ 3.057177] Kernel Offset: disabled [ 3.060781] CPU features: 0x0240002,2000200c [ 3.065187] Memory Limit: none [ 3.068352] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00 ]--- hared libraries: /lib/aarch64-linux-gnu/libmount.so.1: invalid ELF header Which seems to be some kind of other error. If you could tell me if I did wrong, I'd be happy to create a new image. Thanks in advance.
  9. Hello @Werner, over the week end I've got some spare time and compiled armbian and did some testing. First of all, thank you for this easy to use process, it worked like a charm. Here comes the bad news. The patch seems not to have fixed the AS-Media Sata problem. Maybe the wrong is on my side. I compiled Armbian with the following sudo ./compile.sh BOARD=espressobin BRANCH=edge RELEASE=focal BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no COMPRESS_OUTPUTIMAGE=sha,gpg,img Since I used the edge branch and I found the patch commited by you in the master branch, that should work, right? Here is the output when I start up the board. TIM-1.0 WTMI-devel-18.12.0-a0a1cb8 WTMI: system early-init SVC REV: 3, CPU VDD voltage: 1.155V NOTICE: Booting Trusted Firmware NOTICE: BL1: v1.5(release):1f8ca7e (Marvell-devel-18.12.2) NOTICE: BL1: Built : 09:48:09, Feb 20 2019 NOTICE: BL1: Booting BL2 NOTICE: BL2: v1.5(release):1f8ca7e (Marvell-devel-18.12.2) NOTICE: BL2: Built : 09:48:10, Feb 20 2019 NOTICE: BL1: Booting BL31 NOTICE: BL31: v1.5(release):1f8ca7e (Marvell-devel-18.12.2) NOTICE: BL31: Built : 09:4 U-Boot 2018.03-devel-18.12.3-gc9aa92c-armbian (Feb 20 2019 - 09:45:04 +0100) Model: Marvell Armada 3720 Community Board ESPRESSOBin CPU 1000 [MHz] L2 800 [MHz] TClock 200 [MHz] DDR 800 [MHz] DRAM: 2 GiB Comphy chip #0: Comphy-0: USB3 5 Gbps Comphy-1: PEX0 2.5 Gbps Comphy-2: SATA0 6 Gbps Target spinup took 0 ms. AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl SATA mode flags: ncq led only pmp fbss pio slum part sxs PCIE-0: Link up MMC: sdhci@d0000: 0, sdhci@d8000: 1 Loading Environment from SPI Flash... SF: Detected w25q32dw with page size 256 Bytes, erase size 4 KiB, total 4 MiB OK Model: Marvell Armada 3720 Community Board ESPRESSOBin Net: eth0: neta@30000 [PRIME] Hit any key to stop autoboot: 0 starting USB... USB0: Register 2000104 NbrPorts 2 Starting the controller USB XHCI 1.00 USB1: USB EHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 1 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found ## Loading init Ramdisk from Legacy Image at 01100000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 10352285 Bytes = 9.9 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 06000000 Booting using the fdt blob at 0x6000000 Loading Ramdisk to 7ec4b000, end 7f62a69d ... OK Using Device Tree in place at 0000000006000000, end 0000000006005d61 Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] [ 0.000000] Linux version 5.13.7-mvebu64 (root@mint-pc) (aarch64-linux-gnu-gcc (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 8.3.0, GNU ld (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 2.32.0.20190321) #trunk SMP PREEMPT Sun Aug 1 11:54:45 CEST 2021 [ 0.000000] Machine model: Globalscale Marvell ESPRESSOBin Board [ 0.000000] earlycon: ar3700_uart0 at MMIO 0x00000000d0012000 (options '') [ 0.000000] printk: bootconsole [ar3700_uart0] enabled Loading, please wait... Starting version 245.4-4ubuntu3.11 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Will now check root file system ... fsck from util-linux 2.34 [/usr/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1 /dev/mmcblk0p1: recovering journal /dev/mmcblk0p1: clean, 43141/1846656 files, 444693/7498752 blocks done. done. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... done. [ 3.286103] Internal error: synchronous external abort: 96000210 [#1] PREEMPT SMP [ 3.293847] Modules linked in: mv88e6xxx dsa_core hsr bridge stp llc phy_mvebu_a3700_comphy [ 3.302493] CPU: 0 PID: 323 Comm: run-init Not tainted 5.13.7-mvebu64 #trunk [ 3.309767] Hardware name: Globalscale Marvell ESPRESSOBin Board (DT) [ 3.316409] pstate: 000000c5 (nzcv daIF -PAN -UAO -TCO BTYPE=--) [ 3.322606] pc : ahci_single_level_irq_intr+0x1c/0x90 [ 3.327827] lr : __handle_irq_event_percpu+0x54/0x170 [ 3.333041] sp : ffffffc010003d30 [ 3.336455] x29: ffffffc010003d30 x28: ffffff8000290000 x27: 2f2f2f2f2f2f2f2f [ 3.343825] x26: ffffffc010fc5368 x25: ffffffc0114a9edc x24: ffffff8002bd6200 [ 3.351194] x23: 0000000000000035 x22: ffffffc010003de4 x21: 0000000000000000 [ 3.358562] x20: ffffffc011655008 x19: ffffff8002bbc300 x18: ffffff807f24b300 [ 3.365931] x17: 0000000000000000 x16: 0000000000000000 x15: 0000b55c59f9ec62 [ 3.373300] x14: 0000000000000092 x13: 0000000000000040 x12: 0000000000000000 [ 3.380668] x11: 0000000000000040 x10: ffffffc011423648 x9 : ffffffc011423640 [ 3.388036] x8 : ffffff8000400270 x7 : 0000000000000000 x6 : 0000000000000000 [ 3.395405] x5 : ffffffc06e9dd000 x4 : ffffffc010003e20 x3 : ffffffc06e9dd000 [ 3.402773] x2 : ffffff8002bd6080 x1 : ffffff8002b5ff00 x0 : 0000000000000035 [ 3.410142] Call trace: [ 3.412662] ahci_single_level_irq_intr+0x1c/0x90 [ 3.417516] __handle_irq_event_percpu+0x54/0x170 [ 3.422369] handle_irq_event_percpu+0x38/0x90 [ 3.426953] handle_irq_event+0x48/0xe0 [ 3.430910] handle_simple_irq+0x94/0xd0 [ 3.434959] generic_handle_irq+0x30/0x48 [ 3.439095] advk_pcie_irq_handler+0x214/0x240 [ 3.443681] __handle_irq_event_percpu+0x54/0x170 [ 3.448534] handle_irq_event_percpu+0x38/0x90 [ 3.453117] handle_irq_event+0x48/0xe0 [ 3.457074] handle_fasteoi_irq+0xb8/0x170 [ 3.461300] generic_handle_irq+0x30/0x48 [ 3.465436] __handle_domain_irq+0x64/0xc0 [ 3.469661] gic_handle_irq+0xbc/0x138 [ 3.473533] el1_irq+0xb8/0x150 [ 3.476773] dput+0x0/0x20 [ 3.479565] walk_component+0x70/0x1d8 [ 3.483433] link_path_walk.part.54+0x254/0x388 [ 3.488106] path_lookupat.isra.56+0x3c/0x158 [ 3.492601] filename_lookup.part.73+0x88/0x148 [ 3.497275] user_path_at_empty+0x50/0x68 [ 3.501411] do_faccessat+0x90/0x2b0 [ 3.505103] __arm64_sys_faccessat+0x24/0x30 [ 3.509510] invoke_syscall+0x44/0x108 [ 3.513379] el0_svc_common.constprop.2+0x84/0xd8 [ 3.518234] do_el0_svc+0x24/0x88 [ 3.521654] el0_svc+0x24/0x38 [ 3.524808] el0_sync_handler+0x90/0xb8 [ 3.528766] el0_sync+0x178/0x180 [ 3.532190] Code: a90153f3 f9401022 f9400854 91002294 (b9400293) [ 3.538482] ---[ end trace 6173084cd6700768 ]--- [ 3.543245] Kernel panic - not syncing: synchronous external abort: Fatal exception in interrupt [ 3.552306] SMP: stopping secondary CPUs [ 3.556353] Kernel Offset: disabled [ 3.559947] CPU features: 0x00001001,20000846 [ 3.564440] Memory Limit: none [ 3.567589] ---[ end Kernel panic - not syncing: synchronous external abort: Fatal exception in interrupt ]--- Any help or hint would be appreciated. Otherwise I have to get back to the Linux ger mailing list of pci and inform them. Thank you very much in advance! Best regards, Rötti
  10. Currently trying to build Armbian for the first time. But I'm stuck on how to build it for Espressobin. It was supported a half a year ago afaik. I can't find the board to choose in the configuration screen of compile. Where can I download board specific stuff to get it as a choice in the compile screen? Thanks in advance. ---- Update: Never mind found the button to build CBC.
  11. Hello, I created a Feature Request to get @Pali's and Marek's patch included into Armbian. The Feature Request can be found here:
  12. Hello, there has been a linux kernel issue in the pci part. The symptoms are Armbian kernel panics. This has already been discussed in the armbian forum: A patch has been supplied by @Pali and Marek Behún in the drivers/pci/quirks.c file. Thank you guys very much for that! Bug report can be found here:https://bugzilla.kernel.org/show_bug.cgi?id=212695 And patch can be found here: https://lore.kernel.org/linux-pci/20210317115924.31885-1-kabel@kernel.org/ This is the actual patch content: --- drivers/pci/quirks.c | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c index 653660e3ba9e..a561136efb08 100644 --- a/drivers/pci/quirks.c +++ b/drivers/pci/quirks.c @@ -3251,6 +3251,11 @@ DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_SOLARFLARE, PCI_DEVICE_ID_SOLARFLARE_SFC4000A_1, fixup_mpss_256); DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_SOLARFLARE, PCI_DEVICE_ID_SOLARFLARE_SFC4000B, fixup_mpss_256); +/* + * For some reason DECLARE_PCI_FIXUP_HEADER does not work with pci-aardvark + * controller. We have to use DECLARE_PCI_FIXUP_EARLY. + */ +DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_ASMEDIA, 0x0612, fixup_mpss_256); /* * Intel 5000 and 5100 Memory controllers have an erratum with read completion -- As proposed by @Pali, I'd like to kindly ask that this patch gets included into Armbian as this affects several boards using ASMedia chip ASM1062 on ARM. If this report lacks any information I'd be happy to supply them. Thank you very much in advance. Rötti
  13. Hello Pali, as said in the kernel mailing list: Thanks to you and Marek. What I'd like to ask is, how does the workflow or the next steps look like? I mean, how long does it take to get the patch into the kernel (weeks, month)? How likely is it to be rejected? As soon as there is a new Kernel, will there be any nightly builds from armbian side? Are those changes flowing into Armbian directly or are there backports? Thank you in advance.
  14. Hi Pali, deeply sorry for the long delay, but we struggled with some Covid-19 related issue within the family. I Added the lspci -nn -vv output to the mailing list. But I could not find the according dmesg output. After unplugging the SATA cable and rebooting I were able to login and looking at /var/dmesg but I couldn't find any information from the time around the crash. As you can see in the output below I already have these parameters in the console variable. Is there a special way to boot with this parameter, or is it automatically used when I call 'boot' because of 'set_bootargs' which contains 'console' already? Marvell>> printenv arch=arm baudrate=115200 board=mvebu_armada-37xx board_name=mvebu_armada-37xx boot_a_script=ext4load ${boot_interface} ${devnum}:1 ${scriptaddr} ${prefix}boot.scr;source ${scriptaddr}; boot_prefixes=/ /boot/ boot_targets=usb mmc1 mmc0 bootcmd=for target in ${boot_targets}; do run bootcmd_${target}; done bootcmd_mmc0=setenv devnum 0; setenv boot_interface mmc; run scan_dev_for_boot; bootcmd_mmc1=setenv devnum 1; setenv boot_interface mmc; run scan_dev_for_boot; bootcmd_usb=setenv devnum 0; usb start;setenv boot_interface usb; run scan_dev_for_boot; bootdelay=2 console=console=ttyMV0,115200 earlycon=ar3700_uart,0xd0012000 cpu=armv8 eth1addr=00:51:82:11:22:01 eth2addr=00:51:82:11:22:02 eth3addr=00:51:82:11:22:03 ethact=neta@30000 ethaddr=00:51:82:11:22:00 ethprime=eth0 extra_params=pci=pcie_bus_safe fdt_addr=0x6000000 fdt_addr_r=0x6f00000 fdt_high=0xffffffffffffffff fdt_name=fdt.dtb fdtcontroladdr=7f62d490 gatewayip=10.4.50.254 get_images=tftpboot $kernel_addr_r $image_name; tftpboot $fdt_addr_r $fdt_name; run get_ramfs get_ramfs=if test "${ramfs_name}" != "-"; then setenv ramdisk_addr_r 0x8000000; tftpboot $ramdisk_addr_r $ramfs_name; else setenv ramdisk_addr_r -;fi hostname=marvell image_name=Image initrd_addr=0x1100000 initrd_image=uInitrd initrd_size=0x2000000 ipaddr=0.0.0.0 kernel_addr=0x7000000 kernel_addr_r=0x7000000 loadaddr=0x8000000 netdev=eth0 netmask=255.255.255.0 ramdisk_addr_r=0x8000000 ramfs_name=- root=root=/dev/nfs rw rootpath=/srv/nfs/ scan_dev_for_boot=for prefix in ${boot_prefixes}; do echo ${prefix};run boot_a_script; done scriptaddr=0x6d00000 serverip=0.0.0.0 set_bootargs=setenv bootargs $console $root ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netdev:none nfsroot=$serverip:$rootpath,tcp,v3 $extra_params $cpuidle soc=mvebu stderr=serial@12000 stdin=serial@12000 stdout=serial@12000 vendor=Marvell Environment size: 1962/65532 bytes I thank you very much for your awesome support!
  15. Hello guys, @Pali I posted the problem to the ide-linux kernel mailing list as proposed, but unfortunately received no answer. Here is the link: https://www.spinics.net/lists/linux-ide/msg60178.html Furthermore I were able to narrow down the kernel versions and exact image version of Armbian where it broke: Armbian 19.11.3 with Kernel 4.14.135 <- last version which was working Armbian 5.65 with Kernel 4.18.16 <- first version which is not working @lampra I'm not booting from sata. I'm still booting from SD-card, but get a kernel panic by mere plugging in the SATA cable via the pcie sata-controller. I'm sorry I'm not having further information about your issue.