From: Mark Knecht <markknecht@gmail.com>
To: Gentoo AMD64 <gentoo-amd64@lists.gentoo.org>
Subject: Re: [gentoo-amd64] Kernel-3.10 Nvidia Emerge Failure And Other Stuff
Date: Mon, 1 Jul 2013 13:30:47 -0700 [thread overview]
Message-ID: <CAK2H+ef+p4z-K3j84BzR5d9Hb8p+y7d06rf8NGa+1td=wYpvTg@mail.gmail.com> (raw)
In-Reply-To: <CAK2H+edmmNHQD7gydycibKr=DFxbjF8w_0J0BQO3Ap7HWTV0mA@mail.gmail.com>
On Mon, Jul 1, 2013 at 12:51 PM, Mark Knecht <markknecht@gmail.com> wrote:
> On Mon, Jul 1, 2013 at 12:35 PM, Frank Peters <frank.peters@comcast.net> wrote:
> <SNIP>
>> However, the main problem for me with kernel-3.20 is that the nvidia-drivers
>> will fail to emerge. Here is the error:
>>
>> nvidia-drivers-319.32/work/kernel/nv-i2c.c: In function 'nv_i2c_del_adapter':
>> nv-i2c.c:327:14: error: void value not ignored as it ought to be
>>
>> When I encountered this failure I expected that a huge outcry of bug reports
>> would ensue, but so far things have been rather quiet. There are only a few
>> postings of this problem with 3.10-rc1 and not much else.
>>
>> I should perhaps just patiently wait for the eventual rapid fix, because this
>> error is a real show stopper, but I will make an inquiry nonetheless.
>> Has anyone on the list encountered this error with nvidia and kernel-3.10?
>>
>> I hope it is not, again, some strange affliction peculiar to my machine.
>>
>> Frank Peters
>
>
> Hi Frank,
> I don't think the Gentoo devs pay much attention to that sort of
> failure. I don't report them anymore.
>
> My personal experience with major kernel revision jumps like this
> is that it's best to give NVidia a few days and to watch their web
> site for a new version. They typically update very quickly. (1-2 days)
>
> HTH,
> Mark
Frank,
On the NVidia site they show a new beta driver released today, July
1st, 2013. The version number is 325.08. I just did a sync and that
revision does not appear to be in portage yet, at least on the server
I'm syncing to.
I suspect that's the driver you're looking for but that is just a guess.
HTH,
Mark
next prev parent reply other threads:[~2013-07-01 20:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 19:35 [gentoo-amd64] Kernel-3.10 Nvidia Emerge Failure And Other Stuff Frank Peters
2013-07-01 19:51 ` Mark Knecht
2013-07-01 20:04 ` Dale
2013-07-02 0:57 ` B Vance
2013-07-02 0:38 ` Frank Peters
2013-07-01 20:30 ` Mark Knecht [this message]
2013-07-01 20:51 ` Rich Freeman
2013-07-04 23:57 ` Mark Knecht
2013-07-05 1:08 ` Frank Peters
2013-07-01 21:06 ` Frank Peters
2013-07-02 11:29 ` [gentoo-amd64] " Duncan
2013-07-02 16:54 ` Frank Peters
2013-07-03 2:10 ` Duncan
2013-07-04 23:48 ` Sven Köhler
2013-07-05 1:28 ` Frank Peters
2013-07-05 16:41 ` Sven Köhler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAK2H+ef+p4z-K3j84BzR5d9Hb8p+y7d06rf8NGa+1td=wYpvTg@mail.gmail.com' \
--to=markknecht@gmail.com \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox