Comment 7 for bug 864466

Further testing shows that totextmode is both insufficient and unnecessary.

- If a framebuffer module is loaded so that the kernel has an fbcon, 'chvt 1' is sufficient to get a text console, and the panic() function already does this.
- If no framebuffer module is loaded, the kernel seemingly doesn't know how to change the console from graphics mode to text mode, regardless of how many times you call totextmode or chvt.
- We currently do not include any framebuffer modules in the initramfs by default. We could change this so that they're included unconditionally, but this would increase the size of the initramfs (possibly impacting boot speed) and would result in them being autoloaded by default (definitely impacting boot speed, as well as impacting boot experience since on intel this brings a modeswitch that clears the purple background).
- We could avoid the full overhead of having all the modules in the initramfs by only including vesafb. However, this precludes loading other framebuffer modules later for the same card, which means users would be stuck with vesafb instead of the native driver, making it impossible to resume from a 'break' and get the correct post-boot experience.

So this is definitely a 'wontfix' for oneiric. We should still do something to improve the handling of 'break=', but this isn't it, and any other solution is too risky for oneiric.