Skip to main content ↑ ↓
Topic: change in /boot for linux-raspberrypi4-5.10.17-3-aarch64.pkg.tar.xz (Read 958 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

change in /boot for linux-raspberrypi4-5.10.17-3-aarch64.pkg.tar.xz

Not sure who maintains the armtix kernel packages, but I observe a change between

linux-raspberrypi4-5.10.17-2-aarch64.pkg.tar.xz and linux-raspberrypi4-5.10.17-3-aarch64.pkg.tar.xz

Code: [Select]
sudo diff -brw {2,3}/boot
Only in 2/boot: bcm2710-rpi-2-b.dtb
Only in 2/boot: bcm2710-rpi-3-b.dtb
Only in 2/boot: bcm2710-rpi-3-b-plus.dtb
Only in 2/boot: bcm2710-rpi-cm3.dtb
Only in 2/boot: bcm2711-rpi-400.dtb
Only in 2/boot: bcm2711-rpi-4-b.dtb
Only in 2/boot: bcm2711-rpi-cm4.dtb
Only in 2/boot: bcm2837-rpi-3-a-plus.dtb
Only in 2/boot: bcm2837-rpi-3-b.dtb
Only in 2/boot: bcm2837-rpi-3-b-plus.dtb
Only in 2/boot: bcm2837-rpi-cm3-io3.dtb
Only in 3/boot: broadcom
Binary files 2/boot/rpi4Image and 3/boot/rpi4Image differ

I am trying to maintain a traditional boot using the 'standard' layout as used by raspberrypi and my post install hook failed to catch that move of the bcm files into /boot/broadcom. For the standard boot process they have to be in /boot I wonder why the artix boot is not like the 'official' boots. The alarm boot also fails for me.

I know there is some intention to try and get u-boot working, but I wonder exactly why armtix doesn't just use the firmware mechanisms.
 

Re: change in /boot for linux-raspberrypi4-5.10.17-3-aarch64.pkg.tar.xz

Reply #1 –
Hi!
I'm building armtix packages and recently made rpi4 work correctly. The thing is, i am trying to make different boot schemes possible. By moving dtbs back to /boot/broadcom (ALARM explicitly moves them out there) i make rpi4 kernel compatible with u-boot (although it doesn't support rpi4 usb yet) and make /boot a bit more clear
ARMtix

Re: change in /boot for linux-raspberrypi4-5.10.17-3-aarch64.pkg.tar.xz

Reply #2 –
Quote from: phoenix_king_rus – on
Hi!
I'm building armtix packages and recently made rpi4 work correctly. The thing is, i am trying to make different boot schemes possible. By moving dtbs back to /boot/broadcom (ALARM explicitly moves them out there) i make rpi4 kernel compatible with u-boot (although it doesn't support rpi4 usb yet) and make /boot a bit more clear
I understand that you are trying to make the uboot version work, but I  suppose you have some special reason for that. If I know that those files will be there in /boot/broadcom I can always write the hooks that make it work oldstyle. Presumably the correct way to do that is to reverse in pre-install any changes that are required in post install. That will at least keep  pacman happy.

You say you don't have rpi4 usb working; that is similar to the problem I have with alarm; I could see the boot happening, but no mouse or keyboard was usable.

Re: change in /boot for linux-raspberrypi4-5.10.17-3-aarch64.pkg.tar.xz

Reply #3 –
Quote from: replabrobin – on
If I know that those files will be there in /boot/broadcom I can always write the hooks that make it work oldstyle. Presumably the correct way to do that is to reverse in pre-install any changes that are required in post install. That will at least keep  pacman happy.
Actually, you can make it simpler: just put "device-tree=/broadcom/bcm2711-rpi-4-b.dtb" in /boot/config.txt, then firmware will take correct dtb for rpi kernel. However, i couldn;t boot board with this dtb, rpi kernel only worked with mainline dtb for me.

Quote from: replabrobin – on
You say you don't have rpi4 usb working; that is similar to the problem I have with alarm; I could see the boot happening, but no mouse or keyboard was usable.
I found that if you boot from usb using rpi eeprom features, usb will work for kernel. But to achieve this you need to boot kernel directly from usb, u-boot is also not used here (at least now)
ARMtix

Re: change in /boot for linux-raspberrypi4-5.10.17-3-aarch64.pkg.tar.xz

Reply #4 –
Quote from: phoenix_king_rus – on
Actually, you can make it simpler: just put "device-tree=/broadcom/bcm2711-rpi-4-b.dtb" in /boot/config.txt, then firmware will take correct dtb for rpi kernel. However, i couldn;t boot board with this dtb, rpi kernel only worked with mainline dtb for me.
I found that if you boot from usb using rpi eeprom features, usb will work for kernel. But to achieve this you need to boot kernel directly from usb, u-boot is also not used here (at least now)

Thanks I will certainly give this a try; I'm using the dtb and kernel files that are in the kernel package, but I am booting using the builtin firmware. This is similar to the way that  manjaro for rpi4 is booting.

So far I have not come across anything disastrous.

Glad to have a working arm system without systemd. So thanks for all efforts.

Re: change in /boot for linux-raspberrypi4-5.10.17-3-aarch64.pkg.tar.xz

Reply #5 –
Quote from: phoenix_king_rus – on
Actually, you can make it simpler: just put "device-tree=/broadcom/bcm2711-rpi-4-b.dtb" in /boot/config.txt, then firmware will take correct dtb for rpi kernel.
I tried the above and find after a few attempts that it doesn't work unless I use
Code: [Select]
device_tree=broadcom/bcm2711-rpi-4-b.dtb
in config.txt. At least that eliminates moving the dtbs during installation.

Re: change in /boot for linux-raspberrypi4-5.10.17-3-aarch64.pkg.tar.xz

Reply #6 –
The instruction i sent use linux-aarch64 package and work for me (i really recommend btrfs for all but /boot on usb drive). As i said, i also tried rpi4 kernel but it only worked with mainline dtb for me
ARMtix