Devices running Endless OS 5 or earlier will first upgrade to Endless OS 5.1.3, which has also just been released, and then to Endless OS 6.0.0. Both updates will be applied automatically (unless you have disabled automatic updates) over the coming weeks.
A small number of devices that were supported by Endless OS 5 are no longer supported by Endless OS 6 and cannot be upgraded from 5.1.3. In some cases, advanced users can change a configuration setting in the affected device’s BIOS to enable the upgrade. See the release notes for full details.
I updated my desktop to Endless OS 6 and it went smoothly and quickly, thank you for the update.
I also downloaded the installer. I was hoping to install Endless OS on my 2010 17" MacBook Pro. It is currently running Debian Bookworm and I assumed it would likely run Endless OS 6. That was not the case. The machine simply hangs upon selecting the Endless OS USB installer I created.
It’s perhaps a little surprising that Bookworm boots on your MacBook Pro while our installer does not, but even Intel Macs need special care and feeding to boot Linux; our bootloaders are configured differently to Bookworm’s; and we use a different build & version of the kernel. As noted on our hardware support page:
Apple hardware […] not officially supported by Endless OS; depending on the exact model of Mac, Endless OS might work, but this is not tested
Thanks for your response. This laptop is getting so old it is about time to teach it to drive. Apple dropped support for it many years ago and until about two years ago Linux would not run on it either, but that has changed. Just about all Linux distros will run on it. Debian 11 did not run on it, but Debian 12 runs just fine.
I have tried to compare Debian’s booting to Endless’, but it is way above my pay grade. Debian is very very slow to boot, both from an installer USB and from the SSD after it is installed. I did let the Endless installer stay in a hung state for an hour just to see if it would come to life, but no luck.
Is there a way to set the boot loader (grub?) to verbose, just to see what if anything is happening?
Overall Debian Bookworm with the Gnome UI is not very different from Endless from a user perspective, however it is missing some of the nice applications that come with Endless.
If you hold Shift or hit Escape at just the right moment (see this page) you may be able to get to the GRUB menu for the installer you’re trying to boot. You could remove quiet and splash from the linuxefi line and see if you can get any more information.
Actually there is no technical barrier to configuring the Endless OS Flatpak remotes on a Debian Bookworm system and installing those apps. (Flathub has documentation on how to configure its remote but I don’t think we have that for eos-apps etc.) You could also build & install eos-desktop-extension locally and it should work on Bookworm’s gnome-shell if you prefer the Endless look-and-feel.
By following the procedure, I was able to install my pinebook pro from version 5.1 to version 6.0.0 very easily.
Many thanks to the Endless team
Thank you for this beautiful version 6
I’m currently checking for power management problems.
In version 5.1, in “sleep” mode, the pinebook pro continued to consume energy “as in normal mode” and therefore quickly drained the battery.
The only solution was to “power off” the machine.
It seems that this problem has not been solved, so I’ll create a topic about it.
There is the warning about toolbox containers and upgrade to EOS 6.0. Since toolbox containers are podman containers, I am curious if this warning is also valid for podman based distrobox containers. Any ideas?
The issue was specific to toolbox, which now needs additional host paths mounted into the container in a way that can’t be done after the container is first created. I don’t know if distrobox will also be affected – based on my understanding of how it works I don’t think it will be affected, because it works using a shell script (executed with the container’s regular shell) rather than a compiled executable that needs to use the host system’s libc.
The upgrade went flawlessly on my Acer TravelMate Spin B118-RN. There are some obscure warning messages when using distrobox:
WARN[0000] Failed to decode the keys [“storage.options.ostree_repo”] from “/sysroot/home/bernhard/.config/containers/storage.conf”
but distrobox appears to run despite these messages, does somebody have ideas how to resolve them?
BTW: congratulations: I had asked for a possibility for hibernation some time ago and found now deeply hidden in the power configurations the option for hibernating (selection between Suspend, Power Off, Hibernate, and Nothing is possible)
and hibernation appears to function without problems, when using the power button. Is there any chance to configure also “Lid close” for hibernate instead of suspend? I could not find any configuration option for it in EndlessOS; although I found instructions for Ubuntu I am curious, if these also apply for EndlessOS. Are these applicable?
We inherit these configuration settings from GNOME.
As it happens I also recently discovered this option. To make hibernation work I created a swap partition (rather than a file), disabled secure boot, and I have a vague memory of editing the kernel command line. (The need to disable secure boot is the main reason why hibernation is no longer widely supported on Linux desktop/laptop systems.)
Endless OS also uses logind so those instructions will probably work. Rather than editing /etc/systemd/logind.conf directly you should instead create a directory /etc/systemd/logind.conf.d and create (say) /etc/systemd/logind.conf.d/hibernate.conf with contents like:
[Login]
HandleLidSwitch=hibernate
See man logind.conf and the comment at the top of /etc/systemd/logind.conf for more information about this “drop-in” pattern.
Apple dropped support for it many years ago and until about two years ago Linux would not run on it either, but that has changed. Just about all Linux distros will run on it. Debian 11 did not run on it, but Debian 12 runs just fine.