🚀 go-pugleaf

Brian K. Justice <bjustice@fallschurch.esys.com> wrote in article
<3326DAF8.31741765@fallschurch.esys.com>...
> David Lerner wrote:
> > 
> > In article <Pine.LNX.3.95.970306120944.127A-100000@wauug.erols.com>,
> > Joe Tseng <jtseng@wauug.erols.com> wrote:
> > > Yesterday I upgraded my RH4 system to RH41 and something went very
wrong.
> > > Suddently I could not access the network.  I found out today that
there
> > > was not even a /dev/eth0 listing.  I do have an old boot log saved in
my
> > > mail folder and this is what I've got:
> > >
> > > eth0: DE434/5 at 0x6000 (PCI bus 0, device 11)
> > > hw address 00:00:c0:01:9f:0e,
> > > requires IRQ11 (provided by PCI BIOS)
> > > de4x5.c:v0.44
> > > eth0:media is TP
> > > IP addr is 0x100007f
> > >
> > > Right now the computer says it's suspending initialization of eth0.
> > >
> > > 1. How can I turn on eth0?

I had a similar experience with RH 4.0 and upgraded kernels.  Messages
saying that "initialization deferred", it turned out to be the initrd stuff
in lilo.conf.  I just re-compiled the kernel with my scsi adapter built-in
instead of a module.  Not sure if this could be a problem with your
ethernet, but you might want to check out mkinitrd.

k