Welcome, Guest. Please login or register.
Did you miss your activation email?

Author Topic:  [solved] nvidia-legacy-340xx-driver  (Read 5725 times)

Offline harley-peter

  • User
  • Posts: 1.023
[solved] nvidia-legacy-340xx-driver
« on: 2016/12/13, 10:31:28 »
Hello,

does anybody knows something about a new release of this driver for xorg from Nvidia? Does Nvidia continue the support for this driver at all? Or can I /must I change to the xserver-xorg-video-nouveau driver? On the Nvidia Homepage there are no new information about this since the last release in September.

My Card:
Code: [Select]
Card: NVIDIA GT218 [GeForce 210] bus-ID: 01:00.0
           Display Server: X.Org 1.18.4 driver: nvidia Resolution: 1920x1080@60.00hz
           GLX Renderer: GeForce 210/PCIe/SSE2 GLX Version: 3.3.0 NVIDIA 340.98 Direct Rendering: Yes
« Last Edit: 2016/12/19, 15:11:42 by harley-peter »

Offline seasons

  • User
  • Posts: 269
Re: nvidia-legacy-340xx-driver
« Reply #1 on: 2016/12/14, 21:29:41 »
Nvidia released it today: http://www.nvidia.com/download/driverResults.aspx/112998/en-us
Now you are waiting on Debian maintainer to upload it.

Quote
Or can I change to the xserver-xorg-video-nouveau driver?

I had a good experience with nouveau on an 8400GS. nouveau gave me the same level of OpenGL and VDPAU support. The 3D performance wasn't quite as fast, but it was still enough for light gaming.

Offline Geier0815

  • User
  • Posts: 588
Re: nvidia-legacy-340xx-driver
« Reply #2 on: 2016/12/18, 14:34:57 »
The 101-1 is in unstable now. BUT for me it doesn't work. After d-u the module couldn't be loaded. Purging all packages with nvidia in name and "apt --no-install-recommends install nvidia-legacy-340xx-kernel-dkms nvidia-legacy-340xx-driver" gives me kernel-panic-like messages like "[ 1379.196779 ] BUG: unable to handle kernel paging request an ffffc9000bdcfcb0" and I have no idea what's going wrong.
Wenn Windows die Lösung ist...
kann ich dann bitte das Problem zurück haben?

Offline harley-peter

  • User
  • Posts: 1.023
Re: nvidia-legacy-340xx-driver
« Reply #3 on: 2016/12/18, 14:59:32 »
Also here no X after a du.

In the Xorg.log:

Code: [Select]
[   198.190] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_31
[   198.193] (--) PCI:*(0:1:0:0) 10de:0a65:19da:1160 rev 162, Mem @ 0xf9000000/16777216, 0xd0000000/268435456, 0xee000000/33554432, I/O @ 0x0000cf00/128, BIOS @ 0x????????/131072
[   198.193] (II) LoadModule: "glx"
[   198.193] (II) Loading /usr/lib/xorg/modules/linux/libglx.so
[   198.210] (II) Module glx: vendor="NVIDIA Corporation"
[   198.210] compiled for 4.0.2, module version = 1.0.0
[   198.210] Module class: X.Org Server Extension
[   198.210] (II) NVIDIA GLX Module  340.101  Thu Dec  1 15:12:41 PST 2016
[   198.211] (II) LoadModule: "nvidia"
[   198.211] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[   198.211] (II) Module nvidia: vendor="NVIDIA Corporation"
[   198.211] compiled for 4.0.2, module version = 1.0.0
[   198.211] Module class: X.Org Video Driver
[   198.211] (II) NVIDIA dlloader X Driver  340.101  Thu Dec  1 14:50:13 PST 2016
[   198.211] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[   198.212] (II) Loading sub module "fb"
[   198.212] (II) LoadModule: "fb"
[   198.212] (II) Loading /usr/lib/xorg/modules/libfb.so
[   198.212] (II) Module fb: vendor="X.Org Foundation"
[   198.212] compiled for 1.19.0, module version = 1.0.0
[   198.212] ABI class: X.Org ANSI C Emulation, version 0.4
[   198.212] (WW) Unresolved symbol: fbGetGCPrivateKey
[   198.212] (II) Loading sub module "wfb"
[   198.212] (II) LoadModule: "wfb"
[   198.212] (II) Loading /usr/lib/xorg/modules/libwfb.so
[   198.212] (II) Module wfb: vendor="X.Org Foundation"
[   198.212] compiled for 1.19.0, module version = 1.0.0
[   198.213] ABI class: X.Org ANSI C Emulation, version 0.4
[   198.213] (II) Loading sub module "ramdac"
[   198.213] (II) LoadModule: "ramdac"
[   198.213] (II) Module "ramdac" already built-in
[   198.278] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the
[   198.278] (EE) NVIDIA:     system's kernel log for additional error messages and
[   198.278] (EE) NVIDIA:     consult the NVIDIA README for details.
[   198.278] (EE) No devices detected.
[   198.278] (EE)
Fatal server error:
[   198.278] (EE) no screens found(EE)
[   198.278] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
 for help.
[   198.278] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[   198.278] (EE)
[   198.396] (EE) Server terminated with error (1). Closing log file.

and in syslog:

Code: [Select]
Dec 18 13:19:59 master kernel: [ 3615.939433] NVRM: API mismatch: the client has the version 340.101, but
Dec 18 13:19:59 master kernel: [ 3615.939433] NVRM: this kernel module has the version 340.98.  Please
Dec 18 13:19:59 master kernel: [ 3615.939433] NVRM: make sure that this kernel module and all NVIDIA driver
Dec 18 13:19:59 master kernel: [ 3615.939433] NVRM: components have the same version.
Dec 18 13:19:59 master kernel: [ 3615.939437] NVRM: nvidia_frontend_ioctl: minor 255, module->ioctl failed, error -22
.
.
.
.
Dec 18 13:47:42 master kernel: [  198.344163] WARNING: CPU: 1 PID: 1321 at /build/linux-siduction-4.9/fs/proc/generic.c:345 proc_register+0xee/0x110
Dec 18 13:47:42 master kernel: [  198.344164] proc_dir_entry 'driver/nvidia' already registered
Dec 18 13:47:42 master kernel: [  198.344165] Modules linked in: nvidia(PO+) cpufreq_powersave pci_stub vboxpci(O) cpufreq_conservative vboxnetadp(O) vboxnetflt(O) vboxdrv(O) af_packet snd_hda_codec_realtek snd_hda_codec_generic snd_usb_audio snd_usbmidi_lib snd_rawmidi uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media snd_seq_device intel_powerclamp snd_hda_codec_hdmi kvm_intel kvm iTCO_wdt iTCO_vendor_support evdev intel_cstate snd_hda_intel input_leds serio_raw snd_hda_codec snd_hda_core button snd_hwdep snd_pcm sg snd_timer pcspkr snd i7core_edac edac_core soundcore lpc_ich acpi_cpufreq drm it87 hwmon_vid coretemp nfsd auth_rpcgss nfs_acl lockd grace sunrpc parport_pc ppdev lp parport ip_tables x_tables autofs4 ext4 crc16 jbd2 fscrypto mbcache hid_generic usbhid hid sd_mod sr_mod cdrom uas
Dec 18 13:47:42 master kernel: [  198.344226]  usb_storage ata_generic pata_acpi crc32c_intel pata_jmicron ahci i2c_i801 ata_piix i2c_smbus libahci i2c_core libata ehci_pci uhci_hcd r8169 mii ehci_hcd scsi_mod usbcore floppy fjes
Dec 18 13:47:42 master kernel: [  198.344246] CPU: 1 PID: 1321 Comm: modprobe Tainted: P        W  O    4.9.0-towo.1-siduction-amd64 #1 siduction 4.9-1
Dec 18 13:47:42 master kernel: [  198.344247] Hardware name: Gigabyte Technology Co., Ltd. P55-UD3/P55-UD3, BIOS F3 07/31/2009
Dec 18 13:47:42 master kernel: [  198.344249]  0000000000000000 ffffffff812a0342 ffffc90001707b88 0000000000000000
Dec 18 13:47:42 master kernel: [  198.344254]  ffffffff8105cfc4 ffff8802258a1340 ffffc90001707be0 ffff880227004840
Dec 18 13:47:42 master kernel: [  198.344258]  ffff88022295b745 ffff880227004878 ffff88022295b6c0 ffffffff8105d03a
Dec 18 13:47:42 master kernel: [  198.344262] Call Trace:
Dec 18 13:47:42 master kernel: [  198.344268]  [<ffffffff812a0342>] ? dump_stack+0x5c/0x7a
Dec 18 13:47:42 master kernel: [  198.344272]  [<ffffffff8105cfc4>] ? __warn+0xb4/0xd0
Dec 18 13:47:42 master kernel: [  198.344275]  [<ffffffff8105d03a>] ? warn_slowpath_fmt+0x5a/0x80
Dec 18 13:47:42 master kernel: [  198.344279]  [<ffffffff8120be68>] ? proc_alloc_inum+0x48/0xd0
Dec 18 13:47:42 master kernel: [  198.344283]  [<ffffffff812a1df9>] ? ida_get_new_above+0x1e9/0x210
Dec 18 13:47:42 master kernel: [  198.344286]  [<ffffffff8120c01e>] ? proc_register+0xee/0x110
Dec 18 13:47:42 master kernel: [  198.344289]  [<ffffffff8120c13c>] ? proc_mkdir_data+0x5c/0x80
Dec 18 13:47:42 master kernel: [  198.344418]  [<ffffffffa06653b7>] ? nv_register_procfs+0x47/0x1d0 [nvidia]
Dec 18 13:47:42 master kernel: [  198.344539]  [<ffffffffa004a299>] ? nvidia_init_module+0x299/0x79b [nvidia]
Dec 18 13:47:42 master kernel: [  198.344659]  [<ffffffffa004a7aa>] ? nv_drm_init+0xf/0xf [nvidia]
Dec 18 13:47:42 master kernel: [  198.344780]  [<ffffffffa004a7f6>] ? nvidia_frontend_init_module+0x4c/0x8c [nvidia]
Dec 18 13:47:42 master kernel: [  198.344783]  [<ffffffff81000426>] ? do_one_initcall+0x46/0x170
Dec 18 13:47:42 master kernel: [  198.344787]  [<ffffffff81161040>] ? free_vmap_area_noflush+0x50/0xb0
Dec 18 13:47:42 master kernel: [  198.344792]  [<ffffffff811213ec>] ? do_init_module+0x51/0x1c5
Dec 18 13:47:42 master kernel: [  198.344797]  [<ffffffff810da78d>] ? load_module+0x1dad/0x24e0
Dec 18 13:47:42 master kernel: [  198.344800]  [<ffffffff810d7e30>] ? __symbol_put+0x80/0x80
Dec 18 13:47:42 master kernel: [  198.344805]  [<ffffffff810db0d2>] ? SYSC_finit_module+0xc2/0xd0
Dec 18 13:47:42 master kernel: [  198.344810]  [<ffffffff81557f7b>] ? entry_SYSCALL_64_fastpath+0x1e/0xad
Dec 18 13:47:42 master kernel: [  198.344812] ---[ end trace d8d6604869fd96cc ]---
Dec 18 13:47:42 master kernel: [  198.344814] NVRM: failed to register procfs!
Dec 18 13:47:42 master kernel: [  198.344850] NVRM: request_mem_region failed for 16M @ 0xf9000000. This can
Dec 18 13:47:42 master kernel: [  198.344850] NVRM: occur when a driver such as rivatv is loaded and claims
Dec 18 13:47:42 master kernel: [  198.344850] NVRM: ownership of the device's registers.
Dec 18 13:47:42 master kernel: [  198.344855] nvidia: probe of 0000:01:00.0 failed with error -1
Dec 18 13:47:42 master kernel: [  198.344883] Error: Driver 'nvidia' is already registered, aborting...
Dec 18 13:47:42 master kernel: [  198.344887] NVRM: DRM init failed

Offline Geier0815

  • User
  • Posts: 588
Re: nvidia-legacy-340xx-driver
« Reply #4 on: 2016/12/18, 15:12:10 »
As you can see here, there is a new package which will reach unstable shortly: https://packages.qa.debian.org/n/nvidia-graphics-drivers-legacy-340xx/news/20161218T134919Z.html 101-1 seems to havo problems with drm in kernel 4.9. I'll try to deinstall 4.9 and install nvidia again. I'll let you know if this will solve the issue.
Wenn Windows die Lösung ist...
kann ich dann bitte das Problem zurück haben?

Online towo

  • Administrator
  • User
  • *****
  • Posts: 2.938
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

Offline Geier0815

  • User
  • Posts: 588
Re: nvidia-legacy-340xx-driver
« Reply #6 on: 2016/12/18, 15:25:14 »
Ok, to patch the driver is a way too. My way with purging 4.9 and wait for 101-2 works also.
Wenn Windows die Lösung ist...
kann ich dann bitte das Problem zurück haben?

Offline Geier0815

  • User
  • Posts: 588
Re: nvidia-legacy-340xx-driver
« Reply #7 on: 2016/12/19, 09:01:44 »
101-2 is out and works like a charm for me even with kernel 4.9.9-towo.1-siduction-amd64.
Wenn Windows die Lösung ist...
kann ich dann bitte das Problem zurück haben?

Offline Camelot

  • User
  • Posts: 81
Re: nvidia-legacy-340xx-driver
« Reply #8 on: 2016/12/19, 11:05:35 »
101-2 is out and works like a charm for me even with kernel 4.9.9-towo.1-siduction-amd64.
I confirm this with nvidia 340.101-2 with 4.9.0-towo.1-siduction-amd64.

@Geier0815
Code: [Select]
$ uname -r
4.9.0-towo.1-siduction-amd64

Offline Geier0815

  • User
  • Posts: 588
Re: nvidia-legacy-340xx-driver
« Reply #9 on: 2016/12/19, 12:24:51 »
Ups, my fault. It should be the same as yours in my post above
Wenn Windows die Lösung ist...
kann ich dann bitte das Problem zurück haben?