Switching SUNXI-DEV to 5.4.y


Recommended Posts

understood martinayotte,  loiter for a while taking your rest!

 

Meanwhile booted the dev image built - just sharing some info for the ones that are interested.

One thing that immediately caught my attention it appears CPUFreq is still WIP ?

Most likely this a .config kernel thingie, which simply needs to be enabled or more work to do ?

 

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

Welcome to Armbian Buster with Linux 5.4.0-rc8-sunxi64

System load:   1.44 0.56 0.22   Up time:       4 min
Memory usage:  12 % of 989MB    IP:            192.168.10.121
CPU temp:      45°C
Usage of /:    11% of 7.1G

Last login: Wed Nov 27 02:34:54 2019 from 192.168.10.98

root@orangepioneplus:~# cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
  no or unknown cpufreq driver is active on this CPU
  maximum transition latency: 4294.55 ms.
analyzing CPU 1:
  no or unknown cpufreq driver is active on this CPU
  maximum transition latency: 4294.55 ms.
analyzing CPU 2:
  no or unknown cpufreq driver is active on this CPU
  maximum transition latency: 4294.55 ms.
analyzing CPU 3:
  no or unknown cpufreq driver is active on this CPU
  maximum transition latency: 4294.55 ms.

 

Link to post
Share on other sites
Want Armbian t-shirt or a cup?

8 hours ago, dolphs said:

understood martinayotte,  loiter for a while taking your rest!

 

Meanwhile booted the dev image built - just sharing some info for the ones that are interested.

One thing that immediately caught my attention it appears CPUFreq is still WIP ?

Most likely this a .config kernel thingie, which simply needs to be enabled or more work to do ?

 


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

Welcome to Armbian Buster with Linux 5.4.0-rc8-sunxi64

System load:   1.44 0.56 0.22   Up time:       4 min
Memory usage:  12 % of 989MB    IP:            192.168.10.121
CPU temp:      45°C
Usage of /:    11% of 7.1G

Last login: Wed Nov 27 02:34:54 2019 from 192.168.10.98

root@orangepioneplus:~# cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
  no or unknown cpufreq driver is active on this CPU
  maximum transition latency: 4294.55 ms.
analyzing CPU 1:
  no or unknown cpufreq driver is active on this CPU
  maximum transition latency: 4294.55 ms.
analyzing CPU 2:
  no or unknown cpufreq driver is active on this CPU
  maximum transition latency: 4294.55 ms.
analyzing CPU 3:
  no or unknown cpufreq driver is active on this CPU
  maximum transition latency: 4294.55 ms.

 

Linux 5.4 now uses a different cpufreq driver for H6. I guess it needs to be enabled in Armbian's Linux defconfig.

Link to post
Share on other sites
14 hours ago, megi said:

Linux 5.4 now uses a different cpufreq driver for H6. I guess it needs to be enabled in Armbian's Linux defconfig.

ta! , uhm right, I just quickly kicked off another build with " KERNEL_CONFIGURE=yes " and except many new features not configured yet I found these disabled:

 

"PSCI CPU idle Driver (ARM_PSCI_CPUIDLE) [N/y/?] (NEW)" ,

"Allwinner nvmem based SUN50I CPUFreq driver (ARM_ALLWINNER_SUN50I_CPUFREQ_NVMEM) [N/m/y/?] (NEW) ",

Optional and out of this scope, but nice have "exFAT fs support (EXFAT_FS) [N/m/y/?] (NEW) ",

 

Set the last two to enabled [Y] and will compile it, once back home I can flash and see what happened ...

Thus basically when new default ".config' is ready for commit, let's not forget to include these please ( and many others I missed out at quick glance ) .

 

thanks

 

 

UPDATE1:  1,5GHz currently max? [ driver: cpufreq-dt ]

<snip snip>
analyzing CPU 3:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 0 1 2 3
  CPUs which need to have their frequency coordinated by software: 0 1 2 3
  maximum transition latency: 244 us.
  hardware limits: 480 MHz - 1.49 GHz
  available frequency steps: 480 MHz, 720 MHz, 816 MHz, 888 MHz, 1.08 GHz, 1.32 GHz, 1.49 GHz
  available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil
  current policy: frequency should be within 480 MHz and 1.49 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 480 MHz (asserted by call to hardware).
  cpufreq stats: 480 MHz:67.14%, 720 MHz:1.34%, 816 MHz:0.01%, 888 MHz:0.05%, 1.08 GHz:0.15%, 1.32 GHz:0.08%, 1.49 GHz:31.23%  (84)

 

UPDATE2: 

Checked /etc/default/cpufrequtils which shows ( as expected MAX_SPEED=1810000 ):

ENABLE=true
MIN_SPEED=480000
MAX_SPEED=1810000
GOVERNOR=ondemand

 

But is it required to enable a flag to " /boot/armbianEnv.txt  "in order to get 1.81Ghz back? 

I do recall, with NEO2 v1.1 board, in past something similar happened and it was needed to add the option " overlays " which is in this version currently missing:

root@orangepioneplus:~# cat /boot/armbianEnv.txt
verbosity=1
console=both
overlay_prefix=sun50i-h6
rootdev=UUID=d1e21321-c4f1-407b-9903-d825f76d9e25
rootfstype=ext4
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

 

Files listed in overlays rgd H6 ( for NEO2 the option is "sun50i-h5-cpu-clock-1.3GHz-1.3v.dtbo" ):

root@orangepioneplus:/boot/dtb/allwinner/overlay# ls -la *h6*
-rw-r--r-- 1 root root 4161 Nov 27 16:06 sun50i-h6-fixup.scr
-rw-r--r-- 1 root root  374 Nov 27 16:06 sun50i-h6-i2c0.dtbo
-rw-r--r-- 1 root root  374 Nov 27 16:06 sun50i-h6-i2c1.dtbo
-rw-r--r-- 1 root root  374 Nov 27 16:06 sun50i-h6-i2c2.dtbo
-rw-r--r-- 1 root root  268 Nov 27 16:06 sun50i-h6-ruart.dtbo
-rw-r--r-- 1 root root 1177 Nov 27 16:06 sun50i-h6-spi-add-cs1.dtbo
-rw-r--r-- 1 root root  804 Nov 27 16:06 sun50i-h6-spi-jedec-nor.dtbo
-rw-r--r-- 1 root root  645 Nov 27 16:06 sun50i-h6-spi-spidev1.dtbo
-rw-r--r-- 1 root root  780 Nov 27 16:06 sun50i-h6-spi-spidev.dtbo
-rw-r--r-- 1 root root  502 Nov 27 16:06 sun50i-h6-uart1.dtbo
-rw-r--r-- 1 root root  790 Nov 27 16:06 sun50i-h6-uart2.dtbo
-rw-r--r-- 1 root root  790 Nov 27 16:06 sun50i-h6-uart3.dtbo
-rw-r--r-- 1 root root  773 Nov 27 16:06 sun50i-h6-w1-gpio.dtbo

 

 

Link to post
Share on other sites

BTW, issue faced earlier with ramdom MAC on 8189fs has been narrowed : I'm using "old school" /etc/network/interface, but it is the NetworkManager that was assigning a random MAC, although it wasn't supposed to touch "wlan0" at all, so the fix is to disable it using "systemctl disable NetworkManager". My OPiPC+s, OPiLite and OPiPlus2E are back to their normal state ...

 

Link to post
Share on other sites
On 11/27/2019 at 1:25 PM, dolphs said:

UPDATE1:  1,5GHz currently max? [ driver: cpufreq-dt ]

 

Actually it is interesting finding these under " CPU Frequency scaling " kernel config options

 <M>   Generic DT based cpufreq driver
 <M>   Allwinner nvmem based SUN50I CPUFreq driver

 

This last option should " add the nvmem based CPUFreq driver for Allwinner dule capable h6 SoC. ", thus also for the orangepioneplus imho

Wonder if this is a driver issue in current kernel and if this has been fixed meanwhile in 5.4.2 ?

 

The first driver gives result as indicated 27 Nov already, the  " sun50i-cpufreq-nvmem " fails on this board so far....

Link to post
Share on other sites

Still exploring kernel 5.4,  

little bit out of scope as I am tuning the orangepioneplus board to my needs ( .config )

and no need for WiFi or Bluetooth

 

Thus  how to disable following wifi drivers that are added to the kernel ( as well wireguard ),

 

[ o.k. ] Adding [ WireGuard tag:0.0.20190702  ]
[ o.k. ] Checking git sources [ wireguard 0.0.20190702 ]
[ .... ] Up to date
[ o.k. ] Patching WireGuard [ Applying workaround for headers compilation ]
[ o.k. ] Adding [ Wireless drivers for Realtek 8811, 8812, 8814 and 8821 chipsets branch:v5.2.20 ]
[ o.k. ] Checking git sources [ rtl8812au v5.2.20 ]
[ .... ] Up to date
[ o.k. ] Adding [ Wireless drivers for Realtek 8188EU 8188EUS and 8188ETV chipsets branch:v5.3.9 ]
[ o.k. ] Checking git sources [ rtl8188eu v5.3.9 ]
[ .... ] Up to date
[ o.k. ] Adding [ Wireless drivers for Realtek 88x2bu chipsets branch:master ]
[ o.k. ] Checking git sources [ rtl88x2bu master ]


Did read it somewhere but I forgot, one to guide me please? At least it is not here unless I am overlooking stuff

TiA!

Link to post
Share on other sites

This just adds the source code needed to compile the modules. If you remove/disable them from your kernel config they won't be built. Though I do not think this is even necessary as they should be built as modules already and if you do not load them they would not eat up any ressources whatsoever besides a tiny bit of space on your sd card.

If they get forcefully loaded on boot for unknown reason blacklist the appropriate modules.

Link to post
Share on other sites
On 12/5/2019 at 7:57 AM, dolphs said:

 

Actually it is interesting finding these under " CPU Frequency scaling " kernel config options

 <>   Generic DT based cpufreq driver
 <*>   Allwinner nvmem based SUN50I CPUFreq driver

 

This last option should " add the nvmem based CPUFreq driver for Allwinner dule capable h6 SoC. ", thus also for the orangepioneplus imho

Wonder if this is a driver issue in current kernel and if this has been fixed meanwhile in 5.4.2 ?

 

The first driver gives result as indicated 27 Nov already, the  " sun50i-cpufreq-nvmem " fails on this board so far....

 

noticed current dev build ( default kernel ) takes still 5.4.2, would like to try 5.4.3  to see if the this generic driver takes clock speedback to 1,8GHz ( currently 1.5 ) on the orangepioneplus.

Not sure if the newer driver ( Alwinner CPUFreq ) is working now, but in 5.4.3 kernel updates has been made to the Generic driver as far I read the ChangeLogs.

imho AR-86 is not closed yet, it works with a workaround unless it has been confirmed the Generic driver is the one to use ( though it should be the SUN50I CPUFreq driver imho? )

Link to post
Share on other sites
1 hour ago, Igor said:

I got 1.8 Ghz on my Opi3. Perhaps there is a problem with other boards, haven't test them ...

 

in which I can contribute to test, as I owe the "orangepioneplus"  ( pihole and ovpn server ) as well a spare, so excellent for testing purposes

Yet as we unfortunately can see it is not showing 1,8 which I reported also 5 December:

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

Welcome to Armbian buster with Linux 5.4.2-sunxi64

System load:   0.27 0.24 0.10   Up time:       2 min
Memory usage:  7 % of 989MB     IP:            192.168.10.121
CPU temp:      45°C
Usage of /:    4% of 15G


root@orangepioneplus:~# cpufreq-info |grep cpufreq
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
  driver: cpufreq-dt
  available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil
  cpufreq stats: 480 MHz:91.69%, 720 MHz:0.53%, 816 MHz:0.02%, 888 MHz:0.25%, 1.08 GHz:0.28%, 1.32 GHz:0.48%, 1.49 GHz:6.74%  (147)
  driver: cpufreq-dt
  available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil
  cpufreq stats: 480 MHz:91.69%, 720 MHz:0.53%, 816 MHz:0.02%, 888 MHz:0.25%, 1.08 GHz:0.28%, 1.32 GHz:0.48%, 1.49 GHz:6.74%  (147)
  driver: cpufreq-dt
  available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil
  cpufreq stats: 480 MHz:91.69%, 720 MHz:0.53%, 816 MHz:0.02%, 888 MHz:0.25%, 1.08 GHz:0.28%, 1.32 GHz:0.48%, 1.49 GHz:6.74%  (147)
  driver: cpufreq-dt
  available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil
  cpufreq stats: 480 MHz:91.69%, 720 MHz:0.53%, 816 MHz:0.02%, 888 MHz:0.25%, 1.08 GHz:0.28%, 1.32 GHz:0.48%, 1.49 GHz:6.74%  (147)

 

Will give it another shot once @megi has 5.4.3 incorporated in orangepi-5.4 branch,

both default and with the " Allwinner nvmem based SUN50I CPUFreq " driver

 

Link to post
Share on other sites
7 minutes ago, dolphs said:

which I reported also 5 December:


Thank you for report. Development needs time and this problem is far far from critical.

 

8 minutes ago, dolphs said:

has 5.4.3 incorporated in orangepi-5.4 branch


We use the same branch. Just lots of patches which could also break something ... some work has to be applied.

Link to post
Share on other sites
15 minutes ago, Igor said:

Thank you for report. Development needs time and this problem is far far from critical.

 

agreed, was just following the Jira stories and noticed AR-86 is not fully solved, just wanted to report back and that is it. 

So I do not want to put any rush on this,  but at least we know now it is not fully solved yet. 

As said once I see either branch or kernel being updated will spin up another test drive.  cheers for your efforts as you know it is appreciated!

Link to post
Share on other sites
1 hour ago, dolphs said:

Will give it another shot once @megi has 5.4.3 incorporated in orangepi-5.4 branch,

both default and with the " Allwinner nvmem based SUN50I CPUFreq " driver

 

I don't think waiting will help. I almost never update non-rc branches after release, I only merge from linux-stable.

Anyway, I can only see you're missing 1.8GHz, because Armbian changes my CPU OPP table to something else, because my OPP table has 1.8GHz operating point.

https://megous.com/git/linux/commit/?h=ths-5.4&id=8bad58044be498d409400dbf9757f2ae25c6ad9d

 

Link to post
Share on other sites

I tried version 5.4(.20) - Ubuntu/Bionic (downloaded from https://www.armbian.com/nanopi-duo-2/ )

Since this topic is about creating 5.4 version for a processor series that I use, I think my posting here is correct. 

I have the Allwinner H3 (SUN8I 1680) processor on a NanoPi Duo2 board.

 

The startup of Bionic hangs at a certain point, always the same point. Here the complete log (in a spoiler block so not everyone has to see this/scroll over it)

 

Spoiler

U-Boot SPL 2019.10-armbian (Feb 17 2020 - 06:26:18 +0100)
DRAM: 512 MiB
Trying to boot from MMC1


U-Boot 2019.10-armbian (Feb 17 2020 - 06:26:18 +0100) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: FriendlyARM NanoPi DUO 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
Net:   No ethernet 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
3789 bytes read in 4 ms (924.8 KiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
190 bytes read in 2 ms (92.8 KiB/s)
8677345 bytes read in 650 ms (12.7 MiB/s)
7744344 bytes read in 580 ms (12.7 MiB/s)
Found mainline kernel configuration
28951 bytes read in 8 ms (3.5 MiB/s)
504 bytes read in 9 ms (54.7 KiB/s)
Applying kernel provided DT overlay sun8i-h3-usbhost0.dtbo
504 bytes read in 10 ms (48.8 KiB/s)
Applying kernel provided DT overlay sun8i-h3-usbhost2.dtbo
504 bytes read in 9 ms (54.7 KiB/s)
Applying kernel provided DT overlay sun8i-h3-usbhost3.dtbo
4155 bytes read in 10 ms (405.3 KiB/s)
Applying kernel provided DT fixup script (sun8i-h3-fixup.scr)

## Executing script at 44000000
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    8677281 Bytes = 8.3 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 43000000
   Booting using the fdt blob at 0x43000000
   Loading Ramdisk to 497b9000, end 49fff7a1 ... OK
   Loading Device Tree to 49749000, end 497b8fff ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Loading, please wait...
starting version 237
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.31.1
[/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1
/dev/mmcblk0p1: clean, 35020/59904 files, 202121/239616 blocks
done.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.

Welcome to Ubuntu 18.04.4 LTS!

[  OK  ] Reached target Swap.
[  OK  ] Started Forward Password Requests to Wall Directory Watch.
[  OK  ] Reached target System Time Synchronized.
[  OK  ] Started Dispatch Password Requests to Console Directory Watch.
[  OK  ] Set up automount Arbitrary Executab…rmats File System Automount Point.
[  OK  ] Reached target Remote File Systems.
[  OK  ] Reached target Local Encrypted Volumes.
[  OK  ] Created slice System Slice.
[  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
[  OK  ] Listening on udev Control Socket.
[  OK  ] Listening on Journal Socket (/dev/log).
[  OK  ] Listening on udev Kernel Socket.
[  OK  ] Listening on fsck to fsckd communication Socket.
[  OK  ] Created slice system-serial\x2dgetty.slice.
[  OK  ] Listening on Journal Socket.
         Starting Nameserver information manager...
         Mounting POSIX Message Queue File System...

         Starting udev Coldplug all Devices...
         Starting Load Kernel Modules...
         Starting Restore / save the current clock...
         Starting Create list of required st…ce nodes for the current kernel...
         Mounting Kernel Debug File System...
[  OK  ] Listening on Journal Audit Socket.
         Starting Set the console keyboard layout...
[  OK  ] Listening on Syslog Socket.
         Starting Journal Service...
         Starting Remount Root and Kernel File Systems...
[  OK  ] Created slice User and Session Slice.
[  OK  ] Reached target Slices.
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Started Load Kernel Modules.
[  OK  ] Started Restore / save the current clock.
[  OK  ] Started Create list of required sta…vice nodes for the current kernel.
[  OK  ] Mounted Kernel Debug File System.
[  OK  ] Started Remount Root and Kernel File Systems.
[  OK  ] Started Nameserver information manager.
[  OK  ] Reached target Network (Pre).
         Starting Load/Save Random Seed...
         Starting Create Static Device Nodes in /dev...
         Starting Apply Kernel Variables...
         Mounting Kernel Configuration File System...
[  OK  ] Mounted Kernel Configuration File System.
[  OK  ] Started Load/Save Random Seed.
[  OK  ] Started Journal Service.
[  OK  ] Started Create Static Device Nodes in /dev.
[  OK  ] Started Apply Kernel Variables.
         Starting udev Kernel Device Manager...
         Starting Flush Journal to Persistent Storage...
[  OK  ] Started udev Coldplug all Devices.
[  OK  ] Started Flush Journal to Persistent Storage.
[  OK  ] Started udev Kernel Device Manager.
[  OK  ] Found device /dev/ttyGS0.
[  OK  ] Started Set the console keyboard layout.
[  OK  ] Reached target Local File Systems (Pre).
         Mounting /tmp...
[  OK  ] Mounted /tmp.
[  OK  ] Reached target Local File Systems.
         Starting Armbian ZRAM config...
         Starting Raise network interfaces...
         Starting Create Volatile Files and Directories...
         Starting Set console font and keymap...
[  OK  ] Started Set console font and keymap.
[  OK  ] Started Create Volatile Files and Directories.
[  OK  ] Started Entropy daemon using the HAVEGE algorithm.
         Starting Update UTMP about System Boot/Shutdown...
         Starting Network Name Resolution...
[    9.455761] lima 1c40000.gpu: IRQ ppmmu2 not found

[    9.460719] lima 1c40000.gpu: IRQ ppmmu3 not found
[    9.465727] lima 1c40000.gpu: IRQ pp2 not found
[    9.470351] lima 1c40000.gpu: IRQ pp3 not found
[  OK  ] Found device /dev/ttyS0.
[  OK  ] Started Update UTMP about System Boot/Shutdown.
[  OK  ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
[  OK  ] Started Network Name Resolution.
[  OK  ] Reached target Host and Network Name Lookups.
         Starting Load/Save RF Kill Switch Status...
[  OK  ] Started Load/Save RF Kill Switch Status.
[  OK  ] Started Raise network interfaces.
[  OK  ] Started Armbian ZRAM config.
         Starting Armbian memory supported logging...
[  OK  ] Started Armbian memory supported logging.
[  OK  ] Reached target System Initialization.
[  OK  ] Started Daily Cleanup of Temporary Directories.
[  OK  ] Started Discard unused blocks once a week.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Reached target Sockets.
[  OK  ] Started Daily apt download activities.
[  OK  ] Started Daily apt upgrade and clean activities.
         Starting Armbian filesystem resize...
[  OK  ] Started resolvconf-pull-resolved.path.
[  OK  ] Reached target Paths.
[  OK  ] Started Message of the Day.
[  OK  ] Reached target Timers.
         Starting Armbian hardware optimization...
         Starting Armbian hardware monitoring...
[  OK  ] Started Armbian hardware optimization.
[  OK  ] Started Armbian hardware monitoring.
[  OK  ] Started Armbian filesystem resize.
[  OK  ] Reached target Basic System.
         Starting Resets System Activity Data Collector...
[  OK  ] Started Regular background program processing daemon.
         Starting rng-tools.service...
         Starting Login Service...
[  OK  ] Started D-Bus System Message Bus.
         Starting Network Manager...
         Starting WPA supplicant...
         Starting resolvconf-pull-resolved.service...
         Starting Dispatcher daemon for systemd-networkd...
         Starting System Logging Service...
[  OK  ] Started Armbian first run tasks.
         Starting LSB: Load kernel modules needed to enable cpufreq scaling...
[  OK  ] Started Resets System Activity Data Collector.
[  OK  ] Started rng-tools.service.
[  OK  ] Started resolvconf-pull-resolved.service.
[  OK  ] Started Login Service.
[  OK  ] Started LSB: Load kernel modules needed to enable cpufreq scaling.
         Starting LSB: set CPUFreq kernel parameters...

[  OK  ] Started WPA supplicant.
[  OK  ] Started System Logging Service.
[  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.
         Starting Hostname Service...
[  OK  ] Started Hostname Service.
[  OK  ] Started Network Manager.
         Starting Network Manager Script Dispatcher Service...
         Starting Network Manager Wait Online...
[  OK  ] Reached target Network.
         Starting OpenBSD Secure Shell server...
         Starting chrony, an NTP client/server...
[  OK  ] Started Unattended Upgrades Shutdown.
         Starting Permit User Sessions...
[  OK  ] Started Network Manager Script Dispatcher Service.
[  OK  ] Started Permit User Sessions.
         Starting Set console scheme...
[  OK  ] Started Set console scheme.
[  OK  ] Created slice system-getty.slice.
[  OK  ] Started chrony, an NTP client/server.
[  OK  ] Started OpenBSD Secure Shell server.

[  OK  ] Started Dispatcher daemon for systemd-networkd.

 

I tried reflashing a couple of times to the SD card.

I tried a different image flasher tool (tried win32diskimager and etcher)

I tried 2 SD cards, both with same result.

 

Now the interesting bit: the Buster (Debian) variant of 5.4.20 DOES work corrrectly and boots up perfectly.

 

Is this interesting feedback for you?

Is there a solution for my Bionic/Ubuntu version? 

Can I give you more information you possibly need?

Link to post
Share on other sites
8 hours ago, Cheater said:

 the Buster (Debian) variant of 5.4.20 DOES work

 

 

Therefore your post has nothing to do with the kernel building :lol:

I'll suggest someone to split this topic up.

This may not even be related to Armbian since Armbians job is to put together a working kernel for various sbcs and build a operating system with minimal customization (Buster and Bionic to say) on top. The kernel boots fine as seen above so this might be OS related and therefore an issue that Ubuntu have to fix themselves.

Link to post
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...