I have been and I am. But, check the documentation and you'll find nothing about System.map's. So, even though you compile a new kernel and install bzImage and System.map, your new System.map is not being referenced. You have to rename it to what SuSE used: System.map-2.2.18, and this is not a logical way to do things. If I were to recompile using the 2.4 kernel I would get a new System.map and then I would have to name it System.map-2.2.18 in order for it to be used at boot. This doesn't make sense. What should happen is that a setting in lilo would allow me to tell the system which System.map to use. JLK On Tuesday 27 March 2001 23:54, Pascal MiQUET wrote:
Why didn't you configure you system like it's mentionned into SuSE documentation ? Personaly I didn't test it, but it's planned to make a try if it works for my PC. Best Pascal MiQUET
----- Original Message ----- From: "Jerry Kreps" <jerrykreps@jlkreps.net> To: "SLE" <suse-linux-e@suse.com> Sent: Wednesday, March 28, 2001 6:45 AM Subject: [SLE] System.map
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???
JLK
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq