Re: Seawolf-list digest, Vol 1 #1691 - 1 msg

Thanx james for ur suggestions
   It was a hardware failure with fault in ethernet card,
Replacing card has fixed the error
Regards,
Hemal


On Fri, 11 Apr 2003 [email protected] wrote :
>Send Seawolf-list mailing list submissions to
> 	[email protected]
>
>To subscribe or unsubscribe via the World Wide Web, visit
> 	https://listman.redhat.com/mailman/listinfo/seawolf-list
>or, via email, send a message with subject or body 'help' to
> 	[email protected]
>
>You can reach the person managing the list at
> 	[email protected]
>
>When replying, please edit your Subject line so it is more 
>specific
>than "Re: Contents of Seawolf-list digest..."
>
>
>Today's Topics:
>
>    1. Re:network error : insmod eth0 failed (James P. Roberts)
>
>--__--__--
>
>Message: 1
> From: "James P. Roberts" <[email protected]>
>To: <[email protected]>
>Subject: Re: network error : insmod eth0 failed
>Date: Thu, 10 Apr 2003 13:10:25 -0400
>Organization: Punster Productions, Inc.
>Reply-To: [email protected]
>
> > Hi all,
> > I am using RedHat 7.1 & not able to access local network
> > i have configured network properly using netconfig & netcfg.
> > but it seems that after using fsck -c -y option, this problem 
>is
> > started.
> > please can any one suggest how to fix this error.
>
>Did fsck find errors?
>
> >
> > I am getting following log messages :
> >
> > file name : /var/log/messages
> >
> > kernel: eth0: trigger_send() called with the transmitter 
>busy.
> > Kernel: eth0: mismatched read page pointers 4c vs 57.
> > kernel: eth0: trigger_send() called with the transmitter 
>busy.
> > kernel: eth0: mismatched read page pointers 4c vs 59.
> > kernel: eth0: trigger_send() called with the transmitter 
>busy.
> > kernel: eth0: mismatched read page pointers 4c vs 77.
> > kernel: eth0: trigger_send() called with the transmitter 
>busy.
>
>This sounds like the ethernet card is hung up (wild guess)...  
>have you tried
>re-booting, including a power off-on cycle?  Another possibility 
>is a hardware
>failure.  If all else fails, try installing a new ethernet card.  
>But try and
>get the existing one to work first.
>
> >
> >   kernel: ne2k-pci: no I/O resource at PCI BAR #0
> >   insmod: 
>/lib/modules/2.4.2-2/kernel/drivers/net/ne2k-pci.o:
> > init_module:No such device
> >
> >    insmod: Hint: insmod errors can be caused by incorrect 
>module
> > parameters,including invalid IO or
> >    IRQ parameters
> >
> >   insmod: 
>/lib/modules/2.4.2-2/kernel/drivers/net/ne2k-pci.o:
> > insmod eth0 failed
>
>Check the documentation for this network card driver 
>(ne2k-pci.o).  You might
>need to specify IO or IRQ params, to match what the card is 
>expecting.  Did it
>work previously, and stopped working after the fsck?  If so, the 
>params you
>already have (if any) are probably ok.  If not, this is probably 
>the thing to
>research.
>
>Also, are you sure this is the correct driver for the ethernet 
>card you
>actually have?  Probably it is, but I would be incomplete if I 
>didn't mention
>it.
>
> >
> > file name : /var/log/boot.log
> >
> >   ifup: Delaying eth0 initialization.
> >   network: Bringing up interface eth0:  failed
>
>I guess that answers my question about the reboot, huh?  It is 
>important to
>shut-down gracefully ("shutdown -h now" or "reboot" at the 
>command line),
>rather than using the power or reset buttons on the computer, so 
>that the file
>system does not get messed up (thus requiring fsck on boot).  You 
>probably
>already knew that; but again, I hate to be incomplete.
>
> >
> > Thanks,
> >
> >
> >
> > Hemal Mehta
>
>Regards,
>Jim
>
>
>
>
>
>--__--__--
>
>_______________________________________________
>Seawolf-list mailing list
>[email protected]
>https://listman.redhat.com/mailman/listinfo/seawolf-list
>
>
>End of Seawolf-list Digest


Hemal Mehta
_______________________________________________________________________
Odomos - the only  mosquito protection outside 4 walls -
Click here to know more!
http://r.rediff.com/r?http://clients.rediff.com/odomos/Odomos.htm&&odomos&&wn