I've changed plymouth 0.8.2-2ubuntu18 in natty so that, instead of disabling drm on nouveau at compile-time, it now accepts a 'plymouth :force-drm' parameter on the kernel command line: if that's omitted, then the behaviour is as in lucid and maverick (i.e. fall back to the plymouth frame-buffer renderer), but if it's present then plymouth will use the drm renderer again.
I'd greatly appreciate it if people who were affected by this bug back in lucid could try with the new plymouth and this kernel parameter, and report whether it still breaks. If it turns out that it's been fixed in the kernel in the meantime, then we can switch back to the drm renderer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/539655 Title: nouveau hard lockup in nouveau_gem_ioctl_cpu_fini -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
