• Content Count

  • Joined

  • Last visited

  1. Hello Werner, Thank you for your propt reply. The output of armbianmonitor -u has been located here: The device tree has been changed according this description (last post): I changed the device tree to integrate the axp209 PMIC driver according to the configuration given in BananaPi's device tree and added SPDIF-Support. So please don't mind about messages which don't appear on usual BananaPro images. regards
  2. Hello, Im currently working on making lima run with an original 5"-LCD on BananaPro. My problem is to make it work with the sun4i-drm driver. At boot everything works fine and the display shows u-boot and kernel outputs but when the kernel starts the sun4i-drm driver the display freezes and turns white after some seconds. dmesg says: [ 11.178221] sun4i-drm display-engine: bound 1e00000.display-frontend (ops 0xc09986d4) [ 11.178361] sun4i-drm display-engine: bound 1e20000.display-frontend (ops 0xc09986d4) [ 11.178858] sun4i-drm display-engine: bound 1e60000.display-backend (ops sun4i_backend_ops [sun4i_backend]) [ 11.179226] sun4i-drm display-engine: bound 1e40000.display-backend (ops sun4i_backend_ops [sun4i_backend]) [ 11.179943] sun4i-drm display-engine: No panel or bridge found... RGB output disabled [ 11.179970] sun4i-drm display-engine: bound 1c0c000.lcd-controller (ops 0xc09973fc) [ 11.180653] sun4i-drm display-engine: No panel or bridge found... RGB output disabled [ 11.180675] sun4i-drm display-engine: bound 1c0d000.lcd-controller (ops 0xc09973fc) [ 11.195807] sun4i-codec 1c22c00.codec: Codec <-> 1c22c00.codec mapping ok [ 11.204374] sun4i-drm display-engine: bound 1c16000.hdmi (ops sun4i_hdmi_driver_exit [sun4i_drm_hdmi]) [ 11.204391] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 11.204395] [drm] No driver support for vblank timestamp query. [ 11.204411] checking generic (7fe89000 177000) vs hw (0 ffffffff) [ 11.204422] fb0: switching to sun4i-drm-fb from simple [ 11.205292] Console: switching to colour dummy device 80x30 [ 11.206140] [drm] Initialized sun4i-drm 1.0.0 20150629 for display-engine on Lima was set up properly and works with HDMI output so far. What confuses me is the line where it says "No panel or bridge found... RGB output disabled". The 5"LCD is connected via RGB-Interface and has already been working less than a second before. So it seems the display has not been detected properly by the sun4i-drm module. Has anyone ever had a similar Problem? Any suggestions where to search for the problem's solution? regards
  3. I got lima working on BananaPro by adding following contents to build/cache/sources/u-boot/v20XX.XX/arch/arm/dts/sun7i-a20-bananapro.dts : Enable HDMI: Enable display engine: Change build/cache/sources/linux-mainline/orange-pi-5.XX/arch/arm/boot/dts/sun7i-a20-bananapro.dts accordingly. Then compile the mesa driver like this: nano /etc/apt/sources.list // uncomment #src apt update apt build-dep -y mesa apt install -y git g++ build-essential pkg-config apt install -y libx11-dev libgl1-mesa-dev apt install -y valgrind cmake libunwind-dev apt install -y libudev-dev // if you get meson version errors apt install -y python3-pip pip3 install --upgrade meson git clone cd mesa/ /usr/local/bin/meson build/ --optimization s --buildtype release --libdir=/usr/lib/arm-linux-gnueabihf -Dgallium-drivers=lima,panfrost,kmsro,swrast -Dplatforms=x11,drm,surfaceless ninja -C build/ ninja -C build/ install Now it's working (at least to run Kodi, but there ist still a great difference in power between this lima driver version and the mali driver provided at! I don't know what changes are necessary to BananaPi but the Problems concerning SATA and AHCI seem to come from a different way of handling the PMIC. I saw similar dts-files with that specific PMIC axp209.dtsi-file. They got a AHCI-tag looking like this: Maybe the target-supply-line will do the thing. I'll ty later. Never the less i get problems when starting my original allwinner 5"-LCD using this tutorial: I changed the parameters from 7"-LCD to 5"-LCD and itis working very well without displayengine enabled. But when I enable it the screen freezes at boottime, right after saying "starting networkinterfaces". Has anyone ever had the same problem and can help me with that?
  4. lsmod shows sun4idrm and as far as i can say all devices needed are where they should be. On that base Lima can be run with basic functionality. It does not work like a charm (not all GL-Drives do work) but lima is able to run kodi.
  5. I just built the lastest armbian sources for BananaPi minimal, which is version Armbian_20.08.0-trunk_Bananapi_buster_current_5.4.44_minimal and startet ist on my BananaPro. After that I got mesa running doing this: ... and kodi on X11 started properly. Got into Kodi->Systeminformation. There it says lima driver is used. This failed on various BananaPro images before. The question is how to integrate that into a build script. Furthermore there seem to be some differences between the image configuration of BananaPi and BananaPro although the only differences are integrated WIFI-Device (Pro) and 40-Pin GPIO (Pro). Therefore there should be no differences between processorelated functionality. Differences known so far (each image tested on bananapro): AHCI does work properly on Pro but fails on Pi, sun4i-drm works on Pi but not on Pro I`m going to try some reverse engineering to find the differences in configuration.
  6. Finally got it to work building mesa on my own on a recent BananaPi image But it would be very cool if the sun4i-drm driver was fixed in BananaPro images. Can you please take care of that, Igor? I'll help you as far as I can and will provide further information from my test machine.
  7. On the BananaPi image startx says: Indeed /usr/lib/arm-linux-gnueabihf/dri/ contains various * files but none called sun4i-drm. Any suggestions what to do?
  8. Thanks a lot for your replies! I still have the problem lima does not work properly. Module sun4i-drm, which is needed for lima, is avaliable via modprobe (at least ist gives no error message), but seems not to be loaded either. lsmod does not show it. I don't exactly know what is wrong but it seems there is a problem with the compiled driver. When I look into /lib/modules/5.4.44-sunxi/kernel/drivers/gpu/drm/sun4i/ there is just a file called sun6i_mipi_dsi.ko. What has sun6i todo with sun4i? The GPU is a different one (Power VR SGX 544 instead of Mali 400). The only thing I've found on my system is /sys/bus/platforms/drivers/sun4i-drm. There is no device bound to and no module connected. So I've build an image for bananapro myself, but it looks the same. For some reason I compiled an image for bananapi and surprisingly sun4i-drm has been loaded. I´m going to check if it works correctly... I'm interested in the differences between those two configurations and of course it would be very nice to apply this configuration also to the bananapro image!
  9. Hello guys, I've been playing around with the build-in lima drivers but didn't get it to work on BananaPro using Armbian_20.02.1_Bananapipro_buster_current_5.4.20_desktop image. I installed drivers armsoc, modesetting, fbdev from debian buster repos but "Xorg -configure" fails. /var/log/Xorg.0.log says: and and generated xorg.conf: Any suggestions what I am doing wrong? regards
  10. Hello there, I'm new to this Forum, so please I been trying to run Kodi as standalone music station with Buster minimal and Kodi 17 on it. This system boots very quick and I've been quite happy when I got kodi starting successfully, but it's very slow. It takes several seconds to switch from one menu item to the next. Next I tried to speed up the graphics using this instructions But failed with xorg saying: /etc/X11/xorg.conf: There is no /dev/mali, /dev/ump or /dev/disp device available. Modules ump, mali, mali_drm are not loaded, but I saw lima drivers were active: I hope we can get this working either via mali or using lima driver. Thanks in advance für your help! regards