Search the Community

Showing results for tags 'mainline'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements & first aid
    • Announcements
    • Board doesn't start
  • Community forums
    • Common issues
    • Peer to peer technical support
    • Feature Requests
    • TV boxes
    • General chit chat
  • Bug tracker
    • Allwinner A20
    • Allwinner H2 & H3
    • Allwinner H5 & A64
    • Armada A388, A3700
    • Amlogic S905(x)
    • NXP (Freescale)
    • Rockchip 3288 & 3328
    • Other supported boards
  • Development
    • Allwinner H6
    • Rockchip 3399
    • Development

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 869 results

  1. I'm trying to disable the HDMI output on my A20-OlinuXino LIME. I have tried to disable the HDMI from the u-boot console using this commands : -setenv video-mode sunxi:1024x768-24@60,monitor=none -saveenv I have also tried to recompile the boot.cmd but even in this way nothing. Corrently i'm using : Linux lime 4.19.62-sunxi #5.92 Where is my mistake? Thanks in advance.
  2. According to the specs of the OP PC Plus, it only supports 32GB micro SD. My only 32GB that I have, that I was booting from on the OP PC plus eventually got corrupted, and will not boot, can't format and install armbian or anything. What are my options? Can I somehow boot from a 64GB micro sdcard, or USB from a fresh armbian image write?
  3. Basic information: Board: Orange Pi Plus 2e Image: Armbian_19.11.3_Orangepiplus2e_buster_current_5.3.9.img Issue: No sound on HDMI output There has been quite a few suggestions for this issue here and and OrangePi Plus and none works for me. Tried following: 0. sudo apt-get update && upgrade 1. Created and Changed /etc/asound.conf Version 1: pcm.!default { type hw card 1 } ctl.!default { type hw card 1 } Version 2: pcm.!default { type hw card 1 device 0 } ctl.!default { type hw card 1 } 2. Verified user is included in group 'audio' and has permissions groups raj tty disk dialout sudo audio video plugdev games users systemd-journal input netdev ssh cat /proc/asound/cards 0 [Codec ]: H3_Audio_Codec - H3 Audio Codec H3 Audio Codec 1 [allwinnerhdmi ]: allwinner_hdmi - allwinner,hdmi allwinner,hdmi cat /proc/asound/pcm 00-00: CDC PCM Codec-0 : CDC PCM Codec-0 : playback 1 : capture 1 01-00: 1c22800.i2s-i2s-hifi i2s-hifi-0 : 1c22800.i2s-i2s-hifi i2s-hifi-0 : playback 1 cat /proc/asound/devices 0: [ 0] : control 16: [ 0- 0]: digital audio playback 24: [ 0- 0]: digital audio capture 32: [ 1] : control 33: : timer 48: [ 1- 0]: digital audio playback cat /proc/asound/modules 0 (efault) 1 snd_soc_simple_card Output of: alsamixer -c 1 controls Outputs: asound$ amixer -c 1 controls numid=2,iface=PCM,name='ELD' numid=1,iface=PCM,name='Playback Channel Map' amixer set PCM 10% unmute amixer: Unable to find simple control 'PCM',0 amixer -c 1 set PCM 2dB+ amixer: Unable to find simple control 'PCM',0 Reinstalled - alsa-utils cat /var/lib/alsa/asound.state state.sun4icodec { control.1 { iface MIXER name 'Power Amplifier Volume' value 32 comment { access 'read write' type INTEGER count 1 range '0 - 63' dbmin -9999999 dbmax 0 dbvalue.0 -3100 } } control.2 { iface MIXER name 'Left Mixer Left DAC Playback Switch' value false comment { access 'read write' type BOOLEAN count 1 } } control.3 { iface MIXER name 'Right Mixer Right DAC Playback Switch' value false comment { access 'read write' type BOOLEAN count 1 } } control.4 { iface MIXER name 'Right Mixer Left DAC Playback Switch' value false comment { access 'read write' type BOOLEAN count 1 } } control.5 { iface MIXER name 'Power Amplifier DAC Playback Switch' value true comment { access 'read write' type BOOLEAN count 1 } } control.6 { iface MIXER name 'Power Amplifier Mixer Playback Switch' value true comment { access 'read write' type BOOLEAN count 1 } } control.7 { iface MIXER name 'Power Amplifier Mute Switch' value true comment { access 'read write' type BOOLEAN count 1 } } } state.SPDIF { control { } } state.Codec { control.1 { iface MIXER name 'DAC Playback Volume' value 45 comment { access 'read write' type INTEGER count 1 range '0 - 63' dbmin -7308 dbmax 0 dbvalue.0 -2088 } } control.2 { iface MIXER name 'Line In Playback Volume' value 3 comment { access 'read write' type INTEGER count 1 range '0 - 7' dbmin -450 dbmax 600 dbvalue.0 0 } } control.3 { iface MIXER name 'Line Out Playback Volume' value 17 comment { access 'read write' type INTEGER count 1 range '0 - 31' dbmin -9999999 dbmax 0 dbvalue.0 -2100 } } control.4 { iface MIXER name 'Line Out Playback Switch' value.0 true value.1 true comment { access 'read write' type BOOLEAN count 2 } } control.5 { iface MIXER name 'Mic2 Playback Volume' value 3 comment { access 'read write' type INTEGER count 1 range '0 - 7' dbmin -450 dbmax 600 dbvalue.0 0 } } control.6 { iface MIXER name 'Mic2 Boost Volume' value 4 comment { access 'read write' type INTEGER count 1 range '0 - 7' dbmin 0 dbmax 4200 dbvalue.0 3300 } } control.7 { iface MIXER name 'Mic1 Playback Volume' value 3 comment { access 'read write' type INTEGER count 1 range '0 - 7' dbmin -450 dbmax 600 dbvalue.0 0 } } control.8 { iface MIXER name 'Mic1 Boost Volume' value 4 comment { access 'read write' type INTEGER count 1 range '0 - 7' dbmin 0 dbmax 4200 dbvalue.0 3300 } } control.9 { iface MIXER name 'ADC Gain Capture Volume' value 3 comment { access 'read write' type INTEGER count 1 range '0 - 7' dbmin -450 dbmax 600 dbvalue.0 0 } } control.10 { iface MIXER name 'DAC Playback Switch' value.0 true value.1 true comment { access 'read write' type BOOLEAN count 2 } } control.11 { iface MIXER name 'DAC Reversed Playback Switch' value.0 false value.1 false comment { access 'read write' type BOOLEAN count 2 } } control.12 { iface MIXER name 'Line In Playback Switch' value.0 false value.1 false comment { access 'read write' type BOOLEAN count 2 } } control.13 { iface MIXER name 'Mic1 Playback Switch' value.0 false value.1 false comment { access 'read write' type BOOLEAN count 2 } } control.14 { iface MIXER name 'Mic2 Playback Switch' value.0 false value.1 false comment { access 'read write' type BOOLEAN count 2 } } control.15 { iface MIXER name 'Mixer Capture Switch' value.0 false value.1 false comment { access 'read write' type BOOLEAN count 2 } } control.16 { iface MIXER name 'Mixer Reversed Capture Switch' value.0 false value.1 false comment { access 'read write' type BOOLEAN count 2 } } control.17 { iface MIXER name 'Line In Capture Switch' value.0 false value.1 false comment { access 'read write' type BOOLEAN count 2 } } control.18 { iface MIXER name 'Mic1 Capture Switch' value.0 false value.1 false comment { access 'read write' type BOOLEAN count 2 } } control.19 { iface MIXER name 'Mic2 Capture Switch' value.0 false value.1 false comment { access 'read write' type BOOLEAN count 2 } } control.20 { iface MIXER name 'Line Out Source Playback Route' value.0 Stereo value.1 Stereo comment { access 'read write' type ENUMERATED count 2 item.0 Stereo item.1 'Mono Differential' } } } state.allwinnerhdmi { control.1 { iface PCM name 'Playback Channel Map' value.0 0 value.1 0 value.2 0 value.3 0 value.4 0 value.5 0 comment { access read type INTEGER count 6 range '0 - 36' } } control.2 { iface PCM name ELD value '0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000' comment { access 'read volatile' type BYTES count 128 } } No luck till date. Thanks Rajesh
  4. Hi everybody, I need your help in setting the default values of some or all GPIO Pin, so that it will be always activated after reboot instead of deactivated like the default is today. The reason for this is that I've connected a relaisboard to some GPIO Pins that will need "1" to be deactivated . Everything works fine, I can control and work with these Pins like needed by using "1" for OFF and "0" for ON. After booting up my BPI I initialize the needed GPIO Pins via export the pins. That will create virtual directories for these Pins with these defaults: direction -> in value -> 0 Like I mentioned, my relaiseboard need a logical 0 to be activated, so when I switch the direction to out, my motor on the related relay start to spin. Doing a sequence of create via export, set direction to out and set value to 1 will we fast, but will activate the motor for a short time, this is what I must avoid! Instead of rebuilding the HW for using the value "1" to been activated instead of "0" I try to change the GPIO default value from 0 to 1 what means deactivated/not active for my relaisboard. Since this is a BPI M2 Zero and there are no newer images I think I need to do this via the script.bin file. I've found for my pin PA08 these entries, but have no idea what default means what: smc_sda = port:PA08<2><default><default><default> scr_sda = port:PA08<2><default><default><default> Please can someone help me doing this or point me to an example how this must be done ? Regards WolliK
  5. I installed the latest 5.4.8 Buster Desktop image on my Orange Pi +2e board but find the Mali drivers are (Utgard) missing or not loaded. I have tried to follow every possible links including (https://linux-sunxi.org/Mali_binary_driver) related to get VDPAU / VAAPI and GPU but with very little success. I want to have HW acceleration enabled for playing MPEG in full screen mode 1920x1280 resolution using mpv. The frame drops are significant. Questions: Are Mali drivers included in this build? If it is then how can I go about adding those drivers. Is there any licencing issues in adding Mali drivers to the Armbian image? Is there any chances of Lima drivers being included in future releases? There are Mali drivers available on ARM developer site that provides GPU Kernel Device drivers. Can I use them to build the custom Armbian image? Appreciate any help in this matter. Thanks Rajesh
  6. Is anyone still working with cubietruck? I installed the latest mainline image over Christmas expecting it to have the cedrus driver but apparently it does not. I thought that everything except HDMI audio should be working in mainline now. So I installed the latest legacy image. It plays videos well but bluetooth doesnt work. I switched it on in armbian-config and 'rfkill list' shows it as not disabled but the bluetooth manager shows no adapter and search is grayed out. This is a regression as it used to work to some extent. Also, very importantly for me, neither image switch over to battery power when the AC goes out. This also used to work on legacy, unless it was cubian that worked and armbian never did, I should keep notes...
  7. Armbianmonitor for 5.4.6: http://ix.io/260C From switching between 4.19.x and 5.4.x kernels I noticed that the lower cpu frequencies got missing. It should start at 120MHz like this: root@horangepione:~# uname -a Linux honeypot2 4.19.84-sunxi #19.11.3 SMP Mon Nov 18 18:39:42 CET 2019 armv7l GNU/Linux root@horangepione:~# cpufreq-info -o minimum CPU frequency - maximum CPU frequency - governor CPU 0 120000 kHz ( 11 %) - 1008000 kHz (100 %) - ondemand CPU 1 120000 kHz ( 11 %) - 1008000 kHz (100 %) - ondemand CPU 2 120000 kHz ( 11 %) - 1008000 kHz (100 %) - ondemand CPU 3 120000 kHz ( 11 %) - 1008000 kHz (100 %) - ondemand Though on 5.4.x the minimum frequency is 480MHz. Since the default cpufrequtils file was not there I created one: cat /etc/default/cpufrequtils # WARNING: this file will be replaced on board support package (linux-root-...) upgrade ENABLE=true MIN_SPEED=120000 MAX_SPEED=1200000 GOVERNOR=ondemand It seems to have an effect because when changing the minimum frequency it clocks up as it should. Frequencies beyond 1.01GHz missing as well but that is a different story...I guess. Cheers Werner
  8. Hello, I am going to start looking into running Docker on OPi +2E soon, but before I get stuck in details I would like to know whether other people have had experience with it..? In particular, I would like to know what to expect when trying to run Docker on an OPi +2E. Having a report from prior experience would be helpful. As far as I understand, Docker is still in pretty much experimental stages on ARM. Kind regards, @ullbeking
  9. Hi everyone! I'm trying to build my own distribution for the Pine64, and I use armbian as a working reference. I'm able to compile ATF + U-boot + Kernel + rootfs and the board actually boots and I get a console over the serial interface and over HDMI. The problem is that GbE Ethernet does not work. It appears that the 8211 phy is not powered. The good guys on the pine64 IRC pointed to the ATF, where the DC1SW regulator should be turned on in order to power the phy. On armbian everything works just fine. I think I messed up something in the build - wrong version / config / dts in either ATF, U-boot or the linux kernel. I tried to understand how the armbian Pine64 image was built - but since I'm totally new to armbian I got lost pretty quick. So basically I want to know how can I find the following information: 1. What version + platform of ATF is used? Is it from the official ARM repo, or some fork? 2. What version + config + dts of U-Boot is used? 3. What version + config + dts of Linux is used? Is it mainline / LTS kernel? are there any special patches applied that I should be aware? I know it is a bit weird question to ask here, but I really want to learn how to create my distro, and armbian is a great reference.
  10. Hi guys, I am trying to use TP-Link dongle WN722N v3 as an access point . I am using Nano Pi Neo Core EMMC with expansion board running Armbian Buster with Linux 5.3.9-sunxi . The device can detect wifi signals nearby as seen on nmtui in managed mode . I followed the instructions on https://forum.odroid.com/viewtopic.php?f=52&t=25472&sid=84d2b8f1e7ad477e9907591eb7fb030d to configure as access point . However , I get an error every time like this . root@Cyborg:~# nmcli connection up HotSpot ifname wlx503eaaa2df7b Error: Connection activation failed: Connection 'HotSpot' is not available on device wlx503eaaa2df7b because profile is not compatible with device (the device does not support Access Point mode) Output of dmesg | tail -n 20 on inserting the dongle . [ 1225.431164] ---[ end trace 91514764a9d606b4 ]--- [ 1225.431176] RTW: rtw_wdev_free(wdev=3fa7fa4c) [ 1225.431184] RTW: rtw_wiphy_free(phy1) [ 1225.431222] RTW: rtw_usb_primary_adapter_deinit((null)) [ 1225.431227] RTW: rtw_dev_unload: bup==_FALSE [ 1225.431239] RTW: +r871xu_dev_remove, hw_init_completed=0 [ 1225.431664] RTW: WARN free_recv_skb_queue not empty, 8 [ 1225.431719] RTW: usb attached..., try to reset usb device [ 1225.557473] usb 3-1: reset high-speed USB device number 3 using ehci-platform [ 1225.714010] In rtw_drv_init return -ENODEV [ 1225.714340] Chip Version Info: CHIP_8188E_Normal_Chip_TSMC_D_CUT_1T1R_RomVer(0) [ 1225.763898] r8188eu 3-1:1.0 wlx503eaaa2df7b: renamed from wlan0 [ 1226.629967] MAC Address = 50:3e:aa:a2:df:7b root@Cyborg:~# I know the dongle works because I used it on a Nano Pi Duo running FriendlyARM's running Ubuntu Linux kernel version 4.14.0 . I am really confused . Is it a kernel issue ? My main intention is to use some GPIOs using Wiring Pi and run an apache webserver on it . I want to use the dongle to serve HTML pages over a hotspot . Any help is appreciated .
  11. Hi guys, I have recently bought a Rock64 to improve the performance of my VPN gateway. First tests look very promising as you can see here: root@rock64:~# openssl speed -evp aes-128-cbc -elapsed You have chosen to measure elapsed time instead of user CPU time. Doing aes-128-cbc for 3s on 16 size blocks: 15394610 aes-128-cbc's in 2.99s Doing aes-128-cbc for 3s on 64 size blocks: 12591175 aes-128-cbc's in 3.00s Doing aes-128-cbc for 3s on 256 size blocks: 6719021 aes-128-cbc's in 3.00s Doing aes-128-cbc for 3s on 1024 size blocks: 2448108 aes-128-cbc's in 3.00s Doing aes-128-cbc for 3s on 8192 size blocks: 352617 aes-128-cbc's in 3.00s Doing aes-128-cbc for 3s on 16384 size blocks: 177668 aes-128-cbc's in 3.00s OpenSSL 1.1.1d 10 Sep 2019 built on: Sat Oct 12 19:56:43 2019 UTC options:bn(64,64) rc4(char) des(int) aes(partial) blowfish(ptr) compiler: gcc -fPIC -pthread -Wa,--noexecstack -Wall -Wa,--noexecstack -g -O2 -fdebug-prefix-map=/build/openssl-H2OJIf/openssl-1.1.1d=. -fstack-protector-strong -Wformat -Werror=format-security -DOPENSSL_USE_NODELETE -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_BN_ASM_MONT -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -DVPAES_ASM -DECP_NISTZ256_ASM -DPOLY1305_ASM -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 The 'numbers' are in 1000s of bytes per second processed. type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes 16384 bytes aes-128-cbc 82379.18k 268611.73k 573356.46k 835620.86k 962879.49k 970304.17k root@rock64:~# openvpn --genkey --secret /tmp/secret root@rock64:~# time openvpn --test-crypto --secret /tmp/secret --verb 0 --tun-mtu 20000 --cipher aes-256-cbc Sat Dec 14 10:26:40 2019 disabling NCP mode (--ncp-disable) because not in P2MP client or server mode real 0m4.978s user 0m4.945s sys 0m0.032s Unfortunately when executing a simple curl, the throughput is very low: root@rock64:~# curl -L https://speed.hetzner.de/1GB.bin > /dev/null % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 2 1000M 2 29.9M 0 0 2090k 0 0:08:09 0:00:14 0:07:55 3106k When using Ubuntu 18.04 Bionic I am reaching speeds of 8,4MByte/s. I have checked the openvpn process and it seems that it is only using 25% of CPU, whereas when using in Ubuntu it is using 50-60%. What are the differences here and why is Armbian limiting the process to 25%? Thanks! Bye
  12. I'm using g_ether to connect OrangePiPc+ to network over USB OTG. On legacy kernel, that was giving 140 Mbits/sec IN (download from network to OrangePiPc+) and 170 Mbits/sec OUT. After upgrading to mainline kernel 4.19.62 (or 5.3.9), IN throughput degraded to 93-98 Mbits/sec (while OUT improved reaching up to 210 Mbits/sec in CDC EEM mode). This easily reproducible on both my boards OrangePiPc+ and OrangePiZero with latest Bionic images (clean installations + "modprobe g_ether iProduct="Linux-USB Ethernet/RNDIS Gadget" iManufacturer="Netchip Technology, Inc." dev_addr=02:81:05:F0:5C:24 host_addr=02:81:05:F0:5C:23 use_eem=0" ). Any ideas where is the bottleneck and how to resolve it? Tried several USB cables and USB host devices. Throughput measured by iperf; samba and nfs are showing the same. ifconfig stats indicating 0 tx/rx errors.
  13. Is it possible that there have been some image changes that broke the XR819 wifi completely? The available images for download on the Armbian page (5.3 server, and 5.4 minimal) as well as a custom built "legacy" branch linux-4.19 image all show the same behavior, The wlan0 interface is not active and it's not possible to bring it up. And dmesg shows that module has been initialized but not much more. Armbianmonitor support info: 5.3.9 official buster server image: http://ix.io/240Y 4.19.88 self-built, two days ago, legacy branch: http://ix.io/240U Everything below is from the official image, but the 4.19 image shows the exact same It is definitely not a hardware issue, I have a SD card with a an older 4.19.72 image (when the branch was still called "next") that works just fine. ifconfig -a ifconfig root@orangepizero:~# ifconfig wlan0 up SIOCSIFFLAGS: Invalid argument root@orangepizero:~# rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no root@orangepizero:~# journalctl -b | grep xradio Nov 19 08:08:00 orangepizero kernel: xradio_wlan mmc1:0001:1: Input buffers: 30 x 1632 bytes Nov 19 08:08:00 orangepizero kernel: xradio_wlan mmc1:0001:1: Firmware Label:XR_C01.08.0043 Jun 6 2016 20:41:04 Nov 19 08:08:28 orangepizero NetworkManager[1057]: <info> [1574150908.3204] rfkill0: found WiFi radio killswitch (at /sys/devices/platform/soc/1c10000.mmc/mmc_host/mmc1/mmc1:0001/mmc1:0001:1/ieee80211/phy0/rfkill0) (driver xradio_wlan) root@orangepizero:~# uname -a Linux orangepizero 5.3.9-sunxi #19.11.3 SMP Mon Nov 18 18:49:43 CET 2019 armv7l GNU/Linux
  14. Hello guys, I am experiencing such a problem: When I boot my orangepi it starts and it is visible in the router's page view getting IP with dhcp. As soon as I connect over ssh (at least this is the way to trigger it, not sure if it is hapening automatically after a while), the device disappears from the network and it is no more available! I have seen this behaviour happening on 2 different routers. Then I rebooted the device again and in the router config I put the same IP statically linked to the device and I tried to connect over ssh and it worked without disappearing anymore. So it sounds like a bug somewhere using dhcp protocol. Is someone else experienced such problem? How I can help to definitely fix this annoying bug? Thanks, Gianni
  15. Hello, After upgrade Armbian (4.19.69-meson64) to Armbian Buster with Linux 5.3.11-meson64 warning messages shows up on boot in dmesg: ... [ 1.973932] Key type encrypted registered [ 1.985109] dwc2 c9000000.usb: c9000000.usb supply vusb_d not found, using dummy regulator [ 1.985153] dwc2 c9000000.usb: c9000000.usb supply vusb_a not found, using dummy regulator [ 1.986616] phy phy-c0000000.phy.0: USB ID detect failed! [ 1.986623] phy phy-c0000000.phy.0: phy poweron failed --> -22 [ 1.986643] ------------[ cut here ]------------ [ 1.986700] WARNING: CPU: 3 PID: 68 at drivers/regulator/core.c:2036 _regulator_put+0x34/0xd8 [ 1.986702] Modules linked in: [ 1.986709] CPU: 3 PID: 68 Comm: kworker/3:1 Not tainted 5.3.11-meson64 #19.11.3 [ 1.986711] Hardware name: Hardkernel ODROID-C2 (DT) [ 1.986719] Workqueue: events deferred_probe_work_func [ 1.986724] pstate: 60000005 (nZCv daif -PAN -UAO) [ 1.986728] pc : _regulator_put+0x34/0xd8 [ 1.986732] lr : _regulator_put+0x34/0xd8 [ 1.986733] sp : ffff000011683af0 [ 1.986735] x29: ffff000011683af0 x28: 0000000000000000 [ 1.986739] x27: ffff80007f2ac6b8 x26: ffff000011106530 [ 1.986743] x25: 0000000000000000 x24: 0000000000000009 [ 1.986746] x23: ffff000011683bb8 x22: ffff80006a1c2b00 [ 1.986750] x21: ffff0000113916c8 x20: ffff80006a1c2d00 [ 1.986753] x19: ffff80006a1c2d00 x18: ffff0000113ae000 [ 1.986756] x17: 000000003ae42590 x16: 00000000ed672116 [ 1.986760] x15: 00000000fffffff0 x14: ffff0000114be0fa [ 1.986763] x13: 0000000000000000 x12: ffff0000114bd000 [ 1.986767] x11: ffff0000113ae000 x10: ffff0000114bd748 [ 1.986770] x9 : 0000000000000000 x8 : 0000000000000001 [ 1.986774] x7 : 00000000000000eb x6 : ffff0000114bd000 [ 1.986777] x5 : 0000000000000000 x4 : 0000000000000000 [ 1.986780] x3 : 00000000ffffffff x2 : 3c797d94ab3f0f00 [ 1.986783] x1 : 0000000000000000 x0 : 0000000000000024 [ 1.986787] Call trace: [ 1.986792] _regulator_put+0x34/0xd8 [ 1.986796] regulator_put+0x2c/0x40 [ 1.986800] regulator_bulk_free+0x30/0x50 [ 1.986805] devm_regulator_bulk_release+0x18/0x20 [ 1.986810] release_nodes+0x1b0/0x220 [ 1.986814] devres_release_all+0x34/0x58 [ 1.986818] really_probe+0x1b8/0x3d0 [ 1.986822] driver_probe_device+0xdc/0x130 [ 1.986825] __device_attach_driver+0x88/0x108 [ 1.986828] bus_for_each_drv+0x78/0xc8 [ 1.986831] __device_attach+0xd4/0x158 [ 1.986834] device_initial_probe+0x10/0x18 [ 1.986837] bus_probe_device+0x90/0x98 [ 1.986840] deferred_probe_work_func+0x88/0xd8 [ 1.986846] process_one_work+0x1e0/0x338 [ 1.986850] worker_thread+0x240/0x440 [ 1.986854] kthread+0x120/0x128 [ 1.986859] ret_from_fork+0x10/0x18 [ 1.986861] ---[ end trace 629d4ecc13425951 ]--- [ 1.986907] ------------[ cut here ]------------ [ 1.986942] WARNING: CPU: 3 PID: 68 at drivers/regulator/core.c:2036 _regulator_put+0x34/0xd8 [ 1.986943] Modules linked in: [ 1.986948] CPU: 3 PID: 68 Comm: kworker/3:1 Tainted: G W 5.3.11-meson64 #19.11.3 [ 1.986950] Hardware name: Hardkernel ODROID-C2 (DT) [ 1.986954] Workqueue: events deferred_probe_work_func [ 1.986958] pstate: 60000005 (nZCv daif -PAN -UAO) [ 1.986962] pc : _regulator_put+0x34/0xd8 [ 1.986965] lr : _regulator_put+0x34/0xd8 [ 1.986967] sp : ffff000011683af0 [ 1.986969] x29: ffff000011683af0 x28: 0000000000000000 [ 1.986972] x27: ffff80007f2ac6b8 x26: ffff000011106530 [ 1.986976] x25: 0000000000000000 x24: 0000000000000009 [ 1.986979] x23: ffff000011683bb8 x22: ffff80006a1c2b00 [ 1.986983] x21: ffff0000113916c8 x20: ffff80006a1c2e00 [ 1.986986] x19: ffff80006a1c2e00 x18: ffff0000113ae000 [ 1.986989] x17: 000000003ae42590 x16: 00000000ed672116 [ 1.986993] x15: 00000000fffffff0 x14: ffff0000114be0fa [ 1.986996] x13: 0000000000000000 x12: ffff0000114bd000 [ 1.987000] x11: ffff0000113ae000 x10: ffff0000114bd748 [ 1.987003] x9 : 0000000000000000 x8 : 0000000000000001 [ 1.987006] x7 : 0000000000000118 x6 : ffff0000114bd000 [ 1.987010] x5 : 0000000000000000 x4 : 0000000000000000 [ 1.987013] x3 : 00000000ffffffff x2 : 3c797d94ab3f0f00 [ 1.987016] x1 : 0000000000000000 x0 : 0000000000000024 [ 1.987019] Call trace: [ 1.987023] _regulator_put+0x34/0xd8 [ 1.987027] regulator_put+0x2c/0x40 [ 1.987030] regulator_bulk_free+0x30/0x50 [ 1.987034] devm_regulator_bulk_release+0x18/0x20 [ 1.987038] release_nodes+0x1b0/0x220 [ 1.987041] devres_release_all+0x34/0x58 [ 1.987044] really_probe+0x1b8/0x3d0 [ 1.987048] driver_probe_device+0xdc/0x130 [ 1.987051] __device_attach_driver+0x88/0x108 [ 1.987053] bus_for_each_drv+0x78/0xc8 [ 1.987056] __device_attach+0xd4/0x158 [ 1.987059] device_initial_probe+0x10/0x18 [ 1.987062] bus_probe_device+0x90/0x98 [ 1.987065] deferred_probe_work_func+0x88/0xd8 [ 1.987069] process_one_work+0x1e0/0x338 [ 1.987072] worker_thread+0x240/0x440 [ 1.987075] kthread+0x120/0x128 [ 1.987078] ret_from_fork+0x10/0x18 [ 1.987081] ---[ end trace 629d4ecc13425952 ]--- [ 1.987135] dwc2: probe of c9000000.usb failed with error -22 [ 1.987536] dwc2 c9100000.usb: c9100000.usb supply vusb_d not found, using dummy regulator [ 1.987581] dwc2 c9100000.usb: c9100000.usb supply vusb_a not found, using dummy regulator [ 2.024002] mmc0: new HS200 MMC card at address 0001 ... I haven't had any system hangups yet but I am worried.
  16. 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:
  17. I have a 1 GB Renegade board and downloaded Armbian_19.11.3_Renegade_buster_current_5.3.11 image to install. Noticed it was only 510MB of RAM. Relevant extracts from serial log: U-Boot 2017.09-armbian (Nov 19 2019 - 00:09:05 +0100) Model: Firefly ROC-RK3328-CC DRAM: 510 MiB ____ _ | _ \ ___ _ __ ___ __ _ __ _ __| | ___ | |_) / _ \ '_ \ / _ \/ _` |/ _` |/ _` |/ _ \ | _ < __/ | | | __/ (_| | (_| | (_| | __/ |_| \_\___|_| |_|\___|\__, |\__,_|\__,_|\___| |___/ Welcome to Armbian Buster with Linux 5.3.11-rockchip64 System load: 0.10 0.14 0.06 Up time: 2 min Memory usage: 22 % of 472MB IP: 192.168.11.175 CPU temp: 44°C Usage of /: 5% of 29G [ General system configuration (beta): armbian-config ] Last login: Sat Nov 23 22:48:50 2019 Using armbian-config I downgraded to kernel 4.4.198 and I now have 919MB of RAM. U-Boot 2017.09-armbian (Nov 19 2019 - 00:01:47 +0100) Model: Firefly ROC-RK3328-CC DRAM: 1022 MiB ____ _ | _ \ ___ _ __ ___ __ _ __ _ __| | ___ | |_) / _ \ '_ \ / _ \/ _` |/ _` |/ _` |/ _ \ | _ < __/ | | | __/ (_| | (_| | (_| | __/ |_| \_\___|_| |_|\___|\__, |\__,_|\__,_|\___| |___/ Welcome to Armbian Buster with Linux 4.4.198-rockchip64 System load: 0.10 0.09 0.03 Up time: 2 min Memory usage: 8 % of 919MB IP: 192.168.11.173 CPU temp: 43°C Usage of /: 5% of 29G [ General system configuration (beta): armbian-config ] Ray
  18. Hi, I want to use g_ether on NanoPi Neo Plus2. For Neo Air, I have already figured out how to do this and I can see usb0 in config. But with armbian 5.85 (4.19.38-sunxi64), the same instructions fail at sudo ifconfig usb0 up with the message "usb0: ERROR while getting interface flags: No such device". Could somebody tell me how to activate USB OTG on NanoPi Neo Plus2 and then use g_ether. I think the same holds true for g_serial. This could be an alternative, but I would prever ethernet connection. My target: Connect NanoPi Neo Plus2 with NanoPi Neo Air via Ethernet Thank you for your help! Steps I followed for g_ether:
  19. Hi, I always been an retrorangepi user for my Opi1. but the lastest retrorangepi is stuck at 4.1 (I try the 4.2 slim but it's too slim) and the 4.3 beta also if its named as full, lacks of kodi and many emulators. so, my thought is. What if I build my personal emulationstation + lastest kodi on top of lastest armbian? Can I install armbian and then emustation and kodi? Do I have to install all emulator one by one? or I could use retroarch? Can I setup armbian to boot emustation? I think could be a good thing also for study
  20. 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
  21. Hi, when I try to connect to OPi Zero via USB TTL (PL2303) and run minicom -D /dev/ttyUSB0 -b 115200 -o, it seems to be normal until it booted to the Kernel then it start outputing garbage but when it started without USB TTL it just work normally U-Boot SPL 2019.04-armbian (Jul 16 2019 - 10:53:57 +0200) DRAM: 256 MiB Trying to boot from MMC1 U-Boot 2019.04-armbian (Jul 16 2019 - 10:53:57 +0200) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi Zero DRAM: 256 MiB MMC: mmc@1c0f000: 0, mmc@1c10000: 1 Loading Environment from EXT4... ** File not found /boot/boot.env ** ** Unable to read "/boot/boot.env" from mmc0:1 ** In: serial Out: serial Err: serial Net: phy interface0 eth0: ethernet@1c30000 starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 USB2: USB EHCI 1.00 USB3: USB OHCI 1.0 USB4: USB EHCI 1.00 USB5: USB OHCI 1.0 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 1 for devices... 1 USB Device(s) found scanning bus 2 for devices... 1 USB Device(s) found scanning bus 3 for devices... 1 USB Device(s) found scanning bus 4 for devices... 1 USB Device(s) found scanning bus 5 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found <INTERRUPT> => @� 0,ڕ� 0,ڕ� 0,ڕ@� 0,ڕ� 0,ڕ� 0,ڕ @� 0,ڕ @� 0,ڕ� 0,ڕ� 0,ڕ @� 0,ڕ @� 0,ڕ� 0,ڕ� 0,ڕ @� 0,ڕ� 0,ڕ 0,ڕ0,ڕ0,ڕ 0,ڕ 0�B �$�<INTERRUPT> ,ڕ0,ڕ 0,ڕ0,ڕ 0,ڕ 0,ڕ0,ڕ0,ڕ0,ڕ 0,ڕ0,ڕ 0,ڕ0,ڕ 0,ڕ 0,ڕ0,ڕ0,ڕ 0,ڕ0,ڕ 0,ڕ 0,ڕ0,ڕ0,ڕ 0,ڕ0,ڕ => ���)d� 0,ڕ Unknown command '���)d�' - try 'help' ���)d�!iJ ! )d@�H�$B�I�` ! ���BUnknown command '�B' - try 'help'iJ ! !`!iJ ! !` => �B ���)d�!iJ ! )d@�H�$B�I�` ! ���B(I d�!iJ ! !`<INTERRUPT> =>���)d�"BB` B�X�X� ! !2J!�����$(( �X�X�@I > > !`�!$�����!L<INTERRUPT> �B ���)d�!iJ ! )d@�H�$B�I�` ! ���B(I d�!iJ ! !`��� Unknown command '�B' - try 'help' ���)d�"BB` B�X�X� ! !2J!��ĉ�$((�B ���)d�!iJ ! )d@�H�$B�I�` ! ���B(I d�!iJ��!BB @@If@!�IH!A<INTERRUPT> => &&��> �Ȁ@�H� B�&&��> �Ȁ@�H��&&��> �Ȁ@�H� B�&&��> �Ȁ@�H� B�&&��> �Ȁ@�H��&&��> �Ȁ@�H��&&��> �Ȁ@�H��&&��> �Ȁ@�H��&&��> �Ȁ=>���)d��BJr2H �B� H�B� �*��H�IH!��Ȁ@�H��&&��> �Ȁ@�H��&&��> �Ȁ@�H��&&��> �Ȁ@�H� B�&&��> �Ȁ@�H��&&��> �Ȁ@�H��&&��> �Ȁ@�H��&&��> �Ȁ@�H�B�&&Unknown command '���)d��BJr2H' - try 'help'> �Ȁ@�H��&&��> �Ȁ@�H�B�&&��> �Ȁ@�H�B�&&��> �Ȁ@�H� ��1PR�K!H�B (�($���� Unknown command '��1PR�K!H�B' - try 'help'
  22. Hello, I am using OPI one with Armbian_5.90_Ubuntu_bionic_4.19.57, so I fliped my 7" touch screen display vertically (rotated 180) by modifing: /etc/X11/xorg.conf/01-armbian-defaults.conf and it worked, but the touch doesn't correspond with it (still points as it was before rotation). how can i flip the touch information (x,y) coordinates vertically (rotate by 180)? Regards,
  23. I'm trying, with no success, to make a 3,5 inch tft lcd screen function with an orange pi zero plus (h5) via SPI. I will love if someone could help me diagnose the reason why I'm failing in doing so. The screen in question is a WaveShare knockoff -> link (the pinout can be found at the bottom of the page.) I'm running Armbian buster 5.92 with the kernel 4.19.63 and all packages upgraded. I also have a working serial connection (using the UART pins located next to Ethernet jack on the board) and am using the 'screen' program to communicate with the device. When connecting the screen and turning on the board the leds on the screen turns on and the display turns a bright white. The display remains this way no matter what I do. My goal is to make the console output to the screen. There is also a 'touch functionality' incorporated, but for me it is secondary. Here is my process so far trying to make the screen work After reading a lot of forum posts for cases similar to mine (but all referring to the zero (h3) board and to a different Armbian/Kernel versions than mine - and also producing different results), I tried to: Activate the 'SPI overlays' needed by editing the /boot/armbianEnv.txt file according to this documentation (I also changed the 'verbosity' parameter to '7' and the 'console' parameter to 'both') overlays=spi-spidev spi-add-cs1 param_spidev_spi_bus=1 param_spidev_spi_cs=1 After rebooting this appear to activate the SPI1 with CS1 as expected $ ls /dev/spi* /dev/spidev1.1 $ sudo dmesg | grep spi [ 2.691646] m25p80 spi0.0: mx25l1606e (2048 Kbytes) [ 4.399025] spidev spi1.1: probing from DT Then I tried to activate and configure the fbtft_device module, that supposedly supports my screen, by creating /etc/modules-load.d/fbtft.conf and adding this two lines: fbtft fbtft_device and also /etc/modprobe.d/fbtft.conf with this configuration options fbtft_device rotate=90 name=piscreen speed=16000000 busnum=1 gpios=reset:2,dc:18 txbuflen=32768 fps=25 Extracted from here After rebooting, again, a new framebuffer device is created $ ls /dev/fb* /dev/fb0 But the screen remains white, with no alteration. In dmesg I can see that SPI1 failed to transfer data and that the fbtft_device is trying to use spi1.0 $ sudo dmesg | grep -i 'fb\|spi' [ 4.391749] spidev spi1.1: probing from DT [ 6.893332] fbtft: module is from the staging directory, the quality is unknown, you have been warned. [ 6.935810] fbtft_device: module is from the staging directory, the quality is unknown, you have been warned. [ 6.953422] m25p80 spi0.0: mx25l1606e spi0.0 40000kHz 8 bits mode=0x00 [ 6.960055] spidev spi1.1: spidev spi1.1 1000kHz 8 bits mode=0x00 [ 6.966595] fbtft_device: GPIOS used by 'piscreen': [ 6.971556] fbtft_device: 'reset' = GPIO2 [ 6.971561] fbtft_device: 'dc' = GPIO18 [ 6.971577] m25p80 spi0.0: mx25l1606e spi0.0 40000kHz 8 bits mode=0x00 [ 6.986087] spidev spi1.1: spidev spi1.1 1000kHz 8 bits mode=0x00 [ 6.986099] spi spi1.0: fb_ili9486 spi1.0 16000kHz 8 bits mode=0x00 [ 7.858552] fb_ili9486: module is from the staging directory, the quality is unknown, you have been warned. [ 9.100443] graphics fb0: fb_ili9486 frame buffer, 480x320, 300 KiB video memory, 32 KiB buffer memory, fps=25, spi1.0 at 16 MHz [ 13.227056] spi_master spi1: spi1.0: timeout transferring 32768 bytes@16000000Hz for 104(100)ms [ 13.227378] fb_ili9486 spi1.0: SPI transfer failed: -110 [ 13.227914] spi_master spi1: failed to transfer one message from queue [ 13.228159] fb_ili9486 spi1.0: fbtft_update_display: write_vmem failed to update display buffer [ 13.341870] spi_master spi1: spi1.0: timeout transferring 2 bytes@16000000Hz for 104(100)ms [ 13.341887] fb_ili9486 spi1.0: SPI transfer failed: -110 [ 13.341907] spi_master spi1: failed to transfer one message from queue [ 13.341917] fb_ili9486 spi1.0: write() failed and returned -110 [ 13.445850] spi_master spi1: spi1.0: timeout transferring 2 bytes@16000000Hz for 104(100)ms [ 13.445864] fb_ili9486 spi1.0: SPI transfer failed: -110 [ 13.445886] spi_master spi1: failed to transfer one message from queue [ 13.445896] fb_ili9486 spi1.0: write() failed and returned -110 [ 13.556038] spi_master spi1: spi1.0: timeout transferring 2 bytes@16000000Hz for 108(100)ms [ 13.556337] fb_ili9486 spi1.0: SPI transfer failed: -110 [ 13.556808] spi_master spi1: failed to transfer one message from queue [ 13.557056] fb_ili9486 spi1.0: write() failed and returned -110 So, according with this fbtft_device documentation I changed /etc/modprobe.d/fbtft.conf to include cs=1 to see if the module would 'use' spi1.1 options fbtft_device rotate=90 name=piscreen speed=16000000 busnum=1 cs=1 gpios=reset:2,dc:18 txbuflen=32768 fps=25 After rebooting, the screen remains white and now dmesg is showing this: $ sudo dmesg | grep -i 'fb\|spi' [ 4.392284] spidev spi1.1: probing from DT [ 6.955069] fbtft: module is from the staging directory, the quality is unknown, you have been warned. [ 6.997515] fbtft_device: module is from the staging directory, the quality is unknown, you have been warned. [ 7.009650] m25p80 spi0.0: mx25l1606e spi0.0 40000kHz 8 bits mode=0x00 [ 7.016383] spidev spi1.1: spidev spi1.1 1000kHz 8 bits mode=0x00 [ 7.016474] spidev spi1.1: Deleting spi1.1 [ 7.027482] fbtft_device: GPIOS used by 'piscreen': [ 7.032449] fbtft_device: 'reset' = GPIO2 [ 7.036490] fbtft_device: 'dc' = GPIO18 [ 7.040409] m25p80 spi0.0: mx25l1606e spi0.0 40000kHz 8 bits mode=0x00 [ 7.047052] spi spi1.1: fb_ili9486 spi1.1 16000kHz 8 bits mode=0x00 [ 7.723075] fb_ili9486: module is from the staging directory, the quality is unknown, you have been warned. [ 8.614341] graphics fb0: fb_ili9486 frame buffer, 480x320, 300 KiB video memory, 32 KiB buffer memory, fps=25, spi1.1 at 16 MHz [ 9.125884] spi_master spi1: spi1.1: timeout transferring 32768 bytes@16000000Hz for 104(100)ms [ 9.136951] fb_ili9486 spi1.1: SPI transfer failed: -110 [ 9.143527] spi_master spi1: failed to transfer one message from queue [ 9.161691] fb_ili9486 spi1.1: fbtft_update_display: write_vmem failed to update display buffer Now it appears that spi1.1 is been deleted and in fact it is not present in /dev/ $ ls /dev/spi* ls: cannot access '/dev/spi*': No such file or directory Now I am stuck. Can someone help me understand and diagnose what is happening?
  24. About 3 months ago i bought the Orange PI Zero Plus Orange Pi Zero Plus I installed Armbian Stretch and started playing around. I noticed that it got up to 71c which was to much so i shut it down and went on the net to buy some 5v fans to cool it. A month ago I received the first fans and noticed now that Armbian Buster had arrived. Since I hadn't gotten far with the config of Armbian Stretch I started on a new image. But to my disappointment the ARM processor is now clocked to 1008Mhz and not the 1.2Ghz the device is set to by manufacturer. I can guess that it is because of the heat problem that it is now set to 1008Mhz. The problem is through armbian-config there is no longer any an 1.2Ghz option only 1008Mhz . And setting nano /etc/default/cpufrequtils service cpufrequtils restart Doesn't change the actual speed from 1Ghz to 1.2Ghz Some info My kernel is uname -a Linux orangepizeroplus 4.19.63-sunxi64 #5.92 SMP Fri Aug 2 00:18:27 CEST 2019 aarch64 GNU/Linux My /etc/default/cpufrequtils looks like # WARNING: this file will be replaced on board support package (linux-root-...) upgrade ENABLE=true MIN_SPEED=480000 MAX_SPEED=1010000 GOVERNOR=ondemand And cpufreq-info shows hardware limits: 120 MHz - 1.01 GHz available frequency steps: 120 MHz, 240 MHz, 480 MHz, 648 MHz, 816 MHz, 960 MHz, 1.01 GHz I suppose it's the kernel which decides what is allowed. And I do get that it will keep the heat down and that setting it to 1008Mhz as default is a good idea. But I was hoping to get the option back to choose 1.2Ghz even if it should default to 1008Mhz now where I have bought both 5v fans and NPN transistors to make a little ARM fan for my OPZ+. Ty for reading and best regards, Darkyere
  25. I am very confused. I don't know where the problem is. Have you ever encountered the same problem? Kernel 4.19.80-sunxi Debian Stretch armbian version 5.98 Orange Pi R1 No third-party hardware was added. Pure R1 bare board Start error message: [ OK ] Started LSB: set CPUFreq kernel parameters. [ 8.670214] Unable to handle kernel NULL pointer dereference at virtual address 00000000 [ 8.681560] pgd = 95d3822c [ 8.684287] [00000000] *pgd=00000000 [ 8.687884] Internal error: Oops: 805 [#1] SMP THUMB2 [ 8.692942] Modules linked in: binfmt_misc 8189es zstd zram lima sun8i_codec_analog snd_soc_simple_card sun8i_adda_pr_regmap snd_soc_simple_card_utils sun4i_i2s gpu_sched ttm snd_soc_core snd_pcm_dmaengine snd_pcm snd_timer sun4i_gpadc_iio snd industrialio soundcore sun8i_ths uio_pdrv_genirq cpufreq_dt uio thermal_sys cfg80211 r8152 usb_f_acm u_serial g_serial libcomposite ip_tables x_tables pwrseq_simple [last unloaded: 8189es] [ 8.730973] CPU: 3 PID: 233 Comm: systemd-journal Not tainted 4.19.79-sunxi #5.98 [ 8.738466] Hardware name: Allwinner sun8i Family [ 8.743191] PC is at rb_erase_cached+0xdc/0x230 [ 8.747744] LR is at rb_erase_cached+0xb5/0x230 [ 8.752296] pc : [<c08f1824>] lr : [<c08f17fd>] psr: 400f00b3 [ 8.758578] sp : cdacbd28 ip : 00000001 fp : cfd71600 [ 8.763820] r10: c0d04d48 r9 : c0d04d48 r8 : c0d04d48 [ 8.769048] r7 : cfd716b4 r6 : 00000000 r5 : 00000000 r4 : cfa1480d [ 8.775587] r3 : cfa1480c r2 : ce5e620c r1 : cfd716b0 r0 : 00000000 [ 8.782131] Flags: nZcv IRQs off FIQs on Mode SVC_32 ISA Thumb Segment none [ 8.789545] Control: 50c5387d Table: 4daec06a DAC: 00000051 [ 8.795316] Process systemd-journal (pid: 233, stack limit = 0x85b75857) [ 8.802034] Stack: (0xcdacbd28 to 0xcdacc000) [ 8.806419] bd20: 00000001 cfd71680 cd674180 c0d04d48 cfae5500 c0140475 [ 8.814616] bd40: cfdeb538 c01c11a7 00000000 c014172f cd674180 cfd71680 c0d04d48 acfe8204 [ 8.822795] bd60: 0004a000 acfe8204 cdab64e0 acfe8204 00000009 cd674180 cd674100 cfd71680 [ 8.830988] bd80: cfae5500 c0d04d48 c0d04d48 c0d04d48 cfd71600 c0147b41 acfe8204 c0d04d48 [ 8.839187] bda0: ffff0000 cdacbee0 7fff0000 cfae5480 cdacbfb0 cdacbe3c cfd71680 c0901f78 [ 8.847384] bdc0: 00000000 c0d04d48 00000009 cfae5480 00000000 cfd71600 cfae5480 cfd71600 [ 8.855581] bde0: cdacbdf8 acfe8204 c0cb9600 cfd71600 cfae5480 c0cb9600 cdacbe20 c0d04d48 [ 8.863780] be00: c0cb9600 cfae5820 c0901f18 c08f9fc3 00000000 00000000 cfdeb538 acfe8204 [ 8.871978] be20: 00000200 cdab64e0 cdacbdd8 0f0b8000 c08fa607 00000000 cdacbe54 acfe8204 [ 8.880178] be40: 00000000 acfe8204 cdacbe94 ffffe000 00000000 00000000 cdacbe70 c0d04d48 [ 8.888376] be60: 00000000 c0d04d48 cdbfd6ac c08fa607 acfe8204 00000001 00000000 c08fd467 [ 8.896574] be80: cdacbf58 c0276517 be9d9540 00000000 0000001d 00000000 00000019 acfe8204 [ 8.904771] bea0: 01bab150 c02764bd cdbfd680 cdbfd6ac cdacbecc c0d04d48 cdbfd694 c0276029 [ 8.912962] bec0: 00000ae9 00000000 000000fc acfe8204 cdacbecc 00000001 00000000 00000000 [ 8.921148] bee0: be9d9540 cda1ab40 cdbfd680 c08fd487 00000000 00000001 cdbfd694 c02762b7 [ 8.929335] bf00: 00000000 cfb10000 c0d05430 c025699b 00000000 c022c7dd c0d04d48 cdbfd6ac [ 8.937524] bf20: 00000000 00000000 cdbfd694 00000000 ffffe000 00000001 cda1ab40 0000001d [ 8.945712] bf40: 00000003 00000000 00000000 00000000 cdaca000 00000005 0000001d be9d9540 [ 8.953901] bf60: 00000000 acfe8204 00000001 cfae5480 c013b391 cdbfd698 cdbfd698 acfe8204 [ 8.962096] bf80: cdaca000 01bab150 00000001 be9d9540 000000fc c0101224 cdaca000 000000fc [ 8.970286] bfa0: 00000008 c01011f9 01bab150 00000001 00000008 be9d9540 0000001d ffffffff [ 8.978460] bfc0: 01bab150 00000001 be9d9540 000000fc ffffffff ffffffff 0000001d 00000008 [ 8.986630] bfe0: 00000000 be9d9530 00000000 b6d79bf2 000f0030 00000008 00000000 00000000 [ 8.994820] [<c08f1824>] (rb_erase_cached) from [<c0140475>] (set_next_entity+0x61/0x568) [ 9.002994] [<c0140475>] (set_next_entity) from [<c0147b41>] (pick_next_task_fair+0x2b1/0x53c) [ 9.011599] [<c0147b41>] (pick_next_task_fair) from [<c08f9fc3>] (__schedule+0xc3/0x6d8) [ 9.019682] [<c08f9fc3>] (__schedule) from [<c08fa607>] (schedule+0x2f/0x68) [ 9.026727] [<c08fa607>] (schedule) from [<c08fd467>] (schedule_hrtimeout_range_clock+0xf3/0xfc) [ 9.035504] [<c08fd467>] (schedule_hrtimeout_range_clock) from [<c08fd487>] (schedule_hrtimeout_range+0x17/0x1c) [ 9.045671] [<c08fd487>] (schedule_hrtimeout_range) from [<c02762b7>] (do_epoll_wait+0x283/0x37c) [ 9.054538] [<c02762b7>] (do_epoll_wait) from [<c01011f9>] (__sys_trace_return+0x1/0xc) [ 9.062529] Exception stack(0xcdacbfa8 to 0xcdacbff0) [ 9.067577] bfa0: 01bab150 00000001 00000008 be9d9540 0000001d ffffffff [ 9.075747] bfc0: 01bab150 00000001 be9d9540 000000fc ffffffff ffffffff 0000001d 00000008 [ 9.083913] bfe0: 00000000 be9d9530 00000000 b6d79bf2 [ 9.088964] Code: f043 0401 6058 6093 (6004) 681c [ 9.093752] ---[ end trace 64ba3d7f8cd4423e ]--- lsmod: Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 0bda:8152 Realtek Semiconductor Corp. RTL8152 Fast Ethernet Adapter Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub root@t1000p:~# lsmod Module Size Used by binfmt_misc 16384 1 8189es 864256 0 zstd 16384 4 lima 40960 0 sun4i_i2s 20480 0 gpu_sched 20480 1 lima ttm 57344 1 lima snd_soc_simple_card 16384 0 snd_soc_simple_card_utils 16384 1 snd_soc_simple_card sun8i_codec_analog 24576 0 sun8i_adda_pr_regmap 16384 1 sun8i_codec_analog snd_soc_core 110592 4 sun4i_i2s,sun8i_codec_analog,snd_soc_simple_card_utils,snd_soc_simple_card sun4i_gpadc_iio 16384 0 snd_pcm_dmaengine 16384 1 snd_soc_core snd_pcm 69632 3 sun4i_i2s,snd_pcm_dmaengine,snd_soc_core snd_timer 24576 1 snd_pcm industrialio 49152 1 sun4i_gpadc_iio snd 45056 3 snd_timer,snd_soc_core,snd_pcm soundcore 16384 1 snd sun8i_ths 16384 0 zram 24576 2 uio_pdrv_genirq 16384 0 uio 16384 1 uio_pdrv_genirq cpufreq_dt 16384 0 thermal_sys 57344 3 cpufreq_dt,sun8i_ths,sun4i_gpadc_iio cfg80211 393216 1 8189es r8152 49152 0 usb_f_acm 16384 1 u_serial 20480 3 usb_f_acm g_serial 16384 0 libcomposite 40960 2 g_serial,usb_f_acm ip_tables 20480 0 x_tables 20480 1 ip_tables pwrseq_simple 16384 1