thank's for your request. i have try the upstream dtb from https://github.com/raspberrypi/firmware/
same firmware errors. Boot stop at "Run /init as init process" On 02.01.20 19:24, Nigel Sollars wrote: > Any progress on this? > > On Wed, Jan 1, 2020 at 12:09 PM Nigel Sollars <[email protected]> wrote: >> Looks like device tree's dtb's, as I said seems that your missing alot >> as per the fist errors ( GPIO's ) and the size difference you saw. >> >> more info here >> >> https://github.com/raspberrypi/linux/issues/2543 >> >> with the link pointing here >> >> https://github.com/raspberrypi/firmware/tree/master/boot >> >> Nige >> >> On Wed, Jan 1, 2020 at 6:15 AM basti <[email protected]> wrote: >>> The kernel was build with >>> >>> make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- defconfig >>> make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- menuconfig >>> (to check if raspberry pi stuff is enablend) >>> make -j`nproc` ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- bindeb-pkg >>> >>> I get also firmware errors when I boot the original ubuntu image (log >>> attached). >>> so i think it doesn't matter. >>> >>> Boot the debian kernel I miss something like: >>> >>> [ 4.541716] mmc0: new ultra high speed DDR50 SDHC card at address aaaa >>> [ 4.555228] mmcblk0: mmc0:aaaa SC32G 29.7 GiB >>> [ 4.569103] mmcblk0: p1 p2 >>> >>> RASPBERRYPI_FIRMWARE is set in kernel config. I'm not sure what this >>> mean, what steps i have to do that the kernel use the firmware. >>> In the log attached you can find this: >>> >>> [ 0.096980] raspberrypi-firmware soc:firmware: Attached to firmware >>> from 2019-08-15 12:03, variant start >>> [ 0.100911] raspberrypi-firmware soc:firmware: Firmware hash is >>> 9f8431fb7839c7f00f52b81f5822ddab2b31d0db >>> >>> which file is used there? >>> >>> On 01.01.20 05:23, Nigel Sollars wrote: >>>> Just took a look at the bootlog there, those GPIO failures arnt >>>> clever, missing firmware I would take a wild guess that things in the >>>> latest kernel tree has changed I did also see an article about newer >>>> support for the Pi 4 in the latest kernel ( cant remember if its 5.4 >>>> or 5.5 ). Do you use 'make menuconfig'?. the size difference you >>>> mention with those errors do point to you not enabling the needful >>>> >>>> Looks like 4.19 has been the latest for along time, I would diff your >>>> 5.5 config with the 4.19 and see what you have missing / what has >>>> moved / changed. A quick google does not yield much so you could be >>>> very much on your own / pioneering this one. >>>> >>>> Hopefully helpful links >>>> >>>> Someone to perhaps reach out to for info, >>>> https://forum.manjaro.org/t/raspberry-pi-4-5-4-1-kernel/114273 >>>> >>>> 5.5 Graphics / better support by all accounts, >>>> >>>> https://www.phoronix.com/scan.php?page=article&item=linux-55-features&num=1 >>>> https://www.linux-arm.info/index.php/1537-linux-5-5-lands-broadcom-bcm2711-raspberry-pi-4-bits >>>> >>>> again hope this helps >>>> >>>> Nige >>>> >>>> On Tue, Dec 31, 2019 at 5:18 AM basti <[email protected]> wrote: >>>>> Hello, >>>>> >>>>> I have try to build kernel for raspi4 from upstream (5.5-rc3). Kernel >>>>> boot but can't find the SD Card, so there is no partition, no root-fs >>>>> and end up in initramfs/busybox. >>>>> >>>>> Log of serial console is attached. I have used U-boot and dtb from >>>>> ubuntu image. My dtb build during kernel build is a half size of the >>>>> ubuntu one and doesn't work. >>>>> >>>>> the custom build kernel works on rpi3 out of the box. >>>>> >>>>> best regards >>>>> >>>>> p.s. i build it as deb package
