Keeping in touch again, it certainly has been a while


It has been a while since we posted an article about other things than important notifications or release announcements, a proper chit-chat, so to say and today, I decided it was time to just say hi again from us.

The team

I wrote the word “I” in the opening of this article not because I’m writing the article, but because it was me who was mostly invisible during a large chunk of this year. The rest of the team, @joekamprad, @manuel, @dalto, @Pudge, @sradjoker, @ringo and all the moderators were very visible and adequate in interacting with you.
It can’t be said enough, they have been doing a stellar job being there for the community and keeping EndeavourOS alive and kicking. EndeavourOS’ crown is undisputably yours, you are and have always been the real heroes of this distro in my eyes.

As for me, I have been through a very rocky period in my life having to deal, with and still dealing with a personal loss but I am climbing out of my mourning period bit by bit and getting to grips with things. So, one of my goals is trying to be more visibly involved with the project again.

Slimbook purchase


Joe was working on a refurbished Dell workstation we bought in 2020 from the donation amount that was available at that time. The machine was a fairly older one, so we knew that it wouldn’t last for a long time, but considering the available resources at that time and the fact we could upgrade it, it was the best option.

This year it became clear that the workstation needed some big updates to keep the workflow going.
We have looked into purchasing upgradable parts for the machine, but our increasing popularity was also reflected in our Open Collective account. So, we decided to make a more sustainable purchase, in both energy consumption and the long-term aspect.


We also wanted to openly support the Open Source community by going for a company that produces machines with Linux as their first priority.
In April we ordered the Slimbook Kymera Ventus AMD with an AMD Ryzen 9 5900X, 32 GB RAM, 500 GB SSD and a 1 TB secondary HDD.
Slimbook gifted us a better cooling fan with LED instead of the standard one we ordered and to have our logo engraved on the front of the machine.
Unfortunately, the machine arrived with transport damage at Joe’s house making the machine not able to boot.
After a very helpful conversation between Joe and Slimbook, the issue was resolved by Slimbook and they even sent us a keyboard for the inconvenience.
The Kymera Ventus is now happily and steadily running at the heart of our development.

PineBook Pro

Pinebook pro

With the addition of Sradjoker to our core development team, EndeavourOS ARM has been making huge leaps in development, also thanks to @jonathon for his invaluable input. To expand the supported hardware for EndeavorOS ARM, we bought the latest PineBook Pro that was released in August.
Behind the scenes, Sradjoker is hard at work to add the PineBook Pro to the supported hardware for our ARM installation.



No, we didn’t buy an entire server room, but this purchase was the most visible and noticeable one and perhaps also the most confusing one for you. Let me explain…

After our previous server was showing its age earlier this year, like the Slimbook purchase, we decided to step up the game by going for a more modern and powerful server that meets our requirements now and in the future.

Unlike the previous situation where the websites, forum and mirror were running on one dedicated server, we went for a separate Ubuntu Linux VPS for the mirror and one dedicated server for the websites and development.
The dedicated server has the following specs: Intel Xeon E3-1230v6 (Kaby Lake), 4 x 3,5 GHz (max. turbo 3,9 GHz), 32 GB DDR4 ECC RAM and 2 x 480 GB SSD and it is running Proxmox 7 on Debian 11 Bullseye.
With Proxmox we are able to run the websites and forum in a VM and still have room to create containers for development.

As you might have noticed we have migrated twice to another server in a very short time. If you missed it, I wouldn’t blame you because both migrations were eclipsed by the Grub issue earlier.
The reason for the double migration was that shortly after we went for the original new server, the provider released slightly newer server models for a drastically lower price. (The difference was around € 35,- less a month)
Since we originally were running the Xeon E3-1230 and not the slightly newer E3-1230v6 hardware, we had to migrate again to get the new and lower price. Luckily, our server provider was very flexible in changing the contract.


Endeavour nose

By the end of last year, we have introduced naming our major releases followed by intermediate releases adding Neo and Nova to the major release name and shipping small changes or bugfixes to the major release.
You might have noticed that those intermediate releases have received version numbers as well since the Artemis release.

Let me explain the difference, the major releases (Atlantis, Apollo, Artemis) ship new features.
The Neo and Nova releases ship improvements and bug fixes accompanied by the latest package and kernel.

So what is the deal with these version number releases operating under the same name like Artemis neo 22.7 and Artemis Neo 22.8, I can hear you think.

Well, those are releases with an important fix, like the Grub issue, but with the same packages and kernel version that is identical to the previous one, Artemis Neo 22.7, in the most extreme case.

But most of the time they are ISO refresh releases with nothing other than the latest packages and kernel version shipped, so without major bug fixes or improvements.
This gives the development team more time to focus on the development of the new features for the major and interim releases, instead of rushing to push one out because the released ISO is deteriorating and in need of a new release.

At the moment Artemis Nova is already 1,5 months old but we are waiting for kernel 6.0 to smoothen out small issues (mainly Nvidia and display bugs) before releasing a new refresh release.
Having said that, our next major release is getting more and more into shape and it will operate under the name Cassini, named after the astronomer and engineer but mostly after the Nasa Saturn mission.
I cannot unveil the new features right now because the dev team has to make choices about which of the exciting new features in development are getting into the release, but Cassini will be a release to look forward to.

Thank you


I think I have brought you up to speed with what has been happening and what is going on with us and I promise to keep in touch like this more often.
Of course, I can’t leave without thanking you, the community, for keeping us alive on the forum, Telegram, Reddit and all of our other official and unofficial channels. But I would also say a special thanks to our financial contributors to our Open Collective account because without that support we wouldn’t be able to move forward with our hardware and infrastructure. :purple_heart:


Translation: Ich melde mich zurück! es ist schon eine Weile her


:fr: translation here: Nous sommes de nouveau en contact, cela fait un moment


Merci beaucoup monsieur!


De rien :smiley:


Thanks much for the update, @Bryanpwo! I had already been wondering about your where-abouts…
We all have our personal, private, intimate issues to go through in this life. I feel for you, as ups followed by downs, followed by ups, etc. aren’t making an exception to anyone of us. My dad (long gone, sadly) used to say this is the only true justice in life that we all eventually have to die, regardless of our achievements or failures. Right now, my mom is in IC and I am praying for her survival.
Anyway, as I remember there were some loose ends regarding the forum-software regarding images posted…
Weren’t they?

:peace_symbol: :heart_eyes:


As I already mentioned we did two migrations with two different forum backups and both resulted in a forum with the exact same image upload issue. Nobody seems to know the reason or a solution to make it work again.

1 Like

Ugh. I remember you saying differently, a background-process to change it… Must have missed your latter post on this, sorry.


That was before the second migration. Since the background rebake didn’t work, we (and the Discourse team) hoped the issue would be resolved by a reinstall of the forum. The Discourse team was convinced it was a glitch in the first migration, but the second migration resulted with that same “glitch”.

Somebody must know! :sweat_smile:



Finnish translation
Suomenkieliset terveiset!


I am sorry to know this. You are a nice man and I am sure you will come over whatever. I wish I can help in any way.

I am sure it will be a great development.

Sorry for this news. I hope she will make it and be fine soon. I will pray for her.

I will pray for all of you guys. I honestly feel anything that hurts anybody hear personally hurts me somehow. If you allow me to count myself one of the family. This is what I feel. Why would I bother to write this if this is not the case.


Here you have slimshady64 in his habitat:


All the blinky is headed to the wall… so one day I will change the desk to show off all the RGB ?


Jeez, what a mess! :rofl:

a lot of connections :wink:

@joekamprad goes online:



Slim Shady


Too many, if you ask me. Here’s my workplace on a very busy day:

And I mean: Really busy!

1 Like

The most important item is on the right side of the picture. :stuck_out_tongue_winking_eye:

That’s a great opportunity to be reminded where to donate to the project! From my side I hope to give once per year since I am using eos on a daily basis. Pretty sure many people pay monthly to use some kind of software (most likely proprietary) or Netflix or similar. Think about it if you use eos for free (and also all the support you get here to fix your computer problems :stuck_out_tongue_winking_eye:)… Check out the donation page :grin: :wink: