![]() |
Official Debian support - Printable Version +- PINE64 (https://forum.pine64.org) +-- Forum: Pinebook Pro (https://forum.pine64.org/forumdisplay.php?fid=111) +--- Forum: Linux on Pinebook Pro (https://forum.pine64.org/forumdisplay.php?fid=114) +--- Thread: Official Debian support (/showthread.php?tid=14109) |
RE: Official Debian support - moonwalkers - 06-30-2021 (06-29-2021, 11:31 PM)sepp Wrote: CONFIG_ROCKCHIP_CDN_DP=y in 5.10.0-7-arm64 stock with u-boot by pcm720 also fineYup. I believe 5.10.0-7 (actual version 5.10.38) is the one that first introduced whatever fix that got CONFIG_ROCKCHIP_CDN_DP=y and BSP u-boot working together for a functional built-in display. Earlier stock kernel versions wouldn't work with built-in screen at all, not unless rebuilt with CONFIG_ROCKCHIP_CDN_DP unset. RE: Official Debian support - moonwalkers - 07-01-2021 MicroSD card installer probably didn't work for me because it's using u-boot-rockchip from unstable, version 2021.01+dfsg-5. Just now I was upgrading eMMC, and after cloning the old eMMC to the bigger new one I tried installing Debian's u-boot before removing the old eMMC, and it booted fine, with actual menu shown on built-in display. The u-boot-rockchip I installed is 2021.07~rc4+dfsg-1 from experimental. All I had to do was run `sudo u-boot-install-rockchip /dev/mmcblk2` and reboot. Haven't yet tested other things, like deep sleep, though I wouldn't be surprised if it didn't work properly. But then it wasn't working properly on BSP u-boot for me any more either, not since I started running stock Debian kernel. So at this point the only non-stock Debian things present on my system are WiFi firmware blobs and couple sound-related hacks, like tweaked and marked immutable alsa.state file and acpid hack for muting speakers when headphones are connected, and the only possible missing functionality that I'm aware of is deep sleep. Yay! As I mentioned before though, my setup is simple as a nail - single bootable ext4 partition starting at 16MiB, no LUKS/LVM, no separate /boot, no UEFI, no GRUB, no etc., just u-boot reading /boot/extlinux/extlinux.conf automatically generated by u-boot-menu. I don't have flash-kernel either, since I don't use separate /boot in this setup. RE: Official Debian support - sepp - 07-03-2021 (07-01-2021, 09:58 AM)moonwalkers Wrote: MicroSD card installer probably didn't work for me because it's using u-boot-rockchip from unstable, version 2021.01+dfsg-5. Just now I was upgrading eMMC, and after cloning the old eMMC to the bigger new one I tried installing Debian's u-boot before removing the old eMMC, and it booted fine, with actual menu shown on built-in display. The u-boot-rockchip I installed is 2021.07~rc4+dfsg-1 from experimental. All I had to do was run `sudo u-boot-install-rockchip /dev/mmcblk2` and reboot. Haven't yet tested other things, like deep sleep, though I wouldn't be surprised if it didn't work properly. But then it wasn't working properly on BSP u-boot for me any more either, not since I started running stock Debian kernel.any news on deep sleep? RE: Official Debian support - moonwalkers - 07-04-2021 (07-03-2021, 01:02 PM)sepp Wrote: ny news on deep sleep? Doesn't seem to work yet. Can't say I'm surprised, TBH. RE: Official Debian support - alpopa - 07-05-2021 (06-27-2021, 07:50 PM)thequailman Wrote: Ok I'm getting closer. I think the problem is with the linux kernel, specifically the option CONFIG_ROCKCHIP_CDN_DP=y is set on the Debian 5.10.40 kernel. This may cause issues, as I have found a couple of references (https://www.kulesz.me/post/150_devuan_pinebookpro/) to recompiling a kernel without this option and it fixes the display. Curiously, the working Manjaro image runs 5.12 with this option set to yes, so I'm wondering if it's fixed in the latest stable kernel. (06-29-2021, 02:11 AM)sepp Wrote: Finally I figured it out: Debian bullseye stock on nvme:Any chance to upstream / document these findings in Debian? RE: Official Debian support - sepp - 07-06-2021 (07-05-2021, 06:42 AM)alpopa Wrote: [quote pid='96752' dateline='1624954285']Any chance to upstream / document these findings in Debian? [/quote] Debian devs are probably busy with the release day approaching - let's see after that and at the end it is an ugly hack just to get things going RE: Official Debian support - sepp - 07-09-2021 I am stuck!!! and obviously too stupid to figure it out myself I went away from stock 5.10.07 linux-image and use @"xmixahlx" debian packages from here https://github.com/xmixahlx/debian-packages/tree/master/pbp-tools/linux/5.8.5. Very stable and no issues for me. So I got adventurous and wanted to build my own (make deb-pkg: .config copied from @xmixahlx build) Builds and installs without an error but does not boot. I figured I"d need some magic (mkimage?) to convert the vmlinuz into something u-boot can work with. mkimage -l vmlinuz-5.8.5-0.40-1-pinebookpro-hwaccel (this is xmixahlx"s) GP Header: Size 4d5a0091 LoadAddr ffff5114 mkimage -l vmlinuz-5.10.48-0.40-1-pinebookpro-hwaccel (this mine) shows no output as said stuck and any help is appreciated RE: Official Debian support - moonwalkers - 07-09-2021 (07-09-2021, 06:02 AM)sepp Wrote: I am stuck!!! Sorry, the only issue I ran into when building own kernels was forgetting to disable generating compressed image - IIRC u-boot have some issue with those. Considering mkimage is a part of u-boot-tools package, could it be that it shows no output because of that? RE: Official Debian support - sepp - 07-09-2021 (07-09-2021, 08:56 AM)moonwalkers Wrote:(07-09-2021, 06:02 AM)sepp Wrote: .... Not sure. vmlinuz-5.10.07 stock as well as @xmixahlx 's vmlinuz-5.8.5-0.40-1-pinebookpro-hwaccel seem to be to small for an uncomressed kernel image RE: Official Debian support - moonwalkers - 07-09-2021 (07-09-2021, 09:09 AM)sepp Wrote: Not sure. vmlinuz-5.10.07 stock as well as @xmixahlx 's vmlinuz-5.8.5-0.40-1-pinebookpro-hwaccel seem to be to small for an uncomressed kernel image I wouldn't say that. E.g. the kernels on my x86 work laptop that is a-OK with compressed ones are all less than 10MiB, but the kernels on my PBP are all over 25MiB+. What's the size of your kernels, the problematic one included? |