You are not logged in.

#76 2020-11-05 17:23:46

levi
Moderator
From: Yorkshire, UK
Registered: 2018-06-16
Posts: 1,179

Re: [SOLVED - Hurrah!] Upgrading from a truly ancient install

Note I don't have access to any Android phones, so I can't test this out myself.

I agree that being able to create an rootfs would have made this issue simpler to resolve, but you've resolved it now haven't you?


Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.

Offline

#77 2020-11-09 11:00:27

SDRausty
Member
Registered: 2020-09-29
Posts: 56
Website

Re: [SOLVED - Hurrah!] Upgrading from a truly ancient install

levi wrote:

you've resolved it now haven't you?

A while later, upon further retesting, other errors were encountered;   A complete install and update of Arch Linux 32 was NOT reattained.  I had attempted to revise the last steps in the update sequence multiply times, but disappointment continued with every revision that I had tried.

Edit: These are some of the errors:

==> Appending keys from archlinux32.gpg...
error: command failed to execute correctly

This next one is big for the visually impaired user;  Do you know how to tell 'pacman' to --noconfirm the removal so that it can --noconfirm the installation?

==>  Running keys [6/7] i386 (x86) architecture upgrade ; pacman -S ca-certificates...
resolving dependencies...
looking for conflicting packages...

:: ca-certificates and ca-certificates-cacert are in conflict. Remove ca-certificates-cacert? [y/N] y

:: Proceed with installation? [Y/n]
error: GPGME error: Invalid crypto engine

Advice how to resolve these matters is requested.

Last edited by SDRausty (2020-11-10 21:25:31)


Architecture: any, using emulated on Android handheld
Testing repos: true, installing Arch Linux 32 packages

Offline

#78 2020-11-09 16:47:26

levi
Moderator
From: Yorkshire, UK
Registered: 2018-06-16
Posts: 1,179

Re: [SOLVED - Hurrah!] Upgrading from a truly ancient install

You can '# yes|pacman -Syu' if you're really sure you want to accept all of the options, which is not generally advised behaviour, but for your uses might be just the thing.

I did receive a few new keys and disable a whole tranche of presumably older ones when I updated today.  Dunno what's up with that but it doesn't seem malicious, but maybe that's causing you grief?


Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.

Offline

#79 2020-11-10 00:21:59

SDRausty
Member
Registered: 2020-09-29
Posts: 56
Website

Re: [SOLVED - Hurrah!] Upgrading from a truly ancient install

Thank you for your encouragement.  It appears that all of the Arch Linux versions are once more install and configure with one tap on armv7l Android 10 with this commit, including Arch Linux 32.

Last edited by SDRausty (2020-11-10 21:27:26)


Architecture: any, using emulated on Android handheld
Testing repos: true, installing Arch Linux 32 packages

Offline

#80 2020-11-10 09:08:26

levi
Moderator
From: Yorkshire, UK
Registered: 2018-06-16
Posts: 1,179

Re: [SOLVED - Hurrah!] Upgrading from a truly ancient install

Ah, so the --noconfirm option actually is a pacman option.  I must've missed that when I scanned it's man page before.


Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.

Offline

#81 2020-12-21 00:21:04

SDRausty
Member
Registered: 2020-09-29
Posts: 56
Website

Re: [SOLVED - Hurrah!] Upgrading from a truly ancient install

It's broken once more

proot info: vpid 1: terminated with signal 11 #141

https://github.com/termux/proot/issues/141

Can you please share a comment why is might be broken again?

Last edited by SDRausty (2020-12-21 00:21:53)


Architecture: any, using emulated on Android handheld
Testing repos: true, installing Arch Linux 32 packages

Offline

#82 2020-12-21 09:07:58

levi
Moderator
From: Yorkshire, UK
Registered: 2018-06-16
Posts: 1,179

Re: [SOLVED - Hurrah!] Upgrading from a truly ancient install

Are there any more logs available?  That single line log references tools I don't recognise, so I don't really know what it means.


Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.

Offline

#83 2020-12-21 16:00:44

SDRausty
Member
Registered: 2020-09-29
Posts: 56
Website

Re: [SOLVED - Hurrah!] Upgrading from a truly ancient install

levi wrote:

Are there any more logs available?

This is the output with 'proot  --verbose=2':

$ x86/startarch+x86
proot info: binding = /sys
proot info: binding = /data/data/com.termux/files/home/x86/var/binds/fbindprocstat:/proc/stat
proot info: binding = /data/data/com.termux/files/home/x86/tmp:/dev/shm
proot info: binding = /data/data/com.termux/files/home/x86/var/binds/fbindprocuptime:/proc/uptime
proot info: binding = /storage/emulated/0:/sdcard
proot info: binding = /data/data/com.termux/files/home
proot info: binding = /storage
proot info: binding = /data/data/com.termux/files/usr
proot info: binding = /dev/urandom:/dev/random
proot info: binding = /dev/pts/30:/proc/19717/fd/0
proot info: binding = /dev/pts/30:/proc/19717/fd/1
proot info: binding = /dev/pts/30:/proc/19717/fd/2
proot info: binding = /proc/19717/fd
proot info: binding = /system
proot info: binding = /vendor
proot info: binding = /dev/ashmem
proot info: binding = /dev
proot info: binding = /apex
proot info: binding = /dev/null:/etc/ld.so.preload
proot info: binding = /:/host-rootfs
proot info: binding = /data/data/com.termux/files/home/x86/var/binds/fbindprocversion:/proc/version
proot info: binding = /data/data/com.termux/files/home/x86/var/binds/fbindprocshmem:/proc/shmem
proot info: binding = /data/data/com.termux/files/home/x86/var/binds/fbindprocpcidevices:/proc/bus/pci/devices
proot info: binding = /data/data/com.termux/files/usr/tmp/proot-19717-PkqvEe:/proc/bus/pci
proot info: binding = /proc
proot info: binding = /data/data/com.termux/files/home/x86:/
proot info: vpid 1: translate("/" + "/usr/bin/env")
proot info: vpid 1:          -> "/data/data/com.termux/files/home/x86/usr/bin/env"
proot info: vpid 1: translate("/" + "/usr/bin/env")
proot info: vpid 1:          -> "/data/data/com.termux/files/home/x86/usr/bin/env"
proot info: host rootfs = /host-rootfs
proot info: glue rootfs = /data/data/com.termux/files/usr/tmp/proot-19717-PkqvEe
proot info: exe = /usr/bin/env
proot info: argv = /usr/bin/env -i HOME=/root TERM=xterm-256color TMPDIR=/tmp ANDROID_DATA=/data /bin/bash -l
proot info: qemu = /data/data/com.termux/files/usr/bin/qemu-i386
proot info: initial cwd = /root
proot info: verbose level = 2
proot info: pid 19717: access to "/dev/pts/30" (fd 0) won't be translated until closed
proot info: pid 19717: access to "/dev/pts/30" (fd 1) won't be translated until closed
proot info: pid 19717: access to "/dev/pts/30" (fd 2) won't be translated until closed
proot info: pid 19717: access to "/proc/19717/fd" (fd 3) won't be translated until closed
proot info: vpid 1: translate("/" + "/usr/bin/env")
proot info: vpid 1:          -> "/data/data/com.termux/files/home/x86/usr/bin/env"
proot info: vpid 1: translate("/" + "/host-rootfs/system/bin/linker")
proot info: vpid 1:          -> "/apex/com.android.runtime/bin/linker"
proot info: ptrace acceleration (seccomp mode 2, new syscall order) enabled
proot info: vpid 1: translate("/" + "/host-rootfs/data/data/com.termux/files/usr/bin/qemu-i386")
proot info: vpid 1:          -> "/data/data/com.termux/files/usr/bin/qemu-i386"
proot info: vpid 1: translate("/" + "/usr/bin/env")
proot info: vpid 1:          -> "/data/data/com.termux/files/home/x86/usr/bin/env"
proot info: vpid 1: terminated with signal 11
proot info: terminating all tracees on exit
startarch+x86  2.0.993: DONE

EDIT: thank you for asking levi;  topic is also updated at https://github.com/termux/proot/issues/141 and https://github.com/termux/proot/issues/140

Last edited by SDRausty (2020-12-21 16:41:02)


Architecture: any, using emulated on Android handheld
Testing repos: true, installing Arch Linux 32 packages

Offline

#84 2020-12-21 19:59:03

levi
Moderator
From: Yorkshire, UK
Registered: 2018-06-16
Posts: 1,179

Re: [SOLVED - Hurrah!] Upgrading from a truly ancient install

FWIW (I'd forgotten) but signal 11 is a SIGSEGV (a segmentation violation). Apparently those can occur in chroot jails like this if it tries to access a lib that's not in the root, but I'm not sure that's the case here if he ordering of that log is trustworthy, apparently it failed translating /usr/bin/env to /data/daat/com.termux/files/home/x86/usr/bin/env.  Does that path exist?  Although to be fair an error like that would only result in a signal violation in normal use if the error handler was buggily written.


Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.

Offline

#85 2022-01-21 20:05:54

SDRausty
Member
Registered: 2020-09-29
Posts: 56
Website

Re: [SOLVED - Hurrah!] Upgrading from a truly ancient install

proot info: vpid 1: terminated with signal 11

Thank you for keeping arch linux 32 on track:

closed this on Jul 4, 2021

This error is now resolved; Thank you for fixing it!

_Originally posted by @SDRausty in https://github.com/termux/proot/issues/ … 873621775_


Architecture: any, using emulated on Android handheld
Testing repos: true, installing Arch Linux 32 packages

Offline

Board footer

Powered by FluxBB