Okay, I tried this, but unfortunately I have no success with this.
I did learn how I can disable the the fancy Fedora bootscreen so I can follow the systemd initialization during boot. (which I’m leaving off for now so I can see wth is going on)
I also learned that; if I try to look for backlight devices with ls /sys/class/backlight i see no devices at all.
I just switched from the nvidia driver to the nouveau driver, i don’t know if that is the reason it’s not detected (backlight didn’t work in both cases, so that’s why i tried switching drivers). But if it does work with the nvidia driver … I can say bye-bye to Wayland… That would be a bummer. I’ll try to keep updating this thread with any findings.
Tried ls /sys/class/backlight again, with the nvidia proprietary drivers. Still no devices to be found there. Do specific driver packages exist for specific Apple computers to deal with these specific device features?
I thought I was going mental, but no… the install USB does have the slider. It knows what hardware to address. What’s the best way to backpedal this information, so I can implement it on the actual installation… I’ve actually had this experience before, where the live install actually gave me a better experience then the install itself… How is this possible?
It even uses the light sensor.
ls /sys/class/backlight now also results acpi_video0
idk if this is in any way related, but i had this somewhat similar issue after the kernel update from 6.0 to 6.1 on a late 2011 mbp - it stuck on 100% brightness with brightness key not responding and no slider available (though i’m running kde).
and since i kind of accepted that kernel updates keep breaking things past version 6 at least on my system i decided against posting it here. so i just went for a previous kernlev version and stuck with it indefinitely.