<div dir="auto"><div dir="ltr">Hi Julian, <div><br></div><div>Please find attached the "consolidated" patch as "final-patch.patch) (I had 3-4 which I merged into one), in case it is useful. As I mentioned, I used Claude Code to support this process, and iterated several times until a working patch was produced. (I also did the same using Gemini, but Gemini's patch seems a little bit more messy, although it also "works" (e.g. the module compiles). I can share the patch produced with Gemini as well for reference when I'm back home, although the one with Claude seemed the cleanest.)<br><br>Thanks,<br>Jonas.</div></div><br><br><div data-smartmail="gmail_signature"><div dir="ltr"><div>Jonás Andradas<br><br>GPG Fingerprint: 678F 7BD0 83C3 28CE 9E8F<br> 3F7F 4D87 9996 E0C6 9372<br></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, May 10, 2026 at 8:17 AM Julian Gilbey <<a href="mailto:jdg@debian.org" target="_blank" rel="noreferrer">jdg@debian.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Dear Jonas,<br>
<br>
Thanks for this tantalising message!<br>
<br>
Until the maintainer is able to provide a "proper" patch, would you be<br>
able to share your patch? The maintainer might well then be able to<br>
check it and either approve or improve on it.<br>
<br>
Best wishes,<br>
<br>
Julian<br>
<br>
On Fri, May 08, 2026 at 08:50:33AM +0200, Jonas Andradas wrote:<br>
> Package: nvidia-kernel-dkms<br>
> Version: 550.163.01-5<br>
> Followup-For: Bug #1135362<br>
> X-Debbugs-Cc: <a href="mailto:debian-amd64@lists.debian.org" target="_blank" rel="noreferrer">debian-amd64@lists.debian.org</a>, <a href="mailto:j.andradas@gmail.com" target="_blank" rel="noreferrer">j.andradas@gmail.com</a><br>
> User: <a href="mailto:debian-amd64@lists.debian.org" target="_blank" rel="noreferrer">debian-amd64@lists.debian.org</a><br>
> Usertags: amd64<br>
> Control: tags -1 ftbfs<br>
> <br>
> Dear Maintainer,<br>
> <br>
> I am experiencing this as well in my Debian sid system. I had a similar issue a<br>
> couple of weeks ago in a Proxmox host (running Debian trixie), as Proxmox<br>
> provides its own kernel and it was bumped to version 7. Leveraging AI (Gemini<br>
> and Claude) I managed to obtain patches for the nvidia-kernel-dkms package in<br>
> trixie, so that it would compile for Proxmox's kernel 7. These compile and I<br>
> get the functionality, so for me it was "good enough" for my homelab, but I<br>
> would not be so bold as to presume they are the best patch possible. If these<br>
> patches can be useful to see the changes that were needed to make this work,<br>
> such as the ones below, I could upload the file under debian/patches that<br>
> applied to the trixie package allowed me to built it for Proxmox's kernel 7:<br>
> <br>
> - conftest.sh: detect NV_VM_AREA_STRUCT_HAS___VM_FLAGS, absence of<br>
> dma_map_ops.map_resource, void return of dma_fence_signal, and<br>
> drm_mode_config_funcs.fb_create format_info argument<br>
> - nv-mm.h: handle vma->vm_flags cast for kernels without __vm_flags<br>
> - nv-mmap.c: wrap VMA_LOCK_OFFSET and __is_vma_write_locked for 1-arg form<br>
> - nv-time.h: compat shim for removed in_irq() macro<br>
> - nv-dma.c: guard dma_map_ops.map_resource access<br>
> - <a href="http://header-presence-tests.mk" rel="noreferrer noreferrer" target="_blank">header-presence-tests.mk</a>: add drm/drm_print.h detection<br>
> - nvidia-drm-priv.h: include drm_print.h for DRM_ERROR/DRM_INFO/DRM_DEBUG<br>
> - nvidia-dma-fence-helper.h: handle void dma_fence_signal return type<br>
> - nvidia-drm-helper.h: use for_each_new_*_in_state iterators<br>
> - nvidia-drm-drv.c, nvidia-drm-fb.c: handle fb_create format_info arg<br>
> <br>
> <br>
> Thanks,<br>
> Jonas.<br>
</blockquote></div><div><br clear="all"></div><div><br></div>