From: Rich Freeman <rich0@gentoo.org>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Kernel-3.10 Nvidia Emerge Failure And Other Stuff
Date: Mon, 1 Jul 2013 16:51:15 -0400 [thread overview]
Message-ID: <CAGfcS_m3pord5H5+s6kOuYBhfM5YNCKzUojS8e9595Y07FKVfw@mail.gmail.com> (raw)
In-Reply-To: <CAK2H+ef+p4z-K3j84BzR5d9Hb8p+y7d06rf8NGa+1td=wYpvTg@mail.gmail.com>
On Mon, Jul 1, 2013 at 4:30 PM, Mark Knecht <markknecht@gmail.com> wrote:
> 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.
>
Nvidia not working with the latest kernel is a known issue. I have no
idea whether that new release fixes it but it is a good guess.
In general with these sorts of issues I would suggest just giving it a
day or two before logging a bug to give everybody a chance to catch
up. Apparently 3.10 changed significantly during the rcs and Nvidia
got tired of regular updates so they decided to just wait for final
release.
Rich
next prev parent reply other threads:[~2013-07-01 20:51 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
2013-07-01 20:51 ` Rich Freeman [this message]
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=CAGfcS_m3pord5H5+s6kOuYBhfM5YNCKzUojS8e9595Y07FKVfw@mail.gmail.com \
--to=rich0@gentoo.org \
--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