Bug 1257345 - Fedora Workstation 22 does not boot on ASUS X553MA laptop
Fedora Workstation 22 does not boot on ASUS X553MA laptop
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: LiveCD (Show other bugs)
22
x86_64 Linux
unspecified Severity unspecified
: ---
: ---
Assigned To: Matthias Clasen
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-08-26 16:59 EDT by Victor
Modified: 2015-08-30 15:04 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-08-30 15:04:12 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Boot process hangs up entirely at this point, removed "quiet" argument (1.23 MB, image/jpeg)
2015-08-26 16:59 EDT, Victor
no flags Details

  None (edit)
Description Victor 2015-08-26 16:59:47 EDT
Created attachment 1067410 [details]
Boot process hangs up entirely at this point, removed "quiet" argument

Description of problem:
Boot process hangs upon reaching a certain point.
Version-Release number of selected component (if applicable):
Fedora-Live-Workstation-x86_64-22-3.iso

How reproducible:
Regular boot from USB/DVD live image

Steps to Reproduce: N/A

Actual results: Normal live install bootup

Expected results: 
Hangs on the following line
"Started Load/Save Screen Backlight Brightness of backlight:intel_backlight

Additional info:

I managed to load the live install properly by adding the argument "modprobe.blacklist=i915" to the boot command. 

The laptop is running on an Intel BayTrail M 3540 Pentium processor, no dedicated graphics chip.
Comment 1 Victor 2015-08-30 12:38:59 EDT
UPDATE: The module blacklist only works if the laptop is running on batteries. Attempting to boot while plugged in will not work, regardless of the module being blacklisted or not.
Comment 2 Victor 2015-08-30 14:09:36 EDT
UPDATE #2: After a couple more trials, I pinned down the issue to the laptop's firmware. Booting in Legacy mode worked without any modifications to the default boot arguments, so this may be a UEFI implementation issue on the manufacturer's side.

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