Skip to content
View in the app

A better way to browse. Learn more.
Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Next LTS kernel 4.19.y Allwinner A10, A20, A64, H2+, H3, H5, H6 debugging party

Igor
in Advanced users - Development

Featured Replies

  • Author
1 hour ago, martinayotte said:

Where is that settings ? It wasn't like that in 4.18.12 ... Personally, I prefer keeping serial since all my boards are headless.


I fixed reality for "both" in boot script. https://github.com/armbian/build/commit/352b2584d2b168ce8701a4ece7acef5036602e3b#diff-0d8dfe4e3afafd7267b256b263a97d6f This means you have boot console to HDMI and serial console (login) is up. Previous both was nothing on the screen until login prompt. That means in some cases "no sign of life" for several minutes at first login. The only conclusion is that Armbian doesn't work.

You can add DEFAULT_CONSOLE="serial"  when building.
 

1 hour ago, martinayotte said:

But in many of my post, I've encouraging Joe to get USB-TTL Serial dongle in their toolbox ...


If we don't find a better way, defaulting to serial on boards without HDMI is an option https://github.com/armbian/build/blob/master/config/boards/orangepizero.conf#L10

  • Author
19 hours ago, lomady said:

I did fresh reinstalls two times: updating these packages after switching to nightly builds and after switching to dev branch. That made no difference, as soon as I power cycle the dev kernel it freezes at boot regardless of the versions of these packages.


Mine hanged with current stock settings already at first boot ... then I tried orangepipc2 DT and ... it looks fine. I notice DT is missing regulator bits and after adding them ... at least that problem is gone. I did several reboots and cold starts. At one cold start it hanged ... Not sure if everything is fine yet.

 

Possible related issue is wrong temperature. It's possible that protection kicks in? When idle it already shows 50° (33 shows my IR meter) and last time when I did stressing it reached critical temp of 92° which triggered controlled power off. This should not happen this soon. 

    • 1
    On 11/17/2018 at 11:55 PM, rusatch said:

    Thank you. I will switch kernel to dev and test it.

    Works perfectly, thanks. 

    Which overlay of this still actual?

    overlays=usbhost2 usbhost3 analog-codec w1-gpio gpio-regulator-1.3v cpu-clock-1.3GHz i2c0 i2c1 pps-gpio
     

    9 hours ago, rusatch said:

    Works perfectly, thanks. 

    Which overlay of this still actual?

    overlays=usbhost2 usbhost3 analog-codec w1-gpio gpio-regulator-1.3v cpu-clock-1.3GHz i2c0 i2c1 pps-gpio

     

    When the latest tree is built and released and you switch to it, then you should change "cpu-clock-1.3GHz" to "cpu-clock-1.3GHz-1.3v".  You can check for this in "/boot/dtb/allwinner/overlay/".

    On 11/15/2018 at 8:05 PM, Igor said:
    • ( @hojnikb available frequency steps: 120 MHz, 240 MHz, 480 MHz, 648 MHz, 816 MHz, 960 MHz, 1.01 GHz, 1.06 GHz, 1.10 GHz, 1.15 GHz, 1.20 GHz, 1.22 GHz, 1.25 GHz, 1.30 GHz, 1.34 GHz, 1.37 GHz)

    •  

     

    This is great news, ill give it a test to see how set voltages perform on real hardware. 

    On 11/15/2018 at 8:05 PM, Igor said:

    Earlier today I pushed a fairy large patchset containing various functional improvements of many boards.  If you have Allwinner board and some spare time:

     

    1. Build DEV image/kernel with https://github.com/armbian/build (you need to add EXPERT="yes" to the config to unlock)

    2. Install DEV kernel from beta repository

     

    1. Optional Defreeze kernel updates
    2. Switch to nightly kernel (armbian-config -> system -> Nightly)
    3. Reboot
    4. Switch to other kernel (armbian-config -> system -> Other -> DEV)

     

    As an Armbian newbie and in the hope for improvement on WIFI for Olimex Teres-1 i tried to test the update on my system. I just went for the steps 1..3 (using armbian-config). I was not able to see any option in menu to execute Step 4.

    However, i can see the running kernel version as 4.19.2-sunxi64. Did i get that patch installed also without Build DEV image/kernel, Install DEV kernel?

     

    WIFI from SoC still does not work after switching to nightly. Then i also inserted a proven USB WIFI dongle and this one also does not get a connection. Therefore to me it seems that the problem may be beyond the specific driver for on-board WIFI. Any remarks on this aspect?

     

    Thanks

    • Author
    8 hours ago, binutzu said:

    As an Armbian newbie and in the hope for improvement on WIFI for Olimex Teres-1 i tried to test the update on my system.


    I was playing yesterday with Teres 1 and at least wifi worked ... try hard reboot and without having anything attached to the USB. If you can, build a complete new image. Wait for new patches - i have to push them up.

    Have been testing on a pineh64.  kernel and uboot seem to be fine,  but something is wrong with the device tree--  The original armbian build (the 4.18 rc7-(-from icenowy, I believe--booted),  but no updates after that worked.  I recompiled her tree  from her 86-integrate-2-ugly branch and am booting fine (both from sd and eemc)  I originally noticed a complaint  about the simplefb node not being found,  but after adding that node, I still got the same kernel oops.  Before that oops,  the boot logs look  the same....  

     

    I'm hoping someone can see what is wrong.  I'm afraid I'm really out of my element here.

     

     

     

     

     

    console_pine64h6.txt

    Orange Pi Zero Plus

     

    Linux orangepizeroplus 4.19.2-sunxi64 #8 SMP Sun Nov 18 23:44:37 CET 2018 aarch64 aarch64 aarch64 GNU/Linux

    BOOT=yes

    VERSION=5.67.181118

    KERNEL=4.19.2-sunxi64

    NETWORK=yes

    WIRELESS=yes

    HDMI=NA

    USB=yes

    DVFS=???yes

    ARMBIANMONITOR=http://ix.io/1u5E

     

    Other bugs:

    - USB serial doesn't work

    - Kernel boot console is missing

     

    Quote

    U-Boot 2018.05-armbian (Nov 19 2018 - 00:18:30 +0100) Allwinner Technology

    CPU:   Allwinner H5 (SUN50I)
    Model: Xunlong Orange Pi Zero Plus
    DRAM:  512 MiB
    MMC:   SUNXI SD/MMC: 0, SUNXI SD/MMC: 1
    Loading Environment from EXT4... ** File not found /boot/boot.env **

    ** Unable to read "/boot/boot.env" from mmc0:1 **
    Failed (-5)
    In:    serial
    Out:   serial
    Err:   serial
    Net:   No ethernet found.
    230454 bytes read in 37 ms (5.9 MiB/s)
    starting USB...
    USB0:   USB EHCI 1.00
    USB1:   USB OHCI 1.0
    scanning bus 0 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 27 ms (109.4 KiB/s)
    ## Executing script at 4fc00000
    U-boot loaded from SD
    Boot script loaded from mmc
    192 bytes read in 21 ms (8.8 KiB/s)
    28549 bytes read in 46 ms (605.5 KiB/s)
    504 bytes read in 56 ms (8.8 KiB/s)
    Applying kernel provided DT overlay sun50i-h5-usbhost2.dtbo
    504 bytes read in 57 ms (7.8 KiB/s)
    Applying kernel provided DT overlay sun50i-h5-usbhost3.dtbo
    4155 bytes read in 45 ms (89.8 KiB/s)
    Applying kernel provided DT fixup script (sun50i-h5-fixup.scr)
    ## Executing script at 44000000
    8652572 bytes read in 761 ms (10.8 MiB/s)
    14243848 bytes read in 1226 ms (11.1 MiB/s)
    ## Loading init Ramdisk from Legacy Image at 4fe00000 ...
       Image Name:   uInitrd
       Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
       Data Size:    8652508 Bytes = 8.3 MiB
       Load Address: 00000000
       Entry Point:  00000000
       Verifying Checksum ... OK
    ## Flattened Device Tree blob at 4fa00000
       Booting using the fdt blob at 0x4fa00000
       Loading Ramdisk to 497bf000, end 49fff6dc ... OK
       reserving fdt memory region: addr=4fa00000 size=6d000
       Loading Device Tree to 000000004974f000, end 00000000497befff ... OK

    Starting kernel ...


    Ubuntu 18.04.1 LTS orangepizeroplus ttyS0

    orangepizeroplus login:
     

    9

     

    40 minutes ago, Igor said:

    Those boards still need to be tested - some of them I don't have:
     

    Nanopi Neo Core 2 LTS
    Orange Pi R1
    Pinebook A64 (know to break booting atm)
    Sopine A64
    Olimex Lime 2 eMMC
    Nanopi Neo Air
    Pine64

    Do they all get an 4.19 dev kernel with the build-system?

    I own a OPi R1....

    While trying to test the Core2 I cant switch with "other" the kernel, but I dud already use Dev (I think) because I did build dev with the build system...

    12 hours ago, Igor said:


    Yes, if DEV is enabled. Armbian-config way not goes for all of them.

    can you describe the "other" way in detail? 

    so I can make my report
    https://github.com/armbian/testings/blob/master/nanopineocore2-dev.report

    ( nanopineocore2-dev: 5.67 First report (#115)5 days ago )

    useful for your testing?

    DEV is enabled via EXPERT="yes" ?

     

    I'll now compile DEV for the R1....

    8 hours ago, Igor said:

    Still  needed testings:

    Orange Pi R1

     

    Quick note - I just built dev for R1 and it works well - did a cursory test of 4.19.2-sunxi and wireless, USB, DVFS/cpufreq, etc. and everything works.  It does have the following warnings (as you noted previously), but the core speeds seem to work fine up to 1.3v/1.01GHz: 

    [    8.116042] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator
[    8.116069] cpu cpu0: _opp_add: OPP not supported by regulators (1056000000)
[    8.116263] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator
[    8.116280] cpu cpu0: _opp_add: OPP not supported by regulators (1104000000)
[    8.116512] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator
[    8.116527] cpu cpu0: _opp_add: OPP not supported by regulators (1152000000)
[    8.116725] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator
[    8.116737] cpu cpu0: _opp_add: OPP not supported by regulators (1200000000)
[    8.116903] core: _opp_supported_by_regulators: OPP minuV: 1340000 maxuV: 1340000, not supported by regulator
[    8.116922] cpu cpu0: _opp_add: OPP not supported by regulators (1224000000)
[    8.117152] core: _opp_supported_by_regulators: OPP minuV: 1340000 maxuV: 1340000, not supported by regulator
[    8.117170] cpu cpu0: _opp_add: OPP not supported by regulators (1248000000)
[    8.117376] core: _opp_supported_by_regulators: OPP minuV: 1340000 maxuV: 1340000, not supported by regulator
[    8.117392] cpu cpu0: _opp_add: OPP not supported by regulators (1296000000)
[    8.117557] core: _opp_supported_by_regulators: OPP minuV: 1400000 maxuV: 1400000, not supported by regulator
[    8.117572] cpu cpu0: _opp_add: OPP not supported by regulators (1344000000)
[    8.117755] core: _opp_supported_by_regulators: OPP minuV: 1400000 maxuV: 1400000, not supported by regulator
[    8.117769] cpu cpu0: _opp_add: OPP not supported by regulators (1368000000)

     

    I'm building an image for pine64 tonight and will test tomorrow. Will report back ASAP.

    54 minutes ago, 5kft said:

     

    Quick note - I just built dev for R1 and it works well - did a cursory test of 4.19.2-sunxi and wireless, USB, DVFS/cpufreq, etc. and everything works. 

    I did also compile for the OPi R1 - I could also successfully test the USB via the OPi NAS AddOn.

    A report has been created (dont know if @5kft did this also)

    I do have some lacking at the SSH-connection via eth0 :( like on a "bad" WiFi-Connection because of:
      

    [ 1439.605021] ==> rtl8188e_iol_efuse_patch
[ 1501.258078] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[ 1523.785870] dwmac-sun8i 1c30000.ethernet eth0: Link is Down
[ 1524.810021] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[ 1528.905843] dwmac-sun8i 1c30000.ethernet eth0: Link is Down
[ 1529.930016] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[ 1538.121820] dwmac-sun8i 1c30000.ethernet eth0: Link is Down
[ 1539.146029] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[ 1628.389288] ==> rtl8188e_iol_efuse_patch
[ 1691.429555] ==> rtl8188e_iol_efuse_patch
[ 1754.554618] ==> rtl8188e_iol_efuse_patch

    the second ethernet-port enxc0742bffxxxx didnt seem to have this lacking ;)

    •
    1
    7 minutes ago, Igor said:

     @guidol tnx.  I am getting close to Pinebook(s) problems.

    which Pinebook problems?
    I did see that the report for the Pinebook is out of date, but there was no newer kernel as the latest report on your page.

    For testing other Pinebook things - I only have a "old" Pinebook - the non-1080-one at 14"

    Pine64+ is booting fine, Ethernet (wired isfine),  still working investigating getting wireless (r8723bs) to work.   Not sure about HDMI yet.

    17 hours ago, vlad59 said:

    I'm building an image for pine64 tonight and will test tomorrow. Will report back ASAP.

     

    So I can confirm, a DEV image boots fine on my Pine64 (1G if that's important). I'll send a complete report later today. For now I can confirm that wired network is fine (Gigabit), Wifi network seems to work (scan is working but not tried to join one for now), Bluetooth don't work (nothing detected).

     

    I'll test HDMI before sending the report. To confirm I tested the right image ;):

      

    root@pine64:~# uname -a
Linux pine64 4.19.2-sunxi64 #1 SMP Thu Nov 22 17:00:08 CET 2018 aarch64 aarch64 aarch64 GNU/Linux

     

    Guest
    This topic is now closed to further replies.
    Go to topic listing

    Account

    Navigation

    Search

    Search

    Configure browser push notifications
    Chrome (Android)
    1. Tap the lock icon next to the address bar.
    2. Tap Permissions → Notifications.
    3. Adjust your preference.
    Chrome (Desktop)
    1. Click the padlock icon in the address bar.
    2. Select Site settings.
    3. Find Notifications and adjust your preference.