SliTaz SliTaz Forum

You are not logged in.

#1 2012-02-12 19:32:17

michaelbischof
Member
Registered: 2012-01-20
Posts: 536

nvidia compiling failed

Hi all,

I have to revive an old thing as I came to the same point:

http://forum.slitaz.org/topic/installing-legacy-nvidia-driver-geforce4-mx420#post-3774

My new private, special enemy is this GeForce 7100 FX graphic card. I run the driver nv, but for good sport I  wanted to try the non-free driver of Jozee:

nvidia-173xx-173.14.25_2.6.30.6.tazpkg

To install it via tazpkg was no problem. But it did not effect in any respect.

With lsmod it did not appear, after depmod -a it did not appear. So what?

I tried to download another driver from the Nvidia-support-page

NVIDIA-Linux-x86-173.14.31-pkg1.run

- this wants apparently to compile a new kernel. I followed the different error messages step by step, installed the necessary tools - and it always ends there were once ertw1 came to:

,,I'm following this guide http://doc.slitaz.org/en:guides:nvidia to install legacy nvidia drivers from the nvidia website to support my Geforce4 MX420 card. Everything goes fine till this step:

make oldconfig && make prepare

At this point I get an error: no rule to make target "oldconfig"

Gentlemen: what to do now?

Offline

#2 2012-02-12 20:42:56

Trixar_za
Administrator
Registered: 2011-03-29
Posts: 1,506

Re: nvidia compiling failed

make config && make prepare ?

Offline

#3 2012-02-12 21:02:56

michaelbischof
Member
Registered: 2012-01-20
Posts: 536

Re: nvidia compiling failed

Thank you - but:

root@slitaz:/usr/src/linux-2.6.37# make config && make prepare

make: Nothing to be done for `config'.

make: *** No rule to make target `prepare'.  Stop.

Offline

#4 2012-02-12 21:38:04

Trixar_za
Administrator
Registered: 2011-03-29
Posts: 1,506

Re: nvidia compiling failed

Read the INSTALL or README files

Offline

#5 2012-02-12 22:14:20

michaelbischof
Member
Registered: 2012-01-20
Posts: 536

Re: nvidia compiling failed

Well, that I had done several times. Whatever I tried I never surpassed this end:

Using: nvidia-installer ncurses user interface

WARNING: Skipping the runlevel check (the utility [c]runlevel[/c] was not found).

-> License accepted.

-> Installing NVIDIA driver version 173.14.31.

-> Performing CC sanity check with CC="cc".

-> Performing CC version check with CC="cc".

ERROR: Unable to determine the version of the kernel sources located in

       '/lib/modules/2.6.37-slitaz/source'.  Please make sure you have

       installed the kernel source files for your kernel and that they are

       properly configured; on Red Hat Linux systems, for example, be sure you

       have the 'kernel-source' or 'kernel-devel' RPM installed.  If you know

       the correct kernel source files are installed, you may specify the

       kernel source path with the '--kernel-source-path' command line option.

ERROR: Installation has failed.  Please see the file

       '/var/log/nvidia-installer.log' for details.  You may find suggestions

       on fixing installation problems in the README available on the Linux

       driver download page at www.nvidia.com.

(This was the end of the log file)

Offline

#6 2012-02-13 07:13:14

Trixar_za
Administrator
Registered: 2011-03-29
Posts: 1,506

Re: nvidia compiling failed

Install the linux-source (it's a 50MB+ download), slitaz-toolchain and slitaz-dev-pkgs packages. You're going to need all of them to compile the driver.

Offline

#7 2012-02-13 08:41:56

michaelbischof
Member
Registered: 2012-01-20
Posts: 536

Re: nvidia compiling failed

Damned, no success either:

,,Using: nvidia-installer ncurses user interface

WARNING: Skipping the runlevel check (the utility [c]runlevel[/c] was not found).

-> License accepted.

-> Installing NVIDIA driver version 173.14.31.

-> Performing CC sanity check with CC="cc".

-> Performing CC version check with CC="cc".

-> Using the kernel source path '/lib/modules/2.6.37-slitaz/source' as

   specified by the '--kernel-source-path' commandline option.

ERROR: Unable to determine the version of the kernel sources located in

       '/lib/modules/2.6.37-slitaz/source'.  Please make sure you have

       installed the kernel source files for your kernel and that they are

       properly configured; on Red Hat Linux systems, for example, be sure you

       have the 'kernel-source' or 'kernel-devel' RPM installed.  If you know

       the correct kernel source files are installed, you may specify the

       kernel source path with the '--kernel-source-path' command line option.

ERROR: Installation has failed.  Please see the file

       '/var/log/nvidia-installer.log' for details.  You may find suggestions

       on fixing installation problems in the README available on the Linux

       driver download page at www.nvidia.com."

That was from this log. With a previous effort it complained that it did not find ,,kernel.h". So I had copied that from /usr/src/linux/include/linux to /lib/modules/2.6.37-slitaz/source/

Damned, I want to bring down this beast on its knees.

By the way: to be forced to compile a kernel just for installing a sh... old graphic card is of course an artifical burgen against linux - so deepheartedly I want to demonstrate that even this won't stop us! ;-)

By the way: it is not like that I cant use slitaz-cooking with this nv driver for that card. It is a matter of principle! ;-)

Offline

#8 2012-02-13 11:43:54

michaelbischof
Member
Registered: 2012-01-20
Posts: 536

Re: nvidia compiling failed

No way, whatever I try the error message is always the same:

,,nvidia-installer command line:

    ./nvidia-installer

Using: nvidia-installer ncurses user interface

WARNING: Skipping the runlevel check (the utility [c]runlevel[/c] was not found).

-> License accepted.

-> Installing NVIDIA driver version 290.10.

-> Performing CC sanity check with CC="cc".

-> Performing CC version check with CC="cc".

ERROR: Unable to determine the version of the kernel sources located in '/lib/modules/2.6.37-slitaz/source'.  Please make sure you have installed the kernel source files for your kernel and that they are properly configured; on Red Hat Linux systems, for example, be sure you have the 'kernel-source' or 'kernel-devel' RPM installed.  If you know the correct kernel source files are installed, you may specify the kernel source path with the '--kernel-source-path' command line option.

ERROR: Installation has failed.  Please see the file '/var/log/nvidia-installer.log' for details.  You may find suggestions on fixing installation problems in the README available on the Linux driver download page at www.nvidia.com."

So either this kernel.h-file is not ok - or this installation program cannot do it. Any experiences here for that problem?

Offline

#9 2012-02-13 12:52:39

totoetsasoeur
Moderator
Registered: 2011-03-29
Posts: 247

Re: nvidia compiling failed

Have you installed the linux-source? http://doc.slitaz.org/en:guides:kernel

Offline

#10 2012-02-13 13:13:23

Trixar_za
Administrator
Registered: 2011-03-29
Posts: 1,506

Re: nvidia compiling failed

Also, do you have the linux-headers package installed?

Offline

#11 2012-02-13 16:18:23

michaelbischof
Member
Registered: 2012-01-20
Posts: 536

Re: nvidia compiling failed

Yes, I have - and finally it worked. A nvidia module was compiled.

It sits in /lib/modules/2.6.37-slitaz/kernel/drivers/video, it is called nvidia.ko and has a size of 12,3 MB.

But it was difficult to get it installed using insmod - although at the end it worked as well.

Now lsmod gives

root@slitaz:~# lsmod | grep nvidia

nvidia              10719403  0

agpgart                18221  3 nvidia,ttm,drm

i2c_core               12192  4 nvidia,drm_kms_helper,drm,i2c_algo_bit

- but the system itself is quite corrupted now by many efforts to get rid of those many programs necessary just for compiling. It got so hugh > 500 MB that I could not use ,,tazlito writeiso" to save it as it is. The desired module I will save - of course!

But to be frank: it was kind of strange sport, not really necessary to make use of slitaz.

Offline

#12 2012-02-13 20:07:34

michaelbischof
Member
Registered: 2012-01-20
Posts: 536

Re: nvidia compiling failed

Not to forget the end of the story:

I succeeded in compiling the module but was not able ,,to make it run". Depmod -a, insmod, modprobe and all that did not really work.

After researching quite a bit I question that this kernel of cooking runs well with Nvidia graphic cards. Any other information?

This package I tried as well:

nvidia-195.36.15_2.6.37.tazpkg

Did not work, or I am too stupid to make it work. Who knows?

Offline

#13 2012-02-13 22:23:54

pankso
Administrator
Registered: 2026-06-27
Posts: 341
Website

Re: nvidia compiling failed

Hi,

Official Nvidia package (nvidia-195.36.15_2.6.37.tazpkg) seems to have build succefully so it should provide the kernel module. Anyway, once you have installed the package from repo or source you must tell the system to use it. I guess you must reconfigure Xorg and load the nvidia kernel module via 'modprobe nvidia'

Official cook: http://cook.slitaz.org/cooker.cgi?pkg=nvidia

There is a page on SliTaz Wiki about compiling from source the nvidia module, you may improve it with your experience and refer to the official package as well :-) http://doc.slitaz.org/en:guides:nvidia

- Christophe

Offline

#14 2012-02-13 23:53:54

michaelbischof
Member
Registered: 2012-01-20
Posts: 536

Re: nvidia compiling failed

No, unfortunately is not that easy.

When you have installed nvidia-195.36.15_2.6.37.tazpkg you cannot reconfigure Xorg. Because the module nvidia is not loaded, nouveau is loaded. This is done when booting. A module claims the kernel it says.

In case you try to load ,modprobe nvidia' and then check with 'tazhw detect-pci' you will see that the module nvidia is not loaded.

Therefore I am damned curious for any feedback from any reader who has managed that.

If I blacklist nouveau after having installed nvidia then the module nvidia is loaded. But it is not possible to get a useful Xorg-configuration. And: in this case you cannot try 'taz x', install nv - then nouveau is loaded but nvidia still ,,claims" the kernel. Tricky, eh?

Offline

#15 2012-02-14 13:53:13

michaelbischof
Member
Registered: 2012-01-20
Posts: 536

Re: nvidia compiling failed

@all

Did anybody succeed in running the nvidia non-free thing on cooking?

What I tried the latest:

I always run into trouble with nvidia module because the nouveau module got loaded when booting. Then it was not possible to unload it by using depmod -r nouveau or rmmod nouveau. Finally both modules were shown by tazhw detect-pci, but the nvidia-settings did not work.

So I started with justx-cooking, installed the nvidia non-free 195... something. It did not work:

- glxinfo error in libc-2.12.so Segmentatin fault

- error shared libraries libffi.so.5

I installed libffi - no help. So much question is whether this cooking-kernel actually can work with nvidia non-free (the nomodeset thing I did not forget).

Offline

#16 2012-02-14 15:40:24

mojo
Administrator
Registered: 2011-03-29
Posts: 2,174

Re: nvidia compiling failed

@pankso

My username/password information sent to pankso@slitaz.org does not work at repos.slitaz.org

@michaelbischof

Built this for my nvidia 8400gs on cooking:

http://www.mediafire.com/file/7v20zi36bbv0443/nvidia-173xx-173.14.28_2.6.37.tazpkg

Supported nvidia chipsets:

ftp://download.nvidia.com/XFree86/Linux-x86/173.14.28/README/appendix-a.html

Offline

#17 2012-02-14 16:00:50

michaelbischof
Member
Registered: 2012-01-20
Posts: 536

Re: nvidia compiling failed

Wow, thanks a lot, Mojo. But now I am the way to our monthly Linux group meeting - so this I will check out tomorrow. I am not a fanatic but used to win - in the end! ;-)

I must confess, sorry, that with a 1280x1024 resolution on 3.0 there is a visible difference between nouveau and nvidia-non-free. On a laptop with 1400 resolution I cannot see any difference. Slitaz is nice enough, this is just sport (for learning, at the end). This ,,tazlito writeiso"-thing offers quite a lot of new possibilities.

By the way (too much documention to read!): which flavour contains everything ready for compiling? May be I overlooked something.

Offline

#18 2012-02-14 22:40:01

michaelbischof
Member
Registered: 2012-01-20
Posts: 536

Re: nvidia compiling failed

Look at the time, please: Heureka!

Details some minutes later. And, admittedly, with great regret I must confess - it makes quite a difference whether one uses nouveau with particularly this graphic card or the proprietary driver (at 1280x1024).

Mojo, a big bang kiss! ;-)

Michael

Offline

#19 2012-02-14 23:33:29

michaelbischof
Member
Registered: 2012-01-20
Posts: 536

Re: nvidia compiling failed

The details:

I tried this on slitaz-core. All I did was to download the package of Mojo, install it,

Detected PCI devices Kernel modules

================================================================================

> Module in use:   snd_ca0106

> Module in use:   sky2

! Missing module:  nouveau,

> Module in use:   nvidia

The module is called nvidia_agp

This evening I learned at lot about this topic in our local Linux user group! Well, linux is about cooperation anyway. But I have to confess: this all was sort of crazy sport. It  is not like that one cannot use Slitaz-cooking without those things, with nouveau one can use it as well.

Offline

#20 2012-02-15 15:09:08

michaelbischof
Member
Registered: 2012-01-20
Posts: 536

Re: nvidia compiling failed

(The following lines are no ,,cry for help", just a description)

Today I tried to bring into use another old machine,500 MB RAM, GeForce 6600. Slitaz-3.0 runs well, Slitaz-vesa as well. With Slitaz-cooking one has to apply the cmd-line ,,nomodeset".

To use the normal way ,,tazhw setup nvidia --non-free" has no result at all. The package gets installed without any error, but then the card does not come into use. For schook kids this would be the final close - on the other hand slitaz-cooking performs well, just looks way less good than a distribution like Mandriva 2010.0 on the same machine. Below I can show how they do it, automatically, newbies couldn't do that manually.

So I question whether sucha thing would make sense on Slitaz.

Just some feed back for those interested - I tried some flavours on this machine:

- the new light-flavour of mojo (new kind of vesa): worked good, but ,,nomodeset"

- flavour ,,for kids": ok, but: in the bootline one has to type ,,lang=de kmap=de" in addition to nomodeset. Otherwise the keyboard does not react, neither the mouse, and after logout the screen remains black.

- flavour framebuffer fb: did not work, segmentation faults

To make use of the flexibility of Slitaz in order to be able to compile some module, some software, it would be nice to have a ,,ready" dev-version als .iso at hand, suited to the particular kernel version. Just thoughts...

<= By the way: urpmi installed automatically about 20-22 packages just for being able to compile the right module! In case one has to do all that manually... :-(

164/166: x11-driver-video-nvidia-current

                                 ###################################################################################

  165/166: nvidia-current-doc-html

                                 ###################################################################################

  166/166: dkms-nvidia-current   ################################################################################### 

Creating symlink /var/lib/dkms/nvidia-current/256.44-1mdv2010.0/source ->

                 /usr/src/nvidia-current-256.44-1mdv2010.0               

DKMS: add Completed.

Preparing kernel 2.6.31.14-desktop586-1mnb for module build:

(This is not compiling a kernel, just preparing kernel symbols)

Storing current .config to be restored when complete

Running Generic preparation routine

make mrproper.............

using /proc/config.gz

make oldconfig......

make prepare....                                               

Building module:

cleaning build area....

make KERNELRELEASE=2.6.31.14-desktop586-1mnb SYSSRC=/lib/modules/2.6.31.14-desktop586-1mnb/build module..............................

cleaning build area....

cleaning kernel tree (make mrproper).......

DKMS: build Completed.

nvidia-current.ko.gz:

- Installation

   - Installing to /lib/modules/2.6.31.14-desktop586-1mnb/dkms/drivers/char/drm/

depmod..........

DKMS: install Completed.

-------- Uninstall Beginning --------

Module:  nvidia-current

Version: 185.18.36-4mdv2010.0

Kernel:  2.6.31.14-desktop586-1mnb (i586)

-------------------------------------

164/166: x11-driver-video-nvidia-current

                                 ###################################################################################

  165/166: nvidia-current-doc-html

                                 ###################################################################################

  166/166: dkms-nvidia-current   ################################################################################### 

Creating symlink /var/lib/dkms/nvidia-current/256.44-1mdv2010.0/source ->

                 /usr/src/nvidia-current-256.44-1mdv2010.0               

DKMS: add Completed.

Preparing kernel 2.6.31.14-desktop586-1mnb for module build:

(This is not compiling a kernel, just preparing kernel symbols)

Storing current .config to be restored when complete

Running Generic preparation routine

make mrproper.............

using /proc/config.gz

make oldconfig......

make prepare....                                               

Building module:

cleaning build area....

make KERNELRELEASE=2.6.31.14-desktop586-1mnb SYSSRC=/lib/modules/2.6.31.14-desktop586-1mnb/build module..............................

cleaning build area....

cleaning kernel tree (make mrproper).......

DKMS: build Completed.

nvidia-current.ko.gz:

- Installation

   - Installing to /lib/modules/2.6.31.14-desktop586-1mnb/dkms/drivers/char/drm/

depmod..........

DKMS: install Completed.

-------- Uninstall Beginning --------

Module:  nvidia-current

Version: 185.18.36-4mdv2010.0

Kernel:  2.6.31.14-desktop586-1mnb (i586)

-------------------------------------

Status: This module version was INACTIVE for this kernel.

depmod......

DKMS: uninstall Completed.

------------------------------

Deleting module version: 185.18.36-4mdv2010.0

completely from the DKMS tree.

------------------------------

Done.

Danke für die Verwendung von smart-urpmi

Status: This module version was INACTIVE for this kernel.

depmod......

DKMS: uninstall Completed.

------------------------------

Deleting module version: 185.18.36-4mdv2010.0

completely from the DKMS tree.

------------------------------

Offline

#21 2012-02-21 19:32:38

michaelbischof
Member
Registered: 2012-01-20
Posts: 536

Re: nvidia compiling failed

This time I write from a slitaz-core installation. Kernel 2.6.37. Did anybody here ever succeed in installing a nvidia-graphic card with this kernel?

On this particular machine it is a GeForce 7100 GS. From Mandriva I know that I will need the 195.36.15.2.6.37-version of the drivers.

To set it up with

#tazhw setup nvidia --non-free

is no headache.

Build Operating System: SliTaz GNU/Linux

Current Operating System: Linux slitaz 2.6.37-slitaz #2 SMP Sat Jan 21 01:52:14 CET 2012 i686

Kernel command line: root=/dev/ram0 rw nomodeset

Build Date: 11 December 2011  01:07:42AM

Current version of pixman: 0.22.0

        Before reporting problems, check http://wiki.x.org

        to make sure that you have the latest version.

Markers: (--) probed, (**) from config file, (==) default setting,

        (++) from command line, (!!) notice, (II) informational,

        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.

(==) Log file: "/var/log/Xorg.1.log", Time: Tue Feb 21 19:29:08 2012

List of video drivers:

        nvidia

        vesa

dlopen: /usr/lib/X11/modules/drivers/nvidia_drv.so: undefined symbol: miEmptyData

(EE) Failed to load /usr/lib/X11/modules/drivers/nvidia_drv.so

(EE) Failed to load module "nvidia" (loader failed, 7)

Using X configuration file: "/root/xorg.conf.new".

New X configuration file written to '/tmp/xorg.conf.nvidia'

Adding to xorg.conf: Option "NoLogo" "True"

Checking if nvidia is working ...

Segmentation fault

================================

Configure nvidia settings :

Invalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 key

ERROR: The control display is undefined; please run [c]nvidia-settings --help[/c]

       for usage information.

I the meantime I know what would happen if I log out from this session: the screen will be black until I re-install nouveau.

Can it be that generally this kernel cannot handle this card? Slitaz 3.0 kernel can handle it.

Offline

#22 2012-02-21 19:56:22

mojo
Administrator
Registered: 2011-03-29
Posts: 2,174

Re: nvidia compiling failed

Commit: http://hg.slitaz.org/wok-undigest/rev/4d10cce9d421

Build log: http://cook.slitaz.org/undigest/cooker.cgi?pkg=nvidia-173xx

Download:

http://cook.slitaz.org/undigest/packages/nvidia-173xx-173.14.31_2.6.37.tazpkg

Offline

#23 2012-02-21 20:05:10

michaelbischof
Member
Registered: 2012-01-20
Posts: 536

Re: nvidia compiling failed

Wow,

damned quick! ;-)

As usual! :-)

I will check it out in a second. Stay tuned.

michael

Offline

#24 2012-02-21 20:41:26

michaelbischof
Member
Registered: 2012-01-20
Posts: 536

Re: nvidia compiling failed

Hmmh,

not yet but we are coming closer.

It did not work but here the output of /var/log/messages:

Feb 21 21:20:30 (none) user.warn kernel: nvidia: module license 'NVIDIA' taints kernel.

Feb 21 21:20:30 (none) daemon.err udevd[4092]: bind failed: Address already in use

Feb 21 21:20:30 (none) user.notice error binding udev control socket

Feb 21 21:20:30 (none) daemon.err udevd[4092]: error binding udev control socket

Feb 21 21:20:30 (none) daemon.err udevd[4093]: bind failed: Address already in use

Feb 21 21:20:30 (none) user.notice error binding udev control socket

Feb 21 21:20:30 (none) daemon.err udevd[4093]: error binding udev control socket

Feb 21 21:20:30 (none) user.warn kernel: Disabling lock debugging due to kernel taint

Feb 21 21:20:30 (none) user.info kernel: nvidia 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16

Feb 21 21:20:30 (none) user.info kernel: vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem

Feb 21 21:20:30 (none) user.warn kernel: NVRM: loading NVIDIA UNIX x86 Kernel Module  173.14.31  Sun Jul 17 22:11:28 PDT 2011

Feb 21 21:21:15 (none) user.debug kernel: mtrr: no MTRR for d0000000,8000000 found

Feb 21 21:21:31 (none) user.info kernel: slim[4111]: segfault at 9 ip b73a61bb sp bf84cad0 error 4 in libxcb.so.1.1.0[b739f000+15000]

Feb 21 21:21:41 (none) auth.info login[4122]: root login on 'tty1'

Feb 21 21:21:50 (none) daemon.err udevd[4140]: bind failed: Address already in use

Feb 21 21:21:50 (none) user.notice error binding udev control socket

Feb 21 21:21:50 (none) daemon.err udevd[4140]: error binding udev control socket

Feb 21 21:21:50 (none) daemon.err udevd[4142]: bind failed: Address already in use

Feb 21 21:21:50 (none) user.info kernel: agpgart-intel 0000:00:00.0: Intel 830M Chipset

Feb 21 21:21:50 (none) user.notice error binding udev control socket

Feb 21 21:21:50 (none) daemon.err udevd[4142]: error binding udev control socket

Feb 21 21:21:50 (none) daemon.err udevd[4143]: bind failed: Address already in use

Feb 21 21:21:50 (none) user.notice error binding udev control socket

Feb 21 21:21:50 (none) daemon.err udevd[4143]: error binding udev control socket

Feb 21 21:21:50 (none) daemon.err udevd[4144]: bind failed: Address already in use

Feb 21 21:21:50 (none) user.info kernel: agpgart-intel 0000:00:00.0: AGP aperture is 128M @ 0xe0000000

Feb 21 21:21:50 (none) user.notice error binding udev control socket

Feb 21 21:21:50 (none) daemon.err udevd[4144]: error binding udev control socket

Feb 21 21:28:42 (none) user.debug kernel: mtrr: no MTRR for d0000000,8000000 found

The xorg.conf-file that did not work:

# nvidia-xconfig: X configuration file generated by nvidia-xconfig

# nvidia-xconfig:  version 1.0  (buildmeister@builder75)  Sun Jul 17 22:46:17 PDT 2011

Section "ServerLayout"

    Identifier     "Layout0"

    Screen      0  "Screen0"

    InputDevice    "Keyboard0" "CoreKeyboard"

    InputDevice    "Mouse0" "CorePointer"

EndSection

Section "Files"

EndSection

Section "InputDevice"

    # generated from default

    Identifier     "Mouse0"

    Driver         "mouse"

    Option         "Protocol" "auto"

    Option         "Device" "/dev/psaux"

    Option         "Emulate3Buttons" "no"

    Option         "ZAxisMapping" "4 5"

EndSection

Section "InputDevice"

    # generated from default

    Identifier     "Keyboard0"

    Driver         "kbd"

EndSection

Section "Monitor"

    Identifier     "Monitor0"

    VendorName     "Unknown"

    ModelName      "Unknown"

    HorizSync       30.0 - 110.0

    VertRefresh     50.0 - 150.0

    Option         "DPMS"

EndSection

Section "Device"

    Identifier     "Device0"

    Driver         "nvidia"

    VendorName     "NVIDIA Corporation"

EndSection

Section "Screen"

    Identifier     "Screen0"

    Device         "Device0"

    Monitor        "Monitor0"

    DefaultDepth    24

    SubSection     "Display"

        Depth       24

    EndSubSection

EndSection

root@slitaz:~# lsmod | grep nvidia

nvidia               7024955  0

agpgart                18221  3 intel_agp,intel_gtt,nvidia

i2c_core               12192  1 nvidia

root@slitaz:~# tazhw detect-pci

Detected PCI devices Kernel modules

================================================================================

> Module in use:   intel_agp

> Module in use:   snd_intel8x0

! Missing module:  nouveau,

> Module in use:   nvidia

@mojo: you are the technician who may be can inerprete that. I am only the user who can try and deliver feed back! ;-)

This was a NV34 GeForce 660 AGP version 3.0 , IRQ 16, kernel modules nouveau, nvidia

I will now check it with a different machine, another nvidia-card.

Offline

#25 2012-02-21 21:04:53

michaelbischof
Member
Registered: 2012-01-20
Posts: 536

Re: nvidia compiling failed

Hi,

now I used this tazpkg-package with a GeForce 7100 GS on another machine. Installation was ok.

But it failed with the following message in /var7log/messages:

Feb 21 20:50:39 (none) user.warn kernel: nvidia: module license 'NVIDIA' taints kernel.

Feb 21 20:50:39 (none) daemon.err udevd[3380]: error: runtime directory '/run/udev' not writable, for now falling back to '/dev/.udev'

Feb 21 20:50:39 (none) daemon.err udevd[3380]: bind failed: Address already in use

Feb 21 20:50:39 (none) daemon.err udevd[3380]: error binding udev control socket

Feb 21 20:50:39 (none) daemon.err udevd[3381]: error: runtime directory '/run/udev' not writable, for now falling back to '/dev/.udev'

Feb 21 20:50:39 (none) daemon.err udevd[3381]: bind failed: Address already in use

Feb 21 20:50:39 (none) daemon.err udevd[3381]: error binding udev control socket

Feb 21 20:50:39 (none) user.warn kernel: Disabling lock debugging due to kernel taint

Feb 21 20:50:39 (none) user.warn kernel: ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18

Feb 21 20:50:39 (none) user.info kernel: nvidia 0000:05:00.0: PCI INT A -> Link[APC3] -> GSI 18 (level, low) -> IRQ 18

Feb 21 20:50:39 (none) user.debug kernel: nvidia 0000:05:00.0: setting latency timer to 64

Feb 21 20:50:39 (none) user.info kernel: vgaarb: device changed decodes: PCI:0000:05:00.0,olddecodes=io+mem,decodes=none:owns=io+mem

Feb 21 20:50:39 (none) user.warn kernel: NVRM: loading NVIDIA UNIX x86 Kernel Module  173.14.31  Sun Jul 17 22:11:28 PDT 2011

Feb 21 20:51:20 (none) user.debug kernel: mtrr: no MTRR for c0000000,8000000 found

Feb 21 20:51:26 (none) auth.info login[2070]: root login on 'tty1'

Feb 21 20:51:36 (none) user.info kernel: slim[3403]: segfault at a ip b72b31bb sp bfc65260 error 4 in libxcb.so.1.1.0[b72ac000+15000]

Feb 21 20:54:56 (none) user.info kernel: nvidia 0000:05:00.0: PCI INT A disabled

Feb 21 20:54:56 (none) daemon.err udevd[3456]: error: runtime directory '/run/udev' not writable, for now falling back to '/dev/.udev'

Feb 21 20:54:56 (none) daemon.err udevd[3456]: bind failed: Address already in use

Feb 21 20:54:56 (none) daemon.err udevd[3456]: error binding udev control socket

Feb 21 20:54:56 (none) daemon.err udevd[3457]: error: runtime directory '/run/udev' not writable, for now falling back to '/dev/.udev'

Feb 21 20:54:56 (none) daemon.err udevd[3457]: bind failed: Address already in use

Feb 21 20:54:56 (none) daemon.err udevd[3457]: error binding udev control socket

Feb 21 20:55:30 (none) auth.info login[2072]: root login on 'tty3'

Feb 21 20:55:36 (none) user.info kernel: nvidia 0000:05:00.0: PCI INT A -> Link[APC3] -> GSI 18 (level, low) -> IRQ 18

Feb 21 20:55:36 (none) user.debug kernel: nvidia 0000:05:00.0: setting latency timer to 64

Feb 21 20:55:36 (none) user.info kernel: vgaarb: device changed decodes: PCI:0000:05:00.0,olddecodes=none,decodes=none:owns=io+mem

Feb 21 20:55:36 (none) daemon.err udevd[3515]: error: runtime directory '/run/udev' not writable, for now falling back to '/dev/.udev'

Feb 21 20:55:36 (none) daemon.err udevd[3515]: bind failed: Address already in use

Feb 21 20:55:36 (none) daemon.err udevd[3515]: error binding udev control socket

Feb 21 20:55:36 (none) daemon.err udevd[3516]: error: runtime directory '/run/udev' not writable, for now falling back to '/dev/.udev'

Feb 21 20:55:36 (none) daemon.err udevd[3516]: bind failed: Address already in use

Feb 21 20:55:36 (none) daemon.err udevd[3516]: error binding udev control socket

Feb 21 20:55:36 (none) user.warn kernel: NVRM: loading NVIDIA UNIX x86 Kernel Module  173.14.31  Sun Jul 17 22:11:28 PDT 2011

root@slitaz:~# lsmod | grep nvidia

nvidia               7024955  0

agpgart                18221  3 nvidia,ttm,drm

i2c_core               12192  5 nvidia,nouveau,drm_kms_helper,drm,i2c_algo_bit

root@slitaz:~# lsmod | grep nouveau

nouveau               413731  0

ttm                    35361  1 nouveau

drm_kms_helper         18798  1 nouveau

drm                   111992  3 nouveau,ttm,drm_kms_helper

i2c_algo_bit            3479  1 nouveau

i2c_core               12192  5 nvidia,nouveau,drm_kms_helper,drm,i2c_algo_bit

video                   9783  1 nouveau

button                  3602  1 nouveau

Anything useful for you, mojo?

Aha, one error message on the black screen:

segfault at a ip b72b31bbbb sp bfc65260

error 4 in libxcb.s.1.1   0[b72ac0000+15000]

Offline

Registered users online in this topic: 0, guests: 1
[Bot] ClaudeBot

Board footer

Powered by FluxBB
Modified by Visman

[ Generated in 0.015 seconds, 7 queries executed - Memory usage: 1.63 MiB (Peak: 1.77 MiB) ]