Created attachment 587750 [details] emerge --info emerge --update --deep --with-bdeps=y --newuse --quiet-build @world gave me sys-kernel/linux-firmware-20190815 and also new kernel source 4.19.66-gentoo. After the update I switched to the new kernel. After reboot I got a black screen at the point where the kernel boots (after dmcrypt asks for passphrase to mount root dir). Two leds on my laptop were flashing, otherwise dead. Could not even get a terminal by pressing ctrl+alt+f1. Ok, thought the problem was the new kernel, so I rebooted using the kernel I ran with before the update - same problem. Found this https://forums.gentoo.org/viewtopic-t-1077674-start-0.html and masked out: =sys-kernel/linux-firmware-20190815 (after usb boot and chroot'ing) and emerge then gave me sys-kernel/linux-firmware-20190603. After reboot my laptop works again.
Please attach your kernel config. Also, is this an optimus notebook?
Created attachment 587762 [details] Linux kernel .config
Yes, my laptop has optimus.
Can you try booting with a "nocoldplug" kernel parameter, to prevent udev autoloading of i915/nouveau modules? With the new/bad linux-firmware installed. If that boots successfully then you can try manually loading those modules and see if it goes black, and if so then capture dmesg output.
Created attachment 587790 [details] dmesg output
With "nocoldplug" and sys-kernel/linux-firmware-20190815 installed, my laptop boots. Manually loading i915 and nouveau also works. After that I could also launch KDE. I added the dmesg output as attachment, but not sure if that helps since I did not get black screen.
This is a bug tracker not a support forum. Once you find the bug that causes your problem, please do not hesitate to reopen this bug report to report your further findings. In the mean time, please use our actual support forums on the web, through e-mail and IRC, to discuss the problem.
So it is not a bug that a simple, normal emerge update gives me a package that leaves me with a laptop that can not boot at all? Silly me for thinking that... I have made this entry in the gentoo forum, but I am not getting much response to it: https://forums.gentoo.org/viewtopic-t-1101414-start-0-postdays-0-postorder-asc-highlight-.html I could use some help in debugging this since I don't even have a log after the failed boot.
