Hi, Ray:

 Thanks.  I'll bet I get a lot further this evening when I get
home and try your suggestions. :-)

A thought to the module programmers:
I wonder why, if ne.o needs 8390.o, it doesn't just
go do it its own self!

 Kernel install.
I'm vague on that part because I'm vague on kernel installing.
Since my newly created 'zdisk' runs, I'll try 'make install' & 'lilo'
this evening when I get home.
;-)

I think I found the part of rc.inet1 where I was attempting to
isapnp install the NIC. I commented the lines and now the complaint
does not show. :-)

 Is is output of the screen messages sent to 'dmesg' or where?
I would make that data available, if I knew how.
I'm sure that the 'Unresolved Symbols' are a bunch of modules (*.o).
It seems to me that there is a 'depmod -a' or similar command
that is supposed to eliminate those messages.

Ray Olszewski wrote:
> 
> Charles --
> 
> Some of what you post here is too vague to troubleshoot. I'll answer what I can.
> 
> You write:
> 
> >If I:
> >insmod ne
> >/lib/modules/2.2.13/net/ne.o: unresolved symbol ei_open
> >" ethdev_init
> >" and about 4 more lines
> 
> ne.o requires that 8390.o be installed first. So either do that with insmod
> or use modprobe to install ne.o (it takescare of dependencies for you).
> 
> Now, you also write:
> 
> > I've compiled a kernel with lots of modules except my boot media.
> >I have 'make dep clean zImage zdisk modules modules_install'
> >seemingly withour error.
> >
> > I see lots of 'unresolved sysbols' when booting.
> 
> It would help if *I* could see them too. But it sounds like you never
> actually install the zImage you create; at least you don't mention doing so.
> But the modules_install step may be causing the new modules to overwrite the
> old ones (depends on what kernel version you are using). Either install the
> new kernel hy hand or (if your kernel Makefile supports it) do a "make
> install" step. Be sure to run lilo after you do this.
> 
> You write:
> 
> >If I:
> >ifconfig eth0
> >eth0: error fetching interface information: Device not found.
> >
> 
> Probably because the module fails, so eth0 doesn't exist.
> 
<snip>

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs

Reply via email to