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 5E9E51381F3 for ; Mon, 26 Aug 2013 01:53:35 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E993EE0B38; Mon, 26 Aug 2013 01:53:30 +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 C984CE0B2D for ; Mon, 26 Aug 2013 01:53:29 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 060FE33EB42 for ; Mon, 26 Aug 2013 01:53:29 +0000 (UTC) X-Virus-Scanned: by amavisd-new using ClamAV at gentoo.org X-Spam-Flag: NO X-Spam-Score: -2.316 X-Spam-Level: X-Spam-Status: No, score=-2.316 tagged_above=-999 required=5.5 tests=[AWL=0.484, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-2.799, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable Received: from smtp.gentoo.org ([IPv6:::ffff:127.0.0.1]) by localhost (smtp.gentoo.org [IPv6:::ffff:127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wcndMhP7dK7y for ; Mon, 26 Aug 2013 01:53:03 +0000 (UTC) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id 0F05933EB3E for ; Mon, 26 Aug 2013 01:53:01 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1VDlzG-0005Sv-N8 for gentoo-user@gentoo.org; Mon, 26 Aug 2013 03:52:58 +0200 Received: from wsip-174-76-82-7.no.no.cox.net ([174.76.82.7]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 26 Aug 2013 03:52:58 +0200 Received: from boxcars by wsip-174-76-82-7.no.no.cox.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 26 Aug 2013 03:52:58 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: =?UTF-8?B?wrtRwqs=?= Subject: [gentoo-user] Re: The NVIDIA/Kernel fiasco -- is it safe to sync yet? Date: Sun, 25 Aug 2013 20:52:46 -0500 Organization: none Message-ID: <20130825205246.3ece7b78@fuchsia.remarqs.net> References: <20130823180959.GA13353@artifex> <1746861.kq9W4Fkxay@apollo> <20130823231239.4d4df2db@fuchsia.remarqs.net> <52186597.6030407@gmail.com> <20130824194527.122b5436@fuchsia.remarqs.net> <521A2E41.2020001@gmail.com> 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 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: wsip-174-76-82-7.no.no.cox.net X-Newsreader: Claws Mail 3.9.0 (GTK+ 2.24.17; x86_64-pc-linux-gnu) X-Archives-Salt: e276d3c0-079a-4887-842c-23dfdba2e792 X-Archives-Hash: 3bd69da640354bfee0efe4fa9a4ccb75 On Sun, 25 Aug 2013 18:18:09 +0200 Alan McKinnon wrote: > On 25/08/2013 02:45, =C2=BBQ=C2=AB wrote: > > On Sat, 24 Aug 2013 09:49:43 +0200 > > Alan McKinnon wrote: > >=20 > >> On 24/08/2013 06:26, Chris Stankevitz wrote: > >>> On Fri, Aug 23, 2013 at 9:12 PM, =C2=BBQ=C2=AB wrot= e: =20 > >>>> 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. =20 > >>> > >>> 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. =20 > >> > >> Those tools already exist. > >> > >> Blockers, which do not really apply here; > >=20 > > 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. > >=20 > >> elog messages > >=20 > > 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. > >=20 > > A wiki page with info about which nvidia-drivers will build against > > which kernels would be a nice thing to have. >=20 > Your reply demonstrates nicely the true nature of the problem: >=20 > 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. >=20 > 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. >=20 > 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. >=20 > 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 was unclear to the point of being misleading. I'm sorry. The wiki idea is only for a page which tells which kernel/nvidia-drivers combinations the Gentoo nvidia-drivers maintainers support. And by "support", I mean they'll look into bugs and fix build problems if they're able to. This is exactly the info I'm grepping out of ewarn messages in their ebuilds now.