View previous topic :: View next topic |
Author |
Message |
NoDataFound n00b
Joined: 01 Aug 2011 Posts: 34
|
Posted: Mon Jan 08, 2018 9:28 pm Post subject: Logging kernel message from the startup |
|
|
Hello,
I have seen on the screen a module which failed to load - something likle "nct6775" and [!!] on the right of the screen. I pretty sure that lmsensor module is failing and why - I've used sensors-detect and it found nct6775 (Nuvoton NCT5573D/NCT5577D/NCT6776F Super IO Sensors) which is probably not built into my modules.
But then again I don't see any error in the kernel log (dmesg, /var/log/dmesg, /var/log/messages).
Which is why I wondered the net in search of a solution to log those event so that I can investigate, but I can't find a proper way to do :
- This indicate some service on Debian : https://superuser.com/questions/176165/where-linux-places-the-messages-of-boot#176169 but I can't find any information on it, The bootlog does not exists (at list in eix after eix-sync)
- This date back from 2008 (https://forums.gentoo.org/viewtopic-t-409643-view-next.html) and it speak about that bootlog... which I can't find.
Is there a proper 2018-way of doing that ?
Regards,
NoDataFOund |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54237 Location: 56N 3W
|
Posted: Mon Jan 08, 2018 9:38 pm Post subject: |
|
|
NoDataFound,
The rc-logger may capture that. Read and edit /etc/rc.conf.
You can try the stone age way too.
That's and check the end of dmesg. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
NoDataFound n00b
Joined: 01 Aug 2011 Posts: 34
|
Posted: Tue Jan 16, 2018 9:09 pm Post subject: |
|
|
Well, modprobe is a solution but it was more general (since I cached a glimpse of this error, modprobe is fine when you know which module is failing).
[edit] and my problem is because the module is not compiled
The modification of rc.conf worked fine:
Code: |
rc boot logging started at Tue Jan 16 20:24:19 2018
* Loading module coretemp ...
[ ok ]
* Loading module nct6775 ...
* Failed to load nct6775
[ !! ]
* Setting system clock using the hardware clock [UTC] ...
[ ok ]
* Starting up RAID devices ...
* mdadm: No arrays found in config file or automatically
[ !! ]
* Checking local filesystems ...
fsck.fat 4.0 (2016-05-06)
|
|
|
Back to top |
|
|
mike155 Advocate
Joined: 17 Sep 2010 Posts: 4438 Location: Frankfurt, Germany
|
Posted: Tue Jan 16, 2018 10:23 pm Post subject: |
|
|
Quote: | Logging kernel message from the startup |
You could use Systemd. It starts logging at the beginning of the init/startup process. |
|
Back to top |
|
|
|