Post by Dave
I've got a Sun Ultra 60 with a hme ethernet interface. I don't believe
there is anything wrong with it (I do need to ensure this though) but it
works very badly when plugged into my DrayTek 2520Vn router. It did work
fine on another router, so either its a compatibility issue with the
DrayTek or its been damaged in the last couple of weeks.)
I had the same experience with my U5 system with hme interface and
Linksys and later a NetGear router. I had to force 10FDX on Solaris 9
and ISTR I did this by editing the /etc/system file.
Once I got to Solaris 10 Update 5, autonegotiation started working and
forcing was no longer necessary.
"A longstanding issue with the hme0 interface was resolved by Solaris
10. I was never able to get autonegotiation working between first a
Linksys router/switch and later the Netgear. I had to force hme0 and
then it would only work if I forced 10FDX; 100FDX refused to work either
way. hme patches didn't help. Now I am finally autonegging:
NOTICE: hme0: 100Mbps full duplex link up "
Post by Dave
I'm wondering if perhaps things like auto speed sensing, half/full
duplex or something else is just not compatible with the DrayTek. In
which case, is there anything I can do to force the hmeo interface to
stay in a mode that works?
but its 10 years old and I'm not sure if much of it is applicable in
Solaris 10 update 6.
of the methods listed there, #1 is applicable to Solaris 10. Don't use
/etc/system. the .conf files ensure that the params are read by the
kernel early in the boot process, which is good practice:
1) Driver dependent config (/kernel/drv/hme.conf):
-- ------ --------- ------ -----------------------
adv_autoneg_cap = 0 adv_100fdx_cap = 1 adv_100hdx_cap = 0 adv_10fdx_cap
= 0 adv_10hdx_cap = 0;
that will set all instances of hme to 100FDX, the easiest way to set
that up when you have a single interface. To set different params for
multiple instances is a bit trickier, as you need to dig around in
path_to_inst, but doable.
To sort of experiment to see what speed works best with your router, use
the ndd commands 'on the fly' to set either 100FDX or 10FDX. I'm used to
setting the instance first:
ndd -set /dev/hme instance 0 (assuming hme0)
Then . .
ndd -set /dev/hme adv_autoneg_cap 0
ndd -set /dev/hme adv_100hdx_cap 0
ndd -set /dev/hme adv_100fdx_cap 1
check /var/adm/messages for a link message and/or use ndd to check:
# ndd /dev/hme link_status
# ndd /dev/hme link_speed
# ndd /dev/hme link_mode
would indicate up, 100Mbps, full duplex. If that seems to work, then
force the interfaces with hme.conf and reboot.
Post by Dave
Ideally I'd like to force 100baseT full duplex but anything that works
reliably (even 10baseT half-duplex) would be ok!
10HDX would probably work, but it would be slow and aggravating to use,
with network services timing out . . . ugh. Hopefully that won't be