Jump to content

Search the Community

Showing results for tags 'tinkerboard'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Armbian
    • Armbian project administration
  • Community
    • Announcements
    • SBC News
    • Framework and userspace feature requests
    • Off-topic
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Standard support
    • Amlogic meson
    • Allwinner sunxi
    • Rockchip
    • Other families
  • Community maintained / Staging
    • TV boxes
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Support

Categories

  • Official giveaways
  • Community giveaways

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/Jabber


Skype


Github


Discord


Location


Interests

  1. Hello, I have been experimenting with the bluetooth audio on my tinkerboard. The issue is both present on the last rockchip-next (4.1x I think) and the rockchip-current 5.8.18 kernel. I am using bluez and bluealsa. The problem is specific to the onboard bluetooth, using an external bluetooth dongle (a cheap and old CSR Bluetooth 3.0 dongle from China) works as expected, I can even send audio to multiple devices simultaneously (quality is very bad, but thats a bandwidth problem). As long as I just connect one bluetooth audio device everything is fine. I can have multiple paired, but disconnected, devices and as long as I connect and play and diconnect, things keep working. But as soon as I try to connect a second device, while another one is already connected (not even playing), the second device shortly shows up as connected in `bluetoothctl` (while the LED on the speaker itself stil shows not-connected) and about 10-20 seconds later the device shows up as disconnected and would not even reconnect unless switched on or off. The error logged by bluetoothd / bluez (5.55-1) is bluetoothd[15142]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 74:A3:xx:xx:xx:xx: Connection refused (111) The connection process does not reach the bluealsa layer, I had similar problems when quickly testing with pulseaudio's bluetooth module. My question: Is there anywhere in the armbian tinkerboard configuration some hardcoded option to only connect to one device at a time? I cannot imagine this to be alimit of the on-board chip, Are there any config options for the HCI UART kernel driver?
  2. Hi. I would like to download last armbian image for my Asus tinkerboard, but all download links broken: https://www.armbian.com/tinkerboard/ Can you fix that? I found Armbian_20.08.1_Tinkerboard_focal_current_5.8.6_desktop.img.xz here: https://armbian.tnahosting.net/archive/tinkerboard/archive/ Is that latest one?
  3. Wifi AP access point broken in Linux tinkerboard 5.4.44-rockchip #20.05.2 SMP PREEMPT Wed Jun 3 10:43:15 CEST 2020 armv7l armv7l armv7l GNU/Linux [ 456.873025] ------------[ cut here ]------------ [ 456.878198] kernel BUG at mm/slub.c:3968! [ 456.882680] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM [ 456.889200] Modules linked in: xt_MASQUERADE xt_conntrack ipt_REJECT iptable_filter 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 fuse zstd snd_soc_hdmi_codec zram snd_soc_simple_card snd_soc_simple_card_utils gpio_keys panfrost dw_hdmi_i2s_audio gpu_sched snd_usb_audio snd_soc_rockchip_i2s snd_soc_rockchip_pcm snd_hwdep snd_usbmidi_lib rockchip_rga snd_rawmidi snd_soc_core snd_seq_device snd_pcm_dmaengine videobuf2_dma_sg v4l2_mem2mem snd_pcm videobuf2_memops videobuf2_v4l2 snd_timer rk_crypto snd videobuf2_common soundcore syscon_reboot_mode dw_wdt reboot_mode rk3288_gpiomem r8723bs(C) rockchip_thermal cpufreq_dt sch_fq_codel ip_tables hid_logitech_hidpp hid_logitech_dj realtek [ 456.975109] CPU: 1 PID: 1564 Comm: RTW_CMD_THREAD Tainted: G C 5.4.44-rockchip #20.05.2 [ 456.985512] Hardware name: Rockchip (Device Tree) [ 456.990779] PC is at kfree+0x2dc/0x308 [ 456.994974] LR is at nl80211_send_station+0x954/0xfc4 [ 457.000621] pc : [<c02b81c0>] lr : [<c0e2a470>] psr: 400b0013 [ 457.007625] sp : e8edfd28 ip : e8edfd58 fp : e8edfd54 [ 457.013464] r10: c1606788 r9 : eccca0c0 r8 : e8edfec0 [ 457.019304] r7 : e8edfec0 r6 : c0e2a470 r5 : ef3bb75c r4 : 00000000 [ 457.026601] r3 : 00000100 r2 : 00000024 r1 : ea678d61 r0 : e8edfec0 [ 457.033901] Flags: nZcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment none [ 457.041878] Control: 10c5387d Table: 2965806a DAC: 00000051 [ 457.048303] Process RTW_CMD_THREAD (pid: 1564, stack limit = 0x081ec079) [ 457.055796] Stack: (0xe8edfd28 to 0xe8ee0000) [ 457.060669] fd20: ea678cdc c07996bc e8edfe00 e80a9480 00000011 00000000 [ 457.069818] fd40: e8edfec0 eccca0c0 e8edfdb4 e8edfd58 c0e2a470 c02b7ef0 00000005 00000013 [ 457.078967] fd60: c0276534 00000000 c1606788 eccca030 eccca0c0 eccca014 00000000 00000000 [ 457.088115] fd80: 0086c550 e9c85a1a 000101dc ec46d9e0 ec46d000 00000000 00000a20 ea678cca [ 457.097263] fda0: e8edfe00 e80a9480 e8edfdfc e8edfdb8 c0e2b18c c0e29b28 00000000 ec46d800 [ 457.106411] fdc0: ec46d000 ea678cca e8edfe00 00000001 e8edfdec c1606788 0000001c 00000000 [ 457.115560] fde0: 00000000 bf091050 e85b9d80 00009930 e8edfeec e8edfe00 bf086684 c0e2b108 [ 457.124708] fe00: 00000000 00000000 000fffff c02b72e4 c010d6a0 c1606788 e9c85a1a c02b73bc [ 457.133856] fe20: 0000000a 00000000 e8edfebc e8edfe38 c02b73bc c0151ec8 bf069230 bf068f24 [ 457.143004] fe40: e816fc00 c1606788 c010d6a0 00210d00 8015000a 00000001 00000001 e816fc00 [ 457.152153] fe60: ffffe000 600b0013 e8edfeac e8edfe78 ea678cdc 00000085 e8edfec4 8015000a [ 457.161301] fe80: c02b5990 c0277ffc e8edfef0 e9c85a1a 000000a1 ee401c00 ef39d39c bf03df0c [ 457.170450] fea0: e816fc00 c012bf24 ffffe000 000000a1 e8edfed4 e8edfec0 c012bf24 c0151ec8 [ 457.179598] fec0: bf03df20 f1225f84 e8edfeec e9c85a1a f086b000 f1225f84 000000a1 ea678cc0 [ 457.188746] fee0: e8edff0c e8edfef0 bf03df38 bf086610 f086c000 00000000 f086c4b8 c1604900 [ 457.197894] ff00: e8edff24 e8edff10 bf048e4c bf03dd7c f086c000 f086e000 e8edff74 e8edff28 [ 457.207042] ff20: bf03693c bf048dcc e8edff4c e8edff38 f086c49c f086b000 bf099000 ec46f200 [ 457.216190] ff40: e8ede000 f086c480 c014902c e8369900 e9975200 00000000 e8ede000 f086b000 [ 457.225339] ff60: bf0367a4 ed7a57e8 e8edffac e8edff78 c014a214 bf0367b0 e8369928 e8369928 [ 457.234486] ff80: 00000000 e9975200 c014a0a4 00000000 00000000 00000000 00000000 00000000 [ 457.243626] ffa0: 00000000 e8edffb0 c01010e8 c014a0b0 00000000 00000000 00000000 00000000 [ 457.252752] ffc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 457.261879] ffe0: 00000000 00000000 00000000 00000000 00000013 00000000 00000000 00000000 [ 457.271004] Backtrace: [ 457.273733] [<c02b7ee4>] (kfree) from [<c0e2a470>] (nl80211_send_station+0x954/0xfc4) [ 457.282481] r9:eccca0c0 r8:e8edfec0 r7:00000000 r6:00000011 r5:e80a9480 r4:e8edfe00 [ 457.291132] [<c0e29b1c>] (nl80211_send_station) from [<c0e2b18c>] (cfg80211_new_sta+0x90/0x1cc) [ 457.300850] r10:e80a9480 r9:e8edfe00 r8:ea678cca r7:00000a20 r6:00000000 r5:ec46d000 [ 457.309586] r4:ec46d9e0 [ 457.312433] [<c0e2b0fc>] (cfg80211_new_sta) from [<bf086684>] (rtw_cfg80211_indicate_sta_assoc+0x80/0x9c [r8723bs]) [ 457.324095] r10:00009930 r9:e85b9d80 r8:bf091050 r7:00000000 r6:00000000 r5:0000001c [ 457.332831] r4:c1606788 [ 457.335692] [<bf086604>] (rtw_cfg80211_indicate_sta_assoc [r8723bs]) from [<bf03df38>] (rtw_stassoc_event_callback+0x1c8/0x1d4 [r8723bs]) [ 457.349489] r7:ea678cc0 r6:000000a1 r5:f1225f84 r4:f086b000 [ 457.355845] [<bf03dd70>] (rtw_stassoc_event_callback [r8723bs]) from [<bf048e4c>] (mlme_evt_hdl+0x8c/0xb4 [r8723bs]) [ 457.367601] r7:c1604900 r6:f086c4b8 r5:00000000 r4:f086c000 [ 457.373959] [<bf048dc0>] (mlme_evt_hdl [r8723bs]) from [<bf03693c>] (rtw_cmd_thread+0x198/0x3d8 [r8723bs]) [ 457.384744] r5:f086e000 r4:f086c000 [ 457.388754] [<bf0367a4>] (rtw_cmd_thread [r8723bs]) from [<c014a214>] (kthread+0x170/0x174) [ 457.398083] r10:ed7a57e8 r9:bf0367a4 r8:f086b000 r7:e8ede000 r6:00000000 r5:e9975200 [ 457.406828] r4:e8369900 [ 457.409653] [<c014a0a4>] (kthread) from [<c01010e8>] (ret_from_fork+0x14/0x2c) [ 457.417718] Exception stack(0xe8edffb0 to 0xe8edfff8) [ 457.423356] ffa0: 00000000 00000000 00000000 00000000 [ 457.432492] ffc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 457.441618] ffe0: 00000000 00000000 00000000 00000000 00000013 00000000 [ 457.449006] r10:00000000 r9:00000000 r8:00000000 r7:00000000 r6:00000000 r5:c014a0a4 [ 457.457750] r4:e9975200 [ 457.460574] Code: 1a000003 e5953004 e3130001 1a000000 (e7f001f2) [ 457.467381] ---[ end trace 4acbc8c15e9e6aa7 ]---
  4. Hi, since i have a Asus tinkerboard incoming i was wondering if anyone knows if the "generic" arm64 distro will work this board. Its based of the rockchip RK3288 SoC The support pages states that the board supports debian, but since i dont need a UI ect (im going to use it headless) i dont need the board to load a ui into memory and wanted to use a normal build instead of the TinkerOS Please note, my knowledge of the inner workings of *nix is quite limited, so if my question is to generic or imprecise i apologize.
  5. Just as a notice the Raspberrry PI 7" DSI Touchscreen was working fine on Armbian with the 4.4 Kernel. Using the current Armbian for Tinkerboard and the 4.19 Kernel it does not work any longer, nor does it with the current development Kernel 5.1. Does there have to be any special things to be set to get it working again? On the 4.4 Kernel it was working out of the box. Thanx
  6. I am testing RK3288 with ubuntu 20.04 (gnome) btw NICE And I have some problems with panfrost and I am looking for anybody with RK3288 device that can confirm or not same behavior. Problem is that when I switch GPU to 600MHz sudo bash -c 'echo "userspace" > /sys/class/drm/card1/device/devfreq/ffa30000.gpu/governor' sudo bash -c 'echo "600000000" > /sys/class/drm/card1/device/devfreq/ffa30000.gpu/userspace/set_freq' and when I run glmark2-es2 or glmark2-es2-wayland I start to see https://pastebin.com/NuYqHdxH in kernel.log So I made bugreport(https://gitlab.freedesktop.org/mesa/mesa/-/issues/2693) for panfrost and they think that problem is in low voltage on gpu as everything is fine on 400MHz So anybody can try? just build ubuntu 20.04 for your RK3288 device sudo BETA=yes EXPERT=yes ./compile.sh server build should be fine and then apt install ubuntu-desktop ubuntu 20.04 has almost latest mesa so everything work just fine
  7. In order to review the Tinker Board boot logs via serial console, I set up armbianEnv.txt to get the logs. But Armbian didn't output anything. Can anyone tell me what is wrong? As long as I reviewed boot.cmd, the serial port was assigned to /dev/ttyS2. So I used UART2 GPIO pins (GP7C7 for TX, GP7C6 for RX) to interact. (snip) if test "${console}" = "serial" || test "${console}" = "both"; then setenv consoleargs "console=ttyS2,115200n8 ${consoleargs}"; fi (snip) The barudrate is 115200. Of course, I re-checked my connection between USB-UART serial cable and UART2 GPIO pins (USB-UART RX to GP7C7TX, USB-UART TX to GP7C6 RX). Any information is helpful and appreciated. Thanks. ---- Referenced Doc: https://docs.armbian.com/User-Guide_Allwinner_overlays/#example-bootarmbianenvtxt-contents my armbianEnv.txt: I added console=serial. verbosity=1 console=serial overlay_prefix=rockchip overlays=i2c1 i2c4 spi2 spidev2 uart1 uart2 rootdev=UUID=(stripped) rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u USB UART Cable: FTDI TTL-232R-3V3 Board Product: ASUS Tinker Board (Power supply via GPIO, 5V4A) Armbian Image File: Armbian_20.05.2_Tinkerboard_buster_current_5.4.44_minimal.img.xz OS Info: root@tinkerboard:/boot# cat /etc/armbian-release # PLEASE DO NOT EDIT THIS FILE BOARD=tinkerboard BOARD_NAME="Tinkerboard" BOARDFAMILY=rockchip BUILD_REPOSITORY_URL=https://github.com/armbian/build BUILD_REPOSITORY_COMMIT=2efd215a DISTRIBUTION_CODENAME=buster DISTRIBUTION_STATUS=supported VERSION=20.05.2 LINUXFAMILY=rockchip BRANCH=current ARCH=arm IMAGE_TYPE=stable BOARD_TYPE=conf INITRD_ARCH=arm KERNEL_IMAGE_TYPE=Image root@tinkerboard:/boot# uname -a Linux tinkerboard 5.4.44-rockchip #20.05.2 SMP PREEMPT Wed Jun 3 10:43:15 CEST 2020 armv7l GNU/Linux
  8. Hello people, I use a Tinker Board as a low power desktop computer for browsing, office documents and general tinkering, and after all this time it got personalized enough to worry about loosing all this setup and it is a hassle to just overwrite everything every time a new image comes around. Was wondering if it is possible to use apt dist-upgrade as means to get from Bionic Desktop 5.4 to Focal Desktop 5.4 as can be done on x86 platforms without breaking everything?
  9. I logged an issue a little while ago with Armbian running on the Tinkerboard that the screen when rotated 90 degrees couldn't draw the screen at any speed. I have been playing with a few alternatives incl going back to the original tinkeros. All have issues so I was delighted to see the FOCAL port. I am using the recommended Waveshare 7" touchscreen that you advertise on the home page as tested 3rd party hardware. Both the desktop and the server versions of Focal come up with the error Configure crtc 0 failed setting mode when I manually set the supported resolution of 1024 x 600 at 60Hz using xrandr Exactly the same settings on TinkerOS works perfectly., but has many other issues! In the /var/log/Xorg.0.log file there is an message Allocate new frame buffer 1024 x 600 stride failed to set mode : Invalid argument. I used cvt to generate the modeline using settings 1024 600 60 then I used xrandr --newmode and added the modeline xrandr --addmode HDMI-1 1024x600_60.00 When I set the output to use this setting xrandr --output HDMI-1 --mode "1024x600_60.00" I get the error crtc 0 failed. As mentioned this works on TinkerOS and is the device that is included in the tested 3rd party hardware. What I am doing wrong? Thanks in advance.
  10. Hello people, I have an Asus Tinker Board S and decided to use the Mainline Armbian for this board, love the new panfrost driver but seems it is glitching all over the place, icons in the menu disappear and reappear when mouse hovers over them, tick boxes do not show if they are ticked and only flicker when mouse is over them and applications menu keep redrawing all over when trying to use among the most prominent problems. Other operating systems work well in this matter. Anyone else is having these problems with the mainline 5.4.28 kernel build?
  11. However, Armbian is configured to provide only spidev2.0, while TinkerOS can have spidev0.0, spidev0.1, spidev2.0 and spidev2.1 all enabled at the same time as long as you disable UART4 which shares GPIO header pins with SPI0. In the TinkerOS case, there is a config tool which edits a small and straightforward text file in /boot/ containing lines such as "intf:spi0=on" or "intf:uart4=off". The corresponding Armbian file seems to be /boot/armbianEnv.txt - possibly with overlays=... lines and DTS files. There also is a tool called armbian-add-overlay to load (at runtime?) DTS files...
  12. So recently I decided to use my (quite old) tinker board, I downloaded the last armbian (desktop, 4.4.213) OS, managed to install a vncserver (x11vnc) and also to use it without a screen plugged in it. And now I would like to turn it into a urbackup server, but I got some error with mdadm, "Module md_mod not found in directory /lib/modules/4.4.213-rockchip". I tried to use this forum to find a solution (https://github.com/armbian/build), but I couldn't make it work. When i tipe ´´git clone https://github.com/armbian/build´´ it stop around 7% at resolving deltas, and it just freeze. Someone could have any idea how to solve this issue?? And i can't get my armbianmonitor link to paste...... Thanks guys.
  13. If anyone has troubles with HDMI when using 5.x kernels, and has enough skills to recompile an armbian, give this a try : https://github.com/Miouyouyou/build And then either answer here, or in the bug report : https://github.com/armbian/build/pull/1887
  14. So I have armbian installed on a tinkerboard and have had absolutely no issues with it until I bought a new Samsung 7000 series TV (2019). For some reason this TV does not recognize the signal coming from the tinkerboard. For the life of me I cannot figure out how to get this to work. I notice a few references online about being able to force a resolution but nothing related to the rockchip boards. Is there an equivalent way to force a display resolution as in this article? https://docs.armbian.com/Hardware_Allwinner/#how-to-reconfigure-video-output I'm running 4.19.21-rockchip 5.76 I've also tried kernel 5.4.28 as well and it's the same issue. Just for kicks I loaded Lakka on there and it works just fine so I know the board itself is working properly. I don't even know where to begin. I was hoping someone could chime in and point me in the right direction.
  15. Hi, I installed "Armbian_20.02.7_Tinkerboard_buster_current_5.4.28_minimal" at my tinkerboard and, in order to enable uart 4, I had to rebuild the kernel onboard (from linux-source-current-rockchip_20.02.7_all.deb). The uart 4 came alive but the processor serial number now is missing from cpuinfo (printing 0000000000). How can I bring it up again?
  16. Topic to discuss RK3288 overlays, primarily concerning ASUS Tinker Board, the MiQi is technically EOL and has very little GPIO anyway, and TV boxes are more or less sealed. Kernel 4.19 will be the pilot for this, the discussion now that it seems to be working thanks to @martinayotte and @zador.blood.stained's feedback and examples is what to overlay. For testing/debugging I started with some ASUS overlays for RTC and 1wire. Easy ones: spidev out of the default tree but as default overlays. instead of making 1 overlay and messing with parameters, just make 2 overlays DAC's: I don't have a lot of hardware to play with, but @gkkpch has contributed to the existing ASUS overlays, if we ask super nicely maybe we'll get some help. I2S on mainline is a question Harder ones: RPI display: I almost got this working on Mainline, I need to return to it, make it work, and make it an overlay. Cameras: I honestly don't know if this is actually possible, I need to look at the drivers a bit more closely. Original Content from Split:
  17. Hi. I installed Armbian_20.02.1_Tinkerboard_bionic_current_5.4.20_desktop on my TinkerBoard (not S) and get weird screen state (white, then growing black circle in the middle). I tried Armbian_20.02.1_Tinkerboard_bionic_legacy_4.4.213_desktop and it works very good, but I still want to test vulkan driver, so I updated only kernel to 4.19 (install linux-image-next-rockchip, linux-header-next-rockchip, linux-dtb-next-rockchip and delete 3 old packages). After reboot I got same screen. Is it known bug? Can it be related, that I'm using HDMI-to-VGA adapter? Can you help me to fix it or get usefull logs?
  18. I have a TinkerBoard S. In Bionic Desktop (kernel 4.4), the wireless icon menu lists two devices: wlan0 (which is the expected interface) and p2p0: I don't know this one, but it is always chosen for auto-connecting to the local wireless lan, receiving a random IP and not the one I configured on the router. I can then manually connect to the network with the wlan0 interface the IP is correct. How do I disable / remove / anyway stop that p2p0 interface to "steal" the network connection?
  19. I used sudo swapoff -a as suggested in this thread: but the setting isn't persisted, and upon reboot sudo swapon --summary shows a partition There's no "swap" text in my /etc/fstab I'm trying to install Kubernetes, so I need to disable swap.
  20. Hello, I own a Tinker Board S (bought one or two years ago) attached to a Sony Bravia KDL 22EX320 TV by HDMI, which has a native resolution of 1388x768 pixels. Bionic desktop with kernel 5.4 (got from https://dl.armbian.com/tinkerboard/Bionic_current_desktop) didn't properly recognize the TV resolution, but set it to 1920x1024. If I run xrandr --props the resolution is not listed. I'm posting because I'm almost sure that the old TinkerOS 2.0.8 (that I installed with the board) recognized the TV resolution correctly - it anyway boots to desktop without requiring interaction, so not being able to read the text at the edges of the console is not a big issue - and I just tested that the current 2.1.11 does too: they both start in 1920x1024, but the Monitor settings windows lists 1360x768. Back to Armbian, I however managed to create the default user and to get to the Bionic desktop; I'd like to add that the display settings window should have a "Test" function that reverts to the previous settings if the new aren't confirmed, because if the chosen resolution isn't supported, the screen stays black.
  21. I have Tinker Board S. I have been using both Tinker OS and Armbian for a while. Recently I upgraded to 5.4.28-rockchip. I noticed that randomly and frequently when I watch cnn.com or other media, my video would freeze. Initially I thought the firefox or chromium crashes. However, later, I realized it was the network issue. Other devices were still able to connect to the internet. When I checked the ifconfig, the network devices still showed proper connection. However, there is no way to ping any URLs. Disconnecting/reconnecting network does not fix the issue. The only fix was reboot. How can I troubleshoot this issue? I was trying to do armbianmonitor but at that time, there was no network at all. http://ix.io/2fVR This is armbianmonitor after reboot and no problem at all. for baseline reference.
  22. Hello togehter, i had 2 ASUS TinkerBoard S and I want to work with your software... The Software was via Etcher installed on several MC - Cards (16, 32 and 64 GB), but it still not working. The POWER - LED is red and the both LEDs on GBIC - Interface are blinking green and yellow :-( So, what kind of problems that I have here. I tried out several IMAGE from your WebSite - but no one won't to work with me :-( Best regards Matthias
  23. Using Linux tinkerboard 4.19.69-rockchip #5.95 SMP PREEMPT Mon Sep 2 07:34:36 CEST 2019 armv7l armv7l armv7l GNU/Linux Using glxgears as a test case.. I get 60fps without the screen rotated. If I rotate the screen right or left the frame rate drops to 4fps. That's on a fresh boot with nothing else running. I tested TinkerOS on the same board and it works fine rotated. My Raspberry PI 4 works fine rotated as well. What could be the problem with Armbian?
  24. Anyone have an issue where on a fresh install with apt update and upgrade I create a hotspot then have openvpn connect on boot. It works fine as a hotspot with 200mbps up and down but when the traffic is routes through a vpn by connecting openvpn the board will crash/become unresponsive if the upload is used heavily. Works great until I run a speedtest and on the upload the board will crash. Normal use is fine even pegging download causes no issue. Le potato s905x works amazing in this regard and never crashes period. Is this a known bug?
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines