#
✕ nick:pedantic_picto
#asahi · 2024-05-15 16:40
pedantic_pictoso i assumed it was probably not the "right" way
#asahi · 2024-05-15 16:40
pedantic_pictoyeah i never really deal with selinux
#asahi · 2024-05-15 16:37
pedantic_pictothe trigger was changing enforcing to permissive in /etc/selinux/config and then rebooting. i noticed "dependency failed for selinux-autorelabel-mark.service" but i haven't been able to dig much deeper than just throwing the kill switch
#asahi · 2024-05-15 16:29
pedantic_pictoi was able to figure out my boot issues - it was related to selinux. booting with kernel param `selinux=0` let the system come up and get to kde
#asahi · 2024-05-14 21:26
pedantic_picto or just a blank screen
#asahi · 2024-05-14 21:26
pedantic_pictostill no dice. the previous image i have is 6.8.9-402 but i did notice that the kernel parameters for 6.8.9-403 had `ro`. removing `rhgb` and adding `nomodeset` ended up with a "you are in emergency mode" message saying "cannot open access to console, the root account is locked" with a press enter to continue prompt. doing that tries to start, but ends up with the same thing. fiddling with the kernel parameters either got me to the same spot
#asahi · 2024-05-14 19:27
pedantic_pictom2 macbook pro. trying to remember if i ran an update in the session before it started acting up. i _think_ i ran the upgrade by itself and restarted just to make sure it would work. i'll try out those grub options and see what it says
#asahi · 2024-05-14 19:14
pedantic_pictoi'm not sure if this is the right place to ask this question, but after a reboot today i will either see the fedora loading screen (after u-boot) freeze and become unresponsive, or go for a while and then the display goes blank. pulling up the grub menu to boot into the previous image didn't seem to help. has anyone else run into this?