A more likely scenario is that the compile crashes before completion when you attempt to
experiment with new and untested code. Trying to add support for a newer device to an
older kernel can also sometimes result in a compile crash.
It??™s also possible for you to end up with a tainted kernel. A tainted kernel is one where you
have introduced a module that isn??™t covered by the GPL or similar license. This can
happen when you??™re using hardware that requires a proprietary module (such as Nvidia
display adapters). If you compile the kernel with one of these proprietary modules, you
will see taint warnings.
CHAPTER 24 Kernel and Module Management 502
Should you run into this situation, you??™re down to two options: Remove the offending
module and wait for a solution from the kernel hackers, or try fixing the error yourself.
Most folks might want to take the safer course and wait for a fix, but if you think you
might like to help hack the kernel, this is your opportunity. Finding a solution not only
solves your problem, it might help millions of users down the road.
Pages:
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977