© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Actually, as of linux-image-
Without having read the relevant kernel source, I'd still venture that one of the following causes might be our culprit:
1) the kernel doesn't offer management of module loading order dependencies (unlikely, but you never know).
2) the kernel offers management of module loading order dependencies, but KMS-related modules don't use it (unlikely, but you never know).
3) the kernel offers management of module loading order dependencies, KMS-related modules use it, but in an incorrect way.
4) the kernel offers management of module loading order dependencies, but it is broken, so all attempts by KMS-related modules to use it fail miserably.
Basically, we need a systematic method for loading modules and their dependencies in a predictable order, always. Right now, either we're lacking this or what we have doesn't work as intended.