Search the Community

Showing results for tags 'solved'.

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 A64, H5 and H6
    • Armada A388, A3700
    • Amlogic S905(x), S922X
    • NXP (Freescale)
    • Rockchip 3288 & 3328
    • Rockchip 3399
    • Other supported boards
  • Development
    • Development

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start






Website URL





Found 186 results

  1. Hello, I have used NanoPi M4v2 with "NVMe SSD adapter" (Officially sold by the FriendlyElec). NVMe SSD is detected when I installed ubuntu based kernel 4.4. (FriendlyCore 18.04 or Armbian Bionic desktop based kernal 4.4.y) But When I installed armbian based kernel 5.x, NVMe SSD is not detected. Anyone can advise?
  2. Odroid-N2 using Armbian_20.08.1_Odroidn2_focal_current_5.8.5 I've recently got a "Connection timed out" issue. For instance, I can open files with nano, use htop, armbian-config, update and upgrade packages, but I can't reboot (everything over ssh). I'm having a feeling that the issue started when I tried to figure out if it's possible to get HDMI to work with my 4K TV when the HDMI cable is not plugged in at boot. In that case, I booted several times and chaged boot.ini with setenv display_autodetect "false", setenv hdmimode "1080p60hz" and setenv disablehpd "true" without success. armbianmonitor -u information is attached at the end in my post where this line might be of interest: "[ 0.000000] [Firmware Bug]: Kernel image misaligned at boot, please fix your bootloader!". Conection timed out message: Running armbianmonitor -v: Does armbianmonitor -v give any useful information? It detects corrupted pacakges, but which? The 10-globally-managed-devices.conf does not seem to exist. At least I can't read it with cat or nano. sysctl --system armbianmonitor -u I guess the only way to reboot is to pull the plug? Or could it be done without pulling the plug if I connect to the N2 with UART? I'm thinking about doing a new fresh install, but before that, is it worth trying to use the legacy kernel (4.9)? Thanks for the awesome work with Armbian! It has truly been a blessing since I first discovered it!
  3. At the moment there are three different saved actions that kind of cover the same thing: Complain about missing data I suggest to merge those to one standardized reply that covers missing data and armbianmonitor -u as well as tips. Something like this (with a bit of additional formatting): Will unhide and add this reply.
  4. Hello, I am looking for a way to create an FTP server in my tvbox, where I can create several users with their respective folders to save files and connect from a PC
  5. The registration terms containing: While the regulation as it is makes sense it does not being in the registration notes since the chance that a users registierung him-/herself just to become a moderator is decently low. These should be more kind of rules that members have to agree which are elected to become a forums moderator. Therefore I suggest to either remove those entirely or rewrite them to descripe what the rights and duties of moderators are and integrate this information into the common terms.
  6. Hi all. Firstly, sorry I had posted this query in the wrong forum. I´m trying to add support for a raw SPI comunication through SPI0, as it´s a custom comunication with a little auxiliary board, I think best option is to have a spidev device. My scenario is: Banana pi m2 ultra Armbian 5.4.35-sunxi, server (No gui). I have been modifying .dts and .dtsi files, here are parts of the files that I modified: sun8i-r40.dtsi spi0_pins: spi0-pins { pins = "PC0", "PC1", "PC2"; function = "spi0"; }; spi0: spi@1c05000 { compatible = "allwinner,sun8i-spi"; device_type = "spidev"; reg = <0x01c05000 0x1000>; interrupts = <GIC_SPI 10 IRQ_TYPE_LEVEL_HIGH>; clocks = <&ccu CLK_BUS_SPI0>, <&ccu CLK_SPI0>; clock-names = "ahb", "mod"; pinctrl-names = "default"; pinctrl-0 = <&spi0_pins>; resets = <&ccu RST_BUS_SPI0>; status = "disabled"; #address-cells = <1>; #size-cells = <0>; }; sun8i-r40-bananapi-m2-ultra.dts &spi0 { status = "okay"; num-chipselects = <1>; cs-gpios = <&pio 2 23 GPIO_ACTIVE_LOW>; // CS = PC23 spidev@0 { reg = <0>; compatible = "spidev"; status = "okay"; spi-max-frequency = <1000000>; }; }; I created a script to compile these files !/bin/bash sudo cpp -nostdinc -I include -I arch -undef -x assembler-with-cpp arch/arm/boot/dts/sun8i-r40-bananapi-m2-ultra.dts preproc.dts dtc -I dts -O dtb -o sun8i-bananapi-m2-ultra.dtb preproc.dtc And I get my new dts. As a comment, the compilation of the device tree throws me this warning: sun8i-r40-bananapi-m2-ultra.dtb: Warning (unit_address_vs_reg): Node /clocks/clk@1 has a unit name, but no reg propert However, I think it is prior to my modifications, because if I delete all my changes the warning is already there. So, next step, I procede to replace original dtb in Banana pi with the one that I just generated, under /boot/dtb-5.4.35-sunxi/ And then, reboot. I expected to get spix.y device under /dev but there is no change here. If i decompile my new dtb, I can see spi spi0-pins { pins = "PC0", "PC1", "PC2"; function = "spi0"; phandle = <0x20>; }; spi@1c05000 { compatible = "allwinner,sun8i-spi"; reg = <0x1c05000 0x1000>; interrupts = <0x0 0xa 0x4>; clocks = <0x7 0x29 0x7 0x71>; clock-names = "ahb", "mod"; pinctrl-names = "default"; pinctrl-0 = <0x20>; resets = <0x7 0x11>; status = "okay"; #address-cells = <0x1>; #size-cells = <0x0>; num-chipselects = <0x1>; cs-gpios = <0xd 0x2 0x17 0x1>; So, Could somebody please tell me what thing (or probably things) I am doing wrong, or if there are any steps I am forgetting? Just in case, I modified the armbianEnv.txt that way overlay=spi-spidev param_spidev_spi_bus=0 to add the spidev overlays (although if I'm not wrong this shouldn't be necessary, since I already enabled spi from the dts, is that correct?) Thanks in advance to anyone who takes the time to read my issue, and if you have any suggestions, they will be more than welcome. Regards. mhc
  7. Hi all, I wanna try to use the hardware PWM on pin 7 of my orange pi one plus. Connect the fan. Toggle the SPI to enable, install wiring orangepi and all looks ok. But when in go to /sys/class/pwm i got a empty directory. I thought the should be a device pwmchip0 or something. I searched on the internet but can´t find a solution. This is what WiringOrangePi shows: Is there someone who knows what i do wrong or hwat i should do? Thank you!
  8. Hi, I normally use Proxmox on Intel Nucs (also Buster based) and also had here usbip with some USB sticks on a USB hub. Now I decided to split that up a bit and so I got some ZeroPi devices and wanted to use them as USBIP hosts kind of. So I installed the buster image and also added usbip_host module to /etc/modules. The devices are seen by the Linux on the ZeroPi in general and also /usr/sbin/usbip list -l lists them successfully. Here the dmesg output too: [ 350.174305] usb 4-1: new high-speed USB device number 6 using ehci-platform [ 350.331127] usb 4-1: New USB device found, idVendor=1a40, idProduct=0101, bcdDevice= 1.11 [ 350.331149] usb 4-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [ 350.331163] usb 4-1: Product: USB 2.0 Hub [ 350.332407] hub 4-1:1.0: USB hub found [ 350.332615] hub 4-1:1.0: 4 ports detected [ 350.738278] usb 4-1.2: new full-speed USB device number 7 using ehci-platform [ 350.968886] usb 4-1.2: New USB device found, idVendor=067b, idProduct=2303, bcdDevice= 3.00 [ 350.968907] usb 4-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 350.968922] usb 4-1.2: Product: USB-Serial Controller [ 350.968935] usb 4-1.2: Manufacturer: Prolific Technology Inc. [ 350.970353] pl2303 4-1.2:1.0: pl2303 converter detected [ 350.972932] usb 4-1.2: pl2303 converter now attached to ttyUSB0 [ 351.154251] usb 4-1.3: new full-speed USB device number 8 using ehci-platform [ 351.384959] usb 4-1.3: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00 [ 351.384969] usb 4-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 351.384975] usb 4-1.3: Product: CP2104 USB to UART Bridge Controller [ 351.384980] usb 4-1.3: Manufacturer: Silicon Labs [ 351.384984] usb 4-1.3: SerialNumber: 01065F3B [ 351.386324] cp210x 4-1.3:1.0: cp210x converter detected [ 351.389285] usb 4-1.3: cp210x converter now attached to ttyUSB1 [ 351.590248] usb 4-1.4: new full-speed USB device number 9 using ehci-platform [ 351.820837] usb 4-1.4: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00 [ 351.820848] usb 4-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 351.820854] usb 4-1.4: Product: CP2104 USB to UART Bridge Controller [ 351.820859] usb 4-1.4: Manufacturer: Silicon Labs [ 351.820864] usb 4-1.4: SerialNumber: 010625FA [ 351.822141] cp210x 4-1.4:1.0: cp210x converter detected [ 351.824928] usb 4-1.4: cp210x converter now attached to ttyUSB2 But as soon as I try to bind such a device (e.g. /usr/sbin/usbip bind --busid=4-1.2) it is said that the device is not connected and log (syslog this time) shows: Sep 1 09:03:55 usb3 usbipd: usbipd: info: starting usbipd (usbip-utils 2.0) Sep 1 09:03:55 usb3 usbipd: usbipd: info: listening on Sep 1 09:03:55 usb3 usbipd: usbipd: info: listening on :::3240 ... Sep 1 09:03:56 usb3 kernel: [ 414.661581] pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0 Sep 1 09:03:56 usb3 kernel: [ 414.661655] pl2303 4-1.2:1.0: device disconnected Sep 1 09:03:56 usb3 sh[1837]: usbip: error: error binding device 4-1.2 to driver: No such device Sep 1 09:03:56 usb3 sh[1837]: usbip: error: could not bind device to usbip-host Does anyone have an idea? Googl was also not that helpful so far. I reconnected the hub to the proxmox host and everythig works there agin without any problem :-(
  9. I have two Rock64 single-board computers running Focal Fossa. One is stable and the other gets segmentation faults when compiling and sometimes a kernel oops. After some searching, my understanding is this can be fixed by slowing down the memory speed by installing rk3328_ddr_333MHz_v1.13.bin from the ayufan-rock64 GitHub repository into uboot along with possibly rk3328_miniloader_v2.46.bin as well. Unfortunately, I'm clueless how to do this. I'm running the latest Armbian Focal Fossa Server from August 19 with the 5.7.17 kernel. Do I need to build a new image or can I patch an existing SD card? I'm sorry if I there is already a thread on this. I searched and could not find enough information that would allow me to proceed on my own.
  10. Problem: No usb power on all ports except for OTG port on Rock Pi 4C. Images: Ubuntu Bionic Legacy Desktop, Ubuntu Focal Legacy, Ubuntu Focal Current Desktop Monitoring information: Ubuntu Bionic Legacy Desktop - Ubuntu Focal Current Desktop:
  11. hey, after updating my nanopct4 and rockpi-4b to from 20.05 to 20.08 RDP stopped working for me, only black screen. After reading all the messy logs, fresh install etc, I found a simple working solution online: In /etc/xrdp/ change #!/bin/sh to #!/bin/bash Sources: Maybe others are affected too, don't know about Ubuntu.
  12. Hi. I am digging many things with armbian so I install fresh armbian and many applications so many times. So I am making a long script to install many applications and edit many configuration. When it asked "Yes/On" on text prompt, I use "#echo yes | apt install vim". It works well. But when I install samba, it ask text prompt "yes/no" at first and then with dialog box "yes/no". So I tried "#echo yes | echo no | apt install samba". But it doesn't work. How can I send "yes/no" to dialog box in bash shell??
  13. After having my old debian (wheezy? or jessy?) unbootable from systemd update I decided to clean install. Having gotten a good Power supply, an A1 Speed 10 SD card, etcher image, and armbian debian 20.08 (also tried 20.07), The board boots (Welcome to armbian) up to "network interfaces up) - then the screen goes blank/black, and I get the green led heardbeat (slow blinking) for a while. Pushing power again the board shuts down (green LED blinking rapidly for a moment, then red power LED comes off). I have had installed boot to nand / Sata disk before but all that shouldn't matter I think because the boot from SD Card seems successful - why could it be that the Screen goes black and I don't get to the login after the 'network interfaces iup' part of booting? Update: this is not a boot but exclusively a screen connection problem - after a while my router picked up on the board and I could ssh into it - so it's a graphics problem, likely the VGA connection is turned off by default or something. And now that that became clear, the solution was also already here:
  14. Hello, I am using Armbian on a Nanopi Neo Allwinner h3. I build Armbian with the Armbianbuild repository and noticed that the CPU Frequency in all builds (minimal/standard) (buster/focal) are between 480MHz and 1.37GHz, but the H3 Soc only supports up to 1.2GHz. This problem also occurs on the finished builds which are there to download from the Armbian website. (Tried with Armbian Buster kernel 5.8.y and Armbian Bionic 5.8.y) root@nanopineo:~# cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to, please. analyzing CPU 0: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 244 us. hardware limits: 480 MHz - 1.37 GHz available frequency steps: 480 MHz, 648 MHz, 816 MHz, 960 MHz, 1.01 GHz, 1.10 GHz, 1.20 GHz, 1.30 GHz, 1.37 GHz available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil current policy: frequency should be within 480 MHz and 1.37 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 480 MHz (asserted by call to hardware). cpufreq stats: 480 MHz:77.19%, 648 MHz:0.91%, 816 MHz:0.01%, 960 MHz:0.00%, 1.01 GHz:0.01%, 1.10 GHz:0.02%, 1.20 GHz:0.02%, 1.30 GHz:0.03%, 1.37 GHz:21.80% (421) In the Armbianbuild documentation the default settings in H2+ and H3 for the NanoPi Neo are 240-912MHz. Is there an option to set the CPU Frequency to this range or is it a bug in the newer releases since the Nanopi Neo is a older board?
  15. Do ourselves a favor and add a mark to the TV-Boxes forums that states that those "boards" are mostly community supported ONLY.
  16. Hi. I was testing pwm with a motor, then my rock pis stopped. After boot, I couldn't see wlan0 in nmtui-connect. So I reinstall fresh armbian, I can see wlan0 again. I do wifi setting with nmtui-connect but after rebooting I can't connect wifi. I have to redo wifi setting with nmtui-connect, put password again and it adds another wifi. It seems like it can't connect to previous wifi. When I do "nmcli con show", I can see the previous wifi but it is deactive. I searched about it and found wifi mac address randomization issue. So I checked "10-override-random-mac-disable.conf". [connection] wifi.mac-address-randomization=1 [device] wifi.scan-rand-mac-address=no Whenever I redo nmtui-connect, it add file count in "/etc/NetworkManager/system-connections" Is there any way to solve it? Or pwm thing break wifi chips??
  17. For the Amlogic S905(x) forums add S912 and S922 to it? I don't think there is a need to divite those into the other supported boards.
  18. Not much to say about that. Do some of these mostly proprietary IM even still exist? I suggest to replace a few of those with more adequate solutions like IRC, Matrix or Mastodon and threw out AIM, MSN, ICQ and Yahoo. Opinions?
  19. The latest build fails if this driver is selected to be build with the kernel. Realtek 8192E USB WiFi (RTL8192EU) [N/m/y/?] (NEW) y --> fails / m --> succeeds If 'm' or module is selected then the build succeeds. -R
  20. TL;DR Where in armbian build system correctly can be make N2-only related changes: 1. /boot ext4 volume have to have symlink . as boot, can be created with command ln -s ./ boot 2. kernel env variable set in boot.ini contain part but it shouldn't. This substring need to be removed if btrfs choosen. 3. /boot ext4 partition have only 4 MB free. I am not sure but think it's too small; for example there no space to run update-initramfs -u. I think it should be larger, like 500 MB. Long: I want to run my oDroid-N2 with root on BTRFS filesystem. I use manual on armbian image build and did time ./ BOARD=odroidn2 BRANCH=current RELEASE=focal BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=yes ROOTFS_TYPE=btrfs INSTALL_HEADERS=no BUILD_KSRC=no then image Armbian_20.08.0-trunk_Odroidn2_focal_current_5.7.16.img was written to microSD card with BalenaEtcher program, inserted into N2 with serial console connected. cap1.log Then I create simlink ./ boot on boot volume, and get cap2.log Then I remove rootflags=data=writeback from bootargs and successfully boot into shell prompt, cap3.log changes: diff -u --- 2020-08-20 23:08:36.000000000 +0300 +++ 2020-08-20 23:26:29.000000000 +0300 @@ -20,7 +20,7 @@ fi # Default Console Device Setting -setenv condev "console=${uartconsole} console=tty1 loglevel=1" # on both +setenv condev "console=${uartconsole} console=tty1 loglevel=5" # on both # Auto Detection of Monitor settings based on your Screen information setenv display_autodetect "true" @@ -115,7 +115,7 @@ if ext4load mmc ${devno}:1 0x44000000 /boot/armbianEnv.txt || fatload mmc ${devno}:1 0x44000000 armbianEnv.txt || ext4load mmc ${devno}:1 0x44000000 armbianEnv.txt; then env import -t 0x44000000 ${filesize}; fi # Boot Args -setenv bootargs "root=${rootdev} rootwait rootflags=data=writeback rw rootfstype=${rootfstype} ${condev} ${amlogic} no_console_suspend net.ifnames=0 elevator=noop hdmimode=${hdmimode} cvbsmode=576cvbs max_freq_a53=${max_freq_a53} max_freq_a73=${max_freq_a73} maxcpus=${maxcpus} voutmode=${voutmode} ${cmode} disablehpd=${disablehpd} ${bootsplash} cvbscable=${cvbscable} overscan=${overscan} consoleblank=0" +setenv bootargs "root=${rootdev} rootwait rw rootfstype=${rootfstype} ${condev} ${amlogic} no_console_suspend net.ifnames=0 elevator=noop hdmimode=${hdmimode} cvbsmode=576cvbs max_freq_a53=${max_freq_a53} max_freq_a73=${max_freq_a73} maxcpus=${maxcpus} voutmode=${voutmode} ${cmode} disablehpd=${disablehpd} ${bootsplash} cvbscable=${cvbscable} overscan=${overscan} consoleblank=0" # Set load addresses setenv dtb_loadaddr "0x1000000" cap1.log cap2.log cap3.log
  21. Unable to comment with Firefox on RK3399 in the Armbian forum. See image. Since Chromium isn't working right with Google account I've been using Firefox instead on the M4V2. For a few days I'm unable to comment on the Armbian forum itself with it. In Chromium this works (since I'm commenting with Chromium now) Also have an issue with Facebook not always loading fully in Firefox, don't know if it's related. Just saying so it's known. Cheers.
  22. Hi team. I am having a difficult time getting the standard Opi CSI camera to work on the newest mainline Armbian. I don't have the ability to use a legacy version because it is coupled with a preconfigured Octopi, thanks to @ldiaz. He says that Octopi will work with the camera once the system works with the camera, and I have not been able to get it to work. There are at least a dozen threads here about that camera, but most are dated. And the ones that aren't seem to talk more about performance, and they assume that your camera is working. I also saw one about overlays, which I have no idea how to deal with, or even what they are. Something tells me it just isn't this hard and that there must be some kind of way to deal with this easily, or it just isn't supported right now in this version and that's that. Either is fine. I'm old, and my brain hurts. Thanks in advance.
  23. Greetings everyone. I have sucessfully used Armbian Bionic in a production environment. Its really great. I am now evaluating Armbian Buster and I am seeing a strange issue perhaps you can direct me where to look so I can do troubleshooting. With the board connected to our corporate network, it takes about 48 hours when the whole board (OrangePi+ 2E) will crash with the CPU burning up. The second time it happened I had htop running to try and diagnose the problem. Investigation revealed that rngd became unstable due to the nm-applet. This led me to re-running the known conditions when this happens, with the network disconnected and now it doesn't crash. Below is a screenshot of the crashed state. Any ideas of where to look would be appreciated. My gut feel tells me this is network related and indeed, by disabling the network interface the problem goes away.
  24. Hello Armbian community My HiFiBerry DAC HAT works well on my Raspberry Pi 3B with RasPiOS. However, I would like to put it on my Rock64 to use the higher Ethernet and USB speed it offers. As far as I can tell, HiFiBerry DAC is in the mainline Linux kernel - it is mentioned in the source code, but I do not understand programming, so I cannot see if it is used. Is the HiFiBerry DAC supported in Armbian's kernel? If so, how can I activate and use it? I put the HAT on the Rock64 and installed Armbian_20.05.2_Rock64_buster_current_5.4.43.img.xz , and it booted without problems, but I could not get sound out of the HiFiBerry DAC, and Alsamixer showed no controls for the sound hardware. I also tried making a Virtualbox to compile the Armbian kernel, and I could get the build environment to work, but I did not find any clues to include support for the HiFiBerry DAC - yes, I am truly clueless when it comes to programming, but I can follow a step by step recipe. Please give me a recipe for getting the HiFiBerry DAC to work on Rock64 with Armbian. Best regards Freddy
  25. I think I have somehow managed to remove my wlan0 interface. I've done a lot of testing on this M4V2 and am happy with my latest configuration and then I noticed my wlan0 interface is gone. I know it was there because I had tested it all (this box is going to my work office I'm not very good with the very low level stuff but this is what I have found sudo nmcli dev status DEVICE TYPE STATE CONNECTION eth0 ethernet connected Nano2Home lo loopback unmanaged -- jerry@nano2:~ $ sudo nmcli con show NAME UUID TYPE DEVICE Nano2Home bfe624a0-6c47-34c7-b947-350dd18b2059 ethernet eth0 Wi-Fi connection 1 62eadfc0-4456-4dc6-8624-771996a69834 wifi -- jerry@nano2:~ $ systemctl status sys-subsystem-net-devices-wlan0.device ● sys-subsystem-net-devices-wlan0.device - /sys/subsystem/net/devices/wlan0 Loaded: loaded Active: inactive (dead) Is it possible to recover from this or do I have to reinstall ? I really appreciate any help..