Jump to content

Switching SUNXI-DEV to 5.9.y (h3-h5-h6/megous)

dolphs

By dolphs
in Advanced users - Development

 Share

Recommended Posts

guidol

guidol

Posted
Posted
16 hours ago, 5kft said:

 

It's hard to say what happened without seeing the boot process on console, and the contents of /boot. I've gotten in the habit of uninstalling the current kernel + dtbs before installing the new one in some instances (such as going from -current -> -dev or 5.8 -> 5.9), as by default if you just install the new one the old one won't get uninstalled, and the boot partition can run out of space.  (I ran into this a lot as I was doing the work on v5.9...perhaps I should bump the /boot partition size up a bit more again...)

 

/boot is big enough, because armbian is only using 1 partition (on my install) and Iam using a 8GB MicroSDCard ;)

 

After using a TTL-serial-dongle I did found that kernel 5.9.0rc2 had give me the 2 following problems:

 

1.) is seems to be searching for a UUID/BKLID which is too short:

Its searching for f17c5ebe-dc6c-4c52-831e-f2265 but the full name is f17c5ebe-dc6c-4c52-831e-f226539501a5

which was correct in /boot/armbianEnv.txt and /etc/fstab 

Gave up waiting for root file system device.  Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT!  UUID=f17c5ebe-dc6c-4c52-831e-f2265 does not exist.  Dropping to a shell!
Rebooting automatically due to panic= boot argument
[   43.246465] reboot: Restarting system

 

I mounted the MicroSDCard on my other Neo2 and did a fschk /dev/sdb1 (for the card).

After that the Neo2 did boot from this card, but couldnt find the NAS-HDD which is connected via USB (USB3-SATA on USB2.0 port)

 

2.) the kernel 5.9.0rc2 couldnt load the dtb-overlays (also while now booting from the card and root 7 is there, but the overlays doenst seem to be

compatibe): 

Applying kernel provided DT overlay sun50i-h5-cpu-clock-1.0GHz-1.1v.dtbo
failed on fdt_overlay_apply(): FDT_ERR_NOTFOUND
504 bytes read in 6 ms (82 KiB/s)
Applying kernel provided DT overlay sun50i-h5-usbhost1.dtbo
failed on fdt_overlay_apply(): FDT_ERR_BADMAGIC
base fdt does did not have a /__symbols__ node
make sure you've compiled with -@
504 bytes read in 5 ms (97.7 KiB/s)
Applying kernel provided DT overlay sun50i-h5-usbhost2.dtbo
failed on fdt_overlay_apply(): FDT_ERR_BADMAGIC
base fdt does did not have a /__symbols__ node
make sure you've compiled with -@
Error applying DT overlays, restoring original DT

Because booting the 5.9.0rc2 did work - I reinstalled the kernel 5.8.3 (Image, u-boot, dtb, firmware and config) via dpkg.
After reboot the complete system is working like before without reinstalling :) 

I only deleted some kernel 5.4.x-dtb directorys from /boot ;) 

 

Here some more TTL-Boot-log for your information:

Spoiler

U-Boot 2019.04-armbian (Nov 18 2019 - 21:52:14 +0100) Allwinner Technology

CPU:   Allwinner H5 (SUN50I)
Model: FriendlyARM NanoPi NEO 2
DRAM:  512 MiB
MMC:   mmc@1c0f000: 0
Loading Environment from EXT4... ** File not found /boot/boot.env **

** Unable to read "/boot/boot.env" from mmc0:1 **

U-Boot SPL 2019.04-armbian (Nov 18 2019 - 21:52:14 +0100)
DRAM: 512 MiB
Trying to boot from MMC1
NOTICE:  BL31: v2.2(debug):5d71d3f-dirty
NOTICE:  BL31: Built : 19:39:11, Oct 31 2019
NOTICE:  BL31: Detected Allwinner H5 SoC (1718)
NOTICE:  BL31: Found U-Boot DTB at 0x408baa0, model: FriendlyARM NanoPi NEO 2
INFO:    ARM GICv2 driver initialized
INFO:    Configuring SPC Controller
NOTICE:  BL31: PMIC: Defaulting to PortL GPIO according to H5 reference design.
INFO:    BL31: Platform setup done
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for 855873 was applied
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x4a000000
INFO:    SPSR = 0x3c9


U-Boot 2019.04-armbian (Nov 18 2019 - 21:52:14 +0100) Allwinner Technology

CPU:   Allwinner H5 (SUN50I)
Model: FriendlyARM NanoPi NEO 2
DRAM:  512 MiB
MMC:   mmc@1c0f000: 0
Loading Environment from EXT4... ** File not found /boot/boot.env **

** Unable to read "/boot/boot.env" from mmc0:1 **
In:    serial
Out:   serial
Err:   serial
NanoPi NEO2 v1.0 detected
Net:   phy interface7
eth0: ethernet@1c30000
** Reading file would overwrite reserved memory **
There is no valid bmp file at the given address
starting USB...
USB0:   USB EHCI 1.00
USB1:   USB OHCI 1.0
USB2:   USB EHCI 1.00
USB3:   USB OHCI 1.0
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 1 for devices... 1 USB Device(s) found
scanning bus 2 for devices... 1 USB Device(s) found
scanning bus 3 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
3042 bytes read in 1 ms (2.9 MiB/s)
## Executing script at 4fc00000
U-boot loaded from SD
Boot script loaded from mmc
143 bytes read in 0 ms
30956 bytes read in 7 ms (4.2 MiB/s)
478 bytes read in 3 ms (155.3 KiB/s)
Applying kernel provided DT overlay sun50i-h5-cpu-clock-1.0GHz-1.1v.dtbo
failed on fdt_overlay_apply(): FDT_ERR_NOTFOUND
504 bytes read in 6 ms (82 KiB/s)
Applying kernel provided DT overlay sun50i-h5-usbhost1.dtbo
failed on fdt_overlay_apply(): FDT_ERR_BADMAGIC
base fdt does did not have a /__symbols__ node
make sure you've compiled with -@
504 bytes read in 5 ms (97.7 KiB/s)
Applying kernel provided DT overlay sun50i-h5-usbhost2.dtbo
failed on fdt_overlay_apply(): FDT_ERR_BADMAGIC
base fdt does did not have a /__symbols__ node
make sure you've compiled with -@
Error applying DT overlays, restoring original DT
30956 bytes read in 7 ms (4.2 MiB/s)
10302643 bytes read in 506 ms (19.4 MiB/s)
21235720 bytes read in 1038 ms (19.5 MiB/s)
## Loading init Ramdisk from Legacy Image at 4fe00000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    10302579 Bytes = 9.8 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 4fa00000
   Booting using the fdt blob at 0x4fa00000
EHCI failed to shut down host controller.
   Loading Ramdisk to 4962c000, end 49fff473 ... OK
   Loading Device Tree to 0000000049621000, end 000000004962b8eb ... OK


Starting kernel ...

Loading, please wait...
Starting version 241
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: Waiting for root file system ... 
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.

Gave up waiting for root file system device.  Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT!  UUID=f17c5ebe-dc6c-4c52-831e-f2265 does not exist.  Dropping to a shell!
Rebooting automatically due to panic= boot argument
[   43.246465] reboot: Restarting system

/dev/sdb1: UUID="f17c5ebe-dc6c-4c52-831e-f226539501a5" TYPE="ext4" PARTUUID="513bc63a-01"

root@npi-neo2-24(192.168.6.24):/mnt/sdb1/boot# more armbianEnv.txt
verbosity=1
console=serial
overlay_prefix=sun50i-h5
overlays=cpu-clock-1.0GHz-1.1v usbhost1 usbhost2
rootdev=UUID=f17c5ebe-dc6c-4c52-831e-f226539501a5
rootfstype=ext4
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u


f17c5ebe-dc6c-4c52-831e-f2265
f17c5ebe-dc6c-4c52-831e-f226539501a5
f17c5ebe-dc6c-4c52-831e-f226539501a5
f17c5ebe-dc6c-4c52-831e-f226539501a5

 

Dont know why kernel 5.9.0rc2 was booting in the TTL-Log with U-Boot 2019.04-armbian (Nov 18 2019 - 21:52:14 +0100)

Is there more to do as installing the new u-boot.deb? Wasnt there a option to update u-boot via armbian-config?

e.g.

Install to/update boot loader ==> (2) Install/Update Bootloader on SD/eMMC

 

I think (1) Boot from SD - system on SATA, USB or NVMe isnt the right for me :( 

<
5kft

5kft

Posted
Posted

@guidol thanks for the detail!

 

Quote

/boot is big enough, because armbian is only using 1 partition (on my install) and Iam using a 8GB MicroSDCard 

 

Ah, I'm too used to running different filesystems for "/", so I always have different partitions :)

 

Quote

2.) the kernel 5.9.0rc2 couldnt load the dtb-overlays (also while now booting from the card and root 7 is there, but the overlays doenst seem to be

compatibe):

 

What it looks like is that the u-boot dpkg install failed for 5.9.  When you used "dpkg -i" to install your 5.9 .debs, did you get any messages from dpkg regarding a package conflict for u-boot?  Could you post the output of "dpkg --list | grep boot" for your 5.8 install?

 

2 hours ago, guidol said:

Dont know why kernel 5.9.0rc2 was booting in the TTL-Log with U-Boot 2019.04-armbian (Nov 18 2019 - 21:52:14 +0100)

Is there more to do as installing the new u-boot.deb? Wasnt there a option to update u-boot via armbian-config?

e.g.

Install to/update boot loader ==> (2) Install/Update Bootloader on SD/eMMC

 

I think (1) Boot from SD - system on SATA, USB or NVMe isnt the right for me :( 

 

Correct - you want to use "Install/Update Bootloader on SD/eMMC".

 

Also, as a test, I just reinstalled 5.9 on one of my NEO2s, and it works great, so it should work for you.  This is why I suspect an installation issue with the bootloader .deb.

 

Spoiler

U-Boot SPL 2020.04-armbian (Sep 05 2020 - 12:54:53 +0000)
DRAM: 512 MiB
Trying to boot from MMC1
NOTICE:  BL31: v2.3(debug):a41ca4c-dirty
NOTICE:  BL31: Built : 12:54:46, Sep  5 2020
NOTICE:  BL31: Detected Allwinner H5 SoC (1718)
NOTICE:  BL31: Found U-Boot DTB at 0x4090ab0, model: FriendlyARM NanoPi NEO 2
INFO:    ARM GICv2 driver initialized
INFO:    Configuring SPC Controller
NOTICE:  PMIC: Assuming H5 reference regulator design
INFO:    BL31: Platform setup done
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for 855873 was applied
WARNING: BL31: cortex_a53: CPU workaround for 1530924 was missing!
NOTICE:  PSCI: System suspend is unavailable
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x4a000000
INFO:    SPSR = 0x3c9


U-Boot 2020.04-armbian (Sep 05 2020 - 12:54:53 +0000) Allwinner Technology

CPU:   Allwinner H5 (SUN50I)
Model: FriendlyARM NanoPi NEO 2
DRAM:  512 MiB
MMC:   mmc@1c0f000: 0
Loading Environment from FAT... In:    serial
Out:   serial
Err:   serial
NanoPi NEO2 v1.1 detected
Net:   phy interface7
eth0: ethernet@1c30000
** Reading file would overwrite reserved memory **
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... 2 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
3173 bytes read in 2 ms (1.5 MiB/s)
## Executing script at 4fc00000
U-boot loaded from SD
Boot script loaded from mmc
183 bytes read in 1 ms (178.7 KiB/s)
30952 bytes read in 5 ms (5.9 MiB/s)
504 bytes read in 4 ms (123 KiB/s)
Applying kernel provided DT overlay sun50i-h5-usbhost1.dtbo
504 bytes read in 4 ms (123 KiB/s)
Applying kernel provided DT overlay sun50i-h5-usbhost2.dtbo
4191 bytes read in 4 ms (1022.5 KiB/s)
Applying kernel provided DT fixup script (sun50i-h5-fixup.scr)
## Executing script at 45000000
10329995 bytes read in 493 ms (20 MiB/s)
21235720 bytes read in 1013 ms (20 MiB/s)
## Loading init Ramdisk from Legacy Image at 4fe00000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    10329931 Bytes = 9.9 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 4fa00000
   Booting using the fdt blob at 0x4fa00000
EHCI failed to shut down host controller.
   Loading Ramdisk to 49626000, end 49ffff4b ... OK
   Loading Device Tree to 00000000495b6000, end 0000000049625fff ... OK

Starting kernel ...

Loading, please wait...
Starting version 241
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.33.1
[/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1
/dev/mmcblk0p1: clean, 40142/92544 files, 313189/369664 blocks
done.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.

Welcome to Armbian 20.08.0-trunk Buster!

[  OK  ] Listening on Syslog Socket.
[  OK  ] Listening on initctl Compatibility Named Pipe.
[  OK  ] Listening on udev Kernel Socket.
[  OK  ] Listening on Journal Socket (/dev/log).
     ...

 

 

guidol

guidol

Posted
Posted
4 hours ago, 5kft said:

 

What it looks like is that the u-boot dpkg install failed for 5.9.  When you used "dpkg -i" to install your 5.9 .debs, did you get any messages from dpkg regarding a package conflict for u-boot?  Could you post the output of "dpkg --list | grep boot" for your 5.8 install?

 

@5kft I didnt see (and expect) any errors while installing the u-boot package via dpkg, because it did work for months/years so well
on all of my SBCs :) 

 

here the dpkg-output you requested: 

root@npi-neo2-22(192.168.6.22):~# dpkg --list | grep boot
ii  klibc-utils                      2.0.6-1                             arm64        small utilities built with klibc for early boot
ii  linux-u-boot-nanopineo2-dev      20.08.0-trunk                       arm64        Uboot loader 2020.04
ii  sysfsutils                       2.1.0+repack-5                      arm64        sysfs query tool and boot-time setup
ii  u-boot-tools                     2019.01+dfsg-7                      arm64        companion tools for Das U-Boot bootloader

 

5kft

5kft

Posted
Posted

@guidol - thanks!  U-boot won't install if you try installing -dev over -current (for example) - this is what I wanted to see.  I just did a full build of v5.9-rc2 from master and verified that it works fine on my NEO2 - do you want to give it a try?  https://drive.google.com/file/d/1UBJY_PT66cA_MLRYxsgHsvX-Qex01ZMr/ (just "sudo dpkg -i *.deb" the files in this tarfile)  This could hopefully help narrow down if it is a build problem or something else.

guidol

guidol

Posted
Posted
2 hours ago, 5kft said:

@guidol - thanks!  U-boot won't install if you try installing -dev over -current (for example) 

 

My Neo2 is/was also  with 5.8.3 at -dev:
  

Welcome to Armbian buster with Linux 5.8.3-sunxi64

package bsp-kernel[20.08.0-trunk] u-boot[20.08.0-trunk] dtb   [20.08.0-trunk]
firmware          [20.08.0-trunk] config[20.08.0-trunk] branch[dev]

root@npi-neo2-22(192.168.6.22):~# ls -l /toshiba/neo2_kernel_583/
total 41984
-rwxrwxrwx 1 root root    43636 Aug 24 20:56 armbian-config_20.08.0-trunk_all.deb
-rwxrwxrwx 1 root root  6671580 Aug 24 20:56 armbian-firmware_20.08.0-trunk_all.deb
-rwxrwxrwx 1 root root    77316 Aug 24 20:55 linux-dtb-dev-sunxi64_20.08.0-trunk_arm64.deb
-rwxrwxrwx 1 root root 32077924 Aug 24 20:56 linux-image-dev-sunxi64_20.08.0-trunk_arm64.deb
-rwxrwxrwx 1 root root   268324 Aug 24 20:47 linux-u-boot-dev-nanopineo2_20.08.0-trunk_arm64.deb

5.8.3 System diagnosis information has been uploaded to http://ix.io/2wfb 

 

and my u-boot .deb for 5.9.0rc2 was also at -dev level:
  

root@npi-neo2-22(192.168.6.22):~# ls -l /toshiba/neo2_kernel_590rc2/
total 41984
-rwxrwxrwx 1 root root    43648 Sep  4 18:06 armbian-config_20.08.0-trunk_all.deb
-rwxrwxrwx 1 root root  6775404 Sep  4 18:06 armbian-firmware_20.08.0-trunk_all.deb
-rwxrwxrwx 1 root root    77584 Sep  4 18:05 linux-dtb-dev-sunxi64_20.08.0-trunk_arm64.deb
-rwxrwxrwx 1 root root 32199212 Sep  4 18:06 linux-image-dev-sunxi64_20.08.0-trunk_arm64.deb
-rwxrwxrwx 1 root root   268036 Sep  4 17:54 linux-u-boot-dev-nanopineo2_20.08.0-trunk_arm64.deb

 

5kft

5kft

Posted
Posted
47 minutes ago, guidol said:

My Neo2 is/was also  with 5.8.3 at -dev:

 

Understood - just have no idea why it didn't install correctly.

5kft

5kft

Posted
Posted

Yes, but he's running a version from last year.  But, I don't think that's the problem because his old u-boot is booting 5.8 okay.  It's more like his DT installation is broken or something.  This is what is confusing because this is literally the same for 5.9.  That's why I'd like to try a consistent baseline to debug (e.g., try the build I posted above).

guidol

guidol

Posted
Posted
1 hour ago, 5kft said:

Yes, but he's running a version from last year.  But, I don't think that's the problem because his old u-boot is booting 5.8 okay.  It's more like his DT installation is broken or something. 

@5kft another thing:
I got a second Neo2, but the 1GB Ram version which was running kernel 5.8.3 with Ubuntu focal

This Neo2 has been upgraded via apt update/upgrade to kernel 5.9.0rc2 and DOES BOOT:

System diagnosis information will now be uploaded to http://ix.io/2wiQ

 

I did try this also on my first Neo2 (512MB Ram, Version 1.0) which was running kernel 5.8.3 but with Debian buster

and it failed via apt update/upgrade like before when I did install the newly compiled .deb files :(

 

Now I did know how to go back - this one is back on 5.8.3 where the dtb-overlay for usbhost 1&2 could be loaded

 

I do now compile kernel 5.9.0rc2 with Ubuntu focal and try to put this image on my first/smaller Neo2

(I also have a third one in the smaller configuration which is also running 5.8.3 with Debian Buster)

 

 

5kft

5kft

Posted
Posted
8 minutes ago, guidol said:

I got a second Neo2, but the 1GB Ram version which was running kernel 5.8.3 with Ubuntu focal

This Neo2 has been upgraded via apt update/upgrade to kernel 5.9.0rc2 and DOES BOOT

 

OK, interesting - to confirm, this this second NEO2 a v1.1?

guidol

guidol

Posted
Posted
8 minutes ago, 5kft said:

 

OK, interesting - to confirm, this this second NEO2 a v1.1?

@5kft I think so...got no TTL-Log because all are screwed in the silver NAS-Case from FriendlyARM.

I did bought it later than the small ones and it was named Neo2 LTS at this time.

 

Can I check this via commandline?

5kft

5kft

Posted
Posted
1 minute ago, guidol said:

I think so...got no TTL-Log because all are screwed in the silver NAS-Case from FriendlyARM.

I did bought it later than the small ones and it was named Neo2 LTS at this time.

 

Can I check this via commandline?

 

OK, it's very likely a v1.1.  If you "ls /sys/class/leds/" do you see "green" and "red" LED entries or "red" and "blue" LED entries?

guidol

guidol

Posted
Posted
7 minutes ago, 5kft said:

 

OK, it's very likely a v1.1.  If you "ls /sys/class/leds/" do you see "green" and "red" LED entries or "red" and "blue" LED entries?

@5kft the 1GB version has:
  

root@npi-neo2-24(192.168.6.24):~# ls -l /sys/class/leds
total 0
lrwxrwxrwx 1 root root 0 Sep  6 14:40 nanopi:green:status -> ../../devices/platform/leds/leds/nanopi:green:status
lrwxrwxrwx 1 root root 0 Sep  6 14:40 nanopi:red:pwr -> ../../devices/platform/leds/leds/nanopi:red:pwr

and the 512MB (Version 1.0) has: 

root@npi-neo2-22(192.168.6.22):~# ls -l /sys/class/leds
total 0
lrwxrwxrwx 1 root root 0 Jan  1  1970 nanopi:blue:status -> ../../devices/platform/leds/leds/nanopi:blue:status
lrwxrwxrwx 1 root root 0 Jan  1  1970 nanopi:green:pwr -> ../../devices/platform/leds/leds/nanopi:green:pwr


root@npi-neo2-23(192.168.6.23):~# ls -l /sys/class/leds
total 0
lrwxrwxrwx 1 root root 0 Jan  1  1970 nanopi:blue:status -> ../../devices/platform/leds/leds/nanopi:blue:status
lrwxrwxrwx 1 root root 0 Jan  1  1970 nanopi:green:pwr -> ../../devices/platform/leds/leds/nanopi:green:pwr

 

5kft

5kft

Posted
Posted

OK, so you don't have a problem with the v1.1, but you do have a problem with the v1.0.

 

Doing a quick look at the bootloader logs, here is what I see so far: 

U-Boot 2019.04-armbian (Nov 18 2019 - 21:52:14 +0100) Allwinner Technology

CPU:   Allwinner H5 (SUN50I)
Model: FriendlyARM NanoPi NEO 2
DRAM:  512 MiB
MMC:   mmc@1c0f000: 0
Loading Environment from EXT4... ** File not found /boot/boot.env **
** Unable to read "/boot/boot.env" from mmc0:1 **
In:    serial
Out:   serial
Err:   serial
NanoPi NEO2 v1.0 detected                           #### this is your v1.0 board
Net:   phy interface7
eth0: ethernet@1c30000
** Reading file would overwrite reserved memory **
There is no valid bmp file at the given address     #### this is strange - it can't find the LCD bitmap (??)
starting USB...
USB0:   USB EHCI 1.00
USB1:   USB OHCI 1.0
USB2:   USB EHCI 1.00
USB3:   USB OHCI 1.0
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 1 for devices... 1 USB Device(s) found
scanning bus 2 for devices... 1 USB Device(s) found
scanning bus 3 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
3042 bytes read in 1 ms (2.9 MiB/s)
## Executing script at 4fc00000
U-boot loaded from SD
Boot script loaded from mmc
143 bytes read in 0 ms
30956 bytes read in 7 ms (4.2 MiB/s)            #### this is sun50i-h5-nanopi-neo2.dtb, which is correct
478 bytes read in 3 ms (155.3 KiB/s)            #### this is sun50i-h5-cpu-clock-1.0GHz-1.1v.dtbo, which is correct
Applying kernel provided DT overlay sun50i-h5-cpu-clock-1.0GHz-1.1v.dtbo
failed on fdt_overlay_apply(): FDT_ERR_NOTFOUND #### this is strange
504 bytes read in 6 ms (82 KiB/s)               #### this is sun50i-h5-usbhost1.dtbo
Applying kernel provided DT overlay sun50i-h5-usbhost1.dtbo
failed on fdt_overlay_apply(): FDT_ERR_BADMAGIC #### strange
base fdt does did not have a /__symbols__ node
make sure you've compiled with -@
504 bytes read in 5 ms (97.7 KiB/s)             #### sun50i-h5-usbhost2.dtbo
Applying kernel provided DT overlay sun50i-h5-usbhost2.dtbo
failed on fdt_overlay_apply(): FDT_ERR_BADMAGIC
base fdt does did not have a /__symbols__ node
make sure you've compiled with -@
Error applying DT overlays, restoring original DT
30956 bytes read in 7 ms (4.2 MiB/s)
10302643 bytes read in 506 ms (19.4 MiB/s)
21235720 bytes read in 1038 ms (19.5 MiB/s)

Could you post both the v5.8.3 dtb .deb and the v5.9-rc2 dtb .deb that you are using?  It be helpful to take a look and see what the differences are.

guidol

guidol

Posted
Posted
4 minutes ago, 5kft said:

Could you post both the v5.8.3 dtb .deb and the v5.9-rc2 dtb .deb that you are using?  It be helpful to take a look and see what the differences are.

the .debs I did compile on my armbian-build-system.
But I also got the same problem with the 5.9.0rc2-dtb-deb from apt update/upgrade.

 

The newly compiles 5.9.0rc2 Ubuntu focal does start without problem (no dtbo-errors) on the small Neo2.

 

Now Iam thinking about doing the same with a fresh compiled 5.9.0rc2 with debian buster?

5_8_3_linux-dtb-dev-sunxi64_20.08.0-trunk_arm64.deb 5_9_0_rc2_linux-dtb-dev-sunxi64_20.08.0-trunk_arm64.deb

5kft

5kft

Posted
Posted
5 minutes ago, guidol said:

Now Iam thinking about doing the same with a fresh compiled 5.9.0rc2 with debian buster?

 

I think that would definitely be worth a try.

guidol

guidol

Posted
Posted
25 minutes ago, 5kft said:

 

I think that would definitely be worth a try.

The small Neo2 is also booting fine with 5.9.0rc2 debian buster:

Spoiler

U-Boot SPL 2020.04-armbian (Aug 24 2020 - 20:46:49 +0300)
DRAM: 512 MiB
Trying to boot from MMC1
NOTICE:  BL31: v2.3(debug):8d0a3bb-dirty
NOTICE:  BL31: Built : 20:46:44, Aug 24 2020
NOTICE:  BL31: Detected Allwinner H5 SoC (1718)
NOTICE:  BL31: Found U-Boot DTB at 0x4090ab0, model: FriendlyARM NanoPi NEO 2
INFO:    ARM GICv2 driver initialized
INFO:    Configuring SPC Controller
NOTICE:  PMIC: Assuming H5 reference regulator design
INFO:    BL31: Platform setup done
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for 855873 was applied
WARNING: BL31: cortex_a53: CPU workaround for 1530924 was missing!
NOTICE:  PSCI: System suspend is unavailable
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x4a000000
INFO:    SPSR = 0x3c9


U-Boot 2020.04-armbian (Aug 24 2020 - 20:46:49 +0300) Allwinner Technology

CPU:   Allwinner H5 (SUN50I)
Model: FriendlyARM NanoPi NEO 2
DRAM:  512 MiB
MMC:   mmc@1c0f000: 0
Loading Environment from FAT... In:    serial
Out:   serial
Err:   serial
NanoPi NEO2 v1.0 detected
Net:   phy interface7
eth0: ethernet@1c30000
** Reading file would overwrite reserved memory **
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
3042 bytes read in 3 ms (990.2 KiB/s)
## Executing script at 4fc00000
U-boot loaded from SD
Boot script loaded from mmc
216 bytes read in 2 ms (105.5 KiB/s)
30901 bytes read in 7 ms (4.2 MiB/s)
478 bytes read in 6 ms (77.1 KiB/s)
Applying kernel provided DT overlay sun50i-h5-cpu-clock-1.0GHz-1.1v.dtbo
504 bytes read in 6 ms (82 KiB/s)
Applying kernel provided DT overlay sun50i-h5-usbhost1.dtbo
504 bytes read in 6 ms (82 KiB/s)
Applying kernel provided DT overlay sun50i-h5-usbhost2.dtbo
4191 bytes read in 6 ms (681.6 KiB/s)
Applying kernel provided DT fixup script (sun50i-h5-fixup.scr)
## Executing script at 44000000
10279383 bytes read in 492 ms (19.9 MiB/s)
20496392 bytes read in 979 ms (20 MiB/s)
## Loading init Ramdisk from Legacy Image at 4fe00000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    10279319 Bytes = 9.8 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 4fa00000
   Booting using the fdt blob at 0x4fa00000
EHCI failed to shut down host controller.
   Loading Ramdisk to 49632000, end 49fff997 ... OK
   Loading Device Tree to 00000000495c2000, end 0000000049631fff ... OK

Starting kernel ...

Loading, please wait...
Starting version 241
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.33.1
[/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1
/dev/mmcblk0p1: clean, 46317/945888 files, 623204/3849616 blocks
done.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.

Welcome to Debian GNU/Linux 10 (buster)!
 

 

System diagnosis information will now be uploaded to http://ix.io/2wjt

 

USB port are recognized ans also the /dev/sda(1) on the USB-Port-controller :) 

Dont know why this didnt work as upgrade from 5.8.3

 

Now I will mount the old SDCard and transfer the config-files- now for the first small Neo2 - laster for the second one :( 

5kft

5kft

Posted
Posted
2 minutes ago, guidol said:

The small Neo2 is also booting fine with 5.9.0rc2 debian buster

 

Yes!  I am glad to hear this :thumbup:

dolphs

dolphs

Posted
  • Author
Posted

just built and flashed " Armbian_20.11.0-trunk_Orangepioneplus_buster_dev_5.9.0-rc4_minimal.img " 

 

 

Noticed from the patching logs :

 

Are these patches still needed for 5.9 ?

1/ general-packaging-5.6.y.patch
2/ add-missing-H6-cpu-opp-in-5.7.y.patch 

 

 

Rgd WIFI-galore ...

Would it be possible to exclude WIFI patches using option " EXTRAWIFI=no "

If EXTRAWIFI=yes i( or flag not being used ) by all means go for it and pump it in ...


1/ disable-debug-rtl8189fs.patch

The text leading up to this was:
--------------------------
|diff --git a/drivers/net/wireless/rtl8189fs/include/autoconf.h b/drivers/net/wireless/rtl8189fs/include/autoconf.h
|index 44efe42..6f40903 100644
|--- a/drivers/net/wireless/rtl8189fs/include/autoconf.h
|+++ b/drivers/net/wireless/rtl8189fs/include/autoconf.h
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored

2/ disable-debug-rtl8723ds.patch

The text leading up to this was:
--------------------------
|diff --git a/drivers/net/wireless/rtl8723ds/include/autoconf.h b/drivers/net/wireless/rtl8723ds/include/autoconf.h
|index 9dd1a3e..ed1d27e 100644
|--- a/drivers/net/wireless/rtl8723ds/include/autoconf.h
|+++ b/drivers/net/wireless/rtl8723ds/include/autoconf.h
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored

3/ wifi-4003-fix-sha256_state-clashes.patch
4/ realtek files: rtw_security.h, ioctl_cfg80211, etc
5/ wifi-4004-fix-cfg80211-for-5.8.patch

 

 

The compilation logs contains tons of warnings which I exclude for now.

 

 

Flashed this image and board booted fine!
Splendid work guys, really looking nice already, also BUILD=minimal excluded armbian-config, guess that is fine !

  

root@orangepioneplus's password:
  ___  ____  _    ___
 / _ \|  _ \(_)  / _ \ _ __   ___   _
| | | | |_) | | | | | | '_ \ / _ \_| |_
| |_| |  __/| | | |_| | | | |  __/_   _|
 \___/|_|   |_|  \___/|_| |_|\___| |_|

Welcome to Armbian 20.11.0-trunk Buster with Linux 5.9.0-rc4-sunxi64

No end-user support: built from trunk

System load:   2%               Up time:       4 min
Memory usage:  7% of 985M       IP:            192.168.10.134
CPU temp:      44°C             Usage of /:    5% of 15G

[ Menu-driven system configuration (beta): sudo apt update && sudo apt install armbian-config ]

Warning: a reboot is needed to finish resizing the filesystem
Please reboot the system as soon as possible

 

dolphs

dolphs

Posted
  • Author
Posted
6 minutes ago, dolphs said:

Warning: a reboot is needed to finish resizing the filesystem Please reboot the system as soon as possible

 

just that one does not disappear , at least even not after rebooting 3 times ....

guidol

guidol

Posted
Posted
On 9/6/2020 at 5:56 PM, 5kft said:

 

Yes!  I am glad to hear this :thumbup:

@5kft Today I had a strange thing :( 
Because the Neo2 does run normally fine - with the default voltage - up to 1008Mhz I did try to activate the 1.0Ghz/1.1V dtb-overlay,

but after activating the dtbo and reboot the Neo2.
But the Neo2 failed in appying all dtbo (also USB) and does only start in emergency mode (which isnt accessable from outside the NAS-case):

Spoiler

U-Boot SPL 2020.04-armbian (Sep 06 2020 - 17:07:26 +0300)
DRAM: 512 MiB
Trying to boot from MMC1
NOTICE:  BL31: v2.3(debug):a41ca4c-dirty
NOTICE:  BL31: Built : 17:07:21, Sep  6 2020
NOTICE:  BL31: Detected Allwinner H5 SoC (1718)
NOTICE:  BL31: Found U-Boot DTB at 0x4090ab0, model: FriendlyARM NanoPi NEO 2
INFO:    ARM GICv2 driver initialized
INFO:    Configuring SPC Controller
NOTICE:  PMIC: Assuming H5 reference regulator design
INFO:    BL31: Platform setup done
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for 855873 was applied
WARNING: BL31: cortex_a53: CPU workaround for 1530924 was missing!
NOTICE:  PSCI: System suspend is unavailable
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x4a000000
INFO:    SPSR = 0x3c9


U-Boot 2020.04-armbian (Sep 06 2020 - 17:07:26 +0300) Allwinner Technology

CPU:   Allwinner H5 (SUN50I)
Model: FriendlyARM NanoPi NEO 2
DRAM:  512 MiB
MMC:   mmc@1c0f000: 0
Loading Environment from FAT... In:    serial
Out:   serial
Err:   serial
NanoPi NEO2 v1.0 detected
Net:   phy interface7
eth0: ethernet@1c30000
** Reading file would overwrite reserved memory **
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
3173 bytes read in 3 ms (1 MiB/s)
## Executing script at 4fc00000
U-boot loaded from SD
Boot script loaded from mmc
254 bytes read in 2 ms (124 KiB/s)
30956 bytes read in 6 ms (4.9 MiB/s)
478 bytes read in 4 ms (116.2 KiB/s)
Applying kernel provided DT overlay sun50i-h5-cpu-clock-1.0GHz-1.1v.dtbo
failed on fdt_overlay_apply(): FDT_ERR_NOTFOUND
504 bytes read in 5 ms (97.7 KiB/s)
Applying kernel provided DT overlay sun50i-h5-usbhost1.dtbo
failed on fdt_overlay_apply(): FDT_ERR_BADMAGIC
base fdt does did not have a /__symbols__ node
make sure you've compiled with -@
504 bytes read in 4 ms (123 KiB/s)
Applying kernel provided DT overlay sun50i-h5-usbhost2.dtbo
failed on fdt_overlay_apply(): FDT_ERR_BADMAGIC
base fdt does did not have a /__symbols__ node
make sure you've compiled with -@
Error applying DT overlays, restoring original DT
30956 bytes read in 6 ms (4.9 MiB/s)
10328705 bytes read in 494 ms (19.9 MiB/s)
21235720 bytes read in 1013 ms (20 MiB/s)
## Loading init Ramdisk from Legacy Image at 4fe00000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    10328641 Bytes = 9.9 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 4fa00000
   Booting using the fdt blob at 0x4fa00000
EHCI failed to shut down host controller.
   Loading Ramdisk to 49626000, end 49fffa41 ... OK
   Loading Device Tree to 000000004961b000, end 00000000496258eb ... OK

Starting kernel ...

Loading, please wait...
Starting version 241
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.33.1
[/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1
/dev/mmcblk0p1: recovering journal
/dev/mmcblk0p1: clean, 46623/925120 files, 451140/3849616 blocks
done.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.
 


After booting with TTL-serial-dongle I logged in emergency mode with the root-password and deactivated the 1.0Ghz/1.1V-dtbo saves/rebootet.

And now its working fine again - this the the NEW INSTALLED 5.9.0rc2/debian buster on my small Neo2 (512MB)

 

cpufreq-info only does show cpu-frequencys from 480 to 816Mhz :(

So the dev-dtb is very conservative at the CPU-Speed for the Neo2

dolphs

dolphs

Posted
  • Author
Posted

As H6 got built,

I owe boards below - is there any interest if I'd share default rc4 buster images for these ?

Just need a location to upload these 

./compile.sh BRANCH=dev RELEASE=buster BUILD_MINIMAL=yes BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no

- H2+:  orangepizero lts

- H3:  orangepi lite, Banana Pi BPI-M2+

- H5 : neo2 1.0/ neo2 1.1, neo2 black 

1
5kft

5kft

Posted
Posted
2 hours ago, guidol said:

After booting with TTL-serial-dongle I logged in emergency mode with the root-password and deactivated the 1.0Ghz/1.1V-dtbo saves/rebootet.

And now its working fine again - this the the NEW INSTALLED 5.9.0rc2/debian buster on my small Neo2 (512MB)

 

@guidol - thank you, the logs you provided were exactly what I needed!  I have fixed the issue with the overclock overlays for -dev, and have push the changes to master (https://github.com/armbian/build/commit/9a096fc557367668e01736400d2c5cb4c8c28a75).  Please give these changes a try and let me know how it goes!

1
guidol

guidol

Posted
Posted
55 minutes ago, 5kft said:

 

@guidol - thank you, the logs you provided were exactly what I needed!  I have fixed the issue with the overclock overlays for -dev.  Please give these changes a try and let me know how it goes!

 

@5kft - No Problem - its nice to help getting a stable armbian ;) 

I could recognize what your fix for the overlay patch will do :( What will I see as rection when I would recompile the kernel/dtb?

 

For now I edited the dtbs on v1.0 and v1.1 Neo2 that also 960Mz and 1008Mhz is using the same voltage as 816Mhz - so I got these frequencies again (because they where stable for me the last years :) ) : 

root@npi-neo2-24(192.168.6.24):~# cpufreq-info
  hardware limits: 480 MHz - 1.01 GHz
  available frequency steps: 480 MHz, 648 MHz, 816 MHz, 960 MHz, 1.01 GHz
  current policy: frequency should be within 480 MHz and 1.01 GHz.
                  The governor "conservative" may decide which speed to use
                  within this range.

 

5kft

5kft

Posted
Posted
2 minutes ago, guidol said:

What will I see as rection when I would recompile the kernel/dtb?

 

This fixes operation for these overlays under v5.9 so that they work correctly (just like under v5.8) :)

1
Werner

Werner

Posted
Posted
1 minute ago, guidol said:

@5kft could you please tell us when @Igor has accepted this commit? I couldnt see the accept at the url above...

From what I saw it was a direct commit to master without PR. Therefore nobody had to accept and merge it.

1
guidol

guidol

Posted
Posted
22 hours ago, 5kft said:

 

This fixes operation for these overlays under v5.9 so that they work correctly (just like under v5.8) :)

@5kft Yes - does work now correctly. I compiled the kernel/dtb 5.9.0.rc4 after your commit and installed all files. Then I activated the 1.0Ghz/1.1v dtbo and rebooted. All dtbo-files are now loaded correctly:
 

Spoiler

U-Boot SPL 2020.04-armbian (Sep 06 2020 - 17:07:26 +0300)
DRAM: 512 MiB
Trying to boot from MMC1
NOTICE:  BL31: v2.3(debug):a41ca4c-dirty
NOTICE:  BL31: Built : 17:07:21, Sep  6 2020
NOTICE:  BL31: Detected Allwinner H5 SoC (1718)
NOTICE:  BL31: Found U-Boot DTB at 0x4090ab0, model: FriendlyARM NanoPi NEO 2
INFO:    ARM GICv2 driver initialized
INFO:    Configuring SPC Controller
NOTICE:  PMIC: Assuming H5 reference regulator design
INFO:    BL31: Platform setup done
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for 855873 was applied
WARNING: BL31: cortex_a53: CPU workaround for 1530924 was missing!
NOTICE:  PSCI: System suspend is unavailable
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x4a000000
INFO:    SPSR = 0x3c9


U-Boot 2020.04-armbian (Sep 06 2020 - 17:07:26 +0300) Allwinner Technology

CPU:   Allwinner H5 (SUN50I)
Model: FriendlyARM NanoPi NEO 2
DRAM:  512 MiB
MMC:   mmc@1c0f000: 0
Loading Environment from FAT... In:    serial
Out:   serial
Err:   serial
NanoPi NEO2 v1.0 detected
Net:   phy interface7
eth0: ethernet@1c30000
** Reading file would overwrite reserved memory **
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
3173 bytes read in 3 ms (1 MiB/s)
## Executing script at 4fc00000
U-boot loaded from SD
Boot script loaded from mmc
254 bytes read in 2 ms (124 KiB/s)
30956 bytes read in 7 ms (4.2 MiB/s)
477 bytes read in 5 ms (92.8 KiB/s)
Applying kernel provided DT overlay sun50i-h5-cpu-clock-1.0GHz-1.1v.dtbo
504 bytes read in 5 ms (97.7 KiB/s)
Applying kernel provided DT overlay sun50i-h5-usbhost1.dtbo
504 bytes read in 5 ms (97.7 KiB/s)
Applying kernel provided DT overlay sun50i-h5-usbhost2.dtbo
4191 bytes read in 5 ms (818.4 KiB/s)
Applying kernel provided DT fixup script (sun50i-h5-fixup.scr)
## Executing script at 45000000
10329821 bytes read in 494 ms (19.9 MiB/s)
21235720 bytes read in 1014 ms (20 MiB/s)
## Loading init Ramdisk from Legacy Image at 4fe00000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    10329757 Bytes = 9.9 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 4fa00000
   Booting using the fdt blob at 0x4fa00000
EHCI failed to shut down host controller.
   Loading Ramdisk to 49626000, end 49fffe9d ... OK
   Loading Device Tree to 00000000495b6000, end 0000000049625fff ... OK

Starting kernel ...

Loading, please wait...
Starting version 241
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.33.1
[/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1
/dev/mmcblk0p1: clean, 46639/925120 files, 451395/3849616 blocks
done.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.

Welcome to Armbian 20.11.0-trunk Buster!
 

 

And all CPU-frequencies are available up to the 1008Mhz (1.01Ghz) :) 

1
guidol

guidol

Posted
Posted
On 9/9/2020 at 11:32 AM, dolphs said:

 

just that one does not disappear , at least even not after rebooting 3 times ....

resize message is also here on a actual compiled 5.9.0rc4 and doesnt go away on a NanoPi Neo Core2, but disk is already resized ;)

System diagnosis information will now be uploaded to http://ix.io/2x6c 

Warning: a reboot is needed to finish resizing the filesystem
Please reboot the system as soon as possible


root@npi-neo-core2-21(192.168.6.21):~# df
Filesystem     1K-blocks    Used Available Use% Mounted on

microsd
/dev/mmcblk0p1   7455192 1363500   5983732  19% /

emmc
/dev/mmcblk2p1   7444644 1402308   5647084  20% /


root@npi-neo-core2-21(192.168.6.21):~# resize2fs /dev/mmcblk2p1
resize2fs 1.44.5 (15-Dec-2018)
The filesystem is already 1907712 (4k) blocks long.  Nothing to do!

 

dolphs

dolphs

Posted
  • Author
Posted

Chaps what about these,  

first one to be looked in to on ad hoc basis and rgd WiFi galore a Jira story perhaps ?

 

On 9/9/2020 at 10:25 AM, dolphs said:

Noticed from the patching logs :

 

Are these patches still needed for 5.9 ?

1/ general-packaging-5.6.y.patch
2/ add-missing-H6-cpu-opp-in-5.7.y.patch 

 

 

Rgd WIFI-galore ...

Would it be possible to exclude WIFI patches using option " EXTRAWIFI=no "

If EXTRAWIFI=yes i( or flag not being used ) by all means go for it and pump it in ...

 

Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept