|
Bugzilla – Full Text Bug Listing |
| Summary: | Laptop external monitor capable, laptop screen goes "blank" during installation & rescue | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Forgotten User U_vfIZ_agZ <forgotten_U_vfIZ_agZ> |
| Component: | Installation | Assignee: | E-mail List <kernel-maintainers> |
| Status: | RESOLVED NORESPONSE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Major | ||
| Priority: | P2 - High | CC: | forgotten_U_vfIZ_agZ, jreidinger, jslaby, snwint |
| Version: | Leap 42.2 | Flags: | snwint:
needinfo?
(forgotten_U_vfIZ_agZ) |
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Forgotten User U_vfIZ_agZ
2017-02-28 14:41:32 UTC
Steffen - rescue should not start any X so probably problem with framebuffer? Maybe kernel issue? I guess you have better knowledge who to reassign to. I'll need a bit more details. Rob, do you mean you hit 'enter' and the screen screws up immediately, or do you see the 'Loading Linux kernel' popup and only _after_ that one the screen goes blank (that is, when the kernel starts)? Just Re-created what happened this morning with a Dell Inspiron (Intel CPU) 1720 with Nvidia Graphics Board (8600M 256. Just previous to that I tried to recreate it with the Dell Inspiron 1721 (graphics is a chip on the motherboard) could not duplicate this bug on the Insprion 1721 (AMD CPU) - perhaps this was version 42.1 - and just hooked up a external monitor. Dell Inspiron 1720 below. I selected the rescue mode from the choices from the first window. Basically, the window with "Starting .... Loading linux Kernal" does complete. Monitor then goes into "text mode" and start scrolling with text. Shortly after the display reads ">>> openSuSE Leap 42.2 installation program v5.0.87 (c) 1996-2016 SUSE LLC <<< Starting udev ..." The screen then goes "blank" shortly thereafter. Thanks! That clears things up. This is the moment when KMS takes over. As a workaround you could pass 'nomodeset' as boot option. Assigning to kernel team. Closing due to lack of response. |