Active threads

Yes, I have similar issues with 7.0.12-edge-sunxi kernel, see serial dump/log below: [ 133.382506] Internal error: Oops - undefined instruction: 0 [#1] SMP THUMB2 [ 133.389572] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace netfs sunrpc cp210x binfmt_misc usbserial lima gpu_sched nls_iso8859_1 drm_shmem_help er sun4i_gpadc_iio sunxi_cir axp20x_adc sun4i_ts sunxi_cedrus(C) v4l2_mem2mem videobuf2_dma_contig videobuf2_memops videobuf2_v4l2 videobuf2_common videodev mc display_c onnector cpufreq_dt evdev cfg80211 rfkill nfnetlink ip_tables x_tables autofs4 btrfs xor xor_neon libblake2b raid6_pq pinctrl_axp209 axp20x_usb_power industrialio sun4i_ gpadc sunxi phy_generic realtek [ 133.437258] CPU: 1 UID: 0 PID: 184 Comm: kworker/u8:5 Tainted: G C 7.0.12-edge-sunxi #2 VOLUNTARY [ 133.447746] Tainted: [C]=CRAP [ 133.450738] Hardware name: Allwinner sun7i (A20) Family [ 133.455991] Workqueue: pm pm_runtime_work [ 133.460075] PC is at __rpm_callback+0x64/0x10c [ 133.464565] LR is at rpm_callback+0x51/0x58 [ 133.468789] pc : [<c06d2e40>] lr : [<c06d2f39>] psr: 400f00b3 [ 133.475083] sp : f0a5de90 ip : 00000018 fp : c2ef5200 [ 133.480337] r10: c01761ed r9 : 000f4240 r8 : 00000008 [ 133.485590] r7 : 00000000 r6 : 00000000 r5 : c06d0aad r4 : c1e25410 [ 133.492146] r3 : 60000000 r2 : c1e25410 r1 : c1e25410 r0 : c06d0aad [ 133.498704] Flags: nZcv IRQs off FIQs on Mode SVC_32 ISA Thumb Segment none [ 133.506135] Control: 50c5387d Table: 43eb406a DAC: 00000051 [ 133.511902] Register r0 information: non-slab/vmalloc memory [ 133.517616] Register r1 information: slab kmalloc-1k start c1e25400 pointer offset 16 size 1024 [ 133.526415] Register r2 information: slab kmalloc-1k start c1e25400 pointer offset 16 size 1024 [ 133.535209] Register r3 information: non-paged memory [ 133.540302] Register r4 information: slab kmalloc-1k start c1e25400 pointer offset 16 size 1024 [ 133.549095] Register r5 information: non-slab/vmalloc memory [ 133.554795] Register r6 information: NULL pointer [ 133.559537] Register r7 information: NULL pointer [ 133.564279] Register r8 information: non-paged memory [ 133.569367] Register r9 information: non-paged memory [ 133.574455] Register r10 information: non-slab/vmalloc memory [ 133.580241] Register r11 information: slab task_struct start c2ef5200 pointer offset 0 size 2624 [ 133.589123] Register r12 information: non-paged memory [ 133.594301] Process kworker/u8:5 (pid: 184, stack limit = 0xe8b1571c) [ 133.600779] Stack: (0xf0a5de90 to 0xf0a5e000) [ 133.605178] de80: 60000000 c1e25410 c06d0aad 0000000a [ 133.613397] dea0: 00000000 00000008 000f4240 c06d2f39 c1e25410 c06d0aad 0000000a c06d3f23 [ 133.621617] dec0: c0ab03bf 00000402 c15b5180 c9306c24 c3790705 c34c3c70 c1813000 bf8e21ad [ 133.629836] dee0: c2ef5200 c1813000 01000000 569e35c7 c34f0c70 c1e254f8 c1e254f8 c1b9de00 [ 133.638054] df00: c1813000 01000000 c1b9de05 c1b72670 c1813000 c06d45a7 c2fb5900 c0141a87 [ 133.646273] df20: c3790000 569e35c7 00000000 c2ef5200 c1813000 c2fb5930 f0a5df50 c2fb5900 [ 133.654492] df40: c1813000 c2fb5930 c1603d80 c1813020 c2ef5200 c181305c c1813000 c0142345 [ 133.662711] df60: f0a5df78 c1603d80 f0a9deb8 c36b8fc0 c2ef5200 c0142245 c2fb5900 c2d35c80 [ 133.670929] df80: f0a9deb8 00000000 00000000 c0149e29 00000001 c36b8fc0 c0149d59 00000000 [ 133.679145] dfa0: 00000000 00000000 00000000 c0100155 00000000 00000000 00000000 00000000 [ 133.687359] dfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 133.695575] dfe0: 00000000 00000000 00000000 00000000 00000013 00000000 00000000 00000000 [ 133.703775] Call trace: [ 133.703812] __rpm_callback from rpm_callback+0x51/0x58 [ 133.711641] rpm_callback from rpm_suspend+0xab/0x514 [ 133.716756] rpm_suspend from pm_runtime_work+0x3f/0x70 [ 133.722045] pm_runtime_work from process_one_work+0x12f/0x390 [ 133.727947] process_one_work from worker_thread+0x101/0x254 [ 133.733667] worker_thread from kthread+0xd1/0xec [ 133.738431] kthread from ret_from_fork+0x11/0x1c [ 133.743189] Exception stack(0xf0a5dfb0 to 0xf0a5dff8) [ 133.748280] dfa0: 00000000 00000000 00000000 00000000 [ 133.756494] dfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 133.764705] dfe0: 00000000 00000000 00000000 00000000 00000013 00000000 [ 133.771365] Code: f7ff ff7c 4640 f7ef (fd27) f104 [ 133.776186] ---[ end trace 0000000000000000 ]--- [ 133.780834] note: kworker/u8:5[184] exited with irqs disabled [ 154.802648] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: [ 154.808663] rcu: 0-...0: (10 ticks this GP) idle=4c4c/1/0x40000000 softirq=7570/7571 fqs=2625 [ 154.817336] rcu: (detected by 1, t=5252 jiffies, g=14613, q=22 ncpus=2) [ 154.824076] Sending NMI from CPU 1 to CPUs 0: It was 3 weeks ago I did see this while doing some maintenance,upgrades,tests,experiments. Mine is a Bananapi M1, I use sun7i-a20-bananapi.dtb as DTB, and should be same for U-Boot, although I would need to check again what version/build I use. A difference is WiFi and some others, but my guess is there is something wrong/ongoing that is getting worse over time, as also with less newer kernels, it locks up after a few days quite often. This has been the case since december 2024 kernel 6.6.x as far as I see that written in my notes. I noticed that because I have used my Bananapi as NAS (blocklevel NBD). But it were paging issues and never really could find a pattern, always random. This error message is different, but might have same root-cause. Kernel 6.16.x I have run, but it lacked AXP PMU driver for the LiPo battery powering/charging which I use every now and then (is a great UPS like that). 6.18.x had it back again, but also lockups (same paging issue, I have already a kernel log dumping 24/7 to try to figure out what is wrong, but actually have no clue). I also used 6.12.90+deb13.1-armmp, so vanilla Debian kernel, but it has no overlays available and also no AXP PMU module, so that make it less useful. I set it back to 6.12.58-current-sunxi so that at least it runs reliably for a few days and I can use it ad-hoc as a serial console terminal for a Raspberrypi4 that also used to crash randomly due to USB3 stack issues and also for debugging and testing rather complex networking issues. I am using custom partition layout, the whole thing also runs as 32-bit UEFI KVM as well as systemd-nspawn container (same cloned MAC address so I un-power the real Bananapi then). The setup uses custom extlinux and standard grub-efi. I could easily test 7.0.x or later in a KVM, but assume it will run fine. It is really something about a combination of A20, platform HW, U-Boot, DeviceTree I think. It is a pity as this SBC is about the most useful I have due to its onboard SATA and LiPo battery management, although not 64-bit.

I don't have a Desktop installed on this device (OrangePi 4LTS). I resorted to using the rtmidi C interface instead, I made a wrapper. The Pipewire documentation is hard to figure out. I guess there should be some sort of session management for Non-Desktop sessions to load stuff?

No, same error. We prefer to see the replicateable changes instead of running a wild binary. Does it work for you on real Odroid-HC4 hardware? U-Boot prints (use CONFIG_DISPLAY_BOARDINFO_LATE): SoC: Amlogic Meson SM1 (S905X3) Revision 2b:c (10:2)

@Morales MoralesThe older build where ethernet is working: https://github.com/sicXnull/armbian-build/releases/download/mxqpro/Armbian-unofficial_26.02.0-trunk_Mxqpro-h313_trixie_current_6.12.74_cinnamon_desktop.img.xz The semi-official one where it's not: https://armbian.com/boards/x96q

Oh, my GOD ! I used the Android14 OS image from FriendlyElec google drive, and every video format I tried worked perfectly with full hardware acceleration ! Using Kodi player, this NanoPi M5 it is even capable of playing H.265 Full-4K 60fps 10bit HDR, without frame drop ! So the hardware is perfectly functional for 4K movies. The problem is the software component that is present in other OSes besides Android. Guys, I don't understand... Can't we take the drivers that FriendlyElec used in the Android14 OS image and adapt them for Armbian ? It would be brilliant to have an OS as cool as Armbian with full video acceleration capabilities ! Since I have this board, I'll gladly help you with any tests needed to make this Armbian for NanoPi M5 functional ! Just give me some ideas on what I should do... I will be your NanoPi M5 beta-testeer.

Well I gave up on it. I can't figure out how to boot anything other than armbian on NVMe and I need to boot a USB for starters. I guess I'll have to use for armbian until a cheap board with UEFI arrives. Orange Pi 6 Plus is too expensive for me.

Hi, I think swapon is not visible because you are not root. It should already be there via required package "mount". Try tu "su -" then you will "see" the command.

Hey! i had similar issues with the ES8388 analog and HDMI output path alignment on my OPi5 Plus under recent edge/mainline kernels. Sometimes the card states look fine in ALSA/pavucontrol but the streams just don't bridge to the hardware mapping properly, or the default audio levels are hitting gain issues. To test if it’s just a software-side compression or file amplification issue before diving too deep into modifying the device tree (.dts), try running a quick format check with a known sample using explicit routing- aplay -D plughw:1,0 your_audio.wav If your test files are inherently too quiet or failing to hit the threshold cleanly, you can boost them up beforehand via tools like MP3Louder just to make sure you aren't fighting low baseline source levels on top of the kernel driver bugs. If it completely stays dead silent even with clean, forced audio files, then it's definitely the device tree overlay parameters (simple-audio-card) not toggling correctly on your specific build version. Which image build date and kernel version are you currently on?

The post is from nov 2022, and OP reported it worked 2 weeks later... But good advice non the less... xD

maybe first post the output of uname -a on the raspberrypi3B+

if nand-sata-install is not maintained is there a replacement

Here is the commit: https://github.com/Guation/radxa-cubie-a5e-armbian-build/commit/202f1bf3943e2a583e10405f54b206fae9991a98

@sivert The "edge" kernel 7.x is more or less the stock kernel from upstream. It's missing some specific K1 drivers developed by SpacemiT basically. I think, upstream devs may implement their own version, thus may need some time. I am not sure, if upstream has the necessary SoC register documentation or if they persue some reverse-engineering on this. I recommend sticking with "current". HTH // Sven-Ola

@0757myt: Thank you so much for your clarification. I am really sorry that some parts of the guide are written too briefly. Sometime I don't know how to explain all of this messy things to new users. @hmoob I looked at your board and it seems your board doesn't have a power IC. There are just some diodes and capacitors near the DC port. May be one of them get shorted or burned but they are not really important. If you are good at soldering, you can definitely find the points for + and - pin to power the board so we will have 1 more USB port. Home Assistant need docker supports. Make sure that you are using the latest image (v1.1): https://github.com/chieunhatnang-personal/RK3128-Linux-SupportingScripts/releases/tag/kernel-6.6-armbian-26-v1.1

Since you cannot trust this EMMC, @magixx256 Here is how to get log2ram up and running, plus a quick way to double-check your storage health. 1. Install log2ram Manually Run these commands to pull the official repository, install it, and get it running: # Download and extract the latest release curl -L https://github.com/azlux/log2ram/archive/master.tar.gz | tar zx # Move into the folder and run the installer cd log2ram-master sudo ./install.sh # Clean up the installer files cd .. && rm -rf log2ram-master Reboot to Activate It For log2ram to properly hijack the logging system and mount it into RAM, you need to reboot the machine: sudo reboot Verify It's Working Once the box boots back up, run your status command again: systemctl status log2ram You should see an active (exited) status (which is normal for this service, as it just runs a script at boot to create the RAM disk). You can also verify it's actively mounting by checking your system disks: df -h | grep log2ram You'll see a line showing /var/log mapped to log2ram with a size of about 40MB or 50MB. 2. A Quick Note on System Stability Since log2ram holds your logs in memory and only writes them to your eMMC/SD card once a day (or right before a clean shutdown), a sudden power pull means you lose the logs from that day.

Please note that ophub is not Armbian. They use the Armbian name without permission, do not contribute to Armbian development nor participate in these forums. Having said that, android TV boxes are a community supported effort under Armbian. It would be appreciated if you took the time to submit a PR to include your efforts into Armbian.

I have also tried to build a new image and I am now getting a new error related to 16kb size. I have previosly had success 26.2.0 trunk 151, which was able to boot and worked quite well, Excluding known issues such as HDMI support and Fan speed needing to be adjusted with a script. Issue is that this build is no longer available. I think until we get more demand from Retroid Community we might just be out of luck

Problem solved. I used following instructions : Install Hacs on Home Assistant - Step-by-Step [year] — LazyAdmin

I bought an NVMe SSD and it is being recognized.

Hello everydoby. I'm starting work with the same board. Do you have any new information about the images to this board?

@ulumid Ram Initialstation ist done by U-Boot with a suitibal rkbin binary located in the first sectors of mmc. This ist spezific for your Board. connect PC to serial debug console and Test If Android Boot Starts and switchover to mmc if it is pluged.

Java folder inside, please don't use it. Read before: https://github.com/DesktopECHO/T95-H616-Malware

I made this to work on sbc:s both with or without a boot partition: https://github.com/UnconnectedBedna/shrink-backup Uses rsync so it's way faster than a dd. Creates an img file at minimum size. Autoexpansion on restore available for Armbian. Also contains a systemd-nspawn utility if you want to make changes to the img file itself.

Please read the Armbian TV box FAQ and the installation instructions for amlogic TV boxes. https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first https://forum.armbian.com/topic/33676-installation-instructions-for-tv-boxes-with-amlogic-cpus

Please move to Allwinner https://forum.armbian.com/topic/56539-how-to-install-armbian-on-mx10-f3-tv-stick/ https://xdaforums.com/t/how-to-use-otg-in-twrp.3097688/