Hi, >> How do I troubleshoot this? How do I determine why a service managed >> by systemd didn't start? Why is there nothing written to syslog >> regarding this? > > did you run sensors-detect as root to setup the modules > lm_sensors needs to load on your system? > > You can also fiddle /etc/systemd/system.conf to set the > logging level. Yes, I've done that, and have also run sensors-detect successfully. A few "coretemp" and modules loading messages are printed in syslog, but that's it: Nov 15 21:30:43 mail01 kernel: [190985.265634] coretemp coretemp.1: Using relative temperature scale! Nov 15 21:30:43 mail01 kernel: [190985.275732] coretemp coretemp.0: Using relative temperature scale! Nov 15 21:30:43 mail01 kernel: [190985.285607] coretemp coretemp.1: Using relative temperature scale! Nov 15 21:30:43 mail01 kernel: [190985.295303] coretemp coretemp.0: Using relative temperature scale! Nov 15 21:30:43 mail01 kernel: [190985.304782] coretemp coretemp.1: Using relative temperature scale! Nov 15 21:30:43 mail01 kernel: [190985.316279] w83627hf: w83627hf: Found W83627HF chip at 0x290 Nov 15 21:30:43 mail01 kernel: [190985.396073] w83793 5-002f: Registered watchdog chardev major 10, minor: 212 It used to be there was a script that you could trace for debugging, but I don't understand how the new system works. I've set the following in system.conf: [Manager] LogLevel=info LogTarget=syslog-or-kmsg Is there something more I can do to troubleshoot this? Thanks, Alex -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
