All Activity

This stream auto-updates     

  1. Past hour
  2. I'm currently testing now. Will report back in 20-30 minutes.
  3. Try this version, it has a kernel with all the latest changes.
  4. I've seen in your signature that you have OPi1+s, I've even tried some of your pre-built images, but mine refuses to boot unless I use a pre 5.1.5 dtb or modify the cpu opp table. Weird, but as long as there's a workaround, I'm not complaining.
  5. For SD no " boot.ini", N2 only (extlinux.conf) and u-boot-2019. For USB + new SPIboot (u-boot-2015) use boot.ini (with minimal configuration to run the main kernel). Prior to the SPI support in u-boot-2019, the optimal solution is to use SPIboot that runs any system with removable media and eMMC in any convenient and custom user order.
  6. Today
  7. woohoo i'll have to try i'm still using the hardkernel repo does the new uboot use boot.ini? or standard ubootness
  8. From Armbians point of view it is still the dev branch. Though the linux source repository has been updated to 5.3.0 stable release.
  9. OrangePiZero root@orangepizero:~# uname -r 4.19.59-sunxi root@orangepizero:~# cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 10 (buster)" NAME="Debian GNU/Linux" VERSION_ID="10" VERSION="10 (buster)" VERSION_CODENAME=buster ID=debian HOME_URL="" SUPPORT_URL="" BUG_REPORT_URL="" root@orangepizero:~# Only run sud apt get update / upgrade and then sudo apt install however it threw out this Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details. invoke-rc.d: initscript docker, action "start" failed. * docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; disabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Tue 2019-09-17 13:41:42 UTC; 65ms ago Docs: Process: 9480 ExecStart=/usr/sbin/dockerd -H fd:// $DOCKER_OPTS (code=exited, status=1/FAILURE) Main PID: 9480 (code=exited, status=1/FAILURE) dpkg: error processing package (--configure): installed package post-installation script subprocess returned error exit status 1 Processing triggers for libc-bin (2.28-10) ... Processing triggers for systemd (241-7~deb10u1) ... Processing triggers for man-db (2.8.5-2) ... Errors were encountered while processing: E: Sub-process /usr/bin/dpkg returned an error code (1)
  10. It's been a while since I read this topic .... For reference u-boot-2019 and kernel 5.x have been working at N2 with Armbian (Including sound.).
  11. I understand. It's an unfortunate situation as the USB3.0 interface for meson-g12b devices is broken and neither Amlogic or Hardkernel devs want to send the patch upstream to mainline and follow it up ( One should absolutely avoid using meson-g12b devices if you want to use USB3 then. At the current state, my VIM3 is pointless as I can't move files between my micro SD and USB Harddrives. So I guess I've to build my own kernel and include this patch
  12. 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.
  13. This patch is for an old kernel, I don't work with this old kernel. WiFi is evil, I don't work with it.
  14. The new version for Odroid N2 SPIboot to support all options of running different systems from any media (USB, SD, eMMC PXE).
  15. I did not wait for the release of the official version of the image for SPI with full support for all options for custom startup (SD USB eMMC PXE). As a temporary solution I have gathered the image of "spiboot.img " to update SPI content with a new download option (which supports all described devices). Now, to enable all devices in the startup process (including the ability to directly start the system from USB media) does not require a UART console. All operations can be easily performed by a regular user using standard methods (which are well documented on the WIKI). The update procedure is described on the WIKI. File "spiboot.img" (with all options except Piteboot) can be downloaded here. Pay attention, this version is not Piteboot. During build there was an error with the build kernel, I did not fix (I don't use Piteboot). If somebody need Piteboot, I recommend not using my version. Hi For the statistics, to make sure everything is working correctly, you can check the new SPIBOOT on your model N2 ?
  16. You would need to ask that question in an android forum somewhere Also what is your use case for the T95Z plus? It's not a great TV box, the S912 has lots of cores but they are not that fast, the GPU is barely adequate, it doesn't have usb3, it only has 2gb ram, it's expensive for what you get and it's a discontinued product
  17. And I need to find a way to migrate my current install. I turned 3x 8TB into a 16TB raid-5 BTRFS array, and am somewhere around 8.5-9TB in use. I thought I had a lot of headroom, but if the tools won't work...
  18. I strongly want to buy T95Z PLUS, but I noticed that its operating system is Android 7.1. I am a bit worried that this version will be out of date, causing software incompatibility problems. I have searched on Google for a long time and have not found an answer. Does anyone can answer it?
  19. Good catch! We can afford 130Kb of extra size. I would propose to add it to the base set Send a PR, but we need few tests on other devices to see if this package does no harm? Also make this number +1
  20. What shows your output " cpufreq-info |grep governor " - Should be ondemand I suppose, or set to anything else - eg performance? Perhaps "conservative" is a nicer way for your situation ramping up step by step to reduce CPU temp ( cpufreq-set -g conservative ) ... Anyway will build ( BOARD=orangepioneplus BRANCH=dev RELEASE=buster BUILD_MINIMAL=yes BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no ) and flash my H6 OPiOnePlus later today , or is 5.3 already in default branch ( stable? )
  21. Hello, i am a bit confused about the fans and the RPM. My Helios4 Batch3 is pretty loud. I would like to check the RPM of the fans and the status of the HDUs. How do i get such a nice overview like @Bramani? i red, the fan in Batch3 can not be shut off, should/could i switch the fans? Thanks in advance, Jeckyll
  22. Following a successful deployment of an MCP2515 SPI to CAN device with the great help of I’ve been looking into using an SPI to CANFD device with the orangePi R1 (H2+ based). (CANFD allows greater bitrate than the “regular” CAN) I am looking into using the driver made for the mcp2517fd/mcp2518fd, which has been submitted but not yet linux mainlined: This driver seems to be functional with the raspberry pi, and an example of PCB and associated overlay can be seen here: I’ve been able to compile the drivers successfully (on kernel 4.19.72) and insmod/modprobe them. I also managed to compile the overlays into a dtbo (with dtc v1.4.7 and using -@ argument), but uBoot seems to find some errors in it: Applying kernel provided DT overlay sun8i-h3-spi1-mcp25xxfd.dtbo failed on fdt_overlay_apply(): FDT_ERR_BADOVERLAY Error applying DT overlays, restoring original DT 29943 bytes read in 4 ms (7.1 MiB/s) Any ideas as to how I could look into debugging this? libfdt ( shows 14 different ways that the dtbo file can fail loading and have FDT_ERR_BADOVERLAY thrown This is my dts: /dts-v1/; /plugin/; //#include <dt-bindings/interrupt-controller/irq.h> / { compatible = "allwinner,sun8i-h3"; fragment@0 { target-path = "/aliases"; __overlay__ { spi1 = "/soc/spi@01c69000"; }; }; /* the interrupt pin of the can-controller */ fragment@1 { target = <&pio>; __overlay__ { can0_pin_irq: can0_pin_irq { allwinner,pins = "PA2"; allwinner,function = "irq"; allwinner,drive = <0x0>; allwinner,pull = <0x1>; linux,phandle = <0x1>; phandle = <0x1>; }; }; }; /* the clock/oscillator of the can-controller */ fragment@2 { target-path = "/clocks"; __overlay__ { /* external 20M oscillator of mcp2517fd on SPI0.0 */ mcp2517fd_osc: mcp2517fd_osc { compatible = "fixed-clock"; #clock-cells = <0>; clock-frequency = <0x400000>; linux,phandle = <0x2>; phandle = <0x2>; }; }; }; /* the spi config of the can-controller itself binding everything together */ fragment@3 { //target = <0xffffffff>; target = <&spi1>; can_overlay:__overlay__ { status = "okay"; /* needed to avoid dtc warning */ #address-cells = <1>; #size-cells = <0>; mcp2517fd: mcp2517fd@0 { reg = <0>; compatible = "microchip,mcp2517fd"; pinctrl-names = "default"; pinctrl-0 = <&can0_pin_irq>; spi-max-frequency = <10000000>; interrupt-parent = <&pio>; interrupts = <0 2 8>; /* PA2 / IRQ_TYPE_LEVEL_LOW */ clocks = <&mcp2517fd_osc>; }; }; }; };
  23. new version available?
  24. 64° while running stuff like PiHole. And yes has a heatsink but now fan running right now. But yes, seems higher then before.
  25. @ManoftheSea Indeed it is and I am not sure why it was published in that state. I am calling the jumper setting "1-2" 1 and the jumper setting "2-3" 0. This is because I measured the jumpers with the multimeter and could measure a signal when setting the jumpers to 1-2. The labeling I am using is exactly inverted to the one from the table. 1, 0, 0 (meaning J11=1-2, J3=2-3, J10=2-3) for serial NOR, I actually will set them to 0,0,1 (meaning J11=2-3, J3=2-3, J10=1-2). As if exchanging J11 with J10. I tested it with booting from NOR and booting from UART.
  26. Hi, Two things come to my mind, reading your post armbianmonitor -u tells the reader all the details about your Installation, like Kernel-Version and much more Did you already use the search function in the right hand topcorner?
  1. Load more activity