dkebler

If I understand the custom-image script is run as a chroot after the image is built. So didn't see anything specifically in the docs but can I ONLY run (from compile script) the custom image script on an already already built image (in /output/images)? Along the same lines can I chroot at any time to the image via the compile script? I should mention that I am using the docker container build for arm on my amd machine. (i.e. ./compile.sh docker.... )

I wanted to build the cli version but didn't see an obvious way to do that with conf variables and the docs don't illuminate that choice. so I tried BUILD_MINIMAL=no BUILD_DESKTOP=no and that seems to do force the cli version. Just suggesting that this might be easier to grok if the variable was say BUILD_TYPE=(desktop|cli|minimal|custom) with maybe default cli where custom might be a rootfs that is custom (like one I put together) and thus doesn't need to be reconstructed from the custom-image script. Maybe setting custom then RELEASE could hold the path to the tarball? If that seems better maybe I can try making a pr? BTW this is not necessarily a beginner topic but didn't see a category for just generic building discussion.

armbian-config has a way to update the kernel within a major version but can one upgrade from 5.15 to 6.1 (current/edge). I assume if not then I have to build my own image? What I am after is jammy or bullseye with 6.1 kernel to support some hardware not supported in 5.15. I know the rolling releases (Lunar/Sid) have this kernel but I need a LTS release with 6.1.

@iamdrq [SOLVED] That worked including touch! I downloaded the sid image and added the dts file. I didn't know that armbian had a overlay add command. Plus I don't know enough about kernels and overlays to come up with that dts file so THX! As I look at that code I now see that's a way to enable (okay) a stanza/device in an existing dtb module without having to recompile it. So I have learned something! My goal was to set up home assistant on this board but since I had the touch screen I bought originally for running android (now images of that are way old) I wanted to also set up a minimal X and load a browser in kiosk mode pointing to the home assistant page. Now with your help I can do that! Eventually when 6 kernel ends up in stable release I can switch to that. again THX.

OKE I got my script issue resolved needed to use the dts file and only need to precompile it not the other files. My new version of the script is below Was able to compile with the changes you suggested but had to add also the backlight and avdd stanzas. Not sure if they are needed? So I booted and the hdmi goes blank but then the panel does not come up (super sad). So I went back and removed the avdd-supply and backlight but that did not help. So definitely suck now. Hopefully the hardware if functioning. I have no way to tell. I guess I should try the 6.0 kernel but all the current armbian images for rockpro64 are using 5.15 and I have no experience compiling a kernel and I don't think armbian-config will upgrade across major releases. mipi_panel: panel@0 { compatible = "feiyang,fy07024di26a30d"; reg = <0>; avdd-supply = <&avdd>; backlight = <&backlight>; dvdd-supply = <&vcc3v3_s0>; ports { #address-cells = <1>; #size-cells = <0>; port@0 { reg = <0>; mipi_in_panel: endpoint { remote-endpoint = <&mipi_out_panel>; }; }; }; }; #!/bin/bash SRC=/usr/src/linux-source-5.15.80-rockchip64 ARCH=arm64 DIR=$SRC/arch/$ARCH/boot/dts SOC=rockchip INCLUDE=$SRC/include CHIP=rk3399 DEV=$CHIP-rockpro64 DEP1=$CHIP DEP2=$CHIP-opp DST=$DEV.dtb cp $DIR/$SOC/$DEP1.dtsi . cp $DIR/$SOC/$DEP2.dtsi . # cp $DIR/$SOC/$DEV.dtsi . cp $DEV.dtsi.edits $DEV.dtsi cp $DIR/$SOC/$DEV.dts $DEV.dts.tmp cpp -nostdinc -I $INCLUDE -undef -x assembler-with-cpp $DEV.dts.tmp > $DEV.dts dtc -O dtb -b 0 -o $DST $DEV.dts

I wrote up a little script to deal with includes before running dtc per https://stackoverflow.com/a/36298460/4695378 First I tried just remaking the dtb file with the unchanged rk3399-rockpro64.dtsi but throws an error in the rk3399.dtsi dependency file Error: rk3399.dtsi:15.1-2 syntax error FATAL ERROR: Unable to parse input tree I did nothing but copy that file so not understanding why there is a syntax error in a file that was NOT changed. Anyway, stuck at this point with idea of making a new rk3399-rockpro64.dtb I see some armbian images are now shipping the 6 kernel but not the rock64pro ones :(. Even if they did I think I still have to make the dtb file as the dtsi file has those as status "disabled" instead of "okay" So how does one compile a one off dtb file from dtsi that has dtsi dependencies cause I seem to be missing something here.

ok can grab the kernel source via armbian-config. I'll try editing and compiling the 5.15 dtsi first.

For 5.15 Kernel. There are no dtsi files in the image in order to insert and compile. Can I just compile the entire 6.0 dtsi you pointed to and replace that dtb completely or will that break things? Otherwise i guess I have to go grab the dtsi for 5.15 and edit as you say and then compile. Alternatively I could upgrade the entire kernel to 6.0 but again don't know if that will break things. What did you do?

Thx for info. I haven't had a chance to try yet but I'll report back when I do

@iamdrq can you provide more details of what you did. I don't understand what you mean by Thx

ok so I try to load the module manually and get modprobe --first-time drm_mipi_dsi modprobe: ERROR: could not insert 'drm_mipi_dsi': Module already in kernel so it's already in the kernel so WHY is the DSI device not recognized and loaded (its not listed with lsmod) IF it's auto detected in order to load well the cable to the lcd is connected and it was working with android.

Still trying to get this to work. I did see that the kernel config has enabled it. So apparently that kernel module is loaded. `CONFIG_DRM_MIPI_DSI=y` but `CONFIG_DRM_PANEL_DSI_CM=m` is a loadable module The two DSI modules that that be loaded are apparently `cat /lib/modules/$(uname -r)/modules.builtin | grep dsi` kernel/drivers/gpu/drm/drm_mipi_dsi.ko kernel/drivers/gpu/drm/bridge/synopsys/dw-mipi-dsi.ko ` so I added those to /etc/modules dw_mipi_dsi drm_mipi_dsi but on reboot they are not listed by lsmod.| grep dsi So am I barking up the right tree? How come these built-in modules won't load in this way?

I've got jammy running but I have a dsi display for the board and I'd like that to work (well the tp port too) with jammy. Looking at armbian config I see no setting for it. I know the display works fine as if I load an aryufan android image it works as it is set to use DSI by default. Does this kernel know about the DSI port? Do I have to build a custom kernel? If not then what boot env line will get it going?

I tried flashing the spi u-boot, 2020 arufan version. Honestly not sure it took as I saw nothing on the monitor so had no idea if it was successful but now jammy server/cli version boots