When installing the ebuild in portage, dmesg shows this message: NVRM: bad caching on address 0xffff81011c820000: actual 0x173 != expected 0x17b NVRM: please see the README section on Cache Aliasing for more information NVRM: bad caching on address 0xffff81011c820000: actual 0x173 != expected 0x17b NVRM: bad caching on address 0xffff81011c822000: actual 0x173 != expected 0x17b NVRM: bad caching on address 0xffff81011c822000: actual 0x173 != expected 0x17b NVRM: bad caching on address 0xffff81011c823000: actual 0x173 != expected 0x17b NVRM: bad caching on address 0xffff81011c823000: actual 0x173 != expected 0x17b NVRM: bad caching on address 0xffff81011c824000: actual 0x173 != expected 0x17b NVRM: bad caching on address 0xffff81011c824000: actual 0x173 != expected 0x17b NVRM: bad caching on address 0xffff81011c825000: actual 0x173 != expected 0x17b NVRM: bad caching on address 0xffff81011c825000: actual 0x173 != expected 0x17b On nvnews website it is being said that there is nothing to worry about it, but to fix it they propose the patch I attached this bug report, also I proposed an ebuild bump to 107.08-r1, where the file is patched with the instructions present on the post where is explained the cause of this and the patch needed to fix it: http://nvnews.net/vbulletin/showthread.php?t=110965
Created attachment 154767 [details] ebuild bump
Created attachment 154769 [details, diff] The patch to fix nv.c
This is not a patch approved by upstream (i.e. posted by zander or AaronP on nvnews in a sticky topic). I'm sorry to report that I am not willing to carry such patches in an ebuild, especially when they serve no purpose but to squelch a harmless warning.
Created attachment 159971 [details] autoconf-30063.out Forgot to attach this, sorry...
Oh sorry, I posted the attachment to the wrong bug :-(
