No module symbols loaded - kernel modules not enabled.
Hello,
I get the following output from the command "head -n 7 /var/log/boot.msg".
Inspecting /boot/System.map-2.6.23.1-default Loaded 27483 symbols from /boot/System.map-2.6.23.1-default. Symbols match kernel version 2.6.23.
No module symbols loaded - kernel modules not enabled.
klogd 1.4.1, log source = ksyslog started.
<5>Linux version 2.6.23.1-default (root@Sonne) (gcc version 4.2.1 (SUSE Linux)) #1 SMP PREEMPT Sun Oct 28 15:34:56 CET 2007
A lot of discussions can be found around this specific notice about symbol loading. I am interested in an explanation for the effects on the current kernel.
Does it just mean that no debugging symbols were loaded?
Load all symbols for debugging/ksymoops (KALLSYMS):
"Say Y here to let the kernel print out symbolic crash information and symbolic stack backtraces. This increases the size of the kernel somewhat, as all symbols have to be loaded into the kernel image."
The following configuration option is active on my system, of course.
Automatic kernel module loading (KMOD):
"Normally when you have selected some parts of the kernel to be created as kernel modules, you must load them (using the "modprobe" command) before you can use them. If you say Y here, some parts of the kernel will be able to load modules
automatically: when a part of the kernel needs a module, it runs modprobe with the appropriate arguments, thereby loading the module if it is available. If unsure, say Y."
Regards,
Markus
Quoted 9 lines · Markus Elfring
Hello,
I get the following output from the command "head -n 7
/var/log/boot.msg".Inspecting
/boot/System.map-2.6.23.1-defaultLoaded 27483 symbols from/boot/System.map-2.6.23.1-default. Symbols match kernel version 2.6.23.
No module symbols loaded - kernel modules not enabled.
Quoted 8 lines
klogd 1.4.1, log source = ksyslog started.
<5>Linux version 2.6.23.1-default (root@Sonne) (gcc version 4.2.1 (SUSE Linux)) #1 SMP PREEMPT Sun Oct 28 15:34:56 CET 2007A lot of discussions can be found around this specific notice about symbol loading. I am interested in an explanation for the effects on the current kernel.
Does it just mean that no debugging symbols were loaded?
This message is added by klogd, and it is independent of CONFIG_KALLSYMS. (Since I do have KALLSYMS=y while also getting that message. I suppose it is because CONFIG_DEBUG_INFO=n)
Quoted 3 lines
This message is added by klogd, and it is independent of
CONFIG_KALLSYMS. (Since I do have KALLSYMS=y while also getting that message. I suppose it is becauseCONFIG_DEBUG_INFO=n)
I could not find the message text in my kernel source directory so far. I had also no luck with a cross reference like "http://lxr.linux.no/search".
Which source code is responsible for the notice?
Regards,
Markus
Quoted 9 lines · Markus Elfring
Quoted 4 lines
This message is added by klogd, and it is independent of
CONFIG_KALLSYMS. (Since I do have KALLSYMS=y while also getting that message. I suppose it is becauseCONFIG_DEBUG_INFO=n)I could not find the message text in my kernel source directory so far. I had also no luck with a cross reference like "http://lxr.linux.no/search".
Which source code is responsible for the notice?
Like I said, klogd. This seems to be outside the scope of LKML.
Quoted 1 line
Like I said, klogd. This seems to be outside the scope of LKML.
Which function instructs the kernel log daemon to record the notice at the beginning of the boot process?
http://chuck.netbsd.sk/source/xref/sysklogd-1.4.1rh/klogd.c
Is the message sent by a printk() call?
Where is the text "Inspecting" passed?
Regards,
Markus
Quoted 9 lines · Markus Elfring
Quoted 2 lines
Like I said, klogd. This seems to be outside the scope of LKML.
Which function instructs the kernel log daemon to record the notice at the beginning of the boot process?
http://chuck.netbsd.sk/source/xref/sysklogd-1.4.1rh/klogd.cIs the message sent by a
printk()call?
Where is the text "Inspecting" passed?
Like I said, no. This is done by klogd.
Quoted 1 line
Like I said, no. This is done by klogd.
Now I have found the notice "Inspecting" in the function "CheckMapVersion".
http://chuck.netbsd.sk/source/xref/sysklogd-1.4.1rh/ksym.c
I am interested to look at a source file that contains the dicussed error message. Does anybody know a development package for the kernel log daemon?
Regards,
Markus
Quoted 8 lines
Quoted 2 lines
Like I said, no. This is done by klogd.
Now I have found the notice "Inspecting" in the function "CheckMapVersion".
http://chuck.netbsd.sk/source/xref/sysklogd-1.4.1rh/ksym.cI am interested to look at a source file that contains the dicussed error message. Does anybody know a development package for the kernel log daemon?
syslogd...src.rpm in your distribution.
Re: development package for the kernel log daemon
Quoted 1 line
syslogd...src.rpm in your distribution.
I'm sorry - I can not select a -devel package for klogd, syslogd and syslog-ng in my YaST2 GUI so far. Would you like to suggest any additional installation source?
Regards,
Markus