chrisf

Members
  • Content Count

    160
  • Joined

  • Last visited

About chrisf

  • Rank
    Elite member

Recent Profile Visitors

902 profile views
  1. chrisf

    Espressobin - etherchannel?

    @Jbobspants I think the switch ports are dependent on the eth0 port being up first, maybe it has something to do with timing/ordering?
  2. chrisf

    Espressobin - etherchannel?

    Why are you trying to bond two ports? There is only a 1Gb link between the switch and the SoC, you're not going to get any more bandwidth
  3. chrisf

    Espressobin - etherchannel?

    You have to make a choice with the shared SERDES lanes. Espressobin has already made that for you with it's PCB layout - one lane goes to SATA, one to USB3 and one to PCIe. There is only one lane on the PCIe slot, which is also apparently limited to 2.5Gb in early boards due issues running at PCI 2 speeds. The switch is connected via a 1Gb link to the 3270. Your physical limitations will be 2.5* or 5Gb on the PCIe slot and 3Gb on the SATA 2 connection. The 3Gb link uses 8b/10b encoding, so it's limited to 300MB/s. * OpenWRT has reduce PCIe speed to 1.0 https://git.openwrt.org/?p=openwrt/openwrt.git;a=commitdiff;h=772258044b48036699302840abf96cd34c4e5078
  4. The system is fine, cpuinfo shows 4 cores of 0xc0f and 4 of 0xc07 0xc07 is a Cortex-A7 and 0xc0f is a Cortex-A15 What version of htop is it?
  5. Isn't a pi-hole just a DNS server? You don't need multiple interfaces for that, nor do you need gigabit speeds to serve a local network. All you'd need to do would be update the DHCP settings in your router to set the DNS server to that of the pi-hole.
  6. chrisf

    NanoPC T4 - Fan-connector

    If you have a proper crimping tool for the pin, crimping alone is better than soldering or crimping and soldering. The solder wicks up the stranded wire and creates a point where all the flexing will happen, resulting in easily broken connections.
  7. Have you tried looking at /proc/interrupts to see which cores are actually handling the interrupts?
  8. To me that load log says one core is maxed out due to IRQ activity. You've got a single core doing all the network stuff and it can't handle any more load. Do you need IP masquerading? Is it possible to distribute network IRQ handling to both cores? If you can that may increase bandwidth, but may also slightly increase latency?
  9. The manufacturer of the board isn't paying Armbian. Armbian is a group of volunteers making a Linux distribution. They're also not paying sunxi. sunxi is a group of volunteers making a Linux kernel for Allwinner SoC's. If you want to get mad at someone for the poor software support for your board, get made at Xunlong, the company you actually paid for a product you feel is inadequate. Don't get mad at the people spending their free time making things better for you, without you giving anything back to them.
  10. You could mount a different volume at the place those directories are. Might even work with a symlink
  11. chrisf

    Help on Buffer strength GPIO

    It's my understanding that Allwinner GPIO's have configurable output drive levels. They're configured with the Px_DRVx_REG registers. There are 4 levels, from Level 0 to Level 3. The default is Level 1. I don't know what current corresponds to each level, it used to be 10mA, 20mA, 30mA and 40mA with the A20's. Level 1 is 20mA, which as the default for the register, matches the data sheet maximum drive strength. Personally, I'd put my own buffer on a GPIO if it's driving more than a few mA.
  12. chrisf

    NanoPi NEO4

    The GPU's in these SoC's can usually do h264. Older ones can't do hardware acceleration for h265. It requires kernel driver support for the GPU that's built in. This usually gets done for Android kernels, so phones and tablets have good performance. No one is paying to have this done in the mainline Linux kernel, it's left up to volunteers. The Exynos 5422 in the XU4 has hardware for encoding and decoding h.264 video. The C2's soc, the Amlogic S905 has hardware for h264 and h265. Hardkernel advertises that too, so you'd probably have better luck getting it working. You might need to use their kernel to get something working "out the box".
  13. chrisf

    NanoPi NEO4

    A benefit of the x86 based ones would be hardware video decoding driver support. The XU4 does have h264 hardware decoding support. The problem is getting it working in Chrome for YouTube. Apparently it worked with the Flash plugin, but it requires effort to enable to HTML5 video.
  14. chrisf

    Ubiquiti Unifi Controller on XU4

    It's still on jessie. I've had no reason to change anything. Jessie is still a supported version. In terms of "go into production", it's an SBC in my garage...
  15. chrisf

    Cubietruck : battery issues

    The risk of fire for unprotected cells is tall of you over charge them. They catch on fire when there is an internal short circuit. Over charging is one way to break down the insulation inside.