dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 58671] Nvidia drivers fail compile
Date: Wed, 29 May 2013 21:00:16 +0000 (UTC)	[thread overview]
Message-ID: <20130529210016.4ED9911FADB@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-58671-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=58671





--- Comment #2 from Acidphase <Acidphase@gmail.com>  2013-05-29 21:00:15 ---
Created an attachment (id=102881)
 --> (https://bugzilla.kernel.org/attachment.cgi?id=102881)
NVIDIA-Linux-x86_64-319.17-no-compat32.patch

Found working patch from the nvidia developers forum.

https://devtalk.nvidia.com/default/topic/543728/linux/building-nvidia-driver-on-kernel-3-9-0/post/3814531/#3814531

How to apply patch in Gentoo: 

Just let epatch_user do the work. All you need to do is create a nvidia-drivers
dir in /etc/portage/patches/x11-drivers/

So download patch cp ~/Downloads/NVIDIA-Linux-x86_64-319.17-no-compat32.patch
/etc/portage/patches/x11-drivers/nvidia-drivers

Then just emerge nvidia-drivers or module-rebuild rebuild

This patch works with 3.10-rc3 and nvidia drivers 319.23

Good luck,

Ron

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  parent reply	other threads:[~2013-05-29 21:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-22 21:02 [Bug 58671] New: Nvidia drivers fail compile bugzilla-daemon
2013-05-22 21:05 ` [Bug 58671] " bugzilla-daemon
2013-05-29 21:00 ` bugzilla-daemon [this message]
2013-11-12 15:03 ` bugzilla-daemon
2013-11-12 15:03 ` bugzilla-daemon

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=20130529210016.4ED9911FADB@bugzilla.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.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