On Fri, Jun 19, 2009 at 06:27:14PM -0000, Bryce Harrington wrote: > From the upstream bug it sounds like everything's working now? Was it > purely just config issues, or are there any adjustments needed for X?
Well, from my point of view it was primarily a configuration issue; I've been poking at initramfs-tools and usplash to see how to get them to interact with KMS in a vaguely sensible way, and had loaded i915 without also loading the AGP implementation for my hardware (intel_agp). However, it does seem rather too easy to shoot yourself in the foot in really subtle ways with this stuff right now. It seems to me that early userspace that's trying to bring up KMS ahead of other module loading in order that it can have graphics support in place from the beginning has a bit of a hard time of it. As far as I can see, you need to load any AGP driver that matches something in modules.alias (or I suppose you could just try them all but that'll be slow), and then try the various KMS-capable DRM drivers. Thinking about it, while X is a rather spectacular victim of this, I don't know if there's anything it can do about it itself. I assume that it's just trying to innocently use the DRM driver, and it's really the DRM driver that's got itself hideously confused? -- Sluggish text scrolling, 100%CPU after upgrade from 2.7.1 (UXA bug) https://bugs.launchpad.net/bugs/388368 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
