I'm running ArchLinuxArm in a VM on my MacBook M1 (Apple Silicon). I need to run a couple of x86-64 binaries, so I installed **qemu-user** and **qemu-user-binfmt** packages. If I try to run any x86-64 binary, I get the following error: qemu-x86_64: Could not open '/lib64/ld-linux-x86-64.so.2': No such file or directory Is there any way to install the x86-64 required libraries on ArchLinuxArm? Thanks

I'm trying to chroot into a Arch Linux ARM filesystem from x86_64. I've seen that it's possible to do using static qemu by copying the binary into the chroot system: $ cp /usr/bin/qemu-arm archarm-chroot/usr/bin But despite this I always get the following error: chroot: failed to run command ‘/bin/bash’: Exec format error I know this means that the architectures differ. Am I doing something wrong?

I wanted to try Arch and as I have an M1 Mac, I need to use the ARM version of arch or otherwise my Arch is slow as fuk because it's emulated. I'm using UTM as my virtual machine (for those who don't know, UTM is just a nice GUI frontend for managing QEMU machines, so I'm technically running Arch in QEMU). I'm using the pre-configured installation from the UTM gallery: https://mac.getutm.app/gallery/archlinux-arm I wanted to try installing a desktop environment, so I started with installing SDDM (I'm not sure if it already comes with a desktop environment, but I'm happy if I just have a login screen). Basically I just updated Pacman and then installed SDDM. Then I enabled the SDDM service. Then I had to add a display to my VM, because the installation from the UTM gallery does not have a display output by default, but just a serial interface window to interact with Arch. So in the settings of my VM, I added a display and the display card virtio-ramfb was selected by default, so I kept it like this. When I'm now launching my VM, I have one window for the display and one for the serial interface. While you can see the system booting in the serial window, the graphical window just displays 4 Tuxes in a row for some time, and then just has a black screen, while the serial window is just showing a normal terminal login like before. So, I checked systemctl status sddm to see if it's actually running, and the output said that it was active and showed the last logs from this service: Aug 14 19:42:17 alarm sddm: Failed to read display number from pipe Aug 14 19:42:17 alarm sddm: Display server stopping... Aug 14 19:42:17 alarm sddm: Attempt 2 starting the Display server on vt 2 > Aug 14 19:42:19 alarm sddm: Display server starting... Aug 14 19:42:19 alarm sddm: Writing cookie to "/run/sddm/xauth_DguHSX" Aug 14 19:42:19 alarm sddm: Running: /usr/bin/X -nolisten tcp -background > Aug 14 19:42:19 alarm sddm: Failed to read display number from pipe Aug 14 19:42:19 alarm sddm: Display server stopping... Aug 14 19:42:19 alarm sddm: Attempt 3 starting the Display server on vt 2 > Aug 14 19:42:19 alarm sddm: Could not start Display server on vt 2 I don't know where to find the full logs, but I think the important error message shows up here anyway: Failed to read display number from pipe **What I tried to fix this:** I searched for this error, and I found the suggestion to install the drivers required for my display. This would be virtio-gpu for the display card selected in UTM, but pacman doesn't find any packages named virtio-gpu or virtio. I also read a few times that I'd have to re-generate the initramfs or whatever, I'd have to run mkinitcpio -P. But this command always fails with this error message: gzip: stdout: No space left on device bsdtar: Write error bsdtar: Write error ==> ERROR: Initcpio image generation FAILED: 'bsdtar (step 1)' reported an error Somehow gzip complains about not having space left on device, but increasing the size of the RAM as well as the hard drive in the VM settings didn't worked, so I'm not sure if it's really because of having no space left. Restarting the SDDM service manually also didn't work. I tried it with systemctl restart sddm as well as stopping and then starting it, and I also ran systemctl disable sddm and started it manually after rebooting, but still just black screen. But when starting the system with the SDDM service disabled, I found that the display window now shows the usual Arch terminal, so Arch at least somehow detected the display and is able to print something to the screen. So I guess I might need to something for SDDM or so... Do you know where this error comes from? (And do you also know why my initcpio generation fails?) Thank you! :D

I am trying to install Arch Linux ARM on my Nintendo 3DS and I have a

.conf

file that looks like this:

[options]

HoldPkg     = pacman glibc
Architecture = armv6h
#SigLevel    = Required DatabaseOptional
SigLevel	= Never
LocalFileSigLevel = Optional

[core]
Server = http://mirror.archlinuxarm.org/armv7h/core 

[extra]
Server = http://mirror.archlinuxarm.org/armv7h/extra 

[community]
Server = http://mirror.archlinuxarm.org/armv7h/community 

[alarm]
Server = http://mirror.archlinuxarm.org/armv7h/alarm 

[aur]
Server = http://mirror.archlinuxarm.org/armv7h/aur 

ignore the different architectures And it gives me this error:

error: could not open file /mnt/root/var/cache/pacman/pkg/iptables-1:1.8.10-2-armv7h.pkg.tar.xz.part: Invalid argument
error: failed to setup a download payload for iptables-1:1.8.10-2-armv7h.pkg.tar.xz
warning: failed to retrieve some files
error: failed to commit transaction (failed to retrieve some files)
Errors occurred, no packages were upgraded.
==> ERROR: Failed to install packages to new root

I have tried

directly into the mirror for that specific file, and got a file named

-1_1.8.10-2-armv7h.pkg.tar.xz

, which can't be renamed to

-1:1.8.10-2-armv7h.pkg.tar.xz

, as that is an invalid filename. What should I do?

The subject is an arch arm raspberry pi 3 (lxqt) I am prompted every time when I open network manager or want to reboot for a root password. I have the following modifications in my /etc/sudoers: Cmnd_Alias REBOOT = /sbin/halt, /sbin/reboot, /sbin/poweroff, /usr/bin/shutdown -h now Cmnd_Alias NETWORK = /usr/bin/netctl, /usr/bin/nm-applet, /usr/bin/nm-connection-editor, /usr/bin/nm-online, /usr/bin/nmcli, /usr/bin/nmtui, /usr/bin/nmtui-connect, /usr/bin/nmtui-edit, /usr/bin/nmtui-hostname %network ALL=(ROOT) NOPASSWD: NETWORK %power ALL=(ALL) NOPASSWD: POWER tried (ALL) and (ROOT) for both, neither did work. My /usr/share/polkit-1/actions/org.freedesktop.NetworkManager.policy file contains properly: yes yes and added yes Still it did not fix my problem. Weirly enough even if I dont provide the root password the wifi scan for instance will go through and I see the available connections. I read most posts (10 years old or so) but they did not fix my issue.

I do not know if this question is in the right spot... I have been using RaspberryPies for the lasts years and I was wondering questions about **ARM CPUs** in general, so I would like to know more about you guys's ARM's **experiences**... So the questions are: 1. I recently have been seeing some cloud providers use ARM based CPUs in their services (as I did notice aws and oracle are using it) so **is there any comercial CPU to use it in servers** (with ARM architecture, of course) **which I can buy and use it in**, lets say, **an HP Proliant DL380 Gen10 or a DELL server?** I have been seeing AmpereComputing and they sell a very good micro but it's apparently tied to some hardware vendors (Foxxcon, Gigabyte, Supermicro...) 2. **Can ARM CPUs use 64bits instructions?** I'm trying to compare them with actuals 64bits 3. **Could I use KVM in these ARM CPUs for**, obviously, **virtualization?** Could I also use LXD and Docker or Containerd ? 4. Is there an ARM CPU that I could compare with, let's say, an Intel(R) Xeon(R) Silver 4110 CPU?

There are wait_event_interruptible in a driver to wait until message is aviliable.But this function was interrupted by a signal. I find out this in manpage: > The function will return -ERESTARTSYS if it was interrupted by a signal Another community tell me the signal is "nonblocked pending signals". So I want to know what is "nonblocked pending signals"? And how to find out whitch thread produce this signal? Could I produce this signal manuly to interrupt "wait_event_interruptible " ?

I have Installed the generic aarch64 rootfs to an sdcard , and have placed It inside my phone and am trying to chroot into it - via a superuser adb shell , by running busybox chroot /data/local/mnt /bin/bash however - I get chroot: can't execute '/bin/bash': No such file or directory

**I know this question has been asked multiple times before, but I haven't found a solution that works for me yet.** I'm having trouble playing audio over an SSH session. The device in question is a Raspberry Pi 3B+ running Arch Linux ARM and with USB speakers plugged in. I have an HDMI cable and a keyboard hooked up to it now for an easier setup process, but it is going to be used headless when I'm done. When I log in to the local terminal, playing sounds and recording the microphone are no problem. pactl list short sinks lists HDMI out, the 3.5 mm jack and my USB speakers, and with the latter set as the default sink, playing audio with commands like paplay is no problem at all. However, when I access the pi over SSH, pactl list short sinks only shows a dummy audio sink which quietly discards all audio I try to play. If I happen to be logged in locally at the same time, I see all my sinks and can even play audio! But as soon as I log off locally, audio from the SSH session stops working again. This is very inconvenient because as mentioned earlier, the pi will be used headless later. Some people on the internet have suggested that this is one of the few cases where pulseaudio's highly discouraged system mode makes sense. Following the advice online I did the following steps: 1. sudo systemctl --global mask pulseaudio.socket to stop the userspace server from being started on login. 2. Create user pulse without a home dir. 3. Add myself to the pulse-access group. 4. Reboot. 5. After local login, pactl list short sinks reports Connection failure: Connection refused, verifying that the userspace server has indeed not been spawned. 6. Start pulseaudio in system mode with sudo pulseaudio --system -D. But this actually made things worse. Now, pactl list short sinks only lists the dummy sink both in SSH and local sessions, leaving me unable to play audio even from a local terminal even as root. What can I do? Are there any log files that might contain useful information? Thanks!

After update with pacman -Syuq: # pacman -Sc pacman: error while loading shared libraries: libicuuc.so.59: cannot open shared object file: No such file or directory # find / -name libicuuc.so.* 2>/dev/null /usr/lib/libicuuc.so.60.1 /usr/lib/libicuuc.so.60 Arch Linux in a Pi version 1: # uname -an 4.9.62-1-ARCH #1 SMP Fri Nov 17 13:42:55 UTC 2017 armv6l GNU/Linux

In Arch Linux Arm and Manjaro Arm, Octave and R [fail to launch](https://archlinuxarm.org/forum/viewtopic.php?f=15&t=15054) with OpenBLAS 0.3.13-2. When run, it shows the error

error while loading shared libraries: libblas.so.3: cannot open shared object file

How to fix it?

On an amd64 machine running Manjaro Linux, I'd like to be able to resolve names inside an arm chroot, which is Arch Linux ARM. Unfortunately, it's not working. I suspect it might have something to do with different glibc versions or so, but have no idea how to overcome the problem. The problem exists with both the pre-compiled qemu-static-arm and the self-compiled qemu-user-static packages from AUR. Here's what I've done to get inside the guest system as well as what's been done thus far once inside, including the error message:

[t440s ~]# ping -c 1 unix.stackexchange.com
PING unix.stackexchange.com (151.101.65.69) 56(84) bytes of data.
64 bytes from 151.101.65.69 (151.101.65.69): icmp_seq=1 ttl=60 time=22.5 ms

--- unix.stackexchange.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 22.549/22.549/22.549/0.000 ms
[t440s ~]# mount /dev/mmcblk0p1 root/
[t440s ~]# mount --bind /dev/ root/dev/
[t440s ~]# mount --bind /proc/ root/proc/
[t440s ~]# mount --bind /dev/pts/ root/dev/pts/
[t440s ~]# mount --bind /run/ root/run/
[t440s ~]# cp /usr/bin/qemu-arm-static root/usr/bin/
[t440s ~]# chroot root/ qemu-arm-static /bin/bash
[root@t440s /]# cat etc/resolv.conf 
nameserver 141.1.1.1
[root@t440s /]# ping unix.stackexchange.com
/usr/bin/ping: unix.stackexchange.com: Temporary failure in name resolution
[root@t440s /]# ls -ltr /etc/resolv.conf 
lrwxrwxrwx 1 root root 32 Aug  9 03:54 /etc/resolv.conf -> /run/systemd/resolve/resolv.conf
[root@t440s /]# ls -ltr /run/systemd/resolve/resolv.conf
-rw-r--r-- 1 root root 21 Jan 17 18:42 /run/systemd/resolve/resolv.conf
[root@t440s /]# rm /etc/resolv.conf 
[root@t440s /]# cp /run/systemd/resolve/resolv.conf /etc/
[root@t440s /]# ping unix.stackexchange.com
/usr/bin/ping: unix.stackexchange.com: Temporary failure in name resolution

How can one make name resolution work with this technique?

I'd like to install a bootable Linux system on a micro SD card, **AND** be able to use it as external storage for other devices, such as my Android phone. The plan: Linux ARM on a Raspberry Pi 4. If I insert an SD card (with Arch Linux ARM installed) into my phone, Android only detects the first partition of the SD card (the boot partition). The desired outcome is to mount my home partition with my music, and not the boot partition. I have thought of 2 possible solutions: 1. Find an Android file manager app that can access the 3rd partition (home) 2. Make the first partition my home partition, and then the boot partition as the second, root as 3rd. No luck with the first solution, and I really don't know how to approach the 2nd solution with a successful boot, and I can't install the system via USB, as Raspberry Pi doesn't support it. ## Working solution, adding to Philip Couling's insight ## I could not get Android to read a 2nd partition, no matter the filesystem (at least unrooted), so I deduced that the only choice I had based on my tests were to expand my boot partition, my first partition. Android was able to read vFAT, but was not able to boot Linux (Raspberry Pi 4), but your mileage may vary. It was able to boot from FAT32. I think the best possible file system available to be both read by Android, and to be bootable with a Raspberry Pi 4 is FAT32. Unfortunate, but it will get the job done. My OSes of choice were either Manjaro or Arch, but their default installations make the boot partition FAT16. I was able to change it to FAT32 with the help of GParted, and remained bootable. It was crucial to make sure making sure the labels were identical for Manjaro to be able to boot (BOOT_MNJRO and ROOT_MNJRO) as it was instructed in "/boot/cmdline.txt" **The MicroSD card can now be used as a bootable system, AND used for extra storage for my Android phone. The goal was to use a 2nd MicroSD card as a backup drive, and still be able to use it as portable storage on my phone!** Appreciate Philip Couling's great insight, and using syslinks has made my home directory feel natural.

I'm trying to run busybox on my waveshare stm32 development board but my SOC has "armv7-m" architecture not "armv7-a". so I've put the march flag in the menuconfig of busybox

(-march=armv7-m) Additional CFLAGS

. But when I'm trying to compile it, it throws me thousands of instants of this

architecture profiles M/A

error for each file while linking. So, I decided to put this flag

(-march=armv7-m) Additional LDFLAGS

for linker too, but it didn't help. my platform:

Host:
   | OS: Ubuntu 20 LTS
   | Kernel: Microsoft WSL2 Linux Kernel
   | Cross compile Toolchain: Linaro latest stable version
   |__

Target:
   | Board: Waveshare CoreH7XXI
   | SOC: stm32h743 (Single Core Cortex M7 @400MHz)
   | Architecture: ARMV7-M
   | Onboard DRAM: 8MB - 400KB(reserved by u-boot) = 7.6MB
   | Linux Kernel: 5.8.10 (stable 2020-09-17)
   | Busybox: latest stable version
   |__

makefile log (it was too long, so I've deleted the middle part of it):

LINK    busybox_unstripped
Your linker does not support --sort-section,alignment
Your linker does not support --sort-common
Static linking against glibc, can't use --gc-sections
Trying libraries: m resolv rt
Failed: -Wl,--start-group  -lm -lresolv -lrt  -Wl,--end-group
Output of:
arm-linux-gnueabihf-gcc -Wall -Wshadow -Wwrite-strings -Wundef -Wstrict-prototypes -Wunused -Wunused-parameter -Wunused-function -Wunused-value -Wmissing-prototypes -Wmissing-declarations -Wno-format-security -Wdeclaration-after-statement -Wold-style-definition -finline-limit=0 -fno-builtin-strlen -fomit-frame-pointer -ffunction-sections -fdata-sections -fno-guess-branch-probability -funsigned-char -static-libgcc -falign-functions=1 -falign-jumps=1 -falign-labels=1 -falign-loops=1 -fno-unwind-tables -fno-asynchronous-unwind-tables -fno-builtin-printf -Os -march=armv7-m -static -march=armv7-m -o busybox_unstripped -Wl,--start-group applets/built-in.o archival/lib.a archival/libarchive/lib.a console-tools/lib.a coreutils/lib.a coreutils/libcoreutils/lib.a debianutils/lib.a klibc-utils/lib.a e2fsprogs/lib.a editors/lib.a findutils/lib.a init/lib.a libbb/lib.a libpwdgrp/lib.a loginutils/lib.a mailutils/lib.a miscutils/lib.a modutils/lib.a networking/lib.a networking/libiproute/lib.a networking/udhcp/lib.a printutils/lib.a procps/lib.a runit/lib.a selinux/lib.a shell/lib.a sysklogd/lib.a util-linux/lib.a util-linux/volume_id/lib.a archival/built-in.o archival/libarchive/built-in.o console-tools/built-in.o coreutils/built-in.o coreutils/libcoreutils/built-in.o debianutils/built-in.o klibc-utils/built-in.o e2fsprogs/built-in.o editors/built-in.o findutils/built-in.o init/built-in.o libbb/built-in.o libpwdgrp/built-in.o loginutils/built-in.o mailutils/built-in.o miscutils/built-in.o modutils/built-in.o networking/built-in.o networking/libiproute/built-in.o networking/udhcp/built-in.o printutils/built-in.o procps/built-in.o runit/built-in.o selinux/built-in.o shell/built-in.o sysklogd/built-in.o util-linux/built-in.o util-linux/volume_id/built-in.o -Wl,--end-group -Wl,--start-group -lm -lresolv -lrt -Wl,--end-group
==========
libbb/lib.a(inet_common.o): In function `INET6_resolve':
inet_common.c:(.text.INET6_resolve+0x22): warning: Using 'getaddrinfo' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
coreutils/lib.a(mktemp.o): In function `mktemp_main':
mktemp.c:(.text.mktemp_main+0x4e): warning: the use of mktemp' is dangerous, better use mkstemp'
networking/lib.a(ipcalc.o): In function `ipcalc_main':
ipcalc.c:(.text.ipcalc_main+0x148): warning: Using 'gethostbyaddr' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
libbb/lib.a(inet_common.o): In function `INET_resolve':
inet_common.c:(.text.INET_resolve+0x2c): warning: Using 'gethostbyname' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
networking/lib.a(inetd.o): In function `reread_config_file':
inetd.c:(.text.reread_config_file+0x152): warning: Using 'getservbyname' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
networking/lib.a(netstat.o): In function `ip_port_str':
netstat.c:(.text.ip_port_str+0x2c): warning: Using 'getservbyport' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: error: applets/built-in.o: Conflicting architecture profiles M/A
/opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: failed to merge target specific data of file applets/built-in.o
/opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: error: libbb/lib.a(appletlib.o): Conflicting architecture profiles M/A
/opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: failed to merge target specific data of file libbb/lib.a(appletlib.o)
/opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: error: libbb/lib.a(compare_string_array.o): Conflicting architecture profiles M/A
/opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: failed to merge target specific data of file libbb/lib.a(compare_string_array.o)
/opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: error: libbb/lib.a(concat_path_file.o): Conflicting architecture profiles M/A
/opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: failed to merge target specific data of file libbb/lib.a(concat_path_file.o)
/opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: error: libbb/lib.a(default_error_retval.o): Conflicting architecture profiles M/A
/opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: failed to merge target specific data of file libbb/lib.a(default_error_retval.o)
/opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: error: libbb/lib.a(get_last_path_component.o): Conflicting architecture profiles M/A
/opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: failed to merge target specific data of file libbb/lib.a(get_last_path_component.o)
/opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: error: libbb/lib.a(last_char_is.o): Conflicting architecture profiles M/A
/opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: failed to merge target specific data of file libbb/lib.a(last_char_is.o)
.
.
.
.
.
/opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: failed to merge target specific data of file libbb/lib.a(xgethostbyname.o)
/opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: error: libbb/lib.a(xrealloc_vector.o): Conflicting architecture profiles M/A
/opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: failed to merge target specific data of file libbb/lib.a(xrealloc_vector.o)
/opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: error: libbb/lib.a(xregcomp.o): Conflicting architecture profiles M/A
/opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: failed to merge target specific data of file libbb/lib.a(xregcomp.o)
/opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: error: libbb/lib.a(perror_nomsg.o): Conflicting architecture profiles M/A
/opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: failed to merge target specific data of file libbb/lib.a(perror_nomsg.o)
collect2: error: ld returned 1 exit status
Note: if build needs additional libraries, put them in CONFIG_EXTRA_LDLIBS.
Example: CONFIG_EXTRA_LDLIBS="pthread dl tirpc audit pam"
make: *** [Makefile:718: busybox_unstripped] Error 1

without adding

-v7-m

flag, it compiles it for cortex A:

$ readelf -A busybox
Attribute Section: aeabi
File Attributes
  Tag_CPU_name: "7-A"
  Tag_CPU_arch: v7
  Tag_CPU_arch_profile: Application
  Tag_ARM_ISA_use: Yes
  Tag_THUMB_ISA_use: Thumb-2
  Tag_FP_arch: VFPv3
  Tag_Advanced_SIMD_arch: NEONv1
  Tag_ABI_PCS_wchar_t: 4
  Tag_ABI_FP_rounding: Needed
  Tag_ABI_FP_denormal: Needed
  Tag_ABI_FP_exceptions: Needed
  Tag_ABI_FP_number_model: IEEE 754
  Tag_ABI_align_needed: 8-byte
  Tag_ABI_align_preserved: 8-byte, except leaf SP
  Tag_ABI_enum_size: int
  Tag_ABI_VFP_args: VFP registers
  Tag_CPU_unaligned_access: v6

I'm getting the following after I try to start mysql: $ sudo systemctl start mysqld Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xe" for details. [pi@raspi ~]$ systemctl status mysqld * mariadb.service - MariaDB 10.5.5 database server Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Sun 2020-08-23 08:34:44 PDT; 9s ago Docs: man:mariadbd(8) https://mariadb.com/kb/en/library/systemd/ Process: 466 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS) Process: 467 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=cd /usr/bin/..; /usr/bin/galera_recovery; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/S> Process: 479 ExecStart=/usr/bin/mariadbd $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE) Main PID: 479 (code=exited, status=1/FAILURE) Status: "MariaDB server is down" Aug 23 08:34:44 raspi mariadbd: 2020-08-23 8:34:44 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.4.14. Aug 23 08:34:44 raspi mariadbd: 2020-08-23 8:34:44 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error Aug 23 08:34:44 raspi mariadbd: 2020-08-23 8:34:44 0 [Note] InnoDB: Starting shutdown... Aug 23 08:34:44 raspi mariadbd: 2020-08-23 8:34:44 0 [ERROR] Plugin 'InnoDB' init function returned error. Aug 23 08:34:44 raspi mariadbd: 2020-08-23 8:34:44 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. Aug 23 08:34:44 raspi mariadbd: 2020-08-23 8:34:44 0 [ERROR] Unknown/unsupported storage engine: InnoDB Aug 23 08:34:44 raspi mariadbd: 2020-08-23 8:34:44 0 [ERROR] Aborting Aug 23 08:34:44 raspi systemd: mariadb.service: Main process exited, code=exited, status=1/FAILURE Aug 23 08:34:44 raspi systemd: mariadb.service: Failed with result 'exit-code'. Aug 23 08:34:44 raspi systemd: Failed to start MariaDB 10.5.5 database server. lines 1-21/21 (END) I don't see any information from syslog-ng in /var/log/messages.log either.... I'm not sure what's going on, can anybody help me out with this? :o As @tetech suggested, I should downgrade to a previous version of my mariadb package. So I tried: [pi@raspi pkg]$ sudo pacman -U /var/cache/pacman/pkg/mariadb-10.4.14-1-aarch64.pkg.tar.xz [sudo] password for pi: loading packages... warning: downgrading package mariadb (10.5.5-1 => 10.4.14-1) resolving dependencies... warning: cannot resolve "mariadb-clients=10.4.14", a dependency of "mariadb" :: The following package cannot be upgraded due to unresolvable dependencies: mariadb :: Do you want to skip the above package for this upgrade? [y/N] n error: failed to prepare transaction (could not satisfy dependencies) :: unable to satisfy dependency 'mariadb-clients=10.4.14' required by mariadb [pi@raspi pkg]$ sudo pacman -U /var/cache/pacman/pkg/mariadb-clients-10.4.14-1-aarch64.pkg.tar.xz loading packages... warning: downgrading package mariadb-clients (10.5.5-1 => 10.4.14-1) resolving dependencies... warning: cannot resolve "mariadb-libs=10.4.14", a dependency of "mariadb-clients" :: The following package cannot be upgraded due to unresolvable dependencies: mariadb-clients :: Do you want to skip the above package for this upgrade? [y/N] error: failed to prepare transaction (could not satisfy dependencies) :: unable to satisfy dependency 'mariadb-libs=10.4.14' required by mariadb-clients [pi@raspi pkg]$ sudo pacman -U /var/cache/pacman/pkg/mariadb-libs-10.4.14-1-aarch64.pkg.tar.xz loading packages... warning: downgrading package mariadb-libs (10.5.5-1 => 10.4.14-1) resolving dependencies... looking for conflicting packages... error: failed to prepare transaction (could not satisfy dependencies) :: installing mariadb-libs (10.4.14-1) breaks dependency 'mariadb-libs=10.5.5' required by mariadb-clients [pi@raspi pkg]$ sudo pacman -U /var/cache/pacman/pkg/mariadb-clients-10.4.14-1-aarch64.pkg.tar.xz loading packages... warning: downgrading package mariadb-clients (10.5.5-1 => 10.4.14-1) resolving dependencies... warning: cannot resolve "mariadb-libs=10.4.14", a dependency of "mariadb-clients" :: The following package cannot be upgraded due to unresolvable dependencies: mariadb-clients :: Do you want to skip the above package for this upgrade? [y/N] error: failed to prepare transaction (could not satisfy dependencies) :: unable to satisfy dependency 'mariadb-libs=10.4.14' required by mariadb-clients But it seems like mariadb-libs is complaining about mariadb-clients and vice-versa. How do I get thenm downgraded? I'm now thinking it might just be easier to re-init my db instead....

It seems to have become a bit complex, so first some background: I need to compile self-contained programs that run on arm systems with glibc versions typically between 2.13 and 2.17. When trying to run these programs, I often get an error like this:

dlopen: /lib/libc.so.6: version `GLIBC_2.26' not found (required by /tmp/_MEImvaIVL/libpython3.8.so.1.0)

(In this case I'm using a program with embedded python interpreter, packaged with PyInstaller) I have a working workflow to build the python used in that case from source, and use that python to build the final package, so I figured if I just build it under the right glibc version I'm good to go. I'm using build containers (first docker, now buildah (since it gives me much more flexibility to interact with my build containers)), based on debian:stretch-arm32v7. After significant *trial & horror*, glibc seems to compile quite well initially, but now I'm stuck at:

gcc -no-pie -shared -static-libgcc -Wl,-O1  -Wl,-z,defs -Wl,-dynamic-linker=/opt/glibc-2.17/lib/ld-linux-armhf.so.3  -B/buildroot/build/csu/  -Wl,--version-script=/buildroot/build/libnss_db.map -Wl,-soname=libnss_db.so.2 -Wl,-z,combreloc -Wl,-z,relro -Wl,--hash-style=both  -L/buildroot/build -L/buildroot/build/math -L/buildroot/build/elf -L/buildroot/build/dlfcn -L/buildroot/build/nss -L/buildroot/build/nis -L/buildroot/build/rt -L/buildroot/build/resolv -L/buildroot/build/crypt -L/buildroot/build/nptl -Wl,-rpath-link=/buildroot/build:/buildroot/build/math:/buildroot/build/elf:/buildroot/build/dlfcn:/buildroot/build/nss:/buildroot/build/nis:/buildroot/build/rt:/buildroot/build/resolv:/buildroot/build/crypt:/buildroot/build/nptl -o /buildroot/build/nss/libnss_db.so -T /buildroot/build/shlib.lds /buildroot/build/csu/abi-note.o -Wl,--whole-archive /buildroot/build/nss/libnss_db_pic.a -Wl,--no-whole-archive /buildroot/build/elf/interp.os /buildroot/build/linkobj/libc.so /buildroot/build/libc_nonshared.a /buildroot/build/nss/libnss_files.so
/buildroot/build/nss/libnss_db_pic.a(db-proto.os): In function `_nss_db_getprotoent_r':
db-proto.c:(.text+0x15c): undefined reference to `_nss_files_parse_protoent'
/buildroot/build/nss/libnss_db_pic.a(db-proto.os): In function `_nss_db_getprotobyname_r':
db-proto.c:(.text+0x268): undefined reference to `_nss_files_parse_protoent'

... (more failing functions) ...

collect2: error: ld returned 1 exit status
../Makerules:446: recipe for target '/buildroot/build/nss/libnss_db.so' failed
make: *** [/buildroot/build/nss/libnss_db.so] Error 1

If I enter the container and copy&paste above gcc command, I can immediately reproduce this error. Now if I add the flags -L/usr/lib/arm-linux-gnueabihf (which contains the host's libnss_files.so and the functions the linker can't find, and execute the command again, I get the same error, but if I also add -lnss_files (unsurprisingly?) it works. But this will be the case for many more files, so there must be a deeper lying problem? What surprises me is the flag -Wl,-dynamic-linker=/opt/glibc-2.17/lib/ld-linux-armhf.so.3 in above command. While that indeed is the final target (--prefix=/opt/glibc-2.17), it is still empty since glibc is still being built. Is somehow glibc not bootstrapping correctly? Any ideas? TIA!

I Really think about booting a linux image (WITHOUT GUI Just terminal) in an android device so there are a lot of linux arm images starting by debian , arch , raspberry pi , etc ... Is that possible on an old device That comes with keyboard like this one i see a lot of video that they do a virtualization to the linux image (i Don't Want that ) i realy want to install it on the device storage not on SD-CARD Here is the specification of the phone Chipset : BCM21654 Storage : 4GB RAM : 512 MB Type of processor core : ARM Cortex-A9 ARMv7 the phone is too old i had found the compatible kernel with that model on github it will be really god if i can insert the kernel in the image then run it

I am using Arch Linux on a Chromebook C201 (ARM). Since I recently upgraded the system, the desktop environment seems to be crashing shortly after I login (before the upgrade it was working fine). I have both LXDE and MATE installed and I am seeing similar crashes on both. The two DEs are using different Window Managers (Openbox and marco), so I suspect there may be an issue with X server. When the system crashes, the screen freezes and the desktop completely locks up. There is no response to mouse or keyboard input and I am unable to use CTL-ALT-F2 etc. to switch to a console tty. After a few minutes it dumps me back in the lightdm login screen. I have found the following errors (which seem to be relevant) in ~/.cache/lxsession/LXDE/run.log: ** (lxpanel:524): WARNING **: 21:18:33.907: The directory '~/Templates' doesn't exist, ignoring it ** (pcmanfm:525): WARNING **: 21:18:33.907: The directory '~/Templates' doesn't exist, ignoring it Openbox-Message: Unable to find a valid menu file "/usr/share/lxde/openbox/menu.xml" (lxpanel:524): GLib-GObject-CRITICAL **: 21:18:34.467: g_object_unref: assertion 'G_IS_OBJECT (object)' failed (lxpanel:524): GLib-GObject-CRITICAL **: 21:18:34.467: g_object_unref: assertion 'G_IS_OBJECT (object)' failed (lxpanel:524): GLib-GObject-CRITICAL **: 21:18:34.476: g_object_unref: assertion 'G_IS_OBJECT (object)' failed ** (lxpanel:524): WARNING **: 21:18:34.544: Battery entry BAT0 not found, using sbs-20-000b (lxpanel:524): GLib-GObject-CRITICAL **: 21:18:34.547: g_object_unref: assertion 'G_IS_OBJECT (object)' failed (lxpanel:524): GLib-GObject-CRITICAL **: 21:18:34.547: g_object_unref: assertion 'G_IS_OBJECT (object)' failed ** (lxpanel:524): WARNING **: 21:18:34.736: launchbar: desktop entry does not exist (nm-applet:541): libnotify-WARNING **: 21:18:38.692: Failed to connect to proxy (nm-applet:541): nm-applet-WARNING **: 21:18:38.698: Failed to show notification: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files lxterminal (lxpanel:524): Wnck-WARNING **: 21:18:40.000: Unhandled action type _OB_WM_ACTION_UNDECORATE (lxpanel:524): Wnck-WARNING **: 21:19:12.727: Unhandled action type _OB_WM_ACTION_UNDECORATE (lxpanel:524): Wnck-WARNING **: 21:19:12.861: Unhandled action type _OB_WM_ACTION_UNDECORATE /usr/lib/firefox/firefox (lxpanel:524): Wnck-WARNING **: 21:19:36.058: Unhandled action type _OB_WM_ACTION_UNDECORATE (END) The equivalent errors for MATE (from ~/.xsession-errors) are: mate-session: WARNING: Unable to find provider '' of required component 'dock' Window manager warning: Log level 128: unsetenv() is not thread-safe and should not be used after threads are created (caja:1299): Gtk-WARNING **: 21:22:12.818: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client (mate-power-manager:1337): Gdk-CRITICAL **: 21:22:14.720: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed Gdk-Message: 21:25:19.408: mate-power-manager: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Gdk-Message: 21:25:19.408: evolution-alarm-notify: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Gdk-Message: 21:25:19.409: mate-session: Fatal IO error 104 (Connection reset by peer) on X server :0. Gdk-Message: 21:25:19.409: marco: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Gdk-Message: 21:25:19.415: caja: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Gdk-Message: 21:25:19.413: polkit-mate-authentication-agent-1: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Gdk-Message: 21:25:19.409: mate-maximus: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Gdk-Message: 21:25:19.408: mate-volume-control-status-icon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Gdk-Message: 21:25:19.408: nm-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Gdk-Message: 21:25:19.409: mate-screensaver: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Gdk-Message: 21:25:19.415: mate-settings-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Gdk-Message: 21:25:19.423: mate-panel: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Contents of Xorg.0.log: [ 10.124] X.Org X Server 1.20.7 X Protocol Version 11, Revision 0 [ 10.124] Build Operating System: Linux Arch Linux [ 10.124] Current Operating System: Linux leeLibrebook 5.5.6-1-ARCH #1 SMP PREEMPT Wed Feb 26 00:56:53 UTC 2020 armv7l [ 10.124] Kernel command line: cros_secure console=tty0 init=/sbin/init root=PARTUUID=1b19e700-f9cb-f247-bc7f-207dece4cdb7/PARTNROFF=1 rootwait rw noinitrd [ 10.124] Build Date: 16 January 2020 05:49:11PM [ 10.124] [ 10.124] Current version of pixman: 0.38.4 [ 10.124] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 10.124] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 10.124] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Mar 17 21:57:41 2020 [ 10.125] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 10.125] (==) No Layout section. Using the first Screen section. [ 10.125] (==) No screen section available. Using defaults. [ 10.125] (**) |-->Screen "Default Screen Section" (0) [ 10.125] (**) | |-->Monitor "" [ 10.125] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 10.125] (==) Automatically adding devices [ 10.125] (==) Automatically enabling devices [ 10.125] (==) Automatically adding GPU devices [ 10.125] (==) Automatically binding GPU devices [ 10.125] (==) Max clients allowed: 256, resource mask: 0x1fffff [ 10.126] (WW) The directory "/usr/share/fonts/misc" does not exist. [ 10.126] Entry deleted from font path. [ 10.126] (WW) The directory "/usr/share/fonts/OTF" does not exist. [ 10.126] Entry deleted from font path. [ 10.126] (WW) The directory "/usr/share/fonts/Type1" does not exist. [ 10.126] Entry deleted from font path. [ 10.126] (WW) The directory "/usr/share/fonts/100dpi" does not exist. [ 10.126] Entry deleted from font path. [ 10.126] (WW) The directory "/usr/share/fonts/75dpi" does not exist. [ 10.126] Entry deleted from font path. [ 10.126] (==) FontPath set to: /usr/share/fonts/TTF [ 10.126] (==) ModulePath set to "/usr/lib/xorg/modules" [ 10.126] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 10.126] (II) Module ABI versions: [ 10.126] X.Org ANSI C Emulation: 0.4 [ 10.126] X.Org Video Driver: 24.1 [ 10.126] X.Org XInput driver : 24.1 [ 10.126] X.Org Server Extension : 10.0 [ 10.127] (++) using VT number 7 [ 10.127] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [ 10.129] (II) xfree86: Adding drm device (/dev/dri/card0) [ 10.143] (II) xfree86: Adding drm device (/dev/dri/card1) [ 10.144] (II) no primary bus or device found [ 10.144] falling back to /sys/devices/platform/display-subsystem/drm/card0 [ 10.144] (II) LoadModule: "glx" [ 10.144] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 10.148] (II) Module glx: vendor="X.Org Foundation" [ 10.148] compiled for 1.20.7, module version = 1.0.0 [ 10.148] ABI class: X.Org Server Extension, version 10.0 [ 10.148] (==) Matched modesetting as autoconfigured driver 0 [ 10.148] (==) Matched fbdev as autoconfigured driver 1 [ 10.148] (==) Assigned the driver to the xf86ConfigLayout [ 10.148] (II) LoadModule: "modesetting" [ 10.148] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so [ 10.149] (II) Module modesetting: vendor="X.Org Foundation" [ 10.149] compiled for 1.20.7, module version = 1.20.7 [ 10.149] Module class: X.Org Video Driver [ 10.149] ABI class: X.Org Video Driver, version 24.1 [ 10.149] (II) LoadModule: "fbdev" [ 10.150] (WW) Warning, couldn't open module fbdev [ 10.150] (EE) Failed to load module "fbdev" (module does not exist, 0) [ 10.150] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [ 10.160] (II) modeset(0): using drv /dev/dri/card0 [ 10.160] (II) modeset(0): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 24/32 [ 10.160] (==) modeset(0): Depth 24, (==) framebuffer bpp 32 [ 10.160] (==) modeset(0): RGB weight 888 [ 10.160] (==) modeset(0): Default visual is TrueColor [ 10.160] (II) Loading sub module "glamoregl" [ 10.160] (II) LoadModule: "glamoregl" [ 10.161] (II) Loading /usr/lib/xorg/modules/libglamoregl.so [ 10.173] (II) Module glamoregl: vendor="X.Org Foundation" [ 10.173] compiled for 1.20.7, module version = 1.0.1 [ 10.173] ABI class: X.Org ANSI C Emulation, version 0.4 [ 10.193] (EE) [ 10.193] (EE) Backtrace: [ 10.193] (EE) [ 10.193] (EE) Segmentation fault at address 0xdda8 [ 10.193] (EE) Fatal server error: [ 10.193] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 10.193] (EE) [ 10.193] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 10.193] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 10.193] (EE) [ 10.200] (EE) Server terminated with error (1). Closing log file. Does anyone have any idea what might be causing this? I have run memtester (as suggested in the comments) and it didn't identify any issues with the RAM. The system seems perfectly stable in a console terminal. It's possible the issue is just a bad package from Arch ARM, which has broken the system during the last update. Does anyone have any thoughts on what package is likely to be broken? (if so, I'll try rolling back)

### What I did Install qemu, qemu-arch-extra, qemu-user-static (AUR) in ArchLinux X86_64. systemd takes care of the binfmt, verified from /proc/sys/fs/binfmt_misc/. Download ArchLinux ARM tarball from its website. The direct link is this http://os.archlinuxarm.org/os/ArchLinuxARM-aarch64-latest.tar.gz . Extract it in a folder with sudo bsdtar -xpf command. Copy the /usr/bin/qemu-aarch64-static file into that folder. Chroot with arch-chroot. In commandline: sudo pacman -S qemu qemu-arch-extra sudo yay -S qemu-user-static sudo bsdtar -xpf ArchLinuxARM-aarch64-latest.tar.gz -C folder ls /proc/sys/fs/binfmt_misc/ sudo cp /usr/bin/qemu-aarch64-static folder/usr/bin sudo arch-chroot folder ### Result In the chrooted environment, I can ping any IP address but can not ping any remote host (e.g. example.com) i.e. name resolution does not work. /etc/resolv.conf file is populated. ip shows correct configs of NICs. So, how can I enable name resolution in chrooted ArchLinux ARM? I have tried the same procedure in Ubuntu X86_64 with chrooted into Ubuntu AARCH64. It works.

I have the following set-up: - hw: RPi 3 Model B - os: 4.4.37-1-ARCH #1 SMP armv7l GNU/Linux - file system: /boot(vfat), /(ext4), /var(ext4) - partitions: three; mounted: /boot, /, /var - storage: mlc nand flash micro sd Recently I am getting kernel panic errors at boot time referring to a file in lib which turns out to be some how corrupted.

panic "/sbin/init" error while loading shared libraries  /usr/lib/libseccomp.so.2 invalid elf header

So my theory is that since my root file system is NOT readonly and I am using nand flash and there are unexpected shutdowns, some files are getting corrupted. The goal is to make the root file system readonly so that it may solve the problem. Unfortunately I could not find any good solid source on how making a readonly root file system should be done on Arch Linux. Also posted on Arch Linux Forum: https://archlinuxarm.org/forum/viewtopic.php?f=9&t=11621