[pkg-nvidia-devel] Bug#580894: nvidia-kernel-common: no conflict between nouveau and nvidia on G84M [Quadro NVS 140M]

Andreas Beckmann debian at abeckmann.de
Mon May 17 14:37:32 UTC 2010

Package: nvidia-kernel-common
Version: 20100216+3+nmu1
Severity: normal

I just checked on my laptop with a G84M [Quadro NVS 140M] GPU and found
that I had both nvidia.ko (first) and nouveau.ko (later) loaded without
gettiny any problems. Manually unloading both and thereafter loading
nouveau first switched the system to a nouveau framebuffer console, a
nouveau.ko module no longer being removable and an nvidia.ko that could
not be loaded because nouveau.ko already had claimed the GPU (till the
next reboot). I'm not sure what defined the load order during boot,
neither of the modules is listed in /etc/modules.


-- System Information:
Debian Release: squeeze/sid
  APT prefers stable
  APT policy: (800, 'stable'), (700, 'testing'), (600, 'unstable'), (130, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages nvidia-kernel-common depends on:
ii  module-init-tools            3.12~pre2-3 tools for managing Linux kernel mo

nvidia-kernel-common recommends no packages.

nvidia-kernel-common suggests no packages.

-- no debconf information

More information about the Pkg-nvidia-devel mailing list