[Bug 293362] graphics/nvidia-drm-kmod: No devices on 15.0
| Newsgroups | gmane.os.freebsd.devel.x11 |
|---|---|
| Message-ID | <[email protected]/bugzilla/> |
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=293362 --- Comment #30 from Tomoaki AOKI <[email protected]> --- (In reply to Alexander Ziaee from comment #29) It would be the limitation for non-default variants that graphics/nvidia-drm-kmod{-devel} doesn't automatically detect and select. When dedicated kmod repo and its builders are made available, splitting out kmod parts from x11/nvidia-driver{-304|-340|-390|-470} into corresponding counterpart was requested (at the moment, not decided whether x11/nvidia-driver{-304|-340|-390|-470} to be kmod part or remaining parts was not specified). On kmod builders, as far as I've heared until now, kmod ports are disallowed to depend on anything large like x11-servers/xorg-server. So we've investigated how it can be achieved for NVIDIA driver things, and finally decided to split out kmod parts into x11/nvidia-kmod* ports. But unfortunately, graphics/nvidia-drm-{510|515|61|66|latest}-kmod{-devel} requires x11/nvidia-driver{-devel} to actually run for X11 and/or Wayland. Here, graphics/nvidia-drm-{510|515|61|66|latest}-kmod{-devel} is disallowed to depend upon x11/nvidia-driver{-devel} as of the limitation, as x11/nvidia-driver{-devel} depends on excessive X11 parts for kmod builders. So we need to make graphics/nvidia-drm-kmod{-devel} metaport to depend on x11/nvidia-driver{-devel} and chosen one of graphics/nvidia-drm-{510|515|61|66|latest}-kmod{-devel}, while each of graphics/nvidia-drm-{510|515|61|66|latest}-kmod{-devel} depends on x11/nvidia-kmod{-devel}. (Now we have -580 legacy variant supporting DRM/KMS.) This causes users of non-default one of graphics/nvidia-drm-{510|515|61|66|latest}-kmod{-580|-devel} to be forced to manually install corresponding x11/nvidia-driver{-580|-devel}. This could be fixed once kmod builders become almost equivalent with normal ports builders that reduces the limitation to allow merging back kmod parts into library parts, but as far as I could hear, there seems to be no plan. -- You are receiving this mail because: You are the assignee for the bug.