Description of problem: F19 Live on HP DL130 G3 produces vertically and horizontally wrapped grpahocs Version-Release number of selected component (if applicable): How reproducible: Normal live run on a HP DL 140 G3. Steps to Reproduce: 1. Normal live run on a HP DL 140 G3. Actual results: Vertical and horizontal wrap, with possible graphics temporary are being displayed. Expected results: Normal graphic.
Created attachment 734888 [details] Vertical and horizontally wrapped graphics.
Please provide the information listed at https://fedoraproject.org/wiki/How_to_debug_Xorg_problems - at least as much of itas possible. Thanks!
Thanks Adam, I will do a F19 Live instillation and go through the same process as with bug https://bugzilla.redhat.com/show_bug.cgi?id=951643. As soon as I can hopefully tomorrow.
Is it possible to modify the priority and severity of this bug as I had problems when first posting in Bugzilla. It would be good to get this bug solved for F20. And an Xorg.conf file for VESA in the interim.
This is likely the same bug as 951643 but for F19, so let's re-assign it to mga also (see 951643: the system in question in fact has a Matrox adapter, not a Rage XL, according to the attached logs).
Is there any movement on this as I really need to get my server updated asap.
it's not going to be a high priority for, well, anyone, really, I'm afraid - Matrox cards are a pretty minority pursuit these days. Why do you need graphics for a server anyway? It shouldn't be too hard to write an xorg.conf snippet to use the vesa driver for your card. Or you could just 'yum remove xorg-x11-drv-mga' and that should force it to fall back to vesa.
we do actually support matrox g200se adapters found in servers as a priority, not so much the ATI RageXL which should work but is less of a use case.
please attach the dmesg and Xorg.0.log
I am not sure how to get a dmesg or Xorg.o.log from F19. If you look at the following bug you will see the F18 logs and screen shots for when we were solving that. Presumably the same mods need forward porting from F18 to F19 and rawhide. https://bugzilla.redhat.com/show_bug.cgi?id=951643
I created https://bugzilla.redhat.com/show_bug.cgi?id=982282 against F19 and https://bugzilla.redhat.com/show_bug.cgi?id=982300 against rawhide
Then there were still problems with F18 Matrox MGA graphics miss functioning on some Menus and Dialogs as another bug https://bugzilla.redhat.com/show_bug.cgi?id=1018624
I have tried installing F19 on the HP DL140 G3's but I cannot get Anaconda to install Fedora due to screen mode problems I have tried Basic Mode install but even this behaves improperly, and cmdline mode still tries to access X - I filed a bug for this https://bugzilla.redhat.com/show_bug.cgi?id=968037
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.