Sponsored Content
Full Discussion: Device eth0 issue
Operating Systems Linux Red Hat Device eth0 issue Post 302540622 by Duffs22 on Thursday 21st of July 2011 08:05:06 AM
Old 07-21-2011
Ok I am using RHEL 5.4 so there is no "rpmbuild / --rebuild".

I created a repo from my DVD and managed to install the necessary packages.

So I have run a "make install" on the e1000 src dir and all seem good until I try and include/add the module I get the following error:

insmod: error inserting <path_to_e1000.ko>: -1 Invalid module format

Has anybody seen this before or know what the problem might be?
 

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
IFCFG-VLAN(5)						       Network configuration						     IFCFG-VLAN(5)

NAME
ifcfg-vlan - virtual LAN interface configuration SYNOPSIS
/etc/sysconfig/network/ifcfg-vlan* Virtual LANs (802.1q) To setup a vlan interface you need a configuration file that contains at least the mandatory ETHERDEVICE variable with the real interface used for the virtual LAN. Further, it may contain the optional VLAN_ID variable that specifies the VLAN ID. By default and when the VLAN_ID variable is not set, the number at the end of the interface name is the VLAN ID. Preferably the interface name and the configuration file follow the VLAN interface name scheme (type), that is either: ifcfg-vlan<VLAN-ID> (e.g. ifcfg-vlan42) or ifcfg-name.<VLAN-ID> (e.g. ifcfg-eth0.42) The VLAN-ID can be also 0-padded (e.g. ifcfg-vlan0042 or ifcfg-eth0.0042). Also in case of custom names, trailing digits are interpreted as VLAN-ID by default (e.g. ifcfg-dmz42). When VLAN_ID is set in the config, the interface name have any name (e.g. ifcfg-foobar). Note: The drawback of custom interface names and VLAN_ID usage is, that a rename of the interface is required and that they violate the name scheme. The real interface will be set UP automatically and doesn't need a config file in case of a physical interface. But without a config file YaST will consider this interface as unused, if will not follow hotplug events and you're unable to apply any settings, e.g. ETH- TOOL_OPTIONS. To avoid that, provide an config file with at least STARTMODE='auto'. The rest of the VLAN interface IP and routes configuration do not differ from ordinary interfaces. See also man ifcfg and man routes for details. EXAMPLES
Sets up vlan3 vlan interface on top of eth0: ifcfg-vlan3 STARTMODE='auto' ETHERDEVICE='eth0' IPADDR='192.168.3.27/24' Sets up eth0.3 vlan interface on top of eth0: ifcfg-eth0.3 STARTMODE='auto' ETHERDEVICE='eth0' IPADDR='192.168.3.27/24' Sets up lan1 vlan interface with ID 42 on top of eth0: ifcfg-lan1 STARTMODE='auto' ETHERDEVICE='eth0' VLAN_ID='42' IPADDR='192.168.3.27/24' BUGS
Please report bugs at <http://www.suse.de/feedback> AUTHOR
Christian Zoz <zoz@suse.de> Michal Svec <msvec@suse.cz> Bjoern Jacke Mads Martin Joergensen <mmj@suse.de> Michal Ludvig <mludvig@suse.cz> Marius Tomaschewski <mt@suse.de> SEE ALSO
routes(5), ifcfg(5), ifup(8). sysconfig August 2004 IFCFG-VLAN(5)
All times are GMT -4. The time now is 06:28 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy