On Dec 18, 2005, at 6:08 PM, Maciej Żenczykowski wrote: >>> How do i know that the centOSplus kernel has support for my device >>> (in my case bt848 capture device). I must see the config file >>> right? But rpm doesnt put that config file into /boot > > if you know the module name for your device then you can check rpm > file manifest to see if it contains the appropriate module > >> Sometimes you need to compile your own drivers, since no one >> kernel has all drivers. Especially out of kernel drivers. > > Doubtful, a properly compiled module kernel can contain all the > drivers prebuild as modules - as far as I know this is what the > centosplus kernel does... I was not aware that the Centos kernel included other drivers, like loop-AES, which modifies/replaces the existing loop driver to support encryption. As well as some other drivers that Linus does not like like the LiS Streams package, and some associated drivers built with it. Another, fatal, use of the standard X86 kernel provided by Redhat, and I assume in the unsupported kernel, is the requirement of at least a 686 (or Athlon) CPU. When you have to support 586 based systems, you have to, at a minimum, recompile the kernel. And replace the 686 glibc with the 386 version. And replace the SSL libraries too.