Comment 12 for bug 21416

There are numerous reports on seemingly identical issues, all related to the framebuffer VTs / consoles not working when X is run. This occurs with varying hardware (and varying kernel versions), so the issue may be wider than previously suspected, and possibly related to something that these occurrences have in common.

However, even as these reports have much in common, I am hesitant to mark any as duplicates, since the hardware varies (e.g. four different graphics cards), and because the cause may or may not be the same.

As I summarised these reports, I find it beneficial to attach the summary to each report. Apologies to recipients of Ubuntu Bugs & Ubuntu X SWAT for having to receive multiple copies of the same.

A brief summary follows:

Four reports, with the common behaviour that the framebuffer consoles stop working _as soon as X starts_:
- Bug 21416 - reported by felix.rommel. Acer Aspire 1350 with a Via KN400 Unichrome graphics card.
- Bug 29407 - unsure if original report is related or caused by a different issue, but all comments are related. Comments by Ignacio Lago Fontán, Compaq Evo N600c, ATI Radeon Mobility M6 LY; also by Thilo Six.
- Bug 40297 - reported by kko. Matrox G450 graphics card.
- Bug 42974 - reported by Richard Laager. HP dv800 with a GeForce Go 7400 graphics card.

A fifth report, with identical behaviour (fb stops working with X running), but only after hibernate + resume):
- Bug 36904 - reported by kamome with "dapper flight5 on a via mII12000".

A further report that may or may not be related, but lacks details (i.e. does the fb not work at all, or only stop working after X has been started? what equipment?):
- Bug 42168 - reported by vertiger.