07-21-2011
The reason I tried the e1000(e) drivers was because the bnx2x for broadcom driver is currently installed and I am getting no light activity from the ethernet controller ??
5 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
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
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
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
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
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
LEARN ABOUT CENTOS
firewire
FIREWIRE(4) BSD Kernel Interfaces Manual FIREWIRE(4)
NAME
firewire -- IEEE1394 High-performance Serial Bus
SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file:
device firewire
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
firewire_load="YES"
DESCRIPTION
FreeBSD provides machine-independent bus support and raw drivers for firewire interfaces.
The firewire driver consists of two layers: the controller and the bus layer. The controller attaches to a physical bus (like pci(4)). The
firewire bus attaches to the controller. Additional drivers can be attached to the bus.
Up to 63 devices, including the host itself, can be attached to a firewire bus. The root node is dynamically assigned with a PHY device
function. Also, the other firewire bus specific parameters, e.g., node ID, cycle master, isochronous resource manager and bus manager, are
dynamically assigned, after bus reset is initiated. On the firewire bus, every device is identified by an EUI 64 address.
FILES
/dev/fw0.0
/dev/fwmem0.0
SEE ALSO
fwe(4), fwip(4), fwohci(4), pci(4), sbp(4), eui64(5), fwcontrol(8), kldload(8), sysctl(8)
HISTORY
The firewire driver first appeared in FreeBSD 5.0.
AUTHORS
The firewire driver was written by Katsushi Kobayashi and Hidetoshi Shimokawa for the FreeBSD project.
BUGS
See fwohci(4) for security notes.
BSD
April 1, 2006 BSD