Stefano Papini wrote:
thanks a lot Chris, but how to cope with different kernels? If I'm not wrong I can see one only System.map in my /boot.
Now, I deeply upgraded from 2.2.15 to 2.2.17, 2.4.0... and so on.
Now I've 2.4.1, 2.4.2, 2.4.3.
Is System.map to be set in /etc/lilo.conf????
No, the kernel picks the correct one automatically. If the kernel being loaded is called 'vmlinuz-2.4.3' is will look for a file called 'System.map-2.4.3', similarly, if the kernel is called 'vmlinuz-3sj48d', it will look for 'System.map-3sj48d'. If you copied the kernel over manually, you probably either forgot to copy the System.map file, or you copied it straight to /boot/System.map. I don't know exactly what 'make install' or 'make bzlilo' does, with respect to copying System.map. My /boot looks like this: galaxy:~ # ls /boot . System.map.2.4.3 vmlinuz.2.2.14 .. System.map.devel vmlinuz.2.2.14-2 System.map System.old vmlinuz.2.2.14-3 System.map.2.2.14 boot.0300 vmlinuz.2.2.14-4 System.map.2.2.14-2 boot.b vmlinuz.2.2.5.S System.map.2.2.14-3 chain.b vmlinuz.2.2.5.S-2 System.map.2.2.14-4 lost+found vmlinuz.2.2.5.S-orig System.map.2.2.5.S map vmlinuz.2.4.3 System.map.2.2.5.S-2 os2_d.b vmlinuz.devel System.map.2.2.5.S-orig vmlinuz vmlinuz.old This way, the kernel always gets the correct System.map.
Chris Reeves wrote:
Jerry Kreps wrote:
5) cp bzImage to /boot/vmlinuz.yourinitials 6) cp System.map to /boot/System.map
If you copy the kernel to /boot/vmlinuz.yourinitials, you really should copy System.map to /boot/System.map.yourinitials as well, this way the kernel will read to the correct System.map.
Bye, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\