Bug 160950
Summary: | Chars on console lost when switching out of X11 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Michael Forrest <mef> |
Component: | xorg-x11 | Assignee: | X/OpenGL Maintenance List <xgl-maint> |
Status: | CLOSED DUPLICATE | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-06-25 10:57:48 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Michael Forrest
2005-06-19 07:23:59 UTC
Please review bug number 161242 everyone, and try using the libvgahw.a module that is linked to from that bug report. This is just a hunch I'd like to test to see if the problem reported on Matrox and Intel hardware is also causing problems on Trident and other hardware. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=161242 Anyone who can test this and provide feedback, would be greatly appreciated. Thanks in advance. Tried shutting X down (which gave the blue borders problem, as expected). Replaced libvgahw.a with same from FC3, started X )with startx), then used Ctrl-Alt-Fn to switch back to tty1. Blue border was still there, still hiding the characters in column 0 as before. BUT, then rebooted completely, tried same test, and no more blue border on the 80x25 textmode screen! So I think we've narrowed down the problem to that particular module. Strange how it wasn't fixed with a new X server with the FC3 moduoe in place - could it have kept some bad code in the kernel, which was only removed with a reboot? It will be mighty strange if this turns out to be a gcc 4.0 bug! Anyway, this issue has been worked around for me. My deepest thanks to Mike Harris for taking the time to attach that message to the many reports of corruption. Made it easy to workaround. Marking this as a duplicate. *** This bug has been marked as a duplicate of 161242 *** Oh, forgot to confirm that my display is an i810 Intel chipset on a Gateway E1600 Motherboard (Pentium III - 800 Mhz). Hope we can find the real cause! |