3Com 3CR990-TX-95/3CR990SVR95

acc_at_anthonychavez.org
Date: 06/30/03

  • Next message: Gary Aitken: "Make XFree86-4-Server => can't fetch Wraphelp.c"
    To: freebsd-questions@freebsd.org
    Date: Mon, 30 Jun 2003 10:18:37 -0600
    
    

    Friends:

    I recently purchased a box of 3Com 3CR990-TX-95 NICs from eBay and am
    currently in the process of testing them with a Dell system that a
    friend lent me (sorry, no specs).

    The back of the functional cards are printed with the following
    information: FAB 02-0182-000 REV 07. The only one that has proven to be
    incompatible (see below) states REV 05. This is strong evidence to me
    that the issue lies in the cards themselves and that, for some reason or
    another, REV 05 cards are incompatible with the txp driver.

    This solitary card, surprisingly, seems to function just fine from the
    outside (i.e., the 100Mbps indicator light illuminates and the "ACT"
    light blinks) but spawns a kernel panic when trying to boot or install
    4.8-RELEASE or 5.1-RELEASE.

    When installing either release, I get the following message as
    /stand/sysinstall loads. I get a similar message when booting
    4.8-RELEASE.

    panic: resource_list_release: resource entry is not busy

    OpenBSD 3.3 and NetBSD 1.6.1 don't detect the NIC at all. FWIW, neither
    does Debian 3.0r1 or Slackware 9.0 (both Linux kernel 2.4.20). And
    unfortunately, this box was donated sans a CD-ROM drive and I don't have
    a spare, so I can't install Windoze to see if the NIC is completely
    b0rked.

    Has anyone had similar experiences? Is my hypothesis correct? And if
    so, are there any workarounds? Am I going to run into problems with the
    3CR990SVR95 that I just purchased?

    Thanks!

    -- 
    Anthony Chavez                             http://www.anthonychavez.org/
    mailto:acc@anthonychavez.org         jabber:acc@jabber.anthonychavez.org
    _______________________________________________
    freebsd-questions@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
    

  • Next message: Gary Aitken: "Make XFree86-4-Server => can't fetch Wraphelp.c"

    Relevant Pages

    • Re: tulip ethernet driver
      ... install, and I have tried both without success. ... I can't find a list of supported NICs onwww.minix3.organd only run ... Minix 2.0.4 on my i286-machine. ... (both are ISA-style cards, the first even available in 8 Bit). ...
      (comp.os.minix)
    • Re: tulip ethernet driver
      ... install, and I have tried both without success. ... I can't find a list of supported NICs on www.minix3.org and only run ... Minix 2.0.4 on my i286-machine. ... (both are ISA-style cards, the first even available in 8 Bit). ...
      (comp.os.minix)
    • Re: DHCP problem where ip address is assigned to wrong NIC on reboot
      ... This old machine I've got has two NICs, ... similar is when the system doesn't detect the cards in the same order ... 'eth1' different. ... In that case, the solution is simple: install the 'ifrename' package, ...
      (Debian-User)
    • Re: IIS install on XP in SBS2003 Domain
      ... Thanks for your help but I figured out that it is not IIS it is a windows ... the same thing happens everytime I install IIS. ... disable the old NICs. ... Disabling the on-board nics in BIOS is optional, ...
      (microsoft.public.windows.server.sbs)
    • Re: SBS NIC Cards give Code 1
      ... But it appears something is wrong at a fairly low level - it's possible you'll get the same error regardless of what hardware you try and install - I doubt it's just networking. ... Do I perhaps have a corrupt drivers directory or more likely corruption in the registry linking network drivers? ... NIC settings to them, and then completely removing the physical nics from the box, including drivers and cleaning out devmgr. ... and my SBS server went down hard a number of time. ...
      (microsoft.public.windows.server.sbs)