Jump to content

Search the Community

Showing results for tags 'orangepipc2'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Community
    • Announcements
    • Feature Requests
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Upcoming Hardware (WIP)
    • News
    • Odroid M1
    • ROCK 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


  • Official giveaways
  • Community giveaways

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start






Website URL







  1. I am creating a script that can backup sd-cards running on the system, resizing it with desired value or via resize2fs calculated. I learn a lot but there are a few things I don't fully understand. When I create a backup I dd what I understand is the bootsector, ie I grab the "start" position of the partition I am backing up with fidisk and use that value and a blocksize of 512. I then add another 10mb (in bytes) just to be sure. Usually the bootsector is 8192 big, but not always (IIRC nanopi neo3;s is WAY bigger). dd bs=512 count=$DDBOOTSECTOR if=/dev/mmcblk0 of=$IMG_FILE conv=noerror,sync status=progress I then truncate the file, calculated either by resize2fs minimum calculation or via an input + file usage in df (depending of what flag I start the script with) + bootsector + yadayadayda. (if someone want me to post the script I will, but the script and calculations work, although I "force" some commands) I then loop the created img file and delete the partition on the /dev/loop0 and recreates it to cover 100%. Then format it with mkfs.ext4 copying the name and uuid from wherever I backup from. I mount the loop and rsync / rsync -ahvD --exclude={/lost+found,/proc/*,/sys/*,/dev/*,/tmp,/run/*,/mnt/*,/media/*,/var/log.hdd,/var/swap,/etc/udev/rules.d/70-persistent-net.rules,/var/lib/asterisk/astdb.sqlite3-journal} --info=progress2 --stats --delete --force --partial / $tmp_dir This seems to work, but there are probably some things that are just "accepted" not really "perfect". So questions: 1. Should I only dd the EXACT bootsector and not add the extra 10mb? The reason I ask is because if I try to delete the partition with parted, I have to do a hack in the scrip where I simulate button presses, it warns me that "the partition cant be outside of the disk" when I try to REMOVE it. Solution, I use sfdisk to remove the partition, but it prompts me to think there is something wrong going on here. If the size I create is ABOVE the resize2fs reported minimum i don't get this warning. sfdisk was the solution in this case, but still curious on this behavior. If I try to only dd the small part, it sometimes works, sometimes doesn't so I come here asking. (I might be able to do some further research but since I have other questions, why not ask) 2. Does armbian ever update the u-boot via apt? I do my next update with rscync by looping the file and mounting it. But that wont EVER cover the bootsector. 2b. If yes, do I solve this by again dd:ing ONLY the bootsector? 3. I have noticed that sudo apt update on armbian includes armhf even though running arm64. This makes the update process VERY long. dpkg --print-foreign-architectures shows armhf so i remove it with dpkg --remove-architecture armhf and then find /var/lib/apt/lists/ -type f -exec rm {} -v \; Seems to fix this but is this a bad idea? Why is the armhf even being fetched to begin with? To my memory I have not added arhmf architecture... Thanks in advance!
  2. Hi I'm auto-login using nodm with orange pi. I run my udp.py file by creating a file named udp.desktop under the .etc/xdg/autostart folder at startup. but I need to play the wav file using pygame in the .py file, but I get a warning that the audio device could not be initialized. If I trigger my .py file manually, I can play the wav file without any problems. probably unable to load sound drivers during autostart. Can you help with this.
  3. Hello there, i have one orange pi pc 2 and i need to put this work with 2-Channel Isolated CAN Expansion HAT from Waveshare (2-Channel Isolated CAN Bus Expansion HAT for Raspberry Pi, MCP2515 + SN65HVD230 Dual Chips Solution, Multi Onboard Protection Circuits (waveshare.com) But im stuck with .dts and overlays. This HAT was design to work with raspberry pi but i know we can put it to work with orange pi. My problem is with "chipselect" cause our GPIO pin configuration are diferent then Raspberry Pi Could you please give me an example how should it be my .dts?
  4. Before I file a bug for this, I want to make sure I'm not doing something wrong. I am trying to enable PPS on GPIO pin PD14 of an Orange Pi PC2. I've enabled the pps-gpio and uart overlays in my /boot/armbianEnv.txt file and rebooted. root@ntp0:~# cat /boot/armbianEnv.txt verbosity=1 bootlogo=false console=both disp_mode=1920x1080p60 overlay_prefix=sun50i-h5 rootdev=UUID=20dbbd2a-5783-4f98-b467-62fa62990ac8 rootfstype=ext4 overlays=pps-gpio uart1 param_pps_pin=PD14 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u root@ntp0:~# On reboot I see the following problem in dmesg: [ 5.542593] pps-gpio pps@0: failed to map GPIO to IRQ: -22 [ 5.542626] pps-gpio: probe of pps@0 failed with error -22 If I 'rmmod/modprobe' the pps-gpio/pps-ldisc modules I see pps0 created: [ 54.983158] pps pps0: new PPS source serial1 [ 54.983284] pps pps0: source "/dev/ttyS1" added Yet I am not getting PPS data on pps0 even with the gps locked as measured by cgps/gpsmon. root@ntp0:~# ppstest /dev/pps0 trying PPS source "/dev/pps0" found PPS source "/dev/pps0" ok, found 1 source(s), now start fetching data... time_pps_fetch() error -1 (Connection timed out) time_pps_fetch() error -1 (Connection timed out) time_pps_fetch() error -1 (Connection timed out) ^C root@ntp0:~# lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqklqqqqqqqqqqqqqqqqqqSeen 12/Used 9k x Time: 2022-04-17T18:35:49.000Z (0) xxGNSS PRN Elev Azim SNR Usex x Latitude: xx.xxxxxxxx N xxGP 1 1 26.0 49.0 15.0 Y x x Longitude: yy.yyyyyyyy W xxGP 6 6 23.0 169.0 18.0 Y x x Alt (HAE, MSL): 6353.675, 6407.480 ft xxGP 13 13 28.0 235.0 18.0 Y x x Speed: 0.11 mph xxGP 14 14 54.0 72.0 21.0 Y x x Track (true, var): 332.6, 11.0 deg xxGP 15 15 18.0 270.0 23.0 Y x x Climb: 0.00 ft/min xxGP 17 17 84.0 23.0 22.0 Y x x Status: 3D FIX (9 secs) xxGP 19 19 70.0 231.0 21.0 Y x x Long Err (XDOP, EPX): 0.61, +/- 30.1 ft xxGP 24 24 21.0 314.0 28.0 Y x x Lat Err (YDOP, EPY): 0.64, +/- 31.6 ft xxGP 30 30 26.0 151.0 16.0 Y x x Alt Err (VDOP, EPV): 0.81, +/- 61.1 ft xxGP 7 7 2.0 146.0 0.0 N x x 2D Err (HDOP, CEP): 0.87, +/- 54.2 ft xxGP 21 21 3.0 32.0 0.0 N x x 3D Err (PDOP, SEP): 1.19, +/- 74.2 ft xxSB134 47 0.0 0.0 0.0 N x x Time Err (TDOP): 0.88 xx x x Geo Err (GDOP): 1.87 xx x x ECEF X, VX: n/a n/a xx x x ECEF Y, VY: n/a n/a xx x x ECEF Z, VZ: n/a n/a xx x x Speed Err (EPS): +/- 43.0 mph xx x x Track Err (EPD): n/a xx x x Time offset: 0.551504007 s xx x x Grid Square: AABBCCDD xx x mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqjmqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj (location/grid square redacted) Looking at what the kernel thinks it has for gpio pins enabled I see this: root@ntp0:~# cat /sys/kernel/debug/gpio gpiochip1: GPIOs 0-223, parent: platform/1c20800.pinctrl, 1c20800.pinctrl: gpio-20 ( |orangepi:red:status ) out lo gpio-102 ( |gmac-3v3 ) out hi gpio-166 ( |cd ) in lo IRQ ACTIVE LOW gpio-204 ( |usb0_id_det ) in hi IRQ gpiochip0: GPIOs 352-383, parent: platform/1f02c00.pinctrl, 1f02c00.pinctrl: gpio-354 ( |usb0-vbus ) out lo gpio-355 ( |sw4 ) in hi IRQ ACTIVE LOW gpio-362 ( |orangepi:green:pwr ) out hi root@ntp0:~# Is this indeed a case of the pin not being assigned an interrupt or is the pps-gpio IRQ mapping message unrelated to the problem? Thanks
  5. Hi, Are there any news on if Armbian will be on the new H5 64bit board? Orange released an Android SDK and an Android image but I guess everyone is waiting for a decent 64bit Debian. Since took the plunge and got into the H5 wagon ordering one, I looked at the released info and obviously there was nothing I could use myself.. So the question goes to the Armbian gurus, guys do you think that there could be an Armbian release for H5 this year? Christos
  6. Steps: - Installed "Focal xfce desktop" Orange Pi PC 2 image - Installed mesa-utils - Set display resolution 1920x1080 60hz - Run glxgears Actual behaviour: - running at 30fps Expected behaviour: - running at 60fps or higher Additional information: - glxgears -info output: https://pastebin.com/y4W30MFg
  7. Hey guys. I have been trying to utilize H5 vpu decoding for 10+ hours... Still no go. Here is the checklist: kernel Using mainline kernel 5.8.9 from Armbian/build current. `uname -a` output: All kernel configs needed on Sunxi-Cedrus homepage were added, cma set to 256M. libva-v4l2-request Using https://github.com/Sash0k/libva-v4l2-request master. Compiled and make installed. `vainfo` output: `v4l2-ctl --list-formats` output: `./v4l2-request-test -f 25 -l` output: Cpu usage is quite low(4 cores <5%), checked with lsof and /dev/media0 & /dev/video0 are all occupied by v4l2-request-test. Seems frame decoding is working ok, but the big_buck_bunny video did not show up, something must be wrong here... ffmpeg https://github.com/Kwiboo/FFmpeg.git branch FFmpeg-4l2-request-hwaccel-4.3 `--enable-v4l2-request --enable-libdrm --enable-libudev` added in configure, `ffmpeg -decoders | grep 264` output: And finally running `ffmpeg -loglevel debug -hwaccel drm -i ~/jellyfish-10-mbps-hd-h264.mkv -pix_fmt bgra -f fbdev /dev/fb0` without x11, green artifacts met. One of the four cores is 100% utilized, others are free. Frame rate is super low (<5fps). Changing hwaccel from `drm` to `vaapi` (and what's the difference between these two?), met another kind of artifacts. So, any kind of help are welcomed, thanks! buptsb
  8. HI, guys! I tried to enable spi connect RC522 on OPi_PC(H3). It works! my topic: but now, I make the same way to enable spi with RC522 on OPi_PC2(H5). I can found spi on "/dev/spidev0.0" But when I run "Read.py" script as root. It can't detect & read the cards. How can i use it on OPi_PC2?
  9. I am running Armbian Focal with Linux 5.4.43-sunxi64 (and now downgraded to 4.19.125-sunxi64) on my Orange Pi PC 2. I use motion software to provide a "18ec:5555 Arkmicro Technologies Inc. USB2.0 PC CAMERA" to the network. I also use pjsip to provide SIP functionality for the same device as audio input. As soon as I start pjsip for some reason I get a very high load average until the kernel detectets stalled CPUs and finally the entire device crashes. This worked fine in a previous version and started after I upgraded to focal. I did a kernel backtrace and this is what I got: [ 401.002517] sysrq: Show backtrace of all active CPUs [ 401.009965] sysrq: CPU1: [ 401.010084] Call trace: [ 401.010394] dump_backtrace+0x0/0x180 [ 401.010573] show_stack+0x14/0x20 [ 401.010811] showacpu+0x94/0xc8 [ 401.011039] flush_smp_call_function_queue+0x90/0x150 [ 401.011247] generic_smp_call_function_single_interrupt+0x10/0x18 [ 401.011471] handle_IPI+0xf8/0x180 [ 401.011634] gic_handle_irq+0x9c/0xa0 [ 401.011806] el0_irq_naked+0x4c/0x54 [ 401.011993] sysrq: CPU3: [ 401.012118] Call trace: [ 401.012372] dump_backtrace+0x0/0x180 [ 401.012533] show_stack+0x14/0x20 [ 401.012743] showacpu+0x94/0xc8 [ 401.012939] flush_smp_call_function_queue+0x90/0x150 [ 401.013137] generic_smp_call_function_single_interrupt+0x10/0x18 [ 401.013346] handle_IPI+0xf8/0x180 [ 401.013506] gic_handle_irq+0x9c/0xa0 [ 401.013675] el0_irq_naked+0x4c/0x54 [ 401.013834] sysrq: CPU0: [ 401.013941] Call trace: [ 401.014159] dump_backtrace+0x0/0x180 [ 401.014342] show_stack+0x14/0x20 [ 401.014548] showacpu+0x94/0xc8 [ 401.014937] flush_smp_call_function_queue+0x90/0x150 [ 401.015139] generic_smp_call_function_single_interrupt+0x10/0x18 [ 401.015345] handle_IPI+0xf8/0x180 [ 401.015501] gic_handle_irq+0x9c/0xa0 [ 401.015657] el1_irq+0xb8/0x140 [ 401.015915] arch_counter_get_cntpct+0x8/0x18 [ 401.016143] ktime_get+0x40/0xa0 [ 401.016633] uvc_video_decode_start+0x6d8/0x7e8 [uvcvideo] [ 401.017006] uvc_video_decode_isoc+0xac/0x168 [uvcvideo] [ 401.017359] uvc_video_complete+0x11c/0x1c8 [uvcvideo] [ 401.017613] __usb_hcd_giveback_urb+0x70/0x130 [ 401.017821] usb_giveback_urb_bh+0xf0/0x190 [ 401.018030] tasklet_action_common.isra.19+0xc4/0x188 [ 401.018182] tasklet_hi_action+0x24/0x30 [ 401.018349] __do_softirq+0x11c/0x230 [ 401.018497] irq_exit+0x9c/0xb8 [ 401.018750] __handle_domain_irq+0x64/0xb8 [ 401.018904] gic_handle_irq+0x50/0xa0 [ 401.019058] el1_irq+0xb8/0x140 [ 401.019279] clk_core_unprepare+0x0/0x100 [ 401.019529] clk_core_set_rate_nolock+0x1bc/0x1e8 [ 401.019725] clk_set_rate+0x34/0xa0 [ 401.019962] dev_pm_opp_set_rate+0x394/0x4f0 [ 401.020230] set_target+0x3c/0x80 [cpufreq_dt] [ 401.020428] __cpufreq_driver_target+0x2bc/0x678 [ 401.020611] od_dbs_update+0xb8/0x190 [ 401.020801] dbs_work_handler+0x3c/0x70 [ 401.021027] process_one_work+0x1ec/0x370 [ 401.021218] worker_thread+0x4c/0x4f8 [ 401.021401] kthread+0x120/0x128 [ 401.021601] ret_from_fork+0x10/0x18 [ 403.369173] sysrq: Show backtrace of all active CPUs [ 403.375878] sysrq: CPU0: [ 403.375993] Call trace: [ 403.376316] dump_backtrace+0x0/0x180 [ 403.376496] show_stack+0x14/0x20 [ 403.376721] showacpu+0x94/0xc8 [ 403.376942] flush_smp_call_function_queue+0x90/0x150 [ 403.377146] generic_smp_call_function_single_interrupt+0x10/0x18 [ 403.377354] handle_IPI+0xf8/0x180 [ 403.377667] gic_handle_irq+0x9c/0xa0 [ 403.378019] el1_irq+0xb8/0x140 [ 403.378650] uvc_video_decode_start+0x104/0x7e8 [uvcvideo] [ 403.379181] uvc_video_decode_isoc+0xac/0x168 [uvcvideo] [ 403.379899] uvc_video_complete+0x11c/0x1c8 [uvcvideo] [ 403.380312] __usb_hcd_giveback_urb+0x70/0x130 [ 403.380606] usb_giveback_urb_bh+0xf0/0x190 [ 403.380793] tasklet_action_common.isra.19+0xc4/0x188 [ 403.380945] tasklet_hi_action+0x24/0x30 [ 403.381110] __do_softirq+0x11c/0x230 [ 403.381460] irq_exit+0x9c/0xb8 [ 403.381862] __handle_domain_irq+0x64/0xb8 [ 403.382180] gic_handle_irq+0x50/0xa0 [ 403.382497] el1_irq+0xb8/0x140 [ 403.382876] tcp_sendmsg_locked+0x288/0xc90 [ 403.383202] tcp_sendmsg+0x34/0x58 [ 403.383488] inet_sendmsg+0x40/0x68 [ 403.383686] sock_sendmsg+0x44/0x50 [ 403.383869] __sys_sendto+0xcc/0x130 [ 403.384033] __arm64_sys_sendto+0x24/0x30 [ 403.384273] el0_svc_common.constprop.2+0x88/0x150 [ 403.384476] el0_svc_handler+0x20/0x80 [ 403.384636] el0_svc+0x8/0xc [ 403.384802] sysrq: CPU1: [ 403.384917] Call trace: [ 403.385150] dump_backtrace+0x0/0x180 [ 403.385323] show_stack+0x14/0x20 [ 403.385535] showacpu+0x94/0xc8 [ 403.385747] flush_smp_call_function_queue+0x90/0x150 [ 403.385950] generic_smp_call_function_single_interrupt+0x10/0x18 [ 403.386152] handle_IPI+0xf8/0x180 [ 403.386306] gic_handle_irq+0x9c/0xa0 [ 403.386477] el0_irq_naked+0x4c/0x54 [ 406.143125] sysrq: Show backtrace of all active CPUs [ 406.158279] sysrq: CPU2: [ 406.158407] Call trace: [ 406.158720] dump_backtrace+0x0/0x180 [ 406.158892] show_stack+0x14/0x20 [ 406.159119] showacpu+0x94/0xc8 [ 406.159340] flush_smp_call_function_queue+0x90/0x150 [ 406.159544] generic_smp_call_function_single_interrupt+0x10/0x18 [ 406.159763] handle_IPI+0xf8/0x180 [ 406.159931] gic_handle_irq+0x9c/0xa0 [ 406.160097] el1_irq+0xb8/0x140 [ 406.160303] __seccomp_filter+0x74/0x5e8 [ 406.160484] __secure_computing+0x38/0xc0 [ 406.160701] syscall_trace_enter+0x100/0x148 [ 406.160925] el0_svc_common.constprop.2+0x54/0x150 [ 406.161125] el0_svc_handler+0x20/0x80 [ 406.161282] el0_svc+0x8/0xc [ 406.161441] sysrq: CPU1: [ 406.161550] Call trace: [ 406.161773] dump_backtrace+0x0/0x180 [ 406.161949] show_stack+0x14/0x20 [ 406.162157] showacpu+0x94/0xc8 [ 406.162349] flush_smp_call_function_queue+0x90/0x150 [ 406.162711] generic_smp_call_function_single_interrupt+0x10/0x18 [ 406.162916] handle_IPI+0xf8/0x180 [ 406.163076] gic_handle_irq+0x9c/0xa0 [ 406.163240] el0_irq_naked+0x4c/0x54 [ 406.163399] sysrq: CPU0: [ 406.163511] Call trace: [ 406.163729] dump_backtrace+0x0/0x180 [ 406.163906] show_stack+0x14/0x20 [ 406.164110] showacpu+0x94/0xc8 [ 406.164311] flush_smp_call_function_queue+0x90/0x150 [ 406.164507] generic_smp_call_function_single_interrupt+0x10/0x18 [ 406.164710] handle_IPI+0xf8/0x180 [ 406.164871] gic_handle_irq+0x9c/0xa0 [ 406.165026] el1_irq+0xb8/0x140 [ 406.165610] uvc_video_decode_start+0x3d8/0x7e8 [uvcvideo] [ 406.166155] uvc_video_decode_isoc+0xac/0x168 [uvcvideo] [ 406.166672] uvc_video_complete+0x11c/0x1c8 [uvcvideo] [ 406.167086] __usb_hcd_giveback_urb+0x70/0x130 [ 406.167451] usb_giveback_urb_bh+0xf0/0x190 [ 406.167804] tasklet_action_common.isra.19+0xc4/0x188 [ 406.168128] tasklet_hi_action+0x24/0x30 [ 406.168458] __do_softirq+0x11c/0x230 [ 406.168691] irq_exit+0x9c/0xb8 [ 406.168922] __handle_domain_irq+0x64/0xb8 [ 406.169071] gic_handle_irq+0x50/0xa0 [ 406.169396] el1_irq+0xb8/0x140 [ 406.169755] tcp_sendmsg_locked+0x288/0xc90 [ 406.170081] tcp_sendmsg+0x34/0x58 [ 406.170441] inet_sendmsg+0x40/0x68 [ 406.170783] sock_sendmsg+0x44/0x50 [ 406.171117] __sys_sendto+0xcc/0x130 [ 406.171444] __arm64_sys_sendto+0x24/0x30 [ 406.171842] el0_svc_common.constprop.2+0x88/0x150 [ 406.172216] el0_svc_handler+0x20/0x80 [ 406.172541] el0_svc+0x8/0xc [ 408.204456] sysrq: Show backtrace of all active CPUs [ 408.214175] sysrq: CPU1: [ 408.214296] Call trace: [ 408.214624] dump_backtrace+0x0/0x180 [ 408.214813] show_stack+0x14/0x20 [ 408.215046] showacpu+0x94/0xc8 [ 408.215271] flush_smp_call_function_queue+0x90/0x150 [ 408.215477] generic_smp_call_function_single_interrupt+0x10/0x18 [ 408.215870] handle_IPI+0xf8/0x180 [ 408.216039] gic_handle_irq+0x9c/0xa0 [ 408.216216] el0_irq_naked+0x4c/0x54 [ 408.216351] sysrq: CPU2: [ 408.216453] Call trace: [ 408.216675] dump_backtrace+0x0/0x180 [ 408.216843] show_stack+0x14/0x20 [ 408.217054] showacpu+0x94/0xc8 [ 408.217250] flush_smp_call_function_queue+0x90/0x150 [ 408.217456] generic_smp_call_function_single_interrupt+0x10/0x18 [ 408.217666] handle_IPI+0xf8/0x180 [ 408.217824] gic_handle_irq+0x9c/0xa0 [ 408.217985] el1_irq+0xb8/0x140 [ 408.218219] kmsg_read+0x50/0x60 [ 408.218440] proc_reg_read+0x5c/0xc8 [ 408.218632] __vfs_read+0x18/0x40 [ 408.218802] vfs_read+0x9c/0x188 [ 408.218968] ksys_read+0x64/0xe8 [ 408.219142] __arm64_sys_read+0x18/0x20 [ 408.219375] el0_svc_common.constprop.2+0x88/0x150 [ 408.219581] el0_svc_handler+0x20/0x80 [ 408.219739] el0_svc+0x8/0xc [ 408.219893] sysrq: CPU0: [ 408.219995] Call trace: [ 408.220206] dump_backtrace+0x0/0x180 [ 408.220376] show_stack+0x14/0x20 [ 408.220588] showacpu+0x94/0xc8 [ 408.220782] flush_smp_call_function_queue+0x90/0x150 [ 408.220981] generic_smp_call_function_single_interrupt+0x10/0x18 [ 408.221184] handle_IPI+0xf8/0x180 [ 408.221336] gic_handle_irq+0x9c/0xa0 [ 408.221490] el1_irq+0xb8/0x140 [ 408.221688] arch_local_irq_restore+0x4/0x10 [ 408.221925] usb_hcd_submit_urb+0xdc/0xad0 [ 408.222133] usb_submit_urb+0x1e0/0x580 [ 408.222619] uvc_video_complete+0x188/0x1c8 [uvcvideo] [ 408.222971] __usb_hcd_giveback_urb+0x70/0x130 [ 408.223348] usb_giveback_urb_bh+0xf0/0x190 [ 408.223700] tasklet_action_common.isra.19+0xc4/0x188 [ 408.224029] tasklet_hi_action+0x24/0x30 [ 408.224350] __do_softirq+0x11c/0x230 [ 408.224589] irq_exit+0x9c/0xb8 [ 408.224822] __handle_domain_irq+0x64/0xb8 [ 408.224972] gic_handle_irq+0x50/0xa0 [ 408.225299] el1_irq+0xb8/0x140 [ 408.225673] tcp_sendmsg_locked+0x288/0xc90 [ 408.226005] tcp_sendmsg+0x34/0x58 [ 408.226364] inet_sendmsg+0x40/0x68 [ 408.226717] sock_sendmsg+0x44/0x50 [ 408.227058] __sys_sendto+0xcc/0x130 [ 408.227391] __arm64_sys_sendto+0x24/0x30 [ 408.227782] el0_svc_common.constprop.2+0x88/0x150 [ 408.228153] el0_svc_handler+0x20/0x80 [ 408.228465] el0_svc+0x8/0xc Does anybody know what might be going on here and how I can fix this issue? Or do I need to go back to Ubuntu Bionic with Armbian Linux 4.13.2-sun50iw2 which I was running before?
  10. There's this: Anybody knows about the status of PWM on the H5 (OPi PC 2 in my case) with mainline kernel? BTW am I off-topic asking about H5 in this forum? Thanks.
  11. I have tested Armbian_19.11.3_Orangepipc2_bionic_current_5.3.9 and Armbian_19.11.3_Orangepipc2_buster_current_5.3.9 images from the official download site. The Debian Buster image is fast and stable. The Ubuntu Bionic build have random hangs on different boot positions. Sometimes works, but after reboot it hangs again randomly. I have burned the the images to the same microsd card. (Toshiba 32GB) I have tested with other microsd cards like Sandisk Extreme 32GB, Samsung EVO+ 32GB. I have the same results. The power supply is enough for the board. (5V 4A) This is not my first orangepi board, so I know how to burn the images to the sdcards. screenlog.bionic.0 (problems) screenlog.buster.0 (all ok) With freshly burned sdcard, sometimes it take a lot of time to boot with the Bionic release. Or simply hangs on different boot positions. Sometimes it gives the following errors: usually hangs in this position:
  12. I have tried to setup user quotas on my Orange PI PC2 and realized that there is no quota module in kernel at all. Switching between all kernel versions with armbian-config utility and all the same - they don't have quota module. Why there is no such necessary module? Is it possible to install this module and how? P.S. Sorry, maybe i have selected wrong chapter for my question
  13. Wanted to share my very positive experience upgrading to the latest kernel. Followed the procedure using armbian-config and it worked out of the box on my OrangePi PC2. Left the system overnight running my standard tests and no issues. Even the problematic rtl8192 has no issue. There used to be a slight judder on the HDMI attached monitor that is gone now, perhaps due to the new MALI450 gpu modules. ___ ____ _ ____ ____ ____ / _ \| _ \(_) | _ \ / ___|___ \ | | | | |_) | | | |_) | | __) | | |_| | __/| | | __/| |___ / __/ \___/|_| |_| |_| \____|_____| Welcome to Ubuntu Xenial with Armbian Linux 5.3.9-sunxi64 Thank you for your hard work.
  14. OPiPC2, with Armbian Bionic desktop mainline based kernel 4.19.y Using it as headless server, all X and desktop stuff removed. Using PuTTY to log in via SSH, line drawing stuff (as usual) only works if translation is set to ISO-8859-1 in PuTTY. mc looks great, but all ncurses-based software (aptitude, htop, bmon etc) does not. Main problem seems that horizontal spacing is "shrunk" whenever there is no text to keep it: This is even more dramatic for menu systems and anything that is column-oriented. Tried dpkg-reconfigure locales to switch system to ISO-8859, but no change, really seems to be an ncurses bug. No such problems with other systems (Raspbian etc.). Is this a known problem? Is there a workaround? Thanks
  15. Hi, how can I enable hardware decode of video h264 mpeg on H5 chip? I use a Orange pi pc2 but video goes slow and lag very much. H5 SoC has very value hardware but isn’t possibile use mali GPU yet? Thanks
  16. Hi, I built Armbian (bionic) from source for Orange Pi PC 2 and everything went through fine. I burn to SD card and load it on the board and it boots well. Then I use "root" to login and forced to change password from default 1234 to somepass. Everything seemed fine until I tried to login with the new password (old password failed to work anymore). The errors are in following screen shot. Kinda new to this stuff, not sure how to fix it. Tried to connect to serial port but somehow a couple of TTL cable all failed to work. Still struggling. Please help!
  17. Hi, seems after some system updates SNMP stop reporting data about storage (size/used). It happen on 2x Orange PI One and on one Orange PI PC2. Actually in monitor what I use for SNMP monitoring I see last valid data was there at 05/09. I think at this time I update all boards and as I remmember there was also some update for snmpd. Can anyone confirm this problem ? And when we talk about SNMP, what is best way to change default logging level for SNMP ? Seems changing in /etc/default/snmpd doesnt have effect and after last update I must again edit files in /lib/systemd to stop that annoying flood in log from SNMP. OPI PC2 - 4.19.63-sunxi64 #5.92 SMP Fri Aug 2 00:18:27 CEST 2019 aarch64 aarch64 aarch64 GNU/Linux OPI One - 4.19.62-sunxi #5.92 SMP Wed Jul 31 22:07:23 CEST 2019 armv7l armv7l armv7l GNU/Linux /Tomi
  18. Hello, I can get 5.90 Bionic to boot, but Unifi needs an old mongodb. Stretch 5.65 worked in the past, but 5.83 will not boot. It hangs after "[ OK ] Started udev Coldplug all Devices." I've tried many, many times. Any idea what this means? I also can't get Stretch 5.65 to work again. It does not boot after a dist-upgrade
  19. hi, I'm trying to use an OrangePiPC2 H5 processor on an old TV. I have got to edit the dts file but I dont know what to change to antivate RCA video & audio output. Plz, help me to set RCA port as default or give me links to learn to edit dts, I've seached a lot but found nothing. thx
  20. Good afternoon, please help configure the rotation of the logs. I am completely new to this system, unfortunately, I can not find a normal instruction on how to configure rotatilog. My problem is that the logs are full, and my necessary scripts stop working. If I constantly clear the logs manually, then the scripts work fine. I tried to configure the rotation in accordance with the instructions, it only works before the reboot, after the reboot, everything I fixed with the rotation changes the paths to /var/log.hdd/. Please help me make sure that all logs do not exceed 1m. and constantly spinning. I apologize in advance if not fully expressed his thought.
  21. hi when i try to play a video player performance is very low on armbian but when i install android on my board video player performance is good Enoughwith mx player app i try improve performance with overclock cpu but its not helpful how can i improve performance of video player on armbian ? and its possible to play h.265 video and 3d video?
  22. HI I noticed that the Windows 10 on Arm version has the ability to install on mini-pc, like the raspberry pi. My question is, is Windows 10 capable of being installed on the BOARD WITH h5 processor? I USE OF QEMU-KVM FOR INSTALL WINDOWS ON MY ORANGE PI BOARD BUT IT HAS VERY LOW PERFORMANCE AND QEMU ONLY USE OF ONE OF H5 CPU CORE . Is it possible to install on orange pi pc2 armbian and Windows operating systems at the same time with dual boot?
  23. Hello everyone :-). I would like help, I checked on the Web and I found using the forum a script (that I modified) to trigger using DTS LEDs. I adapted the script found here at the end of the page: Topic 112-dtb-howto-add-leds I think that for the section "disk-activity" and "netdev" it misses options but I'm not a developer just a scheming. Can you please explain to me how to add options to the mentioned trigger? I searched a lot of time but did not find any information. Here is my script, everything works fine (compiled with armbian-add-overlay), but "disk-activity" and "netdev" do not work. I tested the write / read trigger on disk but did not work either. Can you explain to me how to add the (device) options for disk-activity (with usb-nand-sata on / dev / sda) and netdev (for eth0)? thank you for the one who can help me to understand or to work this script. My card is OrangePi PC2 H5 1GB Sorry for bad english, my mother language is french. (this message is translatted in english from french) here is my script: /dts-v1/; /plugin/; / { compatible = "allwinner,sun50i-h5"; fragment@0 { target = <&pio>; __overlay__ { gpio_pin: gpio_pin { pins = "PA19","PA7","PA8","PA9","PA10","PD11","PA6","PA1","PA0","PA3"; function = "gpio_out"; }; }; }; fragment@1 { target-path = "/"; __overlay__ { gpiopull: gpiopull { compatible = "gpio-leds"; pinctrl-names = "default"; pinctrl-0 = <&gpio_pin>; status = "okay"; gpio_out_19 { label = "P19:orange:wifiRx"; gpios = <&pio 0 19 0>; linux,default-trigger = "phy0rx"; }; gpio_out_7 { label = "P7:red:wifiTX"; gpios = <&pio 0 7 0>; default-state = "om"; linux,default-trigger = "phy0tx"; }; gpio_out_8 { label = "P8:orange:wifiConnect"; gpios = <&pio 0 8 0>; linux,default-trigger = "phy0assoc"; }; gpio_out_9 { label = "P9:green:wifiDetectUSB"; gpios = <&pio 0 9 0>; linux,default-trigger = "phy0radio"; }; gpio_out_10 { label = "P10:blue:cpuOnline"; gpios = <&pio 0 10 0>; linux,default-trigger = "cpu"; }; gpio_out_11 { label = "P11:white:Act"; gpios = <&pio 3 11 0>; linux,default-trigger = "activity"; }; gpio_out_0 { label = "P0:mmc0"; gpios = <&pio 0 0 0>; linux,default-trigger = "mmc0"; }; gpio_out_1 { label = "P1:disk-activity"; gpios = <&pio 0 1 0>; linux,default-trigger = "disk-activity"; }; gpio_out_3 { label = "P3:etherLink1gbps"; gpios = <&pio 0 3 0>; linux,default-trigger = "0.2:01:1Gbps"; }; gpio_out_6 { label = "P6:cpuled"; gpios = <&pio 0 6 0>; linux,default-trigger = "netdev"; }; }; }; }; }; addDTBTest2.dts
  24. Recently I borrowed my Orange Pi PC2 to a friend, and he fails to set up SSH connection w/ it. After debugging w/ HDMI monitor, I found ssh_host_ecdsa_key, ssh_host_ed25519_key and ssh_host_rsa_key are preloaded to the Orange Pi PC2 image, which prevented SSH from working. Even if it doesn't prevent working of SSHD, it's also a severe security hole -- that means all Armbian installation with the same image will uses the same host key and they're vulnerable to MITM attack. I think these files should be purged when generating image, and regenerated when first powerup. It's what AOSC OS images do.
  25. Hello! How to enable 1-Wire Dallas? I tried this: vi /boot/armbianEnv.txt ----------------------------------------------------- overlays=w1-gpio param_w1_pin=PA10 param_w1_pin_int_pullup=1 ----------------------------------------------------- Then I saw /sys/bus/w1/devices 00-400000000000 -> ../../../devices/w1_bus_master1/00-400000000000/ 00-800000000000 -> ../../../devices/w1_bus_master1/00-800000000000/ w1_bus_master1 -> ../../../devices/w1_bus_master1/ But there was not data. I tried this: vi /etc/modules ----------------------------------------------------- g_serial w1-sunxi w1-gpio w1-therm ----------------------------------------------------- ..and I even saw this: lsmod | grep w1 w1_therm 16384 0 w1_gpio 16384 0 wire 28672 2 w1_gpio,w1_therm But with no effect. May you help to understand what's wrong? Kind regards, Ellad
  • Create New...