Charles,
I didn't see your email address in time to cc you on the original help request. I would appreciate it if you could help me find the answer to my problem. Otherwise, I will continue my search elsewhere.
Thanks,
Ryan
-----Original Message----- From: Hammond, Ryan E. To: '[EMAIL PROTECTED]' Sent: 3/3/2003 1:34 PM Subject: [leaf-user] Help w/ bcm5700.o module for Dashstein branch
I am trying to use the Dashstein floppy (kernel 2.2.19) and Dashstein CD )(v 1.0.2) on a Dell PowerEdge 2650 server. This server has built-in dual Broadcom gigabit ethernet cards, which use the bcm5700.o module. Thanks to this list (http://www.mail-archive.com/[EMAIL PROTECTED]/msg11290.ht ml), I've found a bcm5700.o module that will load under the Bering branch. However, I receive 15-20 unresolved symbols when I try to insmod this module under Dashstein.
Can someone point me to a precompiled module, or help me figure out how to roll my own for this LEAF branch?
I doubt a pre-compiled version of this module exists for Dachstein's 2.2.19 kernel, and it's not suprising the module from a 2.4 series kernel won't load properly.
I'd compile this for you, but I lost my leaf develoment environment when a HDD crashed and I have not yet rebuilt it.
If you want to build the module yourself, you can simply download the Dachstein kernel source:
http://leaf-project.org/devel/cstein/files/kernels/Dachstein-source.tar.gz
...which along with a 2.2.19 kernel source tarball (from kernels.org or elsewhere) will allow you to build a Dachstein kernel.
See the readme file contained in the tarball for details, but basically you run an included script to create a patched kernel source tree, copy the appropriate kernel config file to .config, run "make menuconfig" and "make dep", and you've got a Dachstein kernel source tree.
Once you have a valid kernel source tree, you can compile any kernel modules you need. As long as you don't change the kernel config, you should be able to use any compiled modules with the distributed Dachstein kernels.
NOTE: You don't have to do this on a leaf development system with old C libraries. Since the kernel does not link with any external source code, you can build the kernel and new modules on any box with a version of gcc installed that will correctly build the linux kernel. Just don't run "make install" or "make modules_install". :)
NOTE: One other thing...some module makefiles try to "autodetect" the kernel source code by looking at the currently running kernel and trying to find an appropriate source tree in one of several typical locations (ie the recent intel driver modules). You may have to "short-circuit" this process to get the module to compile against the correct kernel source tree if the broadcom modules do something similar. Just holler if you get stuck with anything, and I can probably get you going.
-- Charles Steinkuehler [EMAIL PROTECTED]
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
