All of lore.kernel.org
 help / color / mirror / Atom feed
From: andrzej-kardas@o2.pl (Andrzej Kardas)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Customized kernel and nVidia binary drivers
Date: Fri, 14 Oct 2011 18:43:52 +0200	[thread overview]
Message-ID: <4E9866C8.1080302@o2.pl> (raw)
In-Reply-To: <CACSM0COxJTZ7PncswV_zgBL5D4U2V8UFXFVF9j63uAnPYNTBuQ@mail.gmail.com>



On 14.10.2011 15:26, Cihangir Akt?rk wrote:
> Hi everybody,
>
> I am building custom kernels using "make-kpkg" command - the debian way,
> everything works great even my nVidia propriatery driver. And this nvidia
> module confuses me so much.
>
> When I build my kernel with standard "make", and install it as it is expected
> there is no nvidia module in my /usr/lib/kernel-ver directory and not
> surprisingly
> simply copying this driver from older kernel to a new one doesn't work as well.
It's because version of the module must match kernel version. Nvidia 
ships binary module (already compiled) but also sources some kind of 
"kernel interface to binary module" which must be recompiled every time 
you build new kernel.

> I wonder how can this nVidia binary driver still work if I compile my kernel
> with "make-kpkg"?
> What this utility does to make it happen
That should be helpful for you:

http://wiki.debian.org/NvidiaGraphicsDrivers

--
Regards
Andrzej Kardas'
http://linux.mynotes.pl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20111014/5455724f/attachment.html 

      reply	other threads:[~2011-10-14 16:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-14 13:26 Customized kernel and nVidia binary drivers Cihangir Aktürk
2011-10-14 16:43 ` Andrzej Kardas [this message]

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=4E9866C8.1080302@o2.pl \
    --to=andrzej-kardas@o2.pl \
    --cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.