Hide Forgot
Description of problem: Booting F16 TC2 Version-Release number of selected component (if applicable): F16 TC2 How reproducible: always Steps to Reproduce: 1. TC2 on usbstick using livecd-tools 2. Boot 3. Actual results: Black screen Expected results: GNOME 3.2 shell opens. Additional info: rd.blacklist=radeon solves this partly (radeon can't be used) rd.blacklist=i915 solves this partly (i915 can't be used)
Did earlier versions of F16 test releases work?
What kin of machine is that? (Manufacturer and model.)
I will gain access to that machine on tuesday again and will post it's smolt uuid - it's an HP Envy 13. I didn't test any previous versions of F16, but will also do this on tuesday.
It is this hardware: http://www.smolts.org/client/show/pub_2f0ab03f-dea2-4603-81ef-eea4b74e56e5 Additional informations nedded?
F16 alpha work without this bug. Also switching to DIS and IGD cards works.
[mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update.
I'm also seeing this problem on F16 kernel-3.3.1-3. Using AMD Radeon HD 6450 and onboard Intel graphics. When using the discrete graphics card the onboard graphics does not recognize screens (blank screen). lspci recognizes both graphic controllers. Please let me know if you need any additional testing or information.
Is this still being seen in 3.4 or 3.5 kernels?
# Mass update to all open bugs. Kernel 3.6.2-1.fc16 has just been pushed to updates. This update is a significant rebase from the previous version. Please retest with this kernel, and let us know if your problem has been fixed. In the event that you have upgraded to a newer release and the bug you reported is still present, please change the version field to the newest release you have encountered the issue with. Before doing so, please ensure you are testing the latest kernel update in that release and attach any new and relevant information you may have gathered. If you are not the original bug reporter and you still experience this bug, please file a new report, as it is possible that you may be seeing a different problem. (Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).
I can not test this anymore, as the machine has died. RIP.