05-25-2015
Did you restart the network service? The driver doesn't do everything by itself.
This User Gave Thanks to Corona688 For This Post:
10 More Discussions You Might Find Interesting
1. AIX
I have an LPAR in a P5 machine which has been setup in an HACMP cluster. The person who set it up allocated the wrong network adapter (en) to the persistent network. For the life of me I cannot find where I can re-assign this adapter. Anyone able to help me as I am tearing my hair out and do not... (1 Reply)
Discussion started by: johnf
1 Replies
2. AIX
hello
i've need to change network adapter on machine H80 aix 4.3.3 hacmp ( ent0 )
what i need to do after the new adapter installed on the machine?
thanks
best regards
ariec (1 Reply)
Discussion started by: ariec
1 Replies
3. AIX
When I configure two VIO Servers, VIOS1 used to ping its gateway, after I configured second VIOS2, VIOS1 cannpt ping its gateway, when I run this command:
entstat -all ent#|grep -i priority
Priority: 5 Active: False
How to make Active to True? (1 Reply)
Discussion started by: rainbow_bean
1 Replies
4. UNIX for Dummies Questions & Answers
Hi All,
I am new here - this is my first post.
I have installed Solaris 10 5/09 on my Dell M6300. The install went well, but the Dell's onboard network card is the Broadcom BCM5756ME Gigabit Ethernet - and sadly no Solaris driver exists for it. The Solaris 10 install just jumped by the... (1 Reply)
Discussion started by: soulmerchant
1 Replies
5. IP Networking
Hi All,
Sorry if this is not the correct forum to answer.
But hope somebody can help me...
For these two types of network adapter:
Intel(R) PRO/1000 MT Server Adapter
Intel(R) PRO/1000 MT Dual Port Network Adapter
How many IP addresses can be configured on it at the same time?
System... (3 Replies)
Discussion started by: wilsonSurya
3 Replies
6. IP Networking
i have wireless usb adapter rtl8187 from micromax company
my proplem is the signal is very weak and i cannot open website
can i increase the signal ?
iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wmaster0 no wireless extensions.
wlan0... (5 Replies)
Discussion started by: rsd220
5 Replies
7. UNIX for Dummies Questions & Answers
Hi All
I P2Vd a Unixware 7.1.4 box with VMWare Vsphere. I try to add a network adapter under Network Configuration Manager and it comes up with the error attached.
I've added a virtual adapter using the "E1000" option. It detects both the AMD PCI NET and E1000 virtual adapters under Network... (8 Replies)
Discussion started by: flashinwrx
8 Replies
8. UNIX for Dummies Questions & Answers
Hi all, I got sort of a task to do. I have to write in C "simulated network driver". What does it mean?
- It has to run on all network adapters
- It has to be as simple as it can be
- It has to run on all linux distributions (or at least most of them)
- It does not have to run a network... (4 Replies)
Discussion started by: Chrisdot
4 Replies
9. Hardware
How do I configure my wireless adapter to access the internet? I am running PCLinuxOS 2010. (0 Replies)
Discussion started by: ryan352333
0 Replies
10. SCO
hi .I've installed an operating system SCO in HP Z400 and network cards ZyXEL model FN312 with Chipset RTL8139D put it on .network card installed but do not display network card with command ifconfig -a in list and just show loopback.
show message :
dlpid:unable to open network adapter driver... (14 Replies)
Discussion started by: moein.mojtaba
14 Replies
HY(4) Kernel Interfaces Manual HY(4)
NAME
hy - Network Systems Hyperchannel interface
SYNOPSIS
/sys/conf/SYSTEM:
NHY hy_controllers # Hyperchannel
DESCRIPTION
The hy interface provides access to a Network Systems Corporation Hyperchannel Adapter.
The network to which the interface is attached is specified at boot time with an SIOCSIFADDR ioctl. The host's address is discovered by
reading the adapter status register. The interface will not transmit or receive packets until the network number is known.
DIAGNOSTICS
hy%d: unit number 0x%x port %d type %x microcode level 0x%x. Identifies the device during autoconfiguration.
hy%d: can't handle af%d. The interface was handed a message with addresses formatted in an unsuitable address family; the packet was
dropped.
hy%d: can't initialize. The interface was unable to allocate UNIBUS resources. This is usually due to having too many network devices on
an 11/750 where there are only 3 buffered data paths.
hy%d: NEX - Non Existent Memory. Non existent memory error returned from hardware.
hy%d: BAR overflow. Bus address register overflow error returned from hardware.
hy%d: Power Off bit set, trying to reset. Adapter has lost power, driver will reset the bit and see if power is still out in the adapter.
hy%d: Power Off Error, network shutdown. Power was really off in the adapter, network connections are dropped. Software does not shut
down the network unless power has been off for a while.
hy%d: RECVD MP > MPSIZE (%d). A message proper was received that is too big. Probable a driver bug. Shouldn't happen.
hy%d: xmit error - len > hy_olen [%d > %d]. Probable driver error. Shouldn't happen.
hy%d: DRIVER BUG - INVALID STATE %d. The driver state machine reached a non-existent state. Definite driver bug.
hy%d: watchdog timer expired. A command in the adapter has taken too long to complete. Driver will abort and retry the command.
hy%d: adapter power restored. Software was able to reset the power off bit, indicating that the power has been restored.
SEE ALSO
intro(4N), inet(4F)
BUGS
If the adapter does not respond to the status command issued during autoconfigure, the adapter is assumed down. A reboot is required to
recognize it.
The adapter power fail interrupt seems to occur sporadically when power has, in fact, not failed. The driver will believe that power has
failed only if it can not reset the power fail latch after a ``reasonable'' time interval. These seem to appear about 2-4 times a day on
some machines. There seems to be no correlation with adapter rev level, number of ports used etc. and whether a machine will get these
``bogus powerfails''. They don't seem to cause any real problems so they have been ignored.
3rd Berkeley Distribution August 20, 1987 HY(4)