H96 Max rk3399 TvBox for kernel 6.x

[manhbh]

Hello everyone,
I have an old H96 Max TV box using the rk3399 chip with hexa cores, 1000Mb Lan, 4Gb ram, USB 3.0 and Type C also.
I’ve followed all the steps in this post: Manjaro ARM for Rockchip TV Boxes - #27 by rna
But nothing happens when I plug the SD card into the box. Did I miss any important steps that weren’t mentioned in the post?
Also, the kernel version is now 6.x, so can my TV box run a newer Linux distribution?
Any help would be greatly appreciated.

[SickOS]

You have to follow this link to get the booting.

Manjaro ARM for Rockchip TV Boxes

I have an image for rockchip boxes in my drive, that I think can help rockchip tv users a bit more. https://drive.google.com/drive/folders/13o1S4G5Z3QSoWHrFcC_WPkcFDihUului?usp=sharing It has uboot for nanopc t4 but this can be changed with others included in RK_uboot. Which u-boot works with your box is your task. Making the trials is easy because the flash is made in seconds. So in order to get an install on sd card: 1.- Burn manjaro image with balena etcher. 2.- Burn boot image (e.g. u-b…

[manhbh]

Thank you so much. I started by using your image and then followed the precise steps you RNA outlined, which were:

1. Download the Vim3 image from your Google Drive.
2. Burn the image to an SD card using Etcher.
3. Download “u-boot-rk3399-nanopc-t4” and flash it to the SD Card using these commands:

• sudo dd if=/home/hongmanh/Downloads/u-boot-rk3399-nanopc-t4.img of=/dev/mmcblk0 conv=fsync bs=1 count=442
• sudo dd if=/home/hongmanh/Downloads/u-boot-rk3399-nanopc-t4.img of=/dev/mmcblk/0 conv=fsync bs=512 skip=1 seek=1

4. Configure the uEnv.ini file to set the FDT path to “FDT=/dtbs/rockchip/rk3399-rockpro64.dtb”. However, nothing happened when I inserted the SD card into the box.

Then, I replaced the box’s default bootloader with AndroidTool following i12bretro’s YouTube tutorial https://www.youtube.com/watch?v=Ek8-NXrgJtM (using rk3399_loader_v1.26.bin for my box instead of RK3288Loader_uboot_V2.17.02.bin mentioned in video).
Now, when I plug in the SD card, I can enter the Manjaro boot screen.

But I’m stuck at the initial setup. After choosing the US keyboard, setting my username to “manhbh”, and leaving the other fields blank, when I click “Ok” to confirm, I get the message “=> Configuration aborted. Restarting OEM script…” and I’m back at the beginning, choosing the keyboard again. I’ve tried this multiple times but it’s like I’m stuck in a loop.

---

Mod edit:- Please avoid posting screenshots of textual content when a brief description is all that is needed.

[SickOS]

If you don’t follow the steps in my link can not help you.

[Darksky]

@manhbh

But I’m stuck at the initial setup. After choosing the US keyboard, setting my username to “manhbh”, and leaving the other fields blank,

I have never left fields blank other than the one to add extra groups where it says you can just hit enter. I bet info is required in the missing fields.

[manhbh]

Initially, I tried using the Vim3 image, but then I switched to the Nanopc T4 image following your guidance, hoping for better results. As suggested by Darksky , I filled in all fields on the initial setup screen except for “additional groups”. Thanks, @Darksky !

I’m now able to log in to the desktop environment, but I’m encountering an issue when trying to update the system using the command “sudo pacman -Syu”. I’m getting this error:

warning: removing ‘linux’ from target list because it conflicts with ‘linux-aml’
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: linux-aml and linux-lts are in conflict

I’m unsure how to resolve this error as this is my first time using Manjaro.

[SickOS]

You have learned to boot and then I think you have to move to a more recent image. I would try with the station P1 image in manjaro arm github and if it does not boot we can repair It.

Remember to change de dtb file in extlinux. Tell us which dtb you use in future message.

Linux-aml? So you are in VIM3 image

[Darksky]

I do not know about his device but the vim3 kernel got switched from linux-aml to linux quite a while ago. I believe it switched to linux-lts at the time. I personally keep my kernel up to date here locally for it amd my rock64pro:

Linux vim3 6.12.5-1-MANJARO-ARM #1 SMP PREEMPT Sat Dec 14 17:17:03 CST 2024 aarch64 GNU/Linux

[manhbh]

In your Google Drive, there were two images: Vim3 and Nanopc T4. Initially, I was drawn to the XFCE desktop environment, so I chose the Vim3 image without hesitation when I saw “XFCE” in the image name.

Currently, I’m using the Nanopc T4 image and I’m encountering a ‘linux-aml’ and ‘linux-lts’ conflict error when updating the system. After using Nanopc T4, I’m really impressed with the desktop environment, which is something I couldn’t find in Armbian’s XFCE. Thank you!

By the way, I’m using “rk3399-hugsun-x99.dtb” for my box in the extlinux.conf file.

I have a question: I’m using the Nanopc T4 image flashed to an SD card using Etcher, but why do I need to flash “u-boot-rk3399-nanopc-t4.img” to the SD card again?

[SickOS]

You dont have to burn uboot. This is for other boxes.

[spikerguy]

Try to use rk3399 based image instead of vim3 image.

why dont you try nanopc-t4 image?

Just triggered a new dev build. Wait for it to build and then download the latest image and give it a try.

[manhbh]

Thank you very much. Your link is helpful to me.