Jump to content

Seb_Lz

Members
 View Profile  See their activity

  • Posts

    7

  • Joined

  • Last visited

 Content Type 

Posts posted by Seb_Lz

    Single Armbian image for RK + AML + AW (aarch64 ARMv8)

    in General Chat

    Posted

    On 4/23/2020 at 5:55 AM, Juanjo said:

     

    See 

     

     

    Lastest images from Balbes broke some PHYs. I noted the problem is with a patch that it is used on newer Kernels and how the some PHY parameters are parsed from DTBs

     

    https://patchwork.kernel.org/patch/10985167/

     

    So I reverted those changed on DTB and it worked. Please try attached DTB

     

     

     

     

    meson-gxm-q200.dtb 28.29 kB · 2 downloads

    Thanks a lot @Juanjo ! Your dtb has indeed fixed eth0 interface on my Beelik GT1 (armbian bionic version 5.6.0-rc7-arm-64).

    0

    Single Armbian image for RK + AML + AW (aarch64 ARMv8)

    in General Chat

    Posted

    3 hours ago, stefanog said:

    i have last armbian image in my beelink gt1..... 

    I installed docker.... and after home assistant.. but installation failed !?

    No one had any problems?

     

     

     

     

    3 hours ago, Igor said:

     

    None with official Armbian https://www.armbian.com/download/ but TV boxes software support is not on that level.

     

    I have it installed on my Beelik GT1 following stricly those steps (and using qemuarm-64 for the superviser install):

    https://www.home-assistant.io/hassio/installation/#alternative-install-home-assistant-supervised-on-a-generic-linux-host
     

    Do you guys have a working ethernet connection with your GT1  (I tried khadas-vim2, q200, q201 and many other .dtb but I can only get wifi working, not eth0) ?

    0

    Single Armbian image for RK + AML + AW (aarch64 ARMv8)

    in General Chat

    Posted

    On 4/8/2020 at 5:19 PM, Seb_Lz said:

     

    Small update on my research to make the image work with Beelink GT1:
    After trying a few things, I eventually decided to start again from scratch with Armbian_20.05.1_Arm-64_bionic_current_5.6.0-rc7_20200404.img.xz. After installing, same problem on clean install. I then tried to go back to 20200331 version, which was previously working. To my surprise, and despite using the exact same image (clean format using balenaEtcher), it was also not working anymore ! I thought about an hardware problem, but rebooting on android emmc system prove me wrong as ethernet was there working fine. I then flashed back the SD to 20200404 and used Q201 dtb file. The eth0 interface is recognized but there are still errors in kern.log and the interface is still faulty (can't get an IP from DHCP nor connect to it when set statically): 

    
root@hassio:~# dmesg -T --level=err,warn
[Wed Apr  8 17:02:39 2020] KASLR disabled due to lack of seed
[Wed Apr  8 17:02:41 2020] OCFS2 User DLM kernel interface loaded
[Wed Apr  8 17:02:42 2020] meson8b-dwmac c9410000.ethernet: IRQ eth_wake_irq not found
[Wed Apr  8 17:02:42 2020] meson8b-dwmac c9410000.ethernet: IRQ eth_lpi not found
[Wed Apr  8 17:02:42 2020] meson8b-dwmac c9410000.ethernet: PTP uses main clock
[Wed Apr  8 17:02:42 2020] dwc3 c9000000.dwc3: Failed to get clk 'ref': -2
[Wed Apr  8 17:02:43 2020] phy phy-d0078080.phy.3: unsupported PHY mode 5
[Wed Apr  8 17:02:43 2020] hub 2-0:1.0: config failed, hub doesn't have any ports! (err -19)
[Wed Apr  8 17:02:43 2020] mmc2: queuing unknown CIS tuple 0x80 (2 bytes)
[Wed Apr  8 17:02:43 2020] mmc2: queuing unknown CIS tuple 0x80 (3 bytes)
[Wed Apr  8 17:02:43 2020] mmc2: queuing unknown CIS tuple 0x80 (3 bytes)
[Wed Apr  8 17:02:43 2020] mmc2: queuing unknown CIS tuple 0x80 (7 bytes)
[Wed Apr  8 17:02:47 2020] gx-sound-card sound: ASoC: no DMI vendor name!
[Wed Apr  8 17:02:47 2020] panfrost d00c0000.gpu: d00c0000.gpu supply mali not found, using dummy regulator
[Wed Apr  8 17:02:47 2020] panfrost d00c0000.gpu: GPU Fault 0x00000088 (UNKNOWN) at 0x000000fcffbfffc0
[Wed Apr  8 17:02:48 2020] meson_vdec: module is from the staging directory, the quality is unknown, you have been warned.
[Wed Apr  8 17:02:48 2020] hci_uart_bcm serial0-0: serial0-0 supply vbat not found, using dummy regulator
[Wed Apr  8 17:02:48 2020] hci_uart_bcm serial0-0: serial0-0 supply vddio not found, using dummy regulator
[Wed Apr  8 17:02:48 2020] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[Wed Apr  8 17:02:48 2020] brcmfmac mmc2:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.amlogic,q201.txt failed with error -2
[Wed Apr  8 17:02:48 2020] bluetooth hci1: Direct firmware load for brcm/BCM4345C0.hcd failed with error -2
[Wed Apr  8 17:02:49 2020] meson8b-dwmac c9410000.ethernet eth0: PTP not supported by HW
[Wed Apr  8 17:02:49 2020] ext4 filesystem being mounted at /var/log supports timestamps until 2038 (0x7fffffff)
[Wed Apr  8 17:02:50 2020] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[Wed Apr  8 17:02:50 2020] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04
[Wed Apr  8 17:03:09 2020] process 'docker/tmp/qemu-check033460557/check' started with executable stack
[Wed Apr  8 17:03:12 2020] overlayfs: NFS export requires "index=on", falling back to nfs_export=off.

    I've extracted the dtb file from the working Android system and from the 20200404 img and converted them to dts file. I tried to adapt some values in the ethernet@c9410000 {...} part to mimic what is in the android part, but this didn't help (in some cases, it created more errors). I'm really confused how as how to make progress on this, any kind of help would be very welcome :D (dts files in attachments).

     

    android-q201.dts 47.95 kB · 2 downloads meson-gxm-q201.dts 35.17 kB · 2 downloads

     

    As I was still searching for a solution to get eth0 working on beelink gt1, I've come across this:
    https://github.com/150balbes/Build-Armbian/blob/7fa5c7b89c7444a2d503f064296e0dda219cee20/patch/kernel/meson64-dev/0361-arm64-dts-meson-gxm-add-beelink-gt1.patch
    My understanding is that the dev branch includes a patch that will generate an additional .dtb file specifically for beelink gt1.

     

    Therefore, I tried tried to compile the image from source code. Although this works fine with the "current" branch, compilation fails with the dev branch. I naively tried to add the gt1 patch as a userpatch for the 'current' branch, but the integration of the patch would fail too during the creation process of the image.

     

    Here is the command I used to build dev image: 

    ./compile.sh  BOARD=arm-64 BRANCH=dev RELEASE=bionic BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no COMPRESS_OUTPUTIMAGE=gz

    and here is the error (full logs in attachment): 

    Displaying message: Creating packages
Displaying message: ERROR in function compile_kernel compilation.sh:431 err
Displaying message: Failed moving kernel DEBs  err
Displaying message: Process terminated  info

    Any idea why the dev branch won't build ?

    log.7z

    0

    Single Armbian image for RK + AML + AW (aarch64 ARMv8)

    in General Chat

    Posted

    On 4/7/2020 at 2:54 PM, Seb_Lz said:

     

    I have a similar issue, also with beelink GT1 2Gb ram (S912): with Armbian_20.05.0_Arm-64_bionic_current_5.6.0-rc6_20200331.img, eth0 and wlan0 eventually started to work using dtb q200 (was NOT the case with previous RC6 img, was previously running an old 4.20 kernel img) BUT today I had a small power failure and on reboot, I started to loose eth0 support again, with following error in kern.log: 

    
Apr  7 14:32:56 localhost kernel: [   11.076849] meson8b-dwmac c9410000.ethernet eth0: no phy at addr -1
Apr  7 14:32:56 localhost kernel: [   11.076859] meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)

     

    NB: directly after installing rc6_20200331, I did an apt update + apt upgrade and all went fine (I did not upgrade the kernel), so in my case the problem with eth0 does not seem to be related to upgrading some packages.

    Since this error started to appear just after a power failure, could this be linked to some corrupted file ? Any idea how I could restore  them ?

     

    Small update on my research to make the image work with Beelink GT1:
    After trying a few things, I eventually decided to start again from scratch with Armbian_20.05.1_Arm-64_bionic_current_5.6.0-rc7_20200404.img.xz. After installing, same problem on clean install. I then tried to go back to 20200331 version, which was previously working. To my surprise, and despite using the exact same image (clean format using balenaEtcher), it was also not working anymore ! I thought about an hardware problem, but rebooting on android emmc system prove me wrong as ethernet was there working fine. I then flashed back the SD to 20200404 and used Q201 dtb file. The eth0 interface is recognized but there are still errors in kern.log and the interface is still faulty (can't get an IP from DHCP nor connect to it when set statically): 

    root@hassio:~# dmesg -T --level=err,warn
[Wed Apr  8 17:02:39 2020] KASLR disabled due to lack of seed
[Wed Apr  8 17:02:41 2020] OCFS2 User DLM kernel interface loaded
[Wed Apr  8 17:02:42 2020] meson8b-dwmac c9410000.ethernet: IRQ eth_wake_irq not found
[Wed Apr  8 17:02:42 2020] meson8b-dwmac c9410000.ethernet: IRQ eth_lpi not found
[Wed Apr  8 17:02:42 2020] meson8b-dwmac c9410000.ethernet: PTP uses main clock
[Wed Apr  8 17:02:42 2020] dwc3 c9000000.dwc3: Failed to get clk 'ref': -2
[Wed Apr  8 17:02:43 2020] phy phy-d0078080.phy.3: unsupported PHY mode 5
[Wed Apr  8 17:02:43 2020] hub 2-0:1.0: config failed, hub doesn't have any ports! (err -19)
[Wed Apr  8 17:02:43 2020] mmc2: queuing unknown CIS tuple 0x80 (2 bytes)
[Wed Apr  8 17:02:43 2020] mmc2: queuing unknown CIS tuple 0x80 (3 bytes)
[Wed Apr  8 17:02:43 2020] mmc2: queuing unknown CIS tuple 0x80 (3 bytes)
[Wed Apr  8 17:02:43 2020] mmc2: queuing unknown CIS tuple 0x80 (7 bytes)
[Wed Apr  8 17:02:47 2020] gx-sound-card sound: ASoC: no DMI vendor name!
[Wed Apr  8 17:02:47 2020] panfrost d00c0000.gpu: d00c0000.gpu supply mali not found, using dummy regulator
[Wed Apr  8 17:02:47 2020] panfrost d00c0000.gpu: GPU Fault 0x00000088 (UNKNOWN) at 0x000000fcffbfffc0
[Wed Apr  8 17:02:48 2020] meson_vdec: module is from the staging directory, the quality is unknown, you have been warned.
[Wed Apr  8 17:02:48 2020] hci_uart_bcm serial0-0: serial0-0 supply vbat not found, using dummy regulator
[Wed Apr  8 17:02:48 2020] hci_uart_bcm serial0-0: serial0-0 supply vddio not found, using dummy regulator
[Wed Apr  8 17:02:48 2020] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[Wed Apr  8 17:02:48 2020] brcmfmac mmc2:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.amlogic,q201.txt failed with error -2
[Wed Apr  8 17:02:48 2020] bluetooth hci1: Direct firmware load for brcm/BCM4345C0.hcd failed with error -2
[Wed Apr  8 17:02:49 2020] meson8b-dwmac c9410000.ethernet eth0: PTP not supported by HW
[Wed Apr  8 17:02:49 2020] ext4 filesystem being mounted at /var/log supports timestamps until 2038 (0x7fffffff)
[Wed Apr  8 17:02:50 2020] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[Wed Apr  8 17:02:50 2020] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04
[Wed Apr  8 17:03:09 2020] process 'docker/tmp/qemu-check033460557/check' started with executable stack
[Wed Apr  8 17:03:12 2020] overlayfs: NFS export requires "index=on", falling back to nfs_export=off.

    I've extracted the dtb file from the working Android system and from the 20200404 img and converted them to dts file. I tried to adapt some values in the ethernet@c9410000 {...} part to mimic what is in the android part, but this didn't help (in some cases, it created more errors). I'm really confused how as how to make progress on this, any kind of help would be very welcome :D (dts files in attachments).

     

    android-q201.dts meson-gxm-q201.dts

    0

    Single Armbian image for RK + AML + AW (aarch64 ARMv8)

    in General Chat

    Posted

    On 3/30/2020 at 12:29 AM, thehotery said:

    just installed Armbian_20.05.0_Arm-64_bullseye_current_5.6.0-rc6_20200326.img.xz on beelink gt-1 (amlogic s912) with FDT=/dtb/amlogic/meson-gxm-q200.dtb and.. all works! but until i'm trying to upgrade or some packages to upgrade some of system libs.. lan dont working (cable, wifi working). in dmesg  there's lines

     

    [ 2590.051321] meson8b-dwmac c9410000.ethernet eth0: no phy at addr -1
    [ 2590.051343] meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)

     

     

    last thing before its became broken was upgrading: sudo apt-get install binutils (full log in spoiler

      Hide contents

    user@arm:~$  sudo apt-get install binutils
    [sudo] password for hotery:
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    Some packages could not be installed. This may mean that you have
    requested an impossible situation or if you are using the unstable
    distribution that some required packages have not yet been created
    or been moved out of Incoming.
    The following information may help to resolve the situation:

    The following packages have unmet dependencies:
     binutils : Depends: binutils-aarch64-linux-gnu (= 2.34-5) but 2.34-4 is to be installed
     binutils-aarch64-linux-gnu : Depends: binutils-common (= 2.34-4) but 2.34-5 is to be installed
                                  Depends: libbinutils (= 2.34-4) but 2.34-5 is to be installed
    E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
    user@arm:~$  apt-mark unhold binutuls-aarch64-linux-gnu
    E: Unable to locate package binutuls-aarch64-linux-gnu
    E: No packages found
    user@arm:~$  apt-mark unhold binutils-aarch64-linux-gnu
    dpkg: error: required read/write access to the dpkg database directory /var/lib/dpkg
    E: Sub-process dpkg --set-selections returned an error code (2)
    E: Executing dpkg failed. Are you root?
    user@arm:~$  sudo apt-mark unhold binutils-aarch64-linux-gnu
    Canceled hold on binutils-aarch64-linux-gnu.
    user@arm:~$  sudo apt-get install binutils
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    The following package was automatically installed and is no longer required:
      libprocps7
    Use 'sudo apt autoremove' to remove it.
    The following additional packages will be installed:
      binutils-aarch64-linux-gnu binutils-common libbinutils libctf0
    Suggested packages:
      binutils-doc
    The following packages will be upgraded:
      binutils binutils-aarch64-linux-gnu binutils-common libbinutils libctf0
    5 upgraded, 0 newly installed, 0 to remove and 13 not upgraded.
    Need to get 4,570 kB of archives.
    After this operation, 0 B of additional disk space will be used.
    Do you want to continue? [Y/n] y
    Get:1 http://httpredir.debian.org/debian bullseye/main arm64 libctf0 arm64 2.34-5 [41.7 kB]
    Get:2 http://httpredir.debian.org/debian bullseye/main arm64 binutils-aarch64-linux-gnu arm64 2.34-5 [1,936 kB]
    Get:3 http://httpredir.debian.org/debian bullseye/main arm64 libbinutils arm64 2.34-5 [470 kB]
    Get:4 http://httpredir.debian.org/debian bullseye/main arm64 binutils arm64 2.34-5 [59.0 kB]
    Get:5 http://httpredir.debian.org/debian bullseye/main arm64 binutils-common arm64 2.34-5 [2,063 kB]
    Fetched 4,570 kB in 10s (445 kB/s)
    (Reading database ... 37614 files and directories currently installed.)
    Preparing to unpack .../libctf0_2.34-5_arm64.deb ...
    Unpacking libctf0:arm64 (2.34-5) over (2.34-4) ...
    Preparing to unpack .../binutils-aarch64-linux-gnu_2.34-5_arm64.deb ...
    Unpacking binutils-aarch64-linux-gnu (2.34-5) over (2.34-4) ...
    Preparing to unpack .../libbinutils_2.34-5_arm64.deb ...
    Unpacking libbinutils:arm64 (2.34-5) over (2.34-4) ...
    Preparing to unpack .../binutils_2.34-5_arm64.deb ...
    Unpacking binutils (2.34-5) over (2.34-4) ...
    Preparing to unpack .../binutils-common_2.34-5_arm64.deb ...
    Unpacking binutils-common:arm64 (2.34-5) over (2.34-4) ...
    Setting up binutils-common:arm64 (2.34-5) ...
    Setting up libbinutils:arm64 (2.34-5) ...
    Setting up libctf0:arm64 (2.34-5) ...
    Setting up binutils-aarch64-linux-gnu (2.34-5) ...
    Setting up binutils (2.34-5) ...
    Processing triggers for libc-bin (2.29-10) ...
    Processing triggers for man-db (2.9.1-1) ...

     

     

    things like apt-cache showpkg libbinutils or sudo apt-get install binutils-aarch64-linux-gnu-2.34.4 gives nothing, and in http://ftp.debian.org/debian/pool/main/b/binutils/ no such version.  but maybe thats not a reason of broken lan.. please help to repair it..

     

     

     

    I have a similar issue, also with beelink GT1 2Gb ram (S912): with Armbian_20.05.0_Arm-64_bionic_current_5.6.0-rc6_20200331.img, eth0 and wlan0 eventually started to work using dtb q200 (was NOT the case with previous RC6 img, was previously running an old 4.20 kernel img) BUT today I had a small power failure and on reboot, I started to loose eth0 support again, with following error in kern.log: 

    Apr  7 14:32:56 localhost kernel: [   11.076849] meson8b-dwmac c9410000.ethernet eth0: no phy at addr -1
Apr  7 14:32:56 localhost kernel: [   11.076859] meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)

     

    NB: directly after installing rc6_20200331, I did an apt update + apt upgrade and all went fine (I did not upgrade the kernel), so in my case the problem with eth0 does not seem to be related to upgrading some packages.

    Since this error started to appear just after a power failure, could this be linked to some corrupted file ? Any idea how I could restore  them ?

    0

    Single Armbian image for RK + AML + AW (aarch64 ARMv8)

    in General Chat

    Posted

    On 2/28/2020 at 4:30 PM, Seb_Lz said:

    Hello guys,  I'm trying to get armbian 20.05 buster on a Beelink GT1 2GB, but unfortunately I cannot get ethernet to work. I had success with an older version (4.20.5-aml-s912 ubuntu armbian) with khadas-vim2 dtb, but the same dtb from 20.05 does not work (no eth0 interface). Using q201 dtb seems to make the eth0 interface available but it won't actually connect (dhcp failing, manual configuration also not working). Has anyone managed to get ethernet working on recent kernel with Beelink GT1 ?

    Might also be worth mentionning that wifi is also not working (less of a problem in my case though). It seems so strange that it was working with an older kernel with vim2 dtb and not anymore with the new one. I'm wondering if I missed something, especially since this is quite a popular device and that I doubt being the only one trying to get the new armbian image working on it.
    (And I take this opportunity to thanks everyone, especially balbes150 ofc, involved in this project for the amaizing work done :thumbup:).

    0

    Single Armbian image for RK + AML + AW (aarch64 ARMv8)

    in General Chat

    Posted

    Hello guys,  I'm trying to get armbian 20.05 buster on a Beelink GT1 2GB, but unfortunately I cannot get ethernet to work. I had success with an older version (4.20.5-aml-s912 ubuntu armbian) with khadas-vim2 dtb, but the same dtb from 20.05 does not work (no eth0 interface). Using q201 dtb seems to make the eth0 interface available but it won't actually connect (dhcp failing, manual configuration also not working). Has anyone managed to get ethernet working on recent kernel with Beelink GT1 ?

    0
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept