Bug 2162874 - black screen on booting a luks encrypted installation
Summary: black screen on booting a luks encrypted installation
Keywords:
Status: CLOSED DUPLICATE of bug 2161104
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 37
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-01-21 17:36 UTC by oli
Modified: 2023-01-24 15:07 UTC (History)
18 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-01-24 15:07:31 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmesg (99.84 KB, text/plain)
2023-01-21 17:36 UTC, oli
no flags Details

Description oli 2023-01-21 17:36:21 UTC
Created attachment 1939654 [details]
dmesg

1. Please describe the problem:
when booting a luks encrypted fedora installation, the screen is black when it should ask for the password. one has to enter the password on a blank black screen

2. What is the Version-Release number of the kernel:
6.1.6-200.fc37.x86_64

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :
iirc 6.0.x

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
yes, always, install a f37 and do a dnf upgrade

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:
not sure, dont want to mess up my system

6. Are you running any modules that not shipped with directly Fedora's kernel?:
i use nvidia drivers from rpmfusion

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

Comment 1 Justin M. Forbes 2023-01-24 15:07:31 UTC

*** This bug has been marked as a duplicate of bug 2161104 ***


Note You need to log in before you can comment on or make changes to this bug.