On 5/8/05, Nacho <[EMAIL PROTECTED]> wrote: > > On Fri, May 06, 2005 at 05:32:56PM +0530, Deboo Geek wrote: > > > Why does it happen that when a working (modular) kernel which is > > > working fine on one system (a P - III), when copied to another system > > > (a P4), boots but gives hundreds of messages a bout modules. I did > > > copy the modules directory under the same subdirectory as it si on the > > > other system. DOes a kernel compiled on one system not work for > > > others? The only difference I can see is that the older system, the P > > > - III has debian on it while the newer one has Fedora Core 2. > > Apart from the reasons why it gives that errors (that other people already > talked about), what you can do is just move the .config file of the kernel > source directory to the Fedora machine, and then compile the kernel there, > this is more flexible I think, because you can change some little details > that > may differ from one server to another... also as it's a fast machine I > think > your kernel will get compiled in a few minutes. > > Best regards: > > Nacho
Thanks everyone, I think I found out the problem. There's a /sys directory ( I think it's a 2.6 thing) and I need to copy that too in addition to the modules dir. Correct me if I'm wrong. Otherwise I'll compile on the new macine but I compiled on this machine only to save time and get the kernel with support for moost things. BTW< is there a kernel image like the 2.4-bf4, a generic one with most of the things as modules, for 2..6? Deboo -- Please don't Cc: me, I'm subscribed to the list.
