All Activity

This stream auto-updates     

  1. Past hour
  2. Petee

    A64 date/time clock issue

    Ahh...thank you Martin... root@ICS-Pine64:~# fdtdump /boot/dtb/allwinner/sun50i-a64-pine64-plus.dtb | grep erra **** fdtdump is a low-level debugging tool, not meant for general use. **** If you want to decompile a dtb, you probably want **** dtc -I dtb -O dts <filename> allwinner,erratum-unknown1; root@ICS-Pine64:/boot/dtb/allwinner# dtc -I dtb -O dts -o sun50i-a64-pine64-plus.dts /boot/dtb/allwinner/sun50i-a64-pine64-plus.dtb sun50i-a64-pine64-plus.dts: Warning (avoid_unnecessary_addr_size): /soc/spi@1c68000/spi-flash@0: unnecessary #address-cells/#size-cells without "ranges" or child "reg" property sun50i-a64-pine64-plus.dts: Warning (graph_child_address): /soc/lcd-controller@1c0c000/ports/port@0: graph node has single child node 'endpoint@0', #address-cells/#size-cells are not necessary root@ICS-Pine64:/boot/dtb/allwinner# nano sun50i-a64-pine64-plus.dts Apologies for being dense here.... Found the timer stuff.. add the line "allwinner,erratum-unknown1;" into that node and save. timer { compatible = "arm,armv8-timer"; allwinner,erratum-unknown1; interrupts = < 0x01 0x0d 0xf04 0x01 0x0e 0xf04 0x01 0x0b 0xf04 0x01 0x0a 0xf04 >; }; It is already there when I looked at the file sun50i-a64-pine64-plus.dts. What do I do next?
  3. martinayotte

    A64 date/time clock issue

    You've mistakenly added a <space> between / and boot ... Sorry, copy/paste error ... I'm using self compile dtc ... I've re-edit the above commands by removing this prefix path ...
  4. Petee

    A64 date/time clock issue

    root@ICS-Pine64:~# fdtdump / boot/dtb/allwinner/sun50i-a64-pine64-plus.dtb | grep erra **** fdtdump is a low-level debugging tool, not meant for general use. **** If you want to decompile a dtb, you probably want **** dtc -I dtb -O dts <filename> Couldn't open blob from '/ boot/dtb/allwinner/sun50i-a64-pine64-plus.dtb': No such file or directory FATAL ERROR: could not read: / boot/dtb/allwinner/sun50i-a64-pine64-plus.dtb root@ICS-Pine64:/boot/dtb/allwinner# ls overlay sun50i-h5-nanopi-k1-plus.dtb sun50i-a64-amarula-relic.dtb sun50i-h5-nanopi-m1-plus2.dtb sun50i-a64-bananapi-m64.dtb sun50i-h5-nanopi-neo2.dtb sun50i-a64-nanopi-a64.dtb sun50i-h5-nanopi-neo2-v1.1.dtb sun50i-a64-olinuxino.dtb sun50i-h5-nanopi-neo-core2.dtb sun50i-a64-orangepi-win.dtb sun50i-h5-nanopi-neo-plus2.dtb sun50i-a64-pine64.dtb sun50i-h5-orangepi-pc2.dtb sun50i-a64-pine64-lts.dtb sun50i-h5-orangepi-prime.dtb sun50i-a64-pine64-plus.dtb sun50i-h5-orangepi-zero-plus2.dtb sun50i-a64-pine64-plus.dtb-ORIGINAL sun50i-h5-orangepi-zero-plus.dtb sun50i-a64-pinebook.dtb sun50i-h6-orangepi-lite2.dtb sun50i-a64-sopine-baseboard.dtb sun50i-h6-orangepi-one-plus.dtb sun50i-a64-teres-i.dtb sun50i-h6-pine-h64.dtb sun50i-h5-libretech-all-h3-cc.dtb Getting an error here: root@ICS-Pine64:/boot# git-work/dtc/dtc -I dtb -O dts -o sun50i-a64-pine64-plus.dts /boot/dtb/allwinner/sun50i-a64-pine64-plus.dtb -bash: git-work/dtc/dtc: No such file or directory root@ICS-Pine64:/boot/dtb/allwinner# git-work/dtc/dtc -bash: git-work/dtc/dtc: No such file or directory
  5. Today
  6. martinayotte

    A64 date/time clock issue

    So, it is not fixed ? ... Than, let's check the DTB : what appearing if doing "fdtdump /boot/dtb/allwinner/sun50i-a64-pine64-plus.dtb | grep erra" ? it should show : allwinner,erratum-unknown1; If not, lets edit the DT, by first install DT compiler that support symbols : wget http://ftp.debian.org/debian/pool/main/d/device-tree-compiler/device-tree-compiler_1.4.7-3_arm64.deb dpkg -i device-tree-compiler_1.4.7-3_arm64.deb Then, do backup of DTB and decompile DTB into DTS : cp /boot/dtb/allwinner/sun50i-a64-pine64-plus.dtb /boot/dtb/allwinner/sun50i-a64-pine64-plus.dtb-ORIGINAL git-work/dtc/dtc -I dtb -O dts -o sun50i-a64-pine64-plus.dts /boot/dtb/allwinner/sun50i-a64-pine64-plus.dtb Edit the resulting "sun50i-a64-pine64-plus.dts", find the "timer" node, add the line "allwinner,erratum-unknown1;" into that node and save. Recompile the DTB from the updated DTS : git-work/dtc/dtc -I dts -O dtb -o /boot/dtb/allwinner/sun50i-a64-pine64-plus.dtb sun50i-a64-pine64-plus.dts The, reboot and retest "test_timer" ...
  7. Petee

    A64 date/time clock issue

    I changed the host name from pine64 to ICS-Pine64. root@ICS-Pine64:~# uname -a Linux ICS-Pine64 4.19.35-sunxi64 #5.79.190418 SMP Thu Apr 18 01:36:11 CEST 2019 aarch64 aarch64 aarch64 GNU/Linux Welcome to ARMBIAN 5.78.190415 nightly Ubuntu 18.04.2 LTS 4.19.35-sunxi64 root@ICS-Pine64:~# ./test_timer TAP version 13 # number of cores: 4 ok 1 same timer frequency on all cores # timer frequency is 24000000 Hz (24 MHz) # time1: 7d5fffff7, time2: 7d5e7c200, diff: -1588727 not ok 2 native counter reads are monotonic # 1 errors # min: -1588727, avg: 8, max: 824 ok 3 Linux counter reads are monotonic # 0 errors # min: 541, avg: 74002, max: 734418224158 # core 0: counter value: 34044992124 => 1418 sec # core 0: offsets: back-to-back: 14, b-t-b synced: 9, b-t-b w/ delay: 11 # core 1: counter value: 34044993581 => 1418 sec # core 1: offsets: back-to-back: 11, b-t-b synced: 8, b-t-b w/ delay: 10 # core 2: counter value: 34044995467 => 1418 sec # core 2: offsets: back-to-back: 11, b-t-b synced: 8, b-t-b w/ delay: 10 # core 3: counter value: 34044996666 => 1418 sec # core 3: offsets: back-to-back: 10, b-t-b synced: 8, b-t-b w/ delay: 10 1..3
  8. martinayotte

    A64 date/time clock issue

    Where the ICS in "Linux ICS-Pine64 4.19.35-sunxi64" ? It should normally be seen as "Linux pine64 4.19.35-sunxi64" Anyway, so, this is updating to the Latest NEXT kernel , which seems to also have the timer fix, could you confirm by running "test_timer" ?
  9. Petee

    A64 date/time clock issue

    Gb transfer speeds are fine... Pine64:~# iperf -c 192.168.244.171 ------------------------------------------------------------ Client connecting to 192.168.244.171, TCP port 5001 TCP window size: 85.0 KByte (default) ------------------------------------------------------------ [ 3] local 192.168.244.149 port 57916 connected with 192.168.244.171 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 1.08 GBytes 926 Mbits/sec
  10. Murdag

    Orangepi 3 h6 allwiner chip

    Yeah I scraped VB cause it was so slow, now have qemu setup and running but did not figure out how to forward a drive (that is not even mounted on the host). Putting it onto a LAN and then configuring the wifi things works sure, it's just a bit more to do. thanks anyway
  11. Petee

    A64 date/time clock issue

    Historically with the standard build and doing an armbian-config kernel update it would lock up on reboot and I would start all over with a fresh build.
  12. Petee

    A64 date/time clock issue

    Actually looking at the difference here...looking at the updated standard via nightly good booting ... See this on boot via serial... U-Boot SPL 2018.11-rc3-armbian (Feb 08 2019 - 11:37:16 +0100) root@ICS-Pine64:~# uname -a Linux ICS-Pine64 4.19.35-sunxi64 #5.79.190418 SMP Thu Apr 18 01:36:11 CEST 2019 aarch64 aarch64 aarch64 GNU/Linux root@ICS-Pine64:~# ls -l /boot total 34144 -rw-r--r-- 1 root root 153 Apr 18 16:19 armbianEnv.txt -rw-r--r-- 1 root root 1536 Feb 10 02:54 armbian_first_run.txt.template -rw-r--r-- 1 root root 230454 Feb 10 02:54 boot.bmp -rw-r--r-- 1 root root 2970 Feb 10 02:51 boot.cmd -rw-r--r-- 1 root root 4882 Feb 10 02:54 boot-desktop.png -rw-rw-r-- 1 root root 3042 Feb 10 02:55 boot.scr -rw-r--r-- 1 root root 153079 Apr 17 18:36 config-4.19.35-sunxi64 lrwxrwxrwx 1 root root 19 Apr 18 05:38 dtb -> dtb-4.19.35-sunxi64 drwxr-xr-x 3 root root 4096 Apr 18 05:37 dtb-4.19.35-sunxi64 lrwxrwxrwx 1 root root 23 Apr 18 05:37 Image -> vmlinuz-4.19.35-sunxi64 -rw-r--r-- 1 root root 8624976 Apr 18 05:43 initrd.img-4.19.35-sunxi64 -rw-r--r-- 1 root root 3040151 Apr 17 18:36 System.map-4.19.35-sunxi64 lrwxrwxrwx 1 root root 23 Apr 18 05:43 uInitrd -> uInitrd-4.19.35-sunxi64 -rw-r--r-- 1 root root 8625040 Apr 18 05:43 uInitrd-4.19.35-sunxi64 -rwxr-xr-x 1 root root 14245896 Apr 17 18:36 vmlinuz-4.19.35-sunxi64
  13. martinayotte

    A64 date/time clock issue

    Strange, since I've done the same thing twice this morning, and I didn't have this issue. I don't know, I'm never doing "updates", I always do fresh install. With this standard image with update, what "uname -a" give you ? What is the output of "ls -l /boot" ?
  14. Petee

    A64 date/time clock issue

    Is the nightly Armbian_5.79.190418_Pine64_Ubuntu_bionic_dev_5.0.7.img is now working for you ? No. If I write the nightly image to an SD card it does not boot and shows the errors above via the terminal session. root@pine64:~# [ 312.018172] dwmac-sun8i 1c30000.ethernet eth0: Could not attach to PHY [ 312.024768] dwmac-sun8i 1c30000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) [ 312.064009] dwmac-sun8i 1c30000.ethernet eth0: Could not attach to PHY If I write the standard release Pine64 image to the SD card the Pine64 boots up fine. If I update the standard release to the new nightly build via armbian-config it boots up fine which doesn't make sense. Isn't it the same kernel being updated with the 1 - writing standard release then updating to current nightly build 2 - current nightly build write
  15. martinayotte

    A64 date/time clock issue

    I'm confused which one is which one ... Is the nightly Armbian_5.79.190418_Pine64_Ubuntu_bionic_dev_5.0.7.img is now working for you ?
  16. Petee

    A64 date/time clock issue

    Wierd...via serial terminal see: root@pine64:~# dmesg | grep eth [ 0.000000] psci: probing for conduit method from DT. [ 2.795398] dwmac-sun8i 1c30000.ethernet: PTP uses main clock [ 2.795483] dwmac-sun8i 1c30000.ethernet: Linked as a consumer to regulator.6 [ 2.796023] dwmac-sun8i 1c30000.ethernet: Current syscon value is not the default 6 (expect 0) [ 2.796045] dwmac-sun8i 1c30000.ethernet: No HW DMA feature register supported [ 2.796050] dwmac-sun8i 1c30000.ethernet: RX Checksum Offload Engine supported [ 2.796056] dwmac-sun8i 1c30000.ethernet: COE Type 2 [ 2.796061] dwmac-sun8i 1c30000.ethernet: TX Checksum insertion supported [ 2.796067] dwmac-sun8i 1c30000.ethernet: Normal descriptors [ 2.796072] dwmac-sun8i 1c30000.ethernet: Chain mode enabled [ 11.869154] dwmac-sun8i 1c30000.ethernet eth0: Could not attach to PHY [ 11.875870] dwmac-sun8i 1c30000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) [ 12.010109] dwmac-sun8i 1c30000.ethernet eth0: Could not attach to PHY [ 12.016825] dwmac-sun8i 1c30000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) [ 12.102540] dwmac-sun8i 1c30000.ethernet eth0: Could not attach to PHY [ 12.109185] dwmac-sun8i 1c30000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) [ 12.145562] dwmac-sun8i 1c30000.ethernet eth0: Could not attach to PHY [ 12.152178] dwmac-sun8i 1c30000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) [ 12.191148] dwmac-sun8i 1c30000.ethernet eth0: Could not attach to PHY [ 12.197780] dwmac-sun8i 1c30000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) Booting up with the standard release to updated nightly see: root@ICS-Pine64:~# dmesg | grep eth [ 0.000000] psci: probing for conduit method from DT. [ 2.021202] dwmac-sun8i 1c30000.ethernet: PTP uses main clock [ 2.021289] dwmac-sun8i 1c30000.ethernet: Linked as a consumer to regulator.6 [ 2.021480] dwmac-sun8i 1c30000.ethernet: Current syscon value is not the default 6 (expect 0) [ 2.021494] dwmac-sun8i 1c30000.ethernet: No HW DMA feature register supported [ 2.021499] dwmac-sun8i 1c30000.ethernet: RX Checksum Offload Engine supported [ 2.021505] dwmac-sun8i 1c30000.ethernet: COE Type 2 [ 2.021510] dwmac-sun8i 1c30000.ethernet: TX Checksum insertion supported [ 2.021515] dwmac-sun8i 1c30000.ethernet: Normal descriptors [ 2.021521] dwmac-sun8i 1c30000.ethernet: Chain mode enabled [ 11.662540] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 11.665029] dwmac-sun8i 1c30000.ethernet eth0: No Safety Features support found [ 11.665042] dwmac-sun8i 1c30000.ethernet eth0: No MAC Management Counters available [ 11.665049] dwmac-sun8i 1c30000.ethernet eth0: PTP not supported by HW [ 11.665527] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 12.674853] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx [ 12.674889] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
  17. Igor

    Adding Debian buster

    It seems that base packages are different ... I didn't check anything at this stage. Perhaps a diff between stretch and buster packages should be nice to have. From CLI and desktop ... and adjust accordingly. Probably there are some other packages missing.
  18. Igor

    Orangepi 3 h6 allwiner chip

    Kernel configuration that is used for development is not fine tuned. Add those: CONFIG_PARPORT=m CONFIG_PRINTER=m CONFIG_PPDEV=m and this error will go away.
  19. martinayotte

    Orangepi 3 h6 allwiner chip

    Your image seems to try to find those modules and not finding them ... This doesn't seem to be a "untouched" image, since those modules are not part of the build. Did you install a specific applications or did you modified /etc/modules-load.d/modules.conf ?
  20. martinayotte

    A64 date/time clock issue

    Don't confuse me : Pine64 != Rock64 ... I don't understand why using Armbian_5.79.190418_Pine64_Ubuntu_bionic_dev_5.0.7.img. On my side, here is "dmesg | grep eth" give : root@pine64:~# dmesg | grep eth [ 4.651697] dwmac-sun8i 1c30000.ethernet: PTP uses main clock [ 4.662672] dwmac-sun8i 1c30000.ethernet: Linked as a consumer to regulator.6 [ 4.677055] dwmac-sun8i 1c30000.ethernet: Current syscon value is not the default 6 (expect 0) [ 4.685758] dwmac-sun8i 1c30000.ethernet: No HW DMA feature register supported [ 4.693011] dwmac-sun8i 1c30000.ethernet: RX Checksum Offload Engine supported [ 4.700246] dwmac-sun8i 1c30000.ethernet: COE Type 2 [ 4.705231] dwmac-sun8i 1c30000.ethernet: TX Checksum insertion supported [ 4.712026] dwmac-sun8i 1c30000.ethernet: Normal descriptors [ 4.717702] dwmac-sun8i 1c30000.ethernet: Chain mode enabled [ 18.403292] dwmac-sun8i 1c30000.ethernet eth0: No Safety Features support found [ 18.403309] dwmac-sun8i 1c30000.ethernet eth0: No MAC Management Counters available [ 18.403316] dwmac-sun8i 1c30000.ethernet eth0: PTP not supported by HW [ 31.712399] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx [ 31.712430] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
  21. Petee

    A64 date/time clock issue

    Yes per your instruction did not utilize the 3.3VDC pin on the JTAG port and used a 2 AMP external PS connected to Euler Bus. Aside from the time sync issue (well the time going way off) the network port just disconnects randomly after a day or so with the default Gb setting or adjusted to Mb setting. Does this mean that I have a bad Pine64 here? With the original posted on the Pine64 wiki / forum never had an issue with the legacy Ubuntu 16.04. I did update that original build to Ubuntu 18.04 and it worked OK but did have some issues with it. Had a few minutes here to type between this and that....
  22. ilchenko Evgeny

    Orangepi 3 h6 allwiner chip

    Hi guys! I'm still with my sore) Perhaps this log will enlighten the problem. ozz@orangepi3:~$ systemctl status systemd-modules-load.service * systemd-modules-load.service - Load Kernel Modules Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static; ven Drop-In: /lib/systemd/system/systemd-modules-load.service.d `-10-timeout.conf Active: failed (Result: exit-code) since Thu 2019-04-18 20:26:57 MSK; 3min 49 Docs: man:systemd-modules-load.service(8) man:modules-load.d(5) Process: 465 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status= Main PID: 465 (code=exited, status=1/FAILURE) Apr 18 20:26:57 orangepi3 systemd[1]: Starting Load Kernel Modules... Apr 18 20:26:57 orangepi3 systemd-modules-load[465]: Failed to find module 'lp' Apr 18 20:26:57 orangepi3 systemd-modules-load[465]: Failed to find module 'ppde Apr 18 20:26:57 orangepi3 systemd-modules-load[465]: Failed to find module 'parp Apr 18 20:26:57 orangepi3 systemd[1]: systemd-modules-load.service: Main process Apr 18 20:26:57 orangepi3 systemd[1]: systemd-modules-load.service: Failed with Apr 18 20:26:57 orangepi3 systemd[1]: Failed to start Load Kernel Modules. lines 1-17/17 (END)...skipping... * systemd-modules-load.service - Load Kernel Modules Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static; vendor preset: enabled) Drop-In: /lib/systemd/system/systemd-modules-load.service.d `-10-timeout.conf Active: failed (Result: exit-code) since Thu 2019-04-18 20:26:57 MSK; 3min 49s ago Docs: man:systemd-modules-load.service(8) man:modules-load.d(5) Process: 465 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE) Main PID: 465 (code=exited, status=1/FAILURE) Apr 18 20:26:57 orangepi3 systemd[1]: Starting Load Kernel Modules... Apr 18 20:26:57 orangepi3 systemd-modules-load[465]: Failed to find module 'lp' Apr 18 20:26:57 orangepi3 systemd-modules-load[465]: Failed to find module 'ppdev' Apr 18 20:26:57 orangepi3 systemd-modules-load[465]: Failed to find module 'parport_pc' Apr 18 20:26:57 orangepi3 systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1 Apr 18 20:26:57 orangepi3 systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. Apr 18 20:26:57 orangepi3 systemd[1]: Failed to start Load Kernel Modules.
  23. guidol

    Adding Debian buster

    my first extreme try was the NanoPi A64 (from Pine64) with Buster and as Dev-version, but this experiment was too far It did boot but unstable (reboot & freezes) with different cards... So - because you did post on twitter the picture of the NanoPi R1 mainline 4.19.35 login - I used my "old" Orange Pi R1 and compiled OPi R1 Buster Dev and this seem to run MUCH better than the first try on the NanoPi A64 Now I will try a normal mainline with the NanoPi A64 for Buster - like your NanoPi R1 build but (only dev?) buster hasnt wget fro armbia-config as standard onboard?: root@orangepi:/home/guido# armbian-config /usr/sbin/armbian-config: line 26: wget: command not found Warning: Configuration cannot work properly without a working internet connection. Press CTRL C to stop to stop or any key to ignore and continue. after apt get wget it was OK also ftpd doesnt seem to be onboard anymore - used now vsftpd as replacement
  24. martinayotte

    A64 date/time clock issue

    12h36 EST, Quebec ... I've tried again Armbian_5.79.190418_Pine64_Ubuntu_bionic_dev_5.0.7.img and network is working fine for me. Did you tried not using 3.3V and using your normal PSU, or a 5V attached to GPIO 4/6 pins ? (I'm leaving too, going to supermarket ...)
  25. Petee

    A64 date/time clock issue

    Not sure where you are at Martin. Here it is 1130 C time and will be back later on this afternoon....
  26. Petee

    A64 date/time clock issue

    So did the login in stuff and ... root@pine64:~# ifconfig lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 root@pine64:~# [ 344.021339] dwmac-sun8i 1c30000.ethernet eth0: Could not attach to PHY [ 344.027934] dwmac-sun8i 1c30000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) [ 344.067108] dwmac-sun8i 1c30000.ethernet eth0: Could not attach to PHY [ 344.073698] dwmac-sun8i 1c30000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) [ 344.110071] dwmac-sun8i 1c30000.ethernet eth0: Could not attach to PHY [ 344.116638] dwmac-sun8i 1c30000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) [ 344.145095] dwmac-sun8i 1c30000.ethernet eth0: Could not attach to PHY [ 344.151667] dwmac-sun8i 1c30000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) Got to leave in a little bit here for about 3 hours....do you need anything more for time bean?
  27. Petee

    A64 date/time clock issue

    See an error...using a little 8 port Gb switch (unmanaged) to test... ## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000 EHCI failed to shut down host controller. EHCI failed to shut down host controller. Loading Ramdisk to 497b4000, end 49fff3a9 ... OK reserving fdt memory region: addr=4fa00000 size=6e000 Loading Device Tree to 0000000049743000, end 00000000497b3fff ... OK Starting kernel ... [ 5.275317] asoc-simple-card sound: ASoC: codec-analog@1f015c0 not registered [ 43.843643] dwmac-sun8i 1c30000.ethernet eth0: Could not attach to PHY [ 43.850256] dwmac-sun8i 1c30000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) [ 43.953417] dwmac-sun8i 1c30000.ethernet eth0: Could not attach to PHY [ 43.960064] dwmac-sun8i 1c30000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) [ 43.998929] dwmac-sun8i 1c30000.ethernet eth0: Could not attach to PHY [ 44.005578] dwmac-sun8i 1c30000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) [ 44.045335] dwmac-sun8i 1c30000.ethernet eth0: Could not attach to PHY [ 44.051973] dwmac-sun8i 1c30000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) [ 44.091948] dwmac-sun8i 1c30000.ethernet eth0: Could not attach to PHY [ 44.098542] dwmac-sun8i 1c30000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) Ubuntu 18.04.2 LTS pine64 ttyS0
  1. Load more activity