which architecture am i using? raspberry pi 4 b
January 7, 2024, 03:19
Hello, i'm not understanding which architecture i'm using on my raspberry pi 4 b, 'sudo dpkg --print-architecture' throws 'armhf' but 'arch' throws 'aarch64' and neofetch throws 'OS: Raspbian GNU/Linux 11 (bullseye) aarch64' and in the past i have only been able to install armhf .debian files, so i think its using armhf, if it is using armhf, is it possible to start using aarch64 or both architectures on my current system? like upgrading or something?
'uname -m' also throws 'aarch64'
here is my neofetch output complete:
OS: Raspbian GNU/Linux 11 (bullseye) aarch64
Host: Raspberry Pi 4 Model B Rev 1.4
Kernel: 6.1.42-v8+
Uptime: 21 mins
Packages: 1921 (dpkg)
Shell: bash 5.1.4
Terminal: /dev/pts/0
CPU: BCM2835 (4) @ 2.300GHz
Memory: 426MiB / 7635MiB
I think it's arch 64 then
i tried installing some .aarch64.deb packages and that did not work, only .armhf.deb packages worked
interesting
is this basic raspi 64 bit os?
fully up to date?
don't remember really
i mean, yeah, up to date to debian bullseye standards
which is 11, the last debian is 12
ok run uname -a
Linux raspberrypi 6.1.42-v8+ #1668 SMP PREEMPT Thu Jul 27 15:34:18 BST 2023 aarch64 GNU/Linux
ok interesting
well idk then
definetly weird and confusing
this comes from a docker image not supporting armhf/ armv7 , tried to run the aarch64 one and that did not work
You have to make sure that the packages are made for the "ARM" architecture, also called armv8.
Packages for x86_64 will not work on the Pi as it has an ARM architecture.
thanks for claryfing, yes, i did verify those were for the arm architecture
tried with rustdesk-1.2.3-aarch64.deb package and with lscr.io/linuxserver/duplicati:arm64v8-latest docker image, they do not work
docker automatically chooses the armhf images if i do not specify, if there are not for the current package, it will throw a manifest error
Then the .deb package is for the x86_64 architecture and not for arm.
Do not use aarch64. Use arm, armv8, v8 or "for Raspberry Pi" in the search.
which one should i use there, if the architecture was aarch64?
OK, that's confusing. How did you try to install the .deb?
i recall maybe sudo apt install?
Error message?
ill do it now again to show it, but i will remind you that my system uses armhf so it wont work
console
pi@raspberrypi:~/Downloads $ sudo apt install ./rustdesk-1.2.3-aarch64.deb
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'rustdesk:arm64' instead of './rustdesk-1.2.3-aarch64.deb'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
rustdesk:arm64 : Depends: libgtk-3-0:arm64 but it is not installable
Depends: libxcb-randr0:arm64 but it is not installable
Depends: libxdo3:arm64 but it is not installable
Depends: libxfixes3:arm64 but it is not installable
Depends: libxcb-shape0:arm64 but it is not installable
Depends: libxcb-xfixes0:arm64 but it is not installable
Depends: libasound2:arm64 but it is not installable
Depends: libsystemd0:arm64 but it is not installable
Depends: libva-drm2:arm64 but it is not installable
Depends: libva-x11-2:arm64 but it is not installable
Depends: libvdpau1:arm64 but it is not installable
Depends: libgstreamer-plugins-base1.0-0:arm64 but it is not installable
Depends: libpam0g:arm64 but it is not installable
Depends: libappindicator3-1:arm64 but it is not installable
Depends: gstreamer1.0-pipewire:arm64 but it is not installable
E: Unable to correct problems, you have held broken packages.
rustdesk-1.1.9-raspberry-armhf.deb worked in the past
gonna try the current armv7 one
that worked, rustdesk-1.2.3-armv7-sciter.deb installed
no idea what sciter is but the armv7 deb version worked
usually the docker images have the name you suggest, and armv8+ images do not work, but armv7 images do work
in case of duplicati, there is no armv7 image so i just cant use it currently
Can you post the content of your /boot/config.txt ?
sure
txt # For more options and information see # http://rpf.io/configtxt # Some settings may impact device functionality. See link above for details # uncomment if you get no picture on HDMI for a default "safe" mode #hdmi_safe=1 # uncomment the following to adjust overscan. Use positive numbers if console # goes off screen, and negative if there is too much border #overscan_left=16 #overscan_right=16 #overscan_top=16 #overscan_bottom=16 # uncomment to force a console size. By default it will be display's size minus # overscan. #framebuffer_width=1280 #framebuffer_height=720 # uncomment if hdmi display is not detected and composite is being output #hdmi_force_hotplug=1 # uncomment to force a specific HDMI mode (this will force VGA) #hdmi_group=1 #hdmi_mode=1 # uncomment to force a HDMI mode rather than DVI. This can make audio work in # DMT (computer monitor) modes #hdmi_drive=2 # uncomment to increase signal to HDMI, if you have interference, blanking, or # no display #config_hdmi_boost=4 # uncomment for composite PAL #sdtv_mode=2 #uncomment to overclock the arm. 700 MHz is the default. #arm_freq=800 # Uncomment some or all of these to enable the optional hardware interfaces #dtparam=i2c_arm=on #dtparam=i2s=on #dtparam=spi=on # Uncomment this to enable infrared communication. #dtoverlay=gpio-ir,gpio_pin=17 #dtoverlay=gpio-ir-tx,gpio_pin=18 # Additional overlays and parameters are documented /boot/overlays/README # Enable audio (loads snd_bcm2835) dtparam=audio=on # Automatically load overlays for detected cameras camera_auto_detect=1 # Automatically load overlays for detected DSI displays display_auto_detect=1 # Enable DRM VC4 V3D driver dtoverlay=vc4-kms-v3d max_framebuffers=2 # Disable compensation for displays with overscan disable_overscan=1 #Overclock arm_freq=2300 gpu_freq=500 over_voltage=14 force_turbo=1 [cm4] otg_mode=1 [all] [pi4] # Run as fast as firmware / board allows arm_boost=1 [all] gpu_mem=256 arm_64bit=1
the arm_64bit i just recently added, before last reboot, but it did not change anything actually
everything is the same
also getconf LONG_BIT throws 32
cat /etc/os-release
os-release PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)" NAME="Raspbian GNU/Linux" VERSION_ID="11" VERSION="11 (bullseye)" VERSION_CODENAME=bullseye ID=raspbian ID_LIKE=debian HOME_URL="http://www.raspbian.org/ " SUPPORT_URL="http://www.raspbian.org/RaspbianForums " BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs "
cat /etc/apt/sources.list.d/raspi.list
deb http://archive.raspberrypi.org/debian/ bullseye main # Uncomment line below then 'apt-get update' to enable 'apt-get source' #deb-src http://archive.raspberrypi.org/debian/ bullseye main
getconf LONG_BIT
32
You have probably installed the 32 bit OS.
So if you want to use 64, you have to reinstall the OS.
figured the same, isnt it there like an easy transition? reinstalling would be such a hassle with all the services and configs i already have
Unfortunately, you cannot switch from 32 to 64 without reinstalling.
Did you not document what you did?
wdym?
no i did not, if it was for me i would be using nixos 100%, this raspy is not entirely mine
but how would you document what you did? you got any examples?
you just note down what you did and make backups. otherwise you have to remember etherything for times like these
gonna use ansible next time, i have never did a manual backup
actually that is what i was trynna do with that aarch64 docker image
is there any like system or easy way to do those things?
im really not familiarized with imperative systems
I mean I don't get fancy with it. it's mostly Google docs or something and then just copying the files over to my computer for me
thanks for the help
np
By documentation, I simply mean writing down what you have done.
Example:
Install OS
- Open imager
- Select model = rp4
- Select OS = 64 bit with desktop
Settings
- User = Pi
- Password = Raspberry
- SSID = XYZ
- WLAN password = abcdefg
When you install programs
- Name of the program, possibly link to it
- sudo apt update
- sudo apt upgrade
- sudo apt install something
And then add a note if something does not work. Or if you could fix a bug, how you fixed it.
Then you don't have to keep so much in your head.
nah i did not, that seems like such a hassle
you don't have to do it that well but note down etherything you know you won't remember
would not be that useful since this is not really my system, is a shared system
i would not use raspberry os if it were for me
I mean it's best to do it for debugging
and if you can get the people you share it with to do it too
true, i think there are tools to ease this process
yeah I never got too fancy with it but you can
there are programs that store your "history" as a db, so you got all the commands there in a fancy manner, thats all that comes to mind atm
I mean I use a ssh client which saves the commands I run. that's useful in that sense
also of course software to backup stuff
which one?
I use termiux at the moment, about to switch over to easyssh
But what good are commands alone? The history does not save changes in files such as config.txt. Or changes to passwords etc
good to know, ill find one for terminal
thats why you still got to document. termiux just makes it easier
well, everything is helpful, i was talking about atuin that also keeps context and you can synchronize it between machines
you mean termius?
oh yeah for some reason I always add a x
true, im looking for something that can automatically keep track of that
This happened a lot to me, I simply build from latest source to get everything working.
.