From: Jesper Juhl <jesper.juhl@gmail.com>
To: hanasaki <hanasaki@hanaden.com>
Cc: LIST - Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: kernel 2.6.13 hangs / freezes with nvidia kernel module on switch to virtual console (also 2.6.12)
Date: Mon, 5 Sep 2005 18:13:15 +0200 [thread overview]
Message-ID: <9a874849050905091364b6a103@mail.gmail.com> (raw)
In-Reply-To: <431C6C0A.4080302@hanaden.com>
On 9/5/05, hanasaki <hanasaki@hanaden.com> wrote:
> kernel 2.6.13 hangs / freezes with nvidia
> kernel module on switch to virtual console
>
> Running Debian testing and stable and built the kernel with the attached
> config. Then the NVidia installer was run. Everything boots and runs
> fine. X and Gnome come up and run. Switching to a Virtual Console
> locks up the system and shows some crazy colors.
>
> The system ran fine with the same configs until ~kernel 2.6.12.x and has
> exhibited this failing behavior since then with multiple kernels.
>
> The graphics card is a shown below and has two outputs both in use for
> two monitors. Thus the actual driver from NV is needed. I do not
> believe the Xfree nv driver supports dual head.
>
> ======================
> NVidia version
> NVIDIA-Linux-x86-1.0-7676-pkg1.run <= from nvidia.com
>
Reproduce the problem without a binary only kernel module. Or in this
case, complain to nvidia.
It's impossible for kernel developers to debug a problem involving a
closed source module. The authors of that module will have to do the
fixing.
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
prev parent reply other threads:[~2005-09-05 16:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-05 16:02 hanasaki
2005-09-05 16:13 ` Jesper Juhl [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=9a874849050905091364b6a103@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=hanasaki@hanaden.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome