I, also, had a slew of problems with an attempted install on my gen 10 i5.I almost broke through with AL (the newest installer) when I omitted the use of swap, but for some reason when I logged in, my mouse kept freezing for minutes at a time. I then tried manjaro and endeavourOS got the same results (system locking, freezing).
Finally I decided I needed a working machine and arch was likely my issue… I ended up just installing MXLinux. What can I say. My wine box awaits… my other pc is still okay with AL.
The newer beta you found in another thread indeed has some issues, just built and untested for the fellow to try some things with wifi.
You just had the unfortunate case of updating to a version I had just pushed for internal testing which had this issue of not getting the correct count of partitions so it always thinks you have too few (I’m in the midst of rewriting/improving the partition list), apologies there but such is the way with the unstable packages.
If it’s any consolation it’s the weekend here and we’re working on getting a new release out to deal with the recent influx of issues due to the old age of the iso but we’re reworking the package/base install so testing is needed. We are working on it.
No worries, though, that’s alright I’m trying installing from a beta found in a thread not related to my issues
I did because of the troubles with the one you made for Colson. (Described above) ¯_(ツ)_/¯
then… not updating might be the answer to my worries?
Well, here it is too, and I haven’t any plan for tomorrow soooooo, if you need a beta-tester, eventuality, some help fixing. , my bash scripting skills are a bit rusty, hopefully the installer script is quite easy to follow and understand (gg)
By the way, I tried to say~… I tried adding boot options to the APPEND field in the archiso_(sys|pxe).cfg files but that does not seem to work. I still have to edit the cmd line manually at boot time.
Am I doing something wrong ? I’m quite confused
Yea the pacstrap method is what we’ll be focusing on for the future as it means our isos won’t age so poorly. The copy iso bit is still in just to give the option of a faster install (until the iso breaks they both should result in an identical system).
Glad it worked though, apologies again for the issues.
Yeah i know, I had close to no issue (at least from the installer) with the my last installs a few years back. I was quite surprised in fact. But hey, that’s alright. Except few errors when Pacman tried to create temporary files, the install went smoothly.
Everything’s looks fine for now
Yes, aside from the exit error mentioned (fixed now) it should work nicely.
Those are to be expected (mostly), same as you’d get installing arch. Because pacman is running in a chroot and many things aren’t present like /proc, /dev, etc., pacman has some scripts it tries to run after updating certain packages; systemd and the kernel are good examples. Some of them are smart and realize they’re running in chroot and just bail, others error.