All Activity

Hi! Thanks for replying. I didn't install coreelec actually. I booted from usb flashdrive just for curiosity and it worked. This device was shelved because It was boot looping into android recovery menu and I hadn't the time back then to reinstall stock firmware. A few days ago I decided to try armbian again when I saw a post about coreelec working with this mecool model. And, for my surprise, after i booted into coreelec, it booted into Android TV 10, the stock firmware again. Go figure.... So, the device is working with stock android again and now I'm trying to boot armbian to repurpose this old tvbox as a tiny server for light applications...

I have a RasPi 4b, I'm trying to understand how the device tree is modified so I can use the methodology eventually for a board that has a CM4 on it. So from a virgin clone of the build repo: ./compile.sh BOARD=rpi4b BRANCH=edge RELEASE=bookworm BUILD_MINIMAL=yes KERNEL_CONFIGURE=no KERNEL_GIT=full install image on SD card and boot the device, go through Armbian-setup. All well and good, then varify device tree used for the boot: cat /proc/device-tree/model gets me a: Raspberry Pi 4 Model B Rev 1.5 OK so now lets modify the device tree: ./compile.sh BOARD=rpi4b BRANCH=edge RELEASE=bookworm BUILD_MINIMAL=yes KERNEL_CONFIGURE=no KERNEL_GIT=full kernel-patch When the build pauses, we open another terminal and change the device tree file (note in the build log below I had modified all the CM4 device tree files): sudo nano ./arch/arm/boot/dts/broadcom/bcm2711-rpi-4-b.dts Only change is to modify the model line with a marker, like my initials, new line is: model = "Raspberry Pi 4 Model B AJW"; close editor, and hit enter to restart the build, then copy resulting patch file to: userpatches/kernel/archive/bcm2711-6.7/0010-simple-device-tree.patch rebuild as before, then burn new image to SD card and retest the device tree model, but no change is apparent. So how do you change the device tree for a RasPi 4? log-build-e9849e69-98be-4710-b3be-e05a30285a44.log

The upgrade bricked my Tinkerboard S eMMC a few weeks ago. Due to time constraints, I reloaded the OS on an SD card. I did an update / upgrade today and I believe my SD card was trashed again. I haven't tried rebooting yet but this is what happened the last time and again this time:

Any success with this? I have the same question

@BipBip1981 very good to hear that a higher version also runs stable, did the python test work for you without errors... for i in $(seq 1 100);do python3 -c "import pkg_resources" || break;done

Hi! I'm sorry if the answer to my question is already documented somewhere, but I couldn't find it. I am trying to figure out how to build a specific release. My understanding is that you checkout the desired tag of the armbian/build repo and just build it. However, when I do this with v24.2.1 the image that comes out is named 24.5.0-trunk. Changing the version in the VERSION file (by default set to 24.5.0-trunk) changes the name of the output image, but it is not clear to me if that affects other things than just this. So basically, now I am confused which scenario is correct: Is using the armbian/build tag the correct way to build a specific release and is the VERSION file just cosmetic? Is setting the version in the VERSION file the correct way and should any commit in armbian/build be able to generate the same image, provided the commit is new enough? A 3rd more correct way that I'm not aware of? Can anyone help me out here? Regards Stan

Hi everybody, I test 24.05 trunk build myself armbian bookworm with 6.6.27 Kernel and... For moment, i have a stable Helios64 with 400-1800Mhz schedutil and just my tuned fancontrol file. Running for more than 1 days without crash with my test pattern... and not crash/freeze until now !!!!!! I hope not crash during next few days... If not crash, i advise everybody to swith to this kernel Keep in touch

I guess the dtb file for it is here: https://github.com/leeboby/opizero3-uboot-dtb I guess that does not help without the DTS source file ?

@Dbosco Yes that's it

Just in case someone is interested, this commit restores sysfs for all sunxi64 boards: https://github.com/MichaIng/build/commit/3a3e5fd

This commit restores sysfs for all sunxi64 boards: https://github.com/MichaIng/build/commit/3a3e5fd

Maybe if we can extract more info from android we can figure this out. We need your .dts. Here are steps to do it with a linux PC running ubuntu. git clone https://github.com/cfig/Android_boot_image_editor.git sudo apt install git device-tree-compiler lz4 xz-utils zlib1g-dev openjdk-17-jdk gcc g++ python3 python-is-python3 p7zip-full android-sdk-libsparse-utils erofs-utils cd Android_boot_image_editor sudo apt install adb adb connect 192.168.X.X:5555 (x is your local network address for your box) adb -s 192.168.x.xxx:5555 shell "ls -al /dev/block/platform/soc@3000000/4022000.sdmmc/by-name" if you get: "error: device unauthorized. This adb server's $ADB_VENDOR_KEYS is not set Try 'adb kill-server' if that seems wrong. Otherwise check for a confirmation dialog on your device." You need to authorise your connection on the box. nick@nick-Inspiron-5680:~/Android_boot_image_editor$ adb -s 192.168.50.8:5555 shell "ls -al /dev/block/platform/soc@3000000/4022000.sdmmc/by-name" total 0 drwxr-xr-x 2 root root 540 1969-12-31 19:00 . drwxr-xr-x 3 root root 620 1969-12-31 19:00 .. lrwxrwxrwx 1 root root 21 1969-12-31 19:00 Reserve0 -> /dev/block/mmcblk0p24 lrwxrwxrwx 1 root root 20 1969-12-31 19:00 boot_a -> /dev/block/mmcblk0p5 lrwxrwxrwx 1 root root 20 1969-12-31 19:00 boot_b -> /dev/block/mmcblk0p6 lrwxrwxrwx 1 root root 20 1969-12-31 19:00 bootloader_a -> /dev/block/mmcblk0p1 lrwxrwxrwx 1 root root 20 1969-12-31 19:00 bootloader_b -> /dev/block/mmcblk0p2 lrwxrwxrwx 1 root root 21 1969-12-31 19:00 dtbo_a -> /dev/block/mmcblk0p21 lrwxrwxrwx 1 root root 21 1969-12-31 19:00 dtbo_b -> /dev/block/mmcblk0p22 lrwxrwxrwx 1 root root 21 1969-12-31 19:00 empty -> /dev/block/mmcblk0p18 lrwxrwxrwx 1 root root 20 1969-12-31 19:00 env_a -> /dev/block/mmcblk0p3 lrwxrwxrwx 1 root root 20 1969-12-31 19:00 env_b -> /dev/block/mmcblk0p4 lrwxrwxrwx 1 root root 21 1969-12-31 19:00 frp -> /dev/block/mmcblk0p17 lrwxrwxrwx 1 root root 21 1969-12-31 19:00 media_data -> /dev/block/mmcblk0p23 lrwxrwxrwx 1 root root 21 1969-12-31 19:00 metadata -> /dev/block/mmcblk0p19 lrwxrwxrwx 1 root root 21 1969-12-31 19:00 misc -> /dev/block/mmcblk0p10 lrwxrwxrwx 1 root root 21 1969-12-31 19:00 private -> /dev/block/mmcblk0p20 lrwxrwxrwx 1 root root 20 1969-12-31 19:00 super -> /dev/block/mmcblk0p9 lrwxrwxrwx 1 root root 21 1969-12-31 19:00 userdata -> /dev/block/mmcblk0p25 lrwxrwxrwx 1 root root 21 1969-12-31 19:00 vbmeta_a -> /dev/block/mmcblk0p11 lrwxrwxrwx 1 root root 21 1969-12-31 19:00 vbmeta_b -> /dev/block/mmcblk0p12 lrwxrwxrwx 1 root root 21 1969-12-31 19:00 vbmeta_system_a -> /dev/block/mmcblk0p13 lrwxrwxrwx 1 root root 21 1969-12-31 19:00 vbmeta_system_b -> /dev/block/mmcblk0p14 lrwxrwxrwx 1 root root 21 1969-12-31 19:00 vbmeta_vendor_a -> /dev/block/mmcblk0p15 lrwxrwxrwx 1 root root 21 1969-12-31 19:00 vbmeta_vendor_b -> /dev/block/mmcblk0p16 lrwxrwxrwx 1 root root 20 1969-12-31 19:00 vendor_boot_a -> /dev/block/mmcblk0p7 lrwxrwxrwx 1 root root 20 1969-12-31 19:00 vendor_boot_b -> /dev/block/mmcblk0p8 adb -s 192.168.x.x:5555 pull /dev/block/platform/soc@3000000/4022000.sdmmc/by-name/boot_a mv boot_a boot_a.img ./gradlew unpack cd build cd unzip_boot Your dtb will either be in "boot_a" or "vendor_boot_a". Android_boot_image_editor will extract it. if the commands don't work you can browse the folders. Find the correct path. sudo adb shell su cd /dev/block/platform/

@bjorn it actually isn't necessary to make a new image from scratch, but that we'd need to figure out how to pass that 1.5GB memory size to u-boot, e.g. possibly a DTS overlay. then this means the procedure may possibly be: write the existing published image to sd card make a DTS overlay with the 1.5GB configured (a text file) - may need to be compiled into a DTB file update armbianEnv.txt to use the edited overlay and save them on the image sd card appropriately on booting up, the os should then boot normally as do any other boards. Unfortunately, no one yet has probed this and document the steps to do this successfully.

It is known that Coreelec modifies the boot and so armbian can not boot. You'll have to restore your device.

I don't have time to test wifi, if you be the wifi guy, please use this method to fix the wifi power management or communication: the process will be: compare two decompiled DTS. The old that wifi work and the new 6.6 without wifi and use it to fix the Board bring UP file First Differences: Need to add TCS4525 Regulator Need to remove the fan53555 regulator: Change Pmic20 from RK817 to RK809 But the first thing you can try, is change the Enable wifi Pin! I think it needs to be GPIO2_B1 and today it was on GPIO4_A3

Yes you are right. It was working on the previous 1.1 image. There was the 6.1 kernel being active.

that's great Royk! so i can build Kodi following the official github guide, with GBM and GLES + patches 0001-windowing-gbm-Dynamic-plane-selection.patch / 0002-VideoLayerBridgeDRMPRIME-Use-crop-fields-to-render-t.patch ? or should i use a different configuration? thanks!

@Dbosco The same here until I compiled Kodi with the patch myself and everything works.

Hi! i've tried to apply the patch but i still have a black screen, maybe i did something wrong build: Armbian_24.2.4_Orangepi5_jammy_vendor_6.1.43_kde-neon-amazingfated_desktop After armbian wizard i did: apt update & upgrade reboot apt install kodi kodi-repository-kodi reboot start Kodi in GBM i've tested a video file, and black screen so i've quit from Kodi and i did the procedure below to apply the patches 0001-rga3_uncompact_fix.patch / 0002-vop2_rbga2101010_capability_fix.patch: % git clone -b rk-6.1-rkr1 https://github.com/amazingfate/linux-rockchip.git % cd linux-rockchip % wget https://github.com/hbiyik/ffmpeg-rockchip/wiki/patches/rockchip-kernel/0001-rga3_uncompact_fix.patch % wget https://github.com/hbiyik/ffmpeg-rockchip/wiki/patches/rockchip-kernel/0002-vop2_rgba2101010_capability_fix.patch % patch -p1 < 0001-rga3_uncompact_fix.patch patching file drivers/video/rockchip/rga3/rga3_reg_info.c Reversed (or previously applied) patch detected! Assume -R? [n] y % patch -p1 < 0002-vop2_rgba2101010_capability_fix.patch patching file drivers/gpu/drm/rockchip/rockchip_vop2_reg.c % make CROSS_COMPILE=aarch64-linux-gnu- ARCH=arm64 rockchip_linux_defconfig % make KBUILD_IMAGE="arch/arm64/boot/Image" CROSS_COMPILE=aarch64-linux-gnu- ARCH=arm64 -j "$(nproc)" bindeb-pkg Results: dpkg-deb: building package 'linux-libc-dev' in '../linux-libc-dev_6.1.43-1_arm64.deb'. dpkg-deb: building package 'linux-image-6.1.43' in '../linux-image-6.1.43_6.1.43-1_arm64.deb'. dpkg-deb: building package 'linux-image-6.1.43-dbg' in '../linux-image-6.1.43-dbg_6.1.43-1_arm64.deb'. dpkg-genbuildinfo --build=binary -O../linux-upstream_6.1.43-1_arm64.buildinfo dpkg-genchanges --build=binary -O../linux-upstream_6.1.43-1_arm64.changes dpkg-genchanges: info: binary-only upload (no source code included) dpkg-source --after-build . dpkg-buildpackage: info: binary-only upload (no source included) Then I did % cd .. % sudo dpkg -i *.deb Results: Selecting previously unselected package linux-headers-6.1.43. (Reading database ... 183026 files and directories currently installed.) Preparing to unpack linux-headers-6.1.43_6.1.43-1_arm64.deb ... Unpacking linux-headers-6.1.43 (6.1.43-1) ... Selecting previously unselected package linux-image-6.1.43. Preparing to unpack linux-image-6.1.43_6.1.43-1_arm64.deb ... Unpacking linux-image-6.1.43 (6.1.43-1) ... Selecting previously unselected package linux-image-6.1.43-dbg. Preparing to unpack linux-image-6.1.43-dbg_6.1.43-1_arm64.deb ... Unpacking linux-image-6.1.43-dbg (6.1.43-1) ... Preparing to unpack linux-libc-dev_6.1.43-1_arm64.deb ... Unpacking linux-libc-dev:arm64 (6.1.43-1) over (5.15.0-102.112) ... Setting up linux-headers-6.1.43 (6.1.43-1) ... Setting up linux-image-6.1.43 (6.1.43-1) ... * dkms: running auto installation service for kernel 6.1.43 Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area... make -j8 KERNELRELEASE=6.1.43 KERNEL_DIR=/lib/modules/6.1.43/build all... cleaning build area... v4l2loopback.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.1.43/updates/dkms/ depmod... [ OK ] update-initramfs: Generating /boot/initrd.img-6.1.43 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8156b-2.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8156a-2.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153c-1.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-4.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-2.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/keyspan/usa49wlc.fw for built-in driver keyspan W: Possible missing firmware /lib/firmware/keyspan/usa49w.fw for built-in driver keyspan W: Possible missing firmware /lib/firmware/keyspan/usa19w.fw for built-in driver keyspan W: Possible missing firmware /lib/firmware/keyspan/usa18x.fw for built-in driver keyspan W: Possible missing firmware /lib/firmware/keyspan/usa19qw.fw for built-in driver keyspan W: Possible missing firmware /lib/firmware/keyspan/mpr.fw for built-in driver keyspan W: Possible missing firmware /lib/firmware/keyspan/usa19qi.fw for built-in driver keyspan W: Possible missing firmware /lib/firmware/keyspan/usa19.fw for built-in driver keyspan W: Possible missing firmware /lib/firmware/keyspan/usa28xb.fw for built-in driver keyspan W: Possible missing firmware /lib/firmware/keyspan/usa28xa.fw for built-in driver keyspan W: Possible missing firmware /lib/firmware/keyspan/usa28x.fw for built-in driver keyspan W: Possible missing firmware /lib/firmware/keyspan/usa28.fw for built-in driver keyspan W: Possible missing firmware /lib/firmware/bfubase.frm for built-in driver bfusb W: Possible missing firmware /lib/firmware/intel/ibt-12-16.ddc for built-in driver btintel W: Possible missing firmware /lib/firmware/intel/ibt-12-16.sfi for built-in driver btintel W: Possible missing firmware /lib/firmware/intel/ibt-11-5.ddc for built-in driver btintel W: Possible missing firmware /lib/firmware/intel/ibt-11-5.sfi for built-in driver btintel W: Possible missing firmware /lib/firmware/mrvl/sdsd8997_combo_v4.bin for built-in driver btmrvl_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8987_uapsta.bin for built-in driver btmrvl_sdio W: Possible missing firmware /lib/firmware/mrvl/sdsd8977_combo_v2.bin for built-in driver btmrvl_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8897_uapsta.bin for built-in driver btmrvl_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8887_uapsta.bin for built-in driver btmrvl_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8797_uapsta.bin for built-in driver btmrvl_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8787_uapsta.bin for built-in driver btmrvl_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8688.bin for built-in driver btmrvl_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8688_helper.bin for built-in driver btmrvl_sdio W: Possible missing firmware /lib/firmware/rtl_bt/rtl8851bu_config.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8851bu_fw.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8852cu_config.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8852cu_fw.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8852bu_config.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8852bu_fw.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8852au_config.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8852au_fw.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8821a_config.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8821a_fw.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8761a_config.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8761a_fw.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8723a_fw.bin for built-in driver btrtl update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.1.43 Image Name: uInitrd Created: Tue Apr 16 13:06:04 2024 Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 15405164 Bytes = 15044.11 KiB = 14.69 MiB Load Address: 00000000 Entry Point: 00000000 update-initramfs: Armbian: Symlinking /boot/uInitrd-6.1.43 to /boot/uInitrd ln: failed to create symbolic link '/boot/uInitrd': Operation not permitted update-initramfs: Symlink failed, moving /boot/uInitrd-6.1.43 to /boot/uInitrd renamed '/boot/uInitrd-6.1.43' -> '/boot/uInitrd' update-initramfs: Armbian: done. Free space after deleting the package linux-image-6.1.43 in /boot: 67.7M Setting up linux-image-6.1.43-dbg (6.1.43-1) ... Setting up linux-libc-dev:arm64 (6.1.43-1) ... % reboot Tested Kodi again, and black screen Any suggestion? Thanks!!

at kernel 6.6 your wifi work? how? I think wifi was wrong.... thats the current DTS: You can Use it to compare with the original DTB -> DTS file and figure out any error on This DTS file that bring board UP

I dont know about overlays I have uploaded new bluetooth images to drive @pocosparc https://forum.armbian.com/topic/28895-efforts-to-develop-firmware-for-h96-max-v56-rk3566-8g64g/?do=findComment&comment=187569

Yes it was working before as the kernel itself reported that the bin files are missing. Now I am not sure how the kernel was compiled. So it will automatically parse from the config and driver bin files and then create the wlan0 interface?

I dont wanna take this risks with drivers, you can create a Github Pull Request to armbian too. your wifi was working? dont need any fix? i think you wont need to change DTB anymore, just need the kernel 6 binary to brcm4335

What do you want to say with this? This is how I added the tx/rx DMA IRQ names, yes. I don't know why the overlay (if it already exists), was not active on my Rockshit device.

I'm uploading all bluetooth updated images again sudo apt-get install device-tree-compiler you can: dtc -I dtb -O dts h96-tv-box-3566.dtb -o h96-tv-box-3566.dts edit the DTS file to work with wifi and reverse it: dtc -I dts -O dtb -o H96-tvbox-3566-wifi.dtb H96-tvbox-3566-wifi.dts apply it on device i think you will need to find the brcmfmac4335-sdio.firefly,rk3566-roc-pc.bin for kernel 6.6 it was working on 6.2