15/05/2011 11:23, Camaleón wrote:
> On Sun, 15 May 2011 10:07:25 +0100, Brad Rogers wrote:
>
>> On Sun, 15 May 2011 08:37:43 +0000 (UTC) Camaleón <noelamac@gmail.com>
>> wrote:
>>
>> Hello Camaleón,
>
> (replying to your e-mail but also addressed to tv.debian's)
>
>>> Just a quick note on nvidia (or ati) proprietary drivers: they need the
>>> corresponding kernel version package.
>>
>> Whilst what you say is true, a lot of the agony of installing nVidia
>> drivers can be done away with by installing the nvidia-kernel-dkms
>> package and associated dependencies.
>>
>> Doing that takes care of all the kernel dependant rebuilds of the
>> driver, meaning that the sys-admin (me) doesn't have to remember to do
>> it.
>
> :-)
>
> Don't ask me why -maybe due to inexperience-, but the first time I had to
> deal with the closed nvidia driver in Debian I prefered¹ to not use
> "dkms" and manually pulled the required packages which was the method I
> was more used to. Hopefully, all went ok.
>
> And the same goes for my VirtuaBox client. Whenever I have to install or
> update the "guest additions" I prefer to manually update the kernel
> headers (which I hope they get automatically updated now that I've
> installed the kernel meta-package).
>
> ¹I didn't know how this thingy worked, it is something I never used in
> openSUSE, the distro I was using before coming to Debian.
>
> Greetings,
>

I was a great fan of module-assistant, but since dkms entered Debian I
don't miss m-a ! Give it a try, especially when using custom kernels it
saves a lot of time for more interesting things than compiling modules.
The only downside I see is philosophical, it makes using proprietary
modules far too easy, there used to be some kind of redemption in the
manual compilation suffering ;-)


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4DCFA39D.4030106@googlemail.com">http://lists.debian.org/4DCFA39D.4030106@googlemail.com

On Sun, 15 May 2011 09:23:45 +0000 (UTC)
Camaleón <noelamac@gmail.com> wrote:

> Don't ask me why -maybe due to inexperience-, but the first time I had

Inexperience? You? Unfamiliar, perhaps.

> to deal with the closed nvidia driver in Debian I prefered¹ to not use
> "dkms" and manually pulled the required packages which was the method
> I was more used to. Hopefully, all went ok.

I was glad when DKMS came along as it meant I didn't have to turn the X
server off to perform the necessary incantations to get the latest
nVidia driver installed and working. This mainly because, at that time,
I didn't understand xorg, kernel modules and so forth well enough to get
myself out of trouble, if the worse happened.

I'm no expert now, but at least I have an idea of what to do. Also,
I've now got a spare machine to get online with to search/ask for
assistance, if it's required.

> headers (which I hope they get automatically updated now that I've
> installed the kernel meta-package).

If they don't, file a bug report. :-)

> ¹I didn't know how this thingy worked, it is something I never used in
> openSUSE, the distro I was using before coming to Debian.

No surprise there. The D in DKMS stands for "Debian", after all. :-)

--
Regards _
/ ) "The blindingly obvious is
/ _)rad never immediately apparent"
No guarantee the stimuli must be perceived the same...
Gary Gilmore's Eyes - The Adverts

15/05/2011 12:10, Brad Rogers wrote:
>> On Sun, 15 May 2011 09:23:45 +0000 (UTC)
>> Camaleón <noelamac@gmail.com> wrote:

[snip]

>> ¹I didn't know how this thingy worked, it is something I never used in
>> openSUSE, the distro I was using before coming to Debian.
>
> No surprise there. The D in DKMS stands for "Debian", after all. :-)
>

More like "Dell" who first developed it, it is supposed to really stands
for "Dynamic". I may very well be wrong but I think it appears in Ubuntu
before it made it's way into Debian, a case of "reverse upstream relation".


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4DCFC353.5070702@googlemail.com">http://lists.debian.org/4DCFC353.5070702@googlemail.com

On Sun, 15 May 2011 14:13:07 +0200
"tv.debian@googlemail.com" <tv.debian@googlemail.com> wrote:

Hello tv.debian@googlemail.com,

> More like "Dell" who first developed it, it is supposed to really
> stands for "Dynamic". I may very well be wrong but I think it appears

You're right; I don't what made me think it was Debian. :-/

--
Regards _
/ ) "The blindingly obvious is
/ _)rad never immediately apparent"
Sign away your life
Tin Soldiers - Stiff Little Fingers

On Du, 15 mai 11, 11:57:49, tv.debian@googlemail.com wrote:
> >
> > ¹I didn't know how this thingy worked, it is something I never used in
> > openSUSE, the distro I was using before coming to Debian.

openSUSE should now have DKMS as well[1]

> I was a great fan of module-assistant, but since dkms entered Debian I
> don't miss m-a ! Give it a try, especially when using custom kernels it
> saves a lot of time for more interesting things than compiling modules.
> The only downside I see is philosophical, it makes using proprietary
> modules far too easy, there used to be some kind of redemption in the
> manual compilation suffering ;-)

There are still things missing, like #583580 and the ability to build a
deb to install on another machine, very useful if one has to install
OOT[2] kernel modules on machines which shouldn't/can't have a compiler
installed.

[1] at least according to Wikipedia
http://en.wikipedia.org/wiki/Dynamic_Kernel_Module_Support
[3] Out of Tree

Regards,
Andrei
--
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic

On Sun, 15 May 2011 19:57:33 +0300, Andrei Popescu wrote:

> On Du, 15 mai 11, 11:57:49, tv.debian@googlemail.com wrote:
>> >
>> > ¹I didn't know how this thingy worked, it is something I never used
>> > in openSUSE, the distro I was using before coming to Debian.
>
> openSUSE should now have DKMS as well[1]

Err, the above paragraph was mine ;-)

And yes, dkms is available under openSUSE OBS (their Build Service) but
I've never heard of anyone using it (and I've been using openSUSE from
2003 up to 2010) >;-)

(...)

> [1] at least according to Wikipedia
> http://en.wikipedia.org/wiki/Dynamic_Kernel_Module_Support

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: pan.2011.05.15.17.58.30@gmail.com">http://lists.debian.org/pan.2011.05.15.17.58.30@gmail.com

Russell L. Carter wrote:

Hi Curt,

On 05/14/2011 07:00 PM, Curt Howland wrote:

I've found that I have to re-install the binary Nvidia driver often
after updates, when the X system gets updated, due to changes to
simlinks.

If you're using the Nvidia binary driver, try reinstalling it.


I did that.


<snip>

The current Nvidia binary driver is 270.41.06, you tried reinstalling
that one?


Hugo


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

Archive: iqp4nm$skk$1@dough.gmane.org">http://lists.debian.org/iqp4nm$skk$1@dough.gmane.org

On Du, 15 mai 11, 17:58:30, Camaleón wrote:
> On Sun, 15 May 2011 19:57:33 +0300, Andrei Popescu wrote:
>
> > On Du, 15 mai 11, 11:57:49, tv.debian@googlemail.com wrote:
> >> >
> >> > ¹I didn't know how this thingy worked, it is something I never used
> >> > in openSUSE, the distro I was using before coming to Debian.
> >
> > openSUSE should now have DKMS as well[1]
>
> Err, the above paragraph was mine ;-)

Yes, I know Camaleón, I just snipped the relevant attribution line
(sorry tv.debian

Regards,
Andrei
P.S. at least this time I got the accent right
--
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic

First, thanks much to the people on the other side of the globe who
see a new day before me. I have dug deeper and can now get more specific
about the nvidia blank screen problem. (For the record, I have a
fixed hardware config that I've tracked debian-testing on for two
years, and also tracking nvidia drivers. I used to just download
them from nvidia.com but for the past few months I've been using
dkms, which has worked beautifully.)

Thanks to tv.debian for reminding me that nouveau might be
blacklisted. It turns out that it was, in the file

/etc/modprobe.d/nvidia-installer-disable-nouveau.conf

I had the nouveau packages installed:

root@feyerabend:/etc/modprobe.d# dpkg -l | grep nouveau
ii libdrm-nouveau1a 2.4.24-2 Userspace
interface to nouveau-specific kernel DRM services -- runtime
ii xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 X.Org X
server -- Nouveau display driver (experimental)

so when I rm'd the blacklist file the gdm3 greeter popped up and X is
up and running. This proves the hardware is working (or at least not
completely broken).

I don't have the ability to make a choice between nvidia vs. nouveau, I
make a living with high performance numerical algorithms, including GPU
programming, so my only choice is between Linux and Windows. Ok?
I would be a very unhappy man on Windows, so I'll forge on.

So next I install the current nvidia dkms packages. I've removed
everything that's normal output:

root@feyerabend:~# apt-get autoremove --purge xserver-xorg-video-nouveau
libdrm-nouveau1a

since the nouveau module is still loaded I reboot, and return to a
console prompt with no X. Next I'll install the nvidia packages.
Note that the modprobe blows up. After the apt-get install output
I'll append the traceback the showed up in /var/log/messages.

(The recent memcpy/memmove issue is orthogonal to kernel modules,
right?)

root@feyerabend:~# apt-get install nvidia-kernel-dkms nvidia-glx
nvidia-kernel-270.41.06 nvidia-settings
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'nvidia-kernel-dkms' instead of 'nvidia-kernel-270.41.06'
The following NEW packages will be installed:
nvidia-glx nvidia-kernel-dkms nvidia-settings
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/12.8 MB of archives.
After this operation, 41.2 MB of additional disk space will be used.
Selecting previously deselected package nvidia-kernel-dkms.
(Reading database ... 204047 files and directories currently installed.)
Unpacking nvidia-kernel-dkms (from .../nvidia-kernel-dkms_270.41.06-1_amd64.deb) ...
Selecting previously deselected package nvidia-glx.
Unpacking nvidia-glx (from .../nvidia-glx_270.41.06-1_amd64.deb) ...
Selecting previously deselected package nvidia-settings.
Unpacking nvidia-settings (from .../nvidia-settings_195.36.24-1_amd64.deb) ...
Processing triggers for man-db ...
Processing triggers for menu ...
Setting up nvidia-kernel-dkms (270.41.06-1) ...
Loading new nvidia-270.41.06 DKMS files...
First Installation: checking all kernels...
Building only for 2.6.38-2-amd64
Building initial module for 2.6.38-2-amd64
Done.

nvidia.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/2.6.38-2-amd64/updates/dkms/

depmod...
Message from syslogd@feyerabend at May 15 11:35:38 ...
kernel:[ 177.226221] Oops: 0000 [#1] SMP

Message from syslogd@feyerabend at May 15 11:35:38 ...
kernel:[ 177.226223] last sysfs file: /sys/bus/acpi/drivers/NVIDIA ACPI Video
Driver/uevent

Message from syslogd@feyerabend at May 15 11:35:38 ...
kernel:[ 177.226406] Stack:

Message from syslogd@feyerabend at May 15 11:35:38 ...
kernel:[ 177.226416] Call Trace:

Message from syslogd@feyerabend at May 15 11:35:38 ...
kernel:[ 177.226841] Code: 00 ba 00 00 00 00 be 3c 00 00 00 41 ff 55 20 48 89
c3 b9 01 00 00 00 ba 00 00 00 00 be 15 00 00 00 4c 89 ef 41 ff 55 20 49 89 c6
<48> 8b 05 f7 6a c6 00 48 89 45 10 8b 05 f5 6a c6 00 89 45 18 0f

Message from syslogd@feyerabend at May 15 11:35:38 ...
kernel:[ 177.226980] CR2: ffffffffa129b076

Message from syslogd@feyerabend at May 15 11:35:38 ...
kernel:[ 177.226221] Oops: 0000 [#1] SMP

Message from syslogd@feyerabend at May 15 11:35:38 ...
kernel:[ 177.226223] last sysfs file: /sys/bus/acpi/drivers/NVIDIA ACPI Video
Driver/uevent

Message from syslogd@feyerabend at May 15 11:35:38 ...
kernel:[ 177.226406] Stack:

Message from syslogd@feyerabend at May 15 11:35:38 ...
kernel:[ 177.226416] Call Trace:

Message from syslogd@feyerabend at May 15 11:35:38 ...
kernel:[ 177.226841] Code: 00 ba 00 00 00 00 be 3c 00 00 00 41 ff 55 20 48 89
c3 b9 01 00 00 00 ba 00 00 00 00 be 15 00 00 00 4c 89 ef 41 ff 55 20 49 89 c6
<48> 8b 05 f7 6a c6 00 48 89 45 10 8b 05 f5 6a c6 00 89 45 18 0f

Message from syslogd@feyerabend at May 15 11:35:38 ...
kernel:[ 177.226980] CR2: ffffffffa129b076
.

DKMS: install Completed.
Setting up nvidia-glx (270.41.06-1) ...
No diversion 'diversion of /usr/lib/xorg/modules/extensions/libGLcore.so to
/usr/lib/nvidia/libGLcore.so.xlibmesa by nvidia-glx', none removed.
No diversion 'diversion of /usr/lib/xorg/modules/extensions/libGLcore.a to
/usr/lib/nvidia/libGLcore.a.xlibmesa by nvidia-glx', none removed.
No diversion 'diversion of /usr/lib/xorg/modules/extensions/libglx.a to
/usr/lib/nvidia/libglx.a.xlibmesa by nvidia-glx', none removed.
update-alternatives: using /usr/lib/nvidia/libglx.so to provide
/usr/lib/xorg/modules/extensions/libglx.so (libglx.so) in auto mode.
Setting up nvidia-settings (195.36.24-1) ...
Processing triggers for libgl1-nvidia-alternatives ...
Processing triggers for menu ...
root@feyerabend:~#

/var/log/messages traceback:

May 15 11:35:37 feyerabend kernel: [ 176.396112] Disabling lock debugging due
to kernel taint
May 15 11:35:37 feyerabend kernel: [ 176.396117] nvidia: module license
'NVIDIA' taints kernel.
May 15 11:35:38 feyerabend kernel: [ 177.178623] nvidia 0000:01:00.0: PCI INT A
-> GSI 16 (level, low) -> IRQ 16
May 15 11:35:38 feyerabend kernel: [ 177.178637] vgaarb: device changed
decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=nonew ns=
io+mem
May 15 11:35:38 feyerabend kernel: [ 177.178734] NVRM: loading NVIDIA UNIX
x86_64 Kernel Module 270.41.06 Mon Apr 18 14:53:56 PDT 20
11
May 15 11:35:38 feyerabend kernel: [ 177.226218] PGD 1605067 PUD 1609063 PMD 0
May 15 11:35:38 feyerabend kernel: [ 177.226225] CPU 0
May 15 11:35:38 feyerabend kernel: [ 177.226226] Modules linked in: nvidia(P)
acpi_cpufreq mperf parport_pc ppdev lp parport cpufreq_s
tats cpufreq_conservative cpufreq_powersave cpufreq_userspace fuse nfsd nfs
lockd fscache nfs_acl auth_rpcgss sunrpc xfs exportfs ext2
loop usbhid hid snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep
snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_midi snd_rawmidi
snd_seq_midi_event snd_seq evdev snd_timer snd_seq_device tpm_tis tpm tpm_bios
psmouse snd i2c_i801 serio_raw i2c_core x38_edac soundco
re snd_page_alloc pcspkr edac_core processor button ext4 mbcache jbd2 crc16
dm_mod sg sd_mod sr_mod cdrom crc_t10dif uhci_hcd fan ahci
libahci sky2 libata ehci_hcd scsi_mod thermal usbcore thermal_sys nls_base [last
unloaded: scsi_wait_scan]
May 15 11:35:38 feyerabend kernel: [ 177.226262]
May 15 11:35:38 feyerabend kernel: [ 177.226264] Pid: 4609, comm: Xorg Tainted:
P O 2.6.38-2-amd64 #1 OEM OEM/LP LT X48-T3RS
May 15 11:35:38 feyerabend kernel: [ 177.226267] RIP: 0010:[<ffffffffa0634578>]
[<ffffffffa0634578>] _nv028301rm+0x44/0x176 [nvidia]
May 15 11:35:38 feyerabend kernel: [ 177.226386] RSP: 0018:ffff8802245dfb88
EFLAGS: 00010282
May 15 11:35:38 feyerabend kernel: [ 177.226388] RAX: ffff8801fc94c000 RBX:
ffff880223a9a000 RCX: 0000000000000001
May 15 11:35:38 feyerabend kernel: [ 177.226389] RDX: ffff8801fc94c000 RSI:
0000000000000015 RDI: ffff880224874000
May 15 11:35:38 feyerabend kernel: [ 177.226391] RBP: ffff880225955f68 R08:
ffff8801fd690000 R09: ffff880225955f78
May 15 11:35:38 feyerabend kernel: [ 177.226393] R10: ffff88022f8026c0 R11:
0000000000000077 R12: ffff880224688000
May 15 11:35:38 feyerabend kernel: [ 177.226394] R13: ffff880224874000 R14:
ffff8801fc94c000 R15: ffff880224648800
May 15 11:35:38 feyerabend kernel: [ 177.226396] FS: 00007f2732c77880(0000)
GS:ffff8800cfc00000(0000) knlGS:0000000000000000
May 15 11:35:38 feyerabend kernel: [ 177.226398] CS: 0010 DS: 0000 ES: 0000
CR0: 0000000080050033
May 15 11:35:38 feyerabend kernel: [ 177.226400] CR2: ffffffffa129b076 CR3:
000000022442a000 CR4: 00000000000406f0
May 15 11:35:38 feyerabend kernel: [ 177.226401] DR0: 0000000000000000 DR1:
0000000000000000 DR2: 0000000000000000
May 15 11:35:38 feyerabend kernel: [ 177.226403] DR3: 0000000000000000 DR6:
00000000ffff0ff0 DR7: 0000000000000400
May 15 11:35:38 feyerabend kernel: [ 177.226405] Process Xorg (pid: 4609,
threadinfo ffff8802245de000, task ffff880224bb4a40)
May 15 11:35:38 feyerabend kernel: [ 177.226407] ffffc90011893000
ffff880224874000 ffff880225955fe8 ffff880224688000
May 15 11:35:38 feyerabend kernel: [ 177.226411] ffffc90011893000
ffffffffa09dc95b ffff8801fc94c000 ffff880224648800
May 15 11:35:38 feyerabend kernel: [ 177.226413] ffff880224874000
ffffc90011893000 ffff8802239e4000 ffffffffa09dd983
May 15 11:35:38 feyerabend kernel: [ 177.226517] [<ffffffffa09dc95b>] ?
_nv002401rm+0x218/0x260 [nvidia]
May 15 11:35:38 feyerabend kernel: [ 177.226614] [<ffffffffa09dd983>] ?
_nv002394rm+0x41b/0x685 [nvidia]
May 15 11:35:38 feyerabend kernel: [ 177.226711] [<ffffffffa09e351d>] ?
rm_init_adapter+0x9d/0x111 [nvidia]
May 15 11:35:38 feyerabend kernel: [ 177.226808] [<ffffffffa0a00699>] ?
nv_kern_open+0x49a/0x603 [nvidia]
May 15 11:35:38 feyerabend kernel: [ 177.226812] [<ffffffff810fa480>] ?
exact_match+0x0/0x4
May 15 11:35:38 feyerabend kernel: [ 177.226814] [<ffffffff810fa802>] ?
chrdev_open+0x12a/0x148
May 15 11:35:38 feyerabend kernel: [ 177.226817] [<ffffffff810fa6d8>] ?
chrdev_open+0x0/0x148
May 15 11:35:38 feyerabend kernel: [ 177.226819] [<ffffffff810f642a>] ?
__dentry_open+0x15a/0x271
May 15 11:35:38 feyerabend kernel: [ 177.226821] [<ffffffff810ff637>] ?
dget+0x12/0x1e
May 15 11:35:38 feyerabend kernel: [ 177.226824] [<ffffffff811013e6>] ?
finish_open+0x97/0x15f
May 15 11:35:38 feyerabend kernel: [ 177.226826] [<ffffffff81102412>] ?
do_path_lookup+0x5d/0xfc
May 15 11:35:38 feyerabend kernel: [ 177.226828] [<ffffffff81103162>] ?
do_filp_open+0x171/0x5be
May 15 11:35:38 feyerabend kernel: [ 177.226831] [<ffffffff8110b58e>] ?
setattr_copy+0x98/0xd7
May 15 11:35:38 feyerabend kernel: [ 177.226833] [<ffffffff810f6752>] ?
chown_common+0x90/0x9b
May 15 11:35:38 feyerabend kernel: [ 177.226835] [<ffffffff8110bee4>] ?
alloc_fd+0x69/0x10b
May 15 11:35:38 feyerabend kernel: [ 177.226837] [<ffffffff810f620f>] ?
do_sys_open+0x56/0xda
May 15 11:35:38 feyerabend kernel: [ 177.226840] [<ffffffff81009952>] ?
system_call_fastpath+0x16/0x1b
May 15 11:35:38 feyerabend kernel: [ 177.226979] RSP <ffff8802245dfb88>
May 15 11:35:38 feyerabend kernel: [ 177.226982] ---[ end trace
58be261eea03ecf3 ]---
root@feyerabend:~#

[end of message]


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4DD020ED.3040100@pinyon.org">http://lists.debian.org/4DD020ED.3040100@pinyon.org

I left out the step of replacing Driver="nouveau" with Driver="nvidia"
in /etc/X11/xorg.conf, sorry.

On 05/15/2011 11:52 AM, Russell L. Carter wrote:
>
> First, thanks much to the people on the other side of the globe who
> see a new day before me. I have dug deeper and can now get more specific
> about the nvidia blank screen problem. (For the record, I have a
> fixed hardware config that I've tracked debian-testing on for two
> years, and also tracking nvidia drivers. I used to just download
> them from nvidia.com but for the past few months I've been using
> dkms, which has worked beautifully.)
>
> Thanks to tv.debian for reminding me that nouveau might be
> blacklisted. It turns out that it was, in the file
>
> /etc/modprobe.d/nvidia-installer-disable-nouveau.conf
>
> I had the nouveau packages installed:
>
> root@feyerabend:/etc/modprobe.d# dpkg -l | grep nouveau
> ii libdrm-nouveau1a 2.4.24-2 Userspace
> interface to nouveau-specific kernel DRM services -- runtime
> ii xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 X.Org X
> server -- Nouveau display driver (experimental)
>
> so when I rm'd the blacklist file the gdm3 greeter popped up and X is
> up and running. This proves the hardware is working (or at least not
> completely broken).
>
> I don't have the ability to make a choice between nvidia vs. nouveau, I
> make a living with high performance numerical algorithms, including GPU
> programming, so my only choice is between Linux and Windows. Ok?
> I would be a very unhappy man on Windows, so I'll forge on.
>
> So next I install the current nvidia dkms packages. I've removed
> everything that's normal output:
>
> root@feyerabend:~# apt-get autoremove --purge xserver-xorg-video-nouveau
> libdrm-nouveau1a
>
> since the nouveau module is still loaded I reboot, and return to a
> console prompt with no X. Next I'll install the nvidia packages.
> Note that the modprobe blows up. After the apt-get install output
> I'll append the traceback the showed up in /var/log/messages.
>
> (The recent memcpy/memmove issue is orthogonal to kernel modules,
> right?)
>
> root@feyerabend:~# apt-get install nvidia-kernel-dkms nvidia-glx
> nvidia-kernel-270.41.06 nvidia-settings
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Note, selecting 'nvidia-kernel-dkms' instead of 'nvidia-kernel-270.41.06'
> The following NEW packages will be installed:
> nvidia-glx nvidia-kernel-dkms nvidia-settings
> 0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
> Need to get 0 B/12.8 MB of archives.
> After this operation, 41.2 MB of additional disk space will be used.
> Selecting previously deselected package nvidia-kernel-dkms.
> (Reading database ... 204047 files and directories currently installed.)
> Unpacking nvidia-kernel-dkms (from .../nvidia-kernel-dkms_270.41.06-1_amd64.deb) ...
> Selecting previously deselected package nvidia-glx.
> Unpacking nvidia-glx (from .../nvidia-glx_270.41.06-1_amd64.deb) ...
> Selecting previously deselected package nvidia-settings.
> Unpacking nvidia-settings (from .../nvidia-settings_195.36.24-1_amd64.deb) ...
> Processing triggers for man-db ...
> Processing triggers for menu ...
> Setting up nvidia-kernel-dkms (270.41.06-1) ...
> Loading new nvidia-270.41.06 DKMS files...
> First Installation: checking all kernels...
> Building only for 2.6.38-2-amd64
> Building initial module for 2.6.38-2-amd64
> Done.
>
> nvidia.ko:
> Running module version sanity check.
> - Original module
> - No original module exists within this kernel
> - Installation
> - Installing to /lib/modules/2.6.38-2-amd64/updates/dkms/
>
> depmod...
> Message from syslogd@feyerabend at May 15 11:35:38 ...
> kernel:[ 177.226221] Oops: 0000 [#1] SMP
>
> Message from syslogd@feyerabend at May 15 11:35:38 ...
> kernel:[ 177.226223] last sysfs file: /sys/bus/acpi/drivers/NVIDIA ACPI Video
> Driver/uevent
>
> Message from syslogd@feyerabend at May 15 11:35:38 ...
> kernel:[ 177.226406] Stack:
>
> Message from syslogd@feyerabend at May 15 11:35:38 ...
> kernel:[ 177.226416] Call Trace:
>
> Message from syslogd@feyerabend at May 15 11:35:38 ...
> kernel:[ 177.226841] Code: 00 ba 00 00 00 00 be 3c 00 00 00 41 ff 55 20 48 89
> c3 b9 01 00 00 00 ba 00 00 00 00 be 15 00 00 00 4c 89 ef 41 ff 55 20 49 89 c6
> <48> 8b 05 f7 6a c6 00 48 89 45 10 8b 05 f5 6a c6 00 89 45 18 0f
>
> Message from syslogd@feyerabend at May 15 11:35:38 ...
> kernel:[ 177.226980] CR2: ffffffffa129b076
>
> Message from syslogd@feyerabend at May 15 11:35:38 ...
> kernel:[ 177.226221] Oops: 0000 [#1] SMP
>
> Message from syslogd@feyerabend at May 15 11:35:38 ...
> kernel:[ 177.226223] last sysfs file: /sys/bus/acpi/drivers/NVIDIA ACPI Video
> Driver/uevent
>
> Message from syslogd@feyerabend at May 15 11:35:38 ...
> kernel:[ 177.226406] Stack:
>
> Message from syslogd@feyerabend at May 15 11:35:38 ...
> kernel:[ 177.226416] Call Trace:
>
> Message from syslogd@feyerabend at May 15 11:35:38 ...
> kernel:[ 177.226841] Code: 00 ba 00 00 00 00 be 3c 00 00 00 41 ff 55 20 48 89
> c3 b9 01 00 00 00 ba 00 00 00 00 be 15 00 00 00 4c 89 ef 41 ff 55 20 49 89 c6
> <48> 8b 05 f7 6a c6 00 48 89 45 10 8b 05 f5 6a c6 00 89 45 18 0f
>
> Message from syslogd@feyerabend at May 15 11:35:38 ...
> kernel:[ 177.226980] CR2: ffffffffa129b076
> .
>
> DKMS: install Completed.
> Setting up nvidia-glx (270.41.06-1) ...
> No diversion 'diversion of /usr/lib/xorg/modules/extensions/libGLcore.so to
> /usr/lib/nvidia/libGLcore.so.xlibmesa by nvidia-glx', none removed.
> No diversion 'diversion of /usr/lib/xorg/modules/extensions/libGLcore.a to
> /usr/lib/nvidia/libGLcore.a.xlibmesa by nvidia-glx', none removed.
> No diversion 'diversion of /usr/lib/xorg/modules/extensions/libglx.a to
> /usr/lib/nvidia/libglx.a.xlibmesa by nvidia-glx', none removed.
> update-alternatives: using /usr/lib/nvidia/libglx.so to provide
> /usr/lib/xorg/modules/extensions/libglx.so (libglx.so) in auto mode.
> Setting up nvidia-settings (195.36.24-1) ...
> Processing triggers for libgl1-nvidia-alternatives ...
> Processing triggers for menu ...
> root@feyerabend:~#
>
> /var/log/messages traceback:
>
> May 15 11:35:37 feyerabend kernel: [ 176.396112] Disabling lock debugging due
> to kernel taint
> May 15 11:35:37 feyerabend kernel: [ 176.396117] nvidia: module license
> 'NVIDIA' taints kernel.
> May 15 11:35:38 feyerabend kernel: [ 177.178623] nvidia 0000:01:00.0: PCI INT A
> -> GSI 16 (level, low) -> IRQ 16
> May 15 11:35:38 feyerabend kernel: [ 177.178637] vgaarb: device changed
> decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=nonew ns=
> io+mem
> May 15 11:35:38 feyerabend kernel: [ 177.178734] NVRM: loading NVIDIA UNIX
> x86_64 Kernel Module 270.41.06 Mon Apr 18 14:53:56 PDT 20
> 11
> May 15 11:35:38 feyerabend kernel: [ 177.226218] PGD 1605067 PUD 1609063 PMD 0
> May 15 11:35:38 feyerabend kernel: [ 177.226225] CPU 0
> May 15 11:35:38 feyerabend kernel: [ 177.226226] Modules linked in: nvidia(P)
> acpi_cpufreq mperf parport_pc ppdev lp parport cpufreq_s
> tats cpufreq_conservative cpufreq_powersave cpufreq_userspace fuse nfsd nfs
> lockd fscache nfs_acl auth_rpcgss sunrpc xfs exportfs ext2
> loop usbhid hid snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep
> snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_midi snd_rawmidi
> snd_seq_midi_event snd_seq evdev snd_timer snd_seq_device tpm_tis tpm tpm_bios
> psmouse snd i2c_i801 serio_raw i2c_core x38_edac soundco
> re snd_page_alloc pcspkr edac_core processor button ext4 mbcache jbd2 crc16
> dm_mod sg sd_mod sr_mod cdrom crc_t10dif uhci_hcd fan ahci
> libahci sky2 libata ehci_hcd scsi_mod thermal usbcore thermal_sys nls_base [last
> unloaded: scsi_wait_scan]
> May 15 11:35:38 feyerabend kernel: [ 177.226262]
> May 15 11:35:38 feyerabend kernel: [ 177.226264] Pid: 4609, comm: Xorg Tainted:
> P O 2.6.38-2-amd64 #1 OEM OEM/LP LT X48-T3RS
> May 15 11:35:38 feyerabend kernel: [ 177.226267] RIP: 0010:[<ffffffffa0634578>]
> [<ffffffffa0634578>] _nv028301rm+0x44/0x176 [nvidia]
> May 15 11:35:38 feyerabend kernel: [ 177.226386] RSP: 0018:ffff8802245dfb88
> EFLAGS: 00010282
> May 15 11:35:38 feyerabend kernel: [ 177.226388] RAX: ffff8801fc94c000 RBX:
> ffff880223a9a000 RCX: 0000000000000001
> May 15 11:35:38 feyerabend kernel: [ 177.226389] RDX: ffff8801fc94c000 RSI:
> 0000000000000015 RDI: ffff880224874000
> May 15 11:35:38 feyerabend kernel: [ 177.226391] RBP: ffff880225955f68 R08:
> ffff8801fd690000 R09: ffff880225955f78
> May 15 11:35:38 feyerabend kernel: [ 177.226393] R10: ffff88022f8026c0 R11:
> 0000000000000077 R12: ffff880224688000
> May 15 11:35:38 feyerabend kernel: [ 177.226394] R13: ffff880224874000 R14:
> ffff8801fc94c000 R15: ffff880224648800
> May 15 11:35:38 feyerabend kernel: [ 177.226396] FS: 00007f2732c77880(0000)
> GS:ffff8800cfc00000(0000) knlGS:0000000000000000
> May 15 11:35:38 feyerabend kernel: [ 177.226398] CS: 0010 DS: 0000 ES: 0000
> CR0: 0000000080050033
> May 15 11:35:38 feyerabend kernel: [ 177.226400] CR2: ffffffffa129b076 CR3:
> 000000022442a000 CR4: 00000000000406f0
> May 15 11:35:38 feyerabend kernel: [ 177.226401] DR0: 0000000000000000 DR1:
> 0000000000000000 DR2: 0000000000000000
> May 15 11:35:38 feyerabend kernel: [ 177.226403] DR3: 0000000000000000 DR6:
> 00000000ffff0ff0 DR7: 0000000000000400
> May 15 11:35:38 feyerabend kernel: [ 177.226405] Process Xorg (pid: 4609,
> threadinfo ffff8802245de000, task ffff880224bb4a40)
> May 15 11:35:38 feyerabend kernel: [ 177.226407] ffffc90011893000
> ffff880224874000 ffff880225955fe8 ffff880224688000
> May 15 11:35:38 feyerabend kernel: [ 177.226411] ffffc90011893000
> ffffffffa09dc95b ffff8801fc94c000 ffff880224648800
> May 15 11:35:38 feyerabend kernel: [ 177.226413] ffff880224874000
> ffffc90011893000 ffff8802239e4000 ffffffffa09dd983
> May 15 11:35:38 feyerabend kernel: [ 177.226517] [<ffffffffa09dc95b>] ?
> _nv002401rm+0x218/0x260 [nvidia]
> May 15 11:35:38 feyerabend kernel: [ 177.226614] [<ffffffffa09dd983>] ?
> _nv002394rm+0x41b/0x685 [nvidia]
> May 15 11:35:38 feyerabend kernel: [ 177.226711] [<ffffffffa09e351d>] ?
> rm_init_adapter+0x9d/0x111 [nvidia]
> May 15 11:35:38 feyerabend kernel: [ 177.226808] [<ffffffffa0a00699>] ?
> nv_kern_open+0x49a/0x603 [nvidia]
> May 15 11:35:38 feyerabend kernel: [ 177.226812] [<ffffffff810fa480>] ?
> exact_match+0x0/0x4
> May 15 11:35:38 feyerabend kernel: [ 177.226814] [<ffffffff810fa802>] ?
> chrdev_open+0x12a/0x148
> May 15 11:35:38 feyerabend kernel: [ 177.226817] [<ffffffff810fa6d8>] ?
> chrdev_open+0x0/0x148
> May 15 11:35:38 feyerabend kernel: [ 177.226819] [<ffffffff810f642a>] ?
> __dentry_open+0x15a/0x271
> May 15 11:35:38 feyerabend kernel: [ 177.226821] [<ffffffff810ff637>] ?
> dget+0x12/0x1e
> May 15 11:35:38 feyerabend kernel: [ 177.226824] [<ffffffff811013e6>] ?
> finish_open+0x97/0x15f
> May 15 11:35:38 feyerabend kernel: [ 177.226826] [<ffffffff81102412>] ?
> do_path_lookup+0x5d/0xfc
> May 15 11:35:38 feyerabend kernel: [ 177.226828] [<ffffffff81103162>] ?
> do_filp_open+0x171/0x5be
> May 15 11:35:38 feyerabend kernel: [ 177.226831] [<ffffffff8110b58e>] ?
> setattr_copy+0x98/0xd7
> May 15 11:35:38 feyerabend kernel: [ 177.226833] [<ffffffff810f6752>] ?
> chown_common+0x90/0x9b
> May 15 11:35:38 feyerabend kernel: [ 177.226835] [<ffffffff8110bee4>] ?
> alloc_fd+0x69/0x10b
> May 15 11:35:38 feyerabend kernel: [ 177.226837] [<ffffffff810f620f>] ?
> do_sys_open+0x56/0xda
> May 15 11:35:38 feyerabend kernel: [ 177.226840] [<ffffffff81009952>] ?
> system_call_fastpath+0x16/0x1b
> May 15 11:35:38 feyerabend kernel: [ 177.226979] RSP <ffff8802245dfb88>
> May 15 11:35:38 feyerabend kernel: [ 177.226982] ---[ end trace
> 58be261eea03ecf3 ]---
> root@feyerabend:~#
>
> [end of message]
>
>


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4DD021D2.5090202@pinyon.org">http://lists.debian.org/4DD021D2.5090202@pinyon.org