Active threads

Showing topics posted in for the last 365 days.

This stream auto-updates     

  1. Past hour
  2. https://forum.loverpi.com/discussion/861/upstream-u-boot-status Will it be possible to use the forthcoming SPI u-boot to boot armbian?
  3. Today
  4. chwe

    Image for M4 V 2

    as soon as this PR makes it: https://github.com/armbian/build/pull/1646 and images are available on our download page. Or you build one of your own with the PR already applied.
  5. Hi, thanks for the reply So after a lot of working around I managed to boot an image from the eMMC, this is the https://dl.armbian.com/_old/tinkerboard/archive/Armbian_5.77_Tinkerboard_Debian_stretch_next_4.19.33.7z I need to compile it with the CRYPTOROOT parameters, how do I build that specific version? So far building with KERNELBRANCH and LIB_TAG options doesn't seem to work Any help is greatly appreciated
  6. mainline kernel support, libreelec is allready working. is there any chance on getting amrbian ported here, i allready did some test and made it boot, but network does not get an ip adress link with ethtool show up and 1 gbit. same for the eachlink device
  7. I've seen this patch from 2017 last week, but I don't understand why it has not been approved and merged yet. Maybe you can try to save it under userpatches/kernel/rockchip64-dev/ folder and try to build a DEV image ... EDIT : Oh ! This patch is so old, it didn't applied at all. I had to revamp it and restart a new build. Will test later ...
  8. I bought a DEALDIG BOXD6 (s912 3GB/32GB) with seems a clone of a Beelink GT1 Ultimate. This box works great with Armbian (bluetooth, WiFi): _ __ __ _ / \ | \/ | | / _ \ | |\/| | | / ___ \| | | | |___ /_/ \_\_| |_|_____| Welcome to Ubuntu Eoan with Armbian Linux 5.3.0-aml-g12 System load: 0.00 0.14 0.25 Up time: 20 min Local users: 3 Memory usage: 14 % of 2805MB IP: 169.254.5.80 192.168.0.124 CPU temp: 50°C Usage of /: 42% of 28G 0 mise à jour peut être installée immédiatement. 0 de ces mises à jour est une mise à jour de sécurité. *** /dev/mmcblk1p2 will be checked for errors at next reboot *** *** /dev/mmcblk1p2 will be checked for errors at next reboot *** Last login: Fri Dec 6 14:19:08 2019 inxi -Fxs System: Host: Dealdig-BOXD6 Kernel: 5.3.0-aml-g12 aarch64 bits: 64 compiler: gcc v: 7.4.1 Console: N/A Distro: Ubuntu 19.10 (Eoan Ermine) Machine: Type: ARM Device System: Amlogic Meson GXM (S912) Q201 Development Board details: N/A Battery: Device-1: hidpp_battery_0 model: Logitech Wireless Touch Keyboard K400 Plus charge: 55% (should be ignored) status: Discharging CPU: Topology: 8-Core (2-Die) model: ARMv8 v8l variant: cortex-a53 bits: 64 type: MCP MCM arch: v8l rev: 4 features: Use -f option to see features bogomips: 0 Speed: 1512 MHz min/max: 100/1512:1000 MHz Core speeds (MHz): 1: 1512 2: 1512 3: 1512 4: 1512 5: 1000 6: 1000 7: 1000 8: 1000 Graphics: Device-1: meson-gxm-dw-hdmi driver: meson_dw_hdmi v: N/A bus ID: N/A Device-2: meson-gxm-mali driver: panfrost v: kernel bus ID: N/A Display: server: X.Org 1.20.5 driver: modesetting unloaded: fbdev resolution: 1920x1080~60Hz OpenGL: renderer: panfrost v: 2.1 Mesa 19.2.1 direct render: Yes Audio: Device-1: meson-gxm-dw-hdmi driver: meson_dw_hdmi bus ID: N/A Device-2: meson-gx-audio-core driver: meson_gx_audio_core bus ID: N/A Device-3: simple-audio-card driver: asoc_simple_card bus ID: N/A Sound Server: ALSA v: k5.3.0-aml-g12 Network: Device-1: meson-gxbb-dwmac driver: meson8b_dwmac v: N/A port: N/A bus ID: N/A IF: eth0 state: down mac: 98:13:39:XX:XX:XX Device-2: pwm-clock driver: pwm_clock v: N/A port: N/A bus ID: N/A IF-ID-1: wlan0 state: up mac: 10:d0:7a:XX:XX:XX Drives: Local Storage: total: 28.91 GiB used: 11.60 GiB (40.1%) ID-1: /dev/mmcblk1 model: SLD32G size: 28.91 GiB Partition: ID-1: / size: 27.57 GiB used: 11.50 GiB (41.7%) fs: ext4 dev: /dev/mmcblk1p2 ID-2: /boot size: 121.7 MiB used: 99.9 MiB (82.1%) fs: vfat dev: /dev/mmcblk1p1 ID-3: /var/log size: 48.4 MiB used: 7.3 MiB (15.1%) fs: ext4 dev: /dev/zram0 Sensors: Message: No sensors data was found. Is sensors configured? Info: Processes: 258 Uptime: 7m Memory: 2.74 GiB used: 914.2 MiB (32.6%) Init: systemd runlevel: 5 Compilers: gcc: 9.2.1 clang: 9.0.0-2 Shell: bash v: 5.0.3 inxi: 3.0.36
  9. Freeshly built Armbian_19.11.3_Orangepipc2_disco_current_5.3.13 works without problem. Restarted several times.
  10. @balbes150 Thank you for good work with the distributions! I have one question or request. Is there any change to get some kind of change log for the new releases?
  11. Below 10C? Around 13C? What's Ambient, 0C? You keep this outdoors, in the Arctic?
  12. did you doublecheck that you didnt add a space on the username root? Thats the most error when I type to fast. Normally you have to enter 2 times root/1234 and then you have to change the password.
  13. my ./userpatches/config-default.conf defaults to branch master as LIB_TAG but I cant set BRANCH=master at compile.sh because then I do get [ error ] Kernel branch not defined for this board [ master ] So I could use LEGACY, CURRENT and DEV and maybe NEXT Which branch should I use to get an older u-boot? I think released branches are v19.08 and v19.11 (took the names from https://github.com/armbian/build ) but I also do get [ error ] Kernel branch not defined for this board [ v19.08 ] [ error ] Kernel branch not defined for this board [ v19.11 ] But also with LEGACY and NEXT I do get only the new u-boot 2019.10 Please give me a info what to try
  14. OrangePi told me on twitter that the camera for my OrangePi RK3399 would be this one... I should get it tomorrow, so that I'll soon know that. They told me the same thing for the 10.1 display, but I did not buy it (yet).
  15. Are looking subject about TV boxes, there the entire grinding halt after the info.
  16. You can "thank" AML for this. They broke the u-boot. They put a bunch of crap in it that works exclusively with their old and crappy 4.9 core. For the color to work correctly with the 5.4 kernel, you either need the old u-boot-2015 (from the firmware, before AML broke it) or use u-boot-2019 (removing u-boot-2015 completely). Offtopic. The behavior of AML lately has been increasingly frustrating for me. They do not pay any attention to the development of support for their chips in the main core (this work is done by third-party developers). Instead of helping, their new patches create a bunch of problems for the main kernel. I am waiting for the release of new Rockchip chips (or other platform options other than AML), and I hope to completely switch to using them for my development (minimizing support for AML, limiting myself to the chip models I already have).
  17. Kernel 5.98 uses two packages (image and dtb). 5.99 the kernel uses a single shared package. You need to delete both packages (image and dtb).
  18. Armbian_19.11.3_Aml-g12_bionic_dev_5.4.0-next-20191202_desktop Magicsee N6 Max boots to desktop using rockpi-4 dtb (after wait) randomly turns off TV display (display restored by off-on TV)
  19. Since with the ARM architecture it is not only necessary to know which components are soldered on the SBC but also know how exactly they are connected each other it is elementary to know if and which common (by Armbian supported) SBC the TV box is built around if it is not a custom built by the manufacturer. And even then it might not help you since the Allwinner H6 and all boards based on it are still in development state and do not come with any support.
  20. Agree with OP ! Maybe the community will be able to discuss the parts of a future pinephone 2. For a free modem I have a very small hope for the future... Guys, do you think that its so impossible for the comunity to make a modem ? Maybe with a risc ?
  21. Yesterday
  22. Peeked inside. I can see memory modules and it seems the model is identical to A95x F2R
  23. ... which is a part of the README https://github.com/brektrou/rtl8821CU#arm-architecture-tweak-for-this-driver-this-solves-compilation-problem-of-this-driver Does it work now?
  24. Hi there, I was wondering if there is a GPIO generic Python library somewhere for Armbian? I think I remember that the pins are not always announced the same way on Armbian and on OrangePi distros. I have seen this effort by @chwe, but is there anything else? Thanks.
  25. Will there be support for the RK3399PRO processor? e.g. for a Rocki pi N10 SBC?
  26. Actually, I don't have any issue using an HDMI monitor alone, just with the adapter. So it could be related to the PHY implementation, did I hit an edge case? I would gladly help to diagnose the problem if there is any way to do it in that case.
  1. Load more activity