Errors now printed in the console:
eth1: transmit timed out
eth1: 21140 transmit timed out, status fc740000,
eth1: transmit timed out, switching to 100baseTx
eth1: transmit timed out
eth1: 21140 transmit timed out, status fc740000
eth1: transmit timed out, switching to MII media.
eth1: Out-of-sync dirty pointer, 4611 vs. 4628.
eth1: Setting full-duplex based on MII#1
eth1: transmit timed out
eth1: transmit timed out
On Wed, 25 Jul 2001, Horst von Brand wrote:
> "Richard B. Johnson" <root@chaos.analogic.com> said:
> > On Wed, 25 Jul 2001, TO. Wilderman Ceren wrote:
> > > I have a problem., i compile this morning the kernel 2.4.7, when i
> > > reboot and load the new compiled bzImage, the module is not loaded by
> > > insmod., errors found:
> > >
> > > /lib/modules/2.4.7/kernel/drivers/net/dmfe.o: init_module: No such
> > > device
> > > Hint: insmod errors can be caused by incorrect module parameters,
> > > including invalid IO or IRQ parameters
> > > /lib/modules/2.4.7/kernel/drivers/net/dmfe.o: insmod
> > > /lib/modules/2.4.7/kernel/drivers/net/dmfe.o failed
> > > /lib/modules/2.4.7/kernel/drivers/net/dmfe.o: insmod dmfe failed
> > >
> > [SNIPPED...]
> > In /etc/modules.conf, look at eth0 alias and/or eth1 alias. It
> > should be the name of the driver you intend to use. You don't
> > have to reboot for tests, just put the right stuff in and
> > do your `ifconfig` stuff by hand.
> >
> > Also, sometime, with your new kernel running, do `depmod -a` this
> > will update the dependencies.
>
> Here on RH 7.1 we are using the tulip module for dmfe. Works fine AFAIKT.
>
---*-*-*-*-*-*-*-*-*-*- Wilderman Ceren Tecnologo en Sistemas Este Mensaje fue enviado desde Pine ICQ: 4493959 - 37207794 MSN Messenger: wildercol
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/