You should have a line that has the word "wd" instead of "ciss".
Did you transfer the /etc/conf directory from the old machine to the new one?
If you have to rebuild the kernel it will be built with the ciss driver instead of the wd driver.
All the kernel configuration files are in the /etc/conf directory.
Is a good place to start reading.
hi,
i m tryin to learn ldap.
but its not getting configured.
the error msg it shows is:
LDAP configure error: BDB/HDB : Berkeley DB version incompatibe.
The BDB version i have installed is bdb4.2.52 and the ldap version is openldap-2.3.12.
my machine is running on red hat linux 9.
Why... (1 Reply)
My computer which uses scoUNIX, has an internal scsi tape backup. It will
no longer backup . It posts this message Notice :Stp tape 0 device 46/0
offline. This has been discussed before by the forum and I'd appreciate any
help that any expert could provide for me for a step wise approach to... (0 Replies)
My tape drive is not backing up my data. This is the message that comes up as the computer starts up each morning. Notice Stp:SCSI tape 0 device 46/0 offline. The computer is equipped with a Seagate STD 24000N internal tape drive and the green indicator light on it continuously is on but the amber... (0 Replies)
I am having trouble understanding the difference between a passthrough device and a named device and when you would use one or the other to access equipment.
As an example, we have a tape library and giving the command
"camcontrol devlist" gives the following output:
akx# camcontrol... (1 Reply)
Hello,
I attached a tape drive to one of my partitions but i cannot find the device.
I run the command lsdev|grep rmt but i dont get anything in return.
When i run lsslot -c slot i can see the slot number and the device that belongs to the tape drive but i cannot find any rmt files in /dev.... (6 Replies)
Help Please!
I picked up a V440 and it has 4 disks. I installed Solaris fine to disk 3, but I cannot see the other disks in Solaris.
I have run probe-scsi-all from OBP and I see the other disks and they have names in devalias AFAIK. It's just in Solaris they do not appear. I have run... (6 Replies)
Hi have a solaris server with the following IP 192.168.0.85, but anybody can login in using 172.19.0.85, and the ifconfigcommand does not show the 172.19.05 .
# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask... (6 Replies)
I have kali running on vbox as :-
/etc/network/interfaces
ifup eth0 gives me
tpcdump (0 Replies)
Discussion started by: lazerz
0 Replies
LEARN ABOUT CENTOS
vx
VX(4) BSD/i386 Kernel Interfaces Manual VX(4)NAME
vx -- 3Com EtherLink III / Fast EtherLink III (3c59x) Ethernet driver
SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file:
device vx
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
if_vx_load="YES"
DESCRIPTION
The vx driver provides support for the 3Com ``Vortex'' chipset.
The medium selection can be influenced by the following link flags to the ifconfig(8) command:
link0 Use the AUI port.
link1 Use the BNC port.
link2 Use the UTP port.
HARDWARE
The vx driver supports the following cards:
o 3Com 3c590 EtherLink III PCI
o 3Com 3c592 EtherLink III EISA
o 3Com 3c595 Fast EtherLink III PCI in 10 Mbps mode
o 3Com 3c597 Fast EtherLink III EISA in 10 Mbps mode
DIAGNOSTICS
vx%d: not configured; kernel is built for only %d devices. There are not enough devices in the kernel configuration file for the number of
adapters present in the system. Add devices to the configuration file, rebuild the kernel, and reboot.
All other diagnostics indicate either a hardware problem or a bug in the driver.
CAVEATS
Some early-revision 3c590 cards are defective and suffer from many receive overruns, which cause lost packets. The author has attempted to
implement a test for it based on the information supplied by 3Com, but the test resulted mostly in spurious warnings.
The performance of this driver is somewhat limited by the fact that it uses only polled-mode I/O and does not make use of the bus-mastering
capability of the cards.
SEE ALSO arp(4), netintro(4), ng_ether(4), ifconfig(8)HISTORY
The vx device driver first appeared in FreeBSD 2.1. It was derived from the ep driver, from which it inherits most of its limitations.
AUTHORS
The vx device driver and this manual page were written by Fred Gray <fgray@rice.edu>, based on the work of Herb Peyerl and with the assis-
tance of numerous others.
BUGS
The vx driver is known not to reset the adapter correctly following a warm boot on some systems.
The vx driver has not been exhaustively tested with all the models of cards that it claims to support.
BSD July 16, 2005 BSD