10-19-2011
agree with DukeNuke2, check the third line, there is somthing wrong with your e1000g (NIC)...
10 More Discussions You Might Find Interesting
1. Solaris
Do we have any Virtual Data Center software as we have Virtual Machine?
I want to practice everything of Solaris practically but i don't have resources like data center which includes Servers, Data storages, switches, and other things. (2 Replies)
Discussion started by: karman0931
2 Replies
2. Solaris
Hi
I have two solaris 10 virtual machines on my Vista laptop.
I want to access both machines using putty in vista. I used DHCP while installing virtual machines. one machine gets the ip address and other does not. What is the problem? can i assign a static ip address if yes how?
... (2 Replies)
Discussion started by: ankurk
2 Replies
3. UNIX for Dummies Questions & Answers
Hi All
I am having a solaris 10 virtual machine on vista (using vmware 7) laptop.
Now i want to access virtual machine from vista using putty.
Problem is that i insalled the solaris machine as dhcp. and whenever i connect to internet or reboot my system the IP address of solaris... (1 Reply)
Discussion started by: ankurk
1 Replies
4. Solaris
Trying to set or modify the randomly set hostID of a Solaris 10 virtual/guest machine that I installed on a Windows-XP host machine (using Virtual Box 4.1.12).
I was able to set/modify the hostname of the Solaris 10 virtual/guest machine during installation as well as via the Virtual Box... (4 Replies)
Discussion started by: Matt_VB
4 Replies
5. Virtualization and Cloud Computing
Hi All
How would you send a solaris virtual machine in vmware esx, a break signal? :confused: (0 Replies)
Discussion started by: jakerock
0 Replies
6. Red Hat
My RHEL virtual Machine Does not have Virtual Machine Manager Desktop Tool
Hi,
I don't seem to have the Virtual Machine Manager Desktop tool set up on my RHEL6 Machine. The Linux machine runs off VMWare player and I'm not sure whether it is a VMWare software issue or a problem with the RHEL6... (2 Replies)
Discussion started by: accipiter1
2 Replies
7. Solaris
hi,
I am using command psrinfo -p to check the number of physical processors present on any soalris machine.I want to check the number of virtual processors assigned for particular solaris machine.
which command/set of command need to be used which can grep or show the total virtual processors... (8 Replies)
Discussion started by: omkar.jadhav
8 Replies
8. AIX
Hi There,
I have zero information and zero knowledge for IBM virtual machine except Amazon cloud and VMware ESXi (Only Linux OS available).
Anyone could provide me the following answer -
Can IBM VM been deploy on X86 and X64 (Intel Chip)?
If answer is yes any chance to deploy AIX OS... (13 Replies)
Discussion started by: chenyung
13 Replies
9. Solaris
Hello,
please, can somebody tell me if can i virtualize Solaris 11 SPARC architecture in a x86 PC?
Virtualbox allows doing that? i need to run Solaris 11 SPARC to make a lab, and dont have any SUN machine to do on it.
Thanks in advance! (9 Replies)
Discussion started by: MuziKizuM
9 Replies
10. UNIX for Beginners Questions & Answers
Hi All,
Is there any way I can prioritize my VMs when there is resource crunch in host machine so that some VMs will be allocated more vcpu, more memory than other VMs in kvm/qemu hypervisor based virtual machines?
Lets say in my cloud environment my Ubuntu 16 compute hosts are running some... (0 Replies)
Discussion started by: SanjayK
0 Replies
AN(4) BSD Kernel Interfaces Manual AN(4)
NAME
an -- Aironet Communications 4500/4800 wireless network adapter driver
SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file:
device an
device wlan
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
if_an_load="YES"
DESCRIPTION
The an driver provides support for Aironet Communications 4500 and 4800 wireless network adapters and variants, including the following:
o Aironet Communications 4500 and 4800 series
o Cisco Aironet 340 and 350 series
o Xircom Wireless Ethernet Adapter
Support for these devices include the ISA, PCI and PCMCIA varieties. The Aironet 4500 series adapters operate at 1 and 2Mbps while the
Aironet 4800 series and Cisco adapters can operate at 1, 2, 5.5 and 11Mbps. The ISA, PCI and PCMCIA devices are all based on the same core
PCMCIA modules and all have the same programming interface, however unlike the Lucent WaveLAN/IEEE cards, the ISA and PCI cards appear to the
host as normal ISA and PCI devices and do not require any PCCARD support.
The PCMCIA Aironet cards require PC Card support, including the kernel pccard(4) driver. ISA cards can either be configured to use ISA Plug
and Play or to use a particular I/O address and IRQ by properly setting the DIP switches on the board. (The default switch setting is for
Plug and Play.) The an driver has Plug and Play support and will work in either configuration, however when using a hard-wired I/O address
and IRQ, the driver configuration and the NIC's switch settings must agree. PCI cards require no switch settings of any kind and will be
automatically probed and attached.
All host/device interaction with the Aironet cards is via programmed I/O. The Aironet devices support 802.11 and 802.3 frames, power manage-
ment, BSS (infrastructure) and IBSS (ad-hoc) operation modes. The an driver encapsulates all IP and ARP traffic as 802.11 frames, however it
can receive either 802.11 or 802.3 frames. Transmit speed is selectable between 1Mbps, 2Mbps, 5.5Mbps, 11Mbps or "auto" (the NIC automati-
cally chooses the best speed).
By default, the an driver configures the Aironet card for infrastructure operation.
For more information on configuring this device, see ifconfig(8).
DIAGNOSTICS
an%d: init failed The Aironet card failed to become ready after an initialization command was issued.
an%d: failed to allocate %d bytes on NIC The driver was unable to allocate memory for transmit frames in the NIC's on-board RAM.
an%d: device timeout The Aironet card failed to generate an interrupt to acknowledge a transmit command.
SEE ALSO
altq(4), arp(4), miibus(4), netintro(4), wlan(4), ancontrol(8), ifconfig(8)
HISTORY
The an device driver first appeared in FreeBSD 4.0.
AUTHORS
The an driver was written by Bill Paul <wpaul@ee.columbia.edu>.
BSD July 16, 2005 BSD