Bug 2181175 - Black screen after system boot and not able to login to via graphic interface.
Summary: Black screen after system boot and not able to login to via graphic interface.
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 37
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-23 09:34 UTC by Dejan Rasic
Modified: 2023-07-04 16:57 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Dejan Rasic 2023-03-23 09:34:36 UTC
Description of problem:
I am using Fedora 37 kernel vmlinuz-6.2.7-200.fc37.x86_64
After update I am not able to login via GUI. System is unresponsive just get a black screen.
I can login via console, ctl+alt+f3 and get non graphical mode but I can't switch back 
to GUI. After running ctro+alt+f1 i am getting the login page but "it works in infinite loop".
Currently  I am using lover kernel version, vmlinuz-6.1.18-200.fc37.x86_64, and it works fine.

At the moment I can't provide more details via problem reporting tool.

My system is HP Victus 
CPU
Architecture:            x86_64
  CPU op-mode(s):        32-bit, 64-bit
  Address sizes:         39 bits physical, 48 bits virtual
  Byte Order:            Little Endian
CPU(s):                  20
  On-line CPU(s) list:   0-19
Vendor ID:               GenuineIntel
  Model name:            12th Gen Intel(R) Core(TM) i7-12700H

Storage:
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
zram0       252:0    0     8G  0 disk [SWAP]
nvme0n1     259:0    0 476.9G  0 disk 
├─nvme0n1p1 259:1    0   512M  0 part 
├─nvme0n1p2 259:2    0   4.9G  0 part 
├─nvme0n1p3 259:3    0   510M  0 part 
├─nvme0n1p4 259:4    0   976M  0 part /boot/efi
├─nvme0n1p5 259:5    0   7.6G  0 part [SWAP]
└─nvme0n1p6 259:6    0   439G  0 part /var/lib/docker/btrfs
                                      /var
                                      /home
                                      /
graphic:
dmesg | grep -iE 'secure|nvidia'
[    0.000000] secureboot: Secure boot disabled
[    0.006524] secureboot: Secure boot disabled
[    2.470293] sdhci: Secure Digital Host Controller Interface driver
[    2.747753] nouveau 0000:01:00.0: NVIDIA TU117 (167000a1)
[    6.122379] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input31
[    6.122436] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input32
[    6.122469] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input33
[    6.122509] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input34





Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
 Before this problem I also had few problems, type  #512481 whic is already reported.

Comment 1 Dejan Rasic 2023-04-01 07:36:09 UTC
Hi , 
Please let me know if there is any update or I should provide more details?

Regards, 
Dejan

Comment 2 Dejan Rasic 2023-04-19 06:34:13 UTC
Hi , 
Please let me know if there is any update or I should provide more details?

Regards, 
Dejan

Comment 3 ben 2023-07-02 11:06:32 UTC
A previous update to this worked on my other boxes but with my Gigabyte AERO machine it still shows a blank screen on kernels 3.6.7 and above

Operating System: Fedora Linux 38
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.10
Kernel Version: 6.3.8-200.fc38.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz
Memory: 31.1 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 630
Manufacturer: GIGABYTE
Product Name: AERO 15-WA

Comment 4 ben 2023-07-02 16:10:34 UTC
Never mind I think it's NVIDIA related as it's only happening with custom kernel and driver

Comment 5 ben 2023-07-02 18:43:38 UTC
No, (why is this still an issue?)I've now logged in using custom kernel 6.3.6 even without the NVIDIA driver I installed on 6.3.8.

Comment 6 ben 2023-07-04 16:57:34 UTC
Yeah, wrong kernel.
Anyway, my problem was resolved by removing Xorg.conf
Plus my login was not blank it had the Fedora logo along with the machines BIOS Logo


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