Bug 873366 - xvinfo reports no adapters on Intel HD4000 (regression from F17)
Summary: xvinfo reports no adapters on Intel HD4000 (regression from F17)
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 18
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-05 16:24 UTC by Aron Griffis
Modified: 2014-02-05 12:52 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 12:52:18 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
xvinfo, dmesg and Xorg.0.log on F18 (107.72 KB, text/plain)
2012-11-05 16:24 UTC, Aron Griffis
no flags Details
xvinfo, dmesg and Xorg.0.log on F17 (117.25 KB, text/plain)
2012-11-05 16:25 UTC, Aron Griffis
no flags Details

Description Aron Griffis 2012-11-05 16:24:42 UTC
Created attachment 638736 [details]
xvinfo, dmesg and Xorg.0.log on F18

Description of problem:
xvinfo reports "Intel(R) Textured Video" on F17, but on F18 it reports "no adapters present"

Version-Release number of selected component (if applicable):
kernel-3.6.5-2.fc18.x86_64
xorg-x11-drv-intel-2.20.12-1.fc18.x86_64

How reproducible:
every time

Steps to Reproduce:
1. install F18 on Ivybridge
2. run xvinfo
  
Actual results:
no adapters present

Expected results:
Intel(R) Textured Video

Additional info:
see attachments

Comment 1 Aron Griffis 2012-11-05 16:25:43 UTC
Created attachment 638737 [details]
xvinfo, dmesg and Xorg.0.log on F17

Comment 2 Adam Jackson 2012-11-14 19:53:42 UTC
[    17.910] setversion 1.4 failed

This typically happens because some other process (almost certainly plymouth) was holding on to the drm device so Xorg couldn't acquire it.  Do you still see this with current plymouth?

Comment 3 Aron Griffis 2012-11-20 23:35:46 UTC
Current plymouth seems to have fixed the problem. Thanks Adam.

Comment 4 Fedora End Of Life 2013-12-21 09:17:26 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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.

Comment 5 Fedora End Of Life 2014-02-05 12:52:21 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.


Note You need to log in before you can comment on or make changes to this bug.