Active threads

Thanks for your help. I understand I can add my codes while building. However, would it be possible anyway to emulate the SBC on PC from the running image, even on a later stage?

https://paste.armbian.com/nocivefiki

https://debug.armbian.de tl;dr: get an USB uart adapter and debug via serial console.

moved

SOLD

I found the error, please don't do it again. Just Search for Supported boards before buying Partners boards that will work in this case: https://www.armbian.com/partners/

Probably never will until roll-over to next LTS version. We don't have people to maintain this.

Even with the new version,I am still running into the same error dmesg.multitool.log

Recommendation: Switch to the edge kernel (eMMC drive access + better performance + more complete kernel features) I just tried out that Armbian Noble image with the vendor kernel. I noticed the eMMC drive didn't show up. Also the user interface seemed a bit sluggish. I normally use the edge kernel, it's far more complete than the vender kernel. I tried that here, and the eMMC drive appeared, and also the user interface become much smoother. You can use armbian-config to switch to the latest edge kernel (6.16.4).

"if you have ever booted a different distribution then your box will be incompatible with the Armbian build" are you serious? No matter after all this linux on arm shit problems i had last week, i really must say that a windows 10 + kodi.exe on a thin client is really the best in quality (dxva) and stability. And it only eats 1-2w more power than this u1 thingie. So, i just keep my moonlight on windows and put tvheadend together with the wintv solohd into a vmware player. bye bye.

You should also be updating your /etc/apt/sources.list.d/armbian.list as well (otherwise you will be mixing bookworm armbian packages with trixie debian packages)

How do install armbian in my TX98 TV BOX Processor:Allwinner H313 I bought it on tiktok shop

To maintain changes between different kernel versions, you can use overlays. I did this by following some dts changes from @ebin-dev. Add this line user_overlays=rockchip-rk3399-op1-opp rockchip-rk3399-l2-cache to /boot/armbianEnv.txt Copy the dtbo files to /boot/overlay-user (mkdir -p /boot/overlay-user if the folder does not exist). rockchip-rk3399-l2-cache.dtborockchip-rk3399-op1-opp.dtborockchip-rk3399-op1-opp.dtsrockchip-rk3399-l2-cache.dts

Hello, and thank you for the suggestions. Just to clarify, I am not using an ILI9341 or ST7789 display. My display is a ST7735S (1.8", 128x160), a generic model purchased from AliExpress. The main issue is that while this setup worked perfectly on older Armbian kernels, it's no longer working with the current Kernel 6.12.x. It seems like the necessary module might have been removed or changed in the newer versions. I am not using a desktop environment; my goal is to use the display directly from the console/framebuffer (no X11). I’ve made some progress, but now I’m stuck. Here’s what I'm observing: The system does create a framebuffer device at /dev/fb0. When I use a tool like fbi to show an image, it runs without any errors. If I try to dump the framebuffer device (e.g., cat /dev/fb0), it outputs data, which suggests something is being written to the buffer. The problem is on the physical display itself: the screen's backlight turns on, but it remains completely blank (white). No image is ever displayed. I'm unfortunately not sure how to proceed from here. It feels like the display is being initialized enough to turn on the backlight, but the actual image data isn't being displayed correctly. I suspect the driver is not sending the right commands. Does anyone have an idea what I could try next? Thank you!

@FucusMeDeep don't throw yourself into this, I'm not the best example to be messing with junk, but times have changed, if it were really interesting I would recommend it. with that time and money I buy a board https://www.banana-pi.org/ anything that involves reinventing the wheel there is already ready, don't use material discarded by someone else. develop something on top of these boards, go further create something at a higher level than what you want to create. do this project with a more documented and healthy board: CH573F from Nanjing Qinheng Microelectronics Part of the document's included below: WCH 官方网站 www.wch.cn(zh-CN) / www.wch-ic.com(en) 时钟和电源 时钟： 32Mhz HSE 高速无源晶体输入 32.768k LSE 低速无源晶体输入 电源： 3.3V-5.5V电源输入，3.3V LDO最大100mA额外输出 USB电源串有二极管，防止电流倒灌 同时二极管可以通过短路焊盘旁路 5V带有TVS二极管 接口和按键 接口： 12Pin 2.54mm间距 I/O接口 * 2 按键： 复位/B23按键 * 1 Boot/B22按键 * 1

@RealAn DTS for Kernel 6.1: Unfortunately, all boards for TV Box device are embargoed upon landing in my country's territory. If any Golden Knight wants to do the development, I believe this is a good time.

I have had a bit of time to do some testing (re: MMC disconnects) This bug does not appear in kernel 6.6 A version of this bug appears in 6.10, but without the full trace. Output at the point of disconnect is: [ 1082.901830] EXT4-fs error (device mmcblk0p2): __ext4_get_inode_loc_noinmem:4512: inode #25776: block 1769: comm cron: unable to read itable block [ 1082.914822] EXT4-fs (mmcblk0p2): Remounting filesystem read-only or [ 8235.333023] EXT4-fs (mmcblk0p2): shut down requested (2) It is worth noting that the device is noticeably more sluggish on this kernel (not measured, and may or may not be related) On kernel 6.12 The bug manifests with a full trace: [ 1956.200890] I/O error, dev mmcblk0, sector 9337968 op 0x1:(WRITE) flags 0xc800 phys_seg 1 prio class 2 [ 1965.163111] rcu: INFO: rcu_sched self-detected stall on CPU [ 1965.165764] rcu: 0-....: (57 ticks this GP) idle=9194/1/0x40000004 softirq=13082/13083 fqs=48 [ 1965.173801] rcu: (t=2142 jiffies g=20165 q=305 ncpus=4) [ 1965.179160] CPU: 0 UID: 0 PID: 78 Comm: kworker/0:3 Not tainted 6.12.49-current-meson #1 [ 1965.179720] Hardware name: Amlogic Meson platform [ 1965.179991] Workqueue: events dbs_work_handler [ 1965.180753] PC is at __netif_receive_skb_core.constprop.0+0x4/0x10a4 [ 1965.181411] LR is at __netif_receive_skb_list_core+0xf0/0x1f4 [ 1965.181948] pc : [<c10f55bc>] lr : [<c10f674c>] psr: 80030113 [ 1965.182280] sp : f0801d14 ip : 00000000 fp : c4000000 [ 1965.182583] r10: c211a108 r9 : 00000000 r8 : c4000000 [ 1965.182874] r7 : f0801d48 r6 : c400148c r5 : c211a108 r4 : c4e09900 [ 1965.183225] r3 : c2abbd80 r2 : f0801d44 r1 : 00000000 r0 : f0801d40 [ 1965.183585] Flags: Nzcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment none [ 1965.184017] Control: 10c5387d Table: 05ad004a DAC: 00000051 [ 1965.184260] Call trace: [ 1965.184552] __netif_receive_skb_core.constprop.0 from 0xc4003640 [ 1965.262719] sched: DL replenish lagged too much [ 1990.096714] mmc0: card 0002 removed [ 1990.100368] Aborting journal on device mmcblk0p2-8. [ 1990.100590] JBD2: I/O error when updating journal superblock for mmcblk0p2-8. [ 1990.102743] ------------[ cut here ]------------ [ 1990.111672] WARNING: CPU: 0 PID: 131 at drivers/mmc/host/meson-mx-sdio.c:446 meson_mx_mmc_irq_thread+0x168/0x174 [ 1990.121734] Modules linked in: zram zsmalloc binfmt_misc snd_soc_meson_gx_sound_card snd_soc_meson_aiu snd_soc_hdmi_codec snd_soc_meson_card_utils snd_soc_meson_codec_glue snd_soc_core evdev snd_pcm snd_timer meson_ir snd rc_core soundcore meson_saradc thermal_generic_adc cfg80211 rfkill efi_pstore pstore [ 1990.148744] CPU: 0 UID: 0 PID: 131 Comm: irq/35-c1108c20 Not tainted 6.12.49-current-meson #1 [ 1990.148779] Hardware name: Amlogic Meson platform [ 1990.148791] Call trace: [ 1990.148807] unwind_backtrace from show_stack+0x10/0x14 [ 1990.148865] show_stack from dump_stack_lvl+0x54/0x68 [ 1990.148921] dump_stack_lvl from __warn+0x80/0x114 [ 1990.148980] __warn from warn_slowpath_fmt+0x184/0x18c [ 1990.149030] warn_slowpath_fmt from meson_mx_mmc_irq_thread+0x168/0x174 [ 1990.149088] meson_mx_mmc_irq_thread from irq_thread_fn+0x1c/0x7c [ 1990.149150] irq_thread_fn from irq_thread+0x138/0x21c [ 1990.149207] irq_thread from kthread+0xdc/0xf8 [ 1990.149270] kthread from ret_from_fork+0x14/0x28 [ 1990.149314] Exception stack(0xf106dfb0 to 0xf106dff8) [ 1990.149339] dfa0: 00000000 00000000 00000000 00000000 [ 1990.149365] dfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 1990.149388] dfe0: 00000000 00000000 00000000 00000000 00000013 00000000 [ 1990.149420] ---[ end trace 0000000000000000 ]--- [ 1990.574529] EXT4-fs (mmcblk0p2): shut down requested (2) [ 1991.000606] mmc0: new high speed SDHC card at address 0002 [ 1991.001627] mmcblk0: mmc0:0002 00000 7.32 GiB [ 1991.006695] mmcblk0: p1 p2 [ 2041.955601] EXT4-fs warning (device mmcblk0p2): dx_probe:823: inode #593: lblock 0: comm bash: error -5 reading directory block [ 2041.961894] EXT4-fs warning (device mmcblk0p2): dx_probe:823: inode #593: lblock 0: comm bash: error -5 reading directory block [ 2041.974376] EXT4-fs warning (device mmcblk0p2): dx_probe:823: inode #593: lblock 0: comm bash: error -5 reading directory block If I were to speculate it looks like: initial bug introduced kernel 6.7 to 6.10 Bug was identified and the "fix"/"work around" has lead to the more verbose failure somewhere in 6.11 - 6.12 I went for the low hanging fruit first and can confirm the driver meson-mx-sdio.c is unchanged across all versions. I have also compared the DTBs: 6.6 -> 6.10 Significant changes 6.10 -> 6.12 Identical The changes looks to be the USB fix. I suspect that the issue is not with the DTB files, as the significant changes will be down to shifting phandle references by +1, I have now completely ruled out changes to the DTB. I loaded up the 6.12 kernel with the 6.6 DTB and hit the bug fairly quickly (wish I'd done this to start with, to be honest!) When I next get some time I will start diffing changes to the mmc/core and clk/meson drivers between 6.6 -> 6.10. If anyone else wants to have a crack at this in the meantime, based on the above information, then please, have at it!

https://github.com/radxa-pkg/aic8800/releases/tag/4.0+git20250410.b99ca8b6-2 The above should get you to a useable page. Download the USB version of the .deb package. I stored mine in the /root but had to copy it to the /tmp directory and install it from there. I installed the .deb package after the apt upgrade process, then rebooted. There may be a more recent version of the package. If I find it, I'll post a link Hope this helps, let me know if you run into trouble.

i can say that linux-image-6.12.43+deb12-arm64 works

Thanks for the reply @hexdump , the thing I don't understand is that in the thread I mentioned in my first message to this thread : the person claims to have successfully installed the OS on the internal eMMC on my very same box. Why running from eMMC wouldn't be possible on mine? What I am afraid of is that maybe there is some information / log which might be important in the outputs I provided in my pictures in the first message which I fail to recognize. About the message from @SteeMan I don't understand what he means by "and patch and apply it to a newer u-boot and build a newer u-boot"... In the /boot/build-u-boot/readme.txt file the instructions only have 3 different u-boots possible (s905x, s905x2 and s905x3) and all of them are like "git clone, run make" and that's it. Could you please be more explicit in what I should do or point me to some useful documentation? Thanks a lot for your help.

This build has disabled ffmpeg, I don't know it is possible to build with it for wayland client. I recommend x11 client because it is the most usable client with the most features. FreeRDP developers is developing a new sdl client for all platforms: linux, mac, wayland, x11, but that is still at an early stage. If you run xfreerdp, make sure to use gfx:AVC444 so that server sends h264 stream to you, then freerdp will use ffmpeg to decode it. You can check /proc/mpp_service/ to see if mpp hardware decoder is used. But don't expect the cpu will be extremely low, freerdp is decoding two avc420 streams and then combine them into one yuv444 frame, and then use cpu to convert yuv444 to rgb, then render it to x11, hardware decoder can only off-load few of the cpu load.

Not sure whether is specific to Opi5-Plus, on Arch Linux mpv-0.40.0 somehow also did not support --hwdec=v4l2request as such had to resort to the mpv-full-git which supports --hwdec=v4l2request. Debian-Trixie's repo mpv-0.40.0 also doesn't seems to support --hwdec=v4l2request.

I had the same problem when trying this directly on my Banana PI M5. But when I connected from my notebook via ssh everything worked fine and I could create the root and user password. Afterwards login was also possible directly on the machine.

Hi, I guess this happens because of the "-x" option in rsync which tells rsync to not cross the filesystem hierarchy. /var/log is typically a mount (/dev/zram1) so it will not be synced.

I suggest booting from µSD and then making a copy of eMMC to somewhere and reinstall after that. You can then restore whatever you need from your eMMC backup. Most likely that will be vastly less headache and much higher chances of success.