SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
The problem now is:
I can boot the new bzImage but I can see (also it's gone very fast)
that there're MANY problems while the kernel is loaded and my first
task would be to analyse the log...but... i don't now where or how to get it *G*
I've looked in /var/log but there several textfiles and I've no clue which one is the right one.
Hm... I can't find those errors in /var/log/messages
and dmesg isn't telling me any errors , but I think that's because right
now I'm running /boot/vmlinuz again
Gonna test more in a few hours ...right now I'm dead tired.
I remember seen that many modules where not loaded.
eth0 and all the stuff could be initialized 'cause all the modules where not loaded.
Do I have to write some custom file to include all this stuff?
I thought if I use xconfig , save & exit + do all the other stuff , it would work?
Or did I miss something - i definitely haven't writen anything like "include this and this and this module"
Ok...have to get some sleep... damn headaches are killing me
Thanks for the link tricky, but I don't seem to understand the last post:
"well, guess what my problem was... I had no problem! The reason I kept seeing 'unable to load module' was because it was still booting with the old 'rc.modules' file where I had uncommented alot of lines to load modules. The new kernel had these things loaded into it, so the 'make modules/modules_install' didn't copy the modules over, resulting in modprobe not being able to find the modules in '/lib/modules/...'"
I've recompiled the kernel again, my way to do it is the exact same way
ixion did it and I get the same problems :-/
"Nothing to do" etc @ make modules_install
I too had uncommented some stuff in rc.modules (f.ex. the emu stuff for my soundblaster etc.)
and now I've no idea what I'm doing wrong?
There don't seem to be any modules loaded?
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 816M
agpgart: Unsupported SiS chipset (device id: 0648), you might want to try agp_tr
agpgart: no supported devices found.
[drm] Initialized tdfx 1.0.0 20010216 on minor 0
[drm] Initialized radeon 1.1.1 20010405 on minor 1
[drm:drm_init] *ERROR* Cannot initialize the agpgart module.
I'd just like to jump in here and ask a question, both to you Faeroon, and the others...
When you compile a kernel, aren't you meant to copy the System.map file from the kernel source directory to the /boot dir also? Yet the guide in TLDP didn't mention it...maybe i mistaken, maybe you don't have to do this?
If so, it could possibly be whats causing your problems, Faeroon?
When you recompile the kernel and you know you selected those modules, are you selecting them as builtin or as a module ?
It will create a new modules file called rc.modules.new or something along the lines like that. Make sure you don't have any uncommented modules that you don't want to load.
If your getting that error at make modules_install, its either a way your configuring the kernel in either make xconfig or make menuconfig most likely.
If you want, when you configure your kernel, save the configuration before exiting and saving, then try to pull it back up and see if your configurations stayed how you wanted. Then move on to recompile.
And Grim Reaper, when compiling a kernel in Linux and you edit your Lilo.conf file ahead, you can use the make install command and it copies and updates Lilo for you.. quite nice really, so there is no need to manually copy whatever necessary to their new destinations.
Originally posted by Grim Reaper But does System.map have anything to do with lilo? I never thought it did...
What exactly does System.map do, seeings as it sounds like it isn't needed, but is still there on most distro's?
What I also meant to say is the make install command not only updates lilo but also moves the System.map.. and anything else for your kernel to boot properly.. sort of say. The System.map is somewhat needed though, my search on google came up with this page that explains it: http://www.dirac.org/linux/systemmap.html
Hi all, I'm new to the forum but having broken a few installs of Slackware, RedHat, SUSE, etc by screwing up kernel rebuilds so I'll throw in my learned the hard way method for rebuilding kernels.
* cd /usr/src/linux
* make mrproper (cleans out old build temp files, may not be needed. also note this deletes any previous .config file, see below)
* can copy previous config from /boot as a base template... cp /boot/config-2.4.xx-new .config
* make menuconfig (or make config or make xconfig)
* pick all the appropriate options, but take note:
-remember which of your system drivers you are adding into the kernel and which ones you are modularizing; A good trick is to open /etc/rc.d/rc.modules in a different terminal window and remark/unremark appropriate modules as you go through the config. ie I modularize my sound card driver so uncomment it in rc.modules but build my scsi driver into the kernel so comment out the line for it in rc.modules.
* make dep
* make clean (can do these together, they are fairly short... root@scoob:/usr/src/linux# make dep ; make clean)
* make bzImage (Usually the longest part of the process)
* make zImage instead of bzImage if you can pull off a small kernel
* make modules
-note: can do any command below except make modules_install in a second terminal while make modules is running
* mv /lib/modules/2.4.xx /lib/modules/2.4.xx-old (this moves the old modules out of the way so make modules_install doesn't overwrite them)
* make modules_install (this basically copies the new modules to /lib/modules/2.4.xx)
* cp arch/i386/boot/zImage /boot/vmlinuz-2.2.xx-new
* edit /etc/lilo.conf (it's a good idea to copy your original image= section and rename it to something like original so you can boot the old kernel)
*mv System.map /boot/System.map-2.4.xx-new
*delete or rename the symbolic link System.map and make a new one ln -s /boot/System.map-2.4.xx-new /boot/System.map
*cp .config /boot/config-2.4.xx-new
*delete or rename the symbolic link config and make a new one ln -s /boot/config-2.4.xx-new /boot/config
* reboot (no need to do it immediately but the new kernel won't be loaded until you reboot)
This does a few things, first off the System.map from the new build is now in /boot where the kernel can find it rather than the old one. Second, you have a saved copy of your .config as /boot/config-2.4.xx-new and can copy it back as a template if you need to modify your kernel build, see the third step above. By moving the old modules out of the way, you can trim your system by deleting these once you are satisfied with the new kernel.
Things to look out for:
-This isn't the definitive guide to compiling your kernel! Do reference any appropriate man pages, HOWTOs, etc while doing this.
-on Slackware, your network card module may be loaded in /etc/rc.d/rc.netdevice instead of /etc/rc.d/rc.modules
-by moving your old modules out of the way you can hose your system if you forgot an important module like your hard drive driver in the new kernel.
-editing the rc. startup files can really mess up your system if you don't CAREFULLY follow syntax.
I've also had problems where errors fly by on screen during boot and you can't find them in system logs and there is probably a proper way to get the sysytem to log them but a dirty trick that I use is to open up the startup files like rc.M and add some pauses like this:
echo "press ENTER to continue -myname"
This way, during boot I will see the message and have to hit enter to continue booting. When I'm done I open up the files again and use a search for myname to delete these pauses.