Search the Community

Showing results for tags 'mainline'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Announcements & first aid
    • Announcements
    • Board doesn't start
  • Community forums
    • Common issues / peer to peer technical support
    • Reviews, Tutorials, Hardware hacks
    • Feature Requests
    • TV boxes
    • General chit chat
  • Bug tracker - supported boards only
    • Allwinner A20
    • Allwinner H2 & H3
    • Allwinner A64, H5 and H6
    • Armada A388, A3700
    • Amlogic S905(x), S922X
    • NXP (Freescale)
    • Rockchip 3288 & 3328
    • Rockchip 3399
    • Other supported boards
  • Development
    • Development
  • TV Boxes's General chat
  • TV Boxes's Single Armbian image for RK + AML + AW (aarch64 ARMv8)
  • TV Boxes's Single Armbian image for RK + AML + AW (armhf ARMv7)
  • TV Boxes's Review
  • Android fanboys's Forums

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start






Website URL





  1. From reading through the forums I cobbled together what I thought might work for getting spi nor to boot, but it fails: Activate the spi-jedec-nor overlay in /boot/armbianEnv.txt : overlays=spi-jedec-nor param_spinor_spi_bus=0 Then, after reboot, "cat /proc/mtd" should produce something like this : dev: size erasesize name mtd0: 00200000 00001000 "spi0.0" Here is where it fails - I just get the heading, with no mtd0: 00200000 00001000 "spi0.0". Should I be using a different param_spinor_spi_bus? I assume that once that works, the following will work?
  2. Hi, OPiPC with latest mainline (ARMBIAN 5.34 user-built Ubuntu 16.04.3 LTS 4.13.12-sunxi). Need to test the I2S0. From what I see in patches, the I2S driver code is already there so I just need an overlay to use it. Is there any DT overlay for using the H3 I2S0 with any codec ? Even as a generic simple-audio-codec ? Christos
  3. Hello, I have installed ARMBIAN 5.60 stable Debian GNU/Linux 9 (stretch) 4.14.70-sunxi on a Banana Pi M2+ and I need to read and write to the GPIO pins from a bash script, does anyone have a workable solution? I tried with an Orange Pi in the past and I compiled a binary to access the gpio values but it did not work and I cannot find that source any more. Thanks in advance.
  4. Hello,Respected Developers: I'm an Orange Pi user.In the process of using the armbian, I encountered serious problems. My Control Board is Orange Pi PC Plus.Armbian is "ARMBIAN 5.59 stable Ubuntu 18.04.1 LTS 4.14.65-sunxi" I installed jdk and mysql.And run a JAVA program.I set a time zone for Asia-Chongqing,The system language is Chinese,I use three serial ports. When running for a period of time,There will be bugs.About one to three days. The specific phenomena are as follows: 1.Run "date",the time is 1978. 2.Mysql occupy cpu 195%, occupy mem 27%,systemd occupy cpu 34%,Another s
  5. Hi, I have a couple of these boards which I have been using with Armbian and the old, 3.10 kernel. Ideally I would really like to go mainline as later kernels have some functionality that would be useful for my use of the board. The only remaining reason (apart from cpu freq.) for sticking to the 3.10 kernel has been the lack of MIPI DSI support in mainline, but now I see that, despite the Matrix at still being red for A64 mipi, some work is being/has been done by Maxime Ripard. I'm just wondering if anyone here knows if
  6. In the FriendlyARM thread we did try to use A64 images from the Pine64 or the BananaPi M64 with the NanoPi A64. The last times we did that with less success - OK Sytem is running but Network/Sound has to added via USB. No suppport for the onboard devices But today a user did wrote that - with the actual stable Pine64-image ( Armbian_5.69_Pine64_Debian_stretch_next_4.19.13 ) WiFi is useable. So I flasded the Pine64-image to a MicroSDCard and did boot. Additiionally I
  7. I have Orange PI PC Plus with GC2035 camera module. Upgraded to 4.13.6 sunxi-next mainline kernel and noticed that GC2035 camera driver is gone! Why is it so? Maybe someone forgot to include this driver to the kernel? People are still using these cameras and need them! If it was a conscious decision to remove the GC2035 camera from the sunxi-next tree - then, well, it was a horrible decision that should be reversed. Please return this driver. Earlier it was at ./drivers/media/video/sunxi-vfe/device/gc2035.c location, but
  8. Hello Folks, Good day. I hope you're doing great. I'm trying to make the OrangePI 10.1 inch MIPI DSI (product page) work on the most recent (mainline) Armbian build. Building the image using the OrangePI source repositories and following the instructions on OPi4B manual enables the LCD and touch, However, my intention is to make the LCD + Touch work on the most recent Armbian Focal (mainline). I've setup my Armbian build env but I cannot see to find how to enable this MIPI screen on any build options. Here's the instructions from Page #20 of OPi 4B manual: Down
  9. Hello, I have a massive problem as the time/date on my Pine64 keep changing randomly to the year 2113. In my project, I use several Pine64s and the problem now occurs on many of these Pine64s. Unfortunately I need the correct time for my project. I am using the following system: ARMBIAN 5.32.170911 nightly Ubuntu 16.04.3 LTS 4.13.0-sun50iw1 (with additional overlays = uart3 and console = ttyS3) Could this be due to the error described in the post and is the bug fixed in kernel version 4.14? Could I install this kernel version 4.14 via armbian-config (next-kernel)?
  10. Hello everyone. This happens on my OrangePi after a couple of hours of running. I don't think this happened before installing the kernel 4.14. I haven't changed my power supply, which should be working well - custom DC/DC converter connected to GPIO pins. Is anyone else experiencing this? Anything I can do? [19155.760977] INFO: rcu_sched self-detected stall on CPU [19155.760983] INFO: rcu_sched self-detected stall on CPU [19155.760997] INFO: rcu_sched detected stalls on CPUs/tasks: [19155.761010] 2-...: (1 ticks this GP) idle=18a/1/0 softirq=332295/332295 fqs=0 [19155.761017] 0-
  11. Hello, I am trying to communicate with a mcp2515 breakout (8Mhz oscillator) on an Orange Pi Pc+ I have modified the breakout following info on Raspberry Pi: HowTo/Quickstart MCP2515 to keep logic level @3v I have two other nodes composed by two Arduinos, with same (not modified) breakout, one that transmits the other receives. I have successfully tested the first breakout (used on OPi) with an Arduino (powered by 3.3v and 5v on TJA1050). It lets me think that hardware is OK. Below photos of wiring (nb: orange wire becomes red, is wired near TJA1050 =
  12. Hi! Now that the camera interface has been merged in mainline Kernel, I would like to try to use the OrangePi OV5640 camera module on my OrangePi One. So with the latest Armbian Bionic (20.02.1, kernel 5.4.20), I have been trying to get a device tree overlay. But for now, it fails to compile with: $ sudo armbian-add-overlay sun8i-h3-csi.dts Compiling the overlay Error: sun8i-h3-csi.dts:27.23-24 syntax error FATAL ERROR: Unable to parse input tree Error compiling the overlay My current overlay looks like this: /dts-v1/; /plugin/; / { compatible = "allw
  13. Hello all I want to control some GPIO pins on my NanoPi Neo (H3) board and installed WiringNP. Executing commands results in the error piBoardRev: Unable to determine board revision from /proc/cpuinfo I've traced the source of the error down to this line, where WiringNP tries to open /sys/class/sunxi_info/sys_info to determine which board it is running on. This path is not present in my Armbian os. I'm using 4.11.12-sun8i #20 SMP armv7l armv7l armv7l GNU/Linux Am I missing something here? Or are there alternatives to using WiringNP?
  14. Hi, I want to use g_ether on NanoPi Neo Plus2. For Neo Air, I have already figured out how to do this and I can see usb0 in config. But with armbian 5.85 (4.19.38-sunxi64), the same instructions fail at sudo ifconfig usb0 up with the message "usb0: ERROR while getting interface flags: No such device". Could somebody tell me how to activate USB OTG on NanoPi Neo Plus2 and then use g_ether. I think the same holds true for g_serial. This could be an alternative, but I would prever ethernet connection. My target: Connect NanoPi Neo Plus2 with NanoPi Neo Air via Ethernet
  15. We have initial support for Pine64/Pine64+ for a long time in our repository but not released any official images yet. Since this will change soon a sneak preview what to expect. Hardware related issues: Please don't blame Armbian for the few design flaws Pine64 and Pine64+ show: These boards use Micro USB for DC-IN which is the worst possible decision. Most USB cables have a resistance way too high and are responsible for severe voltage drops when consumption increases, then the tiny Micro USB contacts have also a pretty high contact resistance and also maximum a
  16. K-worker takes 10-20 % of one cpu core with later kernels. Does the 4.17 kernel still have this problem? Or is bionic a solution?
  17. Using Armbian_20.02.1 with 5.4 kernel on NEO2 board, I'm running into an issue trying to get the USB OTG working with the g_ether module. When I run modprobe g_ether I see the following in dmesg: [ 490.490582] udc-core: couldn't find an available UDC - added [g_ether] to list of pending drivers I've also tried compiling my own img using the Armbian builder but it looks like all the correct OTG options are already selected by default. Any ideas what I'm doing wrong?
  18. Hello people, I use a Tinker Board as a low power desktop computer for browsing, office documents and general tinkering, and after all this time it got personalized enough to worry about loosing all this setup and it is a hassle to just overwrite everything every time a new image comes around. Was wondering if it is possible to use apt dist-upgrade as means to get from Bionic Desktop 5.4 to Focal Desktop 5.4 as can be done on x86 platforms without breaking everything?
  19. I logged an issue a little while ago with Armbian running on the Tinkerboard that the screen when rotated 90 degrees couldn't draw the screen at any speed. I have been playing with a few alternatives incl going back to the original tinkeros. All have issues so I was delighted to see the FOCAL port. I am using the recommended Waveshare 7" touchscreen that you advertise on the home page as tested 3rd party hardware. Both the desktop and the server versions of Focal come up with the error Configure crtc 0 failed setting mode when I manually set the supported resolution of 1024 x 60
  20. Just wanted to note this - target NanoPi NEO2 - task at hand is Byte-UnixBench.... more to follow...
  21. Enable in armbian-config USB and this no detect USB OTG and additional USB host on the board no working any usb device (microphone, usb storage, keyboard, etc.) that connects detects it Any help you can give me
  22. I am using a orangepi win plus. I have attached a ssd1306 OLED display to the board, using i2c1 interface, using the luma.oled library as driver. import sys from PIL import Image from PIL import ImageDraw from PIL import ImageFont import subprocess from luma.core.interface.serial import i2c from luma.core.render import canvas from luma.oled.device import ssd1306, ssd1325, ssd1331, sh1106 from time import sleep serial = i2c(port=1, address=0x3C) device = ssd1306(serial, rotate=0) width=device.width height=device.height image ='1', (device.width, device.height)) # Get draw
  23. Hello people, I have an Asus Tinker Board S and decided to use the Mainline Armbian for this board, love the new panfrost driver but seems it is glitching all over the place, icons in the menu disappear and reappear when mouse hovers over them, tick boxes do not show if they are ticked and only flicker when mouse is over them and applications menu keep redrawing all over when trying to use among the most prominent problems. Other operating systems work well in this matter. Anyone else is having these problems with the mainline 5.4.28 kernel build?
  24. Device: Orange Pi +2e. Environment one 16GB SD Card and 16GB eMMC onboard. Output from Armbianmonitor attached. The eMMC device onboard is always detected as mmcblk2. Irrespective of whether SD Card is present or not or if you boot from SD Card or eMMC. This is observed only on 20.05 and 20.08 builds. It does not happen on 20.02 build. [ 3.769548] sun8i-h3-pinctrl 1c20800.pinctrl: 1c20800.pinctrl supply vcc-pc not found, using dummy regulator [ 3.781702] mmc0: host does not support reading read-only switch, assuming write-enable [ 3.78
  25. I have a 1 GB Renegade board and downloaded Armbian_19.11.3_Renegade_buster_current_5.3.11 image to install. Noticed it was only 510MB of RAM. Relevant extracts from serial log: U-Boot 2017.09-armbian (Nov 19 2019 - 00:09:05 +0100) Model: Firefly ROC-RK3328-CC DRAM: 510 MiB ____ _ | _ \ ___ _ __ ___ __ _ __ _ __| | ___ | |_) / _ \ '_ \ / _ \/ _` |/ _` |/ _` |/ _ \ | _ < __/ | | | __/ (_| | (_| | (_| | __/ |_| \_\___|_| |_|\___|\__, |\__,_|\__,_|\___| |___/ Welcome to Armbi