Active threads

Don't know what to tell you, it is running fine on my boxes and dmesg is clean. Also I cannot see what is your build version since the screenshot is missing the top line of the screen. 🤷‍♂️

This is internal development for our boards, unfortunately, there is no public repository for our kernel. The code is borrowed from reverse-engineered POCs h264 + * Based on https://github.com/jemk/cedrus + * Copyright (c) 2014-2015 Jens Kuske <jenskuske@gmail.com> jpeg + * Based on https://gitorious.org/recedro/jepoc + * Copyright (c) 2014 Manuel Braga <mul.braga@gmail.com>

Btw, about things turning orange... I had that experience some time ago before I got into Armbian. I did a clean install of Debian Bookworm. Then I tried installing the vendor GPU drivers and packages from the Orange PI company. Their drivers and packages were so horribly hacked / designed that various programs that needed certain SoC features needed to be custom modified to work with those specific vendor drivers. So all versions of those programs needed be held and were non-upgradable if I wanted continued GPU and video acceleration support. Anyway the main GPU driver package, when I installed it myself (instead of whatever secret sorcery their installation did), it turned things orange. Fortunately now, pure Trixie works out of the box on my board (from the Debian installer .iso), except that the kernel needs to be upgraded from their 6.12 to 6.16.3 from trixie-backports. Armbian's edge kernel on an otherwise pure Trixie is even better than Debian's, because it's customized for Rockchip. If you've been doing things like I was trying to before, things have much improved and now simple is better and it works. Also things tend to get really mangled up when upgrading over time - especially major LTS upgrades. Why not try a fresh install of a 25.8.1 Armbian image?

Fix: run armbian-install, then selected “Install/Update the bootloader on SD card (/dev/mmcblk0)”

U-Boot 2024.01-armbian-2024.01-S866c-Pbc32-Ha9af-V80bb-Bda0a-R448a (Nov 25 2024 - 14:01:12 -0500) Allwinner Technology CPU: Allwinner H616 (SUN50I) Model: Transpeed 8K618-T DRAM: 4 GiB Core: 61 devices, 22 uclasses, devicetree: separate WDT: Not starting watchdog@30090a0 MMC: mmc@4020000: 0, mmc@4022000: 1 Loading Environment from FAT... MMC: no card present ** Bad device specification mmc 0 ** In: serial@5000000 Out: serial@5000000 Err: serial@5000000 Net: apply fix for AC300 ephy bb version bug ... using AC300 emac1 ephy default config ... eth0: ethernet@5030000 starting USB... Bus usb@5101000: sun4i_usb_phy phy@5100400: External vbus detected, not enabling our own vbus USB EHCI 1.00 Bus usb@5101400: USB OHCI 1.0 Bus usb@5200000: USB EHCI 1.00 Bus usb@5200400: USB OHCI 1.0 scanning bus usb@5101000 for devices... 1 USB Device(s) found scanning bus usb@5101400 for devices... 1 USB Device(s) found scanning bus usb@5200000 for devices... 1 USB Device(s) found scanning bus usb@5200400 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop MMC: no card present switch to partitions #0, OK mmc1(part 0) is current device Scanning mmc 1:1... MMC: no card present No EFI system partition No EFI system partition Failed to persist EFI variables BootOrder not defined EFI boot manager: Cannot load any image Device 0: unknown device ethernet@5030000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! missing environment variable: pxeuuid Retrieving file: pxelinux.cfg/01-02-00-41-2d-68-a7 ethernet@5030000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Retrieving file: pxelinux.cfg/00000000 ethernet@5030000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Retrieving file: pxelinux.cfg/0000000 what can i do ? and how to do? 3ks

Describe what you did before to make it work. Show the DTS, the wiring you connected and the linux version that worked. If you used spidev before, I don't have experience in that. I only have experience with these drivers: panel-mipi-dbi-spi, ili9431 and adafrui-xy... The threads I showed you require you to stop using spidev, since the Linux kernel will communicate directly to the LCD, without a user program. Using both will just make them interfere with each other. If the LCD remains white and doesn't even flicker, and you made it work in an older kernel, then keep that wiring. If the /dev/fb0 exists, it means that linux has taken one SPI output port for display, but you need to make sure that: * and SPI parameters in the DTS are correct, * the gpio to handle the command/data, reset parameters are pointing to valid orange pi pins which are not used by anything else * the high/low polarity of those gpio * the wiring is correct, * the initialization bytes are correct

Kernel 6.1 is Vendor. Kernel 6.12 is Current / Mainline Kernel 6.16 is Edge. It's simple to change to edge. Just run armbian-config (it's available in the menu, or just type it in the command line using sudo). In armbian-config, as you make the selections, you'll find that you keep pressing ENTER until you get to the long list of kernels. Then scroll down to the latest Edge, which as of I last looked was 6.16.4. It may also say Armbian 25.8.1.

Ok, I foud some time to make additional tests. Here is what I found. It fully boots with 'x96q-lpddr3' SD card image if you swap dtb to one of the two: h618-linganpi-3h h618-orngepi2w However in both cases internal Ethernet does not work. I can use USB to ETH converter. Do you see any way to make internal ETH working in this board? In original Android dmesg there is a message about gmac: [ 28.389711] sunxi-gmac gmac1 eth0: eth0: Type(6) PHY ID 00441400 at 0 IRQ poll (gmac1-0:00) Does it sound like a solution?

quoting JPL: Did you see any announcement by the github's owner, about what we can expect from her/his source code? Looking at the content of the file, it seems like we need to download the code from: https://github.com/philipl/mpv#branch=v4l2request or https://github.com/philipl/mpv/tree/v4l2request And include this build-time configuration -Dv4l2request='enabled' I have posted instructions to build MPV on Sept 26 in this thread

Thanks for your comments. I did not touch the regulator@40 values at all - only the opp frequencies in line with suggestions from @prahal and some cache settings. cpufreq sampling_rates were changed to about 40000 (depending on the cluster) for kernels 6.6 by a script in /etc/rc.local. The script does not apply anymore in linux 6.12. Instead of disabling the A72 cluster altogether, reducing the burden on the CPUs during data transfers helps to substantially reduce crashes and avoids triggering the watchdog timer. P.S.: I bought a Rock-5B in October 2022 and I finally migrated everything to it.

The easiest way to do this is through a chroot (or perhaps systemd-nspawn) but how practical this is will be dependent on your end goals. I do this all the time.

At the risk of speaking too soon, I think I have found the issue. I need to revert some changes, and do some final testing, but hopefully a PR will be inbound to fix this in the next couple of days.

https://paste.armbian.com/nocivefiki

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/

"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

@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.

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.