How about the iso from the latest testing announcement that Phil posted? Did someone test them (the xfce one)?. I am on a metered connection right now, i cannot sped 5GB just to test.
The latter is at least 3 Xfce images, copied to Ventoy, and while trying to boot live, the boot process stops with this message.
(Full Intel IGP machine LENOVO ThinkPad T480)
“Unable to contact settings server
Could not connect: No such file or directory”
I noticed that in the last approx. 1.5-2 months there are problems with the Manjro images.
Time to ping @philm i think. This is a high priority problem, i think. When you make a distro and the official images do not boot… not the best recruiting strategy.
Linked discussion
TLDR: the xfce images do not boot to desktop with the above error at the login screen, loginng as manjaro manjaro also does not work (the login screen should not even be shown). This is on real hardware, seems like they boot on virtual machines.
Exactly, the first iso i personally tested as broken was with 7.0.
So maybe just remove plymouth i guess?
Maybe it can be tested if one takes a broken iso and starts with editing the grub kernel parameter adding
plymouth.enable=0 disablehooks=plymouth
I am on a stupid mobile internet right now and cannot help much with the 5 GB downloads.
Im actually just did that on the Live Boot with the Edit option in Grub.
Sadly, It doesn’t changed the situation.
But i could with some heavy and strange tricks, to finally get a monitor signal after 3-5 times switching between several TTY’s and Logged in and swap to desktop with alt+ctrl+f1-f6, logged in with manjaro and manjaro (in SDDM) to get no monitor signal AGAIN and repeat everything again and again and pressing also crtl+alt+f9 to reset desktop and then to TTY again and logged in.
And out of nowhere i was on the desktop and had a picture.
Its magic, thanks to @fredvej in your preview iso topic, who wrote that info.
I did switched between tty’s but didn’t used any special commands like him with run localectl set-keymap dk… which he wrote.
If someone test longer, its possible there is a clean way to get a picture. Maybe it was crlt+alt+f9? maybe the login in TTY… who knows.
/off depends what you store there. A simple grub is 3 mb. The winboze files around 100. If you store kernels there, or make UKIs, with initramfs containing everything (fallbacks), and have nvidia and the driver is also put there with the kms hook, a kernel can indeed take several hundred MB. Quite an edge case i would say. (Worst case - fallback and early nvidia will probably be around 150+150mb per kernel. But you don’t really need fallback so i think even in the worst of worst scenarios you will fit 2 kernels on 500mb).
I think for 99.9% of the cases 500 mb is enough. You will probably only use 20 mb from it at most.
Calamares uses 300M and it has proven enough - dual booting windows you only have 100M and that is usually enough - you can even get a single unified kernel to fit into such partition.
If you want to encrypt the system but want to leave /boot unencrypted you should set aside enough space - like 4096M - then encrypt the root.
I use 2048M EFI - because I am using unified kernel directly from efi. For that reason I have - a while back - suggested we make it the default on the installer.
