Public bug reported:
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.
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
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
Why this is a bug:
Text mode 80x25 is very useful for doing work on muds and the kernel
development. It's snappy and fast. Forcing it out of existence with
hard code is improper forcing of system policy.
+
+ 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.
** Description changed:
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
-
- Why this is a bug:
-
- Text mode 80x25 is very useful for doing work on muds and the kernel
- development. It's snappy and fast. Forcing it out of existence with
- hard code is improper forcing of system policy.
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.
--
Can't disable fbcon
https://bugs.launchpad.net/bugs/483301
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help : https://help.launchpad.net/ListHelp
