Am Montag, 19. Januar 2004 21:34 schrieb Olaf Titz: > [CCd to linux-kernel and dvb lists. Context: SuSE 9.0, kernel 2.4.21, > ttusb_dec module fails] > Eeek. If the OP didn't even know if he needed the cipcb module, this > should mean he didn't knowingly start the CIPE driver, and[*] thus the > cipcb module was loaded by the modprobe dependency mechanism by virtue > of it defining a symbol called "crc32". > > modprobe shouldn't know of that symbol in the CIPE module at all, > because it's not meant to be exported. There are some definitions in > the module subsystem which deal with the exporting of symbols. I > suspect either CIPE or DVB (or both of them) needs a fix in this area. > Anyone here knows more? Correct, I didn't load cipe manually, I load the modules by insmod normally and since ttusb_dec claimed for crc32 (I didn't know which module would sadisfy this) I gave this module to modprobes control. > Another data point: crc32 isn't available in 2.4.21 at all, so it's > apparently(?) not a kernel configuration problem. But shouldn't that > mean that the ttusb_dec driver wouldn't run at all under that kernel? > [*] unless SUSE has really screwed it up and started a CIPE process by > default, but this is rather implausible as it needs nontrivial > configuration, and loading the module without the ciped process just > wastes memory. No, they don't Rafael -- www.pinguin-and-knights.org 2003 by Lontro
Attachment:
pgp00011.pgp
Description: signature