vlad59

Members
  • Content Count

    170
  • Joined

  • Last visited

About vlad59

  • Rank
    Elite member

Recent Profile Visitors

1251 profile views
  1. @megi Forgot to tell if you want more Tanix TX6 report, go to librelec forum or ask Jernej, he is the one who made the librelec image.
  2. @megi Yeah I won the allwinner lottery (or at least the interesting stuff lottery), tell me if you need anything else
  3. Tanix TX6 : LibreELEC:~ # ./regtool h6-soc-bin SoC bin: invalid (bin=0) (raw=2)
  4. Last time I checked LZ4 kernel algo was not properly optimized for ARM (with NEON) so I don't think you can directly apply this blog results to ARM. The same "problem" happen with zram which is slower than in x86 world.
  5. Hi all, I have a Tanix TX6 4Gb/32Gb on the way. I hope to use it with armbian (if that does not work, I'll use libreelec but I'd prefer having a generic linux). Is there a step by step guide on how to build an armbian image. I read the whole thread and saw that megous tree is almost good to go especially with 5.4 that got a lot of patch included. It's less clear for uboot, is latest uboot good to use or is there some patch to use. Is there a fork of armbian/build with everything included maybe ? Thanks in advance for any help
  6. Done, I hope the PR is good .
  7. A little late but it's working fine : root@pine64:~# uname -a Linux pine64 5.3.1-sunxi64 #5.97 SMP Mon Sep 23 18:28:48 CEST 2019 aarch64 aarch64 aarch64 GNU/Linux root@pine64:~# ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supported pause frame use: Symmetric Receive-only Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Link partner advertised pause frame use: Symmetric Receive-only Link partner advertised auto-negotiation: Yes Link partner advertised FEC modes: Not reported Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 1 Transceiver: internal Auto-negotiation: on Supports Wake-on: d Wake-on: d Current message level: 0x0000003f (63) drv probe link timer ifdown ifup Link detected: yes root@pine64:~# for now my patch is in `userpatches/kernel/sunxi-dev/`. If I understand correctly I just have to move the patch to `patch/kernel/sunxi-dev/` and make a PR, right ?
  8. @martinayotte@Igor I finally found where I read about problem on some pine64+ for ethernet, it was in Librelec forums and Jernej added a patch fixing that a few weeks ago : https://github.com/LibreELEC/LibreELEC.tv/blob/9d68e4ba191d7b0bd319e1e254610917e69526e0/projects/Allwinner/devices/A64/patches/linux/03_pine64_plus_ethernet_fixes.patch The last part of the patch is interesting (= could fix my problem) and was queued for kernel 5.4 : https://lkml.org/lkml/2019/9/18/714 Grepping for `config-magic-for-pine64` or `regulator-enable-ramp-delay = <100000>` inside armbian build source return nothing so I guess that can be it. I'll try a dev build with this patch tomorrow and report here either way.
  9. That's strange indeed, I'll try a new build in a few days (it's currently building and uploading new arm64 docker images 24/7) It was perfectly working with a dev build between the end of july and the beginning of august. I had many problem with date jump in 2114 so I tried updating yesterday (apt-get update && upgrade) and had the problem with eth0. I then tried a full install and I had the same problem. As I said I still have a few days of work for the pine64 and I'll retry a new build
  10. I rebuilt a full image this morning and I still have no wired network. I went back to kernel 4.19.X. I'll spend some time tonight to compare the device trees between 5.2 and 5.3.
  11. Hi, I just updated my pine64 1Gb today (so 190916), it restarted perfectly with 5.3.0 kernel but I lost eth0 with `no phy at addr -1` in dmesg (wlan0 still works fine). Anybody can confirm ? I remember reading about this on irc about 5.3 and pine64 some weeks ago , I'll try to find it again.
  12. Hi all, FYI, I just build an image for a Pine64 (1Gb) and everything seems perfectly fine with kernel 5.2.X -> thanks a lot to all armbian team and especially to @martinayotte I'll probable rebuild my Banana pi image later this month.
  13. For the record my cable length was over 70m (meters not centimeters)
  14. 60cm should be very safe, it should not hurt to try 3K3.
  15. @eyatsko What is the total cable length for your 6 sensors ? Do you use CAT5 / CAT6 ? 5 or 6 years ago, I tried to add 4 sensors in each of my first floor rooms (in the ceiling) -> 4 * 4 = 16 DS18B20 but it was way too much cable length (even with cat5) to have a consistent sensor read. I often had only 8 or 9 sensor available (and sometimes to whole bus disappeared). I tried lowering the pullup, it helped. I tried replacing my only pullup with 3 (and even 4) 15k (distributed along the cable) : it also helped but it was never perfect. Finally I ended up with 4 buses of 4 sensors using 4 pins and it was flawless. Less interesting for you but now I have a single ESP8266 for each room with a some i2c sensors (SI7021, ...). All my DS18B20 were donated or binned. Hope this helps