Umm, no. Haven't tested on Feisty. What my last two comments mean, on Dapper,
is this:
- First, with boot parameters amounting to "vga=normal" ("no special vga
options", i.e. vesafb not used), this problem isn't actual and can't be tested.
- Second, after I passed "vga=791" to the kernel at boot time, the vesafb
worked correctly, showing the expanded console mode (and the splash appeared
accordingly smaller), _and_, more importantly, the consoles continued to work
even after X had been started.
Thanks for your concern, though.
PS. You may notice I edited the title earlier to remove the reference to
Dapper. I hadn't myself met the problem on Dapper, at the time - only
reports of it from other people. (I have since stopped referencing other
people's experiences in my reports. ;-) So, I can't personally verify
that the problem existed on Dapper, but if it did, an update has fixed
this.
--
X completely corrupts VesaFB Virtual Terminals' image
https://launchpad.net/bugs/40297
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
