kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #35929
[Bug 483301] Re: Can't disable fbcon
Shentino, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/483301/comments/15
regarding this being obsolete. For future reference you can manage the
status of your own bugs by clicking on the current status in the yellow
line and then choosing a new status in the revealed drop down box. You
can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/483301
Title:
Can't disable fbcon
Status in “linux” package in Ubuntu:
Invalid
Bug description:
Binary package hint: xorg
I just found out that a dependency in fbcon is hard-coded in Xorg for
whenever kernel mode switching is used.
Attempting to manually hide fbcon.ko results in massive screen
corruption.
Version: Karmic Koala
Up to date as of: Nov 15
Expected outcome:
Without fbcon, switching VTs should have dropped the screen back into
text mode. The kernel or whatever code handling the mode switch
should have noticed that it needed to go into text mode, and actually
done so.
Actual outcome:
Without fbcon, the screen got horrendously corrupted. Almost as if
the console was treating the video memory as if it was in text mode,
but the screen was still in graphics mode.
Why this is a bug:
Text mode 80x25 is very useful for doing work on muds and the kernel
development. I use it extensively because it's fast and snappy.
Making the console a framebuffer slows things WAY down.
Switching between text and graphics modes shouldn't result in
corruption. Attempting to force-load fbcon is not only an apparent
kludge, but it's also an improper forcing of system policy.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/483301/+subscriptions