Quoting "David Burgess" <[email protected]>:

On Wed, Mar 9, 2011 at 10:28 PM, ttargownik <[email protected]> wrote:

I have tried re-building a custom kernel within the CHROOT environment, and
I have tried building the module from source against the appropriate kernel
headers, to no avail.

As long as you're building kernels, why not build in your driver in
statically, then you don't have to mess with modules and the initrd?

db

Good point db, but it seems something is going awry in the compilation anyhow. You are sure that you got the .config file correct Tomas? In the config for your newly built kernel there should be a line in the config something like:

CONFIG_R6040=m

If you selected to build as a module, or:

CONFIG_R6040=y

if you selected to build it statically. Sorry if you knew this already Tomas and I'm repeating the obvious, I have no idea how much experience you have of building kernels.

So for the kernel I just compiled I run "grep CONFIG_R6040 /boot/config-2.6.38-beng" and get the result "CONFIG_R6040=m".

So, just before you compile, check the .config file in your kernel source directory, and see if that line is there.

Cheers,
==
From Ben Green

Attachment: pgpt4JfrNhvNY.pgp
Description: PGP Digital Signature

------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Reply via email to