Bug 1080177 - Kernel 4.15.* doesn't bot any more on a Lenovo L450 i5-5200U
Kernel 4.15.* doesn't bot any more on a Lenovo L450 i5-5200U
Status: RESOLVED NORESPONSE
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Kernel
Current
x86-64 openSUSE Factory
: P5 - None : Normal (vote)
: ---
Assigned To: E-mail List
E-mail List
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-02-08 22:35 UTC by Joop Boonen
Modified: 2018-06-16 12:25 UTC (History)
3 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---
tiwai: needinfo? (joop.boonen)


Attachments
Lenovo L450 i5-5200U boot kernel vmlinuz-4.15.2-1-default (1.62 MB, image/png)
2018-02-15 14:59 UTC, Joop Boonen
Details
journalctl --boot=-1 (failed session with nomodeset) (123.60 KB, text/plain)
2018-02-16 12:25 UTC, Joop Boonen
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Joop Boonen 2018-02-08 22:35:03 UTC
The Lenovo L450 doesn't boot any more with kernel 4.15.* .
The system switches the monitor off and doesn't ask the encryption password.
Comment 1 Jiri Slaby 2018-02-13 09:53:30 UTC
could you remove splash=silent and quiet kernel boot options in grub and see if you can see the reason?
Comment 2 Joop Boonen 2018-02-15 14:59:41 UTC
Created attachment 760276 [details]
Lenovo L450 i5-5200U boot kernel vmlinuz-4.15.2-1-default

After "fb: switching to inteldrmfb from EFI VGA" the monitor turns black and switches off.
Comment 3 Takashi Iwai 2018-02-15 16:33:11 UTC
Try to boot with "nomodeset" option in addition to the removal of "splash=silent" and "quiet".  This will disable the i915 graphics driver, so it may reach to a further point.
Comment 4 Joop Boonen 2018-02-16 12:25:18 UTC
Created attachment 760371 [details]
journalctl --boot=-1 (failed session with nomodeset)

I can now enter the unlock password, the system continues booting boot still suspends.

I've attached the "journalctl --boot=-1" (is the failed boot) messages.
Comment 5 Takashi Iwai 2018-02-16 12:53:10 UTC
So far, so good.

Could you remote-login at this state?  If yes, login, and run

  echo 0x0e > /sys/module/drm/parameters/debug
  modprobe -r i915
  modprobe i915 modeset=1

as root.  This will re-load the i915 driver, and you'll likely have a non-working display.
Then check the kernel log via remote login.
Comment 6 Jiri Slaby 2018-06-16 12:25:40 UTC
Closing due to lack of response.