06-28-2021, 08:42 AM
(This post was last modified: 06-28-2021, 08:49 AM by moonwalkers.)
(06-28-2021, 05:56 AM)alpopa Wrote: I wander if passing some parameters to kernel does the trick rather than recompilation of it.
Also, I am under impression that for WiFi firmware the best place is linux-firmware-misc package.
I doubt it. My kernel command line besides the usual `root=<device> ro quiet splash` contains only `plymouth.ignore-serial-consoles`. But it also works fine without `plymouth.ignore-serial-consoles`, it's just that I get a wall of text instead of graphical splash in that case.
And for firmware I think more appropriate would be the current firmware-brcm80211 package instead of the no longer existent in Debian linux-firmware-misc package.
(06-28-2021, 07:17 AM)thequailman Wrote: Here are the results:
5.10.40 with CONFIG_ROCKCHIP_CDN_DP unset = display works
5.12.13 with Debian default kernel config = display does not work
So, do I submit a bug report to the Debian kernel team and ask for the config to be unset?
Also, the u-boot in experimental doesn't work, I had to use the one from Manjaro.
I did not recompile 5.10.38, it had CONFIG_ROCKCHIP_CDN_DP=y, yet it worked fine on my machine. I do suspect that it has to do with the version of u-boot, interaction between the firmware and the kernel. BTW, I'm running 5.10.46 right now, Debian's linux-image-5.10.0-8-arm64 from Unstable. Still CONFIG_ROCKCHIP_CDN_DP=y, still works fine with mrfixit's release v2.0 BSP u-boot.
This message was created with 100% recycled electrons