Search the Community

Showing results for tags 'Solved'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements
    • Announcements
  • Community/Newbie forums
    • Board does not start
    • Off-topic
    • Reviews, Tutorials, Hardware hacks
    • Help wanted
    • TV boxes
  • Hobbyists forums
    • P2P help
    • Feature Requests
  • Bug tracker - supported boards and images only
    • Allwinner A20
    • Allwinner H2 & H3
    • Allwinner A64, H5, H6 and H616
    • Armada A388, A3700
    • Amlogic S905(x), S922X
    • NXP (Freescale)
    • Rockchip 3288 & 3328
    • Rockchip 3399
    • Other supported boards
  • Development
    • Board Bring Up
    • Armbian Project Administration
    • Development
  • TV Boxes's General Chat
  • TV Boxes's Reviews/Tutorials
  • TV Boxes's FAQ
  • TV Boxes's TV Boxes running Armbian
  • TV Boxes's Rockchip CPU Boxes
  • TV Boxes's Amlogic CPU Boxes
  • TV Boxes's Allwinner CPU Boxes
  • Android fanboys's Forums
  • Gaming on ARM's Reviews
  • Gaming on ARM's Issues
  • Kobol Forum's Helios4
  • Kobol Forum's Helios64

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP


Skype


Github


Location


Interests

  1. Hi, I would like to know if it is possible to switch from the current branch to the legacy one as I've read that the board will be much more stable with the older kernel ? I've installed my NanopiM4 last march, and I've experienced some random freezes of my board after some time (can take weeks). It seems that one of my solutions would be to use the legacy kernel as it is much more stable - information I got by reading the forums (something I haven't done before because I'm stupid and was in a hurry...). Is it possible to downgrade only the kernel at all ? Here are the packages that (I think) I have to replace : linux-buster-root-current-nanopim4/buster,now 20.08.3 arm64 [installed] linux-dtb-current-rockchip64/buster,now 20.08.3 arm64 [installed] linux-headers-current-rockchip64/buster,now 20.08.3 arm64 [installed] linux-image-current-rockchip64/buster,now 20.08.3 arm64 [installed] linux-u-boot-nanopim4-current/buster,now 20.08.1 arm64 [installed] With those packages, then : linux-buster-root-legacy-nanopim4 - armbian tweaks for buster on nanopim4 (legacy branch) linux-dtb-legacy-rockchip64 - linux dtb, version 4.4.213-rockchip64 linux-headers-legacy-rockchip64 - linux kernel headers for 4.4.213-rockchip64 on arm64 linux-image-legacy-rockchip64 - linux kernel, version 4.4.213-rockchip64 linux-u-boot-nanopim4-legacy - uboot loader 2020.07 Will that be enough or are more packages needed without screwing my install ? Should I use apt-get or do I have to use the armbian-config tool instead ? Is there an order to respect ?
  2. At the moment there are three sub-forums within common issues: Reviews, Research guides & tutorials and Hardware hacks. Those forums obviously do not receive much attention and the reason might be they are not that present like other forums (and surely new tutorials are not that often posted like issue complains ). Anyway I was thinking about how to bring more attention to these topics and reduce the amount of sub-forums the same time. What I came up with was the following idea: All topics within those forums will be marked with an appropriate prefix, mostly like the forums were called at the moment (so Review, Research/Tutorial and Hardware hack). This can be done in batch in no time. Then the three forums are being merged into one and moved as a unified forum from sub-forums status to a full forum right between Common issues and Feature Requests. New topics MUST be approved to make sure no BS or requests are posted there (latter should be done anywhere else). Based on the average activity there this should not lead into a significant amount of additional work (if any). And MUST have a prefix like described above. Choosing a prefix on topic creation can be enforced by forums software. Please let me know what do you think. PS: Yeah I know I should do other stuff in vacation than this
  3. Hello, I'm tearing my hair out. Help would be much appreciated. Initially, I installed Armbian on an SD card and successfully installed tvheadend and got the tuner to scan successfully. Great, or so I thought. Time to build my 'real' system on a eMMC. After many repeated builds, I cannot, for the life of me, get a successful scan. I'm using the 'predefined' network (UK Sutton Coldfield) which worked just fine before. I am running Armbian_20.08.1_Odroidn2_focal_current_5.8.5_desktop. Edit (can only post one per day). JMMC, what did I do different? Probably the order of things. I initially tried to install tvheadend via armbian-config, it didn't do anything. I installed from the repository. Did I do an 'update & upgrade' before that? Can't remember. Did I do an install firmware, full or part (from armbian-config) before or after? You see my point? Many combinations and permutations, tried a few but loosing track. I'll gladly accept your buster option. Thanks.
  4. I would like to re-enable the Governance_Maintainer page at the docs which has not been used and maintained for quite a while now. https://github.com/armbian/documentation/blob/master/docs/Governance_Maintainers_TBD.md From time to time I already adjusted the list to what I believe fits the current situation but I wanted to hear from you all what you think about it or maybe even why it should not receive attention/maintenance.
  5. HI. I burned the latest official Rockpi4 focal kernel 5.8.x on both rockpi 4 B and C. The problem is only present on the C model. Both USB 2.0 aren't working at all.
  6. Please, does the latest Armbian support setting the resolution on boot? I want to use this resolution in my SDL2 based app, so things like randr does not help me. Thank you very much.
  7. 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 0.0.0.0:3240 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 :-(
  8. It is possible to add explanations to certain expression or acronyms. The example above shows the (in this case case-sensitive) expression OOB (you see it is "underdot'ed") with the explanation "out of the box" while pointing with the cursor on it. Do you think this is a useful feature and if so what acronyms could/should be added to be automatically highlighted? Ideas: dtc - device tree compiler dtb - device tree blob dts - device tree source IRC - internet relay chat sunxi - board family of Allwinner 32bit ARM SoCs sunxi64 - board family of Allwinner 64bit ARM SoCs XU4 - Odroid XU4 OPi - Orange Pi N2 - Odroid N2 C2 - Odroid C2 C4 - Odroid C4 RK - Rockchip AML - Amlogic AW - Allwinner M4 - NanoPi M4 M4V2 - NanoPi M4V2 P2P - peer to peer eMMC - embeeded MultiMediaCard OS - operating system VPU - video processing unit panfrost - driver for Mali Midgard and Bifrost GPUs cedrus - driver for hardware accelerated video de-/encoding PSU - power supply unit RC - release candidate WG - Wireguard
  9. Hi, I have and Orange Pi PC board on which I'm trying to use Armbian from yestarday, "trying" because I have several different problems on which I investigated also on this forum, but I'm unable to solve at the moment (the reason because I'm writing here). Let's start from the beginning. I downloaded the armbian image from armbian website (https://www.armbian.com/orange-pi-pc/), version I'm using now is Armbian 20.08.1 Buster with Linux 5.8.5-sunxi, but I have tried also other versions with exact same behaviour. The first problem is time synchronization root@orangepipc:~# timedatectl Local time: Thu 2020-09-03 16:34:17 CEST Universal time: Thu 2020-09-03 14:34:17 UTC RTC time: Thu 1970-01-01 07:54:18 Time zone: Europe/Rome (CEST, +0200) System clock synchronized: no NTP service: inactive RTC in local TZ: no In this forum I found that a possible solution could be uninstall/install chrony, but if I'm able to remove this I'm not able to reinstall root@orangepipc:~# apt install chrony Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: chrony 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 216 kB of archives. After this operation, 397 kB of additional disk space will be used. Err:1 http://deb.debian.org/debian buster/main armhf chrony armhf 3.4-4 Could not connect to prod.debian.map.fastly.net:80 (151.101.112.204). - connect (111: Connection refused) Could not connect to deb.debian.org:80 (151.101.114.133). - connect (111: Connection refused) E: Failed to fetch http://deb.debian.org/debian/pool/main/c/chrony/chrony_3.4-4_armhf.deb Could not connect to prod.debian.map.fastly.net:80 (151.101.112.204). - connect (111: Connection refused) Could not connect to deb.debian.org:80 (151.101.114.133). - connect (111: Connection refused) E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? In general I'm not able to use apt at all... root@orangepipc:~# apt update Err:1 http://apt.armbian.com buster InRelease Could not connect to apt.armbian.com:80 (173.45.128.12). - connect (111: Connection refused) Err:2 http://security.debian.org buster/updates InRelease Could not connect to prod.debian.map.fastly.net:80 (151.101.112.204). - connect (111: Connection refused) Could not connect to security.debian.org:80 (151.101.192.204). - connect (111: Connection refused) Could not connect to security.debian.org:80 (151.101.0.204). - connect (111: Connection refused) Could not connect to security.debian.org:80 (151.101.64.204). - connect (111: Connection refused) Could not connect to security.debian.org:80 (151.101.128.204). - connect (111: Connection refused) Err:3 http://deb.debian.org/debian buster InRelease Could not connect to prod.debian.map.fastly.net:80 (151.101.112.204). - connect (111: Connection refused) Could not connect to deb.debian.org:80 (151.101.114.133). - connect (111: Connection refused) Err:4 http://deb.debian.org/debian buster-updates InRelease Unable to connect to deb.debian.org:http: Err:5 http://deb.debian.org/debian buster-backports InRelease Unable to connect to deb.debian.org:http: Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. W: Failed to fetch http://deb.debian.org/debian/dists/buster/InRelease Could not connect to prod.debian.map.fastly.net:80 (151.101.112.204). - connect (111: Connection refused) Could not connect to deb.debian.org:80 (151.101.114.133). - connect (111: Connection refused) W: Failed to fetch http://deb.debian.org/debian/dists/buster-updates/InRelease Unable to connect to deb.debian.org:http: W: Failed to fetch http://deb.debian.org/debian/dists/buster-backports/InRelease Unable to connect to deb.debian.org:http: W: Failed to fetch http://security.debian.org/dists/buster/updates/InRelease Could not connect to prod.debian.map.fastly.net:80 (151.101.112.204). - connect (111: Connection refused) Could not connect to security.debian.org:80 (151.101.192.204). - connect (111: Connection refused) Could not connect to security.debian.org:80 (151.101.0.204). - connect (111: Connection refused) Could not connect to security.debian.org:80 (151.101.64.204). - connect (111: Connection refused) Could not connect to security.debian.org:80 (151.101.128.204). - connect (111: Connection refused) W: Failed to fetch http://apt.armbian.com/dists/buster/InRelease Could not connect to apt.armbian.com:80 (173.45.128.12). - connect (111: Connection refused) W: Some index files failed to download. They have been ignored, or old ones used instead. root@orangepipc:~# DNS resolution and ping of the server to which apt is unable to connect are working fine root@orangepipc:~# ping deb.debian.org PING debian.map.fastly.net (151.101.114.133) 56(84) bytes of data. 64 bytes from 151.101.114.133 (151.101.114.133): icmp_seq=1 ttl=52 time=36.8 ms 64 bytes from 151.101.114.133 (151.101.114.133): icmp_seq=2 ttl=52 time=37.4 ms 64 bytes from 151.101.114.133 (151.101.114.133): icmp_seq=3 ttl=52 time=37.2 ms 64 bytes from 151.101.114.133 (151.101.114.133): icmp_seq=4 ttl=52 time=38.0 ms 64 bytes from 151.101.114.133 (151.101.114.133): icmp_seq=5 ttl=52 time=37.6 ms 64 bytes from 151.101.114.133 (151.101.114.133): icmp_seq=6 ttl=52 time=36.8 ms 64 bytes from 151.101.114.133 (151.101.114.133): icmp_seq=7 ttl=52 time=38.7 ms ^X64 bytes from 151.101.114.133 (151.101.114.133): icmp_seq=8 ttl=52 time=37.3 ms 64 bytes from 151.101.114.133 (151.101.114.133): icmp_seq=9 ttl=52 time=36.5 ms ^C --- debian.map.fastly.net ping statistics --- 9 packets transmitted, 9 received, 0% packet loss, time 20ms rtt min/avg/max/mdev = 36.540/37.377/38.687/0.623 ms If i put url http://deb.debian.org/debian/dists/buster/InRelease in web browser it's working, so the problem is not server unavailability. I don't have trouble with my LAN root@orangepipc:~# ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.20.0.195 netmask 255.255.255.0 broadcast 172.20.0.255 ether 02:81:ab:f8:f0:eb txqueuelen 1000 (Ethernet) RX packets 279682 bytes 22254870 (21.2 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2114 bytes 213315 (208.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 38 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 loop txqueuelen 1000 (Local Loopback) RX packets 1 bytes 29 (29.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1 bytes 29 (29.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 I have also problem using GPIO but it's a secondary trouble for the moment. I do not know what to do, I need help because in this way Armbian is useless on my board. Thanks in advance, Daniele.
  10. 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!
  11. 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.
  12. 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
  13. 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.
  14. 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
  15. 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!
  16. Hello, Earlier on this week I decided to upgrade the kernel and the DTBs on my Armbian cluster (quite a few different boards but all of them based on Allwinner A20) from buster-next-5.92 to buster-current-20.08.2. Having successfully completed the upgrade on several other servers, I moved on to the lime2 one - which promptly failed to come back up after the reboot. Connecting the serial console shows u-boot doing its thing without issues and the kernel beginning to boot, producing normal messages - only to suddenly freeze. When exactly the freeze occurs varies, sometimes it even happens halfway through outputting a message line - but it is definitely before the handover to init and I think it's also before initramfs kicks in. Having poked around a bit, I have narrowed the problem down to the DTB update. If I have /boot/dtb point to dtb-4.19.62-sunxi, the system comes up fine - even with the new kernel. On the other hand, as soon as I symlink it back to dtb-5.8.6-sunxi the kernel hangs. BTW. I do not use any overlays and apart from the verbosity increase I do not think I have changed anything in armbianEnv.txt since system installation. In fact, let me just post it here: verbosity=7 logo=disabled console=both disp_mode=1920x1080p60 overlay_prefix=sun7i-a20 rootdev=UUID=REDACTED rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u Any ideas how I can debug this further? If you need any more information, let me know.
  17. This is a bunch of background info, scroll down to TL;DR for my question.... Hello, I am working on developing an application to make single board computers easier to use for non-technical users. You can think of it as something similar to yunohost or freedombox, but with more hand-holding involved around the hardware & network setup. I'm trying to enable people like my mother who've never seen or used a terminal/shell before to be able to set up and operate a server in their home. The general process looks something like this: user downloads my cross platform desktop application called "seedpacket" they run the app and go through a series of setup wizard screens one of the screens prompts them to insert an SD card, then the application will flash the SD card with a linux image for their SBC. seedpacket will then write additional files to the SD card, including things like the user's wifi credentials that they entered earlier on in the wizard. finally, the user will be prompted to insert the SD card into the SBC and turn it on. automated setup scripts will run on the SBC and send data to a cloud service, seedpacket will poll this cloud service and display progress information to the user. I want to support installing Armbian this way. So far I have steps 2 thru 5 working. I can flash the image to the SD card and write my custom config files to the SD card as well. I just tried testing it on my odroid XU4 and it boots, my custom sshd_config & authorized_keys files work, which is great! Next steps: I want to figure out where to put my script that communicates with the cloud service I want to automate the stuff that happens automatically on first login (/usr/lib/armbian/armbian-firstlogin) I want to automate the process of migrating the OS to a USB SATA device (/usr/sbin/nand-sata-install) I want the script that communicates with the cloud service to be able to post an update ASAP, preferably after the first boot and before it reboots to apply the partition re-sizing on the SD card. ------------------------ TL;DR --------------------------------- I just booted Armbian on my odroid XU4 and I can tell it rebooted once after the first boot, based on the /var/log/armbian-hardware-monitor.log having two boot cycles in it. However, I've been looking through https://github.com/armbian/build/blob/master/packages/bsp/common/usr/lib/armbian/armbian-resize-filesystem and I can't tell for the life of me where/what causes the system to reboot. Maybe I am just blind and missing something obvious? I want to understand this because I may want to ensure that some additional steps complete before it reboots. EDIT 2: Soooo it looks like I'm a fool, nothing caused it to restart, because it didn't restart... I must have rebooted it myself and forgotten about it, because I just re-flashed the SD card, did it again, and it only booted once. Lol. At any rate, I will still ask just in case: is there any situation where it will reboot after the first boot ?
  18. Hello, It seems a few weeks ago linux-headers-3.4.113-sun8i package was removed from armbian repo. Is it persistent? How I can get it? Thank you. -- BR Oleg
  19. 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??
  20. 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: https://forum.armbian.com/topic/445-debian-images-cubietruck-vga-output-problem/
  21. 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 cpufreq@vger.kernel.org, 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?
  22. Recently upgraded kernel from 5.7 to 5.8.6-sunxi Unfortunately, got few kernel panics today. How to rollback to previous?
  23. Do ourselves a favor and add a mark to the TV-Boxes forums that states that those "boards" are mostly community supported ONLY.
  24. 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??
  25. 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.