Bug 2077359 - KDE on X11 with native graphics hangs with Nvidia GPU and UEFI
Summary: KDE on X11 with native graphics hangs with Nvidia GPU and UEFI
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 36
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: https://ask.fedoraproject.org/t/commo...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-21 07:16 UTC by stefan
Modified: 2023-05-25 15:22 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-25 15:22:49 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
lspci -nn (3.01 KB, text/plain)
2022-04-21 07:16 UTC, stefan
no flags Details
Logs from failed session (3.93 MB, text/plain)
2022-04-22 23:01 UTC, Mikhail Shchemelev
no flags Details
journal.txt (690.97 KB, text/plain)
2022-04-25 09:50 UTC, stefan
no flags Details

Description stefan 2022-04-21 07:16:53 UTC
Created attachment 1873992 [details]
lspci -nn

lspci -nn | grep VGA

01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF110 [GeForce GTX 570] [10de:1081] (rev a1)


in standard boot mode does not work, also can not go with f2 or so to the
root login.



previous discussion 

https://bugzilla.redhat.com/show_bug.cgi?id=2074789#

Comment 1 Adam Williamson 2022-04-21 15:36:05 UTC
Can you provide journal output from an attempt to boot this way? You should be able to do it like this:

* Boot in the broken way, wait for a few minutes
* Reboot with 'nomodeset' so you can access the system, log in, and run "sudo journalctl -b-1 > /tmp/journal.txt"
* Upload /tmp/journal.txt

Note, you do have to do this with an installed system, you can't do it from a live image.

Thanks a lot!

Comment 2 Mikhail Shchemelev 2022-04-22 23:01:47 UTC
Created attachment 1874512 [details]
Logs from failed session

Here's mine. GTX 1070, tested on install from Fedora-KDE-Live-x86_64-36-20220422.n.0 compose. 

The behaviour when logging in wayland session matches what i saw on loading live session in standard mode (complete lockup in couple of seconds)

Unless i hit some other issue, i think bug title should be corrected, since standard boot is wayland?
In fact it seems this issue is specific to Plasma Wayland session. 
Plasma X11 , and Gnome Wayland session on Workstation Live, and Everything netinstall (whatever is uses) all work fine.

Note: "nouveau: kernel rejected pushbuf: Недопустимый аргумент" the last part means "invalid argument"

I'm keeping this install pristine in case you need some more info

Comment 3 stefan 2022-04-25 09:50:03 UTC
Created attachment 1874792 [details]
journal.txt

here is the journal.txt


sudo journalctl -b-1 > /tmp/journal.txt" no work -b-1

Comment 4 Adam Williamson 2022-04-26 22:52:56 UTC
Mikhail: "standard boot" was in contrast to "basic graphics mode boot", from the bug this split off from. Rewriting a bit. Thanks for the logs.

Comment 5 Ben Cotton 2023-04-25 17:02:06 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 6 Adam Williamson 2023-04-27 23:21:49 UTC
was this fixed in F37 or F38, at least? sorry we never got to look into it for F36 :( nouveau is a bit understaffed.

Comment 7 Ludek Smid 2023-05-25 15:22:49 UTC
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


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