- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: eth0 problem
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2007 07:33 PM
03-14-2007 07:33 PM
I am using a RHEL AS 3, NIC card intel Gigabyte.During install OS did not get NIC. no message on 'dmesg' command and no device eth0 message on 'ifconfig eth0' command. if i do 'network service restart' it shows like: 3c501 device eth0 does not seem to be present,delaying initialization.
please help me . guide me step by step command.
Thanks
Shahid
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2007 08:26 PM
03-14-2007 08:26 PM
Re: eth0 problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2007 08:44 PM
03-14-2007 08:44 PM
SolutionPlease run "cat /etc/modules.conf" and copy the result here. There should be a line like "alias eth0
If
If you don't know the name of the correct driver module, please run "lspci" and show us the output, so we can figure out the correct driver module.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2007 09:24 PM
03-14-2007 09:24 PM
Re: eth0 problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2007 09:34 PM
03-14-2007 09:34 PM
Re: eth0 problem
o/p result is here
#cat /etc/modules.conf
Alias eth0 3c501
#lspci
00:19.0 Ethernet Controller: IntelCorporation: Unknow device 104a(rev 02)
#depmod -a
#
Please help me. How to i install driver ?
Regards
shahid
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2007 09:39 PM
03-14-2007 09:39 PM
Re: eth0 problem
If it's not update 8, I suggest to upgrade.
As for NIC driver - you can try add
modprobe e1000
but I guess that it won't work...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-15-2007 03:15 AM
03-15-2007 03:15 AM
Re: eth0 problem
To confirm that the "e1000" module is available, run:
modinfo e1000
If it responds:
modinfo: e1000: no module by that name found
then the e1000 module is not available. The easiest way to fix this might be to re-install with a newer Update level of RHEL AS 3 (i.e. RHEL AS 3 Update 8). The CD images are available from https://rhn.redhat.com - you'll need to register to Red Hat Network to access it.
If it responds with several lines, starting with something like this:
filename: /lib/modules/2.4.18-18.7.xsmp/kernel/drivers/net/e1000/e1000.o
description: "Intel(R) PRO/1000 Network Driver"
author: "Intel Corporation,
license: "Dual BSD/GPL"
[...]
then the e1000 module is available and you'll only need to change /etc/modules.conf to say "e1000" instead of "3c501". There are many ways to do that... here's one:
First, backup the /etc/modules.conf file:
cp /etc/modules.conf /etc/modules.conf.backup
Edit the modules.conf file:
vi /etc/modules.conf
Verify the file is OK:
cat /etc/modules.conf
(If something went wrong, "mv /etc/modules.conf.backup /etc/modules.conf" to undo your changes.)
Make the change effective immediately, so you don't need to reboot:
depmod -a
Make sure the wrong module is not loaded:
rmmod 3c501
(this might respond with "rmmod: module 3c501 is not loaded". That's OK.)
Restart networking:
service network restart