[Bug 1018353] New: No display shown when video is not set during installation
http://bugzilla.opensuse.org/show_bug.cgi?id=1018353 Bug ID: 1018353 Summary: No display shown when video is not set during installation Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: openSUSE 42.2 Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers@suse.de Reporter: richard.bos@xs4all.nl QA Contact: jsrain@suse.com Found By: --- Blocker: --- Created attachment 708751 --> http://bugzilla.opensuse.org/attachment.cgi?id=708751&action=edit y2log installation log with default settings No GUI shown during installation. The GUI is only shown after manually selecting the video resolution. It's very confusing when the installer does not show any GUI after the boot prompt. It took a long time, effort and dedication to determine that the system can show a installer GUI. Initially I thought that LVDS-1:d and VGA-1:e were needed to make the installer GUI show up. In the end and with experimenting, it seems that video=1280x1024 works. The latter can be obtained via <F3>(video) and the selection of 1280x1024 setting. Hopefully with the log information attached, it is possible to determine what causing the current behavior, so with the next openSUSE version the installer GUI is presented to the user. Step to reproduce: - power on system - openSUSE boot prompt is shown - select installation - system boots from CD - kernel is loaded - after some time system starts to configure automatically, at this point the screen turns black.... - with video=1280x1028 a GUI installer is provided to the user in the end. The y2log-default-boot has been obtained, by typing various commands blind, to be able to save the log.... hwinfo attached -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1018353
http://bugzilla.opensuse.org/show_bug.cgi?id=1018353#c1
--- Comment #1 from Richard Bos
http://bugzilla.opensuse.org/show_bug.cgi?id=1018353
http://bugzilla.opensuse.org/show_bug.cgi?id=1018353#c2
--- Comment #2 from Richard Bos
http://bugzilla.opensuse.org/show_bug.cgi?id=1018353
http://bugzilla.opensuse.org/show_bug.cgi?id=1018353#c3
--- Comment #3 from Richard Bos
http://bugzilla.opensuse.org/show_bug.cgi?id=1018353
http://bugzilla.opensuse.org/show_bug.cgi?id=1018353#c15
--- Comment #15 from Richard Bos
There is no easy way to a detect a black screen, graphics corruption or similar bugs in the graphics driver.
Ain't it possible to configure a not supported gfx card (just in the distribution files)? I tested it today again, kernel boot parameters: LVDS-0:d LVDS-1:d VGA-0:e VGA-1:e (either separately or combined) do not result in GUI. The only thing that helps, is setting the video mode (to 1280x1024). This makes the installation possible via X (yast-qt). Either via boot argument video=1280x1024 are using the video boot menu (<F3>). Attached the log files for a boot cycle without boot parameter and with video set. In the latter case there is y2start.log and Xorg log. In the case without video defined only one log available (the only one available is y2log). The log files are obtained via the same method, using a script. But when no video set the script is to be executed without any visuals... If I interpret the y2log for the case without video setting, the ncurses gui is started, while in the other case (video set), yast-qt is started... video = yes: bug-20170114-093438 video = no: bug-20170114-144830 # diff bug-20170114-093438/YaST2/y2log bug-20170114-144830/y2log | sed 's/^/ vid=no:/' | head -20 1c1 vid=yes: <1> install(3192) [liby2] genericfrontend.cc(main):617 Launched YaST2 component 'y2base' 'installation' '("initial")' 'qt' '--noborder' '--auto-fonts' '--fullscreen' --- vid=no: <1> install(3192) [liby2] genericfrontend.cc(main):617 Launched YaST2 component 'y2base' 'installation' '("text_fallback")' '("initial")' 'ncurses' '--noborder' '--auto-fonts' '--fullscreen' 9c9 vid=yes: <1> install(3192) [ui] YPath.cc(YPath):49 Given filename: libyui-qt.so.7 --- vid=no: <1> install(3192) [ui] YPath.cc(YPath):49 Given filename: libyui-ncurses.so.7 13c13 vid=yes: <1> install(3192) [ui] YPath.cc(YPath):67 Looking for: libyui-qt.so.7 --- vid=no: <1> install(3192) [ui] YPath.cc(YPath):67 Looking for: libyui-ncurses.so.7 15c15 vid=yes: <1> install(3192) [ui] YPath.cc(YPath):118 Found libyui-qt.so.7 in /usr/lib64/yui --- vid=no: <1> install(3192) [ui] YPath.cc(YPath):118 Found libyui-ncurses.so.7 in /usr/lib64/yui 18,34c18,31 vid=yes: <1> install(3192) [qt-ui] YQUI.cc(YQUI):100 This is libyui-qt 2.46.24 vid=yes: <1> install(3192) [qt-styler] QY2Styler.cc(loadStyleSheet):91 Using style sheet "/usr/share/YaST2/theme/current/wizard/installation.qss" vid=yes: <1> install(3192) [qt-ui] YQUI.cc(processCommandLineArgs):298 Qt argument: YaST2 Looks like X is not started... Can't it be figured out, that installer should use a video mode, preferable 1280x1024, for a succesfull installation??? Either via analysis of gfxcard hwinfo in combination with the boot parameters, e.g.: if gfxcard gma500 adn if boot parameters set, do nothing. if boot parameters not set, set video mode = 1280x1024 and continue fi -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1018353
http://bugzilla.opensuse.org/show_bug.cgi?id=1018353#c17
--- Comment #17 from Richard Bos
http://bugzilla.opensuse.org/show_bug.cgi?id=1018353
Patrik Jakobsson
http://bugzilla.opensuse.org/show_bug.cgi?id=1018353
http://bugzilla.opensuse.org/show_bug.cgi?id=1018353#c20
--- Comment #20 from Richard Bos
http://bugzilla.opensuse.org/show_bug.cgi?id=1018353
http://bugzilla.opensuse.org/show_bug.cgi?id=1018353#c22
--- Comment #22 from Richard Bos
Hi, I've been trying to reproduce this on the gma500 machines I have available but they all hang at various points (not necessarily gfx related). Also, they're all 32bit machines which make things difficult.
Great. Very much appreciated.
What seems to be happening is that gma500 fails at some point and when restoring back to fb console it also fails, hence no textmode fallback.
Can you boot with drm.debug=0x3f and then look at dmesg. That would give us more information. I'll continue trying to get something up and running on these machines to see if I can pinpoint the first failure.
dmesg attached. Be aware that there is no video/display. I can only check what dmesg states, when it is saved and read in another running system.
Btw, do you only have a single VGA monitor attached to the machine and no LVDS-panel at all?
There is only a VGA monitor. I've no idea how to attach an LVDS panel at all. I'll attach dmest in the next updated. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1018353
http://bugzilla.opensuse.org/show_bug.cgi?id=1018353#c23
--- Comment #23 from Richard Bos
http://bugzilla.opensuse.org/show_bug.cgi?id=1018353
http://bugzilla.opensuse.org/show_bug.cgi?id=1018353#c24
--- Comment #24 from Richard Bos
http://bugzilla.opensuse.org/show_bug.cgi?id=1018353
http://bugzilla.opensuse.org/show_bug.cgi?id=1018353#c25
--- Comment #25 from Patrik Jakobsson
http://bugzilla.opensuse.org/show_bug.cgi?id=1018353
http://bugzilla.opensuse.org/show_bug.cgi?id=1018353#c26
--- Comment #26 from Patrik Jakobsson
http://bugzilla.opensuse.org/show_bug.cgi?id=1018353
http://bugzilla.opensuse.org/show_bug.cgi?id=1018353#c27
--- Comment #27 from Richard Bos
http://bugzilla.opensuse.org/show_bug.cgi?id=1018353
http://bugzilla.opensuse.org/show_bug.cgi?id=1018353#c28
--- Comment #28 from Richard Bos
http://bugzilla.opensuse.org/show_bug.cgi?id=1018353
http://bugzilla.opensuse.org/show_bug.cgi?id=1018353#c29
--- Comment #29 from Patrik Jakobsson
http://bugzilla.opensuse.org/show_bug.cgi?id=1018353
Stefan Dirsch
participants (1)
-
bugzilla_noreply@novell.com