I'm no expert on the topic but I thought 2.6.16 did a few things to hotplug
which tended to break things ... I spent some time trying to get the UVC,
Kvaser and a couple of other drivers working on 2.6.16 before giving up and
going back to 2.6.15.
At any rate, here are a few things that I've found useful to check when
having kernel module compile problems.
- Make sure the right kernel source is there
- Symlink /usr/src/<kernelname> to where the kernel source actually is
(Redhat has a habit of putting it in non-standard places like
/usr/src/redhat/BUILD/<kernelprefix>). Make sure that <kernelname> matches
what uname gives you.
- If you download the kernel RPM and just install it normally (-Uvh or
whatever), you need to run "rpmbuild -bp" (at least I think it's bp) in the
SPECS directory to actually patch the kernel source
- If you're right out of ideas, actually try compiling and installing a
temporary kernel (this ensures that the source you have matches your kernel
- and that the source is there to begin with) - whilst you're at it, make
sure all the things you need are compiled into the kernel. You do this as a
last resort before you give up and go to bed - heck your computer might as
well be doing something useful whilst you dream about putting a hammer
through it right? ;-D
Hope this helps!
- Raymond
At 08:21 PM 26/04/2006 +1000, you wrote:
Hi all,
I'm just enquiring to make sure that my previous post about not being able
to install the drivers on an FC4 with a 2.6.16-1.2069_FC4smp made it
through to the group?
Regards,
Patrick
_______________________________________________
pwc mailing list
[email protected]
http://lists.saillard.org/mailman/listinfo/pwc
_______________________________________________
pwc mailing list
[email protected]
http://lists.saillard.org/mailman/listinfo/pwc
