Bug 855220
| Summary: | Kernel 3.5.3-1.fc17.x86_64 fails normal boot on an Acer Aspire One 722 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jim Bray <cashmundy> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 17 | CC: | artkun, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, ta.very.much.mate |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-12-20 15:59:33 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Jim Bray
2012-09-07 02:46:19 UTC
This kernel is now in FC17 updates. It can be booted by editing the boot sequence to boot to single-user. On normal (multi-user) boot, it reaches the point at which it wants the password to decrypt the filesystem, at which point it switches to graphics, displays vertical bars for about 5 seconds, and then acts hung, but can be rebooted via alt-sysrq commands. If booted with "s" appended to the linux grub2 command-line, it correctly enters some graphics mode, requests the password, and reaches single-user, and then finishes booting normally on exit from SU. 3.6.0-0.rc4.git2.1.fc18.x86_64 boots normally. It is unusable due to X consuming all CPU, but that is a separate issue, hopefully just an incompatibility. F17 should get a 3.6 update this week sometime. We'll mark this as POST for now and assume it's fixed with that update. If you test it and it fails still, please comment here. kernel-3.6.1-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/kernel-3.6.1-1.fc17 Sorry, can't test it. The Fedora 18 Alpha installer wiped my disk without warning, Win7 and Fedora gone, can't recover anything with testdisk. Switched to Linux Mint LMDE, doubt I will ever try Fedora again. (In reply to comment #5) > Sorry, can't test it. The Fedora 18 Alpha installer wiped my disk without > warning, Win7 and Fedora gone, can't recover anything with testdisk. > Switched to Linux Mint LMDE, doubt I will ever try Fedora again. Well, I'd be more careful if I decided to try Alpha version of a distribution like Fedora. Good point. I'm sticking with Alphas of other distributions from now on. (In reply to comment #7) > Good point. I'm sticking with Alphas of other distributions from now on. If you like bleeding edge, you should try Arch. It's a bit more difficult to install, but at least it's more stable than Alphas of traditional release model distros. (In reply to comment #5) > Sorry, can't test it. The Fedora 18 Alpha installer wiped my disk without > warning, Win7 and Fedora gone, can't recover anything with testdisk. > Switched to Linux Mint LMDE, doubt I will ever try Fedora again. Unfortunate. Did you read the release notes before you tried the Alpha? This issue was pointed out there. Apparently RedHat/Fedora has developed a Microsoft-like attitude that wiping data is to be expected. I didn't read the release notes. If I was to buy a car, I wouldn't read the owner's manual looking for warnings that the car was prone to explosion. In my fairly wide and long experience, the rest of the linux world doesn't seem to think releasing disk-eating ISO images is quite the thing. I'll keep Arch in mind.I've had good luck with Debian/unstable for most of the last 15 years ir so, tried quite a few others, always bleeding-edge. What is so disturbing in this case is that it was known the installer would trash the disk without warning, and this, by an 8 to 5 vote, wasn't considered a big problem. See bug beliw for details. https://bugzilla.redhat.com/show_bug.cgi?id=855976 Writing on a phone, can't fix the typos, so s/i/o We thank you for testing nonetheless. Good luck in your travels elsewhere. Thanks. Good luck with Fedora. I was favorably impressed with 16 and 17. A lot of things "just worked" which require tinkering in Debian. Package kernel-3.6.1-1.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 kernel-3.6.1-1.fc17' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-15855/kernel-3.6.1-1.fc17 then log in and leave karma (feedback). kernel-3.6.1-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. |