It is REALLY tough to get a hold of this driver. I've been hunting for three days and JUST found them. Broadcom has no downloads at all, and Asus only has Win/Dos downloads for the BCM4401. And would'nt ya know, my driver disc is up and vanished! I have the damn slip with the sticker still in it but no driver disc!

Anyway, found these drivers at MSI's site! Dunno why the Asus download doesn't have them.. here is the link. It's a Win .exe file so you'll need some way of extracting it.

http://download.msi.com.tw/support/dvr_exe/440145.exe

Hope this helps everyone!

Ok, grr.. I'm using MDK9 and when I try to "make" the driver from the sources everything appears to go through, the bcm4000.o file is created, but the term window reports alot of errors about files not being where it needs them.

I've installed the kernel source and all dep-mods but still get this problem. Even with the completed .o file If I use the Ethernet config tool, I get no option for the driver I just compiled. The 4401 is seen as a "Unknown eth0" in the config tool BTW. When I tried to make the .o before installing the kernel source there was a message in term saying that kern 2.4.x have a different path to some things and that I had to make some changes to the makefile.. unfortunate for me, i didn't save that message.. Any ideas/help??

Thanks!

Well, I used a file that ultrax emailed to me. I have RH 7.1 and so I needed to hunt for the kernel-source which I luckily found on the cd. The rest (libacl, libacl-devel, libattr, and libattr-devel) I had to find on the web. I got an error for every one of those packages I installed but continued on anyway. Then, I tarred the file, cd into the src directory and ran make. Well, it ran and I got the files but I also had screen upon screen loaded with the error "paste...and something about preprocessing token". I ignored it and successfully loaded the driver by running /sbin/insmod bcm4400.o. Then I ran netconfig, and much to my amazement, everything is working. Try that and good luck - if you want the driver I have, let me know and I'll email it to you - not sure if it's the same one you got.

Ok! New update for me. Still using MDK9 (Is that my problem?) Re-install MDK9 again, choosing to install source during the install. Install goes fine, boot into KDE 3.0, browse to where the source files are, try to "make" agian. This time there are only 2 errors. They state the same error about pre-processing. After this completes, attempt to "make install" Error now is "Not a valid ELF file" soooo have it compiled but will not install.

Next phase: go to work and use machine at work ALSO running MDK9 but kernel 2.4.20. Compile source, NO errors, use "make install" tries to but then says "no such device" which makes sense. Make an RPM to install the Module (have it if anyone needs. Compiled in MDK9 w/kern 2.4.20). Take RPM for new kern, new kern source, and new driver RPM home.

Next phase: Install new kern RPM using Kpackage. Install goes fine, no errors. All files installed successfully. Reboot and choose new kern in LILO, system hardlock. Numlock doesn't even respond. Reboot and try old kern, hardlock. Yay, install time again.

Next phase: Install MDK9 agian, delete old partitions and remake new ones. Choose not to install kern 2.4.19 source, install goes well. Immediatly after install completes to to install new kern RPM using Kpackage again. Installs fine again. Reboot, try new kern, hardlock. Reset, try old link, hardlock.

Next phase: Install MDK9 again, delete old partitions and remake new ones. Choose not to install kern 2.4.19 source, install goes well. After install completes try to install new kern RPM again. This time using Mandrake Control Center/Add Software. Install goes fine again, THIS time check LILO config before reboot. LILO is set to boot original kern at /boot/vlinuz which itself is a link to NEW KERN! Change entry to boot old kern. Save and reboot. Try new kern again, hardlock. Reset, try old kern, loads start screen, then errors saying that INIT not set or something similar.

At this point, I decide to check my XP entry to make sure it still works.. Yup, loads fine and runs perfect (WinXP SP1). *sigh* I really want to use MDK9 but I'm beginning to think it hates my system. (Asus A7V8X, GeForce3 Ti200, 2 Maxtor 20GB, SBLive) I have a 3com PCI hard but what's the point? I don't want two NIC's.

Well, if anyone has any other ideas for me feel free to post.

hiya... if you need the driver for the broadcom get it from the following url

http://www.yowser.org/linux/drivers/net/

there is the gz file and the release.txt off the cdrom as well as the md5

Sorry if this is a repost.

Im gald to see I am not the only one with a problem with this motherboard )

I am having the exact same problem, however mine has a bit of a twist. I should mention I have the new Asus A7V8X MB.

I am able to compile NIC driver from the source code on the Asus CD, and there are no compile errors. The object files are made automatically and placed in

/lib/modules/2.4.19-16mdk/kernel/drivers/net

All files in here are object files but they have been GZip'ed, there is not one file with out a .0.gz extension.

Anyway when I try to install the module I get an instmod error:
init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.

I have determinded that the Onboard Lan card is a Broadcom 5702 Gigabit adapter. It is also on IRQ 10. I found this by /sbin/lspci-v

What am I doing wrong when im trying to insmod? The exact syntax im typing is
insmod bcm5700

The error message suggest I use a IRQ as a parameter to insmod, so how would I actually do this?

If anyone has successfully added this driver using INSMOD please let me know how you did it, any help is greatly appreciated.

I recently bouhgt a Dell Dimension 2350 which uses the Broadcom 4401 ethernet controller as well. I need to build a RedHat 8.0 driver for it. Could someone email or point me to a location for getting the sources. The few URLs posted in this topic don't return the code.

Jim

What's your email address coreman???

reith@racores.com

Thanks

Coreman, did you get the drivers working successfully? If so could you please email me the drivers as well? darrylc@rogers.com

Thank-you in advance

Yes, it worked fine just as described in the release doc.

Here's the tarball and doc

http://www.racores.com/temp/bcm4400-1.0.1.tar.gz
http://www.racores.com/temp/RELEASE.TXT

Later:

Due to overwhelming response to people unable to build the driver with these instructions, here's the driver I built. This is for use on a Dell Dimension 2350 running Red Hat 8.0

http://www.racores.com/temp/bcm4400.o

Thank-you for the post. By the way what Distribution are you using? I am using Mandrake 9. Im not sure if that matters or not, but I think this driver works for all Distributions. Am I correct in assuming that?

Thanks again!

I built it for Red Hat 8.0. The sources are from the Devo kernels. The driver is standard in the 2.5.x tree

I'm Looking How To DO A make File Also i suck @ it my system Just Manndrake 8.2 kernal is like 4.18 somthing like that if one could compile it be great :P



Broadcom Corporation
16215 Alton Parkway,
Irvine, CA 92619-7013

Release Notes
Broadcom BCM4400 Linux Driver
Version 1.0.1
08/26/2002

Table of Contents
=================

Introduction
Limitations
Packaging
Installing Source RPM Package
Building Driver From TAR File
Notes
Patching PCI Files
Patching Driver Into Kernel
Network Installation
Unloading and Removing Driver
Module Parameters
Driver Messages
Statistics
Revision History


Introduction
============

This file describes the Linux driver for the Broadcom BCM4400 series
10/100 Mbps Ethernet Network Controllers.


Limitations
===========

The current version of the driver has been tested on Red Hat 7.1, 7.2,
7.3, and 8.0 beta Linux distributions for i386 systems, and other similar
Linux distributions using 2.4.x kernels. The driver has been tested up to
kernel version 2.4.18.


Packaging
=========

The driver is released in two packaging formats: source RPM and compressed tar
formats. The file names for the two packages are bcm4400-<version>.src.rpm and
bcm4400-<version>.tar.gz respectively. Identical source files to build the
driver are included in both packages.


Installing Source RPM Package
=============================

1. Install the source RPM package:

rpm -ivh bcm4400-<version>.src.rpm

If installing the driver on SuSE Linux, refer to the Notes section below
before continuing.

2. CD to the RPM path and build the binary driver for your kernel:

cd /usr/src/{redhat,OpenLinux,turbo,packages,rpm ..}
rpm -bb SPECS/bcm4400.spec

or

rpmbuild -bb SPECS/bcm4400.spec (for RPM version 4.x.x)

Note that the RPM path is different for different Linux distributions.

3. Install the newly built package (driver and man page):

rpm -ivh RPMS/i386/bcm4400-<version>.i386.rpm

The driver will be installed in the following path:

2.2.x kernels:

/lib/modules/<kernel_version>/net/bcm4400.o

2.4.x kernels:

/lib/modules/<kernel_version>/kernel/drivers/net/bcm4400.o

4. Load the driver:

insmod bcm4400

5. To configure network protocol and address, refer to various Linux
documentations.

Building Driver From TAR File
=============================

1. Create a directory and extract the files:

tar xvzf bcm4400-<version>.tar.gz

If installing the driver on SuSE Linux, refer to the Notes section below
before continuing.

2. Build the driver bcm4400.o as a loadable module for the running kernel:

cd src
make

3. Test the driver by loading it:

insmod bcm4400.o

4. Install the driver and man page:

make install

See RPM instructions above for the location of the installed driver.

5. To configure network protocol and address, refer to various Linux
documentations.

Notes
=====

Note 1: If compiling the driver under SuSE Linux kernel and errors are
reported, follow the general guidelines below to rebuild the kernel
source tree:

cd /usr/src/linux-<kernel_version>.SuSE
cp /boot/vmlinuz.config .config
cp /boot/vmlinuz.version.h include/linux/version.h
cp /boot/vmlinuz.autoconf.h include/linux/autoconf.h
make oldconfig
make dep

where <kernel_version> is the actual kernel version used in the SuSE
distribution. Example: /usr/src/linux-2.4.4.SuSE


Unloading and Removing Driver
=============================

To unload the driver, use ifconfig to bring down all eth# interfaces opened
by the driver, then do the following:

rmmod bcm4400


If the driver was installed using rpm, do the following to remove it:

rpm -e bcm4400


If the driver was installed using make install from the tar file, the driver
bcm4400.o has to be manually deleted from the system. Refer to the section
"Building Driver From TAR File" for the location of the installed driver.


Module Parameters
=================

Optional parameters for the driver can be supplied as command line arguments
to the insmod command. Typically, these parameters are set in the file
/etc/modules.conf (see the man page for modules.conf). These parameters take
the form

<parameter>=value[,value,...]

where the multiple values for the same parameter are for multiple NICs
installed in the system.

Note that default or other meaningful values will be used when invalid values
are selected. Some combinations of parameter values may conflict and lead to
failures. The driver cannot detect all such conflicting combinations.

All the parameters are listed below.

line_speed

Selects the line speed of the link. This parameter is used together with
full_duplex and auto_speed to select the speed and duplexity of the link
and the setting of autonegotiation.

The valid values are:

0 Autonegotiate for highest speed supported by link partner (default)
10 10 Mbps
100 100 Mbps

If line_speed is set to 10, 100, or 1000, the NIC will autonegotiate for
the selected speed (and selected duplexity) if auto_speed is set to 1.
If auto_speed is set to 0, the selected speed and duplexity will be
set without autonegotiation. Note that 1000 Mbps must be negotiated for
copper twisted pair links.

auto_speed

Enables or disables autonegotiation. The valid values are:

0 Autonegotiation disabled
1 Autonegotiation enabled (default)

Note that this parameter is ignored and assumed 1 if line_speed is set
to 0.

full_duplex

Selects the duplexity of the link. This paramter is used together with
line_speed to select the speed and duplexity of the link. Note that this
parameter is ignored if line_speed is 0.

The valid values are:

0 half duplex
1 full duplex (default)


rx_flow_control

Enables or disables receiving flow control (pause) frames. This parameter
is used together with auto_flow_control. The valid values are:

0 pause receive disabled (default)
1 pause receive enabled if auto_flow_control is set to 0, or
pause receive advertised if auto_flow_control is set to 1

tx_flow_control

Enables or disables transmitting flow control (pause) frames. This parameter
is used together with auto_flow_control. The valid values are:

0 pause transmit disabled (default)
1 pause transmit enabled if auto_flow_control is set to 0, or
pause transmit advertised if auto_flow_control is set to 1

auto_flow_control

Enables or disables autonegotiation of flow control. This parameter is used
together with rx_flow_control and tx_flow_control to determine the
advertised flow control capability. The valid values are:

0 flow control autonegotiation disabled (default)
1 flow control autonegotiation enabled with capability specified in
rx_flow_control and tx_flow_control (only valid if line_speed is
set to 0 or auto_speed is set to 1)

tx_pkt_desc_cnt

Configures the number of transmit descriptors. Default is 64. The
valid range is from 1 to 511.

rx_pkt_desc_cnt

Configures the number of receive descriptors. Default is 64. The
valid range is from 1 to 511.


Driver Messages
===============

The following are the most common sample messages that may be logged in the file
/var/log/messages. Use dmesg -n <level> to control the level at which messages
will appear on the console. Most systems are set to level 6 by default.

Broadcom 4401 Ethernet Driver bcm4400 ver. 1.0.0 (08/21/02)

Driver signon


eth#: Broadcom BCM4401 100Base-T found at mem f7ffc000, IRQ 18, node addr
0010180407b2

NIC detected


bcm4400: eth# NIC Link is Up, 100 Mbps full duplex

Link up and speed indication


bcm4400: eth# NIC Link is Down

Link down indication


Statistics
==========

Detailed statistics and configuration information can be viewed in the file
/proc/net/nicinfo/eth#.info.


Revision History
================
1.0.1 (08/26/02)

- Fixed the problem of resets during heavy traffic.

1.0.0 (08/22/02)

- First release.




Hopen that helps anyone has the time to compie a driver

I recently bouhgt a Dell Dimension 2350 which uses the Broadcom 4401 ethernet controller as well. I need to build a RedHat 8.0 driver for it. Could someone email or point me to a location for getting the sources. The few URLs posted in this topic don't return the code.

Jim

I Also have the same Systems With a few changes i Need Please A Mandrake 8.2 i586 please everything else got setup just no net

Please E-Mail me the driver! I think a don't a good one! Thaks!