> In this case, perhaps a better solution would be to mention that > autonegociation is broken, and therefore speeds need to be > adjusted manually in the man page. Does that look better to you ?
It would be better to know first if other tl(4) users are experiencing the same problem. Hard to know since this card has almost completely faded away from dmesg reports. Also we have no idea about your particular PHY setup. There are several flavours: tl0 at pci0 dev 16 function 0 "Compaq Embedded Netelligent 10/100 TX" rev 0x10: irq 11 address whatever lxtphy0 at tl0 phy 1: LXT970 10/100 media interface, rev. 0 ukphy0 at tl0 phy 31: Generic IEEE 802.3u media interface ukphy0: OUI 0x100014, model 0x0001, rev. 6 tl0 at pci0 dev 12 function 0 "Compaq Netelligent 10 T" rev 0x10: irq 10 address whatever ukphy0 at tl0 phy 31: Generic IEEE 802.3u media interface ukphy0: OUI 0x100014, model 0x0001, rev. 4 (this one is a 10Mbit/s only model) tl0 at pci1 dev 11 function 0 "Compaq ProLiant Netelligent 10/100 TX" rev 0x10: irq 4 address whatever nsphy0 at tl0 phy 1: DP83840 10/100 media interface, rev. 1 ukphy0 at tl0 phy 31: Generic IEEE 802.3u media interface ukphy0: OUI 0x100014, model 0x0001, rev. 5 The problem you are encountering could actually be a bug in one of the phy drivers, or (more likely) in the interface between tl(4) and the mii(4) layer. Miod