Aurelien Jarno <[EMAIL PROTECTED]> writes: > Everything you sent me in your previous mail seems to be ok. I still > don't know why could cause the problem you have, and as I can reproduce > it here, I have to ask you some questions again...
Actually, the problem may be solved. I recently compiled kernel 2.6.14, and for whatever reason, it failed if I had modules_image on the command line before kernel_image. Once I figured this out, and switched them, I went ahead with the install. And the taint message disappeared.... :P Anyway, my guess is that it has something to do with the way make-kpkg was handling compiling the modules (a kernel-package bug?). I'm afraid I don't know enough about the process to have an informed guess as to what that might be, though. The other possibility, I guess, is that it's a change in linux-2.6.14, which might make more sense as I'm pretty sure I didn't usually have modules_image on the make-kpkg command line first -- just the past few times. Anyway, if you'd like me to try to narrow it down a bit I can do so (e.g., by compiling 2.6.12 + rt2500 with modules_image both first & second) I can do so, but I'm not sure it's worth the effort if this issue is unique to me. -- Jeremy Hankins <[EMAIL PROTECTED]> PGP fingerprint: 748F 4D16 538E 75D6 8333 9E10 D212 B5ED 37D0 0A03 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
