Bug 1257345

Summary: Fedora Workstation 22 does not boot on ASUS X553MA laptop
Product: [Fedora] Fedora Reporter: Victor <victorvalenca>
Component: LiveCDAssignee: Matthias Clasen <mclasen>
Status: CLOSED NOTABUG QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: victorvalenca
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: 2015-08-30 19:04:12 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:
Attachments:
Description Flags
Boot process hangs up entirely at this point, removed "quiet" argument none

Description Victor 2015-08-26 20:59:47 UTC
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 16:38:59 UTC
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 18:09:36 UTC
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.