Mainline kernel not working (no screen)
07-17-2020, 06:05 AM
Hi all,
I successfully started a Debian 10 ARM64 rootfs + initrd, preinstalled using QEMU with LXDE and autologin. For a touch screen this is not easy to use, but I expect using keyboard and mouse soon
Using the 5.6.0-pine64 kernel which was provided with Ubuntu at delivery few weeks ago, having included the 5.6.0-pine64 modules into the debian's initrd, and having the "fstab" file corrected into rootfs, it boots fine. I customised the U-Boot boot script too.
However, I tried to do the same with a 5.8.0-rc5 kernel, using the config-5.6.0-pine64 as .config file for building the 5.8.0-rc5 kernel.
But I have no screen. I tried disabling "Enable loadable module support" so that every driver is embedded/preloaded into the kernel, but nothing more.
When comparing resulting .config, the following lines are missing after having 5.8.0-rc5 kernel built :
I guess the fact of having CONFIG_DRM_PANEL_PINEPHONE_JD9365DA missing may be one of the reasons why I have nothing on the screen...
Are you sure that mainline kernel can really be used on the pinephone?
If so, is there some diffconfig or pinephone64-defconfig somewhere?
Thank you in advance!
I successfully started a Debian 10 ARM64 rootfs + initrd, preinstalled using QEMU with LXDE and autologin. For a touch screen this is not easy to use, but I expect using keyboard and mouse soon
Using the 5.6.0-pine64 kernel which was provided with Ubuntu at delivery few weeks ago, having included the 5.6.0-pine64 modules into the debian's initrd, and having the "fstab" file corrected into rootfs, it boots fine. I customised the U-Boot boot script too.
However, I tried to do the same with a 5.8.0-rc5 kernel, using the config-5.6.0-pine64 as .config file for building the 5.8.0-rc5 kernel.
But I have no screen. I tried disabling "Enable loadable module support" so that every driver is embedded/preloaded into the kernel, but nothing more.
When comparing resulting .config, the following lines are missing after having 5.8.0-rc5 kernel built :
Code:
CONFIG_CC_HAS_WARN_MAYBE_UNINITIALIZED=y
CONFIG_ARCH_CLOCKSOURCE_DATA=y
CONFIG_MEMCG_SWAP_ENABLED=y
CONFIG_ARM64_WORKAROUND_SPECULATIVE_AT_VHE=y
CONFIG_ARM64_WORKAROUND_SPECULATIVE_AT_NVHE=y
CONFIG_ARM64_LSE_ATOMICS=y
CONFIG_ARM64_PTR_AUTH=y
CONFIG_PLUGIN_HOSTCC=""
CONFIG_HAVE_MEMBLOCK_NODE_MAP=y
CONFIG_TRANSPARENT_HUGE_PAGECACHE=y
CONFIG_VEXPRESS_SYSCFG=y
CONFIG_V4L_PLATFORM_DRIVERS=y
CONFIG_VIDEO_SUN4I_CSI=m
CONFIG_VIDEO_SUN6I_CSI=m
CONFIG_V4L_MEM2MEM_DRIVERS=y
CONFIG_DRM_PANEL_PINEPHONE_JD9365DA=y
CONFIG_DRM_PANEL_XINGBANGDA_XBD599=y
CONFIG_DRM_I2C_ADV7533=y
CONFIG_SND_SOC_EC25=m
CONFIG_USB_CHIPIDEA_OF=m
CONFIG_RTL8723CS_NEW=m
CONFIG_COMMON_CLK_VERSATILE=y
CONFIG_CLK_SP810=y
CONFIG_CLK_VEXPRESS_OSC=y
CONFIG_CLKSRC_MMIO=y
CONFIG_CLKSRC_VERSATILE=y
CONFIG_RPMSG_QCOM_GLINK_NATIVE=y
CONFIG_OPTIMIZE_INLINING=y
CONFIG_UBSAN_ALIGNMENT=yI guess the fact of having CONFIG_DRM_PANEL_PINEPHONE_JD9365DA missing may be one of the reasons why I have nothing on the screen...
Are you sure that mainline kernel can really be used on the pinephone?
If so, is there some diffconfig or pinephone64-defconfig somewhere?
Thank you in advance!
