Sponsored Content
Full Discussion: Device eth0 issue
Operating Systems Linux Red Hat Device eth0 issue Post 302544867 by fpmurphy on Friday 5th of August 2011 09:04:18 AM
Old 08-05-2011
It still sounds like you do not have the correct driver module for this interface.

To select the correct driver package, you should do something like the following:
(The example shows a Realtek, your output should be different)
Code:
# /sbin/lspci | grep -i net  

04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)

# /sbin/lspci -n | grep '04:00.0'

04:00.0 0200: 10ec:8168 (rev 01)

By using the Vendor & Device numbers from an ID pairing, you can check to see if your system contains an appropriate driver module for that particular device:
Code:
# grep -i 10ec /lib/modules/*/modules.alias | grep -i 8168

If this does not print out a suitable module, then ElRepo.org should be your next stop.

Search for the Vendor Device ID pairing of 10ec:8168 on the ElRepo DeviceIDs page will show that kmod-r8168 should work with this particular Ethernet controller. Then go to the download area to retrieve the appropriate binary. There are different binaries for PAE, 32bit, 64bit, etc. so make sure to select the correct one.
 

5 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Eth err: "3c501 device eth0 does not seem to be present"

HI, When I do 'service network restart' , I am getting the following error. "3c501 device eth0 does not seem to be present, delaying initialization" Can any one suggest me the cause/solution for this? When I do 'lspci' it is showing the ehternet card as " Ethernet controller"Marvell... (2 Replies)
Discussion started by: praveen_b744
2 Replies

2. AIX

How to find all device on p570 when need do device firmware upgrade?

I need upgrade firmware for the device of p570, when I go to IBM FIX download website, there are a lot of device of p570 listed. How can I know what device I have on my p570? (4 Replies)
Discussion started by: rainbow_bean
4 Replies

3. Solaris

Global device issue in sun cluster3.2

In my 2 node cluster (sun cluster3.2) running on x86 VMs. One of my nodes VM1 does not have the global devices populated due to which i cannot failover my file system to node VM1 , what could be the reason for this and how can i rectify it ? VM1:/>cd /dev/global -bash: cd: /dev/global: No... (1 Reply)
Discussion started by: fugitive
1 Replies

4. Red Hat

Unable To Activate Ethernet Network Device in RHEL 5.5 - e100 device eth0 does not seem to be presen

Hi All, Could anyone please help to resolve the below problem. I installed RHEL5.5 in my desktop.But when i try to activate the ethernet connection then it gives me the error. I spent 2 days for the above and go through with several suggestion found by googling. But no luck. ... (0 Replies)
Discussion started by: Tanmoy
0 Replies

5. HP-UX

Failed to open tape device /dev/rmt/0mn:Device busy (errno = 16)

Hi, Unable to make tape backup, please help. /opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00 * Creating local directories for configuration files and archive. ======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery. (Mon... (4 Replies)
Discussion started by: anuragr
4 Replies
ALC(4)							   BSD Kernel Interfaces Manual 						    ALC(4)

NAME
alc -- Atheros AR813x/AR815x Gigabit/Fast Ethernet driver SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file: device miibus device alc Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_alc_load="YES" DESCRIPTION
The alc device driver provides support for Atheros AR813x and AR815x PCI Express Gigabit/Fast Ethernet controllers. All LOMs supported by the alc driver have TCP/UDP/IP checksum offload for transmit, TCP segmentation offload (TSO), hardware VLAN tag strip- ping/insertion features, Wake On Lan (WOL) and an interrupt moderation mechanism as well as a 64-bit multicast hash filter. The AR813x and AR815x supports Jumbo Frames (up to 9216 and 6144 bytes, respectively), which can be configured via the interface MTU setting. Selecting an MTU larger than 1500 bytes with the ifconfig(8) utility configures the adapter to receive and transmit Jumbo Frames. The alc driver supports the following media types: autoselect Enable autoselection of the media type and options. The user can manually override the autoselected mode by adding media options to rc.conf(5). 10baseT/UTP Set 10Mbps operation. 100baseTX Set 100Mbps (Fast Ethernet) operation. 1000baseTX Set 1000baseTX operation over twisted pair. The alc driver supports the following media options: full-duplex Force full duplex operation. half-duplex Force half duplex operation. For more information on configuring this device, see ifconfig(8). HARDWARE
The alc device driver provides support for the following Ethernet controllers: o Atheros AR8131 PCI Express Gigabit Ethernet controller o Atheros AR8132 PCI Express Fast Ethernet controller o Atheros AR8151 v1.0 PCI Express Gigabit Ethernet controller o Atheros AR8151 v2.0 PCI Express Gigabit Ethernet controller o Atheros AR8152 v1.1 PCI Express Fast Ethernet controller o Atheros AR8152 v2.0 PCI Express Fast Ethernet controller LOADER TUNABLES
Tunables can be set at the loader(8) prompt before booting the kernel or stored in loader.conf(5). hw.alc.msi_disable This tunable disables MSI support on the Ethernet hardware. The default value is 0. hw.alc.msix_disable This tunable disables MSI-X support on the Ethernet hardware. The default value is 0. SYSCTL VARIABLES
The following variables are available as both sysctl(8) variables and loader(8) tunables: dev.alc.%d.int_rx_mod Maximum amount of time to delay receive interrupt processing in units of 1us. The accepted range is 0 to 130000, the default is 100(100us). Value 0 completely disables the interrupt moderation. dev.alc.%d.int_tx_mod Maximum amount of time to delay transmit interrupt processing in units of 1us. The accepted range is 0 to 130000, the default is 1000(1ms). Value 0 completely disables the interrupt moderation. dev.alc.%d.process_limit Maximum amount of Rx frames to be processed in the event loop before rescheduling a taskqueue. The accepted range is 32 to 255, the default value is 64 events. The interface does not need to be brought down and up again before a change takes effect. SEE ALSO
altq(4), arp(4), miibus(4), netintro(4), ng_ether(4), vlan(4), ifconfig(8) HISTORY
The alc driver was written by Pyun YongHyeon <yongari@FreeBSD.org>. It first appeared in FreeBSD 8.0. BSD
August 9, 2010 BSD
All times are GMT -4. The time now is 09:44 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy