Active threads

@xiboliyadongtu How was it going?

Addon for @maxsub and the bricked R2S: I tested USB boot from u-boot cmdline on my RV2, and it works. Here's how: usb start setenv devtype usb setenv devnum 0:1 setenv prefix boot/ #setenv fdtfile spacemit/x1_orangepi-r2s.dtb setenv fdtfile spacemit/k1-orangepi-rv2.dtb setenv bootargs "console=ttyS0,115200 root=/dev/sda1" ls ${devtype} ${devnum} ${prefix} load ${devtype} ${devnum} ${ramdisk_addr_r} ${prefix}uInitrd load ${devtype} ${devnum} ${kernel_addr_r} ${prefix}Image load ${devtype} ${devnum} ${fdt_addr_r} ${prefix}dtb/${fdtfile} booti ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r} In case you have a blank u-boot-env, here's mine attached // HTH printenv.cap

OK, so that went reasonably fast and produced the 4 kernel debs. The linux-libc-dev-edge-rockchip64 didn't install due to conflict with the (current/stable) linux-libc-dev package - I think this is expected - but the rest of the kernel packages have been succesfully installed and the dkms error seems resolved.

Hello everyone, I'm trying to locate a specific older Armbian build for an RK3318 TV box and hoping someone in the community might have it archived. I'm looking for: Version: Armbian 22.05.1 (or similar from that era) Kernel: Legacy 4.4.213 Base: Debian Buster Desktop: XFCE (or even a CLI version is fine) The original download link from users.armbian.com/balbes150/ is now a 404. I understand this is a very old "Community Maintained" build and that RK3318 support has moved to newer kernels . I'm specifically seeking this kernel version for a project. If anyone has this image file or a similar legacy build (kernel 4.4.x) for the RK3318 stashed away, could you please share it or point me to an alternative source? Any help would be greatly appreciated! Hardware: (e.g., H96 Max RK3318 - please specify your exact box model) Thank you

Have you tried all of the gxm dtb files? Per the instructions (https://forum.armbian.com/topic/33676-installation-instructions-for-tv-boxes-with-amlogic-cpus)

Depends on the image you are using. The image for 3 LTS should work for the 3 LTS. The image for the 3 (without lts) will not.

Without uart hard to tell.

In the world of TV boxes "identical looking" means nothing, as manufacturers build each batch with the lowest cost components available at the time. There are many cases where identical looking boxes even contain different cpus ( ie amlogic vs rockchip). My recommendation would be first to verify the markings on the boards (there is usually some sort of board identifying text on the board)to really see if they are the same under the hood.

I had similar issues with the original camera. But after days of testing even with the official radxa image I think I found the possible problem. There is a batch of boards with a wrong csi connector, the pins are not correct. I found it here: https://github.com/radxa-build/radxa-zero3/issues/15 I send a mail to my supplier and they will send me a fixed cable, I can give an update if it's fixed.

Wifi works normaly only trought NetworkManager.

I just tested the latest Armbian distros, Armbian 26.2.0-trunk.493 XFCE and Armbian 26.2.0-trunk.493 Minimal / IOT, and none worked. Then I tried Radxa system images, rock-4se_bookworm_kde_r4.output_512.img.xz did not work. So I got confused because my Rock 4SE v 1.53 SBC worked a long time ago. Found backup of old boot image, which I used with the NVMe drive, because it could not boot on its own. And do you know what? Finally, I saw a picture on the screen with boot log information, which made me happy because it proved my SBC had not died. Then I started looking at some old system images for this board and found one which is booting, it is rock-4se_debian_bullseye_kde_b38.img.

Did anyone ever get anything to work on a x96q v4.1? If so, what was it and where can i get it?

I will try!! @Lamerjack

I`ll already done it. Switched to original Btt image. Understand what that board is didn`t love any sd-card. I`ll stopts on AP32GMCSH10UB-RA card. If card didn't made friends with the board it not boot,reboot`s,power off, halt`s.... IO pins i didnt use.... I`ll swithed to ch340 as uart, because it`s understand 3.3 and 5v levels. The board only 3.3 CAN i use on RP2040+can chip, what cost only 5$(in total), not 15$ for btt can. in a end of can bus i`ll use EBB42 so it`s have all i need.... It`s about I2C bus. Thats my story If u need help, free to ask. I`ll will help if i coud

Well since you asked in this sub-forum, feel free to start:

a few things happened since sunday: i set up a project homepage: https://langerma.github.io/dumpstore/ - screenshots, feature overview, install instructions. and a wiki of course: https://github.com/langerma/dumpstore/wiki three new things landed since the initial post: live ansible task streaming the op-log dialog now shows tasks appearing one by one as ansible runs them, instead of dumping everything at once when the playbook finishes. small thing, but makes it feel a lot more responsive. pool scrub scheduling you can now add/remove pools from the periodic scrub schedule directly from the ui. on linux it edits ZFS_SCRUB_POOLS in /etc/default/zfs (zfsutils-linux), on freebsd it manages daily_scrub_zfs_pools in /etc/periodic.conf. platform-aware, same interface. schema-driven ui all zfs property dropdowns (compression, atime, recordsize, etc.) and the shell picker for users are now driven by a single schema definition in the backend. GET /api/schema returns the full list filtered by platform. before this, the values were hardcoded in four different places — html, js, and go. adding a new property now means touching one file. nothing groundbreaking, just steady progress.

Well the only thing armbian-config does, is calling "armbian-install" which has been there for ages

What firmware are you using?

Find a board similar to yours and make the necessary adaptations. and on Linux Rockchip: So we can do an shutuo-v8-rk3288 compatible: many times in mainline you can do some tricks like disabling all usb

Thanks for your reply. Sorry for the bad identification of my SBC, (i have many ). The board is this one : https://www.armbian.com/orange-pi-5-plus/ Therefore, it seems that my bug report is relevant

https://www.mediafire.com/file/f2iaay5gccs163l/TV_STICK_R3_TRB.rar/file

As I had read, the maximum amount of RAM the H618 handles is 4GB, so, this 8GB TV Box should be a false information.

v25.11.2 for Orange Pi 5 Plus running Armbian Linux 6.1.115-vendor-rk35xx on mine. Just saying. You should use a spoiler for the slop. tl;dr: vendor kernel has exactly nothing in common with mainline besides the fact that it is supposed to run in the same hw.

Meson 8B is codename of s805 means its not 4k at all bro mine is also 8B i checked it with adb

According to the datasheet (https://de.scribd.com/document/948890791/MT7988A-Datasheet) the supported baudrate seems to be between 300baud and 3Mbaud. However cannot tell anything about support status. Neither do I have this hw, nor did I ever dig into this soc. Starting with device tree overlays might be a good start or check the whole device tree in general for the uart nodes if present.