Sponsored Content
Full Discussion: Device eth0 issue
Operating Systems Linux Red Hat Device eth0 issue Post 302540333 by Duffs22 on Wednesday 20th of July 2011 12:42:19 PM
Old 07-20-2011
I have located the following driver but not I think I may not be running the correct rpm command for install it:

# rpm -iv hp-e1000-8.0.25-1.src.rpm

error: cannot create %sourcedir /usr/src/redhat/SOURCES

Any idea on how I can install a .src rpm package?

---------- Post updated at 11:42 AM ---------- Previous update was at 09:42 AM ----------

Ok, I have just created the dir that was appently missing and have ran a "make install" against the src rpm and it has requested additional kernel-devel packages.

I have mounted my install DVD and located these rpm's but it will not install, giving the error that it is not an RPM package. Is there any way to install these packages from the install DVD or should I try and source them elsewhere?

R,
D.
 

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
aoe-interfaces(8)					      System Manager's Manual						 aoe-interfaces(8)

NAME
aoe-interfaces - restrict aoe driver to specified network interfaces SYNOPSIS
aoe-interfaces [dev1] [dev2 ...] aoe-interfaces -c DESCRIPTION
The aoe-interfaces command tells the aoe driver to ignore ATA over Ethernet (AoE) traffic on all but the specified network interfaces. It is analogous to the aoe_iflist module load option. If neither the aoe_iflist module load option nor the aoe-interfaces command are used, the aoe driver will use any network interface for AoE traffic. Using aoe-interfaces to limit AoE to only trusted networks prevents the case where a rogue AoE target appears on a public net- work, diverting data from the legitimate AoE target. Such an imposter target effectively corrupts the data on the legitimate target. If the aoe driver is a module, then calling aoe-interfaces without arguments will display the current interfaces list. If it hasn't been set then the output will be blank. It's good to run the aoe-discover command after setting the AoE interfaces list. OPTIONS
-c The -c flag will clear the interface access list, permitting any interface to be used. EXAMPLE
In this example, the root user on a host named nai loads the aoe module with only eth0 allowable for AoE traffic. After remembering that shelf 7 is on eth3, this sysadmin uses aoe-interfaces to add eth3 to the list of allowable network interfaces and then calls aoe-discover to ask the aoe driver to look for new AoE devices. nai:~# modprobe aoe aoe_iflist="eth0" nai:~# aoe-stat e10.9 eth0 up nai:~# aoe-interfaces eth0 eth3 nai:~# aoe-discover nai:~# aoe-stat e7.0 eth3 up e7.1 eth3 up e7.2 eth3 up e7.3 eth3 up e7.4 eth3 up e7.5 eth3 up e7.6 eth3 up e7.7 eth3 up e7.8 eth3 up e7.9 eth3 up e10.9 eth0 up nai:~# aoe-interfaces eth0 eth3 SEE ALSO
aoe-discover(8), aoe-stat(8), aoetools(8). AUTHOR
Ed L. Cashin (ecashin@coraid.com) aoe-interfaces(8)
All times are GMT -4. The time now is 07:39 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy