Posts: 1
Joined: Mon Sep 28, 2020 12:44 pm

32-bit Bullseye "converted" to 64-bit!?!

Fri Mar 31, 2023 11:13 am

This week I discovered that what I thought was a 32-bit Bullseye SD card somehow had been "converted" to 64-bit?

I overwrote the SD card with the default Raspberry Pi OS suggested by version 1.7.4 of the Imager application on my Windows PC. I then performed the following steps:
  • 1. Boot with the newly written SD card
    2. Reboot after having adapted the volume to the 64 GB card
    3. Log the sizeness of the Linux disitribution to the architecture_boot.log file
    3. Update and upgrade the packets with the sudo apt update, sudo apt full-upgrade -y and sudo apt auto-remove command
    4. Log the sizeness to the architecture_apt_full-upgrade.log file
    5. Setup the card with the Appearance settings, Printer settings and Screen settings
    6. Log the sizeness to the architecture_appearance+printer+screen_settings.log file
    7. Configured the activity panel settings
    8. Log the sizeness to the architecture_activitypanel_settings.log file
    9. Replace the wpa_supplicant.conf and dhcpcd.conf configuration files
    10. Reboot the Pi
    11. Log the sizeness to the architecture_wpa_supplicant+dhcpcd_settings.log file
I tried to attach these small text log files but this forum only allows picture files? All commands indicated that everything was 32-bit until step 11. The log file from step 11 shows some output as 64-bit and other outputs as 32-bit. My previous attempt to find out what configuration step that transmogrifies my 32-bit Bullseye installation to a pseudo-64-bit installation changed the output from the uname -a command after having ran the Raspberry Pi Configuration and rebooted. Is it the second reboot that changes the Linux system to "64"-bit?

This is annoying since I need a proper 32-bit Bullseye card to test on.

Posts: 220
Joined: Thu Jan 16, 2020 10:52 am

Re: 32-bit Bullseye "converted" to 64-bit!?!

Fri Mar 31, 2023 11:53 am

See this thread from last week: viewtopic.php?t=349291

It's documented that the default kernel has been changed, and shouldn't affect most things. If you absolutely need the kernel to report as 32 bit then put arm_64bit=0 in /boot/config.txt and reboot.

User avatar
Posts: 6092
Joined: Sun Jan 26, 2014 8:36 pm
Location: Near The National Museum of Computing

Re: 32-bit Bullseye "converted" to 64-bit!?!

Fri Mar 31, 2023 11:54 am

For the small text files, use Code tags and copy/paste the text into the post.

Return to “Troubleshooting”