Thanks for the pointer. I've read through the messages under bug 246269, and I'm not very much reassured.
As far as I can see, the conclusion is that Intrepid has been "switched" to a new frame-buffer, uvesafb, that doesn't work as it is supposed to, at least in part because the v86d supplied in the Ubuntu repositories was compiled against the wrong ?libc (and wasn't even included in the default install, despite being needed for the new uvesafb. The solution that presents itself to me as a user would be to switch back to vesafb until a working set-up with uvesafb can be provided, or to provide a version of v86d that does work. I know that an alpha version is a work in progress, but having a system that works does seem rather a basic requirement. I seem to be one of the lucky ones; now that I have discovered that my original problems were due to a usplash crash (thanks to your help) I can boot up without usplash and log-in, and shut down without crashing. Other people seem to be suffering worse problems, which prevent them from booting at all in some cases - all because uvesafb is not working correctly. For the record, having installed v86d, I am still getting the error -22 failure to load VBE, or whatever, at the start of the boot sequence. uvesafb shows up in lsmod, but does not seem to be active. As others have reported, modprobe uvesafb generates an error if I try to include the mode parameter. -- shutdown crashes, leaving Intrepid running but stuck https://bugs.launchpad.net/bugs/264571 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
