You are not logged in.
Pages: 1
fdisk -l
/dev/sda1 4G Linux Swap
/dev/sda2 294.1G Linux Filesystem (ext4)
mount /dev/sda2 /mnt
arch-chroot /mnt
chroot: failed to run command ?/bin/bash?: No such file or directory
I am doing an BIOS setup not an UEFI. Why i cant run arch-chroot?
Last edited by LiberalPerson (2025-11-16 03:59:04)
Offline
Did you check there is a `/mnt/bin/bash` and what is `ldd /mnt/bin/bash` telling you? It could be, that it is missing some shared libraries..
ls /mnt/bin/bash
ls: cannot access '/mnt/bin/bash': No such file or directory
ldd /mnt/bin/bash
ldd: /mnt/bin/bash: No such file or directory
Offline
I was made earlier
pacstrap -K /mnt base linux linux-firmware nano
Offline
bash should be part of base, any errors while calling pacstrap, like pgp key signing errors?
Yes there are much
An example:
error: linux-firmware: signature from "Andreas Baumann (sign) <mail@andreasbaumann.cc>" is unknown trust
::File /mnt/var/cache/pacman/pkg/linux-firmware-20250917-1.0-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
Aborts these errors automatically without entering any prompt.
My architecture is pentium4. I checked it as entering "cat /proc/cpuinfo". And i have "cmov, mmx, sse and sse2" flags.
Last edited by LiberalPerson (2025-11-15 12:20:54)
Offline
Fixing Broken Keyring(s)
Sometimes an ISO contains broken keys. This can easily be fixed by updating your keyring with pacman -S archlinux-keyring archlinux32-keyring
Issues i have run:
1- pacman -S didnt work so i used pacman -Sy
----
2- pacman -Sy archlinux-keyring archlinux32-keyring
pacman offered me 2 packages that will be installed. I confirmed. I took signature errors (unknown trust) for both packages. It asked me if i want to delete corrupted .zst files and i confirmed because it was default.
Then checked the packages with pacman -Qi
archlinux32-keyring is accessible by pacman -Qi and its architecture is "any"
And archlinux32-keyring is conflicting and replacing with "archlinux32-keyring-transition" according to pacman -Qi
But "archlinux32-keyring-transition" is unaccessible by pacman -Qi
archlinux-keyring is unaccessible.
----
3- pacman-key --populate archlinux32
==> Appending keys from archlinux32.gpg...
And other progresses...
gpg: next trustdb check due at 2025-12-31
(End of answer series)
pacman-key --populate archlinux
==> ERROR: The keyring file /usr/share/pacman/keyrings/archlinux.gpg does not exist.
Last edited by LiberalPerson (2025-11-15 11:50:53)
Offline
Creawte a pacman.conf where you set SigLevel=Never. Keys seem roally borked and expired, also master keys it seems..
Yes, adding SigLevel=Never to repository settings worked.
Offline
On the bottom of https://buildmaster.archlinux32.org/buildmaster/ you can see the signing and master certificates and their state, red means expired (so mine) and yellow means
close to expire.
Offline
Pages: 1