[gentoo-user] Nvidia driver - blank screen not even console display

[Joseph]

I just upgraded system including kernel to 3.5.7 because of udev-197
Now I have a blank screen, not even console login (I can only access is via ssh)
Here is Xorg.0.log

[ 55.449] (II) NVIDIA(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 55.449] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[ 55.449] (==) NVIDIA(0): RGB weight 888
[ 55.449] (==) NVIDIA(0): Default visual is TrueColor
[ 55.449] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 55.449] (**) NVIDIA(0): Enabling 2D acceleration
[ 55.449] (EE) NVIDIA(0): Failed to initialize the GLX module; please check in your X
[ 55.449] (EE) NVIDIA(0): log file that the GLX module has been loaded in your X
[ 55.449] (EE) NVIDIA(0): server, and that the module is the NVIDIA GLX module. If
[ 55.449] (EE) NVIDIA(0): you continue to encounter problems, Please try
[ 55.449] (EE) NVIDIA(0): reinstalling the NVIDIA driver.
[ 67.826] (II) NVIDIA(GPU-0): Display (BenQ V2400W (DFP-1)) does not support NVIDIA 3D
[ 67.826] (II) NVIDIA(GPU-0): Vision stereo.
[ 67.827] (II) NVIDIA(0): NVIDIA GPU GeForce GTS 450 (GF116) at PCI:1:0:0 (GPU-0)
[ 67.827] (--) NVIDIA(0): Memory: 1048576 kBytes
[ 67.827] (--) NVIDIA(0): VideoBIOS: 70.26.29.00.00
[ 67.827] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 67.827] (--) NVIDIA(0): Interlaced video modes are supported on this GPU
[ 70.833] (--) NVIDIA(0): Valid display device(s) on GeForce GTS 450 at PCI:1:0:0
[ 70.833] (--) NVIDIA(0): CRT-0
[ 70.833] (--) NVIDIA(0): CRT-1
[ 70.833] (--) NVIDIA(0): DFP-0
[ 70.833] (--) NVIDIA(0): BenQ V2400W (DFP-1) (connected)
[ 70.833] (--) NVIDIA(0): CRT-0: 400.0 MHz maximum pixel clock
[ 70.833] (--) NVIDIA(0): CRT-1: 400.0 MHz maximum pixel clock
[ 70.833] (--) NVIDIA(0): DFP-0: 330.0 MHz maximum pixel clock
[ 70.833] (--) NVIDIA(0): DFP-0: Internal Single Link TMDS
[ 70.833] (--) NVIDIA(0): BenQ V2400W (DFP-1): 165.0 MHz maximum pixel clock
[ 70.833] (--) NVIDIA(0): BenQ V2400W (DFP-1): Internal Single Link TMDS
[ 70.833] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 70.833] (**) NVIDIA(0): device BenQ V2400W (DFP-1) (Using EDID frequencies has
[ 70.833] (**) NVIDIA(0): been enabled on all display devices.)
[ 70.834] (WW) NVIDIA(GPU-0): The EDID for BenQ V2400W (DFP-1) contradicts itself: mode
[ 70.834] (WW) NVIDIA(GPU-0): "720x480" is specified in the EDID; however, the EDID's
[ 70.834] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-94.000 kHz) would exclude
[ 70.834] (WW) NVIDIA(GPU-0): this mode's HorizSync (15.7 kHz); ignoring HorizSync check
[ 70.834] (WW) NVIDIA(GPU-0): for mode "720x480".
[ 70.835] (==) NVIDIA(0):
[ 70.835] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[ 70.835] (==) NVIDIA(0): will be used as the requested mode.
[ 70.835] (==) NVIDIA(0):
[ 70.835] (II) NVIDIA(0): Validated MetaModes:
[ 70.835] (II) NVIDIA(0): "DFP-1:nvidia-auto-select"
[ 70.835] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1200
[ 70.863] (--) NVIDIA(0): DPI set to (93, 95); computed from "UseEdidDpi" X config
[ 70.863] (--) NVIDIA(0): option
[ 70.863] (--) Depth 24 pixmap format is 32 bpp
[ 70.863] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
[ 70.863] (II) NVIDIA: access.
[ 70.867] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 70.867] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 70.867] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 70.867] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 70.867] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 70.867] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 70.867] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 70.867] (II) NVIDIA(0): Config Options in the README.
[ 73.872] (II) NVIDIA(0): Setting mode "DFP-1:nvidia-auto-select"
[ 80.897] (EE)
[ 80.897] (EE) Backtrace:
[ 80.898] (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x5979d6]
[ 80.898] (EE) 1: /usr/bin/X (0x400000+0x19b8c9) [0x59b8c9]
[ 80.898] (EE) 2: /lib64/libpthread.so.0 (0x7fcdd1510000+0x10810) [0x7fcdd1520810]
[ 80.898] (EE) 3: /lib64/libc.so.6 (0x7fcdd0170000+0x136284) [0x7fcdd02a6284]
[ 80.898] (EE) 4: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7fcdce668000+0x116fd3) [0x7fcdce77efd3]
[ 80.898] (EE) 5: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7fcdce668000+0x1172ed) [0x7fcdce77f2ed]
[ 80.898] (EE) 6: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7fcdce668000+0xab654) [0x7fcdce713654]
[ 80.898] (EE) 7: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7fcdce668000+0xe64e1) [0x7fcdce74e4e1]
[ 80.898] (EE) 8: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7fcdce668000+0xb87ed) [0x7fcdce7207ed]
[ 80.898] (EE) 9: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7fcdce668000+0x55a3d2) [0x7fcdcebc23d2]
[ 80.898] (EE) 10: /usr/bin/X (AddScreen+0x88) [0x439928]
[ 80.898] (EE) 11: /usr/bin/X (InitOutput+0x3fc) [0x47d09c]
[ 80.898] (EE) 12: /usr/bin/X (0x400000+0x280e3) [0x4280e3]
[ 80.898] (EE) 13: /lib64/libc.so.6 (__libc_start_main+0xec) [0x7fcdd01924cc]
[ 80.898] (EE) 14: /usr/bin/X (0x400000+0x27e09) [0x427e09]
[ 80.898] (EE)
[ 80.898] (EE) Segmentation fault at address 0x7fcdd219fff0
[ 80.898]
Fatal server error:
[ 80.898] Caught signal 11 (Segmentation fault). Server aborting
[ 80.898]
[ 80.898] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 80.898] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 80.898] (EE)
[ 80.900] Server terminated with error (1). Closing log file.

cat /etc/X11/xorg.conf
# uncomment when the card gets IN

Section "Device"
Identifier "Nvidia card"
Driver "nvidia"
EndSection

eselect opengl list
Available OpenGL implementations:
[1] nvidia
[2] xorg-x11 *

I run: emerge -1av $(qlist -IC x11-drivers)
but it doesn't help

--
Joseph

[Canek Peláez Valdés]

If you are using the nvidia driver in your xorg.conf, shouldn't you
have the NVidia OpenGL implementation?

Regards.
--
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México

[Joseph]

On 02/22/13 01:22, Canek Pel�ez Vald�s wrote:
>>
>> cat /etc/X11/xorg.conf
>> # uncomment when the card gets IN
>>
>> Section "Device"
>> Identifier "Nvidia card"
>> Driver "nvidia"
>> EndSection
>>
>> eselect opengl list
>> Available OpenGL implementations:
>> [1] nvidia
>> [2] xorg-x11 *
>
>If you are using the nvidia driver in your xorg.conf, shouldn't you
>have the NVidia OpenGL implementation?
>
>Regards.
>--

>Canek Pel�ez Vald�s
>Posgrado en Ciencia e Ingenier�a de la Computaci�n
>Universidad Nacional Aut�noma de M�xico

Yes, I tried "nvidia" as well but still getting the same error message :-/

--
Joseph

[Alexandre Domi]

Seems you're getting a nvidia segfault... Did you try revdep-rebuild, or updating your system?

Regards

Le 22 févr. 2013 08:35, "Joseph" <sysc...@gmail.com> a écrit :

On 02/22/13 01:22, Canek Peláez Valdés wrote:

cat /etc/X11/xorg.conf
# uncomment when the card gets IN

Section "Device"
    Identifier "Nvidia card"
    Driver     "nvidia"
EndSection

eselect opengl list
Available OpenGL implementations:
  [1]   nvidia
  [2]   xorg-x11 *

If you are using the nvidia driver in your xorg.conf, shouldn't you
have the NVidia OpenGL implementation?

Regards.
--

Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México

[Joseph]

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;
...

And I did run "ake oldconfig" when I upgraded the kernel.

--
Joseph

[Dale]

It also says to run make prepare. Me, I would run "make all" if I
could. I'm assuming you have complete access to your own system here.

My next question in my mind. How did you compile a kernel and not run
make all? If you compiled the kernel you are running on that system
then all that should be there. That leads to a new question. What
kernel is /usr/src/linux pointing too? Is it the correct one?

Just thinking out loud here. Maybe it helps.

Dale

:-) :-)

--
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!

[Joseph]

I fore got to add, when I run: When I run nvidia-settings I get

You do not appear to be using the NVIDIA X driver. Please edit your X configuration file (just run `nvidia-xconfig` as root),
and restart the X server.

but we don't have `nvidia-xconfig`

--
Joseph

[Alexandre Domi]

That'd be right.

It could be that /usr/src/linux is pointing to an unmerged kernel (that's the only reason I see for the missing files...)

2013/2/22 Dale <rdale...@gmail.com>

[Dale]

Joseph wrote:
> On 02/22/13 02:36, Dale wrote:

> I just run: make all
> make[1]: Nothing to be done for `all'.
> make[1]: Nothing to be done for `relocs'.
> CHK include/linux/version.h
> CHK include/generated/utsrelease.h
> CALL scripts/checksyscalls.sh
> CHK include/generated/compile.h
> make[3]: `arch/x86/realmode/rm/realmode.bin' is up to date.
> Kernel: arch/x86/boot/bzImage is ready (#2)
> Building modules, stage 2.
> MODPOST 6 modules
>
> usuall after: make oldconfig
> I run: make && make modules_install
>
> the kernel I'm using is linux-3.5.7-gentoo
>


Then the error you are getting is weird. I do basically the same thing
as you. I run make oldconfig, answer the questions there, run make all
&& make modules_install and that is it. After that, I can update
nvidia's drivers and such and it not complain. I have in the past
forgot to change the symlink tho. I used to do it manually but now use
eselect to do that. Just for giggles, what does eselect kernel list
show as being selected? Maybe something is not quite right there.

[Joseph]

On 02/22/13 02:36, Dale wrote:

I just run:
make all
make[1]: Nothing to be done for `all'.
make[1]: Nothing to be done for `relocs'.
CHK include/linux/version.h
CHK include/generated/utsrelease.h
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
make[3]: `arch/x86/realmode/rm/realmode.bin' is up to date.
Kernel: arch/x86/boot/bzImage is ready (#2)
Building modules, stage 2.
MODPOST 6 modules

usuall after: make oldconfig
I run: make && make modules_install

the kernel I'm using is linux-3.5.7-gentoo

--
Joseph

[Joseph]

On 02/22/13 09:52, Alexandre Domi wrote:
> That'd be right.
> It could be that /usr/src/linux is pointing to an unmerged kernel
> (that's the only reason I see for the missing files...)

I just installed this kernel:
emerge =sys-kernel/gentoo-sources-3.5.7
--
Joseph

[Alexandre Domi]

Yes, but what does 'eselect kernel list' show you?

2013/2/22 Joseph <sysc...@gmail.com>

[Joseph]

On 02/22/13 02:59, Dale wrote:
>>>> 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;
>>>> ...
>>>>
>>>> And I did run "ake oldconfig" when I upgraded the kernel.
>

>Then the error you are getting is weird. I do basically the same thing
>as you. I run make oldconfig, answer the questions there, run make all
>&& make modules_install and that is it. After that, I can update
>nvidia's drivers and such and it not complain. I have in the past
>forgot to change the symlink tho. I used to do it manually but now use
>eselect to do that. Just for giggles, what does eselect kernel list
>show as being selected? Maybe something is not quite right there.
>
>Dale

I just re-emerge the kernel and linux is pointing to correct one:
lrwxrwxrwx 1 root root 18 Feb 21 22:35 linux -> linux-3.5.7-gentoo

I run: make all && make modules_instal
emerge nvidia-drivers

but still getting that strange error listed above.

--
Joseph

[Joseph]

On 02/22/13 10:14, Alexandre Domi wrote:
> Yes, but what does 'eselect kernel list' show you?

eselect kernel list
Available kernel symlink targets:
[1] linux-2.6.32-gentoo-r29
[2] linux-3.1.5-gentoo
[3] linux-3.1.6-gentoo
[4] linux-3.5.7-gentoo *

--
Joseph

[Joseph]

I have nvidia-dirvers emerged with flag "tools" but I don't have binary: "nvidia-xconfig"
and some other users have this binary, so what is going on :-/

--
Joseph

[Joseph]

In addition I get the flooring errors in Xorg.0.log

cat /var/log/Xorg.0.log | grep EE
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 288.401] Initializing built-in extension MIT-SCREEN-SAVER
[ 313.863] (EE)
[ 313.863] (EE) Backtrace:
[ 313.863] (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x5979d6]
[ 313.863] (EE) 1: /usr/bin/X (0x400000+0x19b8c9) [0x59b8c9]
[ 313.863] (EE) 2: /lib64/libpthread.so.0 (0x7fdb5cc20000+0x10810) [0x7fdb5cc30810]
[ 313.863] (EE) 3: /lib64/libc.so.6 (0x7fdb5b880000+0x136284) [0x7fdb5b9b6284]
[ 313.863] (EE) 4: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7fdb56fd8000+0x116fd3) [0x7fdb570eefd3]
[ 313.863] (EE) 5: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7fdb56fd8000+0x1172ed) [0x7fdb570ef2ed]
[ 313.863] (EE) 6: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7fdb56fd8000+0xab654) [0x7fdb57083654]
[ 313.863] (EE) 7: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7fdb56fd8000+0xe64e1) [0x7fdb570be4e1]
[ 313.863] (EE) 8: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7fdb56fd8000+0xb87ed) [0x7fdb570907ed]
[ 313.863] (EE) 9: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7fdb56fd8000+0x55a3d2) [0x7fdb575323d2]
[ 313.863] (EE) 10: /usr/bin/X (AddScreen+0x88) [0x439928]
[ 313.864] (EE) 11: /usr/bin/X (InitOutput+0x3fc) [0x47d09c]
[ 313.864] (EE) 12: /usr/bin/X (0x400000+0x280e3) [0x4280e3]
[ 313.864] (EE) 13: /lib64/libc.so.6 (__libc_start_main+0xec) [0x7fdb5b8a24cc]
[ 313.864] (EE) 14: /usr/bin/X (0x400000+0x27e09) [0x427e09]
[ 313.864] (EE)
[ 313.864] (EE) Segmentation fault at address 0x7fdb5d8b7ff0
[ 313.864] (EE)
[ 313.864] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 313.864] (EE)

--
Joseph

[Dale]

Grasping at straws here. What does df -h show? You don't have to post
it. Just see if you have space left on whatever /usr is on. Maybe it
is full or something.

Other than this, I'm pretty much clueless. This is weird. Maybe
someone else will come up with a idea.

[Joseph]

On 02/22/13 03:33, Dale wrote:
>Joseph wrote:
>> On 02/22/13 10:14, Alexandre Domi wrote:
>>> Yes, but what does 'eselect kernel list' show you?
>>
>> eselect kernel list
>> Available kernel symlink targets:
>> [1] linux-2.6.32-gentoo-r29
>> [2] linux-3.1.5-gentoo
>> [3] linux-3.1.6-gentoo
>> [4] linux-3.5.7-gentoo *
>>
>
>Grasping at straws here. What does df -h show? You don't have to post
>it. Just see if you have space left on whatever /usr is on. Maybe it
>is full or something.
>
>Other than this, I'm pretty much clueless. This is weird. Maybe
>someone else will come up with a idea.
>
>Dale

Plenty of room:

df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 74G 14G 56G 20% /
/dev/root 74G 14G 56G 20% /
tmpfs 3.9G 760K 3.9G 1% /run
udev 10M 0 10M 0% /dev
shm 3.9G 0 3.9G 0% /dev/shm
cgroup_root 10M 0 10M 0% /sys/fs/cgroup
/dev/sda4 925G 401G 478G 46% /home
/dev/sda5 828G 400G 386G 51% /home2

--
Joseph

[Raffaele BELARDI]

On 02/22/2013 10:39 AM, Joseph wrote:
> In addition I get the flooring errors in Xorg.0.log
>
> cat /var/log/Xorg.0.log | grep EE
> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> [ 288.401] Initializing built-in extension MIT-SCREEN-SAVER
> [ 313.863] (EE)
> [ 313.863] (EE) Backtrace:
> [ 313.863] (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x5979d6]
> [ 313.863] (EE) 1: /usr/bin/X (0x400000+0x19b8c9) [0x59b8c9]
> [ 313.863] (EE) 2: /lib64/libpthread.so.0 (0x7fdb5cc20000+0x10810) [0x7fdb5cc30810]
> [ 313.863] (EE) 3: /lib64/libc.so.6 (0x7fdb5b880000+0x136284) [0x7fdb5b9b6284]
> [ 313.863] (EE) 4: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7fdb56fd8000+0x116fd3) [0x7fdb570eefd3]

Did you also update the Nvidia driver when you updated the system? Maybe
the new Nvidia driver does not support your graphic board.

I have a GeForce GT 520 box where I am stuck with nvidia-drivers-295.20
because newer drivers segfault (even though officially they should
support the GT520).

raffaele

[Joseph]

According to lspic I have:
VGA compatible controller: NVIDIA Corporation GF116 [GeForce GTS 450] (rev a1)

So are you saying I should downgrade to 295.20?

--
Joseph

[Joseph]

On 02/22/13 10:49, Raffaele BELARDI wrote:

Yes, I'm running nvidia-drivers-304.64

--
Joseph

[Raffaele BELARDI]

I don't know, but it might be worth a try.

What was the last working version of nvidia-drivers that you had? You
could try to downgrade to that one.

raffaele

[Dale]

You may want to check out this page:

http://www.nvidia.com/object/linux-display-amd64-310.32-driver.html

If I selected something incorrectly, you can just start the process over
in the upper left part of the page where it says drivers.

[Joseph]

I went back to kernel-3.1.6 and the nvidia-driever-295.75 and 304.64 both working correctly.
But when I go to kernel-3.5.7 the nvidia-drivers are not working.

--
Joseph

[Dale]

Looks like you need to avoid that kernel version. I would try 3.7.8 or
something. I wouldn't use the 3.8 just yet. There was another thread
about it having some sort of changes and the nvidia drivers *may* not be
ready.

At least you have a screen to look at now. ;-)

[Joseph]

On 02/22/13 06:53, Dale wrote:
>Joseph wrote:
>> On 02/22/13 06:17, Dale wrote:
>>>
>>> You may want to check out this page:
>>>
>>> http://www.nvidia.com/object/linux-display-amd64-310.32-driver.html
>>>
>>> If I selected something incorrectly, you can just start the process over
>>> in the upper left part of the page where it says drivers.
>>>
>>> Dale
>>
>> I went back to kernel-3.1.6 and the nvidia-driever-295.75 and 304.64
>> both working correctly. But when I go to kernel-3.5.7 the
>> nvidia-drivers are not working.
>>
>
>Looks like you need to avoid that kernel version. I would try 3.7.8 or
>something. I wouldn't use the 3.8 just yet. There was another thread
>about it having some sort of changes and the nvidia drivers *may* not be
>ready.
>
>At least you have a screen to look at now. ;-)
>
>Dale

I'm on kernel 3.1.6 and not moving any further, if it ain't broken don't fix it :-)
They are moving with changing too fast and not testing it correctly, creating hell for us users.

--
Joseph

[Dale]

Joseph wrote:
>
> I'm on kernel 3.1.6 and not moving any further, if it ain't broken
> don't fix it :-)
> They are moving with changing too fast and not testing it correctly,
> creating hell for us users.
>

My solution, don't reboot. lol I do upgrade when I can tho. If 3.1.6
is working, use it for a while until you can test another version and
have success. I've had to skip versions a few times to because of a
problem with something not working right. It happens.

[walt]

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.

[Joseph]

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

[Nikos Chantziaras]

On 22/02/13 08:14, Joseph wrote:
> I just upgraded system including kernel to 3.5.7 because of udev-197
> Now I have a blank screen, not even console login (I can only access is
> via ssh)

With NVidia, it is usually a good idea to at least use the latest stable
gentoo-sources. So you should use 3.7.9. Also, it *is* a good idea to
keyword the latest NVidia driver that's considered stable by NVidia, not
by Gentoo. That would be 313.18.

So update to gentoo-sources-3.7.9 and nvidia-drivers-313.18. And make
sure you do (as root):

eselect opencl set nvidia
eselect opengl set nvidia

[Joseph]

I'm starting to have serious doubts in Nvidia (those binary drivers are piece of crap).
My system just freeze after one day; I went back to nvidia-dirvers-295.75

--
Joseph

[Neil Bothwick]

On Sat, 23 Feb 2013 00:32:15 -0700, Joseph wrote:

> I'm starting to have serious doubts in Nvidia (those binary drivers are
> piece of crap). My system just freeze after one day; I went back to
> nvidia-dirvers-295.75

Have you tried the nouveau drivers? The 3D may not be as fast but the
kernel incompatibilities disappear.


--
Neil Bothwick

Crash: (v.) to terminate a program in the usual fashion, i.e. by locking
up the computer or setting fire to the printer. (n.) the process of such
termination.

[Joseph]

On 02/23/13 07:24, Nikos Chantziaras wrote:

According to nvidia the latest stable "certified" driver for my card:
GeForce GTS 450
is: 310.32 (which is in portage)

I tried it with kernel-3.6.11 it does not work but it works with 3.1.6
I don't know why?

--
Joseph

[Randolph Maaßen]

2013/2/23 Joseph <sysc...@gmail.com>

Hi,

I have just read the thread and recognized that you have the same graphics card as I have.

I updated my kernel this week to gentoo-sources 3.8.0. After that I tried to install the 313.18 driver and compilation failed.

So I tried the 310.32  driver and it works perfectly with the new kernel.

HTH

--

Mit freundlichen Grüßen / Best regards

 

Randolph Maaßen

[Joseph]

On 02/23/13 08:55, Neil Bothwick wrote:
>On Sat, 23 Feb 2013 00:32:15 -0700, Joseph wrote:
>
>> I'm starting to have serious doubts in Nvidia (those binary drivers are
>> piece of crap). My system just freeze after one day; I went back to
>> nvidia-dirvers-295.75
>
>Have you tried the nouveau drivers? The 3D may not be as fast but the
>kernel incompatibilities disappear.
>
>
>--
>Neil Bothwick

According to Nvidia (http://www.nvidia.com/object/linux-display-amd64-310.32-driver.html)
the latest stable driver for my card GeForce GTS 450
is: 310.32
This driver works with kernel-3.1.6 but not with latest 3.6.11

I'm trying to setup dual driver as nvidia and nouveau as a backup.

--
Joseph

[Joseph]

On 02/22/13 10:49, Raffaele BELARDI wrote:

The official stable driver (certified by nvidia) for your card is the same one as for mine: 310.32
http://www.nvidia.com/object/linux-display-amd64-310.32-driver.html

Just unmask it and use it, it is working on my system OK with kernel 3.1.6 but, it will work with 3.8 as well (as just reported by Randolph Maa�en)

--
Joseph

[Nikos Chantziaras]

On 24/02/13 00:53, Joseph wrote:
> On 02/23/13 08:55, Neil Bothwick wrote:
>> On Sat, 23 Feb 2013 00:32:15 -0700, Joseph wrote:
>>
>>> I'm starting to have serious doubts in Nvidia (those binary drivers are
>>> piece of crap). My system just freeze after one day; I went back to
>>> nvidia-dirvers-295.75
>>
>> Have you tried the nouveau drivers? The 3D may not be as fast but the
>> kernel incompatibilities disappear.
>>
>>
>> --
>> Neil Bothwick
>
> According to Nvidia
> (http://www.nvidia.com/object/linux-display-amd64-310.32-driver.html)
> the latest stable driver for my card GeForce GTS 450
> is: 310.32 This driver works with kernel-3.1.6 but not with latest 3.6.11

Nope. The latest driver for you card is the latest driver available. The
400 series is *not* a legacy product. The 310.32 driver is the latest
long-term release driver. The 313.18 is the latest short-term release
driver and it also supports your card:

http://www.nvidia.com/object/linux-display-amd64-313.18-driver.html