Short: Executing depmod seemed to solve my problem. Suggest closing the "bug". Long: I continuted playing around to find the reasons for the async reply. As it seemed to be related with GU-actions as I mentioned before, I tried to use the nvidia xserver instead of the nv xserver in xorg. After compiling using make-kpkg and installing I couldn't load the module (actually, I compiled it together with the kernel). Looking in /lib/modules showed that there were too directories coming from my last built of the kernel: /lib/modules/2.6.12.20060128 (containing the nvidia kernel object) and /lib/modules/2.6.12.20060128y (containing all other modules). Afer copying the nvidia kernel object to the other directory and a depmod, I could load it with modprobe. But then - instead of using the nvidia server as planned - I thought: "Ok, I've changed something. I should try it again with the nv xserver before switching so that I really would _know_ that the problem has been in the nv xserver if it would works with the nvidia xserver". So I tried it and voila - even trying hard to produce an async error I didn't succeed (with the nv xserver). So I didn't even try with the nvidia xserver because I blame having the wrong module dependencies caused the problem. (I always thought that depmod will be called automatically when compiling a kernel with make-kpkg). Conclusion: - Alays run depmode after compiling a kernel - openoffice is not guilty (even it's the only program that "showed" the misconfiguration). - I suggest to close the "bug". - If I should be successful in getting an async reply again, I will write again. Thank you, "sorry", and greetings, Philipp
Attachment:
signature.asc
Description: Digital signature