Jump to content

Search the Community

Showing results for tags 'orangepiplus2e'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Community
    • Announcements
    • Feature Requests
  • Using Armbian
    • Beginners
    • Advanced users - Development
  • Upcoming Hardware (WIP)
    • News
    • Odroid M1
    • ROCK Pi 5B
  • Maintained Hardware
    • Board does not start
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Unmaintained (CSC/EOL/TVB) / Other
    • TV boxes
    • Off-topic
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families

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


Discord


Location


Interests

  1. Hello! I run Armbian (just updated to version 21) from an 128GByte heavy duty SD card. I am just trying to setup searx (https://github.com/searx/searx) which is using Docker containers. One of the Docker containers won't start, throwing an error message: I searched for long, trying to find some possible solution for this issue. The most fitting seemd to be, where someone said: Yes, it's for another OS and hardware, but I found no other possible solution. So disabling apparmor through a kernel parameter, is what I am trying to achieve. I addded 'apparmor=0' to the bootenv, using armbian-config. I also updated the bootloader using armbian-config (is this necessary after updating env at all?). But: it does not work. dmesg shows the command line as: No 'apparmor=0' in there. And the initial problem with Docker remains. Can you help me please, I don't know how to go on from here .. Thanks! Edit: Btw, there was another issue which seemed to have resolved by itself, but maybe it's important: I did a dist-upgrade from 20 to 21 before. Then I rebooted and installed docker.io and docker-compose - but the docker-compose installation broke with an error, because zram/var/log was full at 49MByte used to 100%. I then uninstalled both, rebooted again, and then installed both packages again, which for some reason worked on the 2nd try ... but now I have noticed that zram/var/log is full most of the time (with no further errors so far..) Is this all right?
  2. Remark: on my Orange Pi PC and Orange Pi Plus 2e - everything is OK. Problem occurred on Orange Pi Plus 2 and Orange Pi Zero After upgrading to: [root@PKTEST ~]# uname -a Linux PKTEST 5.10.4-sunxi #20.11.6 SMP Sun Jan 3 21:28:45 CET 2021 armv7l GNU/Linux My "headless" Orange Pi Plus 2 "disappeared from network. I switch it off and connected via serial. I was able to login. Device runs successfully, it is assigning IP to network interface (static assignment) but... there is no connectivity at all (both egress and ingress). [root@PKTEST ~]# ifconfig enx0281cbcd0fcf: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.10.250 netmask 255.255.255.0 broadcast 192.168.10.255 inet6 fe80::81:cbff:fecd:fcf prefixlen 64 scopeid 0x20<link> ether 02:81:cb:cd:0f:cf txqueuelen 1000 (Ethernet) RX packets 71 bytes 4397 (4.2 KiB) RX errors 0 dropped 38 overruns 0 frame 0 TX packets 44 bytes 2484 (2.4 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 41 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 80 bytes 12802 (12.5 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 80 bytes 12802 (12.5 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 [root@PKTEST ~]# ping localhost PING localhost(localhost (::1)) 56 data bytes 64 bytes from localhost (::1): icmp_seq=1 ttl=64 time=0.129 ms 64 bytes from localhost (::1): icmp_seq=2 ttl=64 time=0.166 ms 64 bytes from localhost (::1): icmp_seq=3 ttl=64 time=0.154 ms ^C --- localhost ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 52ms rtt min/avg/max/mdev = 0.129/0.149/0.166/0.020 ms [root@PKTEST ~]# ping 127.0.0.1 PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data. 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.107 ms ^C --- 127.0.0.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.107/0.107/0.107/0.000 ms [root@PKTEST ~]# ping 192.168.10.1 PING 192.168.10.1 (192.168.10.1) 56(84) bytes of data. From 192.168.10.250 icmp_seq=1 Destination Host Unreachable From 192.168.10.250 icmp_seq=2 Destination Host Unreachable From 192.168.10.250 icmp_seq=3 Destination Host Unreachable ^C --- 192.168.10.1 ping statistics --- 4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 78ms
  3. Last night I downloaded "https://dl.armbian.com/orangepiplus2e/Debian_buster_next.7z" (OPi+2E) ... burned it to SD card and fired up the board ..later installed desktop and other software ...BUT when I was installing MPV I observed that few files with "Vulcan" in their names were also installed...so does that mean that mainline next 4.19.xx images for H3 are now fully suitable for multimedia desktops with Hardware graphics/Video acceleration fully supported ?
  4. Hello everyone. This happens on my OrangePi after a couple of hours of running. I don't think this happened before installing the kernel 4.14. I haven't changed my power supply, which should be working well - custom DC/DC converter connected to GPIO pins. Is anyone else experiencing this? Anything I can do? [19155.760977] INFO: rcu_sched self-detected stall on CPU [19155.760983] INFO: rcu_sched self-detected stall on CPU [19155.760997] INFO: rcu_sched detected stalls on CPUs/tasks: [19155.761010] 2-...: (1 ticks this GP) idle=18a/1/0 softirq=332295/332295 fqs=0 [19155.761017] 0-...: (0 ticks this GP) idle=dbe/1/0 softirq=475103/475103 fqs=0 [19155.761018] [19155.761025] 1-...: (1 GPs behind) idle=f36/1/0 softirq=422883/422884 fqs=0 [19155.761034] 2-...: (1 ticks this GP) idle=18a/1/0 softirq=332295/332295 fqs=0 [19155.761040] rcu_sched kthread starved for 91911 jiffies! g126395 c126394 f0x0 RCU_GP_WAIT_FQS(3) ->state=0x402 ->cpu=3 [19155.761041] [19155.819568] 1-...: (1 GPs behind) idle=f36/1/0 softirq=422883/422884 fqs=0 [19155.826612] (t=91911 jiffies g=126395 c=126394 q=3) [19155.831672] rcu_sched kthread starved for 91911 jiffies! g126395 c126394 f0x0 RCU_GP_WAIT_FQS(3) ->state=0x0 ->cpu=0 [19185.762182] rcu_sched kthread starved for 91911 jiffies! g126395 c126394 f0x0 RCU_GP_WAIT_FQS(3) ->state=0x0 ->cpu=0 [19155.760977] INFO: rcu_sched self-detected stall on CPU [19155.760983] INFO: rcu_sched self-detected stall on CPU [19155.760997] INFO: rcu_sched detected stalls on CPUs/tasks: [19155.761010] 2-...: (1 ticks this GP) idle=18a/1/0 softirq=332295/332295 fqs=0 [19155.761017] 0-...: (0 ticks this GP) idle=dbe/1/0 softirq=475103/475103 fqs=0 [19155.761018] [19155.761025] 1-...: (1 GPs behind) idle=f36/1/0 softirq=422883/422884 fqs=0 [19155.761028] (t=91911 jiffies g=126395 c=126394 q=3) [19155.761034] 2-...: (1 ticks this GP) idle=18a/1/0 softirq=332295/332295 fqs=0 [19155.761040] rcu_sched kthread starved for 91911 jiffies! g126395 c126394 f0x0 RCU_GP_WAIT_FQS(3) ->state=0x402 ->cpu=3 [19155.761041] [19155.761044] rcu_sched I [19155.761048] (detected by 3, t=91911 jiffies, g=126395, c=126394, q=3) [19155.761052] 0 8 2 0x00000000 [19155.761057] Sending NMI from CPU 3 to CPUs 0: [19155.761079] [<c08762b9>] (__schedule) from [<c087682b>] (schedule+0x2f/0x68) [19155.761093] [<c087682b>] (schedule) from [<c087909d>] (schedule_timeout+0x75/0x314) [19155.761108] [<c087909d>] (schedule_timeout) from [<c0164f95>] (rcu_gp_kthread+0x415/0x674) [19155.761123] [<c0164f95>] (rcu_gp_kthread) from [<c0131a9d>] (kthread+0xfd/0x104) [19155.761138] [<c0131a9d>] (kthread) from [<c0106719>] (ret_from_fork+0x11/0x38) [19155.819568] 1-...: (1 GPs behind) idle=f36/1/0 softirq=422883/422884 fqs=0 [19155.826612] (t=91911 jiffies g=126395 c=126394 q=3) [19155.831672] rcu_sched kthread starved for 91911 jiffies! g126395 c126394 f0x0 RCU_GP_WAIT_FQS(3) ->state=0x0 ->cpu=0 [19155.842191] rcu_sched R running task 0 8 2 0x00000000 [19155.842210] [<c08762b9>] (__schedule) from [<c087682b>] (schedule+0x2f/0x68) [19155.842222] [<c087682b>] (schedule) from [<c087909d>] (schedule_timeout+0x75/0x314) [19155.842234] [<c087909d>] (schedule_timeout) from [<c0164f95>] (rcu_gp_kthread+0x415/0x674) [19155.842245] [<c0164f95>] (rcu_gp_kthread) from [<c0131a9d>] (kthread+0xfd/0x104) [19155.842256] [<c0131a9d>] (kthread) from [<c0106719>] (ret_from_fork+0x11/0x38) [19165.761432] Sending NMI from CPU 3 to CPUs 1: [19175.761806] Sending NMI from CPU 3 to CPUs 2: [19185.762182] rcu_sched kthread starved for 91911 jiffies! g126395 c126394 f0x0 RCU_GP_WAIT_FQS(3) ->state=0x0 ->cpu=0 [19185.762186] Sending NMI from CPU 2 to CPUs 0: [19185.772707] rcu_sched R running task 0 8 2 0x00000000 [19185.772726] [<c08762b9>] (__schedule) from [<c087682b>] (schedule+0x2f/0x68) [19185.772738] [<c087682b>] (schedule) from [<c087909d>] (schedule_timeout+0x75/0x314) [19185.772749] [<c087909d>] (schedule_timeout) from [<c0164f95>] (rcu_gp_kthread+0x415/0x674) [19185.772760] [<c0164f95>] (rcu_gp_kthread) from [<c0131a9d>] (kthread+0xfd/0x104) [19185.772772] [<c0131a9d>] (kthread) from [<c0106719>] (ret_from_fork+0x11/0x38) [19195.762559] Sending NMI from CPU 2 to CPUs 1: [19205.762933] NMI backtrace for cpu 2 [19205.762942] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 4.14.14-sunxi #38 [19205.762945] Hardware name: Allwinner sun8i Family [19205.762959] [<c010db15>] (unwind_backtrace) from [<c010a0d9>] (show_stack+0x11/0x14) [19205.762970] [<c010a0d9>] (show_stack) from [<c0867e29>] (dump_stack+0x69/0x78) [19205.762983] [<c0867e29>] (dump_stack) from [<c086bc37>] (nmi_cpu_backtrace+0xd3/0xd4) [19205.762996] [<c086bc37>] (nmi_cpu_backtrace) from [<c086bccf>] (nmi_trigger_cpumask_backtrace+0x97/0xd0) [19205.763008] [<c086bccf>] (nmi_trigger_cpumask_backtrace) from [<c01662a7>] (rcu_dump_cpu_stacks+0x77/0x94) [19205.763019] [<c01662a7>] (rcu_dump_cpu_stacks) from [<c0165a65>] (rcu_check_callbacks+0x4d5/0x690) [19205.763032] [<c0165a65>] (rcu_check_callbacks) from [<c0169f5f>] (update_process_times+0x2b/0x48) [19205.763046] [<c0169f5f>] (update_process_times) from [<c0177d11>] (tick_sched_timer+0x31/0x68) [19205.763057] [<c0177d11>] (tick_sched_timer) from [<c016ac85>] (__hrtimer_run_queues+0xf5/0x224) [19205.763066] [<c016ac85>] (__hrtimer_run_queues) from [<c016af81>] (hrtimer_interrupt+0x81/0x180) [19205.763079] [<c016af81>] (hrtimer_interrupt) from [<c07483a1>] (arch_timer_handler_phys+0x25/0x28) [19205.763093] [<c07483a1>] (arch_timer_handler_phys) from [<c015d52f>] (handle_percpu_devid_irq+0x57/0x19c) [19205.763107] [<c015d52f>] (handle_percpu_devid_irq) from [<c0159a49>] (generic_handle_irq+0x1d/0x28) [19205.763120] [<c0159a49>] (generic_handle_irq) from [<c0159e59>] (__handle_domain_irq+0x45/0x84) [19205.763131] [<c0159e59>] (__handle_domain_irq) from [<c01013b5>] (gic_handle_irq+0x39/0x68) [19205.763141] [<c01013b5>] (gic_handle_irq) from [<c010aa25>] (__irq_svc+0x65/0x94) [19205.763146] Exception stack(0xee523f78 to 0xee523fc0) [19205.763152] 3f60: 00000001 00000000 [19205.763161] 3f80: 00000000 c0116561 ffffe000 c0d03fcc c0d03f6c c0cb6438 c0ddd8eb 00000000 [19205.763170] 3fa0: 00000000 00000000 00087b5d ee523fc8 c01070e7 c01070e8 40000033 ffffffff [19205.763181] [<c010aa25>] (__irq_svc) from [<c01070e8>] (arch_cpu_idle+0x28/0x2c) [19205.763194] [<c01070e8>] (arch_cpu_idle) from [<c014c93d>] (do_idle+0x115/0x16c) [19205.763206] [<c014c93d>] (do_idle) from [<c014cb89>] (cpu_startup_entry+0x19/0x1c) [19205.763216] [<c014cb89>] (cpu_startup_entry) from [<401016f1>] (0x401016f1) [19205.763226] Sending NMI from CPU 1 to CPUs 0: [19215.763599] NMI backtrace for cpu 1 [19215.763605] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.14.14-sunxi #38 [19215.763608] Hardware name: Allwinner sun8i Family [19215.763618] [<c010db15>] (unwind_backtrace) from [<c010a0d9>] (show_stack+0x11/0x14) [19215.763627] [<c010a0d9>] (show_stack) from [<c0867e29>] (dump_stack+0x69/0x78) [19215.763638] [<c0867e29>] (dump_stack) from [<c086bc37>] (nmi_cpu_backtrace+0xd3/0xd4) [19215.763650] [<c086bc37>] (nmi_cpu_backtrace) from [<c086bccf>] (nmi_trigger_cpumask_backtrace+0x97/0xd0) [19215.763661] [<c086bccf>] (nmi_trigger_cpumask_backtrace) from [<c01662a7>] (rcu_dump_cpu_stacks+0x77/0x94) [19215.763672] [<c01662a7>] (rcu_dump_cpu_stacks) from [<c0165a65>] (rcu_check_callbacks+0x4d5/0x690) [19215.763683] [<c0165a65>] (rcu_check_callbacks) from [<c0169f5f>] (update_process_times+0x2b/0x48) [19215.763695] [<c0169f5f>] (update_process_times) from [<c0177d11>] (tick_sched_timer+0x31/0x68) [19215.763705] [<c0177d11>] (tick_sched_timer) from [<c016ac85>] (__hrtimer_run_queues+0xf5/0x224) [19215.763714] [<c016ac85>] (__hrtimer_run_queues) from [<c016af81>] (hrtimer_interrupt+0x81/0x180) [19215.763724] [<c016af81>] (hrtimer_interrupt) from [<c07483a1>] (arch_timer_handler_phys+0x25/0x28) [19215.763735] [<c07483a1>] (arch_timer_handler_phys) from [<c015d52f>] (handle_percpu_devid_irq+0x57/0x19c) [19215.763746] [<c015d52f>] (handle_percpu_devid_irq) from [<c0159a49>] (generic_handle_irq+0x1d/0x28) [19215.763758] [<c0159a49>] (generic_handle_irq) from [<c0159e59>] (__handle_domain_irq+0x45/0x84) [19215.763768] [<c0159e59>] (__handle_domain_irq) from [<c01013b5>] (gic_handle_irq+0x39/0x68) [19215.763777] [<c01013b5>] (gic_handle_irq) from [<c010aa25>] (__irq_svc+0x65/0x94) [19215.763781] Exception stack(0xee521f78 to 0xee521fc0) [19215.763787] 1f60: 00000001 00000000 [19215.763796] 1f80: 00000000 c0116561 ffffe000 c0d03fcc c0d03f6c c0cb6438 c0ddd8eb 00000000 [19215.763805] 1fa0: 00000000 00000000 00000018 ee521fc8 c01070e7 c01070e8 40000033 ffffffff [19215.763815] [<c010aa25>] (__irq_svc) from [<c01070e8>] (arch_cpu_idle+0x28/0x2c) [19215.763826] [<c01070e8>] (arch_cpu_idle) from [<c014c93d>] (do_idle+0x115/0x16c) [19215.763837] [<c014c93d>] (do_idle) from [<c014cb89>] (cpu_startup_entry+0x19/0x1c) [19215.763846] [<c014cb89>] (cpu_startup_entry) from [<401016f1>] (0x401016f1) [19215.763853] Sending NMI from CPU 1 to CPUs 2: [19225.764386] NMI backtrace for cpu 2 [19225.764393] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 4.14.14-sunxi #38 [19225.764395] Hardware name: Allwinner sun8i Family [19225.764399] task: ee4f8000 task.stack: ee522000 [19225.764404] PC is at __do_softirq+0x7a/0x25c [19225.764412] LR is at irq_exit+0x7f/0xc4 [19225.764416] pc : [<c0101462>] lr : [<c011ef33>] psr: 40000133 [19225.764419] sp : ee523ee8 ip : 7fffffff fp : 4000001f [19225.764422] r10: c0d02080 r9 : ee434000 r8 : 00000001 [19225.764426] r7 : ffffe000 r6 : 00000282 r5 : 00000000 r4 : ffffe000 [19225.764430] r3 : 00000080 r2 : 00000000 r1 : c0df6740 r0 : c0df6740 [19225.764435] Flags: nZcv IRQs on FIQs on Mode SVC_32 ISA Thumb Segment none [19225.764439] Control: 50c5387d Table: 56ff006a DAC: 00000051 [19225.764444] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 4.14.14-sunxi #38 [19225.764446] Hardware name: Allwinner sun8i Family [19225.764456] [<c010db15>] (unwind_backtrace) from [<c010a0d9>] (show_stack+0x11/0x14) [19225.764465] [<c010a0d9>] (show_stack) from [<c0867e29>] (dump_stack+0x69/0x78) [19225.764475] [<c0867e29>] (dump_stack) from [<c086bbef>] (nmi_cpu_backtrace+0x8b/0xd4) [19225.764486] [<c086bbef>] (nmi_cpu_backtrace) from [<c010ca01>] (handle_IPI+0x75/0x278) [19225.764495] [<c010ca01>] (handle_IPI) from [<c01013e3>] (gic_handle_irq+0x67/0x68) [19225.764502] [<c01013e3>] (gic_handle_irq) from [<c010aa25>] (__irq_svc+0x65/0x94) [19225.764506] Exception stack(0xee523e98 to 0xee523ee0) [19225.764510] 3e80: c0df6740 c0df6740 [19225.764519] 3ea0: 00000000 00000080 ffffe000 00000000 00000282 ffffe000 00000001 ee434000 [19225.764527] 3ec0: c0d02080 4000001f 7fffffff ee523ee8 c011ef33 c0101462 40000133 ffffffff [19225.764535] [<c010aa25>] (__irq_svc) from [<c0101462>] (__do_softirq+0x7a/0x25c) [19225.764545] [<c0101462>] (__do_softirq) from [<c011ef33>] (irq_exit+0x7f/0xc4) [19225.764557] [<c011ef33>] (irq_exit) from [<c0159e5d>] (__handle_domain_irq+0x49/0x84) [19225.764567] [<c0159e5d>] (__handle_domain_irq) from [<c01013b5>] (gic_handle_irq+0x39/0x68) [19225.764575] [<c01013b5>] (gic_handle_irq) from [<c010aa25>] (__irq_svc+0x65/0x94) [19225.764578] Exception stack(0xee523f78 to 0xee523fc0) [19225.764582] 3f60: 00000001 00000000 [19225.764590] 3f80: 00000000 c0116561 ffffe000 c0d03fcc c0d03f6c c0cb6438 c0ddd8eb 00000000 [19225.764603] 3fa0: 00000000 00000000 00087b5d ee523fc8 c01070e7 c01070e8 40000033 ffffffff [19225.764613] [<c010aa25>] (__irq_svc) from [<c01070e8>] (arch_cpu_idle+0x28/0x2c) [19225.764624] [<c01070e8>] (arch_cpu_idle) from [<c014c93d>] (do_idle+0x115/0x16c) [19225.764642] [<c014c93d>] (do_idle) from [<c014cb89>] (cpu_startup_entry+0x19/0x1c) [19225.764656] [<c014cb89>] (cpu_startup_entry) from [<401016f1>] (0x401016f1)
  5. I have seen many tutorials about connecting real time clock hardware on Orange Pi and Raspberry Pi. What i didn't like was removing of fake-hwclock service, because I want that RTC works when it is connected, and fake-hwclock when RTC is not connected. Therefore, I changed /sbin/fake-hwclock script to work in this way. So, here is how to do this, tested on OrangePi+2E, Armbian Ubuntu legacy kernel: Purchase cheap DS3231 module on eBay (cca. $1) like this one: http://www.ebay.com/itm/DS3231-AT24C32-IIC-Modul-High-Precision-Real-Time-Clock-Module-Arduino-New-/292041844936?hash=item43ff0ce8c8:g:d80AAOSwdGFYtsFP Put battery in module. Shutdown and powerof OPi and connect module: Orange (i2c0 bus) RTC module (DS3231 RTC + 24C32 eeprom) 1 3.3V 2 VCC 3 PA12 (TWI0_SDA/DI_RX/PA_EINT12) 3 SDA 5 PA11 (TWI0_SCK/DI_TX/PA_EINT11) 4 SCL 9 GND 1 GND Power up OPi Install i2c-tools. sudo apt install i2c-tools Type command: i2cdetect -y 0 You should see: 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- 57 -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- 68 -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- This means that module is connected properly and that we have DS3231 on address 0x68 and eeprom 24C32 on address 0x57. Type: sudo echo ds1307 0x68 > /sys/class/i2c-adapter/i2c-0/new_device i2cdetect -y 0 You should see: 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- 57 -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- This means that system is now using our RTC. Also, now should exist new device /dev/rtc1 Be sure that your system time is right, and type: sudo hwclock -w -f /dev/rtc1 Now our RTC must have right time. Check with: sudo hwclock -r -f /dev/rtc1 If everithing was ok, copy /sbin/fake-hwclock to bacup (just in case) sudo cp ~/programming/sh/fake_hwclock/sbin/fake-hwclock /sbin/fake-hwclock Edit /sbin/fake-hwclock and place this code in it: Reboot. Now you should have right system time backed up by RTC.
  6. Hi I trying to return in work OPi+2e board but faced some odd thing. When I trying to boot Armbian I getting temperatures about 180C which leads to shutdown during booting. It reproduceable with all versions from hirsute/5.12.15 back to oldest avaliable bionic/5.4.8 Official Ubuntu xenial/5.3.5 works fine, but /sys/class/thermal/thermal_zone0/temp gives negative readings (like about -76500) Installed on eMMC old RetrOrangePi which is Armbian jessie/3.4.113 also works but gives zero (exactly 0) temp reading. Finger test gives "room temperature" reading and "warm" while old OS works. Definetly not 180C Board itself is from 2017, worked as media player with active cooling so I doubt it was overheated but will not be surprised if it's hardware degradation issue. Anyway, any ideas how to get it working with current Armbian? Personaly I'm fine with wrong temp reading if board works. Tried to add thermal.nocrt=1 with no success, probally did something wrong. buster / 5.10.34 boot log
  7. So, here is the problem: I'm running the latest version of Armbian buster on an Orange PI PC+2E and as you know this piece of crap doesn't even support a proper shutdown function: all what is does is "reboot: system halted" and the screen remains on. Is there a way to turn the screen off (at least) after system halted? maybe a script that runs right before shutdown ? I've reas several discussion but non of the solutions worked
  8. Hello, Is there anyone that has problem with USB keyboard on armbian 20.11.9 buster. I have tried both 20.11.6 and 20.11.9 buster nut the keyboard can't be recognized in armbian. (caplock, numlock LED don't work as well) I tried 4 USB ports on the port but doesn't work. The keyboard is working fine with my Windows PC. Thanks
  9. I just updated my armbian kernel, I did it with: apt-cache search linux-generic to find the images and sudo apt-get install name of the image to install, the new kernel is in the /boot folder but if I restart It continues to start with the old one, and if I eliminate the old one it no longer starts. How do I select the new kernel to boot from it? i use orangepi+2e
  10. In a brainfart i thought the rpi gpio is compatible with most arm boards. so i took one witch i had laying around and i connected the Raspberry pi DVB-T HAT module (TV uHAT). I checked if the SPI bus pins where compatible and with the help of the "Hardware_Allwinner_overlays guide" i created a overlay for the rpi-tv (used the original from the raspberry pi github). to my surprise (after some struggle) it work. // rpi-tv HAT /dts-v1/; /plugin/; / { compatible = "allwinner,sun4i-a10", "allwinner,sun7i-a20", "allwinner,sun8i-h3", "allwinner,sun50i-a64", "allwinner,sun50i-h5"; fragment@0 { target = <&spi0>; __overlay__ { /* needed to avoid dtc warning */ #address-cells = <1>; #size-cells = <0>; status = "okay"; cxd2880@0 { compatible = "sony,cxd2880"; reg = <0>; /* CE0 */ spi-max-frequency = <50000000>; status = "okay"; }; }; }; }; sudo armbian-add-overlay rpi-tv-overlay.dts I quickly install tvheadend and went to watch some TV :p Why i did this because the H3 GPU/CPU has h265 encoding (in the Nederlands tv is transmitted with the h265 1080p 50fps) with the recent Sunxi-cedrus update libav can work with hardware encoding (in theory, i don't know it is fast enough ) But i can not find a proper recent guide the install then, does any one installed the Sunxi-cedrus? And do i have to compile the complete custom kernel to do this? or is this already in the main line? onlything is can find is this: https://linux-sunxi.org/Sunxi-cedrus ref: https://docs.armbian.com/Hardware_Allwinner_overlays/
  11. I'm testing the OrangePi+ and OrangePi+2 for review. I noticed my OPi+ was running a lot cooler than my OPi+2. Reason is difference in kernel. Just tried 5.8.5 on the OPi+ and it also ran as hot as the OPi+2. OPi+ with kernel 4.19.62 vs OPi+/OPi+2 with kernel 5.8.5 No fan idle OPi+ 50C No fan maxed OPi+ Throttle at 75C to 1.3Ghz at 80C to 1.2Ghz doesn't go higher than 80C Fan idle OPi+ 27C Fan maxed OPi+ 54C No fan idle OPi+2 58C No fan maxed OPi+2 Throttle at 80C to 1.3Ghz at 85C lower. Barely reaches 85C / Debian throttle at 75C to 1.3Ghz Fan idle OPi+2 33C Fan maxed OPi+2 60C 2 heatsinks+fan 64C with 1 heatsink+fan See these 2 next to each other. Both without a fan and with a heatsink Here OPi+ with 4.19.62 : http://ix.io/2DeH Here OPi+2 with 5.8.5 : http://ix.io/2DgC 5.8.5 also performs a lot worse in every tasks. Blender with 4.19.62 : 1h36m39s With heatsink + fan no throttle 1.37Ghz Blender with 5.8.5 : 1h49m36s With heatsink + fan no throttle 1.37Ghz Even without fan 4.19.62 does still better while throttling to 1.3Ghz : 1h43m52s But it rarely goes over 80C, while mainline goes easily over 80C and throttles heavily without a fan. Example with SBC-bench, the same task. Same heatsink, no fan. Left 5.8.5 right 4.19.62 I'll keep using 4.19.62 Just wanted to inform about it. Also the available frequencies are very different. I expect voltages will be different too. Focal 5.8.5 and Buster 5.8.5 are not stable for me. With Bionic I did not have stabillity issues with 5.8.5, but it does perform a lot worse than bionic with 4.19.62. Never had a crash with 4.19 for +1 year. Also zram performs almost 2 x better with 4.19.62 Bionic vs 5.8.5 Focal. zram Bionic 4.19.62 1.4 GB/s 0.01 msec vs 5.8.5 zram Armbian Focal 0.87GB/s 0.01 msec zram Armbian Buster 1.0 GB/s 0.01 msec zram Armbian Bionic 1.2 GB/s 0.01 msec All very strange. But I know enough for my video.
  12. Device: Orange Pi +2e. Builds 20.20, 20.05, 20.08 The Armbian Boot Logo is shown only when we boot from SD Card. Do nand-sata-install to eMMC and boot from eMMC, the logo disappears. Could this be a timing issue as it boots faster on eMMC? I do not see any flicker or flash during u-boot. --Rajesh
  13. I installed the image Armbian_20.08.1_Orangepiplus2e_focal_current_5.8.5_desktop.img on my Orange PI Plus 2E and I installed RetroArch to setup a retro gaming board. Everything installed ok but all games even weak games like for Super Nintendo, are running slow and no audio, does anyone here already tried to get RetroArch working on this board? Audio is not working , it uses pulseaudio and it's installed already. I already tested RetrOrange Pi image, it uses Armbian too I guess, most of the games runs at full speed, the reason I am not using is that is a little outdated, some emulators doesn't work and some are missing and I personally prefer using RetroArch directly, no emulationstation or anything.
  14. Hello. I have just acquired an Orange Pi plus 2e. Armbian Xenial is installed on emmc. I wish my SD card to become my /home. Can you help me? Thank you.
  15. I have two Orange PI +2E machines. The first one I got was a while ago so it's running a 3.4.113 kernel (16.04), the more recent one I purchased is running 4.19.13 kernel (18.04) - both are Ubuntu Armbian. I've noticed when I use the "shutdown now" command on the older pi, the board actually powers off but when I use the same command on the newer kernel board, it never powers down. The newer board appears to stop all services and eventually report that the system is halted but it remains in that state. Is there a way to enable it to power off after a "shutdown now" is issued? I'm wondering if this is a kernel difference but it may be something else completely. Thanks, -Greg
  16. I'm getting logspam from RTL871X running buster on my OrangePi Plus 2e. I'm not using wifi on this so I guess I could just disable/blacklist rtl871x to stop this? But is there a better/cleaner way to stop all these log entries? Or does it indicate something is broken/mis-configured? syslog is showing many many log entries from RTL871X; each minute I get the following sequence: May 23 16:52:06 orangepiplus2e kernel: RTL871X: cfg80211_rtw_scan(wlan0) May 23 16:52:06 orangepiplus2e kernel: RTL871X: _rtw_pwr_wakeup call ips_leave.... May 23 16:52:06 orangepiplus2e kernel: RTL871X: ==>ips_leave cnts:112 May 23 16:52:06 orangepiplus2e kernel: RTL871X: ===> rtw_ips_pwr_up.............. May 23 16:52:06 orangepiplus2e kernel: RTL871X: ===> ips_netdrv_open......... May 23 16:52:06 orangepiplus2e kernel: RTL871X: FW does not exist before power on!! May 23 16:52:06 orangepiplus2e kernel: RTL871X: SetHwReg8188F: hci_sus_state=1 May 23 16:52:06 orangepiplus2e kernel: RTL871X: SetHwReg8188F: bMacPwrCtrlOn=1 May 23 16:52:06 orangepiplus2e kernel: RTL871X: SetHwReg8188F: hci_sus_state=2 May 23 16:52:06 orangepiplus2e kernel: RTL871X: PowerOnCheck: val_mix:0x0000063f, res:0x0000063f May 23 16:52:06 orangepiplus2e kernel: RTL871X: PowerOnCheck: 0x100 the result of cmd52 and cmd53 is the same. May 23 16:52:06 orangepiplus2e kernel: RTL871X: PowerOnCheck: 0x1B8 test Pass. May 23 16:52:06 orangepiplus2e kernel: RTL871X: Power on ok! May 23 16:52:06 orangepiplus2e kernel: RTL871X: rtl8188f_FirmwareDownload(wlan0) tmp_ps=3 May 23 16:52:06 orangepiplus2e kernel: RTL871X: rtl8188f_FirmwareDownload fw: FW_NIC, size: 21020 May 23 16:52:06 orangepiplus2e kernel: RTL871X: rtl8188f_FirmwareDownload: fw_ver=4 fw_subver=0000 sig=0x88f1, Month=08, Date=22, Hour=17, Minute=36 May 23 16:52:06 orangepiplus2e kernel: RTL871X: rtl8188f_FirmwareDownload(): Shift for fw header! May 23 16:52:06 orangepiplus2e kernel: RTL871X: rtl8188f_FirmwareDownload by IO write! May 23 16:52:06 orangepiplus2e kernel: RTL871X: polling_fwdl_chksum: Checksum report OK! (1, 0ms), REG_MCUFWDL:0x00050505 May 23 16:52:06 orangepiplus2e kernel: RTL871X: _8051Reset8188: Finish May 23 16:52:06 orangepiplus2e kernel: RTL871X: _FWFreeToGo: Polling FW ready OK! (237, 16ms), REG_MCUFWDL:0x000505c6 May 23 16:52:06 orangepiplus2e kernel: RTL871X: rtl8188f_FirmwareDownload: DLFW OK ! May 23 16:52:06 orangepiplus2e kernel: RTL871X: rtl8188f_FirmwareDownload success. write_fw:1, 236ms May 23 16:52:06 orangepiplus2e kernel: RTL871X: <=== rtl8188f_FirmwareDownload() May 23 16:52:06 orangepiplus2e kernel: RTL871X: HalDetectPwrDownMode(): PDN=0 May 23 16:52:06 orangepiplus2e kernel: RTL871X: Set RF Chip ID to RF_6052 and RF type to 3. May 23 16:52:06 orangepiplus2e kernel: RTL871X: #### hw_var_set_opmode() -4815 iface_type(0) mode = 2 #### May 23 16:52:06 orangepiplus2e kernel: RTL871X: rtw_rf_get_kfree_tx_gain_offset path:0, ch:6, bb_gain_sel:0, kfree_offset:0 May 23 16:52:06 orangepiplus2e kernel: RTL871X: kfree gain_offset 0x55:0x82060 May 23 16:52:06 orangepiplus2e kernel: RTL871X: after :0x2060 May 23 16:52:06 orangepiplus2e kernel: RTL871X: <=== rtw_ips_pwr_up.............. in 728ms May 23 16:52:06 orangepiplus2e kernel: RTL871X: nolinked power save leave May 23 16:52:06 orangepiplus2e kernel: RTL871X: ==> ips_leave.....LED(0x01028282)... May 23 16:52:08 orangepiplus2e kernel: RTL871X: survey done event(35) band:0 for wlan0 May 23 16:52:08 orangepiplus2e kernel: RTL871X: rtw_indicate_scan_done(wlan0) May 23 16:52:08 orangepiplus2e kernel: RTL871X: ==>rtw_ps_processor .fw_state(8) May 23 16:52:08 orangepiplus2e kernel: RTL871X: ==>ips_enter cnts:113 May 23 16:52:08 orangepiplus2e kernel: RTL871X: nolinked power save enter May 23 16:52:08 orangepiplus2e kernel: RTL871X: ===> rtw_ips_pwr_down................... May 23 16:52:08 orangepiplus2e kernel: RTL871X: ====> rtw_ips_dev_unload... May 23 16:52:08 orangepiplus2e kernel: RTL871X: SetHwReg8188F: bMacPwrCtrlOn=0 May 23 16:52:08 orangepiplus2e kernel: RTL871X: SetHwReg8188F: hci_sus_state=3 May 23 16:52:08 orangepiplus2e kernel: RTL871X: SetHwReg8188F: hci_sus_state=0 May 23 16:52:08 orangepiplus2e kernel: RTL871X: <=== rtw_ips_pwr_down..................... in 8ms
  17. Yesterday ubuntu issued updates related to DRM, packages: ii libdrm-amdgpu1:armhf 2.4.99-1ubuntu1~18.04.1 armhf Userspace interface to amdgpu-specific kernel DRM services -- runtime ii libdrm-common 2.4.99-1ubuntu1~18.04.1 all Userspace interface to kernel DRM services -- common files ii libdrm-etnaviv1:armhf 2.4.99-1ubuntu1~18.04.1 armhf Userspace interface to etnaviv-specific kernel DRM services -- runtime ii libdrm-nouveau2:armhf 2.4.99-1ubuntu1~18.04.1 armhf Userspace interface to nouveau-specific kernel DRM services -- runtime ii libdrm-radeon1:armhf 2.4.99-1ubuntu1~18.04.1 armhf Userspace interface to radeon-specific kernel DRM services -- runtime ii libdrm2:armhf 2.4.99-1ubuntu1~18.04.1 armhf Userspace interface to kernel DRM services -- runtime ii libegl-mesa0:armhf 19.2.1-1ubuntu1~18.04.1 armhf free implementation of the EGL API -- Mesa vendor library ii libegl1-mesa:armhf 19.2.1-1ubuntu1~18.04.1 armhf transitional dummy package ii libgbm1:armhf 19.2.1-1ubuntu1~18.04.1 armhf generic buffer management API -- runtime ii libgl1-mesa-dri:armhf 19.2.1-1ubuntu1~18.04.1 armhf free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-glx:armhf 19.2.1-1ubuntu1~18.04.1 armhf transitional dummy package ii libglapi-mesa:armhf 19.2.1-1ubuntu1~18.04.1 armhf free implementation of the GL API -- shared library ii libglx-mesa0:armhf 19.2.1-1ubuntu1~18.04.1 armhf free implementation of the OpenGL API -- GLX vendor library After updating, my OrangePiPlus 2E with kernel 5.4 starts to have problems with screen rendering. Colors were strange, no bit images were rendered, no transparencies etc. XFCE desktop, but also lightdm login screen was rendered very wrong. Same happened to H5 based boards also, OrangePi Prime and OrangePi PC2. I tried different versions of the kernel, 5.4.6, 5.4.8, 5.4.12, but also 5.3.13, always with the same result. But, on kernel 4.19.xx everything work good. I also tried several versions of 4.19 kernels, an everything had been always ok. Previous version of this libraries: hi libdrm-amdgpu1:armhf 2.4.97-1ubuntu1~18.04.1 armhf Userspace interface to amdgpu-specific kernel DRM services -- runtime hi libdrm-common 2.4.97-1ubuntu1~18.04.1 all Userspace interface to kernel DRM services -- common files hi libdrm-etnaviv1:armhf 2.4.97-1ubuntu1~18.04.1 armhf Userspace interface to etnaviv-specific kernel DRM services -- runtime hi libdrm-nouveau2:armhf 2.4.97-1ubuntu1~18.04.1 armhf Userspace interface to nouveau-specific kernel DRM services -- runtime hi libdrm-radeon1:armhf 2.4.97-1ubuntu1~18.04.1 armhf Userspace interface to radeon-specific kernel DRM services -- runtime hi libdrm2:armhf 2.4.97-1ubuntu1~18.04.1 armhf Userspace interface to kernel DRM services -- runtime hi libegl-mesa0:armhf 19.0.8-0ubuntu0~18.04.3 armhf free implementation of the EGL API -- Mesa vendor library hi libegl1-mesa:armhf 19.0.8-0ubuntu0~18.04.3 armhf transitional dummy package hi libgbm1:armhf 19.0.8-0ubuntu0~18.04.3 armhf generic buffer management API -- runtime hi libgl1-mesa-dri:armhf 19.0.8-0ubuntu0~18.04.3 armhf free implementation of the OpenGL API -- DRI modules hi libgl1-mesa-glx:armhf 19.0.8-0ubuntu0~18.04.3 armhf transitional dummy package hi libglapi-mesa:armhf 19.0.8-0ubuntu0~18.04.3 armhf free implementation of the GL API -- shared library hi libglx-mesa0:armhf 19.0.8-0ubuntu0~18.04.3 armhf free implementation of the OpenGL API -- GLX vendor library don't have any problems with kernel 5. There are my limits of knowledge, so I reverted my boards to kernel 4.19.96 until somebody more experienced find what is going on.
  18. A couple of years ago wifi worked without any problems on old version of Armbian, but on the current version It doen't work completely. Any suggestions? uname -a Linux HAMServer 5.4.45-sunxi #20.05.4 SMP Sun Jun 14 21:46:20 CEST 2020 armv7l armv7l armv7l GNU/Linux lsmod | grep 8189fs 8189fs 1069056 0 cfg80211 413696 1 8189fs ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.88.16 netmask 255.255.255.0 broadcast 192.168.88.255 inet6 fe80::8385:e766:9c48:e593 prefixlen 64 scopeid 0x20<link> ether 02:81:a4:6e:47:9e txqueuelen 1000 (Ethernet) RX packets 7721 bytes 618507 (618.5 KB) RX errors 0 dropped 12 overruns 0 frame 0 TX packets 11125 bytes 2714338 (2.7 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 39 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
  19. that steps must be followed to install kodi in armbian? thnks I have added 'deb http://http.debian.net/debianjessie-backports main' in sources.list and sudo apt-get update & sudo apt-get install kodi but when you start kodi the screen goes black
  20. Hello community.. I strugling with hardware acceleration on Orange PI +2E. I read all forums and used google..but all what I found are old threads. I would like to know where can I find some tutorials how to install drivers for HW encoding in h264. Compilation of ffmpeg is not a problem, I did it and tried to encode 720x576 mpeg2 live stream to h264 @ 1000kbps with fdk-aac, and it works but..all cores are around 70%, and it sometimes starting the buffering when I watching on for example on POT player or Vlc. I would like to achive two thing: 1) to be able to use hw acceleration to encode h264 from mpeg2 stream. 2) to be able to use hw decoding 1080p which is mpeg2 and and encode it with hw acceleration to h264. Is it posible to do this btw? I'm installed the latest version of Ubuntu armbian: Linux orangepiplus2e 5.4.43-sunxi #20.05.2 SMP Mon Jun 1 18:26:22 CEST 2020 armv7l armv7l armv7l GNU/Linux Linux orangepiplus2e 5.4.43-sunxi #20.05.2 SMP Mon Jun 1 18:26:22 CEST 2020 armv7l armv7l armv7l GNU/Linux I would be really greatful for any kind of tutoriaal..links explanation, how to do that. Big thx!
  21. Greetings, as noted in the title I have a Plus 2E and I am trying to use the built in wifi to enable a wifi access point. I followed the instructions and video which recommended using armbian-config to create a hotspot. That utility failed to create the hotspot so I ran hostapd manually to find the issue and the following errors were reported (I will attach a file with complete output: ioctl[RTL_IOCTL_HOSTAPD]: Operation not supported wlan0: Could not connect to kernel driver I spent a couple hours searching and it seems related to the driver support AP mode. I haven't gone down the hole of trying to rebuild the driver yet because I'm not sure what options would be needed to function correctly. Does anyone have any insight as to why this isn't working or what can be done to get a hotspot running in AP mode on an OrangePi Plus 2E? Thanks! 2020051401-hostapd-output.txt
  22. Hi, I've managed to install Armbian_20.05.2_Orangepiplus2e_focal_current_5.4.43_desktop on my board. Now I'd like to get decent web-browsing performance (i.e. 1080 videos on a browser) and I've tried installing the mali drivers with no luck. Is there an updated guide that works with the latest version of armbian? Thanks in advance
  23. Device: Orange Pi +2e. Environment one 16GB SD Card and 16GB eMMC onboard. Output from Armbianmonitor attached. The eMMC device onboard is always detected as mmcblk2. Irrespective of whether SD Card is present or not or if you boot from SD Card or eMMC. This is observed only on 20.05 and 20.08 builds. It does not happen on 20.02 build. [ 3.769548] sun8i-h3-pinctrl 1c20800.pinctrl: 1c20800.pinctrl supply vcc-pc not found, using dummy regulator [ 3.781702] mmc0: host does not support reading read-only switch, assuming write-enable [ 3.784384] mmc0: new high speed SDHC card at address aaaa [ 3.785778] mmcblk0: mmc0:aaaa JULIE 14.8 GiB [ 3.790317] mmcblk0: p1 [ 3.790822] mmc1: new high speed SDIO card at address 0001 [ 3.795670] sunxi-mmc 1c11000.mmc: initialized, max. request size: 16384 KB [ 3.915829] mmc2: new DDR MMC card at address 0001 [ 3.917341] mmcblk2: mmc2:0001 AJTD4R 14.6 GiB [ 3.918284] mmcblk2boot0: mmc2:0001 AJTD4R partition 1 4.00 MiB [ 3.919325] mmcblk2boot1: mmc2:0001 AJTD4R partition 2 4.00 MiB [ 3.922791] mmcblk2: p1 [ 4.143718] usb 6-1: new full-speed USB device number 2 using ohci-platform --Rajesh
  24. This topic has been discussed earlier but there is not concrete mechanism explained to achieve this. Ideally I would like to display a boot logo or boot splash during startup. The device is Orange Pi Plus 2e. As per experience and as mentioned on this forum earlier plymouth was not useful in this case. I tried to set logo="enabled" in /boot/armbianEnv.txt but this doesn't help. When Armbian loads for first time on the device from the image downloaded from this site, it displays 'Initializing Boot Loader' logo image. Pretty cool!!! Can we have something like this for a custom image displayed each time on reboot. I understand that this will be displayed only till kernel loads, but that is good enough of me. I can settle with this limited functionality, but am lost on how to do this. Any pointers or suggestion will be highly appreciated. Stay safe! Regards -R
  25. Hello. I am trying to work with a 7-Segment LED Display Module (HT16K33) in a Orange Pi +2e, but I don't know how to start... Any iddea? Thank you in advance.
×
×
  • Create New...