Osamu Aoki gravada:
> On Thu, Oct 04, 2001 at 09:36:24PM -0300, Ricardo Gazoni wrote: > > Yes, I did. In fact, step 1 loaded /boot/config-2.2.19pre17 and saved it in > > /usr/src/kernel-source-2.2.19pre17/.config. To be precise, doing this via > > make > > xconfig only adds comment lines to the .config file. I checked it out > > carefully.... > > > > > > Everything worked just fine until now. But the old kernel image > > > > (vmlinuz-2.2.19pre17) is 1.001.473 bytes long, and the new one > > > > (vmlinuz-2.2.19foo17) is 1.033.565 bytes long. But the worst thing > > > > is that the new kernle doesn't boot. What am I doing wrong?? > > If difference is few bytes, I suppose some difference in compile > condition may have contributed. But 30KB is large. > > Just to be sure, why not recompile without using xconfig. > > Also check difference in /boot/System.map-2.2.19.... > > Also are you using right compiler version. > > Besides, recompile again and see whether result is same or not. If > different, you may have had memory corruption during compile. Good luck > :-) > -- > ~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ > + Osamu Aoki <[EMAIL PROTECTED]>, GnuPG-key: 1024D/D5DE453D + > + My debian quick-reference, http://www.aokiconsulting.com/quick/ + Compiler version seems OK. Both kernels reports gcc version 2.7.2.3. But the files /boot/System.map-2.2.19foo17 and /boot/System.map.2.2.19pre17 do differ, but I don't know what it means. I'm going to try to compile without using xconfig now, to see what happens. Thanks a lot