broadcom woes

I am trying to setup my braodcom giagbit network card on the
motherboard
from asus (with 64-bit dual xeon and pci express). I downloaded and
compiled and insmoded the module. Everything is fine, except that suse
would not see the broadcom
Anyone had any similar problems?

Thanks,
--j

John wrote:
> I am trying to setup my braodcom giagbit network card on the
> motherboard
> from asus (with 64-bit dual xeon and pci express). I downloaded and
> compiled and insmoded the module. Everything is fine, except that suse
> would not see the broadcom
> Anyone had any similar problems?

"suse" doesn't see it....I take that to mean that some sorf of GUI that
comes on SuSE refuses to recognise that a network device is now
attached? Or some similar story...

What does `ifconfig -a` tell you?

John wrote:
> eth1 Link encap:Ethernet HWaddr 11:11:2F:27:AA:B1
> inet6 addr: fe80::211:2fff:fe26:aab1/64 Scope:Link
> UP BROADCAST NOTRAILERS MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
> Interrupt:16

Well then unless you have two other network cards, which you don't say,
this might be it.

eth0 Link encap:Ethernet HWaddr 00:04:75:7A:89:FD
inet addr:127.186.122.49 Bcast:127.186.122.255
Mask:255.255.255.0
inet6 addr: fe80::204:75ff:fe7a:89fd/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:165595 errors:0 dropped:0 overruns:0 frame:0
TX packets:11907 errors:0 dropped:0 overruns:0 carrier:34
collisions:0 txqueuelen:1000
RX bytes:29222060 (27.8 Mb) TX bytes:1377869 (1.3 Mb)
Interrupt:27 Base address:0xdc00

eth1 Link encap:Ethernet HWaddr 11:11:2F:27:AA:B1
inet6 addr: fe80::211:2fff:fe26:aab1/64 Scope:Link
UP BROADCAST NOTRAILERS MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:16

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:450 errors:0 dropped:0 overruns:0 frame:0
TX packets:450 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:28568 (27.8 Kb) TX bytes:28568 (27.8 Kb)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

Noah Roberts wrote:
> John wrote:
> > I am trying to setup my braodcom giagbit network card on the
> > motherboard
> > from asus (with 64-bit dual xeon and pci express). I downloaded and
> > compiled and insmoded the module. Everything is fine, except that
suse
> > would not see the broadcom
> > Anyone had any similar problems?
>
> "suse" doesn't see it....I take that to mean that some sorf of GUI
that
> comes on SuSE refuses to recognise that a network device is now
> attached? Or some similar story...
>
> What does `ifconfig -a` tell you?

My lspci shows this

0000:02:00.0 Ethernet controller: Broadcom Corporation: Unknown device
1677 (rev 01)

Since my broadcom was not working , I have a 3com 100mbit card
connected to it
for now. Yast on suse shows me Asustek Ethernet controller Configured
with DHCP
instead of broadcom. It does recognise the 3com for sure,


--j

My lspci | grep Bro shows

0000:02:00.0 Ethernet controller: Broadcom Corporation: Unknown device
1677 (rev 01)

And if i remove my 3com card, my network doesnt work. Another problem
is that
SuSe's system configuration utility shows the broadcom card as :

Asustek Ethernet controller
Configured with DHCP

Any remedies?

Thanks,
--j

> My lspci shows this
>
> 0000:02:00.0 Ethernet controller: Broadcom Corporation: Unknown device
> 1677 (rev 01)

I can't find the original post, but based on the above and assuming you
are planning to use a 2.4.x series kernel, there is both good and bad news.

The bad news is that the card doesn't seem to be supported in 2.4.21 or
2.4.25:

$ pwd
/usr/src/linux-2.4.21
$ grep 1677 include/linux/pci_ids.h
$

$ pwd
/usr/src/linux-2.4.25
$ grep 1677 include/linux/pci_ids.h
$

But the good news is that it may be supported in more recent kernels:

$ pwd
/usr/src/linux-2.4.28-pps
$ grep 1677 include/linux/pci_ids.h
#define PCI_DEVICE_ID_TIGON3_5751 0x1677
$ find . -name '*.c' -print | xargs grep PCI_DEVICE_ID_TIGON3_5751
../drivers/net/tg3.c: { PCI_VENDOR_ID_BROADCOM, PCI_DEVICE_ID_TIGON3_5751,

(other matches omitted)

So, if you are OK with rolling your own kernel, you should be able to
build something that will recognize your NIC.

Here is my kernel

Linux hulk 2.6.11-rc1-mm1 #2 SMP Sat Jan 15 18:27:32 EST 2005 x86_64
x86_64
x86_64 GNU/Linux

And I'm sure in theory it does support broadcom. Also I could easily
compile
the braodcom drivers into a module from their website. But insmodding
doesnt
work

> Linux hulk 2.6.11-rc1-mm1 #2 SMP Sat Jan 15 18:27:32 EST 2005 x86_64
> x86_64
> x86_64 GNU/Linux
>
> And I'm sure in theory it does support broadcom. Also I could easily
> compile
> the braodcom drivers into a module from their website. But insmodding
> doesnt work

To see if the kernel is supposed to support the card, grep for the
appropriate magic number in the include/linux directory of your kernel
source. If it's there, see where the corresponding defined constant
appears in the drivers (I would guess it should be where I found it in
the 2.4.28 source). In that case you will be left with the job of
figuring out why the module isn't loading (or, since you seem to have a
custom build kernel, figuring out why it didn't compile). If the
constant isn't in include/linux/pci_ids.h, you will have to figure out
how to install Broadcom's driver.