[aclug-L] Re: NIC gone

[Jonathan Hall <jonhall@xxxxxxxxxxxx>]

You'll need ne2k-pci.o, then, instead of ne.o


On Sun, Feb 06, 2000 at 02:17:37PM -0600, Wayne White wrote:
> PCI, I think
> 
> At 01:16 PM 02/06/2000 -0600, you wrote:
> >Is it ISA or PCI?
> >
> >
> >On Sun, Feb 06, 2000 at 12:27:34PM -0600, Wayne White wrote:
> >> At 12:15 PM 02/06/2000 -0600, you wrote:
> >> >What kind of network card do you have?
> >> 
> >> It is a linksys 10baseT card. It has worked well in this box with
> Mandrake6.1
> >> prior to installing Open Linux and worked with Open Linux 3.2, until the
> >> first 
> >> reboot. I am using an identical card in another box under RedHat.
> >> 
> >> >
> >> >
> >> >On Sun, Feb 06, 2000 at 11:51:46AM -0600, Wayne White wrote:
> >> >> At 10:31 AM 02/06/2000 -0600, you wrote:
> >> >> >You probably just need to run insmod or modprobe to insert the
> appropriate
> >> >> >module for the NIC.  You can make this happen every time you boot by
> >> editing
> >> >> >/etc/modules (that's what it is in Debian, at least, it's probably
> similar
> >> >> >in Caldera).  Simply put the name of the module on a line by itself in
> >> that
> >> >> >file.  For instance, for an NE2000 or compatible:
> >> >> >
> >> >> >
> >> >> >ne
> >> >> >
> >> >> >
> >> >> >Should do it... :-)
> >> >> >
> >> >> >
> >> >> 
> >> >> Well, I wish it had. I added ne to /etc/modules/default, which
> appears to 
> >> >> be the appropriate file in Caldera. No luck. 
> >> >> 
> >> >> Likewise, insmod and modprobe don't help either. When I run modprobe
> -l it
> >> >> doesn't list any modules. insmod ne returns the message that there is
> no 
> >> >> module by that name. I don't understand how it can work when
> installed,but
> >> >> not be there after a reboot. It seems that the module would either
> have to
> >> >> be there or in the kernel for it to work at all. 
> >> >> 
> >> >> Maybe I'll try recompiling the kernel.
> >> >> 
> >> >> Any other ideas?
> >> >> 
> >> >> Thanx,
> >> >> 
> >> >> Wayne
> >> >> 
> >> >> >On Sun, Feb 06, 2000 at 10:24:06AM -0600, Wayne White wrote:
> >> >> >> Yesterday I installed Open Linux 2.3 on a spare machine. It installed
> >> fine
> >> >> >> and all was right with the world. This morning I shut it down do
> >> rearrange
> >> >> >> some cables. When it booted back up it couldn't initialize the eth0.
> >> I get
> >> >> >> the following two messages. "eth) unknown interface  no such
> device" and
> >> >> >> "eth0 initialization failed." Yesterday eth0 worked fine. The
> lights on
> >> >> >> both the NIC and my hub are on. The network cable is in place. I
> find no
> >> >> >> eth0 in the /dev directory, although I'm not sure that I should. 
> >> >> >> 
> >> >> >> I suspect that there was some temporary file left from the install
> that
> >> >> >> allowed the machine to see eth0 until the first reboot. That makes me
> >> think
> >> >> >> that there is probably a file somewhere that can be edited to make
> the
> >> >> >> machine recognize its eth0 again. Is that the case? I don't find any
> >> >> >> configuration utility in Open Linux that would make a change so that
> >> eth0
> >> >> >> would once again be seen. The machine seems to want to initialize
> >> eth0 but
> >> >> >> just can't find it. How would I tell it where to look?
> >> >> >> 
> >> >> >> This is all based on a novice's assumptions, so if I'm wrong about
> this
> >> >> >> stuff set me straight. I would appreciate any help I could get with
> >> this. I
> >> >> >> wanted to fool around with OL for a while, but need the network
> >> connection
> >> >> >> to work.
> >> >> >> 
> >> >> >> TIA,
> >> >> >> 
> >> >> >> Wayne
> >> >> >
> >> >> >--
> >> >> >"The wireless music box has no imaginable commercial value. Who
> would pay
> >> >> >for a message sent to nobody in particular?" -- David Sarnoff's
> associates
> >> >> >in response to his urgings for investment in the radio in the 1920s.
> >> >> >--
> >> >> >- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> >> >> >  Jonathan Hall  *  jonhall@xxxxxxxxxxxx  *  PGP public key available
> >> >> > Systems Admin, Future Internet Services; Goessel, KS * (316) 367-2487
> >> >> >         http://www.futureks.net  *  PGP Key ID: FE 00 FD 51
> >> >> >                  -=  Running Debian GNU/Linux  =-
> >> >> >- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> >> >> >
> >> >> >
> >> >
> >> >--
> >> >Floppy disk tip #3: Do not fold diskettes unless they do not fit into the
> >> >drive. "Big" Diskettes may be folded and used in "Little" drives.
> >> >--
> >> >- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> >> >  Jonathan Hall  *  jonhall@xxxxxxxxxxxx  *  PGP public key available
> >> > Systems Admin, Future Internet Services; Goessel, KS * (316) 367-2487
> >> >         http://www.futureks.net  *  PGP Key ID: FE 00 FD 51
> >> >                  -=  Running Debian GNU/Linux  =-
> >> >- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> >> >
> >> >
> >
> >--
> >Useless fact #4: The average person's left hand does 56% of the typing.
> >--
> >- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> >  Jonathan Hall  *  jonhall@xxxxxxxxxxxx  *  PGP public key available
> > Systems Admin, Future Internet Services; Goessel, KS * (316) 367-2487
> >         http://www.futureks.net  *  PGP Key ID: FE 00 FD 51
> >                  -=  Running Debian GNU/Linux  =-
> >- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> >
> >

--
Famous last words: "Why yes--a bulletproof vest." -- James Rodges, murderer,
on his final request before the firing squad
--
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  Jonathan Hall  *  jonhall@xxxxxxxxxxxx  *  PGP public key available
 Systems Admin, Future Internet Services; Goessel, KS * (316) 367-2487
         http://www.futureks.net  *  PGP Key ID: FE 00 FD 51
                  -=  Running Debian GNU/Linux  =-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -