RE: Intel and Broadcom NICs

From: Sreekanth (sreekanth_at_redlinenetworks.com)
Date: 08/21/03

  • Next message: Pawel Jakub Dawidek: "Re: [future patch] dropping user privileges on demand" 
    To: "'Kevin A. Pieckiel'" <kpieckiel@smartrafficenter.org>, <freebsd-hackers@freebsd.org>
Date: Thu, 21 Aug 2003 13:20:24 -0700

    The intel nic is a fxp interface.Device ID 1050("Intel 82801BA (D865)
    Pro/100 VE Ethernet")You probably need to use the latest driver from
    current.To make sure you have the driver check if you have this line
     { 0x1050, -1, "Intel 82801BA (D865) Pro/100 VE Ethernet" }, in
    if_fxp.c

    Ditto with broadcom NIC

    Sreekanth

    > -----Original Message-----
    > From: owner-freebsd-hackers@freebsd.org
    > [mailto:owner-freebsd-hackers@freebsd.org] On Behalf Of Kevin
    > A. Pieckiel
    > Sent: Thursday, August 21, 2003 12:53 PM
    > To: freebsd-hackers@freebsd.org
    > Subject: Intel and Broadcom NICs
    >
    >
    > I've got a Dell Dimension 8300 on which I have loaded
    > FreeBSD. It has an integrated Intel 10/100 NIC and a
    > Broadcom 10/100/1000 NIC. I know the Broadcom NIC has a 5705
    > chipset, but I don't know about the integrated NIC. I would
    > have thought both of these NICs were supported, but the bge
    > driver doesn't indicate that it finds a NIC and none of the
    > Intel drivers report finding anything, either. What gives?
    >
    > Here's the relevant output from pciconf:
    >
    > none4@pci2:2:0: class=0x020000 card=0x86531028
    > chip=0x165314e4 rev=0x01 hdr=0x00
    > vendor = 'Broadcom Corporation'
    > class = network
    > subclass = ethernet
    > none5@pci2:8:0: class=0x020000 card=0x01571028
    > chip=0x10508086 rev=0x02 hdr=0x00
    > vendor = 'Intel Corporation'
    > class = network
    > subclass = ethernet
    >
    > And here's the relevant output from dmesg:
    >
    > pci2: <network, ethernet> at device 2.0 (no driver attached)
    > pci2: <network, ethernet> at device 8.0 (no driver attached)
    >
    >
    > This is from sources cvs'ed and compiled today (21 Aug 2003).
    >
    > Any help would be appreciated.
    >
    > Kevin A. Pieckiel _______________________________________________
    > freebsd-hackers@freebsd.org mailing list
    > http://lists.freebsd.org/mailman/listinfo/free> bsd-hackers
    > To
    > unsubscribe, send any mail to
    > "freebsd-hackers-unsubscribe@freebsd.org"
    >
    > ---
    > Incoming mail is certified Virus Free.
    > Checked by AVG anti-virus system (http://www.grisoft.com).
    > Version: 6.0.502 / Virus Database: 300 - Release Date: 7/18/2003
    >
    >

    _______________________________________________
    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: Pawel Jakub Dawidek: "Re: [future patch] dropping user privileges on demand"

    Relevant Pages

    • Re: dummynet, em driver, device polling issues :-((
      ... My time machine is broken:) ... The em Intel NICs I found to be ... >> i have been messing with the em driver now for over a month, ...
      (freebsd-net)
    • Re: Wireless network w/ SBS
      ... If you have Intel wireless NICs, you may find a more recent driver on the ... Intel site than what the PC manufacturer offers. ... verify - their documentation should say whether they have AES support or not. ...
      (microsoft.public.windows.server.sbs)
    • Re: How to test a nic card?
      ... check yours against the photos on the download page for the proper driver ... it resolves the problem- some nics have trouble negotiating link speed with ... >>Windows 2000 IP Configuration ... >>Ethernet adapter Local Area Connection: ...
      (microsoft.public.win2000.networking)
    • Re: 2nd NIC ifconfig
      ... also assume eth0 and eth1 are different types of nics and thus need ... then ifconfig eth1 to bring the card up ... if you don't know the driver needed for the secound card. ... I know by using each NIC one at a time that all four NICs I've tried ...
      (comp.os.linux.networking)
    • Re: ethernet inteface: lost connection
      ... chipset nVidia, with a AMD64 CPU, and onboard NIC is nForce. ... While I'm having a problem with the onboard NIC, it's driver ... Why do you assume I have 2 "onboard" NICs? ... unknown hardware address type 776 ...
      (comp.os.linux.hardware)