public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Frank Peters <frank.peters@comcast.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers
Date: Thu, 22 Mar 2012 14:41:31 -0400	[thread overview]
Message-ID: <20120322144131.5f02745a.frank.peters@comcast.net> (raw)
In-Reply-To: <CAK2H+edPXevXQpR09mg4Zv2-3iQd6Hpw1o4VLxJxnxTkFPzCpw@mail.gmail.com>

On Thu, 22 Mar 2012 09:03:59 -0700
Mark Knecht <markknecht@gmail.com> wrote:

>
>    I hadn't played with this since you first posted but I've been
> waiting for a new nvidia-driver to solve the problem and not seen it.
> As my laptop uses vanilla-sources I was stuck but also not really
> wanting to do the patch you did.
> 

It's not much of a patch.  It involves only copying a few files
from one directory to another.  Apparently, these files are
auto-generated by the new kernel and placed in the wrong location
(wrong for Nvidia).

>
> Anyway, for kicks this morning I tried gentoo-sources-3.3.0 and
> found that nvidia-drivers builds & runs fine with that kernel.
> 

Out of habit, I still use the kernel sources from kernel.org.
I have an automated build/install for this from a long time
back.  But maybe I'll look into the gentoo-sources one day.
Thanks for the tip.

However, checking the Changelog for gentoo-sources I do not
see any indication of a possible patch to fix 3.3.0.  Maybe
I'm just not looking in the right place.

Frank Peters




  reply	other threads:[~2012-03-22 21:03 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-19 16:12 [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers Frank Peters
2012-03-19 16:35 ` Mark Knecht
2012-03-19 19:05   ` Frank Peters
2012-03-19 19:16     ` Mark Knecht
2012-03-19 19:30   ` Frank Peters
2012-03-19 20:08     ` Mark Knecht
2012-03-19 20:25       ` Paul Hartman
2012-03-19 19:14 ` Cheng Renquan
2012-03-19 19:17   ` Mark Knecht
2012-03-19 21:28     ` Barry Schwartz
2012-03-19 21:40       ` Mark Knecht
2012-03-20  0:34         ` Barry Schwartz
2012-03-20  4:03         ` Frank Peters
2012-03-20  6:20           ` Barry Schwartz
2012-03-20 18:31             ` [gentoo-amd64] " Duncan
2012-03-20 18:27           ` Duncan
2012-03-22 16:03 ` [gentoo-amd64] " Mark Knecht
2012-03-22 18:41   ` Frank Peters [this message]
2012-03-22 18:58     ` Mark Knecht
2012-03-22 21:18       ` Barry Schwartz
2012-03-22 21:21         ` Barry Schwartz
2012-03-22 21:32     ` Outside of portage (was Re: [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers) Barry Schwartz
2012-03-22 23:04       ` Paul Hartman
2012-03-22 23:28         ` Barry Schwartz
2012-03-22 23:33           ` Harry Holt
2012-03-23  8:42             ` Benny Pedersen
2012-03-23 13:50               ` Harry Holt
2012-03-23  0:14       ` Gary E. Miller
2012-03-23  1:30       ` Mark Knecht
2012-03-23  1:56         ` Barry Schwartz
2012-03-23  4:05       ` [gentoo-amd64] Re: Outside of portage (was " Duncan
2012-03-23 12:41       ` Outside of portage (was Re: [gentoo-amd64] " Frank Peters
2012-03-23 15:49         ` Barry Schwartz
2012-03-23 18:09           ` Dale
2012-03-23 18:28 ` [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers Mark Knecht
2012-03-23 19:11   ` Mark Knecht
2012-03-24  0:20   ` Frank Peters

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=20120322144131.5f02745a.frank.peters@comcast.net \
    --to=frank.peters@comcast.net \
    --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