EndeavourOS Installation Hangs Indefinitely At 13%

So I have managed to successfully install the OS. I have no clue if this pertains to this issue or is somehow related but with the latest ISO release I have been having driver issues with my Realteck RTL8822CE that caused the mirror list in the installer to get all funky and confused. I ended up installing https://github.com/lwfinger/rtw88 which has fixed the driver issue both with the installer and after installation.

Prior to installing using the online method, I fixed the driver issue and then ranked the mirrors using the buttons ā€œArch, Arch, Endeavourā€ in that order from top to bottom. Then I proceeded to install EndeavourOS which finished almost instantly.

I have screenshots of red errors involving mirrors after installing through the offline method and as well as during the installation attempts in the past. Let me know if you would like these, there is a lot of logs shown in the screenshots and I have no actual log file since I have reinstalled using the online installer.

Could you show the contents of file /etc/pacman.d/mirrorlist of this new install?

From what we see, the issue should be fixed.
There was an issue with a Hotfix that causes installer to use the example mirrorlist and not the ranked list.

Sorry for the inconvenience, it wasn’t intentional, just an oversight, and it’s summer holidays here in Europe at the moment.

Usually we are faster in resolving such issues.

9 Likes

We will do that… Better say we already do that, only that we are a very small team, and we rely on the help of reports from the community as no one in the team is resident in one of the areas with problematic mirror situation. So it is hard to reproduce and hard to resolve such issues in e general way.

You can see in this thread, too, rare that users following up on issues and providing needed logs and stuff.

3 Likes

I don’t seriously believe that I live in an area with a problematic mirror situation (Saxony, big city). It’s a shame that this was my first experience with EOS. I’m surprised at myself that I didn’t throw the shit away straight away. Manjaro stick is still lying around here.

I can respect that.

Despite being a Linux user and sysadmin for 25 years, I’ve never delved too much into the calamares installer or live environments, if i knew more about that i would actually be interested in helping maintain the project… but given a lot of the project is based around the installer, I’d probably be in the way more than anything…

Still, i actually have considered forking Arch and doing something very ā€œUn-Archlikeā€ with it at some point. perhaps i need to learn how to help here as a stepping stone. LOL

2 Likes

YES, there were several problems that influenced each other.
There are ongoing issues with some mirrors at the same time.

I was more talking, in general, about creating a save way to have mirrors working for everyone around the globe.

There is no need to threaten to install Manjaro, you are welcome to do so.

5 Likes

Would you still like me to send you that info, even though it is fixed?

1 Like

For the record, it would be interesting, yes.

1 Like

That wasn’t meant as a threat, I’m glad to finally be able to get away from the green thingy. But I still have it in the back of my mind as a backup. It just went badly with the first attempt here. I’ll probably reinstall it again in the next few days because I have the feeling that something might be wrong.

1 Like

the installer could run reflector before the install process, so the user always gets a fresh set of good mirrors.

Good to hear :vulcan_salute: :handshake:

1 Like

My understanding listening to the team, is that the installer wasn’t using the updated mirrorlist it was defaulting to the read only example they can correct me if I’m wrong.

1 Like

We do that already.. not using reflector as it is also problematic in cases.. we have different implementations already to resolve mirrorlist issues.
We have 2 options on the welcome tool to rank archmirrors and one for EndeavourOS mirrors so user can manually rank before starting installer, with tools or even manually changing the list on the livesession all these will get used for the install process.
In case user do not manually rank mirrors installer itself runs ranking of both mirrors before running any package installation. The used script there is where we currently work on to make saver / better / giving more output.

3 Likes

Who do I speak to about refunding the €0.00 I paid for EOS as compensation for this weekend’s outage?

:wink: :laughing:

3 Likes

Refunds will only be made in free beer :wink: :beers:

5 Likes

https://termbin.com/oby3

1 Like

I disagree with your opinion of what EOS is and or it’s goal.

I don’t care for Reddit and users that want to sound off because they have nothing better to say.

I’ve been using EOS for over 5 years and i haven’t found there to be many issues when it comes to mirrors. Yes it happens but it’s not been something that is constantly happening. This is a one off as far as I’m concerned. I said before I didn’t think it was a mirror issue but something in the process causing it. Looks like @joekamprad has confirmed that it was a hotpatch issue inadvertently relating to mirrors that caused it to use the wrong mirror list and not the ranked mirror list.

3 Likes

Ok I was under the impression rather you ranked the mirrors your self or not that pacman during the initial install was in fact going to. So has this changed or did I get my information wrong?

Well, sir, The fact is, EOS inherited the Antergos community of which i was a member of, and regardless if you agree that’s the internal goal of EOS or not its the general label public opinion has placed upon you mostly due to that association, and even if you disagree that to be the internal goal, even if the founder says point black that isn’t really our goal, and to be clear i’m sure they would.. It doesn’t change the mass perception of the project. what it comes down to is people are going to use the project for THEIR reasons not the reasons you have defined for them..

Well, see this in my opinion is a problem especially from the position of a staff member, again projects get adopted and gain popularity because they have a use case for the USERS rather what the creator may or may not envision..

And discounting someones fair assessment that there are issues because you don’t like the notion of the claim, or you don’t believe it or otherwise haven’t experienced it yourself not only do i find that hard to support as a ethical standpoint.. But also it’s just plain unsightly from a member of staff.

I have been known to be extremely critical of FOSS projects that take stances like this, and adopt a, ā€œQuit complaining and fix it yourselfā€ attitude in the past and i’ll be no different here, because it tarnishes the very idea of a community, and by extension the community developed project in my mind that it isn’t funny.

I just personally reject the idea that you should have the right to discard any users complaint or criticism of the product solely based on the notion that you don’t agree with their stance. Which is compounded even more when that stance or complaint is supported by two, three or even 10 users.. I’ve had projects have a literal pile of users saying hey there are issues here and while i don’t have the skill to fix them directly i can offer insight for ways to improve them as my way to contribute, and those project leaders choose to silence those complaints with topic locks rather than to address them because they adopted this mentality that they are volunteers and they are oppressed/unappreciated and the only issues with the project that mattered were they ones they cared about..
And while that HAS NOT happened here. I offer it as reference for what happens these days in some FOSS projects.. It does not inspire community involvement when the existing community is hostile.

I’m not a fan of picking and choosing which issues are deemed worthy or not, if its confirmed by multiple users its a valid issue. Period.