On 11/19/2010 06:36 AM, tekos wrote:
>
> I made a test…I installed default kernel also and booted (I was using
> desktop kernel)…Wireless works fine…So could it be a kernel or a
> driver problem?
I am sounding like a broken recording and repeating myself, but an out-of-kernel
driver MUST be built for EXACTLY the kernel in which it is trying to be loaded.
Thus, 2.6.3X.Y.ZZZZ-default IS NOT THE SAME AS 2.6.3X.Y.ZZZZ-desktop. That is
likely what happened to you, and would have been seen in the dmesg output. It is
not a bug, but a defensive mechanism established by the kernel developers. In
the 2.4 kernels, this rule is not enforced and a lot of time was wasted trying
to debug the cases where a driver module was being forced into a kernel to which
it did not apply.
On 11/19/2010 11:06 AM, DaaX wrote:
>
> Hi lwfinger,
>
> I don’t undertsand what you are implying here. Do you mean that
> installing the default kernel was not a good solution?
No, it was a good solution because the extenal driver you installed was built
for the default kernel, but there was not one for desktop, or you downloaded the
wrong package.
> If it’s not a bug, how one knows that it is a defensive mechanism.
> unless you are close to the kernel developpment, nobody knows that.
I have stated many, many times that an out-of-kernel driver MUST be built the
the EXACT kernel you are running. Even the version of gcc used must be the same.
As to hiding the fact that a driver is not loading, it is prominently displayed
in the output of the dmesg command.