XPost: linux.debian.kernel

Hi,

Please provide complete file paths to check the firmware files.

If I copy /lib/modules/6.15.4-200.fc42.x86_64 from Fedora into Debian's /lib/modules/, can I use "sudo update-grub"  to update the grub boot
entry or do I need to manually edit the entry?

regards,

Benjamin

On 7/21/25 09:50, Uwe Kleine-König wrote:

Hello,

On Sat, Jul 12, 2025 at 08:51:22PM -0600, Benjamin Martin wrote:

Uwe, I tried to run the commands you gave on my Fedora install but was met >> with errors when running the make commands, I did not try it on my Debian
install.


Please see attached boot logs of Fedora, and Debian with kernel 6.15
installed. There are 3 boot sessions in the Debian boot log. First was with >> 2 monitors, 2nd was with all 3 connected (it failed), and 3rd was with 2
connected. Fedora was with all 3 connected.

Thanks. For the future can you please use

journalctl -b -k

to only contain the kernel logs. That makes it a bit easier on the
receiving end.

Comparing the 2nd Debian log with the fedora one I don't spot the
problem. Debian has a message

nouveau 0000:01:00.0: pmu: firmware unavailable

which might be a hint that the relevant hint is related to firmware.

There are a few more differences: Debian has several lines

nouveau 0000:01:00.0: i2c: aux 0004: magic wait 00008000

and timeout messages:

nouveau 0000:01:00.0: sec2:cmdq: timeout waiting for reply
nouveau 0000:01:00.0: gr: init failed, -110
nouveau 0000:01:00.0: timeout
WARNING: CPU: 2 PID: 932 at drivers/gpu/drm/nouveau/nvkm/engine/gr/gf100.c:841 gf100_gr_fecs_bind_pointer+0x123/0x140 [nouveau]
ee1004 wmi_bmof snd_hwdep snd_pcm pcspkr intel_uncore snd_timer snd mei_me mei soundcore intel_pch_thermal raid6_pq joydev intel_pmc_core pmt_telemetry pmt_class intel_vsec acpi_pad evdev sg msr parport_pc ppdev lp parport configfs efi_pstore

nfnetlink efivarfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid nouveau uas usb_storage mxm_wmi drm_gpuvm gpu_sched sd_mod drm_ttm_helper ttm drm_exec drm_display_helper cec
rc_core drm_client_lib drm_kms_helper ahci libahci xhci_pci libata drm nvme xhci_hcd iTCO_wdt scsi_mod intel_pmc_bxt igb iTCO_vendor_support nvme_core watchdog usbcore i2c_algo_bit e1000e nvme_keyring dca nvme_auth i2c_i801 usb_common video i2c_smbus
scsi_common fan wmi button

RIP: 0010:gf100_gr_fecs_bind_pointer+0x123/0x140 [nouveau]
gf100_grctx_generate+0x2c4/0x720 [nouveau]
gf100_gr_chan_new+0x458/0x490 [nouveau]
nvkm_cgrp_ectx_get+0x154/0x1e0 [nouveau]
nvkm_cgrp_vctx_get+0xf7/0x2b0 [nouveau]
nvkm_chan_cctx_get+0x125/0x220 [nouveau]
nvkm_uchan_object_new+0xd3/0x1e0 [nouveau]
nvkm_ioctl_new+0x141/0x220 [nouveau]
? __pfx_nvkm_uchan_object_new+0x10/0x10 [nouveau]
? __pfx_gf100_gr_object_new+0x10/0x10 [nouveau]
nvkm_ioctl+0xbc/0x190 [nouveau]
nvif_object_ctor+0x121/0x1a0 [nouveau]
nouveau_abi16_ioctl+0x4fa/0x5b0 [nouveau]
nouveau_drm_ioctl+0xa2/0xb0 [nouveau]
nouveau 0000:01:00.0: gr: failed to construct context
nouveau 0000:01:00.0: fifo:000000:0003:[Xorg[932]] ectx 0[gr]: -110
nouveau 0000:01:00.0: fifo:000000:0003:0003:[Xorg[932]] vctx 0[gr]: -110

Can you please compare the used firmware blobs between Debian and
fedora? And maybe try booting the Debian system with the fedora kernel
(and vice versa).

For the latter I'd copy fedora's /lib/modules/6.15.4-200.fc42.x86_64
into the Debian rootfs and then edit fedora's grub boot entry to use

root=UUID=6c47cad0-3157-4246-94b0-1985db645ff0

instead of

root=UUID=9445de78-114f-4960-9823-cefaa8824cf1 rootflags=subvol=root resume=UUID=ae6b6cd8-1d85-4f26-b7e6-ce442951cc79

.

If you spot a difference in the firmware files it might also be worth to
boot Debian with fedora's firmware blobs.

Best regards
Uwe

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: linux.debian.kernel

Hi Uwe,

I forgot to mention that the Fedora firmware files were all compressed.
Maybe that is the reason for the firmware errors in the log. Where as
the Debian files are not compressed.


Regards Benjamin.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: linux.debian.kernel

On 2025-07-25 20:24, Benjamin Martin wrote:

With 3 monitors connected I got a black screen, the monitors were turned
on, but black. See log for 3 monitors.

With 2 monitors I was able to login and get to the desktop but was

You problem seems similar to mine. I thought it had to do with 2
monitors on DisplayPort and one on HDMI. My mouse was also sluggish.
And in certain modeset settings, I'd get a blinking cursor in the upper
left corner and nothing else.

All when using Wayland.

I ended up connecting all three monitors as display port to one card:
NVIDIA GeForce RTX 5070 Ti. I have this nvidia driver installed: 575.64.03

I think the key point though is I switched away from Wayland back to
X11. Everything is responsive again.

As much as I'd like to run Wayland, it does seem to have some shortcomings.

You can choose X11 mode in Trixie with KDE (assuming that is what you
are using), but choosing the renderer in the lower left corner prior to
logging in.

Hope this helps.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)