guidol Posted December 6, 2022 Share Posted December 6, 2022 As Caution-Information: Today I updated a NanoPi Neo 2 v1.1 with armbian bullseye bleeding edge-kernel-setting via apt update/upgrade from Kernel 5.19.16 to 6.0.10 (also from armbian 22.08 to armbian 22.11.1) and had a no-boot after restart serial-TTL-Log after reboot: Spoiler U-Boot 2021.10-armbian (Aug 04 2022 - 13:33:04 +0300) Allwinner Technology CPU: Allwinner H5 (SUN50I) Model: FriendlyARM NanoPi NEO 2 DRAM: 1 GiB MMC: mmc@1c0f000: 0 Loading Environment from FAT... Unable to use mmc 0:1... In: serial Out: serial Err: serial NanoPi NEO2 v1.1 detected Net: phy interface7 eth0: ethernet@1c30000 230454 bytes read in 12 ms (18.3 MiB/s) starting USB... Bus usb@1c1a000: USB EHCI 1.00 Bus usb@1c1a400: USB OHCI 1.0 Bus usb@1c1d000: USB EHCI 1.00 Bus usb@1c1d400: USB OHCI 1.0 scanning bus usb@1c1a000 for devices... 1 USB Device(s) found scanning bus usb@1c1a400 for devices... 1 USB Device(s) found scanning bus usb@1c1d000 for devices... 1 USB Device(s) found scanning bus usb@1c1d400 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3202 bytes read in 3 ms (1 MiB/s) ## Executing script at 4fc00000 U-boot loaded from SD Boot script loaded from mmc 232 bytes read in 2 ms (113.3 KiB/s) Failed to load '/boot/dtb/allwinner/sun50i-h5-nanopi-neo2-v1.1.dtb' libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! Failed to load '/boot/dtb/allwinner/overlay/sun50i-h5-usbhost1.dtbo' Failed to load '/boot/dtb/allwinner/overlay/sun50i-h5-usbhost2.dtbo' Failed to load '/boot/dtb/allwinner/overlay/sun50i-h5-fixup.scr' 10868181 bytes read in 451 ms (23 MiB/s) 22179848 bytes read in 919 ms (23 MiB/s) Moving Image from 0x40080000 to 0x40200000, end=41790000 ## Loading init Ramdisk from Legacy Image at 4ff00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 10868117 Bytes = 10.4 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 SCRIPT FAILED: continuing... libfdt fdt_check_header(): FDT_ERR_BADMAGIC Scanning disk mmc@1c0f000.blk... Found 2 disks No EFI system partition BootOrder not defined EFI boot manager: Cannot load any image MMC Device 1 not found no mmc device at slot 1 Device 0: unknown device ethernet@1c30000 Waiting for PHY auto negotiation to complete....... done BOOTP broadcast 1 DHCP client bound to address 192.168.6.151 (706 ms) *** ERROR: `serverip' not set Cannot autoload with TFTPGET missing environment variable: pxeuuid missing environment variable: bootfile Retrieving file: pxelinux.cfg/01-02-01-fc-7c-c2-7d *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A80697 *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A8069 *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A806 *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A80 *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A8 *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0 *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm-sunxi-sunxi *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm-sunxi *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/default *** ERROR: `serverip' not set Config file not found BOOTP broadcast 1 DHCP client bound to address 192.168.6.151 (678 ms) *** ERROR: `serverip' not set Cannot autoload with TFTPGET BOOTP broadcast 1 DHCP client bound to address 192.168.6.151 (704 ms) *** ERROR: `serverip' not set Cannot autoload with TFTPGET => The problem was (the system did work fine before incl. restart etc), that the file /boot/dtb/allwinner/sun50i-h5-nanopi-neo2-v1.1.dtb was missing - and also the complete directory /boot/dtb/allwinner/overlay/ including /boot/dtb/allwinner/overlay/sun50i-h5-usbhost1.dtbo /boot/dtb/allwinner/overlay/sun50i-h5-usbhost2.dtbo /boot/dtb/allwinner/overlay/sun50i-h5-fixup.scr was also mising I had to open my silver-Neo2-NAS-case, extract the SDCard and copy this file and directory from ym other Neo2 (under kernel 5.19.16) over to the SDcard from ym Neo 2 v1.1 So I dont know if I get the same problem, when I try to update my 2 Neo 2 v1.0 Anyone else had bootup-lockup(s) after the 22.11 update? 0 Quote Link to comment Share on other sites More sharing options...
Nefedorov Posted December 12, 2022 Share Posted December 12, 2022 Good afternoon dear guru. I am developing devices for myself, including drawing printed circuit boards myself, now I have a question about how to output multi-channel sound from Armbian nano pi neo and how to create an overlay correctly, I saw that you made an overlay for a 5102 chip and it works. I would like to enable tdm support. Another question, could you please indicate how it would be correct to create a file for Alsa audio so that it would be possible to output three stereo streams simultaneously to the DAC. I will be very grateful to you for your answer. Have a nice day 0 Quote Link to comment Share on other sites More sharing options...
guidol Posted December 15, 2022 Author Share Posted December 15, 2022 Today I had the same problem with my two Neo2 v1.0 After Update/Reboot the director /boot/dtb/allwinner/overlay was completly missing for dtb-6.0.10-sunxi64 (and the directory /boot/dtb-6.0.10-sunxi64/allwinner/ has only -dtb files from the end of Noveber (maybe they are right)) But Iam was in the lucky case that my NanoPi A64 had upgraded successfully to 6.0.10 and all the dtb-files including the overlay-folde for 6.0.10 was there. So I copied these files over to /boot/dtb/allwinner (symbolic link dtb => dtb-6.0.10-sunxi64) and by restarting the Neo2 v1.0 did boot again, because of the missing overlays .dtbo/.scr the Neo2 V1.0 wasnt booting only to emergency mode If anyone need the dtb-directory for sunxi64 and Kernel 6.0.10 I will attach they here at this thread. I dont know whats the difference between the Neo2 and the NanoPi A64 (both sunxi64). The upgrade to 6.0.10 did also work fine on a Orange Pi Zero (sunxi only) allwinner60.zip 0 Quote Link to comment Share on other sites More sharing options...
Nefedorov Posted December 15, 2022 Share Posted December 15, 2022 my board is Nano Pi Neo Core H3 512 mb (( 0 Quote Link to comment Share on other sites More sharing options...
going Posted December 15, 2022 Share Posted December 15, 2022 5 часов назад, guidol сказал: Today I had the same problem with my two Neo2 v1.0 Please roll back to kernel 5.19. Wait a few days. There will be a working 6.1 kernel. Work in progress. 0 Quote Link to comment Share on other sites More sharing options...
guidol Posted December 16, 2022 Author Share Posted December 16, 2022 The Kernel 6.0.10 is working for me here. Only got the problems with the not installed DTBs/Overlays - the Neo2 DTBs/Overlays I copied out of the NanoPi A64 install with Kernel 6.0.10 With 6.0.10 I can wait for 6.1 to come Linux npi-neo2-24 6.0.10-sunxi64 #22.11.1 SMP Wed Nov 30 11:26:36 UTC 2022 aarch64 GNU/Linux 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.