public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Scott Petler <scottp@sonic.net>
To: "Doug Whitesell (LKML)" <dcw-kernel@screamingdolphin.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: kernel panic
Date: Sun, 14 Oct 2007 14:00:12 -0700	[thread overview]
Message-ID: <4712835C.5050400@sonic.net> (raw)
In-Reply-To: <1B7E8ED9-7DA9-41CA-BDF9-219E71AAA905@screamingdolphin.net>

Doug,

I thought that might do it, it does seem to work.  I edited the driver 
line in my xorg.conf
from nvidia to nv and then,
<alt><ctrl> F1
login as root
/etc/init.d/gdm stop
/etc/init.d/gdm start

It came back up with the same flashing crap on the second monitor, so I 
did it again with
the 2nd monitor turned off altogether, and I'll see how long it will run 
on the single monitor
without the nvidia driver without crashing (maybe forever...).

Thanks,
Scott

Doug Whitesell (LKML) wrote:
> On Oct 14, 2007, at 1:44 PM, Scott Petler wrote:
>
>> Trond,
>>
>> I'm not exactly sure how to go back to not using the nvidia driver 
>> and select the xorg one.  I do know that I wasn't able to use both 
>> monitors with the xorg driver, but I'm willing to try that to isolate 
>> the problem.
>
> If memory serves, you change your xorg.conf's "Device" section's 
> "Driver" entry to read:
> "nv"
> instead of
> "nvidia",
>
> although I would consult the xorg documentation/your distribution's 
> documentation (and back up your working xorg.conf) for specific 
> details. (Your boot sequence may also automatically load the nvidia 
> module, again, consult your distribution's documentation for details.)
>
> Cheers/hope this helps,
> dcw
>
>

  reply	other threads:[~2007-10-14 21:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-13 22:48 PROBLEM: kernel panic Scott Petler
2007-10-14 20:24 ` Trond Myklebust
2007-10-14 20:44   ` Scott Petler
2007-10-14 20:51     ` Doug Whitesell (LKML)
2007-10-14 21:00       ` Scott Petler [this message]
2007-10-14 21:32         ` Trond Myklebust
2007-10-14 21:36           ` Scott Petler
  -- strict thread matches above, loose matches on Subject: below --
2008-07-02  6:49 PROBLEM: Kernel panic Svein Larsen
2008-07-02  8:26 ` Frederik Deweerdt

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=4712835C.5050400@sonic.net \
    --to=scottp@sonic.net \
    --cc=dcw-kernel@screamingdolphin.net \
    --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