hmmm... seems like I'm writing to myself .. LOL!
Anycase, just as an update - got things working with the LAN and figured out a whole bunch of things about linux in getting there. All this may sound really noobish to all you experts out there, but seems I've just discovered stuff for myself which makes me 1% more knowledgable in linux than I was a day or two ago.
Lesson #1:
you may have multiple "kernels" installed on your machine at any given point in time. Running "uname -a" will tell you what
kernel source you're presently running on your machine.
Lesson #2: Kernel Sources (... or Kernel headers)
- Kernel sources are somewhat different than the actual kernel that's running your machine. Kernel sources are what you need to make drivers or programs so that they run at their peak efficiency on your machine. Your kernel sources and the kernel must be of the same version if you decide to make drivers or programs.
- Kernel sources are found in /usr/src/ directory.
- Aside from using the "update" or "up2date" feature to upgrade your kernel you may want to have "kernel sources" installed too. These are needed if you want to make drivers from source. What that means is that each system is different and because each system is different you get a chance to make drivers that will fit your configuration even better than some wholesale "pre-made" drivers.
Lesson #3:
There is a biiiig difference between
a) kernel-source-blablabla.rpm
b) kernel-blablabla.src.rpm
The "kernel-source" file is what you need to create the "kernel header" files (which are stored in /usr/src/ directory. The "kernel-source" rpm already comes with "pre-made" updates so you don't have to play around all day trying to figure out what to update and what to leave alone.
The "kernel-source" rpm installs your kernel headers. Without these , you cannot make your own programs or drivers.
The "src.rpm" is a collection of various bits of either a kernel or other programs that are needed to make or compile your own kernel or programs. There are a huge number of options if you use these to make a kernel - not advised for anyone that's new to linux ...
-----------------------------------------------------------------------------------------------------------
How to install those pesky Broadcom drivers without errors??
This is how I made and installed the Broadcom 4401 (Broadcom 440 10/100) drivers on my machine under redhat 9:
Note: if you have limited internet access or if you have no internet access from redhat it's best to download all the components before proceeding.
***** STEPS 1-4 OPTIONAL ******
****
if you do not wish to install new or updated kernel go straight to step 5) ********
*****************************************************************************************
1 - to avoid hassles make your drivers for the newest kernel possible. This way you'll be up to date on your kernel and won't have to bother re-installing the drivers if you upgrade the kernel after installing the drivers in the first place. Really simple:
2 - Download and install the latest Red Hat Linux kernel and kernel source packages:
- get the kernel-<version>.i386.rpm
- get the kernel-source-<version>.i386.rpm
https://rhn.redhat.com/errata/RHBA-2003-263.html
(that URL may change, so go here:
http://www.redhat.com/support/resources/howto/rhl9.html and select "bug fixes")
3 -
Install each of those by opening a console (terminal),
logging in as root and typing:
--> type: rpm -ihv kernel-<version>.i386.rpm
... and
--> type: rpm -ihv kernel-source-<version>.i386.rpm
(You will see a little progress bar in the console/terminal window)
4 - Reboot and
select the new kernel version at boot-up.
... make sure you're running the right kernel before continuing or this won't work at all. Once you'ree all booted up and logged in, open a terminal/console and run "uname -a" --- this will tell you if you are running the same kernel sources as your actual installed kernel.
====: if you followed steps 1-4 then go straight to step 6) ====
*************************************************************************
5 - First it's time to make sure you have the kernel-source installed on your machine so that you can make the drivers for your Broadcom NIC.
Open a console and
--> type: uname -r (tells you kernel version - to compare with next result)
--> type: cd /usr/src/ and type "ls -l"
This will let you know if you have kernel headers installed - needed to make and install the Broadcom drivers and you can compare if you have the same kernel as your kernel headers. The output should read something like this:
This example shows the kernel headers for version 2.4.20-6 are installed. If you have nothing showing after giving the command "ls -l" then go to step 1 of this procedure and install the kernel headers (kernel source)
Code:
[name@localhost]$ ls -l
total 3
drwxr-xr-x 2 root root 48 Jan 24 2003 debug
lrwxrwxrwx 1 root root 14 Sep 22 17:42 linux-2.4 -> linux-2.4.20-6
drwxr-xr-x 16 root root 656 Sep 22 17:42 linux-2.4.20-6
drwxr-xr-x 7 root root 168 Apr 7 15:51 redhat
6 - download the latest "::BCM4401::"drivers from Broadcom - here -->
http://www.broadcom.com/docs/driver-download.html
7 - Install the "Broadcom" source RPM package:
Open a terminal/console, log in as "root":
--> type: rpm -ivh bcm4400-<version>.src.rpm
(this makes a "spec" file which is a compilation of files that will build the final installation file!)
8 - Go to the location where the "spec" file you just made is stored:
--> type: cd /usr/src/redhat/SPEC
--> type: rpmbuild -bb bcm4400.spec
(if you get an error, type: rpm -bb bcm4400.spec)
9 - what you just did is create the FINAL installation file for your Broadcom driver! And the best part is it's taylor-made for your computer!! Now go to where that "compiled" rpm file is stored:
--> type: cd /usr/src/redhat/RPMS/i386
--> type: rpm -ihv bcm4400-<version>.i386.rpm
10 - FINISHED!!! reboot your computer and during the boot Redhat will immediately recognize that you have a new NIC called Broadcom 440 100baseT and ask you to configure it. Just put in your ISP's values like in Windows and continue booting.
(make sure you boot into your new kernelby selecting it at boot if you chose to update your kernel specified in steps 1-4)
----> Log in as yourself and get on the Net.
That's how I did it. Hope it helps whoever's reading this.
//Canon
Broadcom 4401 and Red Hat 9 - kernel headers?
(gripe) I cannot comprehend why Red Hat would not support or provide a workaround for a LAN chipset that is not only popular but widely used by major mobo manufacturers like ASUS, Abit and MSI. For a new Linux user to deal with such a relatively small but very significant issue is enough to turn people away from using Linux - and judging by this and other forums, that actually does happen (which I find really sad, incidentally). Interestingly, not only does every other competitive major distro immediately recognize the card there's never even a question as to onboard LAN eth0 issues whatsoever. Why can't/doesn't Red Hat recognize this and deal with it accordingly???? (/gripe)
Thanks for your rantings. I was lost until I found your post. Your instructions worked perfectly for me.
