Thank you very much for your replies. No 'rhgb' is the workaround in my case. I added my comment to the bug report you mentioned Fabio.
Any idea who is handling this, current status and how/when/why this will be solved ? BR, Alain On Sun, Nov 4, 2018 at 1:05 AM Fabio Valentini <decatho...@gmail.com> wrote: > On Sat, Nov 3, 2018 at 11:41 PM Alain Vigne <alain.vigne...@gmail.com> > wrote: > > > > Hi everyone > > TLDR; I had a working Wayland Gnome Desktop in f28. Not anymore with f29. > > > > Yesterday, I "dnf upgrade" my f28 to f29 ... to find a black screen when > I want to login to my Gnome session :( > > > > The boot is OK till the gdm login screen, but when I enter my password, > the screen turns black, and the keyboard is locked (non-responsive, Num > Lock does not toggle, nor caps lock). > > Then I don't know how to recover control, as no key binding is > effective, no mouse, no screen :(I power off the machine) > > > > I successfully launched the desktop using "startx" from my user account > after booting with runlevel=3, so I think there is an issue with Wayland ! > > > > > lspci|grep "VGA" > > 01:00.0 VGA compatible controller: NVIDIA Corporation GM206 [GeForce GTX > 960] (rev a1) > > I used to install the nvidia drivers, after each kernel upgrade. I did > that, as usual using: > > > ./NVIDIA-Linux-x86_64-410.73.run > > > > Where should I look to have more information about what's wrong with my > system ? > > Which component should I report on BZ ? > > What additional info would be helpful for knowledgeable developers ? > > > > Thanks for your help > > Best regards > > -- > > Alain V. > > Hi Alain, > > This seems to be a common issue with fedora 29 / NVIDIA drivers, I > reported it here: > https://bugzilla.redhat.com/show_bug.cgi?id=1643302 > > And there are some people on reddit who seem to be affected, too. > > Have you tried dropping "rhgb" from the kernel command line (by > editing the GRUB boot entry)? (Possibly also change > nvidia-drm.modeset=1 to nvidia-drm.modeset=0 to disable wayland in > gdm.) > Most people seem to confirm that this serves as a workaround. > > Fabio > > > _______________________________________________ > > devel mailing list -- devel@lists.fedoraproject.org > > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > _______________________________________________ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > -- Alain V.
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
