-----BEGIN PGP SIGNED MESSAGE-----


>>>>> "Thor" == Thor Lancelot Simon <tls@rek.tjls.com> writes:
    >> My firewall has started to do:
    >> 
    >> Jan 20 10:35:20 bud /netbsd: tlp0: receive error: dribbling bit
    >> Jan 20 10:35:20 bud /netbsd: tlp0: receive error: CRC error
    >> Jan 20 10:35:22 bud /netbsd: tlp0: receive error: dribbling bit
    >> Jan 20 10:35:22 bud /netbsd: tlp0: receive error: CRC error

    Thor> This is usually a symptom of a duplex mismatch or MII configuration
    Thor> problem.  Unfortunately, the various 21x4x and clones use a truly
    Thor> wild variety of physical interface mechanisms and don't present a
    Thor> uniform interface for configuring them; worse, some of them don't
    Thor> do Nway negotiation in hardware but require a software state 
    Thor> machine.  Our driver is a lot better than it was, but doesn't
    Thor> always get it right, and with some chips it's worse than that: the
    Thor> driver will somehow get out of sync after everything's worked fine
    Thor> for a long time.

  okay, fair enough.
  a) This is a real 21143 chip. 
  b) this is a straight cable to a GVC ADSL modem. I can force things to
  10baseT, instead of auto, if you think that may help get around nway.

]       ON HUMILITY: to err is human. To moo, bovine.           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Finger me for keys

iQCVAwUBPi2KmoqHRg3pndX9AQHDggP/QU9sRsqmD3uI9xv3QKC45LquMOAuXUu0
+XZosnGe4+P6r1HBTNX8W2SVakh4O+Vc0Qlmgoo3QQGWCOUgfgKSUgvumOmyGfE8
WRdPRKN24YJhfi6spHRx0n1Zmse5Zt3GVDqskwYLUZ3MXjj56el2rTZKDS9KKP7G
uozCgTs43Gg=
=a+cJ
-----END PGP SIGNATURE-----