On woensdag 24 februari 2021 17:00:27 CET Peter Suetterlin wrote:
Peter Suetterlin wrote:
Guillaume Gardet wrote:
It should work. But you may want to install raspberrypi-eeprom package to update firmware in eeprom on the Pi 4.> Thanks so much! Will try :)
Sorry, this took much longer than I wanted, as I realized I don't have a proper power source (USB-C) for the Pi 4 :(
Now I have one, but I'm unable to boot (refresher: I have an SD-card with a TW installation from a Pi 3B+)
I get the EFI bootup messages, then the grub welcome, and the os select sreen. Then it starts to boot, I see
Booting 'openSUSE Tumbleweed'
Loading Linux 5.10.12-1-default ... Loading initial ramdisk .. -
That is in the black square area in the center.
Then some message appears in the left middle (console message?)
EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable, KASLR will be disabled EFI stub: Using DTB from configuration table EFI stub: Exiting boot services and installing virtual address map...
Then the screen turns black, with only an underscore in the upper left. Nothing more :(
Is that fixable, or should I rather do a full re-install?
I made the transition from Pi 3 to Pi 4 with an existing installation (headless JeOS, so no X11) last year, in May. What I did: 1) Overwrite /boot and /boot/efi with those directories from the latest image 2) Replaced the UUIDs with my own in the following files: /boot/efi/EFI/BOOT/grub.cfg /boot/grub2/grub.cfg I'm not sure if replacing /boot and /boot/efi was really necessary. It worked, until the first update. On boot it would hang after "Reached target Basic System" (seen on serial console). After some digging it turned out that these settings in grub.cfg were the culprit: swiotlb=512 cma=300M These settings could be found in: /boot/grub2/grub.cfg /etc/sysconfig/bootloader /etc/default/grub So I removed them, did a grub2-mkconfig -o /boot/grub2/grub.cfg and all was OK. So for you, the first thing that I would check is to see if these swiotlb=512 and cma=300M settings are present in the grub.cfg file and remove them, if present. -- Paul.