You are not logged in.
I using archlinux32-2022.12.01-i486.iso boot in vmware, and dhclient, then mount /dev/sda1 and format to ext4 mounting to /mnt, cp /etc/pacman.d to /tmp/pacman.d , mount --bind /tmp/pacman.d /etc/pacman.d to make some mirror selection. then pacstrap -K /mnt base linux linux-firmware (following the instruction of https://wiki.archlinux.org/title/Installation_guide). but all downloaded file could not pass the verification.
because could not upload images, I write it here:
checking keys in keyring...
checking package integrity...
Error: jansson: signature from ,ndreas Baumann (sign) <mail@andreasbaumann.cc, is unknown trust
:: File /mnt/var/cache/pacman/pkg/jansson-2.14-2.2-i486.pkg.tar.zst. is corrupted (inualid or corrupted package (PGP signature)). Do you want to delete it?
Error: binutils: signature from ,ndreas Baumann (sign) <mail@andreasbaumann.cc, is unknown trust
:: File /mnt/var/cacbe/pacman/pkg/binutils-2.40-6.0,i486.pkg.tar.zst. is corrupted (invalid or corrupted package (PGP signature)). Do you want to delete it?
Error: failed to commit transaction (inualid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.
==> ERROR: Failed to install packages to new root
Last edited by youxiaojie (2023-11-30 04:02:46)
Offline
The ISO is so old, that all keys have basically expired, you can copy /etc/pacman.conf to a /mnt/mypacman.conf and specify it with --config.
Maybe easiest is just to disable the key checks.
Offline
does any way to update key?
Offline
and with tar paramater is used to untar the .zst? tar xvf ...
Offline
I found a list of steps to refresh the keyring (this takes a lot of time on my eeepc) and you must do it twice once for the install media and once for the system once chrooted. I feel like this info should be easier to find and maybe be part of the install process but w/e
https://www.archlinux32.org/download/
Offline
One of my questions would be why your are using the i486 on an eeepc. Even the 701 should support i686 if even pentium4, check out /proc/cpuinfo
and https://www.archlinux32.org/architecture/. The newer the subarchitecture the more working packages you can expect.
Offline
Hi. Sorry for my EN. )) I have same issue. I need test i386 on VM QEMU. I select CPU model "Conroe" then cteate VM. Try use:
1. archlinux32-2023.01.04-i686.iso
and
2. archlinux32-2023.03.02-i686.iso
but have issue about signatures:
Error: failed to commit transaction (inualid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.
==> ERROR: Failed to install packages to new root
On download page i found:
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 and then pacman-key --init, pacman-key --populate archlinux32 and pacman-key --refresh. Eventually this is something you want to do in the chroot of your installation (arch-chroot /mnt).
and try it, but dont have result.
Any ideas? May be i miss select CPU model when create VM? May be need qemu32/kvm32 or how best CPU model for 32 bit CPU select in QEMU? Tnx.
*** UPD
Found little fix - in /etc/pacman.conf set SigLevel=Never
Last edited by omg1 (2024-01-27 11:04:33)
Offline
QEMU has a i486, pentium, pentium2, pentium3 or so if I recall correctly.
The workaround with SigLevel=Never might be best till I can make new ISO images.
Currently far too many things are broken, so remastering an ISO is not an option.
Offline
This worked for me too. To make it super clear to newcomers:
1. set SigLevel=Never in /etc/pacman.conf
2. pacman -S archlinux-keyring archlinux32-keyring archlinux-keyring
3. pacman-key --init
4. pacman-key --populate archlinux32
5. pacman-key --populate archlinux
6. pacman-key --refresh
7. set SigLevel=Required DatabaseOptional
8. Run pacstrap as usual
Then, after doing `arch-chroot`, repeat steps 1-7 from above.
Some steps may be superfluous, this is just what worked for me (as far as I can remember)
Last edited by jacko (2024-02-24 11:50:48)
Offline
Sorry, I can't figure out how to set siglevel = never in pacman.conf. I've been trying to install arch linux 32 on an asus eeePc for 2 days and I still can't find a solution. Can you explain me how to set this options in pacman.conf via the installation terminal?
I tried writing "set SigLevel=Never in /etc/pacman.conf" but nothing changed. Keep checking the signature.
Last edited by Gim (2024-03-14 22:20:08)
Offline
/etc/pacman.conf is a file with a bunch of config options in it. You need to use a text editor to open the file and then modify the line that says "SigLevel=Required DatabaseOptional" to instead say "SigLevel=Never".
To open /etc/pacman.conf with a text editor, I would recommend nano. Type in the terminal `nano /etc/pacman.conf`, possibly using sudo if you need it.
You should check out this article, it will help you with online instructions about arch linux stuff. Best of luck with the eeePc!
Last edited by jacko (2024-03-15 04:14:24)
Offline
Disable signature check seems to work. However, this completely defeats the whole security of the distro, because even after you re-enable it, you just installed a whole slew of unchecked signatures that you will from then on trust for all future updates. Can someone 1) confirm that my understanding is correct (and if so we should probably warn people when using it) and 2) I just arrived at arch32 so my first question is, what is the reason why there is not newer install image?
Anyway, greetings all! Arch32 seems to be giving a new lease on life for my old machines. Keep up having fun and doing great work everyone.
Miki.
Offline
You can minimize the security risk by just lowering the SigLevel during updating the archlinux32-keyring.
Also, you can always import the respective keys by hand (but have fun to track them done somewhere on key servers or so).
SigLevel=Never is a really bad idea and defies the purpose of having keys and signing in place, you're right.
One could also just resign all the packages on the mirror with new ones.
For a distro, which is barely kept alive, used on maybe old laptops or on vintage gear, security requirements are
not the same as if you would run actual servers on Arch32. That's my personal opinion.
Welcome to Arch32
Andreas.
Offline