Comment 226 for bug 129910

Calm down, guys. At least as far as we have our standard 80x24 terminals
working.

This issue is not an xorg driver issue, as Timo already noted. This issue
is caused because the kernel devs have blacklisted all the framebuffer modules.

As the modules have been knowingly blacklisted, this can be deemed as a
feature, not a bug. Let's see what we gain:

$ head -3 /etc/modprobe.d/blacklist-framebuffer
# Framebuffer drivers are generally buggy and poorly-supported, and cause
# suspend failures, kernel panics and general mayhem. For this reason we
# never load them automatically.

OK, so all framebuffer modules are blacklisted for a reason. The questions
I ask are:

1) Are all the fb modules of such a low quality?
2) Can we afford putting the best supported modules back in, so that some
users will still be able to use nice high-res ttys?
3) Is suspend/hibernate working better in gutsy because of the general
blacklisting?
4) If one blacklists fb drivers due to suspend/resume woes, should we take
the next step and blacklist fglrx because it doesn's support SLUB allocator?

Ok, ok, forgive my sarcasm on my last question.

Kyle M Weller escribió:
> Why is this marked invalid? This obviously effects Ubuntu Gutsy so marking
> it invalid is an invalid decision

--
----------------------------------------
Miguel Martínez Canales
    Dto. Física de la Materia Condensada
    UPV/EHU
    Facultad de Ciencia y Tecnología
    Apdo. 644
    48080 Bilbao (Spain)
Fax: +34 94 601 3500
Tlf: +34 94 601 5326
----------------------------------------

  "If you have an apple and I have an apple and
  we exchange these apples then you and I will
  still each have one apple. But if you have an
  idea and I have an idea and we exchange these
  ideas, then each of us will have two ideas."

  George Bernard Shaw