Bug 876296 - unable to "test drive" fedora 17
Summary: unable to "test drive" fedora 17
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 17
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-13 18:41 UTC by williem
Modified: 2013-07-31 18:01 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-07-31 18:01:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
tar file containing log files (160.00 KB, application/x-tar)
2012-11-27 21:18 UTC, williem
no flags Details

Description williem 2012-11-13 18:41:07 UTC
Description of problem:the boot fails


Version-Release number of selected component (if applicable):


How reproducible:everytime


Steps to Reproduce:
1.download ISO image 
2.install using usb stick
3.boot from usb
  
Actual results:
The boot starts but nothing happens 

Expected results: fedora 17 test 


Additional info:I've had the same problem  trying to test fc15, thought that fc17 might solve problem

Comment 1 Josh Boyer 2012-11-14 20:24:21 UTC
There isn't enough information in this bug to even begin debugging it.  Fedora doesn't respin the release ISOs anyway, so we wouldn't be able to fix issues contained therein.

If you care to try the F18 beta when it comes out and let us know if there are issues, we might be able to fix them before the final F18 release.  The latest beta test ISOs can be found here:

http://alt.fedoraproject.org/pub/alt/stage/18-Beta-TC8/

Comment 2 williem 2012-11-15 19:34:36 UTC
Thank you for your thoughts. I did submit a bug report on fc15 back in spring. I was not helped perhaps because of my description of the problem. And oh yes I copied numerous files to the persons helping me. They could find nothing wrong.
I do not want to go through this again because it is ground that has been covered. I will now describe as much as possible what happens during the boot process. When the boot starts Fedora puts up a oval in the middle of the screen and starts to fill it with white. My fc14 does this rather smoothly and when it is filled with white it flashes the "f" in the oval. The login process starts after. This not the case with fc15 and fc17. The oval starts filling and about one third of the way the displays shutters and jumps and rectangular figure appears on the upper left side of the display. A short time later the whitening of the oval continues until finished. The display clears and displays a new background and stops. Nothing happens. I can do a "ctl + alt + f2" an get a login prompt. I can now login as root and issue stopnow command. I am leaning to a Graphics software or hardware problem. My computer is a Compaq presario CQ1. It has a 32 bit VGA intel.

I am hoping that if this is a software problem there might be something I do otherwise I might just get a new computer. It is amazing that fc14 works so good and fc15 and fc17 can not get off the ground.

Comment 3 Josh Boyer 2012-11-16 13:32:30 UTC
Regressions happen.  It's unfortunate, but true.

If you can get to a login prompt, then you might be able to provide people with information that will help them debug the problem.  If you aren't willing to do that though, it will remain unsolved.

Routing this to the intel driver for now.

Comment 4 williem 2012-11-16 17:58:27 UTC
You misunderstood me.  I do NOT get login prompt with fc15 and fc17. I enter "root" at the command line. There is NO login widget displayed. What do you have in mind for more information, remember I've been through this ad nauseam.

Comment 5 williem 2012-11-27 20:07:34 UTC
I ran fc18 and of course it failed. I got the some logfiles but do not know how to include them in this comment. please help.

Comment 6 williem 2012-11-27 21:18:35 UTC
Created attachment 653125 [details]
tar file containing  log files

these are the log files from failed fc18

Comment 7 Adam Jackson 2013-01-22 18:51:22 UTC
The X log here ends with the X server switching to a VT.  It won't do that of its own volition, did you switch VT yourself?

Comment 8 williem 2013-01-24 17:53:09 UTC
(In reply to comment #7)
> The X log here ends with the X server switching to a VT.  It won't do that
> of its own volition, did you switch VT yourself?

No, as stated before the screen jumps and a black square is displayed during boot. It is not smooth.

Comment 9 Fedora End Of Life 2013-07-03 19:29:43 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 10 Fedora End Of Life 2013-07-31 18:01:32 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.