Re: [suse-sles-e] Broadcom Firmware

From: Michael Kershaw (mike.kershaw_at_gmail.com)
Date: Tue Mar 13 2007 - 18:23:42 CET


Message-ID: <a7b43ddc0703131023p66ab9ea0qbdc5e72d622f215b@mail.gmail.com>
Date: Tue, 13 Mar 2007 13:23:42 -0400
From: "Michael Kershaw" <mike.kershaw@gmail.com>
Subject: Re: [suse-sles-e] Broadcom Firmware

Sascha,

     I've looked in the messages file, the boot.msg file, I've used
ethtool. Still no luck. The only thing that I hadn't tried before
you wrote was hwinfo(but i should have =D). I ran it, but still no
luck:

32: PCI 700.0: 0200 Ethernet controller
  [Created at pci.274]
  Unique ID: aK5u.AZuxtJ4LwUF
  Parent ID: M71A.rpRWWLU2Bq3
  SysFS ID: /devices/pci0000:00/0000:00:07.0/0000:07:00.0
  SysFS BusID: 0000:07:00.0
  Hardware Class: network
  Model: "IBM Ethernet controller"
  Vendor: pci 0x14e4 "Broadcom"
  Device: pci 0x1659
  SubVendor: pci 0x1014 "IBM"
  SubDevice: pci 0x02c6
  Revision: 0x11
  Driver: "tg3"
  Memory Range: 0xd8ff0000-0xd8ffffff (rw,non-prefetchable)
  IRQ: 16 (282182000 events)
  HW Address: 00:14:5e:0b:0e:73
  Driver Info #0:
    Driver Status: tg3 is active
    Driver Activation Cmd: "modprobe tg3"
  Driver Info #1:
    Driver Status: bcm5700 is not active
    Driver Activation Cmd: "modprobe bcm5700"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #14 (PCI bridge)

There has got to be a way to get this information from the OS
somewhere, I just haven't stumbled across it yet. Thanks for the
efforts ofcourse =-P

Mike Kershaw

On 3/13/07, Sascha Wehnert <sascha.wehnert@ewetel.net> wrote:
> Hi Michael,
>
> Michael Kershaw wrote:
> > So I have a bunch of IBM xSeries servers here, and I'd say almost all,
> > if not all of them have onboard broadcom network adapters. We're
> > having a little throughput issue claims symantec, and in a round about
> > way, their pointing towards firmware. My problem is, I can't seem to
> > dig up a way to pull out what the firmware version is at all. Anyone
> > know a way to pull it from the OS?
> >
> No access to any system right now :( so just some ideas that came to my
> mind.
>
> Check output of
>
> hwinfo --network_ctrl
>
> Also worth a try is /var/log/boot.msg and have a look at the section
> where the
> driver gets loaded. Perhaps it displays the firmware version of the
> adapters.
>
> netdiag and ethtool packages might also contain tools and switches to query
> the adapters.
> > TIA,
> > Mike Kershaw
> >
> Regards,
>
> Sascha
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: suse-sles-e-unsubscribe@suse.com
> For additional commands, e-mail: suse-sles-e-help@suse.com
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: suse-sles-e-unsubscribe@suse.com
For additional commands, e-mail: suse-sles-e-help@suse.com



This archive was generated by hypermail 2.1.7 : Tue Mar 13 2007 - 20:27:33 CET