I would tentatively agree that the kld_list syntax in /etc/rc.conf is probably not the real issue, but rather, a symptom of the real problem. It definitely seems to be a problem which involves the timing and sequencing of graphics-related events, at least, on my particular system.
It could be very helpful if more people who report the black-screen problem were more willing to share their own graphics processor identification strings, and message logs. Logs of great size can still be easily accommodated on this forum by running commands such as
And here is the link to provide access to my log. Note that the data of interest here will be prefixed with "Oct 9". These termbin.com links will reportedly persist for only about one month:
In my previous post I used a text editor to isolate what I considered to be the more pertinent portions of my dmesg logs, but your mileage may vary.
Also perhaps worth noting is the observation that, in my case at least, lightdm and sddm both seem to do a better job of starting graphics on my system than what I observe when using startx. Again, YMMV.
It could be very helpful if more people who report the black-screen problem were more willing to share their own graphics processor identification strings, and message logs. Logs of great size can still be easily accommodated on this forum by running commands such as
dmesg -a | nc termbin.com 9999
and cat /var/log/messages | nc termbin.com 9999
, and then copying the output links into their posts. For example:
Code:
root@mate:~ # cat /var/log/messages | nc termbin.com 9999
https://termbin.com/slfwl
root@mate:~ #
In my previous post I used a text editor to isolate what I considered to be the more pertinent portions of my dmesg logs, but your mileage may vary.
Also perhaps worth noting is the observation that, in my case at least, lightdm and sddm both seem to do a better job of starting graphics on my system than what I observe when using startx. Again, YMMV.