From the latest SuSE Online update of the kernel. Check in /var/log/boot.msg <- It is the first 4 lines Inspecting /boot/System.map-2.6.11.4-21.7 Loaded 27512 symbols from /boot/System.map-2.6.11.4-21.7. Symbols match kernel version 2.6.11. <- NOTE No module symbols loaded - kernel modules not enabled. Another reason to download and compile your own. -- 73 de Donn Washburn Hpage: " http://www.hal-pc.org/~n5xwb " Ham Callsign N5XWB Email: " n5xwb@hal-pc.org " 307 Savoy St. HAMs: " n5xwb@arrl.net " Sugar Land, TX 77478 BMW MOA #: 4146 - Ambassador LL# 1.281.242.3256 " http://counter.li.org " #279316
On Tue, Jun 21, 2005 at 05:32:34PM -0500, Donn Washburn wrote:
From the latest SuSE Online update of the kernel. Check in /var/log/boot.msg <- It is the first 4 lines
Did you you check any earlier 2.6 kernels?
Inspecting /boot/System.map-2.6.11.4-21.7 Loaded 27512 symbols from /boot/System.map-2.6.11.4-21.7. Symbols match kernel version 2.6.11. <- NOTE No module symbols loaded - kernel modules not enabled.
In my experience, it's been the same with all 2.6 kernels, not just the latest YOU update but I don't see any negative impact on any of my systems.
Another reason to download and compile your own.
I don't see a reason. Do any modules not load on your system? or do not work? Regards, -Kastus
Kastus wrote:
On Tue, Jun 21, 2005 at 05:32:34PM -0500, Donn Washburn wrote:
From the latest SuSE Online update of the kernel. Check in /var/log/boot.msg <- It is the first 4 lines
Did you you check any earlier 2.6 kernels?
Inspecting /boot/System.map-2.6.11.4-21.7 Loaded 27512 symbols from /boot/System.map-2.6.11.4-21.7. Symbols match kernel version 2.6.11. <- NOTE No module symbols loaded - kernel modules not enabled.
In my experience, it's been the same with all 2.6 kernels, not just the latest YOU update but I don't see any negative impact on any of my systems.
Correct, it only reports 2.6.x, but in the original post, it seemed that the modules that were attempting to load was from a 2.6.11.x kernel instead of the 2.6.12 kernel. I still use mkinitrd from the DVD and have experienced no problems with any 2.6.x vanilla kernels I've built. One possible problem and the one question I didn't ask was exactly what the command line was when generating the new initrd, did it align with what was in menu.lst and what initrds were in /boot. I did give an example of my script for generating initrd. The practice here is to give a new name for every kernel I build, so that I don't damage the working setup if the new kernel has a problem where I messed up or left out something, so I can reboot to something that works e.g. in /boot 2.6.12-1 (The kernel, 2.6.12 is the previous kernel, 2.6.12-1 has some experimental patches for my PhoneSkype USB phone) config-2.6.12-1 System.map-2.6.12-1 initrd2.6.12-1 menu.lst ========= title 2.6.12-1 kernel (hd0,0)/boot/2.6.12-1 root=/dev/hda1 vga=0x317 selinux=1 splash=silent resume=/dev/hda2 showopts initrd (hd0,0)/boot/initrd2.6.12-1 # grep match /var/log/boot.msg Symbols match kernel version 2.6.12. # uname -r 2.6.12-1
Another reason to download and compile your own.
I don't see a reason. Do any modules not load on your system? or do not work?
Regards, -Kastus
Donn sent me a copy of the YOU /sbin/mkinitrd and it was missing quite a bit compared to the one from the DVD install. I just did an online update and it never offered mkinitrd, udev or hotplug, so my setup is the original from the DVD install, before and after /sbin/mkinitrd is the same size, date and time. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM Mainframes and Sun Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks
Donn Washburn wrote:
From the latest SuSE Online update of the kernel. Check in /var/log/boot.msg <- It is the first 4 lines
Inspecting /boot/System.map-2.6.11.4-21.7 Loaded 27512 symbols from /boot/System.map-2.6.11.4-21.7. Symbols match kernel version 2.6.11. <- NOTE No module symbols loaded - kernel modules not enabled.
Another reason to download and compile your own.
What is it you're saying here?
On Tuesday 21 June 2005 23:32, Donn Washburn wrote:
From the latest SuSE Online update of the kernel. Check in /var/log/boot.msg <- It is the first 4 lines
Inspecting /boot/System.map-2.6.11.4-21.7 Loaded 27512 symbols from /boot/System.map-2.6.11.4-21.7. Symbols match kernel version 2.6.11. <- NOTE No module symbols loaded - kernel modules not enabled.
Another reason to download and compile your own.
-- 73 de Donn Washburn Hpage: " http://www.hal-pc.org/~n5xwb " Ham Callsign N5XWB Email: " n5xwb@hal-pc.org " 307 Savoy St. HAMs: " n5xwb@arrl.net " Sugar Land, TX 77478 BMW MOA #: 4146 - Ambassador LL# 1.281.242.3256 " http://counter.li.org " #279316
Question .. How many files did you download when you updated your kernel ..?... you did do it by hand did'nt you ..?.. Pete -- If Bill Gates had gotten LAID at High School do YOU think there would be a Microsoft ? Of course NOT ! You gotta spend a lot of time at your school Locker stuffing underware up your ass to think , I am going to take on the worlds Computer Industry -------:heard on Cyber Radio.:-------
Donn Washburn wrote:
From the latest SuSE Online update of the kernel. Check in /var/log/boot.msg <- It is the first 4 lines
Inspecting /boot/System.map-2.6.11.4-21.7 Loaded 27512 symbols from /boot/System.map-2.6.11.4-21.7. Symbols match kernel version 2.6.11. <- NOTE No module symbols loaded - kernel modules not enabled.
Another reason to download and compile your own.
So, for we amateurs in the audience who barely know a kernel from a colonel, is there a moderately detailed, fairly concise tutorial around anywhere explaining the why, the when, and the how behind this particular part of linux use? And, most importantly, how to survive if/when something goes wrong?
On Wednesday 22 June 2005 17:11, David McMillan wrote:
Donn Washburn wrote:
From the latest SuSE Online update of the kernel. Check in /var/log/boot.msg <- It is the first 4 lines
Inspecting /boot/System.map-2.6.11.4-21.7 Loaded 27512 symbols from /boot/System.map-2.6.11.4-21.7. Symbols match kernel version 2.6.11. <- NOTE No module symbols loaded - kernel modules not enabled.
Another reason to download and compile your own.
So, for we amateurs in the audience who barely know a kernel from a colonel,
Remind me not to eat any bread baked by you :)
is there a moderately detailed, fairly concise tutorial around anywhere explaining the why, the when, and the how behind this particular part of linux use? And, most importantly, how to survive if/when something goes wrong?
Try /usr/src/linux/README.SuSE But most of all, try not listening to Donn Washburn. 99.999% of all linux users will never have a need to recompile the kernel
David McMillan wrote:
Donn Washburn wrote:
From the latest SuSE Online update of the kernel. Check in /var/log/boot.msg <- It is the first 4 lines
Inspecting /boot/System.map-2.6.11.4-21.7 Loaded 27512 symbols from /boot/System.map-2.6.11.4-21.7. Symbols match kernel version 2.6.11. <- NOTE No module symbols loaded - kernel modules not enabled.
Another reason to download and compile your own.
I wasn't sure what Donn meant here.
So, for we amateurs in the audience who barely know a kernel from a colonel, is there a moderately detailed, fairly concise tutorial around anywhere explaining the why, the when, and the how behind this particular part of linux use? And, most importantly, how to survive if/when something goes wrong?
Yesterday and on many other occasions I've posted replies saying how this can be done safely. You don't really want to damage your installation when messing with a new kernel by overwriting anything in /boot, a new kernel should always be considered as an experimental kernel to support some special bit of hardware or to see if a problem you experience is resolved by it. If you have problems with the new kernel, you should be able to simply reboot your working kernel and carry on as before. The name of the new kernel, initrd, System.map, etc. in /boot should be unique, you can start off right by adding a digit or letter to the EXTRAVERSION in the kernel Makefile so your new kernel will be e.g 2.6.11.4-21-7a or whatever you fancy. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM Mainframes and Sun Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2005-06-23 at 10:49 +0100, Sid Boyce wrote:
your working kernel and carry on as before. The name of the new kernel, initrd, System.map, etc. in /boot should be unique, you can start off right by adding a digit or letter to the EXTRAVERSION in the kernel Makefile so your new kernel will be e.g 2.6.11.4-21-7a or whatever you fancy.
Use instead the variable: CONFIG_LOCALVERSION="-local" in the .config file (accesible trhough "make menuconfig", for example). I use my initials. It is the place where SuSE puts "-default", "-smp", etc. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFCuppMtTMYHG2NR9URAmHLAJ9Pz7Rmg2VsVSQ9EqIg5DIMENfXwQCfdVcA rwPARAjnqRTOQPM/MlesLjc= =eSGr -----END PGP SIGNATURE-----
participants (8)
-
Anders Johansson -
Carlos E. R. -
David McMillan -
Donn Washburn -
James Knott -
Kastus -
Peter Nikolic -
Sid Boyce