as 550.120 has been stablized in the last 24 hours, went to update and lots of 'naked' return found in RETHUNK.. flooded my console, built against last running kernerl 6.1.106-gentoo-x86_64 where the build succeded and booted to displaymanger sucessfully, can't recreate issue at present time as have reverted to 6.1.106-gentoo-x86_64 have left 6.6.52 kernel on previous nvidia-driver 550.107.02-r1, will try again within 24hrs and update if still relevant.
It makes it much easier if you include the category and version in the title.
Apologies, Thanks for correcting the title
So, if I understand this right, there's no issues right? The RETHUNK warnings are already known and shouldn't be causing problems, it's just noisy while building. Last I know of it's possible to avoid them by building against a kernel that has CONFIG_X86_KERNEL_IBT disabled (it's a security feature, so may not necessarily want to disable that just over warnings). Alternatively, I recall they don't happen with USE=kernel-open albeit enabling that requires a semi-recent card (GTX 1650+ or so).
upon encoutering the issue I did indeed check other sources and found that this issue had affected earlier kernels and the relevant patching that was done, but I found very little regard 6.6 kernels. To be fair I am running a 1030, so difficult to test further but am currently running 550.120 on 6.1.106 and as yet all seems ok, shall revist testing Tuesday 9th PM to see if I can find errors in common with the issue in previous occurances of this issue and test IBT and the kernel-open use flag. At this juncture it may simply be that the 6.6.52 kernel is yet to be patched regarding this issue the same as previous patched kernels.
This still happens even with 6.10/6.11 kernels last I know of, it'll likely keep happening until NVIDIA changes how the binary blob is built. It's long standing noise that been there for about 2 years now? You may not have noticed it before though. I forget when IBT support was added but it wasn't enabled by default until 6.2.x kernel, so likely disabled in your 6.1.x. ...but ultimately does not cause issues and can be ignored. Aka, no need to test for a way for these warnings to go away (aka, there's nothing to do here if you don't have runtime issues). There *used* to be actual runtime issues related to IBT, but nvidia fixed them a while ago.
(In reply to Ionen Wolkens from comment #5) > it'll likely keep happening until NVIDIA changes how the binary > blob is built Guess I'll close given don't think anything to do here, if actually have problems rather than just noise in the build.log please say so.
