Search the Community

Showing results for tags 'mainline'.

More search options

  • 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
    • Feature Requests
    • TV boxes
    • General chit chat
  • Bug tracker
    • Allwinner A20
    • Allwinner H2 & H3
    • Allwinner H5 & A64
    • Armada A388, A3700
    • Amlogic S905(x)
    • NXP (Freescale)
    • Rockchip 3288 & 3328
    • Other supported boards
  • Development
    • Allwinner H6
    • Rockchip 3399
    • Development

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 852 results

  1. Hello together, i opened a ticket here Why "cat /proc/cpuinfo" does not tell anything about the CPU type?
  2. Hi, unfortunately many times the support for XFS filesystem is just forgotton. At the moment I just run the last update for the cubietruck this morning which includes the new kernel version 4.19 and my system, which is used as an NAS device with XFS filessystem, didn't start again. I found out that this filesystem is not supported anymore (see 'cat /proc/filesystems') and no module is available. Could you plaese take care of this to fix this issue in the future? And/Or tell me please how I can get back to the older version of the kernel which supports XFS. The reason why I say this way is because I cannot spend every time hours or day's first to figure out the problem and than rebuild the system by my self and may the next update will cause the same issue again. The result is the lost of trust in Armbian and the way to use it in professional enviroments... So please tell me a quick and reliable solution. ;-) Thanks in advance...
  3. Hello! I'm using Armbian Stretch for 1080P Pinebook A64. I've installed Armbian Stretch about 2 months ago, when it was still "Unsupported" and in-development. Now, however, it's supported. Currently, I'm on Armbian Stretch 5.60 and dev branch. I would like to update to 5.69 and next branch. However, from armbian-config, I'm only able to go from stable to nightly build (5.68, but still dev branch). Moreover, I can't select next kernel from Other menu. Is there a way to switch branches (barring re-flashing from latest image)?
  4. Hi all, I'd like to use a touch display together with my cubietruck. Research shows displays for all other boards but not for cubietruck :-( Isn't there any touch display out there which works with cubietruck? Do I really have to change system to raspberry or something else? Thanks for your help and best regards, cibomato
  5. Hi! Periodically, time in two-three days, sharply increases CPU utilization, the system becomes disfunctional. SD card and power supply maybe not the best, but they working fine in other systems and I'm tried others. SSH hangs on login while this problem is actual, but i have a serial connection, so can investigate in real time. Please, advise, what to look when this situation came again? top - 03:02:15 up 24855 days, 3:14, 1 user, load average: 1.75, 1.77, 1.93 Tasks: 125 total, 3 running, 70 sleeping, 0 stopped, 8 zombie %Cpu(s): 17.4 us, 26.6 sy, 0.0 ni, 56.1 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem : 505152 total, 9724 free, 144028 used, 351400 buff/cache KiB Swap: 1301132 total, 1299340 free, 1792 used. 343236 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 26012 3040 1304 R 100.0 0.6 46:55.28 systemd 851 root 20 0 6128 1368 948 R 75.2 0.3 34:13.74 systemd-lo+ 8668 root 20 0 7044 2608 2136 R 1.3 0.5 0:00.15 top 7 root 20 0 0 0 0 S 0.3 0.0 14:28.83 ksoftirqd/0 8 root 20 0 0 0 0 I 0.3 0.0 1:21.03 rcu_sched 2 root 20 0 0 0 0 S 0.0 0.0 0:00.05 kthreadd root@pione:/media/data/log# systemctl reboot Failed to set wall message, ignoring: Connection timed out Failed to reboot system via logind: Connection timed out Failed to start Connection timed out See system logs and 'systemctl status' for details. root@pione:/media/data/log# root@pione:/media/data/log# systemctl status Failed to get properties: Connection timed out root@pione:/media/data/log# root@pione:/media/data/log# reboot root@pione:/media/data/log# root@pione:/media/data/log# reboot -f Failed to read reboot parameter file: No such file or directory Rebooting. [141846.733884] reboot: Restarting system ▒▒▒▒▒▒ U-Boot SPL 2018.05-armbian (Aug 19 2018 - 17:07:52 +0200) DRAM: 512 MiB Trying to boot from MMC1 System log:
  6. Hi, Since the armbian release 5.3.6 (Linux 8 jessie 4.13.16-sunxi64) does not contain the module 'nls_utf8', one can not use the OpenMediaVault - OMV - plugin 'Remote Mount' for accessing an external HDD ... for example, which is connected to a Fritz!Box (running Fritz!NAS). Further details please see OMV - Remote Mount: How to mount an HDD that is connected to a Fritz!Box 7490? Please include the module 'nls_utf8' (and maybe some more nls_* modules) in an update compilation, which is based on the same kernel. Many thanks in advance. The module is provided in following Debian Jessie file list (image): Regards, Joe
  7. I use mali kernel drivers from Neil All works just fine with 4.19 but it don't work with 4.20 it looks like there is some problem with memory allocation in this Any idea?
  8. I have few of i2c devices that was successfully tested working with RPi Zero W (Tiny RTC, BME280), but no one is visible to NanoPi Neo Air board with Armbian. I can't get it to work on latest few versions of Armbian. As soon as I add i2c0 to overlays there appears two of i2c devices (both silent): $ ls -la /dev/i2c* crw-rw---- 1 root i2c 89, 0 Jan 28 14:58 /dev/i2c-0 crw-rw---- 1 root i2c 89, 1 Jan 28 14:58 /dev/i2c-1 I need to admit that scan itself took quite significant amount of time. $ sudo time i2cdetect -y 0 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- 0.00user 0.04system 3:59.62elapsed 0%CPU (0avgtext+0avgdata 1036maxresident)k 0inputs+0outputs (0major+64minor)pagefaults 0swaps Since it could be a problem with pull-up resistors, I've tried to add 4K7 resistors to SDA and to SCL lines, but situation remains the same. What am I doing wrong? What step is missed? Will appreciate any help. Thank you.
  9. Nanopi T3 rt-preempt patch made the system can't boot. i have use patch-4.14.93-rt53.patch. use this patch made system cannot boot...
  10. Hi, my overlays=w1-gpio spi-spidev are not working anymore since I upgraded from 4.14.84-sunxi to 4.19.13-sunxi (Banana Pi with armbian 5.70). Regarding the 1-wire protocol cat /sys/bus/w1/devices/*/w1_slave responds "No such file or directory" since the upgrade. Also regarding the spi overlay # ls /dev/spi* should result in /dev/spidev0.0 whereas kernel 4.19 says "cannot access /dev/spi*: No such file or directory". All was working fine with the 4.14 kernel. thanks in advance
  11. Hi, I'm trying to set up multiple wlan interfaces for my Orange Pi Zero Plus2 H5. I want to have a interface in AP mode and a interface in Managed Mode ... so that I can provide a minimal "register me into your wlan" AP and the other interface can try that provided wlan credentials without reusing/ turning off / reconfigurating the AP interface. So I want to run a normal hostapd on wlan1 and a wpa_supplicant on wlan0 ... When I'm using the iw list command, I get serveral "valid interface combination", one is * #{ managed } <=1 , #{ AP } <= 1, #{ P2P-client } <= 1, #{ P2P-device} <= 1, #total <= 4, #channel <= 1 afaik that means that I can run one managed (Station) interface and one AP interface with same channel, but it should be totally possible on starting up I've got one wlan0 interface in managed mode, when I'm now trying to add a new interface (iw phy0 interface add wlan1 type managed) I got a error "Device or resource busy" which is totally correct, because there can only be one managed interfache when I turn on the hostapd process on wlan0, it changes that interface to AP mode (I've confirmed this using iw dev), so I'm trying to add now a new interface (iw phy0 interface add wlan1 type managed), but I got a other Error "Operation not supported". So now the question: - Is my general assumption, that the orange pi zero plus2 can run multiple wlan interfaces right ? Since when I'm trying to add more that supported interfaces I got other error than the case, when in my opinion the prerequests are ok... if this is generall not possible I guess I got other errors. - Do I anything wrong with configurating or did I missed some prequests ? - Since the armbian for the h5 is in development, maybe there might be also some issue about the driver etc ? - has anyone succedded with such a usecase on this board ? Thanks in advance Roman Koehler
  12. Hi I am referencing below from this closed thread: So currently I set up wifi through an initial ethernet connection, but the issue is when the wifi connection is successfully setup, that connection does not become active until ethernet is unplugged and board rebooted. Wifi is setup through there an option we are missing that is preventing both network interfaces from working simultaneously? currently just using "sudo nmcli dev wifi connect ssid password password"
  13. Hi, Please, i am seeking for some help. Today i just did an apt-get dist-upgrade and my banana pi updated the kernel to 4.19.13. There wasnt any error messages but then i wasnt able to boot. I get messages like "/boot/zImage file not found" so i checked my sdcard (wich cointains the boot folder) and i saw that zImage was symlink to the previous kernel image (wich no longer existed). I corrected it cause in fact there was a vmlinuz-4.19.13-sunxi but there are some more symlinks broken in boot foolder. UInitrd is also broken and i dont have the appropiate file to make a new symlink, script.bin symlink is also broken (it pointed to /boot/bin/bananapi.bin wich dont exists anymore on my system) Can i repair the boot folder in any way? Can somebody with the same board provide me that files? Basically all the boot folder with kernel 4.19.13-sunxi or if anyone can explain me a way to boot again...
  14. I have a Pine64+ 2GB and use Waveshare 3.5 (A). Armbian Bionic Ubuntu installed. I tried to initiate Waveshare screen by following steps: - Enable spidev0.0 from armbianEnv.txt (confirm with /dev/spidev0.0) - modprobe fbtft by: sudo modprobe fbtft_device name=piscreen But I got error with step 2. Here is the output of dmesg [ 4419.154174] fbtft: module is from the staging directory, the quality is unknown, you have been warned. [ 4419.163004] fbtft_device: module is from the staging directory, the quality is unknown, you have been warned. [ 4419.164436] spidev spi0.0: spidev spi0.0 1000kHz 8 bits mode=0x00 [ 4419.164564] spidev spi0.0: Deleting spi0.0 [ 4419.165176] fbtft_device: GPIOS used by 'piscreen': [ 4419.165183] fbtft_device: 'reset' = GPIO25 [ 4419.165187] fbtft_device: 'dc' = GPIO24 [ 4419.165190] fbtft_device: 'led' = GPIO22 [ 4419.165203] spi spi0.0: fb_ili9486 spi0.0 32000kHz 8 bits mode=0x00 [ 4419.186567] fb_ili9486: module is from the staging directory, the quality is unknown, you have been warned. [ 4419.188554] fb_ili9486 spi0.0: fbtft_request_gpios: gpio_request_one('reset'=25) failed with -517 It seems that GPIO25 is not responded. I know that many have success with OrangePi, but no one with Pine64. Any suggestion? Thanks.
  15. I enabled modules, and connected DS18B20 but still haven't 28-XXX... folder in /sys/bus/w1/devices. In README.sun8i-h3-overlays written that default port is PD14 but i can't find it on my board pinout.
  16. I just got a Nanopi NEO2 512MB, installed Armbian Ubuntu Bionic. It works fine, except for the DVB-T/C stick. It is affected by Kernel 4.10+ problems. I wonder if I can downgrade to an older kernel, like 4.4.0 for example, where everything works perfectly? If yes, how? There is a patch that perhaps would resolve the problem, how could I apply this patch to an of the available releases of Armbian? This patch Please, help me with this. Many thanks!
  17. I will describe my problem with NanoPi Neo Core2: I installed the system on eMMc I installed WiringNP I installed the USB drive Everything worked, also Putty via USB I wanted to connect the external module via SPI. The module requires setting the transfer frequency to 20 MHz. I decided to look at the file sun50i-h5-nanopi-neo-core2.dtb . For this purpose, I decompiled to a file . dts . Due to late night time I made a cardinal error, that is before these activities I did not copy the file . dtb I just played on the operating system. After the power is turned off NanoPi and the next day the system is not raised. Red power LED is lit green while not depicted close. Router does not see NanoPi and was obviously seen. Replacing the power supply did not help. I recorded the system card ( DietPi , Armbian , FriendlyElec ) . After inserting into NanoPi the system also did not start. I tried different combinations: start with ethernet and without, with putty (serial), with different SD cards and nothing. I read on the forum that NanoPi with the H3 processor always tests the presence of an SD card in the first place and if it is in the bootable version it starts the system from it. Probably NanoPi Neo Core2 with H5 processor this rule does not apply. Please help me solve the problem of SETTING UP BOOT FROM SD CARD !
  18. I'm trying to get TFTP support into U-Boot but it insists that 'no ethernet found'. I've added a couple of nodes to the device tree such that it has 'status = "okay" and mac-address = [00 00 00 00 00 00]; I've also added a top level alias in sun50i-h5-nanopi-k1-plus.dts (as added by @martinayotte following this thread) as below. Not sure if the U-Boot config needs changing in any way but the network components are certainly being built. Any thoughts most welcome. AATIA. aliases { serial0 = &uart0; ethernet0 = &emac; }; U-Boot dump of the loaded DTB on running system follows: => bdinfo arch_number = 0x00000000 boot_params = 0x40000100 DRAM bank = 0x00000000 -> start = 0x40000000 -> size = 0x80000000 baudrate = 115200 bps TLB addr = 0xBFFF0000 relocaddr = 0xBDF4B000 reloc off = 0x73F4B000 irq_sp = 0xB9F27590 sp start = 0xB9F27590 Early malloc usage: 2d8 / 400 fdt_blob = 00000000b9f275a8 => fdt addr 00000000b9f275a8 => fdt print ethernet0 ethernet@1c30000 { compatible = "allwinner,sun8i-h3-emac"; syscon = <0x0000000e>; reg = <0x01c30000 0x00010000>; interrupts = <0x00000000 0x00000052 0x00000004>; interrupt-names = "macirq"; resets = <0x00000005 0x0000000c>; reset-names = "stmmaceth"; clocks = <0x00000005 0x0000001b>; clock-names = "stmmaceth"; #address-cells = <0x00000001>; #size-cells = <0x00000000>; status = "okay"; mac-address = [00 00 00 00 00 00]; mdio { #address-cells = <0x00000001>; #size-cells = <0x00000000>; compatible = "snps,dwmac-mdio"; phandle = <0x0000000f>; }; mdio-mux { compatible = "allwinner,sun8i-h3-mdio-mux"; #address-cells = <0x00000001>; #size-cells = <0x00000000>; mdio-parent-bus = <0x0000000f>; mdio@1 { compatible = "allwinner,sun8i-h3-mdio-internal"; reg = <0x00000001>; #address-cells = <0x00000001>; #size-cells = <0x00000000>; ethernet-phy@1 { compatible = "ethernet-phy-ieee802.3-c22"; reg = <0x00000001>; clocks = <0x00000005 0x00000043>; resets = <0x00000005 0x00000027>; }; }; mdio@2 { reg = <0x00000002>; #address-cells = <0x00000001>; #size-cells = <0x00000000>; }; }; };
  19. Hi! I was using armbian 5.60 with 4.14.70 kernel and WiFi AP worked flawsessly. Today I had to rebuild my sd card, so I downloaded the latest available build Armbian Stretch mainline kernel 4.19.y I can connect to WiFi from the board, also able to setup a WiFi AP on the board. But when I try to connect to the new AP I see the following message in terminal and the connecting device fails after several seconds: Message from syslogd@localhost at Jan 17 18:20:38 ... kernel:[ 349.842020] Internal error: Oops: 96000004 [#1] SMP Message from syslogd@localhost at Jan 17 18:20:38 ... kernel:[ 350.021242] Process RTW_CMD_THREAD (pid: 607, stack limit = 0x0000000068aba9f4) Message from syslogd@localhost at Jan 17 18:20:38 ... kernel:[ 350.069577] Code: f9405ae0 a90a0ba0 11000421 8b02001b (b8626800)
  20. I'm running some stress test on the NanoPi neo2 512mb, CPU heating reached 75-76 degrees, and it's stable, the problem that I faced is that the computer changed it's IP suddenly (after 55 minutes of test running), I guess it's because of a network card reset. Did anyone face the following issue? Is it related to the stress test? Or it's another networking problem? The test I'm running is with the "stress" tool, running long time stress on 4 CPUs. In addition, does anyone have any insights regarding this device? good or bad?
  21. Hello guys, at first I want to says thanks for the great OS that you deliver. I use it since 8 months on a bunch of nano-pi neo2's and it runs rock solid. However i rebuild from time to time the image I use from scratch in order to see that the installation is reproducable and repeatable. Today it has encountered that the installation of 'apt-get install python:armhf python-dev:armhf' failed with: # dpkg --add-architecture armhf # sudo apt-get update .... Reading package lists... Done # sudo apt-get install -y python-pip python:armhf python-dev:armhf Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: python-dev:armhf : Depends: libpython-dev:armhf (= 2.7.12-1~16.04) but it is not going to be installed Depends: python2.7-dev:armhf (>= 2.7.12-1~) but it is not going to be installed E: Unable to correct problems, you have held broken packages. I use armbian_5.38_Nanopineo2_Ubuntu_xenial_next_4.14.14.img. The reason I do this, is that I want to use Segger Debugger on the platform, but Segger only provides armhf-libs (used by Pylink-square). Asking Segger to release arm64 libraries already failed. Thanks in advance, Axel.
  22. We have deployed the zero for an integrated MCU on one of our products, and in rare occasions we are experience random lockups of the MCU (possibly related to overheating). Its pretty much impossible to debug this since it happens very rarely, but we are trying to mitigate all possible causes. The MCU is controlling a bigger and more expensive board and a fan. If there are internal failsafes that are being triggered by the MCU and locking it up (like temp) we want to disable as many of them as possible (we would rather have the MCU burn up than our main board). Anyone have any insights on orange pi zero OTP or OCP in kernel or uboot parameters we can disable?
  23. hello after updating from cat /proc/version Linux version 4.14.84-sunxi ( (gcc version 7.2.1 20171011 (Linaro GCC 7.2-2017.11)) #3 SMP Sat Dec 1 07:18:41 CET 2018 to Linux version 4.19.13-sunxi ( (gcc version 7.2.1 20171011 (Linaro GCC 7.2-2017.11)) #5.70 SMP Sat Jan 12 15:43:21 CET 2019 my one wire thermometer stopped working - is there some additional steps needed now? I didn't change my configuration overlays=w1-gpio param_w1_pin=PB10 param_w1_pin_int_pullup=0  and now I have dmesg [ 1174.451457] w1_master_driver w1_bus_master1: Attaching one wire slave 00.e80000000000 crc 2b [ 1174.456242] w1_master_driver w1_bus_master1: Family 0 for 00.e80000000000.2b is not registered. [ 1234.023523] w1_master_driver w1_bus_master1: Attaching one wire slave 00.180000000000 crc 5f [ 1234.029428] w1_master_driver w1_bus_master1: Family 0 for 00.180000000000.5f is not registered. ... ls /sys/bus/w1/devices 00-180000000000 00-580000000000 00-980000000000 w1_bus_master1 (00-... directories names and count changes after every minute) cat /sys/kernel/debug/gpio gpiochip0: GPIOs 0-287, parent: platform/1c20800.pinctrl, 1c20800.pinctrl: gpio-40 ( |ahci-5v ) out hi gpio-224 ( |cd ) in lo IRQ gpio-225 ( |cd ) in lo IRQ gpio-227 ( |usb2-vbus ) out hi gpio-228 ( |usb0_id_det ) in hi IRQ gpio-230 ( |usb1-vbus ) out hi gpio-244 ( |cubieboard2:green:us) out lo gpio-245 ( |cubieboard2:blue:usr) out lo gpio-271 ( |onewire@0 ) in lo gpiochip1: GPIOs 413-415, parent: platform/axp20x-gpio, axp20x-gpio, can sleep: there is no "gpio-42" line, old was cat /sys/kernel/debug/gpio gpiochip0: GPIOs 0-287, parent: platform/1c20800.pinctrl, 1c20800.pinctrl: gpio-40 ( |ahci-5v ) out hi gpio-42 ( |w1 ) in hi gpio-224 ( |cd ) in lo IRQ gpio-225 ( |cd ) in lo IRQ gpio-227 ( |usb2-vbus ) out hi gpio-228 ( |usb0_id_det ) in hi IRQ gpio-230 ( |usb1-vbus ) out hi gpio-244 ( |cubieboard2:green:us) out lo gpio-245 ( |cubieboard2:blue:usr) out lo gpiochip1: GPIOs 413-415, parent: platform/axp20x-gpio, axp20x-gpio, can sleep:
  24. Good day! Tell me if there is support for hardware acceleration Orange PI WIN PLUS Cortex-A64 ?? I try to run a video (vlc,mpv) but it is very slow =(
  25. hi orangepi 2e+ with ARMBIAN 5.65 stable Ubuntu 18.04.1 LTS 4.14.84-sunxi syslog I want to mount my external hard disks with cat /etc/udev/rules.d/91-intenso.rules KERNEL=="sd?1", SUBSYSTEMS=="usb", ATTRS{serial}=="31700000000000007023", SYMLINK+="Intenso", ACTION=="add", RUN+="/bin/mount /dev/Intenso /mnt/Intenso" Normally no problem, tested with Armbian_5.65_Orangepiplus2e_Ubuntu_xenial_default_3.4.113 and Workstation PC Linux 4.15.0-43-generic #46~16.04.1-Ubuntu. With my current version, I have a problem. The udev-rule is/seem ok LINK 'Intenso' /etc/udev/rules.d/91-intenso.rules:1 RUN '/bin/mount /dev/Intenso /mnt/Intenso' /etc/udev/rules.d/91-intenso.rules:1 But orangepi@orangepiplus2e:~$ ls /mnt/Intenso/ orangepi@orangepiplus2e:~$ But If I mount manually orangepi@orangepiplus2e:~$ sudo mount /dev/Intenso /mnt/Intenso/ orangepi@orangepiplus2e:~$ ls /mnt/Intenso/ Filme FRITZ lost+found Musik recup_dir.86 Serien Where is my fault ? Bye nepo