From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 364F21381F3 for ; Sun, 25 Aug 2013 20:00:24 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4512FE0B1A; Sun, 25 Aug 2013 20:00:11 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 278EDE0AE3 for ; Sun, 25 Aug 2013 20:00:10 +0000 (UTC) Received: from [192.168.4.8] (blfd-4d08ee80.pool.mediaWays.net [77.8.238.128]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: hasufell) by smtp.gentoo.org (Postfix) with ESMTPSA id 9000F33EE71 for ; Sun, 25 Aug 2013 20:00:03 +0000 (UTC) Message-ID: <521A6241.8090301@gentoo.org> Date: Sun, 25 Aug 2013 22:00:01 +0200 From: hasufell User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130816 Thunderbird/17.0.8 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: The NVIDIA/Kernel fiasco -- is it safe to sync yet? References: <20130824194527.122b5436@fuchsia.remarqs.net> <521A2E41.2020001@gmail.com> <201308251734.25129.michaelkintzios@gmail.com> In-Reply-To: <201308251734.25129.michaelkintzios@gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Archives-Salt: 0e41b40d-008a-42ec-b245-8569c2c171b6 X-Archives-Hash: d54f1009a84eb266b7501dfd992bd621 On 08/25/2013 06:34 PM, Mick wrote: > On Sunday 25 Aug 2013 17:18:09 Alan McKinnon wrote: >> On 25/08/2013 02:45, »Q« wrote: >>> On Sat, 24 Aug 2013 09:49:43 +0200 >>> >>> Alan McKinnon wrote: >>>> On 24/08/2013 06:26, Chris Stankevitz wrote: >>>>> On Fri, Aug 23, 2013 at 9:12 PM, »Q« wrote: >>>>>> It looks like maybe the best way to tell which ebuilds support >>>>>> which kernels is to read the conditional for the ewarn message in >>>>>> each ebuild. >>>>> >>>>> If this sort of problem spreads it might be good to build into >>>>> portage some kind of blocker/keyword mechanism so that users need >>>>> not deal with this.... not that I have any appreciation for the >>>>> work involved. >>>> >>>> Those tools already exist. >>>> >>>> Blockers, which do not really apply here; >>> >>> In a comment on the bug (which is full of bugspam), someone suggested >>> blocking kernels which are incompatible with the currently-installed >>> nvidia-drivers. I'm glad that idea was dismissed. >>> >>>> elog messages >>> >>> Those elog messages are presented after compiling a new kernel and then >>> trying and failing to compile nvidia-drivers. So now I grep the >>> nvidia-drivers ebuilds for the messages before I compile a new kernel. >>> >>> A wiki page with info about which nvidia-drivers will build against >>> which kernels would be a nice thing to have. >> >> Your reply demonstrates nicely the true nature of the problem: >> >> With nvidia-drivers, sometimes things break and there's nothing sane >> that portage and the devs can do to help you. You can't check the >> configured kernels as they may not be running. You can't check the >> installed sources as they may not be in use. You can't even try identify >> the sources symlinked by /usr/src/linux as they may have been patched, >> tweaked or modified and nvidia-drivers may well build whereas against >> stock sources they don't. >> >> The entire problem is completely due to how nVidia chose to do things, >> it's their business decision. Now, if they were to get their shim code >> into mainline, most of this nonsense would not happen anymore. >> >> The only thing left for Portage and the devs to do is to provide the >> ebuild and ask you to run it. If it doesn't compile, then don't run that >> kernel. >> >> I doubt your wiki page idea will work, it will be just accurate enough >> to look like it might work and just inaccurate enough to be useless. >> Which brings you back to the previous paragraph - try emerge >> nvidia-drivers and if it fails then don't use that kernel. > > I've been always running ATI Radeon cards, by accident rather than design. I > was thinking of moving to NVidia on a new box to be built soon, because of the > many accolades that I have read on the Internet, but reports of problems like > this make me pause for thought. Sure it's not major borkage, but it is an > inconvenience. How do NVidia users manage such problems? Trial and error? > Sort of. When I hit a nice spot with a kernel/nvidia-driver combination, then I do not update both for quite a while.