Switching from Pi 3 to Pi 4
Hi list, a quick question: I have TW running on a Pi 3. Now I bought a new Pi 4. Can I just plug the SD card from the Pi3 into the Pi4 and boot up, or is that asking for trouble?
Him
-----Original Message----- From: Peter Suetterlin <pit@astro.su.se> Sent: 16 February 2021 16:16 To: opensuse-arm@opensuse.org Subject: Switching from Pi 3 to Pi 4
Hi list,
a quick question: I have TW running on a Pi 3. Now I bought a new Pi 4. Can I just plug the SD card from the Pi3 into the Pi4 and boot up, or is that asking for trouble?
It should work. But you may want to install raspberrypi-eeprom package to update firmware in eeprom on the Pi 4. Cheers, Guillaume
On 16/02/2021 16:26, 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 :)
Please double check that the u-boot package you have installed is u-boot-arm64 and not u-boot-rpi3. It shouldn't be the rpi3 one, but who knows.
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?
-----Original Message----- From: Peter Suetterlin <pit@astro.su.se> Sent: 24 February 2021 17:00 To: arm@lists.opensuse.org; opensuse-arm@opensuse.org Subject: Re: Switching from Pi 3 to Pi 4
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?
Would you have a serial cable to help to debug this? Guillaume
-----Original Message----- From: Peter Suetterlin <pit@astro.su.se> Sent: 24 February 2021 17:08 To: arm@lists.opensuse.org Subject: Re: Switching from Pi 3 to Pi 4
Guillaume Gardet wrote:
Would you have a serial cable to help to debug this?
Not at home where I am ATM, I'm afraid. I'll try to read up what's needed exactly (I assume some USB-to-serial converter...)
Yes, any USB/UART converter (3V3) will do the job. I suspect an old X11 hack for RPi3 to be the problem. You can also try a remote SSH access, if it is configured and the RPi4 actually boot, but display only is broken. Cheers, Guillaume IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Guillaume Gardet wrote:
I suspect an old X11 hack for RPi3 to be the problem. You can also try a remote SSH access, if it is configured and the RPi4 actually boot, but display only is broken.
It really seems to be 'dead', it doesn't request an IP address, so I can't log in... I'll see what the serial console will tell (once I have it running).
On Mittwoch, 24. Februar 2021 17:07:45 CET Peter Suetterlin wrote:
Guillaume Gardet wrote:
Would you have a serial cable to help to debug this?
Not at home where I am ATM, I'm afraid. I'll try to read up what's needed exactly (I assume some USB-to-serial converter...)
As you probably have a spare Rpi3 now, you can use that as well - just connect Rx->Tx and Tx->Rx (and GND<->GND), and you should be good to go. Though, long term a USB-serial converter probably is the better solution. Almost any should do, I am not aware of any chipset which is not supported by Linux. Choose any $5 USB-serial converter which uses TTL levels, and if it has a jumper for 5V/3V3 selection, choose 3V3. Kind regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019
Stefan Brüns wrote:
On Mittwoch, 24. Februar 2021 17:07:45 CET Peter Suetterlin wrote:
Guillaume Gardet wrote:
Would you have a serial cable to help to debug this?
Not at home where I am ATM, I'm afraid. I'll try to read up what's needed exactly (I assume some USB-to-serial converter...)
As you probably have a spare Rpi3 now, you can use that as well - just connect Rx->Tx and Tx->Rx (and GND<->GND), and you should be good to go.
Ah, smart idea! Stupid thing is I only have that one Micro-SD card :P That's why I didn't want to re-install, to keep the (working) installation. Guess I need to do some shopping....
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.
participants (5)
-
Guillaume Gardet -
Matthias Brugger -
Paul Uiterlinden -
Peter Suetterlin -
Stefan Brüns