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 000C91381F3 for ; Sun, 25 Aug 2013 16:38:42 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 209D8E0D46; Sun, 25 Aug 2013 16:38:00 +0000 (UTC) Received: from mail-we0-f170.google.com (mail-we0-f170.google.com [74.125.82.170]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id A78FCE0D3D for ; Sun, 25 Aug 2013 16:37:58 +0000 (UTC) Received: by mail-we0-f170.google.com with SMTP id w62so2044861wes.15 for ; Sun, 25 Aug 2013 09:37:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:reply-to:to:subject:date:user-agent:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; bh=h5QYgqtriRHV9ct1Lk7vegKYabkGObtFXsx99HIRyJQ=; b=gaVVkPW9EJkhJiHPcQIc8HhFsX2ixYrYC2P2ldp86gsRaGWJqYEUaUzf70r5tgi+ue mKBYcYkABaunrzeDb1xPzA570HKD1/ZVA/4+GxN4rbG8GE4K357oC6QE43J6KCP+KaxE kt2T2DsMD+cIeF91hhNRvlo1BdwncItfYXMdeWq/OpfND5fIh9Aft+XW4sFkJbZAO/5w 838H+2eau5gCPq/n8KeMM699yC2h82EeiLsJwjZMnfyEcXtO1yZYUnLdC4qZtPV0TGpm ZL9FmJn74dXSGn90lDc/f3j99aPzbwf8lYyd4/6NWAgsQd6qoxnmsbUn6+sWVeSgBKV+ WUow== X-Received: by 10.180.93.136 with SMTP id cu8mr4801354wib.1.1377448677320; Sun, 25 Aug 2013 09:37:57 -0700 (PDT) Received: from dell_xps.localnet (230.3.169.217.in-addr.arpa. [217.169.3.230]) by mx.google.com with ESMTPSA id iz19sm12017959wic.9.1969.12.31.16.00.00 (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 25 Aug 2013 09:37:56 -0700 (PDT) From: Mick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: The NVIDIA/Kernel fiasco -- is it safe to sync yet? Date: Sun, 25 Aug 2013 17:34:21 +0100 User-Agent: KMail/1.13.7 (Linux/3.10.7-gentoo; KDE/4.10.5; x86_64; ; ) References: <20130824194527.122b5436@fuchsia.remarqs.net> <521A2E41.2020001@gmail.com> In-Reply-To: <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: multipart/signed; boundary="nextPart3582314.Z3Um1gnIbX"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201308251734.25129.michaelkintzios@gmail.com> X-Archives-Salt: 74ae0600-953c-4aa9-b9bd-7b716ab2cecd X-Archives-Hash: e38a1823ba4003ce37d581ec6cccdfad --nextPart3582314.Z3Um1gnIbX Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Sunday 25 Aug 2013 17:18:09 Alan McKinnon wrote: > On 25/08/2013 02:45, =C2=BBQ=C2=AB wrote: > > On Sat, 24 Aug 2013 09:49:43 +0200 > >=20 > > Alan McKinnon wrote: > >> On 24/08/2013 06:26, Chris Stankevitz wrote: > >>> On Fri, Aug 23, 2013 at 9:12 PM, =C2=BBQ=C2=AB wrot= e: > >>>> 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. > >>=20 > >> 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've been always running ATI Radeon cards, by accident rather than design. = I=20 was thinking of moving to NVidia on a new box to be built soon, because of = the=20 many accolades that I have read on the Internet, but reports of problems li= ke=20 this make me pause for thought. Sure it's not major borkage, but it is an= =20 inconvenience. How do NVidia users manage such problems? Trial and error? =2D-=20 Regards, Mick --nextPart3582314.Z3Um1gnIbX Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (GNU/Linux) iQEcBAABAgAGBQJSGjIRAAoJELAdA+zwE4YenZkH/3KvJnwj5QhOkQWklgLtEnco OIB8cS30/Wd9PyOtkEYImdL3QSTvUn/VHVxrK2Ae0X2LIMMmilW4YBmFT0xTIRY4 Y1jAH+aPG60EHMm0N1ykcrnw8ujur/1jlFzsk7uBbxXha6eVRLewSpqjBzJuG6dk DHRHiQ73eNL8e8IgVwHMIm1+6qyiCTLVOWZttRaW239efbDooj84FHsRfoZiQgPT dBVgNiwjm3nJUf00djWlibugE6heETcGjPVq9+EQ2GR2aNfFCCwTesrpdBOwpiFr VRoiBd7xWFhL9DUe2IUFxsEfwBuf/CIzAFuXB6xUNsBEdO8bM7diKOM1WE+BXRM= =svQV -----END PGP SIGNATURE----- --nextPart3582314.Z3Um1gnIbX--