Jerry Kreps wrote:
I've been recompiling my 2.2.18 kernel several times during the last couple of days in order to get my IDE PleXWriter 8423Ti to burn a CD. That's another story that's is not sucessful yet.
However, after each kernel compile I'd copy the bzImage and the System.map to /boot and refire lilo. While searching the logs for msgs about the PleXWriter under ide-scsi emulation I noticed that during booting System.map-2.2.18 was always being loaded despite my copying System.map from /usr/src/linux after each compile.
I've noticed that lilo.conf doesn't contain any mention of the system.map. So, how does one tell the kernel which System.map to use, especially if two different kernels create two different System.maps???
I agree this whole thing with the System.map file and the /usr/modules/* is quite a pain. But in my limited experience with it I have found that if your kernel is in /boot/vmlinuz then /boot/System.map and /lib/modules/"uname -r" will be used. If your kernel is in /boot/vmlinuz-2.2.18 then /boot/System.map-2.2.18 and /lib/modules/"uname -r" will be used. This is how it SEEMS to work here for me. Of coarse you have to copy these files to the correct names from your source tree . I don't know EXACTLY how the System.map file is determined. There have been many posted questions regarding this and never a DEFINATE answer as to how it all works. The only real problem I have with it all is with the /lib/modules/"uname -r" thing. When every I stray from the SuSE kernels/naming scheme I always have to load modules via boot.local because they won't load automatically via kmod??? It's not that the kernel doesn't where to load them from it's just that it doesn't even try. Maybe someone that REALLY knows how this all works can either tell us or point us to the doc???? Lenz??? regards Mark