Description of problem: Display connected to VGA port will loose signal as soon as fbdev will kick in during system bootup process. Version-Release number of selected component (if applicable): kernel 3.3.0-0.rc3.git2.2.fc18.x86_64 How reproducible: Always. Steps to Reproduce: 1. Connect display to VGA connector on system with AMD A6-3500 APU with Radeon(tm) HD Graphics; 2. Start system. Actual results: Display will loose signal after fbdev is being started during system bootup. Also, any following X-org driver will not remedy it. Expected results: Display should remain on and working. Additional info: Base Board Information Manufacturer: ASRock Product Name: A75M-HVS BIOS Information Vendor: American Megatrends Inc. Version: P1.60 Release Date: 10/28/2011 CPU: AMD A6-3500 APU with Radeon(tm) HD Graphics Luckily, if to connect display into HDMI port there it is still working as expected.
This sounds like an issue with the radeon driver at first glance.
did this ever work? on any previous kernel?
I do not recall as seeing that working on that particular computer.
Fix summary, we don't ship radeonfb, just the radeon KMS driver.
I may not know that thing, but does the xorg driver need a X to run? That is not the case here as my problem does start way before any X being run, in fact I've disabled booting into X session - in my case initial console mode change will destroy display and according to /proc/fb I have radeondrmfb running. Isn't it part of a kernel not from the xorg driver set?
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
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.