Re: vr(4) duplex problems

From: Daniel O'Connor (doconnor_at_gsoft.com.au)
Date: 06/17/03

  • Next message: Mike Tancsa: "updating a routing table entry" 
    To: Mike Silbersack <silby@silby.com>
Date: Tue, 17 Jun 2003 10:38:23 +0930

    On Tuesday 17 June 2003 00:40, Mike Silbersack wrote:
    > Well, there have been a few reports of similar problems. However, back
    > when those reports came in, there were a bunch of other problems with our
    > if_vr driver, so everyone gave up and switched network cards before we
    > could get to the duplex autoneg problem. :)

    Hehe :)

    > If possible, I'd like you to try some other brands of 100/FDX hubs and see
    > if autonegotiation works properly; this would help tell us if the problem
    > is general, or specific to that card.

    I don't have any other brands of 100/FDX switches :(
    I will try and dig one up, but I think the best I can do is a different
    generation switch from the same manufacturer.

    > Also, can you post the dmesg output relating to your card? I'm curious
    > which PHY device you have.

    Duh, knew I forgot something..

    vr0: <VIA VT6102 Rhine II 10/100BaseTX> port 0xe800-0xe8ff mem 0xdd006000-0xdd0060ff irq 11 at device 18.0 on pci0
    vr0: Ethernet address: 00:04:61:49:23:7c
    miibus1: <MII bus> on vr0
    ukphy0: <Generic IEEE 802.3u media interface> on miibus1
    ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

    vr0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
            inet 203.31.81.48 netmask 0xffffffc0 broadcast 203.31.81.63
            ether 00:04:61:49:23:7c
            media: Ethernet 100baseTX
            status: active 

    -- 
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 9A8C 569F 685A D928 5140  AE4B 319B 41F4 5D17 FDD5
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
  • Next message: Mike Tancsa: "updating a routing table entry"

    Relevant Pages

    • Re: Failover with two switches ..
      ... But keep in mind that in a properly designed and managed network, ... There have also been reports of ... more switches rather than futzing with VLANs. ...
      (comp.dcom.sys.cisco)
    • Re: same old "Data has been changed error message", way around this?
      ... performing this. ... Switches all matching results to TRUE ... Then my reports read the PrintY_N field to see if it is eligible for the ...
      (microsoft.public.access.formscoding)
    • Re: RFM wont boot
      ... some of those rollover switches may still not work (but shouldn't ... replace the bad switches *after* you find and fix the main problem ... Quality Board Work - In Home Service ... inlane reports as the right outlane, and the right outlane reports as ...
      (rec.games.pinball)
    • Re: RFM wont boot
      ... some of those rollover switches may still not work (but shouldn't ... replace the bad switches *after* you find and fix the main problem ... Quality Board Work - In Home Service ... inlane reports as the right outlane, and the right outlane reports as ...
      (rec.games.pinball)