SCIENTIFIC-LINUX-USERS Archives

August 2010

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Alan Bartlett <[log in to unmask]>
Reply To:
Alan Bartlett <[log in to unmask]>
Date:
Thu, 26 Aug 2010 21:34:03 +0100
Content-Type:
text/plain
Parts/Attachments:
text/plain (36 lines)
On 26 August 2010 10:19, Markus Neteler <[log in to unmask]> wrote:

> I hoped to find the NetXen driver in SL 5.5 but it does not seem to be in
> Linux fep 2.6.18-194.11.1.el5 #1 SMP Tue Aug 10 16:39:28 EDT 2010
> x86_64 x86_64 x86_64 GNU/Linux
>
> The network card is this:
>
> lspci  | grep NetX
> 03:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708
> Gigabit Ethernet (rev 12)
> 07:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708
> Gigabit Ethernet (rev 12)
> 08:00.0 Ethernet controller: NetXen Incorporated NXB-10GCX4 10-Gigabit
> Ethernet PCIe Adapter with CX4 copper interface (rev 25)

Markus,

The most precise way of determining exactly which driver is required
for a particular device is via the Vendor:Device ID Pairing (a.k.a.
the device fingerprint).

In you particular case, above, I would be interested in seeing the
output returned by --

/sbin/lspci -n | grep -E '03:00.0|07:00.0|08:00.0'

I would then use the technique, as shown in FAQ #4 at
http://elrepo.org/tiki/FAQ --

grep -i VendorID /lib/modules/*/modules.alias | grep -i DeviceID

Hope this helps.

Alan.

ATOM RSS1 RSS2