Bug 947210 - Video Not Supported
Summary: Video Not Supported
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 17
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 910970 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-01 20:15 UTC by Rusty
Modified: 2013-07-31 22:03 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-31 22:03:21 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Rusty 2013-04-01 20:15:48 UTC
Description of problem:


Version-Release number of selected component (if applicable): Both the Fedora 3.7.x and 3.8.x release of fedora 17


How reproducible: Boot up of the kernel on a Compaq laptop R3140US. when the start up goes to video mode, there is only display of vertical white and other colored lines covering most of the screen.


Steps to Reproduce:
1. Boot a kernel of 3.7.x or 3.8.x
2.
3.
  
Actual results: the video driver does not display the working of the kernel startup.


Expected results: the results of the startup of the different systems on the boot.


Additional info: I have reported this many times and there does not appear to be any work being done on the problem. the 3.6.x kernel video drivers work without any problems. I am not a heavy user nor a developer who understands the workings of the kernel anymore. I do believe it is related to the video driver for the nVIDIA driver. in version  3.7.x and 3.8.x a new version of one of the display drivers was installed that does not support the older version of the nVIDIA chip set for the display.

Comment 1 Rusty 2013-04-01 20:23:04 UTC
See also open bug 910970, which is related to another problem but the display was discussed during that bug.

Again, I am not a developer, I am a novice user and do not know much any more about the kernel nor its modules.

Comment 2 Josh Boyer 2013-04-01 20:23:51 UTC
*** Bug 910970 has been marked as a duplicate of this bug. ***

Comment 3 Rusty 2013-04-01 20:30:02 UTC
(In reply to comment #2) another bug reported by me about this is number 904690 - the same problem earlier version, but I could not supply the needed information so nothing is being done to my knowledge.

> *** Bug 910970 has been marked as a duplicate of this bug. ***

Comment 4 Fedora End Of Life 2013-07-03 21:10:54 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.

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 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 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 17'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 2013-07-31 22:03:25 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.

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.