| Summary: | cannot boot into system with graphical mode installed with basic video driver | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Hongqing Yang <hoyang> | ||||||||||||||
| Component: | mesa | Assignee: | Adam Jackson <ajax> | ||||||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||
| Priority: | unspecified | ||||||||||||||||
| Version: | 17 | CC: | ajax, awilliam, g.kaviyarasu, jonathan, maxamillion, otaylor, robatino, samkraju, vanmeeuwen+fedora, walters | ||||||||||||||
| Target Milestone: | --- | ||||||||||||||||
| Target Release: | --- | ||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||
| OS: | Linux | ||||||||||||||||
| Whiteboard: | AcceptedBlocker | ||||||||||||||||
| Fixed In Version: | mesa-8.0.1-9.fc17 | Doc Type: | Bug Fix | ||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||
| Last Closed: | 2012-03-29 04:12:37 UTC | Type: | --- | ||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||
| Bug Depends On: | |||||||||||||||||
| Bug Blocks: | 752649 | ||||||||||||||||
| Attachments: |
|
||||||||||||||||
Created attachment 571022 [details]
program log
Created attachment 571023 [details]
storage log
Created attachment 571024 [details]
syslog
Created attachment 571025 [details]
xlog
Created attachment 571026 [details]
ifcfg log
The same error are also found in program.log that is installed without swap. There's nothing in your program.log that's a real error message. It's just that some programs write output to stderr. I believe the "Oh no!" message comes from gnome-shell, though. Reassigning. The system cannot boot into terminal one with F17 Beta RC1. Proposing as Beta blocker. Sounds somehow like Shell is trying to run via llvmpipe on VESA, and failing. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Discussed at 2012-03-26 QA meeting, acting as a blocker review meeting. Agreed that this is a blocker per the combination of Alpha criteria "The boot menu for all installation images should include an entry which causes both installation and the installed system to use a generic, highly compatible video driver (such as 'vesa'). This mechanism should work correctly, launching the installer and attempting to use the generic driver" and "Following on from the previous criterion, after firstboot is completed and on subsequent boots, a system installed according to any of the above criteria (or the appropriate Beta or Final criteria, when applying this criterion to those releases) must boot to a working graphical environment without unintended user intervention. This includes correctly accessing any encrypted partitions when the correct passphrase is supplied" - the effect of these is that a 'basic video' installation should boot to a working desktop, which this bug suggests is not the case. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers I just tested and can't reproduce this in a VM at least. Did a basic video install, after install, gdm and shell both run okay. Somewhat jerky, but they run. Hongqing, what hardware did you test on? Can you please provide some logs that would be useful here? As Chris says, this isn't an anaconda issue, it's Shell failing, so look in ~/.xsession-errors , maybe /var/log/messages . -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers I reproduced the same error with F17 Beta RC1. Below is my hardware detail: http://www.smolts.org/client/show/pub_5f3281fe-1b27-40d0-9caa-70d01ef9ce5d The ~/.xsession-errors file does not exist. Tim's 807003 seems somewhat similar - both radeons having trouble with vesa, though one generation different (r520 vs. rv620). -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers oh, if you get the 'oh no!' message when GDM should come up, look for /var/log/gdm/:0-greeter.log . -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers llvmpipe was super crashy with 16bpp until very recently. It's still broken for texture-from-pixmap but at least it won't crash. There's a mesa update in bodhi to fix that. mesa-8.0.1-7.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/mesa-8.0.1-7.fc17 Package mesa-8.0.1-7.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing mesa-8.0.1-7.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-4799/mesa-8.0.1-7.fc17 then log in and leave karma (feedback). ajax: is 807003 likely to be a dupe of this? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers mesa-8.0.1-9.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/mesa-8.0.1-9.fc17 mesa-8.0.1-9.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. |
Created attachment 571021 [details] anaconda log Description of problem: after installation , got the error "Oh no! Something has gone wrong." There are a lot of error in the program.log files. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: