Red Hat Bugzilla – Bug 64409
Driver build problem for kernel 2.4.9-21 and 9-31
Last modified: 2007-04-18 12:42:25 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 4.0)
Description of problem:
In order for me to build my driver that supports the 2.4.9-21 and 9-31 kernel,
I must be booted under the correct kernel image. This is even though I am
pointing to the correct kernel tree. I will attach a more extensive description
when I receive the response message.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. You will be unable to reproduce this problem with out my source
Created attachment 56304 [details]
This is a detailed description of the problem I am experiencing
Ok it looks like you are following the wrong procedure to build drivers.
One does NOT need to rebuild or reconfigure ANYTHING in /usr/src/linux-2.4.X-Y
to build drivers against it. All needed info for the shipped kernels is already
and will be DESTROYED if you reconfigure the kernel.
And yes to use that info it's simplest to reboot into the relevant kernel; it
then Just Works(tm).
That's how it's designed, so that people can have modules that auto-build on
boot (when needed).
I assume you ship source with your module; we can help you to get such an
auto-building set up.
We do not provide kernel source for our driver. In addition, I can not build my
driver if I simply load the kernel source (via the rpm) on my build system. It
does not know whether I am building for an smp or uniprocessor. I use spinlocks
so this is important. Also, the modules directory which contains the name
mangling is not present so this will cause a problem until I run the "make dep"
as I described in the attachment. Also, can you explain why this problem only
occurs on the 9-21 and 9-31 kernels? (please see description in the attachment)
I do not experience this problem on the other Redhat kernels (2-2 and 7-10) and
I followed the exact same steps as described in the attachment.
This process works for us in our testing. Without a reproducer,
there is no way we can help. It sounds like you need support,
rather than a bug fix, and we do have a support department who
have the skills needed to help you.