Get Gentoo!
gentoo.org sites
gentoo.org Wiki Bugs Forums Packages
Planet Archives Sources
Infra Status
summaryrefslogtreecommitdiff
path: root/x11-drivers
Commit message (Collapse)AuthorAgeFilesLines
* x11-drivers/nvidia-drivers: add 525.47.31:0/vulkan, drop 525.47.27Ionen Wolkens2023-07-122-8/+3
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: drop additional framebuffer/drm warningsIonen Wolkens2023-07-085-325/+15
| | | | | | | | | | | | | | | | | | | | | | | | | Warnings were mostly added to help the transition to newer kernels for unsuspecting users. May have helped in some cases, not in others. But with 6.1.x being stable for a while, there's little reason to keep this wall of warnings *here* and try to keep it accurate and updated -- especially when we can't tell what's really in-use or what the user needs (this was just vague suggestions). For initial setting up issues, it sounds better to refer to the Wiki. So if anyone has anything to share with their experience with FB (or other issues) feel free to edit it and improve it so it can help others. Also drop the "builtin" nouveau check that was part of this block. Module is already blacklisted and, if users went out of their way to make it builtin, then let's assume they know what they're doing. Closing #910058 but rather than a fix it's more of a dissociation. Closes: https://bugs.gentoo.org/910058 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* Revert "x11-drivers/xf86-input-wacom: Drop old versions"Sam James2023-07-032-0/+82
| | | | | | | | | This reverts commit f820cfb16e9fe4e496e7d51746ae086d9a4e4b59. It got dropped again, but see 138405e809ff0e3fb82967bf3053ea23a14ccfa4. Bug: https://bugs.gentoo.org/906995 Signed-off-by: Sam James <sam@gentoo.org>
* x11-drivers/nvidia-drivers: drop vuln 470.182.03-r2, 525.116.04-r2Ionen Wolkens2023-07-033-1070/+0
| | | | | | | All done wrt bug #909226 Bug: https://bugs.gentoo.org/909226 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: stabilize 525.125.06 for amd64Ionen Wolkens2023-07-031-1/+1
| | | | | Bug: https://bugs.gentoo.org/909226 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: stabilize 470.199.02 for amd64Ionen Wolkens2023-07-031-1/+1
| | | | | Bug: https://bugs.gentoo.org/909226 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: add 525.125.06Ionen Wolkens2023-06-262-0/+569
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: add 470.199.02Ionen Wolkens2023-06-262-0/+506
| | | | | | This also brings kernel 6.4 support to the 0/470 branch. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: update and install vulkan icd for USE=-XIonen Wolkens2023-06-265-23/+19
| | | | | | | | | | | | | | | Not really tested, but it should be harmless vs not having the file. Skipping revbump, letting it propagate on kernel upgrades / bumps (470 and 525 are bumped in next commits). Please rebuild if want this now for other versions. For 390.x the icd is a template, while the newer drivers had hardcoded libGLX, but docs mentions libEGL is usable for all versions (unlikely to be useful for 390.x given its partial wayland support is broken). Closes: https://bugs.gentoo.org/909181 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: drop vuln 515.105.01-r2 (dead branch)Ionen Wolkens2023-06-262-570/+0
| | | | | | | | | | There is new CVEs for nvidia-drivers but this branch was not updated for it. Assumed to be EOL, so it's time to drop it. If for some reason newer drivers don't work right for you, please fallback to the 470.x branch which is on long term support. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: bump KERNEL_MAX to 6.4 where possibleIonen Wolkens2023-06-253-3/+3
| | | | | | | | There was one "new" issue that affects 0/470 with 6.4 on top of 6.3's, but newer versions already have a condition to not use the removed dumb_destroy callback. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: drop 530.41.03-r2, 535.43.02-r2Ionen Wolkens2023-06-253-1146/+0
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: fix comment typoIonen Wolkens2023-06-171-1/+1
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: backport clang options fix to 525 branchIonen Wolkens2023-06-173-0/+19
| | | | | | | | | Technically 0/390+470+515 also need this, but they have bigger issues with clang-16 and I can only recommend to not use clang with old branches. NVIDIA may update 470 for clang in the future though, the others are unlikely. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: add 525.47.27:0/vulkan, drop 525.47.26Ionen Wolkens2023-06-162-2/+2
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/xf86-video-nouveau: update HOMEPAGEMichael Mair-Keimberger2023-06-151-2/+2
| | | | | Signed-off-by: Michael Mair-Keimberger <mmk@levelnine.at> Signed-off-by: Sam James <sam@gentoo.org>
* x11-drivers/nvidia-drivers: minor ebuild nitpicksIonen Wolkens2023-06-148-24/+24
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: add 535.54.03Ionen Wolkens2023-06-142-0/+579
| | | | | | | New production branch (now non-beta), and a potential future stable candidate. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: revbump for eclass' depmod.d changesIonen Wolkens2023-06-056-0/+0
| | | | | | | | | | Apologies for another rebuild in the short timeframe. See previous linux-mod-r1.eclass commit if want an explanation. Rebuild is not needed for the vast majority of people, but is a precaution given how easy it is to get API mismatch issues. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/xf86-video-intel: Drop old versionsMatt Turner2023-06-052-94/+0
| | | | Signed-off-by: Matt Turner <mattst88@gentoo.org>
* x11-drivers/xf86-video-geode: Drop old versionsMatt Turner2023-06-053-122/+0
| | | | Signed-off-by: Matt Turner <mattst88@gentoo.org>
* x11-drivers/xf86-video-dummy: Drop old versionsMatt Turner2023-06-052-15/+0
| | | | Signed-off-by: Matt Turner <mattst88@gentoo.org>
* x11-drivers/xf86-video-ati: Drop old versionsMatt Turner2023-06-054-456/+0
| | | | Signed-off-by: Matt Turner <mattst88@gentoo.org>
* x11-drivers/xf86-input-wacom: Drop old versionsMatt Turner2023-06-052-82/+0
| | | | Signed-off-by: Matt Turner <mattst88@gentoo.org>
* x11-drivers/nvidia-drivers: extend postinst mismatch warningIonen Wolkens2023-06-057-7/+42
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: adjust openssl handling in 0/535Ionen Wolkens2023-06-051-20/+10
| | | | | | | | | | | | | | | 1. Noticed portage does not easily figure out rebuilds if do a plain `emerge openssl:0/1.1`, but does if drop the || ( ) block. Not fully correct to given wouldn't work with theoretical new subslots, but dropping it for user experience sake (ultimately this is temporary). Skip rebuild given this version won't be keyworded (this is for the next one) and is still rebuilt on kernel bumps either way. 2. Had modified the .manifest block to handle this, but there is no need to. Revert and use skip_files. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: reset insopts after .manifestIonen Wolkens2023-06-047-0/+7
| | | | | | | | | | | | Just noticed /etc/sandbox.d/20nvidia was installed executable, thankfully very few likely have it yet plus it gets cleared on kernel bumps. Could re-order so nothing is done after .manifest, or use a subshell but feel it'd be more confusing / nastier. May revisit the general handling of .manifest eventually. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: migrate all remaining to linux-mod-r1Ionen Wolkens2023-06-048-583/+140
| | | | | | | | | | | | | | | | Bit of a risky move (stable), but given just did a revbump for sandbox.d and that IUSE=+modules/+strip will cause a rebuild as well, it makes some sense to do this at same time. Migration did mostly prove itself with ~arch's 0/530 so far and other notable modules are using the eclass already, and no known issues. So let's hope. *Should* have no real impact on users unless they were disabling USE=driver given renamed to modules to match global IUSE, but will fix asap if something else comes up. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: use sandbox.d for /dev/nvidiactl+/dev/charIonen Wolkens2023-06-047-0/+49
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | /dev/nvidiactl been a long standing issue, sometime appearing in sneaky ways when a revdeps is built with opencl/cuda support even though the package itself does not use it. And /dev/char is newly needed with >=nvidia-drivers-525.105.17 or >=535.43.02, but not 530.41.03. The production branch's 525.105.17 is newer than ~arch's long-living 530 and led to this being overlooked until it hit stable (older stable 525.89.02 was not affected) and was unaware of this until rebuilt libomp[offload] with 535 today (note that 535.43.02 is unkeyworded, it's a beta). Need /dev/char rather than /dev/char/195:255 given it tries to remove + create a symlink and does not simply try to write there. This is not meant to be a full coverage of nvidia devices and only for those being a widespread problem. Special needs or addwrite (typically to run tests) should be handled manually or using cuda.eclass' cuda_add_sandbox. Adding /dev/char to all versions even if not needed *yet* just so it's not overlooked when nvidia spreads it to other branches (except 390 given it's EOL, not to mention has no cuda packages anymore). Bug: https://bugs.gentoo.org/904292 Bug: https://bugs.gentoo.org/905436 Closes: https://bugs.gentoo.org/904944 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/xf86-video-dummy: Stabilize 0.4.1 sparc, #907616Arthur Zamarin2023-06-031-1/+1
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* x11-drivers/xf86-video-ati: Stabilize 22.0.0 sparc, #907616Arthur Zamarin2023-06-031-1/+1
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* x11-drivers/xf86-video-dummy: Stabilize 0.4.1 arm, #907616Sam James2023-06-011-1/+1
| | | | Signed-off-by: Sam James <sam@gentoo.org>
* x11-drivers/xf86-video-dummy: Stabilize 0.4.1 ppc64, #907616Arthur Zamarin2023-06-011-1/+1
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* x11-drivers/xf86-video-ati: Stabilize 22.0.0 ppc64, #907616Arthur Zamarin2023-06-011-1/+1
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* x11-drivers/xf86-video-intel: Stabilize 2.99.917_p20230201 x86, #907616Arthur Zamarin2023-06-011-1/+1
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* x11-drivers/xf86-video-geode: Stabilize 2.11.21 x86, #907616Arthur Zamarin2023-06-011-1/+1
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* x11-drivers/xf86-video-dummy: Stabilize 0.4.1 x86, #907616Arthur Zamarin2023-06-011-1/+1
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* x11-drivers/xf86-video-ati: Stabilize 22.0.0 x86, #907616Arthur Zamarin2023-06-011-1/+1
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* x11-drivers/xf86-video-intel: Stabilize 2.99.917_p20230201 amd64, #907616Arthur Zamarin2023-06-011-1/+1
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* x11-drivers/xf86-video-dummy: Stabilize 0.4.1 amd64, #907616Arthur Zamarin2023-06-011-1/+1
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* x11-drivers/xf86-video-ati: Stabilize 22.0.0 amd64, #907616Arthur Zamarin2023-06-011-1/+1
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* x11-drivers/xf86-video-dummy: Stabilize 0.4.1 ppc, #907616Arthur Zamarin2023-06-011-1/+1
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* x11-drivers/xf86-video-ati: Stabilize 22.0.0 ppc, #907616Arthur Zamarin2023-06-011-1/+1
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* x11-drivers/xf86-video-ati: Stabilize 22.0.0 arm64, #907616Arthur Zamarin2023-06-011-1/+1
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* x11-drivers/nvidia-drivers: drop modules dir rename commentIonen Wolkens2023-05-302-6/+0
| | | | | | | | | | | | Don't think will touch this for the time being given it needs a postinst to delete old modules if they changed location. Not something was really thinking about, not a major issue with most modules given will be cleaned on kernel upgrades but with nvidia it means API mismatch issues until then. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: add 535.43.02 (unkeyworded)Ionen Wolkens2023-05-302-0/+578
| | | | | | | | | | | Only unkeyworded because marked BETA, no notable known issues outright so feel free to opt-in if wanted. Note that this now needs openssl, it bas alternate prebuilts to allow using either 0/1.1 or 0/3 making := subslot rebuilds meaningful (but will switch to hard-requiring 0/3 eventually). Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: migrate latest to linux-mod-r1Ionen Wolkens2023-05-301-119/+35
| | | | | | | | | | | | If no notable issues, the others will be done straight-to-stable at a later date to avoid extra churn managing old branches. This also renames USE=driver to USE=modules to be in-line with other ebuilds, may disrupt a few users in chroots and such (assuming didn't already have a global -modules) but hopefully is obvious enough. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: drop 525.116.03Ionen Wolkens2023-05-262-642/+0
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* Revert "x11-drivers/xf86-input-wacom: Drop old versions"Sam James2023-05-262-0/+82
| | | | | | | | | | | This reverts commit 95608c4d0f8480e8b896b6ea481875c2d0048d48. 1.2.0 seems to have some issues, so restore 1.1.0 for now. Bug: https://bugs.gentoo.org/906995 Bug: https://gitlab.gnome.org/GNOME/gimp/-/issues/9385 Bug: https://github.com/linuxwacom/xf86-input-wacom/issues/307 Signed-off-by: Sam James <sam@gentoo.org>
* x11-drivers/nvidia-drivers: soften IBT warningIonen Wolkens2023-05-246-12/+18
| | | | | | | | | | | | | | | | | | The situation around this is still unclear, getting conflicting reports and (if actually fixed), it's still unclear which versions have received backports. Does not help that, at least initially, it was only fixed with USE=kernel-open because (unlike nvidia last I know of) we are using a newer gcc. And then changelog entries often have mixups (and wrt news outlets, afaik all they did is read these). If anyone reading this actually uses IBT, please send a report if the blob works as intended. Not changing 390's ebuild given that one is almost certainly broken. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>