Jump to content

Recommended Posts

Posted

I'm trying to build an abian trixie image with the CONFIG_DRM_PANEL_MIPI_DBI support module enabled in the kernel. However, no matter how many times I build, when checking the modinfo module, panel-mipi-dbi is not found. In the /boot/config(kernel) configuration, the line is commented out: #CONFIG_DRM_PANEL_MIPI_DBI is not set

I set M to the panel-mipi-dbi kernel module parameter. I also set Y to the parameter. I also tried adjusting the .config file before running the image build. I used both Docker and non-Docker builds. I'm using Ubuntu 22.04.

Posted (edited)

Thank you very much for your answer.

 

sudo apt install docker.io

 

git clone https://github.com/armbian/build armbian

 

cd armbian/

 

./compile.sh

 

In the configurator, I select the custom plate orangepizero3, and then the Trixie release. Then in the configurator, I select device-driver->graphic-support->drm->drm-panel-mipi-dbi-support Then I save the configuration under a custom name. Then exit, exit, exit, and load the configuration.

When asked if I wanted to save the new configuration, I selected both options, but the result was always the same: the module wasn't compiled into the kernel.

Edited by Orima
Posted

Can you post/do something like this:

Quote

git clone https://github.com/armbian/build
cd build
./compile.sh kernel-config \
BOARD=rock-3a \
BRANCH=edge \
BUILD_DESKTOP=no \
BUILD_MINIMAL=no \
RELEASE=trixie \
NETWORKING_STACK="network-manager" \
ROOTFS_TYPE=btrfs \
BTRFS_COMPRESSION=zstd \
BOOTSIZE=512 \
COMPRESS_OUTPUTIMAGE=sha \
FIXED_IMAGE_SIZE=4096 \
EXTRAWIFI=no \
KERNEL_BTF=no \
KERNEL_GIT=shallow
 

I use Armbian Trixie on ARM64 computer to do builds. I banned Ubuntu (certainly old Jammy) and also do not use docker. 

Posted

I'm using compile.sh without any arguments. Can I add the adra module argument to the command? How well will this work? For example, like this: ./compile.sh CONFIGURE_DRM_PANEL_MIPI_DBI=m I tried this, but I got a compilation error saying there was no such argument.

Posted
On 12/11/2025 at 7:18 PM, Orima said:

Are you sure you can't help me?

 

People are already helping you.  But, they're mostly helping you to help yourself.

One thing you can do to make it easier for people to help you is to add the SHARE_LOG build switch to ./compile.sh.  That way your build log will be uploaded and you can share the link here.

Posted

So, here's what I had to do to successfully build the image. First, I corrected my board file in the config/board/orangepizero3.csc directory. The processor value was incorrect, it was 616, so I set it to 618.

Menuconf suggested selecting a board with a 618 chip, but in the board file it was listed as family 616.

Later, I copied my board file to the userpatches directory and added the value CONFIG_DRM_PANEL_MIPI_DBI=m. Then I ran the image build script with the menuconf viewer. I was surprised that the CONFIG_DRM_PANEL_MIPI_DBI parameter already had the value "m"; previously, it was empty.

After all these manipulations, the build went smoothly. Thank you so much for your support.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines