Trying to run gentoo on a renegade and noticed a discrepancy between what’s available in an official image and what I can compile from the libretech git repositories.
The official images include dtb overlays and a rockchip-fixup.scr. Those are not in the dtb files included in the standalone kernel image.
I’m wondering if that’s partially what’s causing some issues for me. I got a system to boot ok but I’m getting repeated dumps in dmesg from the framebuffer.
At the time, yes. Is there a different image in the download sections for the board that it would be better for me to use as my baseline comparison? It was the only thing I could readily see that was different that might be causing the temporary hanging and thread dump messages.
Armbian is a separate project. We don’t support it directly. It is best to ask on the Armbian forums. We release generic distros like Raspbian, Debian, and Ubuntu.
same original issue regardless. I had assumed it was a missing overlay but I guess not. I can open a separate inquiry/issue if needed but tying to run gentoo using the kernel source from the libretech git repository (currently 6.1.87) and get constant threaddumps for rockchip-drm and never get a display.
U-Boot is throwing no errors:
Scanning bootdev 'mmc@ff500000.bootdev':
0 extlinux ready mmc 1 mmc@ff500000.bootdev.part /extlinux/extlinux.conf
** Booting bootflow 'mmc@ff500000.bootdev.part_1' with extlinux
MMC 1 extlinux.conf
1: libretech-6.1.87
Enter choice: 1: libretech-6.1.87
Retrieving file: /vmlinux-6.1.87-g9f51a48ea718
Retrieving file: /initramfs-6.1.87-g9f51a48ea718.img
append: root=UUID=ed71767d-6442-4417-972d-6cab80d983dd rootfstype=xfs
Retrieving file: /dtb/rockchip/rk3328-roc-cc.dtb
Moving Image from 0x2080000 to 0x2200000, end=4f80000
## Flattened Device Tree blob at 01f00000
Booting using the fdt blob at 0x1f00000
Working FDT set to 1f00000
Loading Ramdisk to f44f2000, end f569a587 ... OK
Loading Device Tree to 00000000f44e2000, end 00000000f44f12da ... OK
Working FDT set to f44e2000
Can you elaborate? I used the libretech-flash-tool to flash the u-boot to the flash card. Which bootloader exactly. Are you saying it only works if I set things up with EFI? Do I have to explicitly transfer the bootaa64.efi from one of your images or is the code for it in git?
NOTICE: BL31: v2.9(release):v2.8-1351-g8929dffc0
NOTICE: BL31: Built : 16:23:24, Oct 13 2023
NOTICE: BL31:Rockchip release version: v1.2
U-Boot 2023.07+ (Oct 13 2023 - 16:23:26 -0400) Libre Computer ROC-RK3328-CC
DRAM: 4 GiB
PMIC: RK8050 (on=0x40, off=0x00)
Core: 244 devices, 31 uclasses, devicetree: separate
MMC: mmc@ff500000: 1, mmc@ff520000: 0
Loading Environment from FAT... Unable to use mmc 1:1...
** File not found boot.ini **
Error (-1): cannot determine file size
unsupported rate 18446744073709551615
TMDS clock is zero!
inno_hdmi_phy phy@ff430000: PHY: Failed to power on phy@ff430000: -22.
failed to on hdmi phy (ret=-22)
unsupported rate 18446744073709551615
TMDS clock is zero!
inno_hdmi_phy phy@ff430000: PHY: Failed to power on phy@ff430000: -22.
failed to on hdmi phy (ret=-22)
unsupported rate 18446744073709551615
TMDS clock is zero!
inno_hdmi_phy phy@ff430000: PHY: Failed to power on phy@ff430000: -22.
failed to on hdmi phy (ret=-22)
U-Boot 2023.07+ (Oct 13 2023 - 16:23:26 -0400) Libre Computer ROC-RK3328-CC
Model: Libre Computer ROC-RK3328-CC
starting USB...
Bus usb@ff5c0000: USB EHCI 1.00
Bus usb@ff5d0000: USB OHCI 1.0
Bus usb@ff600000: generic_phy_get_bulk : no phys property
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
Bus usb@ff580000: USB DWC2
scanning bus usb@ff5c0000 for devices... Device NOT ready
Request Sense returned 02 3A 00
2 USB Device(s) found
scanning bus usb@ff5d0000 for devices... 1 USB Device(s) found
scanning bus usb@ff600000 for devices... 2 USB Device(s) found
scanning bus usb@ff580000 for devices... 1 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
Hit any key to stop autoboot: 0
=>
Whatever device tree you booted Linux with is not ours. It says Firefly roc-rk3328-cc. You need to use our u-boot and pass the builtin $fdtcontroladdr to Linux.
I think I fixed it. Weird, b/c what I had should have worked. I was explicitly calling the DTB in the variables i was sending the bootloader, telling it to use $BOOT/dtb/rockchip/rk3328-roc-cc.dtb which should be the exact same one you’re calling according to the u-boot printenv. (fdtfile=rockchip/rk3328-roc-cc.dtb) I removed that line from my extlinux.conf file and now boot cleanly. Thank you for the help with this.