Endeavour uses systemd, which means a lot of your services try to start after network.target. boot into a live USB and take a look around /etc/systems/system for problematic services.
Is there a way to tell what might be the issue?
I see folders like bluetooth.target.wants and network-online.target.wants and they contain .service files. I feel like this is probably what I'm after.
I wonder if it's an issue with Mullvad blocking network connections.
I tried disabling the network manager and Bluetooth through arch-croot but now it's freezing at
[ OK ] Finished Virtual Console Setup
Increase the boot verbosity or boot it up in single user mode and inspect the boot log to see if you can spot the issue.
Thanks that got me to the solution
techsupport
The Lemmy community will help you with your tech problems and questions about anything here. Do not be shy, we will try to help you.
If something works or if you find a solution to your problem let us know it will be greatly apreciated.
Rules: instance rules + stay on topic
Partnered communities: