On Sun, May 08, 2005 at 03:10:50PM +0530, Deboo Geek wrote:
>
> 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.
You need a /sys mount point, but the cont
Deboo Geek wrote:
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 an
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 me
> 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 di
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 un
Deboo Geek wrote:
DOes a kernel compiled on one system not work for
others?
Well, maybe it's complaining because hardware that was present on the
older machine (and therefore has drivers compiled in or as modules)
doesn't exist on the newer machine, and vice versa?
--
To UNSUBSCRIBE, email to [
6 matches
Mail list logo
