From: Joseph <syscon780@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Nvidia driver - blank screen not even console display
Date: Fri, 22 Feb 2013 20:03:48 -0700 [thread overview]
Message-ID: <20130223030348.GB5625@syscon7.inet> (raw)
In-Reply-To: <51281AB0.7000107@gmail.com>
On 02/22/13 17:26, walt wrote:
>On 02/22/2013 12:24 AM, Joseph wrote:
>> On 02/22/13 09:10, Alexandre Domi wrote:
>>> Seems you're getting a nvidia segfault... Did you try revdep-rebuild,
>>> or updating your system?
>>>
>>> Regards
>>
>> Yes, I just updated the system.
>> When I try to compile nvidia-drivers I get this message:
>> ...
>> test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \
>> echo; \
>> echo " ERROR: Kernel configuration is invalid."; \
>> echo " include/generated/autoconf.h or include/config/auto.conf are missing.";\
>> echo " Run 'make oldconfig && make prepare' on kernel src to fix it."; \
>> echo;
>
>Joseph, I feel I should apologize for the numbskull devs at nvidia for writing such
>ridiculous code -- but I'm not responsible for them, honest ;)
>
>The lines of output above are completely normal. They don't describe the *real* error
>that's causing your problem.
>
>You see the "echo" in the message you posted? That means the nvidia devs chose to print
>the lines of code in their installer shellscript as it executes, one line at a time.
>
>That echo "ERROR...etc" is what the nvidia installer would have printed *if* you actually
>experienced that particular kernel config problem -- but you didn't. The real error
>message was printed way below what you posted above, and I suspect it was caused by
>a recent change in the linux kernel headers, but that's just a guess.
>
>You need to examine the remainder of the output from the nvidia installer to find the
>actual error, and post it here so we can help you figure it out.
I think you are correct. It took me all night :-/ to come to this conclusion.
Yes, the kernle-3.5.7 I think is not compatible with the nvidia driver (at least in my case/my video card).
I don't think I was the only one who experience this problem. It just make me wonder why did they make it stable.
--
Joseph
next prev parent reply other threads:[~2013-02-23 3:04 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 6:14 [gentoo-user] Nvidia driver - blank screen not even console display Joseph
2013-02-22 7:22 ` Canek Peláez Valdés
2013-02-22 7:34 ` Joseph
2013-02-22 8:10 ` Alexandre Domi
2013-02-22 8:24 ` Joseph
2013-02-22 8:36 ` Dale
2013-02-22 8:50 ` Joseph
2013-02-22 8:59 ` Dale
2013-02-22 9:29 ` Joseph
2013-02-22 8:51 ` Joseph
2013-02-22 8:52 ` Alexandre Domi
2013-02-22 9:07 ` Joseph
2013-02-22 9:14 ` Alexandre Domi
2013-02-22 9:21 ` Joseph
2013-02-22 9:33 ` Dale
2013-02-22 9:41 ` Joseph
2013-02-22 9:35 ` Joseph
2013-02-22 9:39 ` Joseph
2013-02-22 9:49 ` Raffaele BELARDI
2013-02-22 10:15 ` Joseph
2013-02-22 10:28 ` Raffaele BELARDI
2013-02-22 12:17 ` Dale
2013-02-22 12:42 ` Joseph
2013-02-22 12:53 ` Dale
2013-02-22 20:26 ` Joseph
2013-02-22 23:41 ` Dale
2013-02-22 10:26 ` Joseph
2013-02-24 3:39 ` Joseph
2013-02-23 1:26 ` [gentoo-user] " walt
2013-02-23 3:03 ` Joseph [this message]
2013-02-23 5:24 ` Nikos Chantziaras
2013-02-23 7:32 ` Joseph
2013-02-23 8:55 ` Neil Bothwick
2013-02-23 22:53 ` Joseph
2013-02-24 9:08 ` Nikos Chantziaras
2013-02-23 22:39 ` Joseph
2013-02-23 22:49 ` Randolph Maaßen
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=20130223030348.GB5625@syscon7.inet \
--to=syscon780@gmail.com \
--cc=gentoo-user@lists.gentoo.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