public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alejandro Riveira Fernández" <ariveira@gmail.com>
To: "Michael B. Trausch" <mike@trausch.us>
Cc: Alistair John Strachan <alistair@devzero.co.uk>,
	linux-kernel@vger.kernel.org, pazke@ports.donpac.ru
Subject: Re: Linux 2.6.28-rc7
Date: Tue, 2 Dec 2008 19:06:17 +0100	[thread overview]
Message-ID: <20081202190617.61b61592@varda> (raw)
In-Reply-To: <20081202121111.245d2ecc@zest.spicerack.trausch.us>

El Tue, 2 Dec 2008 12:11:11 -0500
"Michael B. Trausch" <mike@trausch.us> escribió:

[...]
> 
> Alejandro, can you switch back to VTs again after rebuilding your
> NVIDIA module?
 
  I can switch to VT's and the bug still manifest 2.6.28-rc7
  

>  Also, you seem to have mentioned that you're not using
> Ubuntu's packaged NVIDIA driver... this may mean that you've
> overwritten and/or moved other files that Ubuntu uses, since the NVIDIA
> driver installer does this automatically.

  I'm using the nvidia installer for the 180.06 driver yes

> Can you try using a stock
> system, updated kernel, and let DKMS build the NVIDIA module?  You'll
> need to make some alterations, but I can help with those.

 Would the nvidia.com uninstaller leave things as in a stock install?
 Where can i find help about DKMS? also does it work if you use the
 "vanilla way" of installing kernels? i do:
  make ; make install ; make modules_install ; and mkinitramfs to install
  kernels i test
 

> 
> 	HTH,
> 	Mike
> 

  reply	other threads:[~2008-12-02 18:06 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.IDjfwzrT2B02+NHfmYwtICnzOOA@ifi.uio.no>
     [not found] ` <fa.J8MFTCUT8El3sK8BuYDBvaMRaB8@ifi.uio.no>
     [not found]   ` <fa.q/4H3AtoJGSJ+i8tlXR4X35LFFU@ifi.uio.no>
     [not found]     ` <fa.98CeSgxJ/GGaLLyZ97s1oHgh7hE@ifi.uio.no>
2008-12-02 17:11       ` Linux 2.6.28-rc7 Michael B. Trausch
2008-12-02 18:06         ` Alejandro Riveira Fernández [this message]
2008-12-02 18:56           ` Michael B. Trausch
2008-12-02  4:11 Linus Torvalds
2008-12-02 12:14 ` Alejandro Riveira Fernández
2008-12-02 13:11   ` pazke
2008-12-02 14:48     ` Alejandro Riveira Fernández
2008-12-02 15:20       ` Alistair John Strachan
2008-12-02 15:50         ` Alejandro Riveira Fernández
2008-12-02 16:14           ` Alistair John Strachan
2008-12-02 15:54         ` Alejandro Riveira Fernández
2008-12-02 15:50   ` Linus Torvalds
2008-12-02 15:56     ` Alejandro Riveira Fernández
2008-12-02 16:13       ` Linus Torvalds
2008-12-02 18:49         ` Alejandro Riveira Fernández
2008-12-02 19:22           ` Alejandro Riveira Fernández
2008-12-02 19:23           ` Linus Torvalds
2008-12-02 19:45             ` Alejandro Riveira Fernández
2008-12-02 20:40               ` Linus Torvalds
2008-12-02 20:29             ` Al Viro

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=20081202190617.61b61592@varda \
    --to=ariveira@gmail.com \
    --cc=alistair@devzero.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike@trausch.us \
    --cc=pazke@ports.donpac.ru \
    /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