Search the Community

Good afternoon, I run Armbian bullseye on my orangepi zeroplus2-h3. My wifi hotspot causes the OS to reboot sometimes, with the error "xradio WSM-ERR: bh error!>>> 0x0012 (16)" I use the NetworkManager conf files below for my wifi hotspot. echo """ [connection] id=mywifi uuid=58356325-7da4-4d1d-ad6b-54f33bfee335 type=wifi autoconnect=false interface-name=wlan0 permissions= [wifi] band=bg mac-address-blacklist= mode=ap ssid=IQLINK-1 [wifi-security] key-mgmt=wpa-psk psk=123456789 [ipv4] address1=192.168.43.1/24 dns-priority=2 dns-search= method=shared route-metric=2 [ipv6] addr-gen-mode=stable-privacy dns-priority=2 dns-search= method=auto route-metric=2 """ > /etc/NetworkManager/system-connections/mywifi.nmconnection echo """[main] dns=default rc-manager=file plugins=ifupdown,keyfile [ifupdown] managed=true [device] match-device=driver:wlan0 wifi.scan-rand-mac-address=no """ > /etc/NetworkManager/NetworkManager.conf I get the syslog error below and the OS reboot : Feb 2 13:17:37 myhostname kernel: [ 2583.698290] xradio WSM-ERR: bh error!>>> 0x0006 (12) Feb 2 13:17:37 myhostname kernel: [ 2583.698301] ------------[ cut here ]------------ Feb 2 13:17:37 myhostname kernel: [ 2583.698307] WARNING: CPU: 1 PID: 996 at drivers/net/wireless/xradio/ap.c:645 xradio_bss_info_changed+0x72f/0xb04 [xradio_wlan] Feb 2 13:17:37 myhostname kernel: [ 2583.698376] Modules linked in: binfmt_misc nft_chain_nat xt_MASQUERADE xt_state xt_conntrack ipt_REJECT nf_reject_ipv4 nft_counter xt_tcpudp nft_compat nf_tables nfnetlink nf_nat_h323 nf_conntrack_h323 nf_nat_pptp nf_conntrack_pptp nf_nat_tftp nf_conntrack_tftp nf_nat_sip nf_conntrack_sip nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 option usb_wwan qmi_wwan usbserial cdc_wdm lz4hc lz4 zram xradio_wlan mac80211 smsc cfg80211 nls_iso8859_1 sun4i_gpadc_iio industrialio smsc95xx cdc_acm usbnet sun8i_thermal rfkill libarc4 uio_pdrv_genirq uio cpufreq_dt usb_f_acm u_serial g_serial libcomposite ip_tables x_tables autofs4 pwrseq_simple sunxi phy_generic Feb 2 13:17:37 myhostname kernel: [ 2583.698679] CPU: 1 PID: 996 Comm: wpa_supplicant Tainted: G W 5.15.89-sunxi #trunk Feb 2 13:17:37 myhostname kernel: [ 2583.698694] Hardware name: Allwinner sun8i Family Feb 2 13:17:37 myhostname kernel: [ 2583.698708] [<c010cd21>] (unwind_backtrace) from [<c01095f5>] (show_stack+0x11/0x14) Feb 2 13:17:37 myhostname kernel: [ 2583.698737] [<c01095f5>] (show_stack) from [<c09e10b5>] (dump_stack_lvl+0x2b/0x34) Feb 2 13:17:37 myhostname kernel: [ 2583.698766] [<c09e10b5>] (dump_stack_lvl) from [<c011c439>] (__warn+0xad/0xc0) Feb 2 13:17:37 myhostname kernel: [ 2583.698792] [<c011c439>] (__warn) from [<c09dada7>] (warn_slowpath_fmt+0x43/0x7c) Feb 2 13:17:37 myhostname kernel: [ 2583.698813] [<c09dada7>] (warn_slowpath_fmt) from [<bf9d6f47>] (xradio_bss_info_changed+0x72f/0xb04 [xradio_wlan]) Feb 2 13:17:37 myhostname kernel: [ 2583.698873] [<bf9d6f47>] (xradio_bss_info_changed [xradio_wlan]) from [<bf940a79>] (ieee80211_bss_info_change_notify+0x79/0x174 [mac80211]) Feb 2 13:17:37 myhostname kernel: [ 2583.699288] [<bf940a79>] (ieee80211_bss_info_change_notify [mac80211]) from [<bf952fd3>] (ieee80211_do_open+0x19f/0x5e8 [mac80211]) Feb 2 13:17:37 myhostname kernel: [ 2583.699678] [<bf952fd3>] (ieee80211_do_open [mac80211]) from [<bf9535bf>] (ieee80211_if_change_type+0x147/0x254 [mac80211]) Feb 2 13:17:37 myhostname kernel: [ 2583.700058] [<bf9535bf>] (ieee80211_if_change_type [mac80211]) from [<bf959373>] (ieee80211_change_iface+0x23/0x19c [mac80211]) Feb 2 13:17:37 myhostname kernel: [ 2583.700441] [<bf959373>] (ieee80211_change_iface [mac80211]) from [<bf8c3ff7>] (cfg80211_change_iface+0x107/0x2e4 [cfg80211]) Feb 2 13:17:37 myhostname kernel: [ 2583.701188] [<bf8c3ff7>] (cfg80211_change_iface [cfg80211]) from [<bf8e28cd>] (nl80211_set_interface+0xc9/0x164 [cfg80211]) Feb 2 13:17:37 myhostname kernel: [ 2583.701568] [<bf8e28cd>] (nl80211_set_interface [cfg80211]) from [<c08d9555>] (genl_rcv_msg+0x125/0x27c) Feb 2 13:17:37 myhostname kernel: [ 2583.701761] [<c08d9555>] (genl_rcv_msg) from [<c08d899d>] (netlink_rcv_skb+0x81/0xb4) Feb 2 13:17:37 myhostname kernel: [ 2583.701781] [<c08d899d>] (netlink_rcv_skb) from [<c08d8f9d>] (genl_rcv+0x21/0x30) Feb 2 13:17:37 myhostname kernel: [ 2583.701799] [<c08d8f9d>] (genl_rcv) from [<c08d8301>] (netlink_unicast+0x125/0x1a4) Feb 2 13:17:37 myhostname kernel: [ 2583.701816] [<c08d8301>] (netlink_unicast) from [<c08d851b>] (netlink_sendmsg+0x19b/0x36c) Feb 2 13:17:37 myhostname kernel: [ 2583.701834] [<c08d851b>] (netlink_sendmsg) from [<c08601ef>] (sock_sendmsg+0x23/0x2c) Feb 2 13:17:37 myhostname kernel: [ 2583.701858] [<c08601ef>] (sock_sendmsg) from [<c0860495>] (____sys_sendmsg+0x181/0x194) Feb 2 13:17:37 myhostname kernel: [ 2583.701877] [<c0860495>] (____sys_sendmsg) from [<c08615e5>] (___sys_sendmsg+0x49/0x64) Feb 2 13:17:37 myhostname kernel: [ 2583.701898] [<c08615e5>] (___sys_sendmsg) from [<c08618a7>] (__sys_sendmsg+0x37/0x58) Feb 2 13:17:37 myhostname kernel: [ 2583.701918] [<c08618a7>] (__sys_sendmsg) from [<c0100061>] (ret_fast_syscall+0x1/0x52) Feb 2 13:17:37 myhostname kernel: [ 2583.701939] Exception stack(0xcfdedfa8 to 0xcfdedff0) Feb 2 13:17:37 myhostname kernel: [ 2583.701954] dfa0: 01d9d868 01da4288 00000006 beb3f7c8 00000000 00000000 Feb 2 13:17:37 myhostname kernel: [ 2583.701968] dfc0: 01d9d868 01da4288 b6f651f0 00000128 b6f46000 00000001 00000004 01db6c68 Feb 2 13:17:37 myhostname kernel: [ 2583.701977] dfe0: 00000128 beb3f778 b6b5765f b6ad07e6 Feb 2 13:17:37 myhostname kernel: [ 2583.702054] ---[ end trace e554f90c3b6dcdf3 ]--- Feb 2 13:17:37 myhostname kernel: [ 2583.702077] xradio WSM-ERR: bh error!>>> 0x0012 (16) Feb 2 13:17:37 myhostname kernel: [ 2583.702087] xradio STA-ERR: wsm_set_tx_queue_params failed! Feb 2 13:17:37 myhostname kernel: [ 2583.702093] xradio WSM-ERR: bh error!>>> 0x0012 (16) Feb 2 13:17:37 myhostname kernel: [ 2583.702100] xradio STA-ERR: wsm_set_tx_queue_params failed! Feb 2 13:17:37 myhostname kernel: [ 2583.702106] xradio WSM-ERR: bh error!>>> 0x0012 (16) Feb 2 13:17:37 myhostname kernel: [ 2583.702112] xradio STA-ERR: wsm_set_tx_queue_params failed! Feb 2 13:17:37 myhostname kernel: [ 2583.702117] xradio WSM-ERR: bh error!>>> 0x0012 (16) Feb 2 13:17:37 myhostname kernel: [ 2583.702124] xradio STA-ERR: wsm_set_tx_queue_params failed! Feb 2 13:17:39 myhostname systemd[1]: systemd-rfkill.service: Succeeded. Thanks for your help. Clouvis

Since volatile journald logging is done in-memory in /run/log/journal, and made persistent in /var/log.hdd/journal, the rsync of /var/log/journal in nand-sata-install no longer works because it is a symlink to /var/log.hdd/journal in the live system, and will create a circular symlink when booting from NAND. On the target image /var/log is the folder that is directory-mounted to /var/log.hdd during boot. I propose to exclude /var/log from the rsync, and rsync /var/log.hdd to /var/log on the target image. Another solution could be to exclude only /var/log/journal from the rsync, and create an empty /var/log/journal in the target image. Kind regards, Dennis

I have been following a project on git hub and none of the commands work like the project as I have Armbian Focal installed. I need Armbian Bionic with Linux opiz2b 4.19.57-sunxi #5.90 SMP or 4.19.127-sunxi. I realise this is from 2019 and may be too old now to do anything with it. Is it possible to still get this? I can only find minimal versions in the archives that are much newer than this. I have to state here that I am a complete novice at this and so really have no idea what I am doing.

Hello, I am not able to get the keyboard working. I have tried the downloads and compiling my own images. Bulleye is the only thing I can get to compile. There are error massages if I try to compile anything other than Bulleye.

Dear all, I occasionally have a full /var/log at startup on various boards, probably because the logs are not rotated /vaccuumd at boot (we had a thread about this in the old opi1 forum). The rotating /vaccuum is currently done every 15 minutes, so I figured why not do it directly at boot as well? For this purpose I updated /etc/cron.d/armbian-truncate-logs with an extra @reboot line: PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin */15 * * * * root /usr/lib/armbian/armbian-truncate-logs @reboot root /usr/lib/armbian/armbian-truncate-logs I rebooted several times, and didn't get a full /var/log anymore. All subsequent problems like failing networking when filesystem full also vanished;-) Kind regards, Dennis

Good day Armbian Forums! I'm having some trouble with builds of Armbian (up to and including 21.08.6 | kernel 5.10.60-sunxi) seeing wireless access points that are configured to channels 12 & 13 on my Orange Pi Zero Plus2 boards (H3 + 256mb RAM). Specifically, the default Android image (a generic Chinese-language Android multimedia system) that's loaded onto these boards can see and connect to access points that have been set to all channels (1-13) successfully, but any Armbian image I have tried fails to see anything (and subsequently cannot connect) to routers on channels 12 & 13. Due to the nature of this, I believe it may be a region setting or driver I'm missing here. Additionally, in my region (Australia) channels 12 & 13 are allowed, and routers routinely use them. With REGDOMAIN=AU set in /etc/default/crda (and system rebooted), running iw reg get reports country AU set correctly; then running iwlist wlan0 channel reports channels 1-13 are listed, which should be what we want. But then, if I run nmcli dev wifi, or iwlist wlan0 scan | grep SSID, or even use armbian-config's wifi utility, I do not see any routers set to channels 12 & 13. Manually connecting to the SSID via nmcli also fails - it just does not see any routers. Changing these routers to channel 11 and below, they appear with all three commands, and can be connected to successfully. What I have found: Wi-Fi chip is reported to be: "Broadcom BCM43438 combo and Bluetooth Low Energy" wifi (brcmfmac), 70:4A:0E:6C:0C:7C, hw, mtu 1500 If I cd to /usr/lib/firmware/brcm and run ls | grep 43438, a bcm43438-sdio.hcd file is there. Running dmesg | grep brcm command reports the following: root@orangepizeroplus2-h3:/home/julian# dmesg | grep brcm [ 8.368914] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1 [ 8.413375] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.xunlong,orangepi-zero-plus2-h3.txt failed with error -2 [ 8.413395] brcmfmac mmc1:0001:1: Falling back to sysfs fallback for: brcm/brcmfmac43430-sdio.xunlong,orangepi-zero-plus2-h3.txt [ 9.060813] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1 [ 9.101374] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available [ 9.107035] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Mar 30 2016 11:30:56 version 7.45.77.h8.4 FWID 01-ee8a6268 The above tells me that there's an issue with the driver and clm_blob [9.101374] and as such we may have limited channels available (and I'm hoping if that's the issue, it's fixable) - However, I have read elsewhere that perhaps the clm_blob is contained within the driver already and to ignore that message (telling us what we're experiencing). And, if that is case, is there a configuration file I'm missing to 'unlock' these channels? Research tells me it's either the driver or a misconfiguration. Unfortunately, due to the nature of their use (embedded applications in environments where higher channels may be required), requiring the end user to change their Wi-Fi channel is not a feasible option. Many thanks for your help!

Before this I used to connect my APM 2.8.4 Flight controller to a Raspberry PI on Ground, Pin 8 and Pin 10. Today I tried to connect it to my orange pi zero plus2 H3. Pin 9, Pin 8 and Pin 10. On armbian-config toggle UART2. When i tried to connect to it using cat /dev/ttyS2 nothing came out. Once a while sent out some gibberish. I set the correct buadrate at 57600 and 91600 to no available. But I know the settings are correct because when I connect using USB through /dev/ttyACM0 it works. I tried ttyS1 and ttyS3 nothing came out of it. On Raspberry I had done this many times just by turning on the Serial Connection using raspi-config. Anyone have any solution for this?

I am operating a headless data acquisition system with Orange Pi Zero Plus2. In the readings I collect among others data from a discrete separate 18B20 sensor and record the H3 CPU temperature. The 18B20 reading comes from the w1 kernel routine, the CPU temp is provided by armbian OS. With the new OS 5.8.16 I see a strange effect: reading .... the external sensor at /sys/bus/w1/devices/<sensID>/temperature and the CPU temperature at /etc/armbianmonitor/datasources/@soctemp it gives the same reading correct to a 1/100 degree. Even when the system runs low power - this cannot be true. I have no idea how these results can be mixed in the system. Reading the w1 result with checksum in 2 lines is identical to the result above. So I guess something is wrong with the armbian SocTemp reading even though it could be correct within a couple of degrees. Apart from the readings the Orange Pi Zero board operates fine without major problems. Any suggestions ?

After recent upgrade of Debian Buster stable on Orange Pi Zero Plus 2 leds entries disappeared from class directory: Could anybody provide some guidance on how to get them back?

Hello, Im trying to get 2 Uarts working on an Orange Pi Zero+2. Im using armbian Buster image for OPiZ+2 Linux orangepizeroplus2-h3 5.4.43-sunxi #20.05.2 SMP Mon Jun 1 18:26:22 CEST 2020 armv7l GNU/Linux I added UART1, UART2 and UART3 to armbianEnv.txt and was able to read / write on ttyS2 on pins 8 (PA00) and 10 (PA01). But couldnt find which pins ttyS1 or ttyS3 are on. I read at that UART 3 should be Tx PA13 Pin 24 Rx PA14 Pin 23 Is anyone able to suggest which pins I can use for a 2nd UART and is there a file I can look in to find the configuration for the UART Overlays ? Thanks Chris ______________________ Sorry, my mistake with wiring. ttyS3 does work on Tx PA13 Pin 24 Rx PA14 Pin 23 So armbian UART overlays working as required.

I'm trying to set up an OPi Zero Plus 2 with Armbian Buster. As the board has no soldered USB connectors and mine is still in the mail, I was forced to do all this via the serial console via the three pins on the board. (So no nano or nmtui or anything that has an interface.) I run into a problem where a) I couldn't join my WiFi network and b) NetworkManager refused to believe I don't want to use IPv6. So I had to disable NetworkManager and go the wpa_supplicant route. So now I'm in the position that I got everything to work BUT I have to *manually* enable wpa_supplicant and then issue ifdown and ifup - all via the serial console - at every boot before it works. Basically I have to do this at *every* boot: > login as user # sudo su # wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf # ifdown wlan0 # ifup wlan0 After that I have a working IPv4 address and everything works, I can use ssh to connect to the OPi and it connects to the internet like it should (can 'apt update' etc.) The thing is, I REALLY don't want to keep it connected to another computer 24/7 and issue those commands every time it reboots. systemctl: https://pastebin.com/y8tk0DaN At this point, what should've been a 5min job (install armbian on the eMMC on the board) have turned into a 4h+ series of problems after problems after problems. I have followed some eight tutorials and advice that I've found on the subject and NONE of them have worked fully. Some at all. If I had the USB port, I'd most probably just re-flash the SD and start over and keep network manager and deal with whatever that comes with (I don't like NM, it gets in the way FAR too often if you want to manually do something), but I don't and it's impossible to use nmtui via the serial console. And it more or less works right now, only it doesn't start fine at reboot. There must be some easy way to get this to work from this point onward, right? ps. I can't paste armbianmonitor -U anywhere as it exceeds all limits on every paste site I have tried. EDIT: Managed to get armbianmonitor -u working, my bad for forgetting to "sudo" it. sorry.

Hello, I have a OrangePi Zero+2 board and I am using i2c ports for connect several devices. Some i2c works OK. But I requiere r-i2c port. But the port does not work I have spend several days trying to make it works. Please, Can somebody help me?. This is turning into a headache. Thanks in advance.

I installed Armbian_5.75_Orangepizeroplus2-h3_Debian_stretch_next_4.19.20. But it can't boot up. These image can boot up. Armbian_5.65_Orangepizeroplus2-h3_Debian_stretch_next_4.14.78 Armbian_5.69_Orangepizeroplus2-h3_Debian_stretch_next_4.19.13

Hi im using Orange Pi Zero +2 H3 with the current armbian image. 4.19 y i think... basically Im using HDMI out but i want to use the analog audio pins on my project. However the pins seem to be disabled and there doesnt appear any way to enable them. alsamixer only shows the allwinner,HDMI but no controls... Pulse audio panel seems less than helpfulp, lists Analogoutput but doesnt actually send any sound out through the pins. I warn you im not a linux power user. I can just about get around terminal but I dont know where files are off by heart or know exactly what and where to edit. So maybe a little hand holding :) Reading the forums a little people talk about editing a audio.conf file but having a look in the location they mention, no such file exists. if anyone knows this issue and a sure fire way to fix it please let me know :) Thanks Mangy_Dog

Hello, I just use the Zero Plus 2 H3 with extension, using Armbian 5.83 but failed to get the combo to play the sound I use the command aplay -l but return no sound card found How to install driver for sound in this board?

I'm trying to use PA18/PA19 for custom purposes. I need to put these pins to Input state without any pullups/pulldowns. What I can achieve is: to put these pins to input state via the command: gpio mode 30 in gpio mode 31 in ("tri" instead of "in" does not work, it accepts the command, but a multimeter shows the input is still high, as well as gpio readall) These pins are probably pulled high because they are I2C pins. I want to disable the I2C functionality but have not found any means to do so. I have tried this dts script: ##### /dts-v1/; / { compatible = "allwinner,sun8i-h3","allwinner,sun50i-h5","friendlyarm,nanopi-neo2"; fragment@0 { target-path = "/soc/pinctrl@1c20800"; __overlay__ { i2c1 { function = "gpio_in"; bias-high-impedance; }; }; }; }; ###### and had a look at the device tree after a reboot: dtc -I fs -O dts -o ./extracted.dts /proc/device-tree The values got inserted right, but pin behaviour did not change. What I also cannot do is to activate pulldown on those pins. It has no effect. Also tried a python library - https://github.com/duxingkei33/orangepi_PC_gpio_pyH3 - to no avail. Board is an Orange Pi Zero +2 with H3 processor. To sum it up: Input mode is working (with pullup still activated) Pulldown is not working Deactivating Pullup is not working Setting Pin to output mode and switching high/low is working Kernel: 4.19.38-sunxi

Hello! Is there any way to config the frequency used by the DRAM driver when throttling takes place, or even better, disable the DRAM throttling at all? First of all, I have to say that that I'm pushing my Orange Pi Zero H3 board to run at very hot temperatures due to my CPU throttling settings so I can play some retro arcade games (I know I may burn it). But it seems the DRAM driver has its own throttling settings, and it takes place reducing DRAM frequency to 132Mhz. At such DRAM frequency there is flickering at HDMI output. May 13 18:30:31 inova-casa kernel: [15484.645810] [hotplug]: cpu(0) try to kill cpu(2) May 13 18:30:31 inova-casa kernel: [15484.645873] [hotplug]: cpu2 is killed! . May 13 18:30:31 inova-casa kernel: [15484.647486] [ddrfreq] DDR: 408000KHz->132000KHz start May 13 18:30:31 inova-casa kernel: [15484.647500] [ddrfreq] current cpu is cpu0 May 13 18:30:31 inova-casa kernel: [15484.648753] [ddrfreq] elapsed: 1087us May 13 18:30:31 inova-casa kernel: [15484.648773] [ddrfreq] DDR: 408000KHz->132000KHz ok! Unfortunately, manually setting the DRAM frequency don't work either. I mean, when I send the command, the frequency don't change. sudo echo 480000 >/sys/devices/platform/sunxi-ddrfreq/devfreq/sunxi-ddrfreq/cur_freq

Hello... I've got an Orange Pi Zero Plus 2 H3 with Armbian Stretch. Kernel: 4.14.70-sunxi armbianEnv.txt: I did: cp -a /lib/firmware/ap6212/fw_bcm43438a1.bin /lib/firmware/brcm/brcmfmac43430-sdio.bin dmesg when searching for "brcm" gives me: [ 8.123186] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43430-sdio.bin for chip 0x00a9a6(43430) rev 0x000001 [ 8.256708] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Oct 8 2016 15:31:47 version 7.46.57.4.ap.r4 (A1 Station/P2P) FWID 01-3621395e es6.c5.n4.a3 In /etc/default/ap6212 I have: PORT=ttyS1 But the script /etc/init.d/ap6212-bluetooth is failing... with the error "Initialization timed out." Is there any "how-to" for the Orange Pi Zero Plus 2 to get Bluetooth working?

I am trying to get composite video fully working on an Orange Pi Zero Plus 2. I installed the legacy kernel image, and I've been able to turn on composite out, but I just get a blank screen on boot and there is no /dev/fb0. Is there anything else I have to do to enable the framebuffer. This is the (I believe) relevant portions of the script.fex file: [boot_disp] advert_disp = 0 auto_hpd = 1 output_type = 4 hdmi_channel = 0 hdmi_mode = 4 cvbs_channel = 1 cvbs_mode = 11 output_full = 1 hdmi_mode_check = 1 [disp_init] disp_init = 1 disp_mode = 1 screen0_output_type = 3 screen0_output_mode = 5 screen1_output_type = 2 screen1_output_mode = 14 fb0_framebuffer_num = 2 fb0_format = 10 fb0_pixel_sequence = 0 fb0_scaler_mode_enable = 1 fb1_framebuffer_num = 2 fb1_format = 10 fb1_pixel_sequence = 0 fb1_scaler_mode_enable = 1 [hdmi_para] hdmi_used = 0 hdpc_enable = 0 [tv_para] tv_used = 1 tv_dac_used = 1 tv_dac_src0 = 0 these are some possible relevant lines from boot. [ 0.000000] Kernel command line: root=UUID=ab03f9a3-0ba3-4236-8857-33f3229b7a85 rootwait rootfstype=ext4 console=ttyS0,115200 console=tty1 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 monitor=composite-ntsc panic=10 consoleblank=0 loglevel=1 ubootpart=75ceecdb-01 ubootsource=mmc usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cma=96M cgroup_enable=memory swapaccount=1 [ 0.614087] [DISP]disp_module_init [ 0.614413] cmdline,init_disp= [ 0.614448] cmdline,disp= [ 0.615200] [DISP]disp_module_init finish [ 1.029299] cmdline,disp= [ 1.029629] [DISP] disp_init_tv,line:539:screen 0 do not support TV TYPE! [ 1.029647] [DISP] bsp_disp_tv_register,line:998:'ptv is null [ 1.029710] [DISP] disp_device_attached_and_enable,line:159:attched ok, mgr1<-->device1, type=2, mode=14

I have changed to 1080p and its almost stable but pull up any window that has maybe moderate workload to say heavy such a chromium the screen starts bouncing around. Think you know what I mean by bouncy, stuttery flashy. I thought that would just be fbturbo drivers and just the fex script but nope and a bit stuck. There is an image for Xenial as using the legacy version on the OrangePi site that is rock solid @ 1080p so it must be fixable but not sure what. Jan 2019 of xenial. I ran into some permission errors with NodeJS & PM2 so thought I would give Armbian another go as first image I tried was the latest less stable Bionic/Stretch which also at 1080p are like watching a box of frogs. fbturbo, X11 settings and fex script all seem OK anyone any pointers?

I have noticed a very weird problem: connection works for some time (several hours or sometimes days) and then stops. Once it stopped working (connection between my mobile app and OrangePi) I have checked on the board: - ping 8.8.8.8 - OK - ping (router IP) - OK - ping (broadcast ) - FAILED - ping (PC or any other device connected to the network) - FAILED In all cases, Wireshark captures the ping requests. Once I tried to ping OrangePi board from my PC, I see in&out ping packet on OPI board by Wireshark. It seems like some lower layer or router (the same on two different) blocks the outgoing connection. Ideas? (WiFi power management off, no firewall) What helps: - turn on/off wifi adapter. What I have noticed - route -n shows one additional entry: 192.168.31.0 0.0.0.0 255.255.255.0 U ... when the outgoing connection works. So it seems that somehow my IP routing table changed How? Diagnosis information is here(armbianmonitor returns that it cannot be uploaded due to network issues, but it worked): http://ix.io/1DEO (Network/firewall problem detected. Not able to upload debug info.)

Hi! SBC : OrangePi Zero 2 + (H3) Distro: ARMBIAN 5.76 stable Debian GNU/Linux 9 (stretch) 4.19.21-sunxi First when I ran : sudo armbianmonitor -u reply is : System diagnosis information will now be uploaded to Please post the URL in the forum where you've been asked for. Now my problem: I am using Armbian for quite a time and it is wonderful. I am trying to connect a waveshare clone 7 inch lcd with a 800x480 resolution, as the EDID information which lcd provides is broken, I have to force EDID firmware for 800x480 which is already available in the /lib/firmware/edid directory , previously it was working in mainline kernel , but now it refuse to load the same as I upgraded to stretch 4.19.21. /boot/armbianEnv.txt: verbosity=1 logo=disabled console=both edid=0 disp_mode=800x480 extraargs=drm.edid_firmware=edid/800x480.bin overlay_prefix=sun8i-h3 overlays=analog-codec usbhost2 usbhost3 rootdev=UUID=b0cad4ec-9479-4799-9d45-6ca4d9b3da22 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068: dmesg : 1.895908] platform HDMI-A-1: Direct firmware load for edid/800x480.bin failed with error -2 [ 1.895916] platform HDMI-A-1: Falling back to syfs fallback for: edid/800x480.bin [ 62.458285] [drm:drm_load_edid_firmware] *ERROR* Requesting EDID firmware "edid/800x480.bin" failed (err=-11) [ 63.867927] platform HDMI-A-1: Direct firmware load for edid/800x480.bin failed with error -2 [ 63.867943] platform HDMI-A-1: Falling back to syfs fallback for: edid/800x480.bin [ 64.141303] [drm:drm_load_edid_firmware] *ERROR* Requesting EDID firmware "edid/800x480.bin" failed (err=-11) if I change the /boot/armbianEnv.txt file as under extraargs=drm.edid_firmware=edid/800x480.bin to extraargs=drm.edid_firmware=edid/800x600.bin dmesg: [ 1.893325] [drm] Got built-in EDID base block and 0 extensions from "edid/800x600.bin" for connector "HDMI-A-1" [ 3.194872] [drm] Got built-in EDID base block and 0 extensions from "edid/800x600.bin" for connector "HDMI-A-1" it works for 800x600 resolution , so maybe kernel is loading 800x600.bin but not 800x480.bin. Kindly suggest me a solution. Best regards

Issue found! Orange PI changed eMMC from KLM8G1GETF to KLM8G1WEPD. The difference is eMMC 5.0 vs 5.1 and maybe more. The key things is that Armbian (checked using 5.35 and the latest one) does not see this memory (fdisk -l)!! I have noticed it on OPI0 Plus 2 H3. PCB boards are the same, only memory model no. difference. Someone solved it or noticed the same? Confused 🤨

I have perfectly equal Orange Pi Zero Plus 2 H3 boards in their original case - booting from eMMC. Test conditions are: WiFi Hotspot enabled, HDMI off, CPU idle, CPU governor: performance, CPU freq. 240MHz - 1.1 GHz, kernel 4.14.84 Xiaomi Mi5 Charger as psu, 2.4A usb cable armbianmonitor gives me a temp of ~50°C on one board (idle@1.1GHz) and a temp of 65°C on the other board (same conditions, CPU starts throttling here to ~960 MHz). The temp gets so high, that after an apt-get update/upgrade and reboot the opizero plus2 would not boot with an error msg that the temp is too high. The temp seems to be correct more or less, since also the power consumption is significantly higher. While the 50°C board draws ~1.5W, the 65°C board draws ~1.8W. I have no explanation for this...

Can anyone suggest a command line command that would return the status of the connected HDMI monitor? Whether it is on standby or not or something that might help to determine if the display is active or not. I'm currently using Armbian Xenial on a H3 Orange Pi Zero Plus 2. Thanks