ETH0 Failure

[Lunt, Nick]

Hi,

you will need to tell the list the make of your NIC eth0 and possibly the make of the motherboard.
Also any error messages you are seeing.

Nick .


> -----Original Message-----
> From: Cesar Covarrubias [mailto:cesar at uci.edu]
> Sent: 25 October 2005 06:35
> To: 'General Red Hat Linux discussion list'
> Subject: ETH0 Failure
> 
> 
> Hello All,
> 
>  
> 
> I just installed RHEL 4 from the install discs. When I reboot, eth0
> initialization fails. I can't figure out what may be causing 
> this, or how to
> resolve it. I wanted to know if anyone has had experience 
> with this. If so,
> how did you fix it?
> 
>  
> 
> Very Respectfully, 
> 
> Cesar Covarrubias
> 
>  
> 
> -- 
> redhat-list mailing list
> unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/redhat-list
> 


Wesleyan Administration Services Ltd registered number 5188850 and Wesleyan Unit Trust Managers Ltd registered number 2114859 ("WUTM Ltd")
are wholly owned subsidiary companies of Wesleyan Assurance Society, whose registered number is ZC145.
WUTM Ltd is a member of IMA. For ISA/PEP/Unit Trusts Administration Centre: PO Box Basildon SS15 5WQ Telephone: 0870 601 6129
Wesleyan Assurance Society and WUTM Ltd are authorised and regulated by the Financial Services Authority.
Head Office, Colmore Circus, Birmingham B4 6AR. Telephone: 0121 200 3003 Fax 0121 200 2971.
Website: www.wesleyan.co.uk Telephone calls may be recorded for monitoring and training purposes.

CONFIDENTIALITY NOTICE

This communication and the information it contains is intended for the person or organisation to whom it is addressed. Its contents are confidential and may be protected in law. Unauthorised use, copying or disclosure of any of it may be unlawful. If you are not the intended recipient, please contact us immediately.

The contents of any attachments in this e-mail may contain software viruses, which could damage your own computer system. While every reasonable precaution to minimise this risk has been taken, we cannot accept liability for any damage that you sustain as a result of software viruses. You should carry out your own virus checking procedure before opening any attachment.