Nouveau - Aug 2022 - Blank screen after upgrade Fedora 34/XFCE -> Fedora 36/XFCE

Hi nouveau at lists.freedesktop.org,


I hope someone on this list can point me in some useful direction concerning the
following problem:


After upgrade from Fedora 34/XFCE to Fedora 36/XFCE, I experience a black screen
instead of a login prompt, unless I make a file named
/etc/X11/xorg.conf.d/90-monitor.conf which contains eg


Section "Monitor"
        Identifier "DP-1"
        Option "PreferredMode" "720x480"
EndSection

Before the upgrade from Fedora 34 to 36, everything worked if the file looked
like this:

Section "Monitor"
        Identifier "DP-1"
        Modeline "3840x2160" 533.25 3840 3888 3920 4000 2160 2163 2168
2222 +hsync -vsync
        Option "PreferredMode" "3840x2160"
EndSection

But that does not work on my Fedora 36.

I use XFCE instead of Gnome. XFCE seems to use X as opposed to Fedora in general
and Gnome in particular who use Wayland.

If I hand compile the EDID from the screen, I find the following resolutions:
Established timings: 800x600, 800x600, 800x600, 800x600, 832x624, 1024x768,
1024x768, 1024x768, 1280x1024. Standard timings: 1920x1080, 1680x1050, 1440x900,
1280x1024, 1280x960, 1280x720. Detailed timings: 3840x2160, 2560x1440, 1280x720,
720x480, 720x576, 1920x2160. The EDID looks fine as far as I can see.

I have tried all standard and detailed timings and three established timings
(boot at runlevel 3, modify 90-monitor.conf, telinit 5, repeat). All resolutions
except 3840x2160, 2560x1440 and 1920x1080 work acceptably. 3840x2160 and
2560x1440 give a black screen and a monitor poweroff. 1920x1080 gives a noisy,
psychedelic screen which remotely resembles a login screen.

If I boot with no 90-monitor.conf at all then /var/log/Xorg.0.log seems to be in
conflict with itself. First, all resolutions including 3840x2160 are recognized
and agree with what I got out of reading the EDID. But then Xorg.0.log says:

[    38.974] (II) modeset(0): Not using default mode "2560x1440" (bad
mode clock/interlace/doublescan)

But 3840x2160 is the default mode. 3840x2160 is the first detailed timing
record. So it seems that first 3840x2160 is recognized, then ignored, then
2560x1440 is frowned upon, then used anyways.

I have attached /var/log/messages and /var/log/Xorg.0.log from a Fedora 36 and a
Fedora 34 boot. I do not yet have a kernel log, but I hope I can get one by
doing an ssh into the box after the monitor goes blank.

By the way, when I boot Fedora 36 to runlevel 3 then the monitor switches to a
resolution of 3840x2160 and I get a tiny command line. It is when I then do
telinit 5 that the screen goes blank.


In preparation of asking a question on the present list, I have run through
https://nouveau.freedesktop.org/TroubleShooting.html in general and the section
"Are you clear of other kernel drivers that break Nouveau" in
particular. I think I have no other video drivers than Nouveau, but I have done
this:


sudo find /usr -type f -iname "*nvidia*" -print > stdout
2>stderr


I can see some nvidia stuff in stdout. In particular, I can see a file named
typec_nvidia.ko.xz, and TroubleShooting.html warns about a file named nvidia.ko.
Can anyone on the list tell if there is something suspicious in the attached
search-nvidia-stdout?


Cheers,

Klaus

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20220810/4455276a/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: var-log-Xorg.0.log-fedora36
Type: application/octet-stream
Size: 54480 bytes
Desc: var-log-Xorg.0.log-fedora36
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20220810/4455276a/attachment-0005.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: var-log-Xorg.0.log-fedora34
Type: application/octet-stream
Size: 57427 bytes
Desc: var-log-Xorg.0.log-fedora34
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20220810/4455276a/attachment-0006.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: var-log-messages-fedora36
Type: application/octet-stream
Size: 298951 bytes
Desc: var-log-messages-fedora36
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20220810/4455276a/attachment-0007.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: var-log-messages-fedora34
Type: application/octet-stream
Size: 250541 bytes
Desc: var-log-messages-fedora34
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20220810/4455276a/attachment-0008.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: search-nvidia-stdout
Type: application/octet-stream
Size: 5315 bytes
Desc: search-nvidia-stdout
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20220810/4455276a/attachment-0009.obj>

On Wed, Aug 10, 2022 at 9:04 PM Klaus Ebbe Grue <grue at di.ku.dk>
wrote:
>
> Hi nouveau at lists.freedesktop.org,
>
>
> I hope someone on this list can point me in some useful direction
concerning the following problem:
>
>
> After upgrade from Fedora 34/XFCE to Fedora 36/XFCE, I experience a black
screen instead of a login prompt, unless I make a file named
/etc/X11/xorg.conf.d/90-monitor.conf which contains eg
>
>
> Section "Monitor"
>         Identifier "DP-1"
>         Option "PreferredMode" "720x480"
> EndSection
>
> Before the upgrade from Fedora 34 to 36, everything worked if the file
looked like this:
>
> Section "Monitor"
>         Identifier "DP-1"
>         Modeline "3840x2160" 533.25 3840 3888 3920 4000 2160 2163
2168
2222 +hsync -vsync
>         Option "PreferredMode" "3840x2160"
> EndSection
>
> But that does not work on my Fedora 36.
>
did you try not using any custom Xorg config, because I don't see why you
are even trying that?

> I use XFCE instead of Gnome. XFCE seems to use X as opposed to Fedora in
general and Gnome in particular who use Wayland.
>
> If I hand compile the EDID from the screen, I find the following
resolutions: Established timings: 800x600, 800x600, 800x600, 800x600,
832x624, 1024x768, 1024x768, 1024x768, 1280x1024. Standard timings:
1920x1080, 1680x1050, 1440x900, 1280x1024, 1280x960, 1280x720. Detailed
timings: 3840x2160, 2560x1440, 1280x720, 720x480, 720x576, 1920x2160. The
EDID looks fine as far as I can see.
>
> I have tried all standard and detailed timings and three established
timings (boot at runlevel 3, modify 90-monitor.conf, telinit 5, repeat).
All resolutions except 3840x2160, 2560x1440 and 1920x1080 work acceptably.
3840x2160 and 2560x1440 give a black screen and a monitor poweroff.
1920x1080 gives a noisy, psychedelic screen which remotely resembles a
login screen.
>
> If I boot with no 90-monitor.conf at all then /var/log/Xorg.0.log seems
to be in conflict with itself. First, all resolutions including 3840x2160
are recognized and agree with what I got out of reading the EDID. But then
Xorg.0.log says:
>
> [    38.974] (II) modeset(0): Not using default mode "2560x1440"
(bad
mode clock/interlace/doublescan)
>
> But 3840x2160 is the default mode. 3840x2160 is the first detailed timing
record. So it seems that first 3840x2160 is recognized, then ignored, then
2560x1440 is frowned upon, then used anyways.
>
> I have attached /var/log/messages and /var/log/Xorg.0.log from a Fedora
36 and a Fedora 34 boot. I do not yet have a kernel log, but I hope I can
get one by doing an ssh into the box after the monitor goes
blank.
>
> By the way, when I boot Fedora 36 to runlevel 3 then the monitor switches
to a resolution of 3840x2160 and I get a tiny command line. It is when I
then do telinit 5 that the screen goes blank.
>
>
> In preparation of asking a question on the present list, I have run
through https://nouveau.freedesktop.org/TroubleShooting.html in general and
the section "Are you clear of other kernel drivers that break Nouveau"
in
particular. I think I have no other video drivers than Nouveau, but I have
done this:
>
>
> sudo find /usr -type f -iname "*nvidia*" -print > stdout
2>stderr
>
>
> I can see some nvidia stuff in stdout. In particular, I can see a file
named typec_nvidia.ko.xz, and TroubleShooting.html warns about a file named
nvidia.ko. Can anyone on the list tell if there is something suspicious in
the attached search-nvidia-stdout?
>
>
> Cheers,
>
> Klaus
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20220810/c845eec0/attachment.htm>