Re: Update to Sid, and cannot compile Nvidia module; PIC mode?

[Will]

Hey Dirk.  Thank you!  That worked, it compiles!  And I don't have to get
my hands dirty with a patch. :)

On Fri, Oct 28, 2016 at 9:11 PM, Dirk Laebisch  wrote:

> > Anyone else run into this on Sid very recently?  Any hints or pointers?
>
> Yup.
> Providing some compile flags in:
> /usr/src/linux/Makefile
> around line 614 fixed it for me.
>
>  614 # force no-pie for distro compilers that enable pie by default
>  615 KBUILD_CFLAGS += $(call cc-option, -fno-pie)
>  616 KBUILD_CFLAGS += $(call cc-option, -no-pie)
>  617 KBUILD_AFLAGS += $(call cc-option, -fno-pie)
>  618 KBUILD_CPPFLAGS += $(call cc-option, -fno-pie)
>
> After that, dkms succeeded and no further problems ... so far.
>
> Regards
> Dirk
>
>

Re: Update to Sid, and cannot compile Nvidia module; PIC mode?

[Jimmy Johnson]

On 10/28/2016 08:11 PM, Dirk Laebisch wrote:

Anyone else run into this on Sid very recently?  Any hints or pointers?


Yup.
Providing some compile flags in:
/usr/src/linux/Makefile
around line 614 fixed it for me.

 614 # force no-pie for distro compilers that enable pie by default
 615 KBUILD_CFLAGS += $(call cc-option, -fno-pie)
 616 KBUILD_CFLAGS += $(call cc-option, -no-pie)
 617 KBUILD_AFLAGS += $(call cc-option, -fno-pie)
 618 KBUILD_CPPFLAGS += $(call cc-option, -fno-pie)

After that, dkms succeeded and no further problems ... so far.

Regards
Dirk


Hi Dirk, what driver is that?  I have eight systems here using 304 and 
I'm having to use the Debian packages and then downgrade to 
jessie-backports works for me because the package from Nvidia would not 
install the module.


Maybe you can give a step by step?

Thanks for the info,
--
Jimmy Johnson

Debian Sid/Testing - KDE Plasma Version 5.8.2 - EXT4 at sda15
Registered Linux User #380263

Re: Update to Sid, and cannot compile Nvidia module; PIC mode?

[Dirk Laebisch]

> Anyone else run into this on Sid very recently?  Any hints or pointers?

Yup. 
Providing some compile flags in:
/usr/src/linux/Makefile 
around line 614 fixed it for me.

 614 # force no-pie for distro compilers that enable pie by default
 615 KBUILD_CFLAGS += $(call cc-option, -fno-pie)
 616 KBUILD_CFLAGS += $(call cc-option, -no-pie)
 617 KBUILD_AFLAGS += $(call cc-option, -fno-pie)
 618 KBUILD_CPPFLAGS += $(call cc-option, -fno-pie)

After that, dkms succeeded and no further problems ... so far.

Regards
Dirk

Re: Update to Sid, and cannot compile Nvidia module; PIC mode?

[Jörg-Volker Peetz]

Will wrote on 10/28/16 17:21:
> Greetings,
> 
> I usually have to run the NVIDIA installer after a kernel update, but
> something has changed that has broken the process to build the
> proprietary Nvidia kernel module.  I've searched around a bit on the
> Intarwebs before coming to the list, so here goes.
> 
> 
> Installer: NVIDIA-Linux-x86_64-367.44.run
> 
> If I simply run the installer, if fails with this message:
> 
> ERROR: Failed to run `/usr/sbin/dkms build -m nvidia -v 367.44 -k
> 4.7.0-1-amd64`:
>  Kernel preparation unnecessary for this kernel.  Skipping...
> 
>  Building module:
>  cleaning build area...
>  'make' -j8 NV_EXCLUDE_BUILD_MODULES=''
> KERNEL_UNAME=4.7.0-1-amd64 modules(bad exit status: 2)
>  Error! Bad return status for module build on kernel:
> 4.7.0-1-amd64 (x86_64)
>  Consult /var/lib/dkms/nvidia/367.44/build/make.log for more
> information.
> 
> And, the output of /var/lib/dkms/nvidia/367.44/build/make.log:
> 
>   CC [M]  /var/lib/dkms/nvidia/367.44/build/nvidia/nv-instance.o
> /var/lib/dkms/nvidia/367.44/build/nvidia/nv-frontend.c:1:0: error: code
> model kernel does not support PIC mode

This is due to the last hardening changes in gcc-6 after 6.2.0-7 see bug reports
#841368, #841500, and #841533.
There's also given workarounds. See message #51 in #841368 and #52 in #841500.

Regards,
jvp.

Update to Sid, and cannot compile Nvidia module; PIC mode?

[Will]

Greetings,

I usually have to run the NVIDIA installer after a kernel update, but
something has changed that has broken the process to build the
proprietary Nvidia kernel module.  I've searched around a bit on the
Intarwebs before coming to the list, so here goes.


Installer: NVIDIA-Linux-x86_64-367.44.run

If I simply run the installer, if fails with this message:

ERROR: Failed to run `/usr/sbin/dkms build -m nvidia -v 367.44 -k
4.7.0-1-amd64`:
 Kernel preparation unnecessary for this kernel.  Skipping...

 Building module:
 cleaning build area...
 'make' -j8 NV_EXCLUDE_BUILD_MODULES=''
KERNEL_UNAME=4.7.0-1-amd64 modules(bad exit status: 2)
 Error! Bad return status for module build on kernel:
4.7.0-1-amd64 (x86_64)
 Consult /var/lib/dkms/nvidia/367.44/build/make.log for more
information.

And, the output of /var/lib/dkms/nvidia/367.44/build/make.log:

  CC [M]  /var/lib/dkms/nvidia/367.44/build/nvidia/nv-instance.o
/var/lib/dkms/nvidia/367.44/build/nvidia/nv-frontend.c:1:0: error: code
model kernel does not support PIC mode
 /* _NVRM_COPYRIGHT_BEGIN_

  CC [M]  /var/lib/dkms/nvidia/367.44/build/nvidia/nv.o
/usr/src/linux-headers-4.7.0-1-common/scripts/Makefile.build:294: recipe
for target '/var/lib/dkms/nvidia/367.44/build/nvidia/nv-frontend.o' failed
make[3]: *** [/var/lib/dkms/nvidia/367.44/build/nvidia/nv-frontend.o]
Error 1
make[3]: *** Waiting for unfinished jobs
/var/lib/dkms/nvidia/367.44/build/nvidia/nv.c:1:0: error: code model
kernel does not support PIC mode
 /* _NVRM_COPYRIGHT_BEGIN_


Searching on "error: code model kernel does not support PIC mode" yields
a few pages that are interesting, such as:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1574838

and
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574982?comments/19

>From Comment #19, if I add this to the Kbuild file included with the
Nvidia installer, it might compile:

EXTRA_CFLAGS += -fno-pie -fno-stack-protector

So, I unpack the Nvidia installer:
./NVIDIA-Linux-x86_64-367.44.run -x

Change directory into the installer directory, and modify the Kbuild file:
cd NVIDIA-Linux-x86_64-367.44/kernel

Modify the Kbuild file (line 59), with:
EXTRA_CFLAGS += -fno-pie -fno-stack-protector

Run the nvidia-installer from the extracted directory:
cd NVIDIA-Linux-x86_64-367.44 ; ./nvidia-installer

And I get this message:
ERROR: Unable to load the 'nvidia-drm' kernel module.

And from the log file, /var/log/nvidia-installer.log:

creation time: Thu Oct 27 16:29:35 2016
installer version: 367.44

PATH: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

nvidia-installer command line:
./nvidia-installer

Unable to load: nvidia-installer ncurses v6 user interface

Using: nvidia-installer ncurses user interface
-> Detected 8 CPUs online; setting concurrency level to 8.
-> License accepted.
-> Installing NVIDIA driver version 367.44.
-> There appears to already be a driver installed on your system
(version: 367.44).  As part of installing this driver (version: 367.44),
the existing driver will be uninstalled.  Are you sure you want to
continue? (Answer: Continue installation)
-> Would you like to register the kernel module sources with DKMS? This
will allow DKMS to automatically build a new module, if you install a
different kernel later. (Answer: Yes)
-> Installing both new and classic TLS OpenGL libraries.
-> Installing both new and classic TLS 32bit OpenGL libraries.
-> Install NVIDIA's 32-bit compatibility libraries? (Answer: Yes)
-> Will install GLVND GLX client libraries.
-> Uninstalling the previous installation with /usr/bin/nvidia-uninstall.
Looking for install checker script at
./libglvnd_install_checker/check-libglvnd-install.sh
   executing: '/bin/sh
./libglvnd_install_checker/check-libglvnd-install.sh'...
   Checking for libglvnd installation.
   Checking libGLdispatch...
   Can't load library libGLdispatch.so.0: libGLdispatch.so.0: cannot
open shared object file: No such file or directory
Will install libglvnd libraries.
-> Searching for conflicting files:
-> done.
-> Installing 'NVIDIA Accelerated Graphics Driver for Linux-x86_64'
(367.44):
   executing: '/sbin/ldconfig'...
-> done.
-> Driver file installation is complete.
-> Installing DKMS kernel module:
-> done.
ERROR: Unable to load the 'nvidia-drm' kernel module.
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.


Anyone else run into this on Sid very recently?  Any hints or pointers?

Thanks in advance,
Will

Re: nvidia module

[Ralf Mardorf]

On Wed, 2013-07-10 at 14:58 +1200, Chris Bannister wrote:
 On Tue, Jul 09, 2013 at 05:03:40PM +0100, Brad Rogers wrote:
  From the package description of dkms (Dynamic Kernel Module Support
  Framework);
 
 Then why isn't it dkmsf?

Why is it

mkdir

and not

md

or

mdir

resp. why isn't

mdir

more precise, e.g.

msdir

instead ?




-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1373443981.1271.23.camel@archlinux

Re: nvidia module

[Brad Rogers]

On Wed, 10 Jul 2013 14:58:03 +1200
Chris Bannister cbannis...@slingshot.co.nz wrote:

Hello Chris,

On Tue, Jul 09, 2013 at 05:03:40PM +0100, Brad Rogers wrote:
 From the package description of dkms (Dynamic Kernel Module Support
 Framework);
Then why isn't it dkmsf?

:-)

-- 
 Regards  _
 / )   The blindingly obvious is
/ _)radnever immediately apparent
Black man got a lot of problems, but he don't mind throwing a brick
White Riot - The Clash


signature.asc
Description: PGP signature

Re: nvidia module

[Chris Bannister]

On Wed, Jul 10, 2013 at 10:13:01AM +0200, Ralf Mardorf wrote:
 On Wed, 2013-07-10 at 14:58 +1200, Chris Bannister wrote:
  On Tue, Jul 09, 2013 at 05:03:40PM +0100, Brad Rogers wrote:
   From the package description of dkms (Dynamic Kernel Module Support
   Framework);
  
  Then why isn't it dkmsf?
 
 Why is it
 
 mkdir
 

dkms != (Dynamic Kernel Module Support Framework)

mkdir is NOT an acronym!

-- 
If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the 
oppressing. --- Malcolm X


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130710123119.GB32113@tal

Re: nvidia module

[andrey . rybak]

 Really?  I've always needed an xorg.conf file to allow the use of the
 nVidia driver.

Yes man! its true. For example, if i reload system to my old kernel -
everything is ok. And i have not any xorg.conf.
i should do rectification. I am talking about system on notebook with
intel and nvidia videocards. For running applications on nvidia card i use
optiran command from shell.
 As for stopping working after upgrade, you are aware that the nVidia
 module needs to be recompiled after a kernel update?  It's why I use the
 *-dkms nvidia kernel modules, as that way, it's all taken care of for
 you.
Could you explain me this more particullary?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/8c8139c0e136b1b385b369c4337515ea.squir...@newmail.bilkent.edu.tr

Re: nvidia module

[Brad Rogers]

On Tue, 9 Jul 2013 16:49:04 +0300
andrey.ry...@bilkent.edu.tr wrote:

Hello andrey.ry...@bilkent.edu.tr,

 Really?  I've always needed an xorg.conf file to allow the use of the
 nVidia driver.
Yes man! its true. For example, if i reload system to my old kernel -
everything is ok. And i have not any xorg.conf.

That's contrary to everything I've ever heard about running the nvidia
module.  If you say you haven't got an xorg.conf I have to believe you.

 the *-dkms nvidia kernel modules, as that way, it's all taken care of
 for you.
Could you explain me this more particullary?

From the package description of dkms (Dynamic Kernel Module Support
Framework);
DKMS is a framework designed to allow individual kernel modules to be
upgraded without changing the whole kernel. It is also very easy to
rebuild modules as you upgrade kernels.

The upgrade for kernel 3.2.* to 3.9.* broke the nvidia module, which has
to be recompiled at every kernel upgrade.  Installing nvidia-kernel-dkms
brings in nearly everything you need to ensure that the nvidia kernel
module is automatically upgraded every time the kernel changes.  I say
nearly everything because it doesn't pull in the
linux-headers-nnn package(1) which is needed to do the job.  With those
packages installed, any relevant updates will automatically recompile
the module(s) that would break.

(1) Where nnn represents your processor type.  In my case amd64.

-- 
 Regards  _
 / )   The blindingly obvious is
/ _)radnever immediately apparent
He signed up for just three years, it seemed a small amount
Tin Soldiers - Stiff Little Fingers


signature.asc
Description: PGP signature

Re: nvidia module

[Ralf Mardorf]

On Tue, 09 Jul 2013 18:03:40 +0200, Brad Rogers b...@fineby.me.uk wrote:

From the package description of dkms (Dynamic Kernel Module Support
Framework);
DKMS is a framework designed to allow individual kernel modules to be
upgraded without changing the whole kernel. It is also very easy to
rebuild modules as you upgrade kernels.

The upgrade for kernel 3.2.* to 3.9.* broke the nvidia module, which has
to be recompiled at every kernel upgrade.  Installing nvidia-kernel-dkms
brings in nearly everything you need to ensure that the nvidia kernel
module is automatically upgraded every time the kernel changes.  I say
nearly everything because it doesn't pull in the
linux-headers-nnn package(1) which is needed to do the job.  With those
packages installed, any relevant updates will automatically recompile
the module(s) that would break.

(1) Where nnn represents your processor type.  In my case amd64.


It's always smart to load headers first ;).

FWIW dkms can be run manually too, e.g. for VBox on Arch:

dkms install vboxhost/virtualbox-host-source version -k your custom  
kernel's version/your architecture

- https://wiki.archlinux.org/index.php/VirtualBox

I do the same automated by a mkinitcpio hook. This should work  
equal/similar for nvidia on Debian.




--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/op.wzyv8xgiqhadp0@suse11-2

Re: nvidia module

[Chris Bannister]

On Tue, Jul 09, 2013 at 05:03:40PM +0100, Brad Rogers wrote:
 From the package description of dkms (Dynamic Kernel Module Support
 Framework);

Then why isn't it dkmsf?

-- 
If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the 
oppressing. --- Malcolm X


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130710025803.GA22985@tal

Re: nvidia module

[Brad Rogers]

On Sun, 7 Jul 2013 22:01:06 +0300
andrey.ry...@bilkent.edu.tr wrote:

Hello andrey.ry...@bilkent.edu.tr,

i have jessy. why modprobe cannot find nvidia_drv.so? when i used
wheezy i didnot need the xorg.conf. it stopped to work after upgrading.

Really?  I've always needed an xorg.conf file to allow the use of the
nVidia driver.

As for stopping working after upgrade, you are aware that the nVidia
module needs to be recompiled after a kernel update?  It's why I use the
*-dkms nvidia kernel modules, as that way, it's all taken care of for
you.

-- 
 Regards  _
 / )   The blindingly obvious is
/ _)radnever immediately apparent
If you ain't sticking your knives in me, you will be eventually
Monsoon - Robbie Williams


signature.asc
Description: PGP signature

Re: nvidia module

[Lotek]

On 07/07/2013 12:01 PM, andrey.ry...@bilkent.edu.tr wrote:

i have jessy. why modprobe cannot find nvidia_drv.so? when i used wheezy i
didnot need the xorg.conf. it stopped to work after upgrading. There was
no problem when i had upgraded from wheeze to jessy. But when kernel
version was changed to 3.9 the problem was occuring. What can be broken?


I had the same problem when I upgraded to testing, because for some 
reason the nvidia kernel module wasn't upgraded.  So try installing 
nvidia-kernel-3.9-1-686-pae.  (The old xorg.conf file also worked, so if 
you didn't need one with wheezy you might not need one now.)


  Lotek



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/51db0d9e.70...@verizon.net

nvidia module

[andrey . rybak]

hi!
if i do command:
# modprobe nvidia
i retrieve next message:

FATAL: Module nvidia not found.

but i have many nvidia-* packages installed
and between them:

ii  nvidia-kernel-common  20130505+1  
 i386 NVIDIA binary kernel module support files
ii  nvidia-kernel-dkms304.88-3
 i386 NVIDIA binary kernel module DKMS source
ii  nvidia-kernel-source  304.88-3
 i386 NVIDIA binary kernel module source

What should i check to diagnose this problem?
thanks for any suggestions.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/0954ead5c72422e7a36a70c9406d4f7f.squir...@newmail.bilkent.edu.tr

Re: nvidia module

[Ralf Mardorf]

On Sun, 2013-07-07 at 17:19 +0300, andrey.ry...@bilkent.edu.tr wrote:
 hi!
 if i do command:
 # modprobe nvidia
 i retrieve next message:
 
 FATAL: Module nvidia not found.
 
 but i have many nvidia-* packages installed
 and between them:
 
 ii  nvidia-kernel-common  20130505+1  
  i386 NVIDIA binary kernel module support files
 ii  nvidia-kernel-dkms304.88-3
  i386 NVIDIA binary kernel module DKMS source
 ii  nvidia-kernel-source  304.88-3
  i386 NVIDIA binary kernel module source
 
 What should i check to diagnose this problem?
 thanks for any suggestions.

For what Debian release, resp. from what repository?

The module might be somewhere in /lib/modules/$(uname -r)/ .

Have you run DKMS manually?

Any messages?

$ grep EE /var/log/Xorg.0.log
$ grep module /var/log/Xorg.0.log
$ cat /var/log/Xorg.0.log

Any info about the files provided?

dpkg -L nvidia-kernel-common

Hth,

Ralf






-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1373210927.3039.9.camel@archlinux

Re: nvidia module

[andrey . rybak]

 For what Debian release, resp. from what repository?
#lsb_release -a

Release:testing
Codename:   jessie

# uname -a
Linux hostname 3.9-1-686-pae #1 SMP Debian 3.9.6-1 i686 GNU/Linux

 The module might be somewhere in /lib/modules/$(uname -r)/ .

#ls /lib/modules/$(uname -r)/
build  modules.builtin  modules.devname  modules.symbols.bin
kernel modules.builtin.bin  modules.ordersource
modules.alias  modules.dep  modules.softdep  updates
modules.alias.bin  modules.dep.bin  modules.symbols

 Have you run DKMS manually?
How i can do it?

 Any messages?

 $ grep EE /var/log/Xorg.0.log
clean
 $ grep module /var/log/Xorg.0.log
[25.753] (==) ModulePath set to /usr/lib/xorg/modules
[25.946] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[26.060]compiled for 1.12.4, module version = 1.0.0
[26.060] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[26.099]compiled for 1.12.4, module version = 1.0.0
[26.099] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[26.113]compiled for 1.12.4, module version = 1.0.0
[26.114] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[26.124]compiled for 1.12.4, module version = 1.13.0
[26.124] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[26.139]compiled for 1.12.4, module version = 1.0.0
[26.140] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[26.188]compiled for 1.12.4, module version = 1.2.0
[26.293] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[26.331]compiled for 1.12.3.902, module version = 2.19.0
[26.331] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[26.396]compiled for 1.12.1, module version = 2.3.1
[26.396] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[26.427]compiled for 1.12.1, module version = 0.4.2
[26.435] (II) Loading sub module fbdevhw
[26.435] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[26.449]compiled for 1.12.4, module version = 0.0.2
[26.499] (II) Loading sub module fb
[26.499] (II) Loading /usr/lib/xorg/modules/libfb.so
[26.516]compiled for 1.12.4, module version = 1.0.0
[26.516] (II) Loading sub module dri2
[26.516] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[26.516]compiled for 1.12.4, module version = 1.2.0
[28.821] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[28.832]compiled for 1.12.1, module version = 2.7.0
[28.840] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[28.937]compiled for 1.12.4, module version = 1.6.2

 $ cat /var/log/Xorg.0.log
very long output

 Any info about the files provided?

 dpkg -L nvidia-kernel-common
/.
/etc
/etc/init.d
/etc/init.d/nvidia-kernel
/etc/modprobe.d
/etc/modprobe.d/nvidia-kernel-common.conf
/etc/default
/etc/default/nvidia-kernel
/usr
/usr/lib
/usr/lib/ConsoleKit
/usr/lib/ConsoleKit/run-seat.d
/usr/lib/ConsoleKit/run-seat.d/nvidia_helper.ck
/usr/share
/usr/share/doc
/usr/share/doc/nvidia-kernel-common
/usr/share/doc/nvidia-kernel-common/copyright
/usr/share/doc/nvidia-kernel-common/README.Debian
/usr/share/doc/nvidia-kernel-common/changelog.gz
/lib
/lib/udev
/lib/udev/rules.d
/lib/udev/rules.d/60-nvidia-kernel-common.rules
/lib/udev/nvidia_helper





-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/fa51b4e0b767288bc6e643b578afc67c.squir...@newmail.bilkent.edu.tr

Re: nvidia module

[Patrick Bartek]

On Sun, 07 Jul 2013, andrey.ry...@bilkent.edu.tr wrote:

 hi!
 if i do command:
 # modprobe nvidia
 i retrieve next message:
 
 FATAL: Module nvidia not found.
 
 but i have many nvidia-* packages installed
 and between them:
 
 ii  nvidia-kernel-common
 20130505+1 i386 NVIDIA binary kernel module support files
 ii  nvidia-kernel-dkms
 304.88-3 i386 NVIDIA binary kernel module DKMS source
 ii  nvidia-kernel-source
 304.88-3 i386 NVIDIA binary kernel module source
 
 What should i check to diagnose this problem?
 thanks for any suggestions.

Check to see if you have a symbolic link nvidia
in /usr/lib/nvidia which eventually points
to /usr/lib/nvidia/current/nvidia_drv.so

And if you're trying to install the nvidia graphics driver, modprobe
isn't the way to do it, at least, on Wheezy.  You need to create an
xorg.conf file in /etc/X11 and blacklist the default driver, most
likely nouveau, in /etc/modprobe.d, then reboot.  Google for the
specific instructions.

B


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130707101242.078bb...@debian7.boseck208.net

Re: nvidia module

[andrey . rybak]

 Check to see if you have a symbolic link nvidia
 in /usr/lib/nvidia which eventually points
 to /usr/lib/nvidia/current/nvidia_drv.so
yes i have:

/usr/lib/nvidia/nvidia: symbolic link to `/etc/alternatives/nvidia'
/etc/alternatives/nvidia: symbolic link to `/usr/lib/nvidia/current'
# file /usr/lib/nvidia/current
/usr/lib/nvidia/current: directory
# ls /usr/lib/nvidia/current
libglx.so nv-control-dpynvidia_drv.so  nvidia-settings  
nvidia-settings.desktop
libglx.so.304.88  nvidia-bug-report.sh  nvidia.ids nvidia-settings.1.gz


 And if you're trying to install the nvidia graphics driver, modprobe
 isn't the way to do it, at least, on Wheezy.  You need to create an
 xorg.conf file in /etc/X11 and blacklist the default driver, most
 likely nouveau, in /etc/modprobe.d, then reboot.  Google for the
 specific instructions.

i have jessy. why modprobe cannot find nvidia_drv.so? when i used wheezy i
didnot need the xorg.conf. it stopped to work after upgrading. There was
no problem when i had upgraded from wheeze to jessy. But when kernel
version was changed to 3.9 the problem was occuring. What can be broken?



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/847472d8c7cb34b54ef87267d0471391.squir...@newmail.bilkent.edu.tr

Re: nvidia module

[Patrick Bartek]

On Sun, 07 Jul 2013, andrey.ry...@bilkent.edu.tr wrote:

 
  Check to see if you have a symbolic link nvidia
  in /usr/lib/nvidia which eventually points
  to /usr/lib/nvidia/current/nvidia_drv.so
 yes i have:
 
 /usr/lib/nvidia/nvidia: symbolic link to `/etc/alternatives/nvidia'
 /etc/alternatives/nvidia: symbolic link to `/usr/lib/nvidia/current'
 # file /usr/lib/nvidia/current
 /usr/lib/nvidia/current: directory
 # ls /usr/lib/nvidia/current
 libglx.so   nv-control-dpynvidia_drv.so
 nvidia-settings nvidia-settings.desktop
 libglx.so.304.88  nvidia-bug-report.shnvidia.ids
 nvidia-settings.1.gz
 
 
  And if you're trying to install the nvidia graphics driver, modprobe
  isn't the way to do it, at least, on Wheezy.  You need to create an
  xorg.conf file in /etc/X11 and blacklist the default driver, most
  likely nouveau, in /etc/modprobe.d, then reboot.  Google for the
  specific instructions.
 
 i have jessy. why modprobe cannot find nvidia_drv.so? when i used

modprobe only looks /lib/modules/kernelname for loadable modules.
Try using the full path to the nvidia driver.  However, you'll still
need to be sure the default driver isn't loaded at boot time.

 wheezy i didnot need the xorg.conf. it stopped to work after
 upgrading. There was no problem when i had upgraded from wheeze to
 jessy. But when kernel version was changed to 3.9 the problem was
 occuring. What can be broken?

Why don't you try creating an xorg.conf and blacklisting the default
graphic driver.  This is the accepted way according to nVidia to
enable its driver in Wheezy.  Won't hurt to try it for Jessie.

Here's my /etc/X11/xorg.conf

==

# minimal xorg.conf for prop. nvidia driver

Section Device
Identifier  EVGA GeForce 8400GS
Driver  nvidia
EndSection

==


Here's my /etc/modprobe.d/nvidia-common-kernel.conf

==

alias char-major-195* nvidia
options nvidia NVreg_DeviceFileUID=0 NVreg_DeviceFileGID=44 
NVreg_DeviceFileMode=0660
# To enable FastWrites and Sidebus addressing, uncomment these lines
# options nvidia NVreg_EnableAGPSBA=1
# options nvidia NVreg_EnableAGPFW=1

# see #580894
blacklist nouveau




B


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130707212717.4dfa7...@debian7.boseck208.net

Re: X can't find nvidia module

[Hugo Vanwoerkom]

Vincent Lefevre wrote:

On 2012-11-13 15:51:11 -0600, Hugo Vanwoerkom wrote:

But when I startx, X can't find the nvidia module:

...
(EE) Failed to load module nvidia (module does not exist, 0)
...

Any suggestions as to what to do next?


You probably need xserver-xorg-video-nvidia (as in addition to the
NVIDIA kernel driver, you need the NVIDIA Xorg driver). But when I
was using the NVIDIA drivers in the past, I installed nvidia-glx,
which depends on xserver-xorg-video-nvidia and other useful packages.



Thanks Vincent, let me try that. I usually use the closed source NVidia 
driver from upstream, this is the first time that I have tried building 
the driver myself.


Hugo


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/k806nh$5d6$1...@ger.gmane.org

Re: X can't find nvidia module

[Hugo Vanwoerkom]

Hugo Vanwoerkom wrote:

Vincent Lefevre wrote:

On 2012-11-13 15:51:11 -0600, Hugo Vanwoerkom wrote:

But when I startx, X can't find the nvidia module:

...
(EE) Failed to load module nvidia (module does not exist, 0)
...

Any suggestions as to what to do next?


You probably need xserver-xorg-video-nvidia (as in addition to the
NVIDIA kernel driver, you need the NVIDIA Xorg driver). But when I
was using the NVIDIA drivers in the past, I installed nvidia-glx,
which depends on xserver-xorg-video-nvidia and other useful packages.



Thanks Vincent, let me try that. I usually use the closed source NVidia 
driver from upstream, this is the first time that I have tried building 
the driver myself.




That was it. I installed nvidia-glx and that pulled in 
xserver-xorg-video-nvidia and now X comes up. Thanks again.


Hugo


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/k808j4$o2q$1...@ger.gmane.org

X can't find nvidia module

[Hugo Vanwoerkom]

Hi,

I installed the nvidia driver following:

http://wiki.debian.org/NvidiaGraphicsDrivers#Build_manually.2C_with_a_custom_kernel

and using nvidia-kernel-source (304.48-1) with this:

make-kpkg --revision 3.5.4 --append-to-version -nodeb-amd64 
--added-modules nvidia-kernel \

--initrd kernel_image modules_image

That gave me 2 .debs:

linux-image-3.5.4-nodeb-amd64_3.5.4_amd64.deb
nvidia-kernel-3.5.4-nodeb-amd64_304.48-1+3.5.4_amd64.deb

which I installed + booted that kernel.
Syslog shows:

...
NVRM: loading NVIDIA UNIX x86_64 Kernel Module  304.48  Sun Sep  9 
20:22:27 PDT 2012

...

and lsmod shows:

...
nvidia  11186000  0
...

But when I startx, X can't find the nvidia module:

...
(EE) Failed to load module nvidia (module does not exist, 0)
...

Any suggestions as to what to do next?

Hugo


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/k7ufcc$o7k$1...@ger.gmane.org

Re: X can't find nvidia module

[Vincent Lefevre]

On 2012-11-13 15:51:11 -0600, Hugo Vanwoerkom wrote:
 But when I startx, X can't find the nvidia module:
 
 ...
 (EE) Failed to load module nvidia (module does not exist, 0)
 ...
 
 Any suggestions as to what to do next?

You probably need xserver-xorg-video-nvidia (as in addition to the
NVIDIA kernel driver, you need the NVIDIA Xorg driver). But when I
was using the NVIDIA drivers in the past, I installed nvidia-glx,
which depends on xserver-xorg-video-nvidia and other useful packages.

HTH,

-- 
Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/
100% accessible validated (X)HTML - Blog: http://www.vinc17.net/blog/
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20121114013703.gb1...@xvii.vinc17.org

Re: Nvidia module makes system unstable

[Indulekha]

Sean Whalen whalens...@gmail.com wrote:
 Hello All,

 I recently made the switch from Kubuntu 11.10 to Debain stable.
 Everything was running very well until I installed the Nvidia module
 the Debian way.  Then, the system became highly unstable. I noticed
 that the system would become very sluggish during simple tasks The
 most repeatable example of this is the slow rate at which the
 background fades when calling gksu. Additionally, there is a visible
 lag in the redrawing of windows when applications are minimized or
 restored. interestingly, video from YouTube seemed to be fluid.

 The situation was annoying, but not unbearable, until the entire
 system began to freeze. It seems that this may be related in some way
 to bug #664261. My situation differs in that I used the version from
 backports (280.13.really.275.36-1) in order to achieve compatibility
 with my GeForce GTX 560 Ti FPB (Fermi) GPU, it's worth noting that it
 did not experience any stability issues with the Ubuntu distribution
 of the Nvidia module 280.13 when I used Kubuntu 11.10.

 What should I do at this point? I'm tempted use the Nvidia installer,
 but I'm concerned that it might unnecessarily dirty my system. Is it
 possible to cleanly switch from the Nvidia installer to the Debian
 way?

 I'm also not sure whether I should report this as a separate bug, or
 as an addition to the one mentioned above. Any thoughts would be
 helpful.


The nouveau driver is working well on my machine, maybe you'll 
do better to use it too.

-- 
❤ ♫ ❤ ♫ ❤ ♫ ❤   
 Indulekha 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120416075529.GA11928@radhesyama

Nvidia module makes system unstable

[Sean Whalen]

Hello All,

I recently made the switch from Kubuntu 11.10 to Debain stable.
Everything was running very well until I installed the Nvidia module
the Debian way.  Then, the system became highly unstable. I noticed
that the system would become very sluggish during simple tasks The
most repeatable example of this is the slow rate at which the
background fades when calling gksu. Additionally, there is a visible
lag in the redrawing of windows when applications are minimized or
restored. interestingly, video from YouTube seemed to be fluid.

The situation was annoying, but not unbearable, until the entire
system began to freeze. It seems that this may be related in some way
to bug #664261. My situation differs in that I used the version from
backports (280.13.really.275.36-1) in order to achieve compatibility
with my GeForce GTX 560 Ti FPB (Fermi) GPU, it's worth noting that it
did not experience any stability issues with the Ubuntu distribution
of the Nvidia module 280.13 when I used Kubuntu 11.10.

What should I do at this point? I'm tempted use the Nvidia installer,
but I'm concerned that it might unnecessarily dirty my system. Is it
possible to cleanly switch from the Nvidia installer to the Debian
way?

I'm also not sure whether I should report this as a separate bug, or
as an addition to the one mentioned above. Any thoughts would be
helpful.

Thanks in advance,
Sean


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAHJnR_LzgUHziCm6BYLJA_9ngjs=ncs3bnwv9m-6aksnwal...@mail.gmail.com

Re: Nvidia module makes system unstable

[Eduardo Bearzoti]

Hi Sean,

For the past few days, I've been trying to install Squueze on my PC and have 
experienced very similar troubles. My card is a GeForce 8400 GS. The screen and 
the whole system freeze as soon as gdm3 starts. I installed the Nvidia module 
the Debian Way, and also (after some reluctance) used the Nvidia installer. 
For my despair nothing worked. People from this community have suggested that 
it might be a hardware-related problem, but I am not so sure. The older Debian 
release lenny worked just fine with this card (I'm using it now, while I don't 
fix the problem), perhaps due to the non-use of 3D Acceleration. I performed 
RAM tests, and no errors were reported. I also removed all the expansion 
boards, cleaned the contacts and carefully re-seated them all.

Of course my situation is a little worse than yours, because, as you said, 
everything was running well until you installed the Nvidia module. I also tried 
Ubuntu 11.10, and again the screen freezes as X server is loaded. But, again, 
I'm not convinced this is a hardware problem.

With regard to your concern about dirtying the system with Nvidia installer, I 
think it's possible to cleanly switch back to the Debian way. The major 
modifications that the installer does are:

- it adds the file /etc/modprobe.d/nvidia-installer-disable-nouveau.conf, which 
disables the nouveau module, in case you have it installed. Nvidia installer 
says that you'll (just) have to delete it to re-install nouveau.

- it edits a xorg.config file (with your permission). But you can get a new 
xorg.config file after installing the Debian way, by running:
Xorg -configure.

- it requires gcc-4.3, and the newest version available is 4.4. If you will 
need gcc-4.4, you can easily reverse the situation using apt or aptitude.

A friend of mine that has installed Debian in many PCs at his Department also 
reported troubles with Nvidia cards more than once. I'm willing to change my 
video card, because my ideas are running out and I would like to continue using 
Debian :)

I wish you luck.

Best regards,
Eduardo.


--- Em sáb, 14/4/12, Stephen Powell zlinux...@wowway.com escreveu:

 De: Stephen Powell zlinux...@wowway.com
 Assunto: Re: Trouble with Nvidia driver
 Para: debian-user@lists.debian.org
 Data: Sábado, 14 de Abril de 2012, 8:57
 On Sat, 14 Apr 2012 03:27:06 -0400


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1334552102.24169.yahoomailclas...@web112709.mail.gq1.yahoo.com

Re: nvidia module successfully installed

[Ralf Mardorf]

On Thu, 2011-11-24 at 20:32 +, Richard wrote:
 Hi
 I had to purge everything I downloaded previously, blacklist nouveau, kill X 
  gdm3, the run
 NVIDIA-Linux-x86_64-290.10.run, then reboot.
 No more shakey display and I can watch TV again without X crashing.

Good news :)

- Ralf


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1322218355.5631.36.camel@debian

Re: nvidia module successfully installed

[Hugo Vanwoerkom]

Richard wrote:

Hi
I had to purge everything I downloaded previously, blacklist nouveau, kill X  
gdm3, the run
NVIDIA-Linux-x86_64-290.10.run, then reboot.
No more shakey display and I can watch TV again without X crashing.


Good news. IMO the reboot is not necessary, just run 
NVIDIA-Linux-x86_64-290.10.run, which won't run when X is running, and 
restart gdm3.


Hugo


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/jaoitj$197$1...@dough.gmane.org

nvidia module successfully installed

[Richard]

Hi
I had to purge everything I downloaded previously, blacklist nouveau, kill X  
gdm3, the run
NVIDIA-Linux-x86_64-290.10.run, then reboot.
No more shakey display and I can watch TV again without X crashing.
-- 
Best wishes / 73
Richard Bown

e-mail: rich...@g8jvm.com   or   richard.b...@blueyonder.co.uk

nil carborundum a illegitemis
##
Ham Call G8JVM . OS Debian Wheezy/Sid amd64 on a Dual core AMD Athlon 5200, 4 
GB RAM
Maidenhead QRA: IO82SP38, LAT. 52 39.720' N LONG. 2 28.171 W ( degs mins )
QRV HF + VHF Microwave 23 cms:140W,13 cms:100W,6 cms:10W  3 cms:5W
##
 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/2024203226.134a6...@g8jvm.com

Error when loading nvidia module (was: nvidia-driver - some problems)

[Camaleón]

On Sat, 08 Oct 2011 15:10:36 +0200, Hans-J. Ullrich wrote:

 Me again!

:-)

(let me change the subject for this thread to avoid mixing with the other 
one)
 
 Now I went back to the latest nvidia driver. Building went fine (I am
 using dkms), but it inhibits to load.
 
 See the last strace output from strace modprobe nvidia:

(...)

 write(2, FATAL: Error inserting nvidia (/..., 100FATAL: Error
 inserting nvidia (/lib/modules/3.0.0-1-686-pae/updates/dkms/nvidia.ko):
 No such device ) = 100

Okay, so this is the error you said before, right?

I assume that you have followed this steps:

http://wiki.debian.org/NvidiaGraphicsDrivers#Use_DKMS

I dunno how nor what dkms does but I would first check for the basics, 
for instance, is nouveau module unloaded? Have you restared the computer 
(or at least the X server) after installing -and setting as default- the 
nvidia driver?

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2011.10.08.13.42...@gmail.com

Re: Error when loading nvidia module (was: nvidia-driver - some problems)

[Hans-J. Ullrich]

 I dunno how nor what dkms does but I would first check for the basics,
 for instance, is nouveau module unloaded? Have you restared the computer
 (or at least the X server) after installing -and setting as default- the
 nvidia driver?

DKMS is just building and installing the modulel. However, I also tried the 
long way: m-a a-i nvidia-kernel-source and installing by hand. :)

Nouveau is unloaded. Additionally it is blacklisted.

Restarting the computer did not help, too.

I set the nvidia driver as default.

 
 Greetings,

Greetz


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201110081551.30997.hans.ullr...@loop.de

Re: Error when loading nvidia module (was: nvidia-driver - some problems)

[Camaleón]

On Sat, 08 Oct 2011 15:51:30 +0200, Hans-J. Ullrich wrote:

 I dunno how nor what dkms does but I would first check for the
 basics, for instance, is nouveau module unloaded? Have you restared the
 computer (or at least the X server) after installing -and setting as
 default- the nvidia driver?
 
 DKMS is just building and installing the modulel. However, I also tried
 the long way: m-a a-i nvidia-kernel-source and installing by hand. :)
 
 Nouveau is unloaded. Additionally it is blacklisted.
 
 Restarting the computer did not help, too.
 
 I set the nvidia driver as default.

Can you upload the full Xorg log somewhere? (i.e., www.pastebin.com)

Also, consider in opening a bug report for this.

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2011.10.08.14.14...@gmail.com

Subject=Re: Re: VirtualBox 4 fails building kernel module (the same with nvidia module)

[Jonas Jensen]

I switched to custom kernel and came across this thread. I also use
squeeze and this is what I have found.

First of, Debian has the following versions of nvidia-kernel-dkms packages:

squeeze: 195.36.31-6
sid/wheezy: 260.19.44-1
experimental: 270.30-1

The version in squeeze fail on anything above kernel 2.6.38 and none
will compile on 2.6.39 because of BKL removal; nvidia-kernel-dkms
depends on it; include/linux/smp_lock.h is missing and the driver
will not compile without it.

So I settled for kernel 2.6.38.4 and nvidia-kernel-dkms from
experimental because it compiles without issue. The packages from
sid/wheezy also work but why not use the latest and greatest. Here is
what i did:

cd /usr/src

download the following packages from exerimental:

libgl1-nvidia-glx_270.30-1_amd64.deb
nvidia-glx_270.30-1_amd64.deb
nvidia-kernel-dkms_270.30-1_amd64.deb
nvidia-common_20110213+1_amd64.deb
nvidia-kernel-common_20110213+1_amd64.deb

download, untar and configure kernel 2.6.38.4.

cd linux-2.6.38.4

fakeroot make-kpkg --initrd --revision=2.6.38.4+jj
--append_to_version=+jj kernel_image; fakeroot make-kpkg --initrd
--revision=2.6.38.4+jj --append_to_version=+jj kernel_headers

dpkg -i linux-image-2.6.38.4+jj_2.6.38.4+jj_amd64.deb
linux-headers-2.6.38.4+jj_2.6.38.4+jj_amd64.deb

dpkg -i libgl1-nvidia-glx_270.30-1_amd64.deb
nvidia-glx_270.30-1_amd64.deb nvidia-kernel-dkms_270.30-1_amd64.deb
nvidia-common_20110213+1_amd64.deb
nvidia-kernel-common_20110213+1_amd64.deb

dpkg-reconfigure nvidia-kernel-dkms


Best regards,
Jonas Jensen


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/banlktinsnwkfw328pljnb7nycqs7n8x...@mail.gmail.com

Re: Re: VirtualBox 4 fails building kernel module (the same with nvidia module)

[Jonas Jensen]

I switched to custom kernel and came across this thread. I also use
squeeze and this is what I have found.

First of, Debian has the following versions of nvidia-kernel-dkms packages:

squeeze: 195.36.31-6
sid/wheezy: 260.19.44-1
experimental: 270.30-1

The version in squeeze fail on anything above kernel 2.6.38 and none
will compile on 2.6.39 because of BKL removal; nvidia-kernel-dkms
depends on it; include/linux/smp_lock.h is missing and the driver
will not compile without it.

So I settled for kernel 2.6.38.4 and nvidia-kernel-dkms from
experimental because it compiles without issue. The packages from
sid/wheezy also work but why not use the latest and greatest. Here is
what i did:

cd /usr/src

download the following packages from exerimental:

libgl1-nvidia-glx_270.30-1_amd64.deb
nvidia-glx_270.30-1_amd64.deb
nvidia-kernel-dkms_270.30-1_amd64.deb
nvidia-common_20110213+1_amd64.deb
nvidia-kernel-common_20110213+1_amd64.deb

download, untar and configure kernel 2.6.38.4.

cd linux-2.6.38.4

fakeroot make-kpkg --initrd --revision=2.6.38.4+jj
--append_to_version=+jj kernel_image; fakeroot make-kpkg --initrd
--revision=2.6.38.4+jj --append_to_version=+jj kernel_headers

dpkg -i linux-image-2.6.38.4+jj_2.6.38.4+jj_amd64.deb
linux-headers-2.6.38.4+jj_2.6.38.4+jj_amd64.deb

dpkg -i libgl1-nvidia-glx_270.30-1_amd64.deb
nvidia-glx_270.30-1_amd64.deb nvidia-kernel-dkms_270.30-1_amd64.deb
nvidia-common_20110213+1_amd64.deb
nvidia-kernel-common_20110213+1_amd64.deb

dpkg-reconfigure nvidia-kernel-dkms


Best regards,
Jonas Jensen


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/banlktin3y0ndtbfurkci9340ssnhum6...@mail.gmail.com

Re: VirtualBox 4 fails building kernel module (the same with nvidia module)

[Cameron Hutchison]

MRH misiek_s...@o2.pl writes:
On 23/01/11 04:53, Cameron Hutchison wrote:
 and I had to revert two commits to fix it:

 7b8ea53d7f1865cd8f05dfb8f706a4ff5a72abcf (makefile: not need to
 regenerate kernel.release file when make kernelrelease)

 01ab17887f4cdcb8bb5a5d1bc3b160d186e6e99b (Makefile: make kernelrelease
 should show the correct full kernel version)

I'm afraid it's a bit beyond my skills at the moment - I guess it's 
about getting source tree by svn and reverting the changes applied by 
getting previous version of a file?

You need to have the git kernel tree, and you use the git revert
command. The second commit to revert (01ab1788) has a conflict when
reverting, but that's pretty easy to resolve (if you know what you're
doing :-))

Thanks anyway - I hope it will start working for me at some point :)

I haven't had time to look into what the correct fix would be, but I may
have some time in the next few weeks. I'll put it on my todo list.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/3d34.4d3f5ba2.3d...@getafix.xdna.net

Re: VirtualBox 4 fails building kernel module (the same with nvidia module)

[MRH]

On 22/01/11 23:03, tv.deb...@googlemail.com wrote:
[...]


I have the same setup, I build my kernel (2.6.37 currently) with
kernel-package and both nvidia and VirtualBox 4 work fine (they build
automatically with dkms). I don't use extraversion, only
--append-to-version and --revision.
The problem with extraversion and 2.6.37 is known, it's been reported
here if I remember, look for a message starting with kernel-package:
2.6.37 in the archives. But since it seems to affect only proprietary
software I guess they'll have to adapt.




Hmmm, that's interesting - I don't remember tinkering with extraversion 
directly - unless it's '-rc1' suffix which causes the trouble.
I did a number of tests yesterday and I found that I cannot get 
2.6.38-rc1 working at all, however I could finally get back 2.6.32 
working again after I build it (with both --revision and 
--append-to-version). This required deleting /usr/src/linux soft link 
after restarting PC - it has been recreated automagically by 'something' 
pointing to 2.6.38-rc1 source. But after removing the link both


/etc/init.d/vboxdrv setup
m-a a-i nvidia

worked and build me the modules. Still I don't know what's wrong with 
2.6.38-rc1. Perhaps it's '-rc1' fault - I'll wait for stable 2.6.38 and 
will report back :)


Thanks all for the advices.

--
Kind regards,
Michal R. Hoffmann


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4d3ded69.7090...@o2.pl

Re: VirtualBox 4 fails building kernel module (the same with nvidia module)

[MRH]

On 23/01/11 04:53, Cameron Hutchison wrote:

tv.deb...@googlemail.comtv.deb...@googlemail.com  writes:


The problem with extraversion and 2.6.37 is known, it's been reported
here if I remember, look for a message starting with kernel-package:
2.6.37 in the archives. But since it seems to affect only proprietary
software I guess they'll have to adapt.


Since I was the one to report that, I should correct some things I got
wrong. The problem also exists in 2.6.36 - that's when it was
introduced, and I had to revert two commits to fix it:

7b8ea53d7f1865cd8f05dfb8f706a4ff5a72abcf (makefile: not need to
regenerate kernel.release file when make kernelrelease)

01ab17887f4cdcb8bb5a5d1bc3b160d186e6e99b (Makefile: make kernelrelease
should show the correct full kernel version)

I don't know if this is related to the OP's issues - I don't use nvidia
drivers.




I'm afraid it's a bit beyond my skills at the moment - I guess it's 
about getting source tree by svn and reverting the changes applied by 
getting previous version of a file?


Thanks anyway - I hope it will start working for me at some point :)

--
Kind regards,
Michal R. Hoffmann


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4d3dee86.2090...@o2.pl

VirtualBox 4 fails building kernel module (the same with nvidia module)

[MRH]

Recently I updated VirtualBox from 3.2 to 4.0 (non OSE version). From 
that moment it stopped working, saying that the kernel driver (vboxdrv) 
is not loaded and suggesting to run /etc/init.d/vboxdrv setup


This fails:
--
Stopping VirtualBox kernel modules:done..
Uninstalling old VirtualBox DKMS kernel modules:done..
Trying to register the VirtualBox kernel modules using DKMS:
Error! Bad return status for module build on kernel: 2.6.38-rc1.mrh.01 
(x86_64)

Consult the make.log in the build directory
/var/lib/dkms/vboxhost/4.0.2/build/ for more information.

Failed, trying without DKMS ... failed!
Recompiling VirtualBox kernel modules:
Look at /var/log/vbox-install.log to find out what went wrong ... failed!
--

The above is the /var/log/vbox-install.log
Below /var/lib/dkms/vboxhost/4.0.2/build/make.log
--
DKMS make.log for vboxhost-4.0.2 for kernel 2.6.38-rc1.mrh.01 (x86_64)
Sat Jan 22 18:07:34 GMT 2011
make: Entering directory `/usr/src/linux-2.6.38-rc1'
  LD  /var/lib/dkms/vboxhost/4.0.2/build/built-in.o
  LD  /var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/built-in.o
  CC [M]  /var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/linux/SUPDrv-linux.o
In file included from 
/var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/include/VBox/types.h:30,
 from 
/var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/linux/../SUPDrvInternal.h:35,
 from 
/var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/linux/SUPDrv-linux.c:31:
/var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/include/iprt/types.h:105:31: 
error: linux/autoconf.h: No such fil

e or directory
make[2]: *** 
[/var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/linux/SUPDrv-linux.o] Error 1

make[1]: *** [/var/lib/dkms/vboxhost/4.0.2/build/vboxdrv] Error 2
make: *** [_module_/var/lib/dkms/vboxhost/4.0.2/build] Error 2
make: Leaving directory `/usr/src/linux-2.6.38-rc1'
--

I have home-build kernel, I had the same problem on 2.6.32 first, which 
worked nicely with VirtualBox 3.2 but stopped after installing VB 4.0 - 
unfortunately it seems it doesn't help going back to the VB 3.2 version, 
as the kernel driver module has been deleted and it fails building in 
the same way. So it seems there is a problem in building kernel modules. 
I have the same problem with nvidia proprietary driver - fails building.


I suspect the problem is I build the kernel with --append-to-version:

make-kpkg --initrd --revision=.mrh.01 --append-to-version=.mrh.01

but this helps me keeping things tidy.

Now I have no idea where is the problem, is it a known bug or I do 
something wrong (but it worked to me until recently). And I'm afraid I 
have no idea which package is the culprit.


I use debian sid, kernel from http://www.kernel.org/ (2.6.32 or 
2.6.38-rc1), have build and installed linux-image and linux-headers.


Any ideas, please?

--
Kind regards,
Michal R. Hoffmann


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4d3b20c8.3080...@o2.pl

Re: VirtualBox 4 fails building kernel module (the same with nvidia module)

[Nuno Magalhães]

Hi,

You're not gonna get much help using non-free software on a tarnished
kernel. That said, when i have problems with VBox i just purge
everything, dkms included, make sure the drivers are actually deleted,
then reinstall, with dkms. Usually does the trick.

HTH,
Nuno

-- 
Mars 2 Stay!
http://xkcd.com/801/
/etc


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/AANLkTinK602hY5RJF=4vtr6r_wk3xg1q5feyre0at...@mail.gmail.com

Re: VirtualBox 4 fails building kernel module (the same with nvidia module)

[Boyd Stephen Smith Jr.]

In 4d3b20c8.3080...@o2.pl, MRH wrote:
   CC [M]  /var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/linux/SUPDrv-linux.o
In file included from
/var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/include/VBox/types.h:30,
  from
/var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/linux/../SUPDrvInternal.h:35,
  from
/var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/linux/SUPDrv-linux.c:31:
/var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/include/iprt/types.h:105:31:
error: linux/autoconf.h: No such fil
e or directory

This file should be provided by the linux-headers-* package for your kernel.  
Make sure you are this package installed in order to build kernel modules.

I have home-build kernel.

I suspect the problem is I build the kernel with --append-to-version:

make-kpkg --initrd --revision=.mrh.01 --append-to-version=.mrh.01

but this helps me keeping things tidy.

I'm not familiar with make-kpkg since the stock Debian kernels have served me 
well so far.  Does it prepare all the linux-* .debs?  You'll need linux-
headers-* for building kernel modules.
-- 
Boyd Stephen Smith Jr.   ,= ,-_-. =.
b...@iguanasuicide.net   ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/\_/


signature.asc
Description: This is a digitally signed message part.

Re: VirtualBox 4 fails building kernel module (the same with nvidia module)

[MRH]

On 22/01/11 19:42, Boyd Stephen Smith Jr. wrote:

In4d3b20c8.3080...@o2.pl, MRH wrote:

   CC [M]  /var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/linux/SUPDrv-linux.o
In file included from
/var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/include/VBox/types.h:30,
  from
/var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/linux/../SUPDrvInternal.h:35,
  from
/var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/linux/SUPDrv-linux.c:31:
/var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/include/iprt/types.h:105:31:
error: linux/autoconf.h: No such fil
e or directory


This file should be provided by the linux-headers-* package for your kernel.
Make sure you are this package installed in order to build kernel modules.


Installed. As I wrote before, I build and installed both linux-image and 
linux-headers.





I have home-build kernel.

I suspect the problem is I build the kernel with --append-to-version:

make-kpkg --initrd --revision=.mrh.01 --append-to-version=.mrh.01

but this helps me keeping things tidy.


I'm not familiar with make-kpkg since the stock Debian kernels have served me
well so far.  Does it prepare all the linux-* .debs?  You'll need linux-
headers-* for building kernel modules.

Yes, it builds:
linux-image-2.6.38-rc1.mrh.01_.mrh.01_amd64.deb
linux-headers-2.6.38-rc1.mrh.01_.mrh.01_amd64.deb

and I have them installed.

I tried reinstalling dkms, kernel-package, virtualbox, both linux image 
and headers - still nothing.


I installed stock debian kernel - then it worked -ish - I mean both 
drivers have compiled, however X environment did not work (nvidia driver 
didn't work) and some other things I use are not available in the stock 
kernel.


Kind regards,
Michal
--
Michal R. Hoffmann


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4d3b5845.7000...@o2.pl

Re: VirtualBox 4 fails building kernel module (the same with nvidia module)

[tv.deb...@googlemail.com]

On the 22/01/2011 23:20, MRH wrote:
 On 22/01/11 19:42, Boyd Stephen Smith Jr. wrote:
 In4d3b20c8.3080...@o2.pl, MRH wrote:
CC [M] 
 /var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/linux/SUPDrv-linux.o
 In file included from
 /var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/include/VBox/types.h:30,
   from
 /var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/linux/../SUPDrvInternal.h:35,
   from
 /var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/linux/SUPDrv-linux.c:31:
 /var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/include/iprt/types.h:105:31:
 error: linux/autoconf.h: No such fil
 e or directory

 This file should be provided by the linux-headers-* package for your
 kernel.
 Make sure you are this package installed in order to build kernel
 modules.
 
 Installed. As I wrote before, I build and installed both linux-image and
 linux-headers.
 

 I have home-build kernel.

 I suspect the problem is I build the kernel with --append-to-version:

 make-kpkg --initrd --revision=.mrh.01 --append-to-version=.mrh.01

 but this helps me keeping things tidy.

 I'm not familiar with make-kpkg since the stock Debian kernels have
 served me
 well so far.  Does it prepare all the linux-* .debs?  You'll need linux-
 headers-* for building kernel modules.
 Yes, it builds:
 linux-image-2.6.38-rc1.mrh.01_.mrh.01_amd64.deb
 linux-headers-2.6.38-rc1.mrh.01_.mrh.01_amd64.deb
 
 and I have them installed.
 
 I tried reinstalling dkms, kernel-package, virtualbox, both linux image
 and headers - still nothing.
 
 I installed stock debian kernel - then it worked -ish - I mean both
 drivers have compiled, however X environment did not work (nvidia driver
 didn't work) and some other things I use are not available in the stock
 kernel.
 
 Kind regards,
 Michal

I have the same setup, I build my kernel (2.6.37 currently) with
kernel-package and both nvidia and VirtualBox 4 work fine (they build
automatically with dkms). I don't use extraversion, only
--append-to-version and --revision.
The problem with extraversion and 2.6.37 is known, it's been reported
here if I remember, look for a message starting with kernel-package:
2.6.37 in the archives. But since it seems to affect only proprietary
software I guess they'll have to adapt.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4d3b625b.9000...@googlemail.com

Re: VirtualBox 4 fails building kernel module (the same with nvidia module)

[Andrew Reid]

On Saturday 22 January 2011 13:24:08 MRH wrote:
 Recently I updated VirtualBox from 3.2 to 4.0 (non OSE version). From
 that moment it stopped working, saying that the kernel driver (vboxdrv)
 is not loaded and suggesting to run /etc/init.d/vboxdrv setup

 This fails:
 --
 Stopping VirtualBox kernel modules:done..
 Uninstalling old VirtualBox DKMS kernel modules:done..
 Trying to register the VirtualBox kernel modules using DKMS:
 Error! Bad return status for module build on kernel: 2.6.38-rc1.mrh.01
 (x86_64)
 Consult the make.log in the build directory
 /var/lib/dkms/vboxhost/4.0.2/build/ for more information.

 Failed, trying without DKMS ... failed!
 Recompiling VirtualBox kernel modules:
 Look at /var/log/vbox-install.log to find out what went wrong ... failed!
 --

 The above is the /var/log/vbox-install.log
 Below /var/lib/dkms/vboxhost/4.0.2/build/make.log
 --
 DKMS make.log for vboxhost-4.0.2 for kernel 2.6.38-rc1.mrh.01 (x86_64)
 Sat Jan 22 18:07:34 GMT 2011
 make: Entering directory `/usr/src/linux-2.6.38-rc1'
LD  /var/lib/dkms/vboxhost/4.0.2/build/built-in.o
LD  /var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/built-in.o
CC [M]  /var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/linux/SUPDrv-linux.o
 In file included from
 /var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/include/VBox/types.h:30,
   from
 /var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/linux/../SUPDrvInternal.h:35,
   from
 /var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/linux/SUPDrv-linux.c:31:
 /var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/include/iprt/types.h:105:31:
 error: linux/autoconf.h: No such fil
 e or directory
 make[2]: ***
 [/var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/linux/SUPDrv-linux.o] Error 1
 make[1]: *** [/var/lib/dkms/vboxhost/4.0.2/build/vboxdrv] Error 2
 make: *** [_module_/var/lib/dkms/vboxhost/4.0.2/build] Error 2
 make: Leaving directory `/usr/src/linux-2.6.38-rc1'
 --

 I have home-build kernel, I had the same problem on 2.6.32 first, which
 worked nicely with VirtualBox 3.2 but stopped after installing VB 4.0 -
 unfortunately it seems it doesn't help going back to the VB 3.2 version,
 as the kernel driver module has been deleted and it fails building in
 the same way. So it seems there is a problem in building kernel modules.
 I have the same problem with nvidia proprietary driver - fails building.

 I suspect the problem is I build the kernel with --append-to-version:

 make-kpkg --initrd --revision=.mrh.01 --append-to-version=.mrh.01

 but this helps me keeping things tidy.

 Now I have no idea where is the problem, is it a known bug or I do
 something wrong (but it worked to me until recently). And I'm afraid I
 have no idea which package is the culprit.

  For the home-built kernels, you want to also build the 
kernel-headers target, which will create the -headers .deb file,
which you can also install.  Use the same append-to-version as 
for the kernel image target, and it should work without further
intervention.

  I have some really good notes on this somewhere, but can't find them
just now, but as I recall, the make-kpkg docs are pretty good.

-- A.
-- 
Andrew Reid / rei...@bellatlantic.net


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201101221826.41577.rei...@bellatlantic.net

Re: VirtualBox 4 fails building kernel module (the same with nvidia module)

[Cameron Hutchison]

tv.deb...@googlemail.com tv.deb...@googlemail.com writes:

The problem with extraversion and 2.6.37 is known, it's been reported
here if I remember, look for a message starting with kernel-package:
2.6.37 in the archives. But since it seems to affect only proprietary
software I guess they'll have to adapt.

Since I was the one to report that, I should correct some things I got
wrong. The problem also exists in 2.6.36 - that's when it was
introduced, and I had to revert two commits to fix it:

7b8ea53d7f1865cd8f05dfb8f706a4ff5a72abcf (makefile: not need to
regenerate kernel.release file when make kernelrelease)

01ab17887f4cdcb8bb5a5d1bc3b160d186e6e99b (Makefile: make kernelrelease
should show the correct full kernel version)

I don't know if this is related to the OP's issues - I don't use nvidia
drivers.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1f88.4d3bb44a.f1...@getafix.xdna.net

Re: problem with nvidia module and kernel 2.6.26-2-amd64 SOLVED

[Rich Griffiths]

On Sat, 27 Jun 2009 23:20:04 +0200, Norbert Zeh wrote:

 'aptitude search nvidia' showed the following packages as installed:
   nvidia-settings
   nvidia-kernel-common
   nvidia-xconfig
   nvidia-glx
   nvidia-kernel-2.6.26-1-amd64
 
 I'm just guessing, but shouldn't you install
 nvidia-kernel-2.6.26-2-amd64 if you run linux-image-2.6.26-2-amd64?  At
 least an aptitude search nvidia showed me this package as installable.
 
 Cheers,
 Norbert

You're right Norbert!  Many thanks.

I don't know how I missed that, which is literally exactly what I did.  I 
scanned the listings for a '-2-' version of the nvidia-kernel and just 
didn't see it.  You prompted me to look again, and of course it was there.

I'm still wondering how the system seemed to be working fine for 3 months 
with the '-2-' image and the '-1-' nvidia, but I'm delighted to have the 
current problem solved so simply.

-- 
Rich


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

problem with nvidia module and kernel 2.6.26-2-amd64

[Rich Griffiths]

We had a power failure here yesterday.  The problem machine was on a 
small UPS, so it stayed up initially.

After a few minutes without power, I tried to shut down the machine 
normally using the KDE logout - Turn off computer sequence.  OOWrite was 
still open, and it popped up the dialog box asking Save/Discard/Cancel 
the current document.  I chose Discard, and the machine froze up.  
Wouldn't respond to keyboard or mouse.  So I held down the power switch 
to turn it off.

When I powered back up about an hour later, the machine booted up, tried 
to run kdm, and then quit, displaying only a command-line login prompt.

syslog and Xorg.0.log both indicated that the system couldn't find the 
nvidia module (the open source version from the Debian repositories).  
Here are the last few lines from Xorg.0.log:
--
(EE) NVIDIA(0): Failed to load the NVIDIA kernel module!
(EE) NVIDIA(0):  *** Aborting ***
(II) UnloadModule: nvidia
(II) UnloadModule: wfb
(II) UnloadModule: fb
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found
--

This occurred with linux-image-2.6.26-2-amd64.

'lsmod | grep nvidia' returned no modules.

'aptitude search nvidia' showed the following packages as installed:
  nvidia-settings
  nvidia-kernel-common
  nvidia-xconfig
  nvidia-glx
  nvidia-kernel-2.6.26-1-amd64

These are the same packages I have been using without problem since 4 
March 2009.

I still had linux-image-2.6.26-1-amd64 on the hard drive and in /boot/
grub/menu.lst.  So I rebooted into that kernel.  KDE came up fine, and 
the Xorg log now shows that the nvidia stuff was loaded properly.

I ran aptitude in interactive mode, going through the 'u' (update), 
'U' (upgrade), and 'g' (go) options, which reinstalled linux-
image-2.6.26-2-amd64, but I get the same nvidia failure with that kernel.

Helpful advice, please!

-- 
Rich


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: problem with nvidia module and kernel 2.6.26-2-amd64

[Norbert Zeh]

 'aptitude search nvidia' showed the following packages as installed:
   nvidia-settings
   nvidia-kernel-common
   nvidia-xconfig
   nvidia-glx
   nvidia-kernel-2.6.26-1-amd64

I'm just guessing, but shouldn't you install
nvidia-kernel-2.6.26-2-amd64 if you run linux-image-2.6.26-2-amd64?  At
least an aptitude search nvidia showed me this package as installable.

Cheers,
Norbert


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

problem: nvidia module not loading after updating Xorg (solved)

[Eeltje]

Did you get the nvidia module working again? It would be nice if you told 
whether you were successful or not...
--
Eeltje de Vries


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

problem: nvidia module not loading after updating Xorg [SOLVED]: CONFIRMATION

[arijit sarkar]

On Fri, 2007-06-15 at 11:57 +0200, Eeltje wrote:

 Did you get the nvidia module working again? It would be nice if you told 
 whether you were successful or not...
 -- 
 Eeltje de Vries
 
 

I am sorry not to reply early. I was busy for some personal business.
Yes, this problem is solved now.

thanks to, Eeltje, 
execute the following command as root,
# cd /usr/lib/xorg/modules/drivers
# gcc -shared -o nvidia_drv.so nvidia_drv.o

Then restart X. thats all. everything will be fine again. no need to
reinstall nvidia-driver again.

--
Arijit Sarkar
Kolkata, India



Debian GNU/Linux

problem: nvidia module not loading after updating Xorg (solved)

[Eeltje]

I had the same problem, see a different thread. There you can also find how it 
can be solved!
--
Eeltje de Vries


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: problem: nvidia module not loading after updating Xorg (solved)

[benjaminn bregg]

Can you post the link of that thread?



On 6/14/07, Eeltje [EMAIL PROTECTED] wrote:



I had the same problem, see a different thread. There you can also find
how it can be solved!
--
Eeltje de Vries


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
[EMAIL PROTECTED]





--
Arijit Sarkar,
Kolkata, India

Debian GNU/Linux

Re: problem: nvidia module not loading after updating Xorg

[H.S.]

arijit wrote:

Hi all,

I've just updated Xorg packages though synaptic.
But after system restart, i am unable to start X-server.
Error shown : unable to load module: nvidia


Exact same problem in my Etch box too. The work around for now is to run 
dpkg-reconfigure xserver-xorg and to select nv driver and restart gdm 
(or your display manager). This is on a box with:
01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 
MX/MX 400] (rev b2)


-HS


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

problem: nvidia module not loading after updating Xorg (solved)

[Eeltje]

The link is:

[url]http://www.debianhelp.org/node/8092[/url]

To repeat the story written there:

I send a bug report (see: 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=428731) and within minutes I 
got a work around!

What one has to do (as 'root') is:

# cd /usr/lib/xorg/modules/drivers
# gcc -shared -o nvidia_drv.so nvidia_drv.o

Then you can install 'nvidia' in xorg.conf and restart X. It really works!!

--
Eeltje de Vries


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: problem: nvidia module not loading after updating Xorg

[[EMAIL PROTECTED]]

On Jun 12, 11:20 am, arijit [EMAIL PROTECTED] wrote:
 Hi all,

 I've just updated Xorg packages though synaptic.
 But after system restart, i am unable to start X-server.
 Error shown : unable to load module: nvidia
 right now I've switched to 'vesa' but I want to use 'nvidia'.

 Also when i use nvidia-settings, i get this error:
 -
 $ nvidia-settings
 ERROR: NV-CONTROL extension not found on this Display.
 ERROR: Unable to determine number of NVIDIA GPUs on ':0.0'.
 ERROR: Unable to determine number of NVIDIA Frame Lock Devices on
 ':0.0'.
 -

 Here's the some output from Xorg.log:-
 -
 II) LoadModule: nvidia
 (WW) Warning, couldn't open module nvidia
 (II) UnloadModule: nvidia
 (EE) Failed to load module nvidia (module does not exist, 0)
 -

 How can i solve this?
 I was using nvidia-glx, NVIDIA binary XFree86 4.x driver version:
 1.0.8766-4

 --

 Arijit Sarkar
 Kolkata, India

 Evolution on Debian testing

same thing happened to me on the upgrade to xorg 7.2.  the nvidia
driver needs to be recompiled and packaged for the new xorg.thats
what we get for using non-free stuff...

you should file a bug on nvidia-kernel about this so they know that
they need to fix it.  in the meantime, u can download the driver
directly from nvidia.

mike


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: problem: nvidia module not loading after updating Xorg

[arijit sarkar]

On Wed, 2007-06-13 at 21:41 +, [EMAIL PROTECTED] wrote: 

 On Jun 12, 11:20 am, arijit [EMAIL PROTECTED] wrote:
  Hi all,
 
  I've just updated Xorg packages though synaptic.
  But after system restart, i am unable to start X-server.
  Error shown : unable to load module: nvidia
  right now I've switched to 'vesa' but I want to use 'nvidia'.
 
  Also when i use nvidia-settings, i get this error:
  -
  $ nvidia-settings
  ERROR: NV-CONTROL extension not found on this Display.
  ERROR: Unable to determine number of NVIDIA GPUs on ':0.0'.
  ERROR: Unable to determine number of NVIDIA Frame Lock Devices on
  ':0.0'.
  -
 
  Here's the some output from Xorg.log:-
  -
  II) LoadModule: nvidia
  (WW) Warning, couldn't open module nvidia
  (II) UnloadModule: nvidia
  (EE) Failed to load module nvidia (module does not exist, 0)
  -
 
  How can i solve this?
  I was using nvidia-glx, NVIDIA binary XFree86 4.x driver version:
  1.0.8766-4
 
  --
 
  Arijit Sarkar
  Kolkata, India
 
  Evolution on Debian testing
 
 same thing happened to me on the upgrade to xorg 7.2.  the nvidia
 driver needs to be recompiled and packaged for the new xorg.thats
 what we get for using non-free stuff...
 
 you should file a bug on nvidia-kernel about this so they know that
 they need to fix it.  in the meantime, u can download the driver
 directly from nvidia.
 
 mike
 


Thanks for the information. However I've changed my driver to 'nv' for
the time being.
it seems this bug already been reported.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=428697

thanks,

--
Arijit Sarkar
Kolkata, India




Debian GNU/Linux

problem: nvidia module not loading after updating Xorg

[arijit]

Hi all,

I've just updated Xorg packages though synaptic.
But after system restart, i am unable to start X-server.
Error shown : unable to load module: nvidia
right now I've switched to 'vesa' but I want to use 'nvidia'.

Also when i use nvidia-settings, i get this error:
-
$ nvidia-settings
ERROR: NV-CONTROL extension not found on this Display.
ERROR: Unable to determine number of NVIDIA GPUs on ':0.0'.
ERROR: Unable to determine number of NVIDIA Frame Lock Devices on
':0.0'.
-

Here's the some output from Xorg.log:-
-
II) LoadModule: nvidia
(WW) Warning, couldn't open module nvidia
(II) UnloadModule: nvidia
(EE) Failed to load module nvidia (module does not exist, 0)
-

How can i solve this?
I was using nvidia-glx, NVIDIA binary XFree86 4.x driver version:
1.0.8766-4

--

Arijit Sarkar
Kolkata, India


Evolution on Debian testing

Re: problem: nvidia module not loading after updating Xorg

[Bob McGowan]

arijit wrote:

Hi all,

I've just updated Xorg packages though synaptic.
But after system restart, i am unable to start X-server.
Error shown : unable to load module: nvidia
right now I've switched to 'vesa' but I want to use 'nvidia'.

Also when i use nvidia-settings, i get this error:
-
$ nvidia-settings
ERROR: NV-CONTROL extension not found on this Display.
ERROR: Unable to determine number of NVIDIA GPUs on ':0.0'.
ERROR: Unable to determine number of NVIDIA Frame Lock Devices on ':0.0'.
-

Here's the some output from Xorg.log:-
-
II) LoadModule: nvidia
(WW) Warning, couldn't open module nvidia
(II) UnloadModule: nvidia
(EE) Failed to load module nvidia (module does not exist, 0)
-

How can i solve this?
I was using nvidia-glx, NVIDIA binary XFree86 4.x driver version: 
1.0.8766-4


--

/Arijit Sarkar/
/Kolkata, India/


Evolution on Debian testing



Did you also upgrade the kernel?  If so, you need to re-run the nvidia 
installation script to either install a pre-compiled, or to compile and 
install a custom, Nvidia driver.


--
Bob McGowan


smime.p7s
Description: S/MIME Cryptographic Signature

Compiling a Nvidia module [was Re: Compiling a kernel]

[Chris Bannister]

On Mon, Oct 23, 2006 at 11:31:46PM -0500, cothrige wrote:
 With this install of Debian I decided to stick to what I know, and
 grabbed the binary installer direct from NVidia.  I ran that, and in
 less than two minutes I was up and running.  No complaints from Debian
 and no complaints from NVidia.  Oh, except for one because I had tried
 to compile it before I updated the system fully and so I had a gcc
 which didn't match the kernel, but that was fixed in no time.

Apparently the binary installer from NVidia messes with the libraries on
the system and is not the recommended method for installing.

Read http://home.comcast.net/~andrex/Debian-nVidia/

The Debian way is certainly a lot easier. Now where has that nvidia-glx
package gone?

-- 
Chris.
==
 ... the official version cannot be abandoned because the implication of
rejecting it is far too disturbing: that we are subject to a government
conspiracy of `X-Files' proportions and insidiousness.
Letter to the LA Times Magazine, September 18, 2005.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a Nvidia module [was Re: Compiling a kernel]

[cothrige]

* Chris Bannister ([EMAIL PROTECTED]) wrote:
 
 Apparently the binary installer from NVidia messes with the libraries on
 the system and is not the recommended method for installing.
 
 Read http://home.comcast.net/~andrex/Debian-nVidia/
 
 The Debian way is certainly a lot easier. Now where has that nvidia-glx
 package gone?
 

Well, that is exactly the problem.  I tried several times initially to
install it via apt but it could never do it.  IIRC, there was no
nvidia-glx package and so it would not install.  This was a test of an
installation BTW which ended up being only temporary.  When I finally
committed and gave over my main partition to Debian I decided to
simply try it the old fashioned way and see how it went.  So far so
good, though I expect that may change at any time.  Many thanks for
the howto though.  The next time I compile a kernel I will try it the
Debian way, just to see how I perhaps messed up the first time.

Patrick


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a Nvidia module [was Re: Compiling a kernel]

[David Baron]

On Wednesday 25 October 2006 13:29, Chris Bannister wrote:
 On Mon, Oct 23, 2006 at 11:31:46PM -0500, cothrige wrote:
  With this install of Debian I decided to stick to what I know, and
  grabbed the binary installer direct from NVidia.  I ran that, and in
  less than two minutes I was up and running.  No complaints from Debian
  and no complaints from NVidia.  Oh, except for one because I had tried
  to compile it before I updated the system fully and so I had a gcc
  which didn't match the kernel, but that was fixed in no time.

 Apparently the binary installer from NVidia messes with the libraries on
 the system and is not the recommended method for installing.

 Read http://home.comcast.net/~andrex/Debian-nVidia/

 The Debian way is certainly a lot easier. Now where has that nvidia-glx
 package gone?

Nvidia's own gives me twice the frame rate of Debian's nvidia-glx (Sid).

Nvidia is looking for some Xorg SDK to tell it where to place its module. Not 
finding that, it uses the default /usr/lib which means interference with/by 
xorg glx packages. Each time you put in new Xorg stuff, simply rerun their 
installer. A bit of a bother but as you said, a few minutes.

Examin their advanced options. There may be a way to tell it where to 
install the glx stuff. Then simply have xorg.conf check modules there 
first :-)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Compiling a Nvidia module [was Re: Compiling a kernel]

[Alan Ianson]

On Wed October 25 2006 06:39, David Baron wrote:
 On Wednesday 25 October 2006 13:29, Chris Bannister wrote:
  On Mon, Oct 23, 2006 at 11:31:46PM -0500, cothrige wrote:
   With this install of Debian I decided to stick to what I know, and
   grabbed the binary installer direct from NVidia.  I ran that, and in
   less than two minutes I was up and running.  No complaints from Debian
   and no complaints from NVidia.  Oh, except for one because I had tried
   to compile it before I updated the system fully and so I had a gcc
   which didn't match the kernel, but that was fixed in no time.
 
  Apparently the binary installer from NVidia messes with the libraries on
  the system and is not the recommended method for installing.
 
  Read http://home.comcast.net/~andrex/Debian-nVidia/
 
  The Debian way is certainly a lot easier. Now where has that nvidia-glx
  package gone?

 Nvidia's own gives me twice the frame rate of Debian's nvidia-glx (Sid).

 Nvidia is looking for some Xorg SDK to tell it where to place its module.
 Not finding that, it uses the default /usr/lib which means interference
 with/by xorg glx packages. Each time you put in new Xorg stuff, simply
 rerun their installer. A bit of a bother but as you said, a few minutes.

 Examin their advanced options. There may be a way to tell it where to
 install the glx stuff. Then simply have xorg.conf check modules there
 first :-)

When I (cough) installed nvidia's own installer I installed xorg-dev first so 
it could figure out where to put stuff. I'm running with an m-a installed 
module now and am having good results. Wish I had checked the frame rate but 
it seems to be working well in any case.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: nvidia module and 2.6.16 kernel problem

[Tim Wood]

H.S. wrote:


I have installed the new 2.6.16 kernel on two machines running Debian
Sid and tried to install nvidia module. On both machines, the module
compilation (using module-assistant) fails with some error messages
(IIRC there was some error about rlim structure not being defined).

Searching google has hinted that there is a patch for nvidia package
from Nvidia. I was wondering if a Debian nvidia package is forthcoming
that fixes this problem.

-HS





Like stated, it depends on how and what you are trying to install.
I install the nVidia driver:
NVIDIA-Linux-x86-1.0-7167-pkg1.run
directly on 2.6.16-ck1 and found this patch:
http://www.nvnews.net/vbulletin/showthread.php?t=62889
which refers to:
NVIDIA_kernel-1.0-8178-1444349.diff.txt
and if you apply that to the extracted file it applies and the driver then 
compiles.

H 


If the quote is not exactly correct, I apologise, but I receive user 
in digest form.


Our you saying you applied the 8178 patch to the 7167 driver?

I did have the 7176 driver running quite happily on 2.6.15, but have 
even managed to screw that one up too :)


Tim


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: nvidia module and 2.6.16 kernel problem

[Tim Wood]

I receive the digest, so hope this reads ok.


Tim Wood wrote:



I have installed the new 2.6.16 kernel on two machines running Debian
Sid and tried to install nvidia module. On both machines, the module
compilation (using module-assistant) fails with some error messages
(IIRC there was some error about rlim structure not being defined).

Searching google has hinted that there is a patch for nvidia package
from Nvidia. I was wondering if a Debian nvidia package is forthcoming
that fixes this problem.

-HS




I have had this problem. There is a patch to the Nvidia driver
(NVIDIA-Linux-x86-1.0-8178-pkg1.run) available here:

http://www.nvnews.net/vbulletin/showthread.php?t=62015

I've tried it for my laptop, which has a GeForce4 420 Go chip. The
driver compiled and the module loaded, but it completely freezes the
laptop. I do not think this has anything to do with it's being a laptop
as I also have a desktop on which I use the same procedures, 'though I
have not had opportunity to try this latest driver.

The link does contain detailed instructions, on two different methods of
using it, so I'm considering trying the option to build a new version of
the run file and use module assistant.



The success of this procedure might also depend on whether you use the
nvidia installer directly or the Debian package. I think the Debian
package already has some of the individual patches applied to it,
therefore things might go wrong if you apply the cumulative patch.


After some thought I did a diff on the patched files and the ones in 
/usr/src/modules/nvidia-kernel/nv and copied across the patched ones.

m-a did compile and install but the result was the same.

This is a major pain as the laptop completely crashes. I tried it while 
telnetted in from my desktop, but that killed the session. There is 
nothing in Xorg.0.log or in syslog to help.




Some more info is here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=357992

A fix for older cards thanks to Hugo Vanwoerkom:
http://lists.debian.org/debian-user/2006/03/msg02267.html

For the record, I use the nvidia installer directly with 2.6.16 and a
GeForce2 MX 100 (NV11DDR chipset); it works without problems after
applying the cumulative patch.


I'm considering purging everything nvidia, then running the patched 
installer again, and procedding from there. I run flightgear and it's 
unuseable without acceleration. For everything else the nv driver is fine.


I'm away from home right now, but will see how it goes with my desktop 
which as the GeForce2(4?) MX 440.



Tim


Regards,
   Florian



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: nvidia module and 2.6.16 kernel problem [Solved]

[Tim Wood]

I decided to follow the advise in one of Florian' links (Thanks Florian)
and use the  NVIDIA_kernel-1.0-8178-1444349.diff.txt patch to the 7676 
driver. After fixing a few links, it's up and running.


Must say that I'm a bit bemused at applying an 8178 patch to the 7676 
driver, but have not gone through the patch to check. I'm equally 
puzzled as to why the 8178 patched driver does not work as my chip is on 
the list.


As an aside I'd comment that the biggest pain was the crash forced an 
fsck and on a couple of occasions also required manually running a full 
fsck.


Thanks to Florian and Hugo for their help.

Regards,
Tim

(all this took place while Cat 4 Cyclone Glenda just missed me to the west:)


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: nvidia module and 2.6.16 kernel problem [Solved]

[Hugo Vanwoerkom]

Tim Wood wrote:

I decided to follow the advise in one of Florian' links (Thanks Florian)
and use the  NVIDIA_kernel-1.0-8178-1444349.diff.txt patch to the 7676 
driver. After fixing a few links, it's up and running.


Must say that I'm a bit bemused at applying an 8178 patch to the 7676 
driver, but have not gone through the patch to check. I'm equally 
puzzled as to why the 8178 patched driver does not work as my chip is on 
the list.


As an aside I'd comment that the biggest pain was the crash forced an 
fsck and on a couple of occasions also required manually running a full 
fsck.




Going through the patch leads to just more questions.
Sad that the closed source driver still is the best there is for nVidia 
cards.


H


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: nvidia module and 2.6.16 kernel problem

[Florian Kulzer]

Tim Wood wrote:


I have installed the new 2.6.16 kernel on two machines running Debian
Sid and tried to install nvidia module. On both machines, the module
compilation (using module-assistant) fails with some error messages
(IIRC there was some error about rlim structure not being defined).

Searching google has hinted that there is a patch for nvidia package
from Nvidia. I was wondering if a Debian nvidia package is forthcoming
that fixes this problem.

-HS



I have had this problem. There is a patch to the Nvidia driver
(NVIDIA-Linux-x86-1.0-8178-pkg1.run) available here:

http://www.nvnews.net/vbulletin/showthread.php?t=62015

I've tried it for my laptop, which has a GeForce4 420 Go chip. The
driver compiled and the module loaded, but it completely freezes the
laptop. I do not think this has anything to do with it's being a laptop
as I also have a desktop on which I use the same procedures, 'though I
have not had opportunity to try this latest driver.

The link does contain detailed instructions, on two different methods of
using it, so I'm considering trying the option to build a new version of
the run file and use module assistant.


The success of this procedure might also depend on whether you use the
nvidia installer directly or the Debian package. I think the Debian
package already has some of the individual patches applied to it,
therefore things might go wrong if you apply the cumulative patch.

Some more info is here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=357992

A fix for older cards thanks to Hugo Vanwoerkom:
http://lists.debian.org/debian-user/2006/03/msg02267.html

For the record, I use the nvidia installer directly with 2.6.16 and a
GeForce2 MX 100 (NV11DDR chipset); it works without problems after
applying the cumulative patch.

Regards,
   Florian


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: nvidia module and 2.6.16 kernel problem

[Hugo Vanwoerkom]

H.S. wrote:

I have installed the new 2.6.16 kernel on two machines running Debian
Sid and tried to install nvidia module. On both machines, the module
compilation (using module-assistant) fails with some error messages
(IIRC there was some error about rlim structure not being defined).

Searching google has hinted that there is a patch for nvidia package
from Nvidia. I was wondering if a Debian nvidia package is forthcoming
that fixes this problem.

-HS





Like stated, it depends on how and what you are trying to install.
I install the nVidia driver:
NVIDIA-Linux-x86-1.0-7167-pkg1.run
directly on 2.6.16-ck1 and found this patch:
http://www.nvnews.net/vbulletin/showthread.php?t=62889
which refers to:
NVIDIA_kernel-1.0-8178-1444349.diff.txt
and if you apply that to the extracted file it applies and the driver 
then compiles.


H


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

nvidia module and 2.6.16 kernel problem

[H.S.]

I have installed the new 2.6.16 kernel on two machines running Debian
Sid and tried to install nvidia module. On both machines, the module
compilation (using module-assistant) fails with some error messages
(IIRC there was some error about rlim structure not being defined).

Searching google has hinted that there is a patch for nvidia package
from Nvidia. I was wondering if a Debian nvidia package is forthcoming
that fixes this problem.

-HS



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

RE: nvidia module and 2.6.16 kernel problem

[Tim Wood]

I have installed the new 2.6.16 kernel on two machines running Debian
Sid and tried to install nvidia module. On both machines, the module
compilation (using module-assistant) fails with some error messages
(IIRC there was some error about rlim structure not being defined).

Searching google has hinted that there is a patch for nvidia package
from Nvidia. I was wondering if a Debian nvidia package is forthcoming
that fixes this problem.

-HS


I have had this problem. There is a patch to the Nvidia driver 
(NVIDIA-Linux-x86-1.0-8178-pkg1.run) available here:


http://www.nvnews.net/vbulletin/showthread.php?t=62015

I've tried it for my laptop, which has a GeForce4 420 Go chip. The 
driver compiled and the module loaded, but it completely freezes the 
laptop. I do not think this has anything to do with it's being a laptop 
as I also have a desktop on which I use the same procedures, 'though I 
have not had opportunity to try this latest driver.


The link does contain detailed instructions, on two different methods of 
using it, so I'm considering trying the option to build a new version of 
the run file and use module assistant.


Tim


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Nvidia module not found.. aargh

[Lars Schimmer]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi!

Die Sorgen gehen weiter.
Sarge installiert, graphical Desktop installiert, Kernel 2.6.12 gebaut
mit den nvidia-source als modul und restartet.
Juchu, er startet auf dem pentiumD mit der nvidia 7800GT. Und modprob
nvidia lädt das Modul. Aber XFree meint: no screens found, bzw. etwas
vorher steht im Log:
(II) LoadModule: nvidia
(WW) Warning, couldn't open module nvidia
(II) UnloadModule: nvidia
(EE) Failed to load module nvidia (module does not exist, 0)

Whaaat?
lsmod
Module  Size  Used by
nvidia   3715492  0

Sagt der da.

Nanu, wasn kaputt?

Grüße
Lars
- --
- -
TU Graz, Institut für ComputerGraphik  WissensVisualisierung
Tel.: +43 316 873-5405   E-Mail: [EMAIL PROTECTED]
PGP-Key-ID: 0xB87A0E03
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDHAPAVguzrLh6DgMRAm1AAJ4+vrwBiEbvvdHx+Y/wETshhpQd/gCgi6/j
UKFbV3R1rx37rxGKtdlanbc=
=i2H4
-END PGP SIGNATURE-


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: Nvidia module not found.. aargh

[Ole Janssen]

Am Montag, 5. September 2005 10:37 schrieb Lars Schimmer:
 (II) LoadModule: nvidia
 (WW) Warning, couldn't open module nvidia
 (II) UnloadModule: nvidia
 (EE) Failed to load module nvidia (module does not exist, 0)

Hast Du das Paket nvidia-glx installiert?

Viele Grüße, Ole

Re: Nvidia module not found.. aargh

[Lars Schimmer]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Ole Janssen wrote:
 Am Montag, 5. September 2005 10:37 schrieb Lars Schimmer:
 
(II) LoadModule: nvidia
(WW) Warning, couldn't open module nvidia
(II) UnloadModule: nvidia
(EE) Failed to load module nvidia (module does not exist, 0)
 
 
 Hast Du das Paket nvidia-glx installiert?

Nein, habe ich nicht. Das soll man ja auch nicht, wenn man den source
compiliert hat, oder?
Außerdem liegt komischerweise das nvidia module in
/lib/modules/2.6.12/nvidia *huch*
Das lag mal in ...12/kernel/driver/video...

 Viele Grüße, Ole


Grüße
Lars
- --
- -
TU Graz, Institut für ComputerGraphik  WissensVisualisierung
Tel.: +43 316 873-5405   E-Mail: [EMAIL PROTECTED]
PGP-Key-ID: 0xB87A0E03
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDHFhYVguzrLh6DgMRAsDJAKDWoDiMKWR90o/6LtRWYsVheyGeBQCgqV98
qFPycp3glxr8efd/rKwh9dc=
=2UWh
-END PGP SIGNATURE-


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: Nvidia module not found.. aargh

[Friedemann Schorer]

Hi,


Hast Du das Paket nvidia-glx installiert?


Nein, habe ich nicht. Das soll man ja auch nicht, wenn man den source
compiliert hat, oder?


Doch, soll man. Du baust beim Kompilieren gemäß den Vorschlägen in 
/usr/share/doc/nvidia-source/README.Debian ein Paket, das nur ein 
Linker-Kernelmodul zu dem binary-only.Modul von NVidia enthält. Und nur mit 
dem Adapter zum Treiber kommst Du halt nicht weit :D


HTH,

Friedemann

Re: Nvidia module not found.. aargh

[Ole Janssen]

Am Montag, 5. September 2005 17:36 schrieb Friedemann Schorer:
  Hast Du das Paket nvidia-glx installiert?
 
  Nein, habe ich nicht. Das soll man ja auch nicht, wenn man den
  source compiliert hat, oder?

 Doch, soll man. Du baust beim Kompilieren gemäß den Vorschlägen in
 /usr/share/doc/nvidia-source/README.Debian ein Paket, das nur ein
 Linker-Kernelmodul zu dem binary-only.Modul von NVidia enthält. Und
 nur mit dem Adapter zum Treiber kommst Du halt nicht weit :D

Genau. Hier ist es offenbar zu einer Verwechlung gekommen. Sowohl das 
Kernel-Modul, als auch das Xfree-Modul heißen nvidia; was Dir (Lars) 
gemäß Deinem Xfree-Log fehlt ist das Xfree-Modul, das sich in dem Paket 
nvidia-glx befindet.

Viele Grüße, Ole

Re: No X - Problems with loading Nvidia module

[David Roguin]

I had the some problem last night.
I fixed it this morning, some how it broke when i upgrade somehting,
but i dont know.

That's the recipe:
note: i'm not sure if all the steps are necesary, that's because it
worked for me this way.

1. rmmod nvidia
2. apt-get remove --purge nvidia-kernel*
3. cd /usr/src
if you have any nvidia*deb in there remove it.
If you have modules/nvidia-kernel, remove the directory too.

Ok, so far, we clean up (i believe something needed to refresh, but i
don't know other way ;) )

5. module-assistant update
6. module-assistant auto-install nvidia
7. apt-get install nvidia-glx
8. modprobe nvidia
9. restart X.

Enjoy nvidia.

Regards

On 7/11/05, KS [EMAIL PROTECTED] wrote:
 Hi,
 
 I thought of restarting my machine after the browser was getting stuck
 at some websites since last night. On restarting, X couldn't start.  The
 error log indicated that the Nvidia module couldnot be loaded. Below are
 the last few lines from the XFree86 log:
 
 (II) Setting vga for screen 0.
 (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
 (==) NVIDIA(0): RGB weight 888
 (==) NVIDIA(0): Default visual is TrueColor
 (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
 (--) NVIDIA(0): Linear framebuffer at 0xE000
 (--) NVIDIA(0): MMIO registers at 0xFD00
 (EE) NVIDIA(0): Failed to load the NVIDIA kernel module!
 (EE) NVIDIA(0):  *** Aborting ***
 (II) UnloadModule: nvidia
 (EE) Screen(s) found, but none have a usable configuration.
 
 Fatal server error:
 no screens found
 
 
 My machine is running unstable:
 ~$ uname -a
 Linux gurh 2.6.11-1-686 #1 Mon Jun 20 22:00:38 MDT 2005 i686 GNU/Linux
 
 Any suggestions to how to get X working with nvidia module?
 
 Thanks in advance,
 /KS
 --
   KS
   [EMAIL PROTECTED]
 
 --
 http://www.fastmail.fm - Faster than the air-speed velocity of an
   unladen european swallow
 
 
 --
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 

No X - Problems with loading Nvidia module

[KS]

Hi,

I thought of restarting my machine after the browser was getting stuck
at some websites since last night. On restarting, X couldn't start.  The
error log indicated that the Nvidia module couldnot be loaded. Below are
the last few lines from the XFree86 log:

(II) Setting vga for screen 0.
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(--) NVIDIA(0): Linear framebuffer at 0xE000
(--) NVIDIA(0): MMIO registers at 0xFD00
(EE) NVIDIA(0): Failed to load the NVIDIA kernel module!
(EE) NVIDIA(0):  *** Aborting ***
(II) UnloadModule: nvidia
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found


My machine is running unstable:
~$ uname -a
Linux gurh 2.6.11-1-686 #1 Mon Jun 20 22:00:38 MDT 2005 i686 GNU/Linux

Any suggestions to how to get X working with nvidia module?

Thanks in advance,
/KS
-- 
  KS
  [EMAIL PROTECTED]

-- 
http://www.fastmail.fm - Faster than the air-speed velocity of an
  unladen european swallow


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: compiled nvidia module fails

[Matthew Yates]

I run Debian unstable on my desktop at home.  I did an
apt-get upgrade last night and this morning my
Nvidia module failed to load.  The nv module works
OK, but I need TV-out functionality.  My kernel is
2.6.7 and the Nvidia module was downloaded from
nvidia.com and installed following their instructions.

Does anyone know how I can check to see which packages
were upgraded last night?  I didn't keep track of it,
but it may be helpful in figuring out the source of
the problem.  My kernel is custom, so it was not
upgraded.

-Matt



__ 
Do you Yahoo!? 
Yahoo! Mail - Find what you need with new enhanced search.
http://info.mail.yahoo.com/mail_250


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: compiled nvidia module fails

[Tim Beauregard]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matthew Yates wrote:
| Does anyone know how I can check to see which packages
| were upgraded last night?  I didn't keep track of it,
| but it may be helpful in figuring out the source of
| the problem.  My kernel is custom, so it was not
| upgraded.
I don't know how to answer your question, but tell us how long ago since
you did your previous upgrade?
Tim
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org
iD8DBQFBsK4psUUdIDHrdAURAhOCAKDF2raQ/E9m45rL7HD8TEjnF79dYgCgo8Ua
9ikoDo/F6J/Z3pqw1r16E6Q=
=5VVn
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: compiled nvidia module fails

[Matthew Yates]

The previous upgrade was done only a few days ago
(Sunday or Monday I think).  Whatever is causing the
problem was loaded into Debian unstable in the past
week or less.

I have a custom kernel that wasn't upgraded by apt and
the Nvidia module was directly from nvidia.com, so it
wasn't upgraded either.

-Matt

--- Tim Beauregard [EMAIL PROTECTED] wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Matthew Yates wrote:
 | Does anyone know how I can check to see which
 packages
 | were upgraded last night?  I didn't keep track of
 it,
 | but it may be helpful in figuring out the source
 of
 | the problem.  My kernel is custom, so it was not
 | upgraded.
 
 I don't know how to answer your question, but tell
 us how long ago since
 you did your previous upgrade?
 
 Tim
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.2.5 (GNU/Linux)
 Comment: Using GnuPG with Debian -
 http://enigmail.mozdev.org
 

iD8DBQFBsK4psUUdIDHrdAURAhOCAKDF2raQ/E9m45rL7HD8TEjnF79dYgCgo8Ua
 9ikoDo/F6J/Z3pqw1r16E6Q=
 =5VVn
 -END PGP SIGNATURE-
 




__ 
Do you Yahoo!? 
Jazz up your holiday email with celebrity designs. Learn more.
http://celebrity.mail.yahoo.com


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: compiled nvidia module fails

[Matthew Yates]

I fixed the problem, but I still don't know what
caused it.  The nvidia module failed to load.  I also
notice my soundcard module (i810_audio) wasn't loaded.
 I added nvidia' and i810_audio to /etc/modules,
and now everything is working as before.  These
modules were loaded automatically before.  Any idea
why this would change?

-Matt

--- Tim Beauregard [EMAIL PROTECTED] wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Matthew Yates wrote:
 | Does anyone know how I can check to see which
 packages
 | were upgraded last night?  I didn't keep track of
 it,
 | but it may be helpful in figuring out the source
 of
 | the problem.  My kernel is custom, so it was not
 | upgraded.
 
 I don't know how to answer your question, but tell
 us how long ago since
 you did your previous upgrade?
 
 Tim
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.2.5 (GNU/Linux)
 Comment: Using GnuPG with Debian -
 http://enigmail.mozdev.org
 

iD8DBQFBsK4psUUdIDHrdAURAhOCAKDF2raQ/E9m45rL7HD8TEjnF79dYgCgo8Ua
 9ikoDo/F6J/Z3pqw1r16E6Q=
 =5VVn
 -END PGP SIGNATURE-
 




__ 
Do you Yahoo!? 
Meet the all-new My Yahoo! - Try it today! 
http://my.yahoo.com 
 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Re: compiled nvidia module fails

[Collet Brunel]

Check if the nvidia-kernel-source version matches with
the nvidia-glx package version.. there may be a
conflict there.. 





___ 
Yahoo! Acesso Grátis - Internet rápida e grátis. Instale o discador agora! 
http://br.acesso.yahoo.com/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: compiled nvidia module fails

[Tim Beauregard]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Collet Brunel wrote:
| Check if the nvidia-kernel-source version matches with
| the nvidia-glx package version.. there may be a
| conflict there..
Not in my case;
[EMAIL PROTECTED]:~$ dpkg -l nvidia-kernel-source
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:
uppercase=bad)
||/ Name  Version   Description
+++-=-=-==
ii  nvidia-kernel-source  1.0.6629+1-1  NVIDIA binary
kernel module source
[EMAIL PROTECTED]:~$ dpkg -l nvidia-glx
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:
uppercase=bad)
||/ Name  Version   Description
+++-=-=-==
ii  nvidia-glx1.0.6629+1-1  NVIDIA binary
XFree86 4.x driver
Thanks anyway.
Tim
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org
iD8DBQFBr3bGsUUdIDHrdAURAvOtAJ4qZINJUtGJJ8Rv4AxEGj7w61IobwCfWnNE
jRc9spUnjZVG33MDBV0/Ikk=
=rD+v
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: compiled nvidia module fails

[Tim Beauregard]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Olle Eriksson wrote:
| On Tuesday 30 November 2004 22.18, Tim Beauregard wrote:
|I am unable to use the nvidia module compiled from nvidia-kernel-source
|that is used with the nvidia-glx package.  On boot-up, the computer
|freezes when gdm starts.  The error message I get in the logs is
|Failed to initialize the NVIDIA kernel module
|This is using a 2.6.7 compiled kernel on Debian unstable system.
|I have tried recompiling the kernel, as well as reinstalling the entire
|system to no avail.  The nv module works fine.
|I cannot obtain any more log messages as the computer freezes and
|requires reboot, losing any messages before they are written to the
|hard drive.
|I think the problem started after an apt-get update/upgrade, the
|nvidia-glx package may have been upgrade.
|Has anyone else had trouble like this?  Any suggestions greatly
|appreciated.
|
| I am not an expert here, but how about compiling nvidia module with
| 'module-assistant install nvidia'. (Make sure you have modele-assistant
| installed, maybe something else is needed too). Then that will download,
| compile and install the nvidia kernel module.
| I had to do 'module-assistant upgrade nvidia' after an apt-get upgrade.
| After that I had to remove and insert the new kernel module with 'rmmod
| nvidia' and 'modprobe nvidia'.
| Olle
This may be the solution I'm after, but don't know how to apply it to my
system; I'm not familiar with module-assistant.  I compile the nvidia
module in conjunction with the kernel:
apt-get install kernel-source-2.6.7 nvidia-kernel-source
nvidia-kernel-common
tar xvjf kernel-source-2.6.7.bz2
tar xvzf nvidia-kernel-source.tar.gz
ln -s kernel-source-2.6.7 linux
cd linux
(fakeroot make-kpkg clean)
make menuconfig
fakeroot make-kpkg --revision=20041201 kernel_image modules_image
dpkg -i kernel-image-2.6.7-20041201.deb nvidia-kernel-2.6.7-20041201.deb
reboot
apt-get install nvidia-glx
(dpkg-reconfigure nvidia-glx)
Where in all this would I run module-assistant?
Thanks for your advice,
Tim
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org
iD8DBQFBrfk7sUUdIDHrdAURAtKQAJ0b+M+2poMyJyQZg4wBBhb0jVgf5gCgllaJ
qj63k2mkEeAI+RsPjDFcmio=
=Ws8g
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: compiled nvidia module fails

[Andrew Schulman]

 apt-get install kernel-source-2.6.7 nvidia-kernel-source
 nvidia-kernel-common
 tar xvjf kernel-source-2.6.7.bz2
 tar xvzf nvidia-kernel-source.tar.gz
 ln -s kernel-source-2.6.7 linux
 cd linux
 (fakeroot make-kpkg clean)
 make menuconfig
 fakeroot make-kpkg --revision=20041201 kernel_image modules_image
 dpkg -i kernel-image-2.6.7-20041201.deb nvidia-kernel-2.6.7-20041201.deb
 reboot
 apt-get install nvidia-glx
 (dpkg-reconfigure nvidia-glx)
 
 Where in all this would I run module-assistant?

Your procedure above looks right.  If you wanted to use module-
assistant, you would just omit the nvidia-related parts of the procedure 
above, and then run 'module-assistant auto-install nvidia' after 
installing your kernel.

You may find some useful troubleshooting tips for this driver at 
http://home.comcast.net/~andrex/Debian-nVidia/troubleshooting.html.

Good luck,
Andrew.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: compiled nvidia module fails

[Tim Beauregard]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew Schulman wrote:
|Where in all this would I run module-assistant?
|
|
| Your procedure above looks right.  If you wanted to use module-
| assistant, you would just omit the nvidia-related parts of the procedure
| above, and then run 'module-assistant auto-install nvidia' after
| installing your kernel.
|
| You may find some useful troubleshooting tips for this driver at
| http://home.comcast.net/~andrex/Debian-nVidia/troubleshooting.html.
OK, I've been through everything I can think of:
boot parameters: acpi=off noapic pci=noacpi pci=biosirq
recompile kernel without any modules, without APIC
module-assistant auto-install nvidia
(kernel already compiled without 4K stacks)
(have not included rivafb)
the nvidia module installs fine but still get a blank screen.
I'm going off the nvidia hardware, my mother also cannot make it work.
Can see a graphics card purchase on the horizon...
Any suggestions in the meantime?
Thanks, Tim
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org
iD8DBQFBrllTsUUdIDHrdAURAvwlAKCyU61w9C6OlqhZvZ+B1X5oydU5cgCgi5f9
6AgK2m1DLGz4NDbep+ROg+Y=
=+HLH
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

compiled nvidia module fails

[Tim Beauregard]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello,

I am unable to use the nvidia module compiled from nvidia-kernel-source
that is used with the nvidia-glx package.  On boot-up, the computer
freezes when gdm starts.  The error message I get in the logs is

Failed to initialize the NVIDIA kernel module

This is using a 2.6.7 compiled kernel on Debian unstable system.

I have tried recompiling the kernel, as well as reinstalling the entire
system to no avail.  The nv module works fine.

I cannot obtain any more log messages as the computer freezes and
requires reboot, losing any messages before they are written to the hard
drive.

I think the problem started after an apt-get update/upgrade, the
nvidia-glx package may have been upgrade.

Has anyone else had trouble like this?  Any suggestions greatly appreciated.

Thanks,

Tim
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org

iD8DBQFBrOOssUUdIDHrdAURAqb1AKCDQA/hUkf/DCcNJXg+fZCeobCQTgCeIaw6
KhPxK7cSjPZjomo7kPWDXAM=
=8lI4
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: gnome-volume-manager + hal + udev + nvidia module

[mahashakti89]

On Tue, 08 Jun 2004 00:01:11 +0200
B e © k [EMAIL PROTECTED] wrote:

 Le 07.06.2004 21:10, *mahashakti89* nous contait:
 
 
  Je dois réinstaller le pilote , et au démarrage suivant même
  problème, plus de serveur X bien que le module soit présent.
 
 ca vient du module nvidia .
 
 http://linuxfr.org/~phpgml/10980.html
 

Effectif, il a l'air d'exister un patch, à voir ou mieux 
le prochain pilote NVidia. 

Merci

mahashakti


pgpJo7GNWUSEj.pgp
Description: PGP signature

gnome-volume-manager + hal + udev + nvidia module

[mahashakti89]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Bonjour !

J'ai essayé d'installer gnome-volume-manger + udev + hal, donc apt-get
install . , pas de problèmes, mais au redémarrage plus de serveur X
: failed to initialize NVIDIA module !
Je dois réinstaller le pilote , et au démarrage suivant même problème,
plus de serveur X bien que le module soit présent.

Donc apt-get --purge remove .. et tout est rentré dans l'ordre, mais
j'aimerais bien savoir pourquoi ça ne marche pas, une erreur de
configuration , un bug ??? Ou un paquet encore en phase de développement ?

Avez-vous une idée ou des tuyaux à ce sujet ??

Merci

mahashakti
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org

iD8DBQFAxLuOPPuyRSaD7LoRAhgOAJwKHyyDJU2KzNNZTpbGmrLnn4F4AACgpPOx
SaFlOM30XqxjrkGINjMyEWI=
=pqNe
-END PGP SIGNATURE-

Re: X refuses to load nVidia module

[Stephen Cormier]

On December 29, 2003 10:59 pm, Bradley Alexander wrote:
When I tried to load the module under 2.6.0, I got the message
  FATAL: Error inserting nvidia (/lib/modules/2.6.0/nvidia/nvidia.ko):
 Invalid module format


Starting with about test7 and onwards I had to us modprobe -f nvidia to 
get the module to load and then after that X would start.

Stephen


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: X refuses to load nVidia module

[csj]

On 31. December 2003 at 4:50AM -0400,
Stephen Cormier [EMAIL PROTECTED] wrote:

 On December 29, 2003 10:59 pm, Bradley Alexander wrote:

 When I tried to load the module under 2.6.0, I got the message
 FATAL: Error inserting nvidia
 (/lib/modules/2.6.0/nvidia/nvidia.ko): Invalid module format
 
 
 Starting with about test7 and onwards I had to us modprobe -f
 nvidia to get the module to load and then after that X would
 start.

Using make-kpkg, the nvidia-graphics-drivers package, linux 2.6
final and the linux 2.6 hacks, I remember needing to do
dpkg-reconfigure nvidia-glx and enabling something called TLS
support (threaded local storage?).  Of course I doubt if this
applies in this case.  I've not have any problems loading the
kernel part of the nvidia driver.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: X refuses to load nVidia module

[Bradley M Alexander]

On Mon, Dec 29, 2003 at 10:39:11PM -0700, Jamin W. Collins wrote:
 On Mon, Dec 29, 2003 at 09:59:58PM -0500, Bradley Alexander wrote:
  On Mon, 29 Dec 2003 14:32:08 -0700
  Jamin W. Collins [EMAIL PROTECTED] wrote:
   
   When you load the module manually, does it show in the output of lsmod?
  
  Yep. That was the first thing I checked when looking under 2.4.23.
  When I tried to load the module under 2.6.0, I got the message 
  
   FATAL: Error inserting nvidia (/lib/modules/2.6.0/nvidia/nvidia.ko):
  Invalid module format
  
  However, the module was loaded under 2.4.23...
 
 When the module would load, but X would fail to start, I found I had
 differing versions of nvidia-kernel and nvidia-glx installed on the
 system.  Are you sure you had the same version of both installed under
 2.4.23?

Yep. 4496 all around:

[EMAIL PROTECTED] root]# dpkg -l | grep nvidia
ii  nvidia-kernel- 1.0.4496-10+10 NVIDIA binary kernel module for Linux
2.4.23
ii  nvidia-kernel- 1.0.4496-10+10 NVIDIA binary kernel module for Linux
2.6.0
ii  nvidia-kernel- 1.0.4496-7 NVIDIA binary kernel module common files
ii  nvidia-kernel- 1.0.4496-10NVIDIA binary kernel module source


-- 
--Brad

Bradley M. Alexander|
gTLD SysAdmin, Security Engineer|   storm [at] tux.org
Debian/GNU Linux Developer  |   storm [at] debian.org

Key fingerprints:
DSA 0x54434E65: 37F6 BCA6 621D 920C E02E  E3C8 73B2 C019 5443 4E65
RSA 0xC3BCBA91: 3F 0E 26 C1 90 14 AD 0A  C8 9C F0 93 75 A0 01 34

I couldn't repair your brakes, so I made your horn louder.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

X refuses to load nVidia module

[Bradley M Alexander]

I just built a sid box from bare metal last week, and am having problems
getting the nVidia drivers to load. I tried this under 2.4.23 and 2.6.0,
and in both cases, the module refuses to load. At this point, I'm not sure
if it is a module loader problem or within X. X itself is reporting:

XFree86 Version 4.2.1.1 (Debian 4.2.1-14 20031113215638 [EMAIL PROTECTED]) / X Window 
System
(protocol Version 11, revision 0, vendor release 6600)
Release Date: 18 October 2002
...
Build Operating System: Linux 2.4.22-rc2 i686 [ELF] 
Module Loader present
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/XFree86.0.log, Time: Mon Dec 29 16:10:13 2003
(==) Using config file: /etc/X11/XF86Config-4

Then there pages of 

Not loading .note.GNU-stack
Not loading .note.GNU-stack

...and finally...

(EE) Failed to load module nvidia (module does not exist, 0)
Not loading .note.GNU-stack
(EE) No drivers available.

Fatal server error:
no screens found

This happens whether I load the module by hand or not. The nvidia devices
(nvidia[0123] and nvidiactl) exist in /dev.

Since this is happening on the 2.4 kernel as well as 2.6, it has to be a
common system, but I can't find the problem. The nv driver works fine,
though.

Any ideas?

Thanks,

-- 
--Brad

Bradley M. Alexander|
gTLD SysAdmin, Security Engineer|   storm [at] tux.org

Key fingerprints:
DSA 0x54434E65: 37F6 BCA6 621D 920C E02E  E3C8 73B2 C019 5443 4E65
RSA 0xC3BCBA91: 3F 0E 26 C1 90 14 AD 0A  C8 9C F0 93 75 A0 01 34

Your threat environment should dictate your security posture. You generally
don't see Mayberry-style small-town police forces toting automatic weapons
and anti-aircraft missiles. By the same token, a sling and stones hasn't
worked in a combat environment since David's time and he had God's help.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: X refuses to load nVidia module

[Jamin W. Collins]

On Mon, Dec 29, 2003 at 04:18:40PM -0500, Bradley M Alexander wrote:
 I just built a sid box from bare metal last week, and am having problems
 getting the nVidia drivers to load. I tried this under 2.4.23 and 2.6.0,
 and in both cases, the module refuses to load. At this point, I'm not sure
 if it is a module loader problem or within X. X itself is reporting:

Almost every box I own uses the nvidia driver.  How did you build the
driver?  Are you using the Debian packages?  If so, which version of the
packages (both nvidia-kernel and nvidia-glx)?

 This happens whether I load the module by hand or not. The nvidia devices
 (nvidia[0123] and nvidiactl) exist in /dev.

When you load the module manually, does it show in the output of lsmod?


-- 
Jamin W. Collins

Facts do not cease to exist because they are ignored. --Aldous Huxley,
Proper Studies, 1927


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: X refuses to load nVidia module

[Bradley Alexander]

On Mon, 29 Dec 2003 14:32:08 -0700
Jamin W. Collins [EMAIL PROTECTED] wrote:

 On Mon, Dec 29, 2003 at 04:18:40PM -0500, Bradley M Alexander wrote:
  I just built a sid box from bare metal last week, and am having
  problems getting the nVidia drivers to load. I tried this under 2.4.23
  and 2.6.0, and in both cases, the module refuses to load. At this
  point, I'm not sure if it is a module loader problem or within X. X
  itself is reporting:
 
 Almost every box I own uses the nvidia driver.  How did you build the
 driver?  Are you using the Debian packages?  If so, which version of the
 packages (both nvidia-kernel and nvidia-glx)?

Same here. This particular box, however, was just built last week using
the new sarge netinst CD. I'm running the 4496 packages on all of them. I
build the kernel and driver the Debian way. Untar the kernel source, make
menuconfig, make-kpkg kernel_image. For the modules, I make-kpkg modules.
In this case, I untarred the nvidia-kernel-source.tar.gz tarball, ran the
2.6 patch before doing the make-kpkg modules.

  This happens whether I load the module by hand or not. The nvidia
  devices(nvidia[0123] and nvidiactl) exist in /dev.
 
 When you load the module manually, does it show in the output of lsmod?

Yep. That was the first thing I checked when looking under 2.4.23.
When I tried to load the module under 2.6.0, I got the message 

 FATAL: Error inserting nvidia (/lib/modules/2.6.0/nvidia/nvidia.ko):
Invalid module format

However, the module was loaded under 2.4.23...

 
 -- 
 Jamin W. Collins
 
 Facts do not cease to exist because they are ignored. --Aldous Huxley,
 Proper Studies, 1927
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
 with a subject of unsubscribe. Trouble? Contact
 [EMAIL PROTECTED]


-- 
--Brad

Bradley M. Alexander|
gTLD SysAdmin, Security Engineer|   storm [at] tux.org
Debian/GNU Linux Developer  |   storm [at] debian.org

Key fingerprints:
DSA 0x54434E65: 37F6 BCA6 621D 920C E02E  E3C8 73B2 C019 5443 4E65
RSA 0xC3BCBA91: 3F 0E 26 C1 90 14 AD 0A  C8 9C F0 93 75 A0 01 34

Oh yeah, you go to pieces so fast that people get hit by the shrapnel.
--Ford Prefect


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: X refuses to load nVidia module

[Jamin W. Collins]

On Mon, Dec 29, 2003 at 09:59:58PM -0500, Bradley Alexander wrote:
 On Mon, 29 Dec 2003 14:32:08 -0700
 Jamin W. Collins [EMAIL PROTECTED] wrote:
  
  When you load the module manually, does it show in the output of lsmod?
 
 Yep. That was the first thing I checked when looking under 2.4.23.
 When I tried to load the module under 2.6.0, I got the message 
 
  FATAL: Error inserting nvidia (/lib/modules/2.6.0/nvidia/nvidia.ko):
 Invalid module format
 
 However, the module was loaded under 2.4.23...

When the module would load, but X would fail to start, I found I had
differing versions of nvidia-kernel and nvidia-glx installed on the
system.  Are you sure you had the same version of both installed under
2.4.23?

-- 
Jamin W. Collins

Linux is not The Answer. Yes is the answer. Linux is The Question. - Neo


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: nvidia module load problems

[Nic Strong]

On Fri, 2003-02-07 at 16:54, Alan Thompson wrote:
 On Sat, Feb 08, 2003 at 12:26:29AM +, Nic Strong wrote:
  Hi,
  
  Ever since compiling 2.4.20 kernel and the nvidia module/glx (4191)
  whenever I start x the nvidia module does not auto load i have to do an
  explicit 'insmod nvidia' (i never had to do this in the past).
  
  /etc/modules has the following lines:
  
  ### update-modules: start processing /etc/modutils/nvidia-kernel-2.4.20
  alias /dev/nvidia* nvidia
  alias char-major-195 nvidia
  ### update-modules: end processing /etc/modutils/nvidia-kernel-2.4.20
 
 Make sure you don't also have any stray lines refering to the old
 NVdriver module.  I had this a couple of days ago; I tend to keep a
 lot of old kernels around, so I also had the nvidia module package for
 each kernel installed.  So, while I had the correct line, I also had
 several lines like:
 
 ### update-modules: start processing /etc/modutils/nvidia-kernel-2.4.4
 alias char-major-195 NVdriver
 ### update-modules: end processing /etc/modutils/nvidia-kernel-2.4.4
 
 which confused things.  Getting rid of the wrong ones got it working
 right.  I should probably tidy up in general, I doubt I'll ever need
 to boot 2.4.4. again!
 
 Cheers, 
 
 A.
 
 -- 
 Alan Thompson

Thanks for all the help every one. It turned out it was the reference to
the old module name in /etc/modules that was causing the problem.

Cheers,
-- 
Nic Strong [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

nvidia module load problems

[Nic Strong]

Hi,

Ever since compiling 2.4.20 kernel and the nvidia module/glx (4191)
whenever I start x the nvidia module does not auto load i have to do an
explicit 'insmod nvidia' (i never had to do this in the past).

/etc/modules has the following lines:

### update-modules: start processing /etc/modutils/nvidia-kernel-2.4.20
alias /dev/nvidia* nvidia
alias char-major-195 nvidia
### update-modules: end processing /etc/modutils/nvidia-kernel-2.4.20

So I assume update-modules is working correctly ? Any ideas
?
Cheers,
-- 
Nic Strong [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: nvidia module load problems

[Steve Johnson]

I'm running 2.4.20/woody/nv(4191) and mine works fine, the only
difference I can see is that I didn't bother with any of the aliases.
I just have this in /etc/modules

# /etc/modules: kernel modules to load at boot time.
#
# This file should contain the names of kernel modules that are
# to be loaded at boot time, one per line.  Comments begin with
# a #, and everything on the line after them are ignored.
nvidia



-Luck

On Fri, 2003-02-07 at 18:26, Nic Strong wrote:
 Hi,
 
 Ever since compiling 2.4.20 kernel and the nvidia module/glx (4191)
 whenever I start x the nvidia module does not auto load i have to do an
 explicit 'insmod nvidia' (i never had to do this in the past).
 
 /etc/modules has the following lines:
 
 ### update-modules: start processing /etc/modutils/nvidia-kernel-2.4.20
 alias /dev/nvidia* nvidia
 alias char-major-195 nvidia
 ### update-modules: end processing /etc/modutils/nvidia-kernel-2.4.20
 
 So I assume update-modules is working correctly ? Any ideas
 ?
 Cheers,
 -- 
 Nic Strong [EMAIL PROTECTED]
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
-- 
You can get my public key at http://steve.webninja.com
or search for KeyID 0x0F737450 at www.keyserver.net



signature.asc
Description: This is a digitally signed message part

Re: nvidia module load problems

[Lacoste (Frisurf)]

Perhaps a stupid question, since your system seemed to work before you
used 2.4.20.

I think it is X that loads the kernel when reading the XF86Config.
What does your XF86config contain?

Mine has 

Section Device
Identifier  NVIDIA Corporation GeForce2 Go [NV11]
Driver  nvidia
BusID   PCI:01:00:0
EndSection


With:
root@expresso lspci | grep -i nvidia
01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 Go]
(rev b2)

Hope it helps.




Regarding 2.4.20 and nvidia 4191, I have performance problems since I
- kernel upgraded from 2.4.18 gcc 2.95 to 2.4.20 3.2.2 (self compiled)
- nvidia 2960 to 4191 (compiled 
- gnome 2.2

Nautilus takes several seconds to update itself when switching
workspace. It didn't with former installation.


Jerome


On Sat, 2003-02-08 at 01:26, Nic Strong wrote:
 Hi,
 
 Ever since compiling 2.4.20 kernel and the nvidia module/glx (4191)
 whenever I start x the nvidia module does not auto load i have to do an
 explicit 'insmod nvidia' (i never had to do this in the past).
 
 /etc/modules has the following lines:
 
 ### update-modules: start processing /etc/modutils/nvidia-kernel-2.4.20
 alias /dev/nvidia* nvidia
 alias char-major-195 nvidia
 ### update-modules: end processing /etc/modutils/nvidia-kernel-2.4.20
 
 So I assume update-modules is working correctly ? Any ideas
 ?
 Cheers,
 -- 
 Nic Strong [EMAIL PROTECTED]
-- 
Jerome Lacoste (Frisurf) [EMAIL PROTECTED]
CoffeeBreaks


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]