Gunjan Gupta

mtdblock is nand devices. For sdcard and emmcs, it should be something starting with mmcblk.

We are aware of it. The HDMI patch that we are trying to integrate is from Jernej's tree as well. What you need to understand is that we have a generic kernel for all 64-bit allwinner SoCs, which means we have patches that can conflict changes that are done simply on top of mainline tree.

I have never used any of those small screens myself, so can't help you with testing it. However you can try to find some script or library online similar to https://luma-oled.readthedocs.io/en/latest/intro.html. Does the driver get loaded automatically now after making those changes in armbianEnv.txt file? Looking at your first post, I realised that you don't need param_spidev_spi_cs=1 as you are using CS0 (PC3), but param_spidev_spi_bus=0 is required.

modprobe fb_ssd1351 try adding the following to your armbianEnv.txt file param_spidev_spi_bus=0 param_spidev_max_freq=4500000 Save and reboot. See if that makes a difference. I also noticed that you have enabled spi-add-cs1 overlay, so you might also want to add param_spidev_spi_cs=1 to your armbianEnv.txt file.

I don't see any output from fb_ssd1351 module. Do you see it listed in lsmod output? Also does screen work if you load the module yourself? Also please share the content of your /boot/armbianEnv.txt file

can you share the dmesg output?

This should work, I guess /dts-v1/; /plugin/; &pio { ssd1351_pins: ssd1351_pins { pins = "PA6", "PG9"; function = "gpio_out"; }; }; &spi0 { ssd1351: ssd1351@0{ compatible = "solomon,ssd1351"; reg = <0>; pinctrl-names = "default"; pinctrl-0 = <&ssd1351_pins>; spi-max-frequency = <4500000>; bgr = <0>; bpp = <16>; rotate = <0>; fps = <25>; buswidth = <8>; reset-gpios = <&pio 0 6 1>; // PA6 dc-gpios = <&pio 6 9 0>; // PG9 debug = <0>; solomon,height = <128>; solomon,width = <128>; solomon,page-offset = <0>; }; }; Save this into a file and then use "armbian-add-overlay <filename>" to enable the overlay. You will also have to enable spi0 using armbian-config > system > hardware

or use post_family_config hook function in your board file to override the value of KERNELPATCHDIR variable

BTW I am working on migrating armbian to 6.7 kernel - https://github.com/armbian/build/pull/6079 Feel free to test and comeback. currently it fails compilation for xradio and some realtek wifi drivers that I will fix today. It can be compiled when building with EXTRAWIFI=no, but that will skip compiling uwe5622 driver. Edit: Compilation issue is now fixed.

Will take a look and get back to you

Thats from armbian-firstrun. It tends to give that message if no display is detected. Most likely will be due to missing audio hub patches - https://github.com/orangepi-xunlong/linux-orangepi/commit/cfe0a8df18c2418f77acb24b17b88c9271d9613c

Looks like there might be another H618 board in the pipeline named orange pi r1b - https://github.com/orangepi-xunlong/orangepi-build/blob/next/external/config/boards/orangepir1b.conf

That message is pretty early in boot. Also 517 is EPROBE_DEFER which means pin is not available right now and driver will retry to grab it later. Its feel its ok to have that message unless it breaking some functionality. That sounds correct That not needed. Are your changes in your git branch? May be I can take a look

quick look into xfpm-backlight-helper shows it is manipulating files in /sys/class/backlight. If the goal is to do it from /etc/rc.local, probably you can do the same as well.

Could you share the output of dmesg | grep sun4i-drm It would be best if you can share complete dmesg output

@pixdriftTry hdmi on orange pi zero 2 for both 6.1 and 6.6 kernel from my branch - https://github.com/viraniac/armbian_build/tree/h616-hdmi If this works, I will then move all the orangepizero2 patches to orangepizero.dtsi. I want to get this out of the way before I bump the edge kernel to 6.7

@pixdrift could you please test the kernel from the following link on Orange Pi Zero 2 - https://drive.google.com/drive/folders/1cjCyISx3r7bVlXEPapf_5BbONQMyTcHX?usp=drive_link This kernel has all of the sun4i-drm patches enabled. See if HDMI works

https://github.com/armbian/build/pull/6070 should fix the cpufreq hang issue and should also get bluetooth working for orange pi zero 2

Adjust patch/kernel/archive/sunxi-6.6/patches.armbian/arm64-dts-allwinner-h616-Add-efuse_xlate-cpu-frequency-scaling-v1_6_2.patch to patch arch/arm64/boot/dts/allwinner/sun50i-h616-orangepi-zero.dtsi instead of arch/arm64/boot/dts/allwinner/sun50i-h616-orangepi-zero2.dts Interesting. So it happens on h616 as well. Its that wifi driver causing the trouble again. I have encountered this issue on Orange Pi 3 LTS as well. I ended up removing sprdwl_ng from MODULES and loaded it instead using a systemd service. See https://github.com/armbian/build/commit/608618a6f5b341a1a171d3a0841a4807432d8294

There is not enough information to debug your issue. Please share the following Device name that you are having the issue with. Do not abbreviate the device name it will only cause confusion How are you connected to the network, ethernet or wifi? Any firewall rules defined on the device or router/switch? Any other thing related to your setup that can be a variable in this scenario? Any other modifications on the device or is it just a clean install? Can you share the logs from your device?

Bluetooth is not going to work. Its currently broken in zero2 as well. The kernel has the required driver, but the hciattach binary and corresponding service file for the same is missing. I am going to create a extension for uwe5622 wireless module that should make it easy to set this thing in the future

There are five different patches that are imported from megous kernel tree (xff.cz) that conflicts with hdmi patch. The hdmi patch has to be rewritten to fix the same. I haven't started working on it yet, but I will do it soon. Most likely within next 2 weeks window as I would be bumping the allwinner kernel versions. Legacy kernel will be moved o 6.1, current to 6.6 and edge kernel to 6.7

The post has zero information about the soc you are targetting, changes that you made and output you got on serial console when you tried booting. I don't think anyone can help you without getting that information

Thats correct Didn't you yourself said that you need seperate boot partition? That means everything else is in root partition. What else were you expecting to be in boot partition?

Bionic has been out of support for some time now. Try upgrading to focal and then to jammy to get to latest release. Alternatively, you can also download and flash latest image from the download page.