Description of problem: No compatible version of R128 driver available for F21. Version-Release number of selected component (if applicable): Using FedUp on an F20 system using this driver gives the warning: WARNING: problems were encountered during transaction test: broken dependencies xorg-x11-drv-r128-6.9.2-1.fc20.x86_64 requires xorg-x11-server-Xorg-1.14.4-13.fc20.x86_64 Continue with the upgrade at your own risk. How reproducible: Reliably Steps to Reproduce: 1. Run FedUp on a system relying on xorg-x11-drv-r128 2. Reboot Actual results: The system cannot get to a display screen Expected results: The system can get to a display screen Additional info: The bottom line is that F21 installs xorg-x11-server-Xorg.x86_64 1.16.2.901-1.fc21 installed which the only available version of xorg-x11-drv-r128 is unable to use.
(In reply to bob mckay from comment #0) > Description of problem: > No compatible version of R128 driver available for F21. This is expected. The package xorg-x11-drv-r128 has been retired in F21 with the following commit message: 2014-07-06: retired driver, because it does not support KMS: https://lists.fedoraproject.org/pipermail/devel/2013-August/188429.html > WARNING: problems were encountered during transaction test: > broken dependencies > xorg-x11-drv-r128-6.9.2-1.fc20.x86_64 requires > xorg-x11-server-Xorg-1.14.4-13.fc20.x86_64 This is a packaging bug. xorg-x11-server was supposed to obsolete xorg-x11-drv-r128 and its spec says: Obsoletes: xorg-x11-drv-r128 < 6.9.1-15 However, after the Obsoletes was added, the xorg-x11-drv-r128 package received one more update in F20 to version 6.9.2-1, so the Obsoletes does not cover it anymore. > Actual results: > The system cannot get to a display screen I guess it should work by falling back to the vesa driver. (Maybe you have a xorg.conf that prevents the fallback from working?)
Hi Michael; thanks for the explanation. So does this mean that there will be an update to xorg-x11-server to include xorg-x11-drv-r128 < 6.9.2-1 It's highly desirable, because otherwise users are stuck with permanent yum problems. I'm not sure why it didn't fall back to the vesa driver. It turns out that that machine is going to be retired in a couple of weeks, so I will just leave it at F20 until then.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. 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 21 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 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.