Hello all,
thank you all for your hints, special thanks to
David Hull [ <mailto:David_Hull_at_Jabil.com> David_Hull_at_Jabil.com]
dschen - Darren Schenebeck [ <mailto:dschen_at_acxiom.com> dschen_at_acxiom.com]
system administration account [ <mailto:sysadmin_at_astro.su.se>
sysadmin_at_astro.su.se]
Sean O'Connell [ <mailto:sean_at_stat.Duke.EDU> sean_at_stat.Duke.EDU]
Thomas Leitner [ <mailto:tom_at_radar.tu-graz.ac.at> tom_at_radar.tu-graz.ac.at]
Dr. <mailto:Thomas.Blinn_at_Compaq.com> Thomas.Blinn_at_Compaq.com [
<mailto:tpb_at_doctor.zk3.dec.com> tpb_at_doctor.zk3.dec.com]
Selden E Ball Jr [ <mailto:SEB_at_LNS62.LNS.CORNELL.EDU>
SEB_at_LNS62.LNS.CORNELL.EDU]
Degerness, Mandell ISTA:EX [ <mailto:Mandell.Degerness_at_gems2.gov.bc.ca>
Mandell.Degerness_at_gems2.gov.bc.ca]
Original question below.
Best explanation from Dr.Blinn:
"dia" is only reporting the text messages that were displayed by the kernel
at boot time the last time the system was booted (or maybe even some time
before that). The same messages are probably found in your /var/adm/messages
file.
When the "tu" driver started up and started interacting with your unit 0
device, it selected (as a starting point) 10Mbit half duplex.
Nothing prevents some other speed being set later on by software.
Autosensing and autonegotiation are not the same thing, in spite of both
having "auto" in their names.
Because there were LOTS of problems with these interfaces, the preferred
speed setting method is via the lan_config utility.
See the reference page.
Second problem was the strange date shown by dia. I think this is an entry
from old Y2K-testings. I will reset binary.errlog.
regards
Werner Rost
--------------------------------------------------
Werner Rost, Mannesmann-Boge GmbH
Abt: KIR
Tel: 0228/3825-420
Fax: 0228/3825-398
Email: werner.rost_at_boge.mannesmann.de
Friesdorfer Str. 175, 53175 Bonn - Bad Godesberg
---------------------------------------------------
-----Ursprüngliche Nachricht-----
Von: Rost, Werner
Gesendet am: Mittwoch, 31. Januar 2001 16:16
An: ALPHA-System-Managers (E-Mail)
Betreff: Part 2: Speed of NIC
Hello gurus,
thank you for much hints. But now things become more and more strange:
look at following output of "dia -R":
DECevent V3.3
Logging OS 2. Digital UNIX
System Architecture 2. Alpha
Event sequence number 0.
Timestamp of occurrence 19-DEC-2004 10:57:29
Host name goaw12
.......
Digital Personal WorkStation 433au
Firmware revision: 7.0-10
PALcode: Digital UNIX version 1.22-0
pci0 at nexus
tu0: DECchip 21143: Revision: 3.0
tu0: auto negotiation capable device
tu0 at pci0 slot 3
tu0: DEC TULIP (10/100) Ethernet Interface, hardware address:
00-00-F8-75-E4-47
tu0: auto negotiation off: selecting 10BaseT (UTP) port: half duplex
Output of /var/adm/messages:
Jan 31 09:48:15 goaw12 vmunix: Alpha boot: available memory from 0xdb0000 to
0x1
7ffe000
Jan 31 09:48:16 goaw12 vmunix: Digital UNIX V4.0F (Rev. 1229); Tue Jun 29
13:26
:05 MET DST 1999
Jan 31 09:48:16 goaw12 vmunix: physical memory = 384.00 megabytes.
Jan 31 09:48:16 goaw12 vmunix: available memory = 370.32 megabytes.
Jan 31 09:48:16 goaw12 vmunix: using 1467 buffers containing 11.46 megabytes
of
memory
Jan 31 09:48:16 goaw12 vmunix: Digital Personal WorkStation 433au
Jan 31 09:48:16 goaw12 vmunix: Firmware revision: 7.0-10
Jan 31 09:48:16 goaw12 vmunix: PALcode: Digital UNIX version 1.22-0
Jan 31 09:48:16 goaw12 vmunix: pci0 at nexus
Jan 31 09:48:16 goaw12 vmunix: tu0: DECchip 21143: Revision: 3.0
Jan 31 09:48:16 goaw12 vmunix: tu0: auto negotiation capable device
Jan 31 09:48:16 goaw12 vmunix: tu0 at pci0 slot 3
Jan 31 09:48:16 goaw12 vmunix: tu0: DEC TULIP (10/100) Ethernet Interface,
hardware address: 00-00-F8-75-E4-47
Jan 31 09:48:16 goaw12 vmunix: tu0: auto negotiation off: selecting
100BaseTX (UTP) port: full duplex
Jan 31 09:48:16 goaw12 vmunix: ata0 at pci0 slot 4
Digital Unix 4.0F (no patchkit because /var/adm/patch does not exist and
setld -i | grep OSFPAT does not display anything)
Console mode shows "ewa0_mode=fastfd". Because the NIC ist connected to a
switch which port is configured to "speed=100, duplex=full, autosensing=off"
and all works fine NIC speed is definitely 100 M/s!
# consvar -g ewa0_mode
ewa0_mode = FastFD (Full Duplex)
# date
Wed Jan 31 16:13:06 MET 2001
#
1. date of "dia" is wrong but after finishing boot date-command show the
rigt date ?????????
2. "dia" says: "10BaseT half duplex"
/var/adm/messages says: "100Base-TX, full duplex"
What is going wrong?
regards
Werner Rost
--------------------------------------------------
Werner Rost, Mannesmann-Boge GmbH
Abt: KIR
Tel: 0228/3825-420
Fax: 0228/3825-398
Email: werner.rost_at_boge.mannesmann.de
Friesdorfer Str. 175, 53175 Bonn - Bad Godesberg
---------------------------------------------------
-----------------------------------------------------------
This Mail has been checked for Viruses
Attention: Encrypted Mails can NOT be checked !
***
Diese Mail wurde auf Viren ueberprueft
Hinweis: Verschluesselte Mails koennen NICHT geprueft werden!
------------------------------------------------------------
Received on Thu Feb 01 2001 - 12:49:31 NZDT