LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Igor M Podlesny <for.poige+linux@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: NVIDIA's Linux x86 Display Driver fresh driver isn't compatible anymore
Date: Mon, 4 Feb 2008 22:34:30 -0800	[thread overview]
Message-ID: <20080204223430.415161e9@laptopd505.fenrus.org> (raw)
In-Reply-To: <47A80218.3040304@gmail.com>

On Tue, 05 Feb 2008 13:28:40 +0700
Igor M Podlesny <for.poige+linux@gmail.com> wrote:

> On 2008-02-05 12:32, Igor M Podlesny wrote:
> > On 2008-02-04 20:27, Andrew Morton wrote:
> >> On Mon, 04 Feb 2008 20:16:48 +0700 Igor M Podlesny
> >> <for.poige+linux@gmail.com> wrote:
> > [...]
> >>>    Now I can say that both 2.6.24-mm1 and 2.6.24-git11 do NOT
> >>> "see" any of mine LVM-2 disks. pvscan, for e.g., finds nothing at
> >>> all.
> >> 
> >> You may find that you need to update your lvm userspace tools.
> > 
> > 	You're right; I've updated my initrd with fresh lvm
> > userspace-counterpart and now the problem has been fixed. Sorry for
> > groundless alert.
> > 
> > 	Thanks!
> 
> 	But as russian proverb says, trouble never comes alone. :-)
> NVIDIA's fresh driver isn't compatible anymore:
> 
> 	1) To have compiled it I had to replace global_flush_tlb()
> call with __flush_tlb_all() and still guessing was it(?) a correct
> replacment at all :-)

it is not; 
> 
> 	2) When loading it emits such messages:
> 
> 		nvidia: Unknown symbol change_page_attr
> 		nvidia: Unknown symbol init_mm
> 
> 	Can it be quick and easy solved?

best asked at one of the nvidia forums, not on lkml...
they need to adjust a few API calls, it's not hard work but they need
to do that (their driver isn't open source)


-- 
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

  reply	other threads:[~2008-02-05  6:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <43d009740802022335y21c3f93ep4e444bef71338045@mail.gmail.com>
     [not found] ` <20080202235103.20dd9768.akpm@linux-foundation.org>
2008-02-04 13:16   ` Both 2.6.24-mm1 and 2.6.24-git11 do NOT "see" any of mine LVM-2 disks Igor M Podlesny
2008-02-04 13:27     ` Andrew Morton
2008-02-05  5:32       ` > You may find that you need to update your lvm userspace tools Igor M Podlesny
2008-02-05  5:53         ` Andrew Morton
2008-02-05 12:11           ` Alasdair G Kergon
2008-02-05  6:28         ` NVIDIA's Linux x86 Display Driver fresh driver isn't compatible anymore Igor M Podlesny
2008-02-05  6:34           ` Arjan van de Ven [this message]
2008-02-05  6:44             ` > best asked at one of the nvidia forums, not on lkml Igor M Podlesny
2008-02-05  6:53               ` Zachary Amsden
2008-02-05  6:56                 ` > global_flush_tlb() would be the correct one Igor M Podlesny
2008-02-05  7:22                 ` > best asked at one of the nvidia forums, not on lkml Arjan van de Ven

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=20080204223430.415161e9@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=for.poige+linux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: NVIDIA'\''s Linux x86 Display Driver fresh driver isn'\''t compatible anymore' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).