[Bug 1002875] New: plymouth boot splash not working in tumbleweed
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875 Bug ID: 1002875 Summary: plymouth boot splash not working in tumbleweed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: cristian_anita@yahoo.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Hi All, I recently made a fresh install of Tumbleweed 20160924 and plymouth splash screen does not appear at startup (only blinking cursor between grub2 and sddm) and shutdown (only some message about watchdog). plymouth-0.9.2-2.4 plymouth-branding-openSUSE-13.3-4.3 grub2-2.02~beta3-11.1 Same with latest TW update (20161003) Regards, Cristian ANITA -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
Ismail Donmez
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c2
Axel Braun
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c3
--- Comment #3 from Cristian ANITA
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c4
Neil Rickert
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c6
--- Comment #6 from Cristian ANITA
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c7
--- Comment #7 from Axel Braun
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c8
Cristiano Guadagnino
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c9
Aleksey Kontsevich
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c10
--- Comment #10 from Aleksey Kontsevich
If you have a lot of server daemons and cost a long time during start up, You will see it.
That is not the case: when plymouth works ok if we press Esc we see system messages colored [Ok] and screen actually in graphics mode: pressing Esc again - immediately back to the splash so no graphic mode changed. In our case we do not enter to graphics mode - PC remain in text mode and system messages are not colored in text mode like in terminal by Ctrl-Alt-F1. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c11
--- Comment #11 from Aleksey Kontsevich
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c12
Walther Pelser
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c13
--- Comment #13 from Walther Pelser
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c14
--- Comment #14 from Aleksey Kontsevich
Have you tried hitting CTRL-ALT-F7 during boot (after kernel and initrd have loaded)? I have to do that if I want the plymouth splash screen to show up. That is not our case - completely malfunctioning, not working. Also after boot terminal on Ctrl-Alt-F1 have low text resolution, not in high res graphics mode as usual on SUSE (do not know how to get current VESA mode to show You).
Since tumbleweed switched to kernel 4.11.8-2.2 and later to kernel 4.12.XX plymouth is working for me again. Glad for You, however I have latest tumbleweed with 4.12.XX and it does not work for me, does not work for us.
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c15
--- Comment #15 from Aleksey Kontsevich
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c16
--- Comment #16 from Aleksey Kontsevich
Just uninstalled nvidia drivers - plymouth works fine again with highest resolution available 1920x1080, resolution in console is high again, fonts in sddm normal (not small with nvidia). Will stay on nouveau for now since graphical effects works fine in KDE with it.
Seems some nvidia bug: vlc works fine with nouveau, crashed with nvidia drivers. Is it possible to make some old nvidia drivers available in tumbleweed: G03, G02, etc to check? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c17
--- Comment #17 from Cristian ANITA
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c18
--- Comment #18 from Cristian ANITA
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c19
--- Comment #19 from Cristiano Guadagnino
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c20
--- Comment #20 from Aleksey Kontsevich
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c21
--- Comment #21 from Neil Rickert
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c22
--- Comment #22 from Aleksey Kontsevich
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c23
--- Comment #23 from Axel Braun
After latest kernel upgrade plymouth shows gray screen with green dots, not usual Tumbleweed beautiful splash.
Did you try to run mkinitrd manually? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c24
--- Comment #24 from Aleksey Kontsevich
Did you try to run mkinitrd manually? No, what for?
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c25
--- Comment #25 from Cristiano Guadagnino
I have checked two Tumbleweed installations with Intel graphics, and Plymouth is now working fine on those. (...)
I am on my laptop now (Thinkpad T440), which has Intel graphics: ================================================================ cristiano@xmper8q3 [~]$ inxi -G Graphics: Card: Intel Haswell-ULT Integrated Graphics Controller Display Server: x11 (X.Org 1.19.3) drivers: intel (unloaded: modesetting,fbdev,vesa) Resolution: 1920x1080@60.00hz, 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel Haswell Mobile version: 4.5 Mesa 17.2.0 ================================================================ No plymouth splash here, just a black screen. Since months. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c26
--- Comment #26 from Axel Braun
(In reply to Axel Braun from comment #23)
Did you try to run mkinitrd manually? No, what for?
Observed the effect you mentioned a couple of times after upgrades, running mkinitrd fixed it. Have to mention that Plymouth was working before....so if it hadnt been working before for you, it will most likely not afterwards -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c27
--- Comment #27 from Aleksey Kontsevich
Observed the effect you mentioned a couple of times after upgrades, running mkinitrd fixed it. Have to mention that Plymouth was working before....so if it hadnt been working before for you, it will most likely not afterwards Just do sudo mkinitrd without parameters, that is all?
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c28
--- Comment #28 from Axel Braun
(In reply to Axel Braun from comment #26)
Observed the effect you mentioned a couple of times after upgrades, running mkinitrd fixed it. Have to mention that Plymouth was working before....so if it hadnt been working before for you, it will most likely not afterwards Just do sudo mkinitrd without parameters, that is all?
Yes, that should do the job -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c29
--- Comment #29 from Aleksey Kontsevich
(In reply to Aleksey Kontsevich from comment #27)
(In reply to Axel Braun from comment #26)
Observed the effect you mentioned a couple of times after upgrades, running mkinitrd fixed it. Have to mention that Plymouth was working before....so if it hadnt been working before for you, it will most likely not afterwards Just do sudo mkinitrd without parameters, that is all?
Yes, that should do the job
Yes, this works, thanks. Strange it was not done automatically during kernel package update. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
Walther Pelser
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c30
--- Comment #30 from Aleksey Kontsevich
sudo mkinitrd without parameters, that is all?
Yes, that should do the job
Helped temporarily: grey screen again. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c31
Aleksey Kontsevich
Helped temporarily: grey screen again.
plymouth become grey after every kernel update, seems some script breaks plymouth settings there. Reinstalling nouveau packages solves the problem: plymouth become normal again: seems update nouveau scripts in packages fixes plymouth settings. However this is only for nouveau driver. For nvidia driver - still black screen. Are You going to fix this issue?! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c32
--- Comment #32 from Zhao Qiang 赵强
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c33
carlo coppa
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c34
--- Comment #34 from Aleksey Kontsevich
I only see a gray screen with three points.
I confirm: issue still exists. Sometime screen is normal and more often gray screen with three points. Please fix. It worked without a problem and smoothly in openSUSE 12.3 for me, now very unstable. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
Aleksey Kontsevich
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c35
--- Comment #35 from Cristiano Guadagnino
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c36
Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c37
--- Comment #37 from Aleksey Kontsevich
Changing PRIO: P1 is a 'system stopped' - plymouth hardly qualifies for that
If You see grey screen on startup every day, thinking differently. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c38
--- Comment #38 from Dominique Leuenberger
(In reply to Dominique Leuenberger from comment #36)
Changing PRIO: P1 is a 'system stopped' - plymouth hardly qualifies for that
If You see grey screen on startup every day, thinking differently.
Do you reach a working system in the end? If so: then a non-nice splash is definitnively not 'all activity is stopped' worthy. I'm not arguing that the bug is not valid, it clearly is, I'm arguing that it does not qualify as a P1 (let alone deciding of the priorities is defined to be the developers task, not the reporters task); but this all distracts from the actual issue. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c39
--- Comment #39 from Aleksey Kontsevich
but this all distracts from the actual issue.
I just want to pay attention to this task as no progress on it for months. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c40
--- Comment #40 from carlo coppa
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c41
--- Comment #41 from Aleksey Kontsevich
while on the Nouveau persists the ugly gray screen.
For me gray screen appear with both Nouveau and Nvidia. With Nvidia it is more terrible: never see normal screen and screen resolution is wrong. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
Michal Suchanek
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c42
--- Comment #42 from Aleksey Kontsevich
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c43
--- Comment #43 from carlo coppa
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c44
--- Comment #44 from Aleksey Kontsevich
These days I changed the video card and I switched from an Nvidia geforce 315 to an Amd Sapphire Radeon R5 230. Now the splash screen is shown without problems in both Leap and Tumbleweed, fantastic! So I think it's a problem with the Nvidia and Nouveau drivers.
For me on same hardware things worked fine on SUSE 12.x. So think problem could be with both: nvidia and plymouth. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c45
--- Comment #45 from Aleksey Kontsevich
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c46
--- Comment #46 from Aleksey Kontsevich
If you are using proprietary video drivers (NVidia/Ati), then you need to have a vga=xxx parameter in your kernel options or the video framebuffer won't start and thus Plymouth won't run.
Google search returns plenty of links: https://www.google.com/search?num=100&ei=VEf3WsaEOuav6ASFg6mADQ&q=run+plymouth+framebuffer+opensuse like: https://www.reddit.com/r/openSUSE/comments/31mlvu/plymouth_is_broken_in_tumb... Much pain with it in manjaro as well with no useful solution: https://github.com/manjaro/mhwd/issues/32 https://github.com/manjaro/release-plan/issues/115 Whether In-Kernel Boot Splash Screen has the future? https://www.phoronix.com/scan.php?page=news_item&px=SUSE-Kernel-Bootsplash https://www.phoronix.com/scan.php?page=news_item&px=SUSE-Kernel-Bootsplash-V2 Could we hope for some solution on this? Thanks! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c47
--- Comment #47 from Aleksey Kontsevich
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c48
--- Comment #48 from Aleksey Kontsevich
Tried this solution: https://forums.linuxmint.com/viewtopic.php?f=59&t=228094&p=1470667#p1470294 without "efi_gop" as it does not work at all: grub and text terminal resolution looks much better but still grey screen with green dots in plymouth. Also it activated not right after the Linux start: blinking cursor for few seconds before start.
People claims it works in Fedora and some others. Any thought it does not work in SUSE? See discussion below this link: https://forums.linuxmint.com/viewtopic.php?f=59&t=228094&p=1472012#p1470294 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
Aleksey Kontsevich
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c49
--- Comment #49 from Aleksey Kontsevich
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c50
--- Comment #50 from Axel Braun
When it will be fixed?! After latest Tumbleweed and Plymouth upgrades looks even more terrible: most booting time screen is text and grey screen after this.
After upgrade to TW 20181112 I can not confirm this. Did you try to run mkinitrd afterwards? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c51
--- Comment #51 from Aleksey Kontsevich
After upgrade to TW 20181112 I can not confirm this. Did you try to run mkinitrd afterwards?
sudo mkinitrd [sudo] пароль для root: Creating initrd: /boot/initrd-4.18.15-1-default dracut: Executing: /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force /boot/initrd-4.18.15-1-default 4.18.15-1-default dracut: dracut module 'plymouth' will not be installed, because it's in the
Done now. BTW, downgraded to 4.18.15 kernel as 4.19.1 does not load graphical login screen at all - another bug. Will reboot now to check. list to be omitted! dracut: *** Including module: bash *** dracut: *** Including module: systemd *** dracut: *** Including module: warpclock *** dracut: *** Including module: systemd-initrd *** dracut: *** Including module: i18n *** dracut: No KEYMAP configured. dracut: *** Including module: kernel-modules *** dracut: *** Including module: resume *** dracut: *** Including module: rootfs-block *** dracut: *** Including module: suse-xfs *** dracut: *** Including module: terminfo *** dracut: *** Including module: udev-rules *** dracut: Skipping udev rule: 40-redhat.rules dracut: Skipping udev rule: 50-firmware.rules dracut: Skipping udev rule: 50-udev.rules dracut: Skipping udev rule: 91-permissions.rules dracut: Skipping udev rule: 80-drivers-modprobe.rules dracut: *** Including module: dracut-systemd *** dracut: *** Including module: haveged *** dracut: *** Including module: ostree *** dracut: *** Including module: usrmount *** dracut: *** Including module: base *** dracut: *** Including module: fs-lib *** dracut: *** Including module: shutdown *** dracut: *** Including module: suse *** dracut: *** Including modules done *** dracut: *** Installing kernel module dependencies and firmware *** dracut: *** Installing kernel module dependencies and firmware done *** dracut: *** Resolving executable dependencies *** dracut: *** Resolving executable dependencies done*** dracut: *** Hardlinking files *** dracut: *** Hardlinking files done *** dracut: *** Stripping files *** dracut: *** Stripping files done *** dracut: *** Generating early-microcode cpio image *** dracut: *** Constructing AuthenticAMD.bin **** dracut: *** Store current command line parameters *** dracut: Stored kernel commandline: dracut: resume=UUID=a322fe78-f7ec-4e2e-b58c-b24679f93ea5 dracut: root=UUID=94011706-5426-43f8-af6c-5e43f6eb7f1d rootfstype=ext4 rootflags=rw,relatime,errors=remount-ro dracut: *** Creating image file '/boot/initrd-4.18.15-1-default' *** dracut: *** Creating initramfs image file '/boot/initrd-4.18.15-1-default' done *** -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c52
--- Comment #52 from Aleksey Kontsevich
Did you try to run mkinitrd afterwards?
Does not help - all the same. On boot something fails to load [FAILED] on the very beginning however do not see what exactly because of fast scrolling. Any way to get this? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c53
--- Comment #53 from Axel Braun
(In reply to Axel Braun from comment #50)
After upgrade to TW 20181112 I can not confirm this. Did you try to run mkinitrd afterwards?
Done now. BTW, downgraded to 4.18.15 kernel as 4.19.1 does not load graphical login screen at all - another bug. Will reboot now to check.
sudo mkinitrd [sudo] пароль для root: Creating initrd: /boot/initrd-4.18.15-1-default dracut: Executing: /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force /boot/initrd-4.18.15-1-default 4.18.15-1-default dracut: dracut module 'plymouth' will not be installed, because it's in the list to be omitted!
Did you see this line? Pls check your configuration..... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c54
--- Comment #54 from carlo coppa
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c55
--- Comment #55 from Aleksey Kontsevich
then running mkinitrd will recreate your initrd, tell Dracut to load your driver, and Plymouth will use it
Thanks! Trying... Still got the message on mkinitrd:
dracut: dracut module 'plymouth' will not be installed, because it's in the list to be omitted!
Enable it in dracut configuration? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875 http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c56 --- Comment #56 from Aleksey Kontsevich--- (In reply to carlo coppa from comment #54) > one way of working around this issue is to create a file called > /etc/sysconfig/kernel and add a line for 'INITRD_MODULES=' in it No, does not work at all: - first text screen - then grey plymouth again - then text screen again Terrible!!! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c57
--- Comment #57 from Aleksey Kontsevich
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c58
--- Comment #58 from Aleksey Kontsevich
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c59
--- Comment #59 from Aleksey Kontsevich
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c60
--- Comment #60 from Aleksey Kontsevich
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c61
--- Comment #61 from Aleksey Kontsevich
systemctl status systemd-modules-load.service
● systemd-modules-load.service - Load Kernel Modules Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static; vendor preset: disabled) Active: active (exited) since Thu 2018-11-15 20:48:50 EET; 1h 43min ago Docs: man:systemd-modules-load.service(8) man:modules-load.d(5) Main PID: 538 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4915) CGroup: /system.slice/systemd-modules-load.service nov 15 20:48:50 localhost systemd[1]: Started Load Kernel Modules. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c62
--- Comment #62 from Aleksey Kontsevich
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c63
--- Comment #63 from Aleksey Kontsevich
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c64
--- Comment #64 from Aleksey Kontsevich
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c65
--- Comment #65 from Aleksey Kontsevich
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c66
Kyaw Thu Soe
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c67
--- Comment #67 from Cliff Zhao
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c68
--- Comment #68 from Aleksey Kontsevich
With the latest update in openSUSE:Factory, I confirmed the Plymouth works fine in many hardware env, Does this still suffer you?
Me - yes. However I have not tried Factory yet. What repo, packages to try? Thanks! -- You are receiving this mail because: You are on the CC list for the bug.
(In reply to Cliff Zhao from comment #67)
With the latest update in openSUSE:Factory, I confirmed the Plymouth works fine in many hardware env, Does this still suffer you?
Me - yes. However I have not tried Factory yet. But this bug happens on the Tumbleweed, if you tried on other edition or not
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c69
--- Comment #69 from Cliff Zhao
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c70
--- Comment #70 from Aleksey Kontsevich
I think just install plymouth from http://download.opensuse.org/tumbleweed/repo/oss/x86_64/ is okay. and I installed plymouth, plymouth-scripts, plymouth-plugin-label, plymouth-plugin-label-ft, plymouth-theme-bgrt, plymouth-branding-openSUSE, plymouth-plugin-two-step, plymouth-theme-spinner, libply-splash-graphics4, libply-splash-core4, libply4, libply-boot-client4.
I already have all of these only some versions differ: libply-splash-graphics5, libply-boot-client5, libply-splash-core5, libply5. And still grey screen with green dots with nvidia driver and nothing with nouveau as well. So nothing was fixed there. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c71
--- Comment #71 from Cliff Zhao
(In reply to Cliff Zhao from comment #69)
I think just install plymouth from http://download.opensuse.org/tumbleweed/repo/oss/x86_64/ is okay. and I installed plymouth, plymouth-scripts, plymouth-plugin-label, plymouth-plugin-label-ft, plymouth-theme-bgrt, plymouth-branding-openSUSE, plymouth-plugin-two-step, plymouth-theme-spinner, libply-splash-graphics4, libply-splash-core4, libply4, libply-boot-client4.
I already have all of these only some versions differ: libply-splash-graphics5, libply-boot-client5, libply-splash-core5, libply5.
And still grey screen with green dots with nvidia driver and nothing with nouveau as well. So nothing was fixed there.
Hi Aleksey: the "3 green dots" are the failsafe mode for Plymouth, Nvidia's business driver is not supported, because it is not open source, I can't do the reverse engineering to hack it, sorry. Maybe Nvidia's engineers can, who knows. So we only can talk about the open-source driver, and you said that "nouveau" works fine, Is there any other hardware env reproduce this problem? Thanks! -- You are receiving this mail because: You are on the CC list for the bug.
the "3 green dots" are the failsafe mode for Plymouth, Nvidia's business driver is not supported, because it is not open source, I can't do the reverse engineering to hack it, sorry. Maybe Nvidia's engineers can, who knows. Plymouth worked with nvidia before 0.9.2 version so it is definitelly plymouth
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c72
--- Comment #72 from Aleksey Kontsevich
So we only can talk about the open-source driver, and you said that "nouveau" works fine, Is there any other hardware env reproduce this problem? I've never said that: nouveau also shows 3 green dots as well and screen blinking. Also on X start screen resolution is very low, so nouveau is completely unusable! Only nvidia works somehow.
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c73
--- Comment #73 from Cliff Zhao
(In reply to Cliff Zhao from comment #71)
the "3 green dots" are the failsafe mode for Plymouth, Nvidia's business driver is not supported, because it is not open source, I can't do the reverse engineering to hack it, sorry. Maybe Nvidia's engineers can, who knows. Plymouth worked with nvidia before 0.9.2 version so it is definitelly plymouth problem! And previously in SUSE 12, etc. Yes, I understand your situation. Maybe this problem exposed by the update, but we should know that there also have some people whos device doesn't work in SLE12, but fixed with this update and some people's device works so fine with Nvidia card in SUSE 15. and please note that I don't mean that this problem doesn't have any relationship with the plymouth, but I mean that the conditions is insufficient, the work can not be done from our side.
So we only can talk about the open-source driver, and you said that "nouveau" works fine, Is there any other hardware env reproduce this problem? I've never said that: nouveau also shows 3 green dots as well and screen blinking. Also on X start screen resolution is very low, so nouveau is completely unusable! Only nvidia works somehow.
Sorry about that. we are very interested in this part of the problem. First, could you please confirm it is not a hardware problem? Does your card works fine under other operating systems? how does it looks like in SLE-12? If it works well, could you please open a new bug to describe the detailed reproduce steps and the actual result with default kernel driver(nouveau)? Thanks! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c74
--- Comment #74 from Aleksey Kontsevich
Sorry about that. we are very interested in this part of the problem. First, could you please confirm it is not a hardware problem?
How can I check?!
Does your card works fine under other operating systems? idk
how does it looks like in SLE-12? Sorry have much work and not enough time to install other OSs.
If it works well, could you please open a new bug to describe the detailed reproduce steps and the actual result with default kernel driver(nouveau)? What step to reproduce could be?! Just installed clean system, root partition was formatted - may be it worked somehow - was far away, but not all the time - grey screen was as well, but after I installed nvidia driver - green dots. Uninstall - green dots. DO not want to reinstall again. Possible uninstall scripts are not clear. Tried to reinstall nouveau - no luck.
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c75
--- Comment #75 from Cliff Zhao
(In reply to Cliff Zhao from comment #73)
Sorry about that. we are very interested in this part of the problem. First, could you please confirm it is not a hardware problem?
How can I check?!
Does your card works fine under other operating systems? idk
how does it looks like in SLE-12? Sorry have much work and not enough time to install other OSs.
So when you using the Nvidia driver, can you use the desktop? Do the desktop's revolution and the color looks correct? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c76
--- Comment #76 from Aleksey Kontsevich
So when you using the Nvidia driver, can you use the desktop? What do You mean? X and KDE work ok.
Do the desktop's revolution and the color looks correct? With nvidia drivers - yes.
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c77
--- Comment #77 from Cliff Zhao
(In reply to Cliff Zhao from comment #75)
So when you using the Nvidia driver, can you use the desktop? What do You mean? X and KDE work ok.
Do the desktop's revolution and the color looks correct? With nvidia drivers - yes.
And you said that the desktop only works in a low resolution with the neuveau driver. So if you add "plymouth.enable=0" option in the kernel command line(edit /boot/grub2/grub.cfg), is there any change on your desktop? Can everything works fine? You said that "X and KDE", you confirm you are using X but not wayland? Thanks! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c78
--- Comment #78 from Aleksey Kontsevich
And you said that the desktop only works in a low resolution with the neuveau driver. With nouveau - yes. With nvidia - resolution is ok.
So if you add "plymouth.enable=0" option in the kernel command line(edit /boot/grub2/grub.cfg), is there any change on your desktop? Can everything works fine? Need to check, do not know when have time. What for? Both have problems with plymouth, at least all other things works ok with nvidia.
You said that "X and KDE", you confirm you are using X but not wayland? I'm using what Tumbleweed installer installed - Xorg.
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c79
--- Comment #79 from Cliff Zhao
(In reply to Cliff Zhao from comment #77)
And you said that the desktop only works in a low resolution with the neuveau driver. With nouveau - yes. With nvidia - resolution is ok.
So if you add "plymouth.enable=0" option in the kernel command line(edit /boot/grub2/grub.cfg), is there any change on your desktop? Can everything works fine? Need to check, do not know when have time. What for? Both have problems with plymouth, at least all other things works ok with nvidia.
When you have time and get the result, please update, thanks so much! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c80
Aleksey Kontsevich
zypper dup so seems some update scripts is broken. Do not like to reinstall Tumbleweed every time plymouth is broken. Why it works fine with any other distribution whether with nouveau, intel or nvidia drivers and usually broken here?! Why SUSE can't fix it once and for all?!
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c81
--- Comment #81 from Cliff Zhao
Plymouth is broken again and looks like complete sh... Was working for some time, If it behaves like this, this should be another issue, please open a new bug, and don't forget to attach the support-log. Thank you!
...
every time plymouth is broken. Why it works fine with any other distribution whether with nouveau, intel or nvidia drivers and usually broken here?! Why SUSE can't fix it once and for all?! First, sorry for the inconvenience. And I want to say that the situation is very complex, which should be discus by different bugs, some of them are Plymouth's bug, some is caused by other component's modification. But Plymouth is always in front position of the stage.
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c82
--- Comment #82 from Cliff Zhao
(In reply to Aleksey Kontsevich from comment #80)
Plymouth is broken again and looks like complete sh... Was working for some time, If it behaves like this, this should be another issue, please open a new bug, and don't forget to attach the support-log. Thank you!
...
every time plymouth is broken. Why it works fine with any other distribution whether with nouveau, intel or nvidia drivers and usually broken here?! Why SUSE can't fix it once and for all?! First, sorry for the inconvenience. And I want to say that the situation is very complex, which should be discus by different bugs, some of them are Plymouth's bug, some is caused by other component's modification. But Plymouth is always in front position of the stage.
And maybe you could have a check if your problem is the same with bsc#1179625? Is the method in comment1 of that bug works for you? https://bugzilla.opensuse.org/show_bug.cgi?id=1179625 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c83
--- Comment #83 from Aleksey Kontsevich
If it behaves like this, this should be another issue, please open a new bug, and don't forget to attach the support-log. Can do but why it can't be solved here? And what is support-log?
And maybe you could have a check if your problem is the same with bsc#1179625? Is the method in comment1 of that bug works for you? What method? It describes nothing - how to solve - steps to fix? And do not think it will solve anything. In Ubuntu plymouth starts immediately and user do not see a console at all. In SUSE starting kernel message appears in any case for some reason after grub which is weird!
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c84
--- Comment #84 from Cliff Zhao
(In reply to Cliff Zhao from comment #81)
If it behaves like this, this should be another issue, please open a new bug, and don't forget to attach the support-log. Can do but why it can't be solved here? And what is support-log? Because it is very hard to manage. This bug already have many forking discussions, and the problem which you are facing is different with the reporter's scenario.
to get the supportlog: 1, $ zypper install supportutils 2, $ supportconfig 3, Upload the tar file from your system "/var/log/scc_...txz" to here as an attachment.
And maybe you could have a check if your problem is the same with bsc#1179625? Is the method in comment1 of that bug works for you? What method? It describes nothing - how to solve - steps to fix? And do not
think it will solve anything. In Ubuntu plymouth starts immediately and user do not see a console at all. In SUSE starting kernel message appears in any case for some reason after grub which is weird! But this is also different from your comment80's problem. It should be the
comment1 of "that bug". sudo plymouth-set-default-theme --rebuild-initrd bgrt or sudo plymouth-set-default-theme bgrt && dracut -f third bug, and please paste the reproduce steps there. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c85
--- Comment #85 from Aleksey Kontsevich
sudo plymouth-set-default-theme --rebuild-initrd bgrt
Does not fix the problem: console-> green dots -> console with green dots - complete mess! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c86
--- Comment #86 from Aleksey Kontsevich
to get the supportlog: 1, $ zypper install supportutils 2, $ supportconfig 3, Upload the tar file from your system "/var/log/scc_...txz" to here as an attachment.
When to do that? After start, before start, do then restart? What? Or does not matter? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c87
--- Comment #87 from Cliff Zhao
to get the supportlog: 1, $ zypper install supportutils 2, $ supportconfig 3, Upload the tar file from your system "/var/log/scc_...txz" to here as an attachment.
When to do that? After start, before start, do then restart? What? Or does not matter?
After you've just experienced this error during boot up, then you will login to the desktop, do it. By the way: the 2nd action of "sudo plymouth-set-default-theme bgrt; sudo dracut -f" Also doesn't work for your system? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c88
--- Comment #88 from Aleksey Kontsevich
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c89
--- Comment #89 from Aleksey Kontsevich
to get the supportlog: 1, $ zypper install supportutils 2, $ supportconfig 3, Upload the tar file from your system "/var/log/scc_...txz" to here as an attachment. After you've just experienced this error during boot up, then you will login to the desktop, do it.
Attached: https://bugzilla.opensuse.org/attachment.cgi?id=846188
By the way: the 2nd action of "sudo plymouth-set-default-theme bgrt; sudo dracut -f" Also doesn't work for your system?
Yes, doesn't work. However after today's massive Tumbleweed upgrade (20210212) - more than 3000 packages were updated, things become better: - no console garbage mixed with green dots - on shutdown plymouth screen is normal - start I still see green dots, but at least no console for now. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c90
--- Comment #90 from Cliff Zhao
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c91
--- Comment #91 from Aleksey Kontsevich
When I check the log, I found that you are using the Nvidia's commerce driver. Am I right? It's out of the supporting scope, at least no level3 support as I know. Sorry.
Like I said it was working here in Suse and always works fine in Ubuntu.
By the way, Could your problem happen with the open source driver?
I used open source driver, however migrated back to nvidia as nouveau crashes X11 often on some videos, video accelerations, etc. Can't use it. Both drivers are installed however (like in Ubuntu) so should work fine. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c92
--- Comment #92 from Cliff Zhao
(In reply to Cliff Zhao from comment #90)
When I check the log, I found that you are using the Nvidia's commerce driver. Am I right? It's out of the supporting scope, at least no level3 support as I know. Sorry.
Like I said it was working here in Suse and always works fine in Ubuntu.
You know that it is a closed source application. Even if Ubuntu can support it, I can't guarantee to fully support it. But I think I could ask other people to see if there has any parameter or some configuration for this driver which is public, to see if it can work.
By the way, Could your problem happen with the open source driver?
I used open source driver, however migrated back to nvidia as nouveau crashes X11 often on some videos, video accelerations, etc. Can't use it. Both drivers are installed however (like in Ubuntu) so should work fine. In this case, You are welcome to report bug to nouveau(kernel) or Xorg to resolve the crash problem. There are very limit things we can do about the business driver. Maybe this is not what you want, but I only can promise to do my best to help, But no guarantee about the success.
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c93
--- Comment #93 from Aleksey Kontsevich
You know that it is a closed source application. Even if Ubuntu can support it, I can't guarantee to fully support it. But I think I could ask other people to see if there has any parameter or some configuration for this driver which is public, to see if it can work.
Thanks!
In this case, You are welcome to report bug to nouveau(kernel) or Xorg to resolve the crash problem.
What to report?! Sometimes it crashes in Firefox or other video playing applications. Actually Mesa-nouveau always warn about this in license agreement on every install.
There are very limit things we can do about the business driver. Maybe this is not what you want, but I only can promise to do my best to help, But no guarantee about the success.
Thanks much! However I think nvidia driver only starts (or works) when X.org is started, on boot nouveau works, that is why it works in Ubuntu I think. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c94
--- Comment #94 from Cliff Zhao
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c95
--- Comment #95 from Aleksey Kontsevich
Maybe the proprietary Nvidia drivers require a kernel command line to get the mode-setting. I'm still collecting the information...
Found working solution: https://www.reddit.com/r/openSUSE/comments/dxlyfd/how_do_i_bring_back_plymou... - plymouth works just fine now with nvidia proprietary drivers. Think while rpms with drivers are created by SUSE: https://download.nvidia.com/opensuse/README - need to add scripts to create these files on rpms install: Make a nvidia.conf file with the following content:
options nvidia_drm modeset=1
Then copy this file to /etc/modprobe.d/ Second, make another nvidia.conf file with the following content:
add_drivers+=" nvidia nvidia_modeset nvidia_uvm nvidia_drm "
install_items+=" /etc/modprobe.d/nvidia.conf "
Copy this file to /etc/dracut.conf.d/ Then update dracut:
sudo dracut -f
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c96
--- Comment #96 from Michal Suchanek
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c97
Cliff Zhao
(In reply to Cliff Zhao from comment #94)
Maybe the proprietary Nvidia drivers require a kernel command line to get the mode-setting. I'm still collecting the information...
Found working solution: https://www.reddit.com/r/openSUSE/comments/dxlyfd/ how_do_i_bring_back_plymouth_after_nvidia_driver/ - plymouth works just fine now with nvidia proprietary drivers.
Think while rpms with drivers are created by SUSE: https://download.nvidia.com/opensuse/README - need to add scripts to create these files on rpms install:
Make a nvidia.conf file with the following content:
options nvidia_drm modeset=1
Then copy this file to /etc/modprobe.d/
Second, make another nvidia.conf file with the following content:
add_drivers+=" nvidia nvidia_modeset nvidia_uvm nvidia_drm "
install_items+=" /etc/modprobe.d/nvidia.conf "
Copy this file to /etc/dracut.conf.d/
Then update dracut:
sudo dracut -f
Nice search, so this bug could be close. thanks! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c98
Aleksey Kontsevich
Nice search, so this bug could be close. thanks!
Yes, could be closed when above commands added to nvidia drivers install scripts as these packages maintained by SUSE. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c99
--- Comment #99 from Cliff Zhao
Nice search, so this bug could be close. thanks!
Yes, could be closed when above commands added to nvidia drivers install scripts as these packages maintained by SUSE.
Maybe the maintainer for Nvidia driver's package could consider this solution. But from my side there's no guarantee that Plymouth will work even these commands the added to the Nvidia driver script in the future. Because as you know, it is a proprietary driver. I'm really sorry for that. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c100
--- Comment #100 from Aleksey Kontsevich
Maybe the maintainer for Nvidia driver's package could consider this solution.
Could You notice him please? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c101
Michal Suchanek
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c102
--- Comment #102 from Cliff Zhao
Maybe the maintainer for Nvidia driver's package could consider this solution.
Could You notice him please?
Maybe open another bug is better to describ the background to him clearly, I guess. And Michal has already setup the needinfo. Don't worry. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c103
--- Comment #103 from Aleksey Kontsevich
Maybe open another bug is better to describ the background to him clearly, I guess. And Michal has already setup the needinfo. Don't worry.
What info is necessary? I think all steps I did are provided here. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c104
--- Comment #104 from Cliff Zhao
Maybe open another bug is better to describ the background to him clearly, I guess. And Michal has already setup the needinfo. Don't worry.
What info is necessary? I think all steps I did are provided here.
Michal has already set the needinfo flag to the maintainer of the NVIDIA dirver in openSUSE community, So please don't worry. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c105
Stefan Dirsch
(In reply to Cliff Zhao from comment #94)
Maybe the proprietary Nvidia drivers require a kernel command line to get the mode-setting. I'm still collecting the information...
Found working solution: https://www.reddit.com/r/openSUSE/comments/dxlyfd/ how_do_i_bring_back_plymouth_after_nvidia_driver/ - plymouth works just fine now with nvidia proprietary drivers.
Think while rpms with drivers are created by SUSE: https://download.nvidia.com/opensuse/README - need to add scripts to create these files on rpms install:
Make a nvidia.conf file with the following content:
options nvidia_drm modeset=1
Then copy this file to /etc/modprobe.d/
Well, I meanwhile did this for our G05 packages. Even though for different reason: to enable Wayland support. I guess here it's needed for the KMS support of plymouth.
Second, make another nvidia.conf file with the following content:
add_drivers+=" nvidia nvidia_modeset nvidia_uvm nvidia_drm "
install_items+=" /etc/modprobe.d/nvidia.conf "
Copy this file to /etc/dracut.conf.d/
Actually I did the contrary a long time ago.
-------------------------------------------------------------------
Tue Jul 21 09:08:17 UTC 2020 - Stefan Dirsch
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c106
--- Comment #106 from Aleksey Kontsevich
Readding them to initrd may work as well or may lead (again) to different issues, which turn out to be more serious than a splash screen,
No issues observed, all works fine!
which you nowadays with SSDs in place see for about 2 seconds.
I have HDD and see it for 30 sec. But even for 2 sec I'd like to see splash and not weird green matrix. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875
http://bugzilla.opensuse.org/show_bug.cgi?id=1002875#c108
--- Comment #108 from Aleksey Kontsevich
(In reply to Cliff Zhao from comment #94)
Maybe the proprietary Nvidia drivers require a kernel command line to get the mode-setting. I'm still collecting the information...
Found working solution: https://www.reddit.com/r/openSUSE/comments/dxlyfd/ how_do_i_bring_back_plymouth_after_nvidia_driver/ - plymouth works just fine now with nvidia proprietary drivers.
Think while rpms with drivers are created by SUSE: https://download.nvidia.com/opensuse/README - need to add scripts to create these files on rpms install:
Make a nvidia.conf file with the following content:
options nvidia_drm modeset=1
Then copy this file to /etc/modprobe.d/
Second, make another nvidia.conf file with the following content:
add_drivers+=" nvidia nvidia_modeset nvidia_uvm nvidia_drm "
install_items+=" /etc/modprobe.d/nvidia.conf "
Copy this file to /etc/dracut.conf.d/
Then update dracut:
sudo dracut -f
On latest 5.15 kernel it produces error on dracut run:
`dracut-install: Failed to find module 'nvidia_uvm'`
So need to remove `nvidia_uvm` from `/etc/dracut.conf.d/nvidia.conf` file: ``` add_drivers+=" nvidia nvidia_modeset nvidia_drm " install_items+=" /etc/modprobe.d/nvidia.conf " ``` and rerun `sudo dracut -f`. https://www.reddit.com/r/openSUSE/comments/dxlyfd/comment/ho8jtd0/?utm_source=share&utm_medium=web2x&context=3 -- You are receiving this mail because: You are on the CC list for the bug.
participants (2)
-
bugzilla_noreply@novell.com
-
bugzilla_noreply@suse.com