ok Nigel, the tutorial on https://gist.github.com/G-UK/ee7edc4844f14fec12450b2211fc886e
is working. so i have build a 4.19 kernel to boot rpi4. but this is not the problem. The main reason I use "real" debian system is the horrible kernel name schema on raspbian. that's make the task to do a remote kernel update on a system where only ssh access is available more to a game of luck then to a administrative task. especial when you need a initram to boot like in my case. Or even you have to write a buggy wrapper to fix this. In my opinion debian has find a good way for that problem. So i highly prefer this system/kernel and the way it boots. An other side effect is that it seems to have a better network stack. I used some rpi3 as apt cacher and with debian 64bit there is a better performance of the already cached files but is can also be caused on the 64bit. I haven't check this very much. The dtb files build with kernel 4.19 dosen't also work, when i try to boot my custom 5.5 kernel. Boot stop at "Run /init as init process" but most of the firmware errors seems to be fixed. So I'am looking forward the day were there is a 5.5 branch on raspberr kernel source and try the vanilla/upstream debian kernel again unless you have an idea how to fix "Run /init as init process" as described above. thanks a look for your help. On 02.01.20 21:36, Nigel Sollars wrote: > Ok cool, > > So I did some more looking around, perhaps looking at this ( if you > have not yet ) might be pertinent, > > https://gist.github.com/G-UK/ee7edc4844f14fec12450b2211fc886e > > Nige > > On Thu, Jan 2, 2020 at 2:02 PM basti <mailingl...@unix-solution.de> wrote: >> 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 <nsoll...@gmail.com> 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 <mailingl...@unix-solution.de> 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 <mailingl...@unix-solution.de> >>>>>> 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 >
