04-03-2003
That script is rather brute force and it doesn't really answer the question. Cassy want to autonegotiate.
Cassy, that error message means that the hme driver is not loaded into the kernel. Hopefully, this is because you don't have an hme card. To find out what you do have, use:
netstat -in
and look at the first column, which is "Name". Ignore the lo0 interface, that is a loopback that enables the box to send tcp/ip to itself. Any other lines are actual interfaces. If you actually have a "hme0" or "hme1" or something, I'm going to very confused given that error message.
I guess I'll assume that you have a "qfe0". (Note that if you have a "le0", you have a very old card that can only do 10/half-duplex.)
To see the speed on qfe0, do:
ndd -set /dev/qfe instance 0
ndd -get /dev/qfe link_speed
With qfe a "1" means 100 and a "0" means 10. But each driver is a little different, this may not hold true for other cards.
Also,
ndd -get /dev/qfe \?
will show all the parameters in the qfe driver.
One of them is "adv_autoneg_cap". This controls whether or not the card is advertising autonegotiate.
Another is "lp_autoneg_cap". This is read-only but it shows you if your link partner has advertised autonegotiate.
4 More Discussions You Might Find Interesting
1. Solaris
I have compiled my application on Solaris 10 with following description
SunOS ldg1 5.10 Generic_138888-03 sun4v sparc SUNW,Sun-Blade-T6320
The compiler is Sun C++ 5.9 SunOS_sparc Patch 124863-01 2007/07/25
But when installing the application on Solaris 9
SunOS odcarch02 5.9... (2 Replies)
Discussion started by: ash_bit2k2
2 Replies
2. Solaris
Hi,
I am unable to login into my terminal hosting Solaris 10 and get the below error message
"Server refused to allocate pty
ld.so.1: sh: fatal: libc.so.1: open failed: No such file or directory "
Is there anyways i can get into my machine and what kind of changes are required to be... (7 Replies)
Discussion started by: sankasu
7 Replies
3. Solaris
Need a procedure document to do "root disk mirroring in solaris volume manager for solaris 10". I hope some one will help me asap. I need to do it production environment.
Let me know if you need any deatils on this.
Thanks,
Rama (1 Reply)
Discussion started by: ramareddi16
1 Replies
4. Solaris
Hi Gurus
I am not able to find the patching procedure for solaris 10 ( sol10 u11) to latest patchset with sun cluster having failover zones so that same I should follow.
Take an instance, there are sol1 and sol2 nodes and having two failover zones like sozone1-rg and sozone2-rg and currently... (1 Reply)
Discussion started by: nick101
1 Replies
HME(4) BSD Kernel Interfaces Manual HME(4)
NAME
hme -- Sun Microelectronics STP2002-STQ Ethernet interfaces device driver
SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file:
device miibus
device hme
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
if_hme_load="YES"
DESCRIPTION
The hme driver supports Sun Microelectronics STP2002-STQ ``Happy Meal Ethernet'' Fast Ethernet interfaces.
All controllers supported by the hme driver have TCP checksum offload capability for both receive and transmit, support for the reception and
transmission of extended frames for vlan(4) and a 128-bit multicast hash filter.
HARDWARE
The hme driver supports the on-board Ethernet interfaces of many Sun UltraSPARC workstation and server models.
Cards supported by the hme driver include:
o Sun PCI SunSwift Adapter (``SUNW,hme'')
o Sun SBus SunSwift Adapter (``hme'' and ``SUNW,hme'')
o Sun PCI Sun100BaseT Adapter 2.0 (``SUNW,hme'')
o Sun SBus Sun100BaseT 2.0 (``SUNW,hme'')
o Sun PCI Quad FastEthernet Controller (``SUNW,qfe'')
o Sun SBus Quad FastEthernet Controller (``SUNW,qfe'')
NOTES
On sparc64 the hme driver respects the local-mac-address? system configuration variable which can be set in the Open Firmware boot monitor
using the setenv command or by eeprom(8). If set to ``false'' (the default), the hme driver will use the system's default MAC address for
all of its devices. If set to ``true'', the unique MAC address of each interface is used if present rather than the system's default MAC
address.
Supported interfaces having their own MAC address include on-board versions on boards equipped with more than one Ethernet interface and all
add-on cards except the single-port SBus versions.
SEE ALSO
altq(4), intro(4), miibus(4), netintro(4), vlan(4), eeprom(8), ifconfig(8)
Sun Microelectronics, STP2002QFP Fast Ethernet, Parallel Port, SCSI (FEPS) User's Guide, April 1996,
http://mediacast.sun.com/users/Barton808/media/STP2002QFP-FEPs_UG.pdf.
HISTORY
The hme driver first appeared in NetBSD 1.5. The first FreeBSD version to include it was FreeBSD 5.0.
AUTHORS
The hme driver was written by Paul Kranenburg <pk@NetBSD.org>.
BSD
June 14, 2009 BSD