I do not currently have any EOS on this Macbook Pro. I have run EOS in the past. I’m just trying to overwrite what’s on there and put EOS on it.
If you were using Artemis Nova, I would try to help.
The people in this topic are trying to boot the installer ISO. Installing refind really isn’t possible in that situation.
I’m sure I could hack together some version of EOS that would install so I could hack some solution to update to Cassini, but that is not what I’m sure the developers want. EOS is about, IMHO, ease of use. So I will spend my time on helping get Cassini ISO to boot. I’m not in a bind. The Macbook Pro is something I play with when I want to test out a new Distro or config of an old one.
you’re right.
I experienced the same kernel panic that (Doomdeer).
When artemis nova is installed, solution is very simple.
I did some testing. I got a copy of EndeavourOS_Artemis_nova_22_9.iso and flashed that to a USB key and did an Online install of EOS-Plasma with btrfs no swap. No issues with the install and it rebooted. There were no updates available when I check it out after the first reboot from the SSD.
I still can’t boot the cassini ISO without the Kernel panic but I get Cassini installed via the upgrade process. It left grub in place and that’s how it boots.
I seem to still have mkinitcpio but no dracut.
The new Cassini ISO has a different structure to install with selected boot options of systemd or grub. It is also using dracut. If you update from a previous install or ISO it is updated because it is rolling. But these new features only come from installing using the latest ISO.
Edit: You can convert to systemd boot. There is a tutorial for that. I’m not sure about dracut.
Okay, then what I see is what is expected. So if I need to get to Cassini now it’s install Artemis-Nova and upgrade. It’s a reasonable workaround for now. gives the developers time to find the real issue. I have a old Intel PC that I could try the Cassini IOS on, assuming it warms up a little in the garage. That’s where it stays. Usually not too cold, but this week too cold form me.
1 Like
This is a common misconception. As far as I know the ISO has always used systemd boot even before cassini.
Also the ISO itself uses mkinitcpio too. We haven’t changed that to dracut.
So for all intents and purposes the ISO structure hasn’t changed
It is trivial to convert to dracut. The instructions are in the dracut wiki article on Discovery
No misconception on my part. I’m referring to the install with an ISO previous to Cassini. It may boot on systemd but it’s only option is installing with grub.
Nothing in the Arch wiki is trivial. 
Edit: For me anyway!
Not the Arch wiki. Our wiki.
Okay… I didn’t know it’s been added already. Need to look at it i guess.
Yes that is correct, but the people in this thread can’t even boot the ISO. The systemd install in calamares won’t effect the ISO booting process
Not saying it does or did. I was only explaining current Cassini vs previous ISO that it doesn’t automatically update to those things. I have no answer why the Mac book pro doesn’t boot on the ISO. Wasn’t really talking about that side of it. 
Maybe I’m not explaining it in the right way. But it’s my way of thinking. Maybe structure isn’t the right word. But it’s changed in the fact that it has the option to install systemd or grub or no bootloader at all and it is using dracut. That’s all I know. Don’t know how to explain it any other way.
I know this topic has become nearly baffling to follow but Rick was responding to someone who said they installed Artemis Nova and upgraded to “Cassini”.
I think he was just pointing out that there were differences between upgrading to the latest software and installing from the Cassini ISO.
3 Likes
This is the only correct conclusion 
1 Like
How come I’m the only one understanding it now? It took a while but i get it! 