[SOLVED] stretch nvidia-legacy-340xx-driver trouble

Kernels & Hardware, configuring network, installing services

[SOLVED] stretch nvidia-legacy-340xx-driver trouble

Postby draco » 2017-03-15 22:11

I'm trying to configure my Nvidia ION card on Stretch.

uname -a
Linux host 4.9.0-2-686-pae #1 SMP Debian 4.9.13-1 (2017-02-27) i686 GNU/Linux

nvidia-detect
Detected NVIDIA GPUs:
03:00.0 VGA compatible controller [0300]: NVIDIA Corporation ION VGA [10de:087d] (rev b1)
Checking card: NVIDIA Corporation ION VGA (rev b1)
Your card is only supported up to the 340 legacy drivers series.
It is recommended to install the
nvidia-legacy-340xx-driver

I've run
apt-get purge xserver-xorg-video-nouveau (could not get hdmi working, VGA worked OK)

apt-get install nvidia-legacy-340xx-driver nvidia-xconfig

dkms status
nvidia-legacy-340xx, 340.102, 4.9.0-2-686-pae, i686: installed
rtl8192eu, 1.0, 4.9.0-2-686-pae, i686: installed

results in a black screen and the following Xorg.0.log

[ 670.217] (II) NVIDIA(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 670.217] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[ 670.217] (==) NVIDIA(0): RGB weight 888
[ 670.218] (==) NVIDIA(0): Default visual is TrueColor
[ 670.218] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 670.218] () NVIDIA(0): Enabling 2D acceleration
[ 670.561] (II) NVIDIA(0): Display (LG Electronics 23EN43 (CRT-0)) does not support
[ 670.561] (II) NVIDIA(0): NVIDIA 3D Vision stereo.
[ 670.562] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20150116)
[ 670.564] (II) NVIDIA(0): NVIDIA GPU ION (C79) at PCI:3:0:0 (GPU-0)
[ 670.564] (--) NVIDIA(0): Memory: 262144 kBytes
[ 670.565] (--) NVIDIA(0): VideoBIOS: 62.79.6c.00.01
[ 674.566] (EE) NVIDIA(GPU-0): EVO Push buffer channel allocation failed
[ 674.568] (EE) NVIDIA(GPU-0): Failed to allocate EVO core DMA push buffer
[ 767.555] (EE) NVIDIA(0): Failing initialization of X screen 0
[ 767.555] (II) UnloadModule: "nvidia"

Any help would be much appreciated.

Thanks
Last edited by draco on 2017-03-19 04:35, edited 2 times in total.
draco
 
Posts: 4
Joined: 2017-03-15 21:33

Re: stretch nvidia-legacy-340xx-driver trouble

Postby TonyT » 2017-03-15 23:29

You'll need a lot more than just the driver to use legacy nvidia. For example, I am running Stretch 64 bit and recently installed the legacy driver, these packages were installed with it using Synaptic after selecting the nvidia legacy driver and dkms.:

Commit Log for Sun Mar 5 20:42:08 2017

Installed the following packages:
dkms (2.3-2)
glx-alternative-mesa (0.7.4)
glx-alternative-nvidia (0.7.4)
glx-diversions (0.7.4)
libegl1-nvidia-legacy-340xx (340.102-1)
libegl1-nvidia-legacy-340xx:i386 (340.102-1)
libgl1-nvidia-legacy-340xx-glx (340.102-1)
libgl1-nvidia-legacy-340xx-glx:i386 (340.102-1)
libgles1-nvidia-legacy-340xx (340.102-1)
libgles1-nvidia-legacy-340xx:i386 (340.102-1)
libgles2-nvidia-legacy-340xx (340.102-1)
libgles2-nvidia-legacy-340xx:i386 (340.102-1)
libnvidia-legacy-340xx-cfg1 (340.102-1)
libnvidia-legacy-340xx-cfg1:i386 (340.102-1)
libnvidia-legacy-340xx-eglcore (340.102-1)
libnvidia-legacy-340xx-eglcore:i386 (340.102-1)
libnvidia-legacy-340xx-glcore (340.102-1)
libnvidia-legacy-340xx-glcore:i386 (340.102-1)
libnvidia-legacy-340xx-ml1 (340.102-1)
linux-headers-amd64 (4.9+78)
nvidia-installer-cleanup (20151021+4)
nvidia-kernel-common (20151021+4)
nvidia-legacy-340xx-alternative (340.102-1)
nvidia-legacy-340xx-driver (340.102-1)
nvidia-legacy-340xx-driver-bin (340.102-1)
nvidia-legacy-340xx-driver-libs (340.102-1)
nvidia-legacy-340xx-driver-libs-i386:i386 (340.102-1)
nvidia-legacy-340xx-driver-libs:i386 (340.102-1)
nvidia-legacy-340xx-kernel-dkms (340.102-1)
nvidia-legacy-340xx-kernel-support (340.102-1)
nvidia-legacy-340xx-vdpau-driver (340.102-1)
nvidia-modprobe (375.26-1)
nvidia-persistenced (375.26-2)
nvidia-settings-legacy-340xx (340.101-1)
nvidia-support (20151021+4)
pkg-config (0.29-4)
update-glx (0.7.4)
xserver-xorg-video-nvidia-legacy-340xx (340.102-1)
TonyT
 
Posts: 439
Joined: 2006-09-04 11:57

Re: stretch nvidia-legacy-340xx-driver trouble

Postby stevepusser » 2017-03-15 23:52

Throw out all that multiarch drama, since the OP is running 32-bit.

Have you tried booting with the "nomodeset" kernel parameter? And do you see any boot messages going by, or is it just black from the beginning?
The MX Linux repositories: Backports galore! If we don't have something, just ask and we'll try--we like challenges. New packages: AzPainter 2.0.4, Pale Moon 27.3.0, Liquorix kernel 4.11-4, mpv 0.25.0, Kodi 17.1, Ksnip 1.3.1, Mesa 13.0.6
User avatar
stevepusser
 
Posts: 8227
Joined: 2009-10-06 05:53

Re: stretch nvidia-legacy-340xx-driver trouble

Postby draco » 2017-03-16 00:51

Thanks I tried nomodeset in grub, still blank screen. I can see debug messages right up until Debian login: then the nvidia logo loads for a second then screen blank. I can ssh into the machine and I see this in syslog.

Mar 16 12:37:23 host kernel: [ 648.244016] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [Xorg:4253]
Mar 16 12:37:23 host kernel: [ 648.244016] Modules linked in: appletalk ax25 ipx p8023 p8022 psnap llc cpufreq_userspace cpufreq_powersave cpufreq_conservative rpcsec_gss_krb5 nfsv4 nls_utf8 cifs nfs cmac md4 hmac des_generic dns_resolver fscache uinput snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic arc4 joydev ath5k ath mac80211 cfg80211 snd_hda_intel snd_hda_codec rfkill snd_hda_core snd_hwdep snd_pcm_oss snd_mixer_oss evdev snd_pcm coretemp serio_raw pcspkr sg shpchp snd_timer snd nv_tco soundcore wmi button acpi_cpufreq tpm_tis tpm_tis_core tpm binfmt_misc nvidia(POE) nfsd auth_rpcgss nfs_acl lockd grace sunrpc drm 8192eu(OE) loop parport_pc ppdev lp parport ip_tables x_tables autofs4 ext4 crc16 jbd2 crc32c_generic fscrypto ecb xts lrw gf128mul ablk_helper cryptd aes_i586 mbcache hid_generic usbhid hid sd_mod
Mar 16 12:37:23 host kernel: [ 648.244016] ohci_pci ahci libahci libata ohci_hcd ehci_pci ehci_hcd psmouse usbcore scsi_mod forcedeth thermal i2c_nforce2 usb_common
Mar 16 12:37:23 host kernel: [ 648.244016] CPU: 2 PID: 4253 Comm: Xorg Tainted: P OEL 4.9.0-2-686-pae #1 Debian 4.9.13-1
Mar 16 12:37:23 host kernel: [ 648.244016] Hardware name: Acer Aspire R3610/FMCP7A-ION, BIOS P01-A2 08/10/2009
Mar 16 12:37:23 host kernel: [ 648.244016] task: f60bd400 task.stack: f0dcc000
Mar 16 12:37:23 host kernel: [ 648.244016] EIP: 0060:[<f9425edf>] EFLAGS: 00203282 CPU: 2
Mar 16 12:37:23 host kernel: [ 648.244016] EIP is at os_io_write_byte+0xf/0x20 [nvidia]
Mar 16 12:37:23 host kernel: [ 648.244016] EAX: 00000094 EBX: 0000c000 ECX: 00000001 EDX: 000003d4
Mar 16 12:37:23 host kernel: [ 648.244016] ESI: 00001b82 EDI: ffffffff EBP: f0dcdd7c ESP: f0dcdd7c
Mar 16 12:37:23 host kernel: [ 648.244016] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Mar 16 12:37:23 host kernel: [ 648.244016] CR0: 80050033 CR2: 805c916c CR3: 325b6f20 CR4: 000006f0
Mar 16 12:37:23 host kernel: [ 648.244016] Stack:
Mar 16 12:37:23 host kernel: [ 648.244016] f61e5f8c f98f9366 000003d4 00000094 f98f1164 000000ee f99134b4 00004f02
Mar 16 12:37:23 host kernel: [ 648.244016] f61e5fb0 f0dd4004 f9904e13 f0dd4004 f61e5fac f61e5fb0 f61e5fb4 f61e5fb8
Mar 16 12:37:23 host kernel: [ 648.244016] 00000000 f6845304 00000010 f0dd4004 f99087d5 f0dd4004 f61e5fac f61e5fb0
Mar 16 12:37:23 host kernel: [ 648.244016] Call Trace:
Mar 16 12:37:23 host kernel: [ 648.244016] [<f98f9366>] ? _nv017293rm+0x7726/0xacb0 [nvidia]
Mar 16 12:37:23 host kernel: [ 648.244016] [<f98f1164>] ? _nv000909rm+0x74/0x8c [nvidia]
Mar 16 12:37:23 host kernel: [ 648.244016] [<f99134b4>] ? _nv013089rm+0x14c/0x780 [nvidia]
Mar 16 12:37:23 host kernel: [ 648.244016] [<f9904e13>] ? _nv013383rm+0x63/0x118 [nvidia]
Mar 16 12:37:23 host kernel: [ 648.244016] [<f99087d5>] ? _nv000798rm+0x2b1/0x310 [nvidia]
Mar 16 12:37:23 host kernel: [ 648.244016] [<f9908b03>] ? _nv000720rm+0x2cf/0x4b8 [nvidia]
Mar 16 12:37:23 host kernel: [ 648.244016] [<f9911276>] ? _nv000732rm+0xd6/0x354 [nvidia]
Mar 16 12:37:23 host kernel: [ 648.244016] [<f990a3be>] ? rm_disable_adapter+0x46/0xb4 [nvidia]
Mar 16 12:37:23 host kernel: [ 648.244016] [<f941ee0b>] ? nvidia_close+0x3eb/0x4a0 [nvidia]
Mar 16 12:37:23 host kernel: [ 648.244016] [<f941ebfe>] ? nvidia_close+0x1de/0x4a0 [nvidia]
Mar 16 12:37:23 host kernel: [ 648.244016] [<f942832d>] ? nvidia_frontend_compat_ioctl+0x1d/0x30 [nvidia]
Mar 16 12:37:23 host kernel: [ 648.244016] [<f942824d>] ? nvidia_frontend_close+0x3d/0x90 [nvidia]
Mar 16 12:37:23 host kernel: [ 648.244016] [<ce1d9f69>] ? __fput+0xc9/0x1d0
Mar 16 12:37:23 host kernel: [ 648.244016] [<ce0824a7>] ? task_work_run+0x77/0x90
Mar 16 12:37:23 host kernel: [ 648.244016] [<ce003095>] ? exit_to_usermode_loop+0xc5/0xd0
Mar 16 12:37:23 host kernel: [ 648.244016] [<ce00379f>] ? do_fast_syscall_32+0x12f/0x150
Mar 16 12:37:23 host kernel: [ 648.244016] [<ce59ecca>] ? sysenter_past_esp+0x47/0x75
Mar 16 12:37:23 host kernel: [ 648.244016] Code: 43 cb f9 c7 45 08 6e 90 a7 f9 c6 05 ff 44 cb f9 00 83 c4 04 5b 5e 5d e9 eb f7 d3 d4 55 89 e5 3e 8d 74 26 00 8b 45 0c 8b 55 08 ee <5d> c3 eb 0d 90 90 90 90 90 90 90 90 90 90 90 90 90 55 89 e5 3e
Mar 16 12:37:23 host kernel: [ 676.244017] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [Xorg:4253]
Mar 16 12:37:23 host kernel: [ 676.244017] Modules linked in: appletalk ax25 ipx p8023 p8022 psnap llc cpufreq_userspace cpufreq_powersave cpufreq_conservative rpcsec_gss_krb5 nfsv4 nls_utf8 cifs nfs cmac md4 hmac des_generic dns_resolver fscache uinput snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic arc4 joydev ath5k ath mac80211 cfg80211 snd_hda_intel snd_hda_codec rfkill snd_hda_core snd_hwdep snd_pcm_oss snd_mixer_oss evdev snd_pcm coretemp serio_raw pcspkr sg shpchp snd_timer snd nv_tco soundcore wmi button acpi_cpufreq tpm_tis tpm_tis_core tpm binfmt_misc nvidia(POE) nfsd auth_rpcgss nfs_acl lockd grace sunrpc drm 8192eu(OE) loop parport_pc ppdev lp parport ip_tables x_tables autofs4 ext4 crc16 jbd2 crc32c_generic fscrypto ecb xts lrw gf128mul ablk_helper cryptd aes_i586 mbcache hid_generic usbhid hid sd_mod
Mar 16 12:37:23 host kernel: [ 676.244017] ohci_pci ahci libahci libata ohci_hcd ehci_pci ehci_hcd psmouse usbcore scsi_mod forcedeth thermal i2c_nforce2 usb_common
Mar 16 12:37:23 host kernel: [ 676.244017] CPU: 2 PID: 4253 Comm: Xorg Tainted: P OEL 4.9.0-2-686-pae #1 Debian 4.9.13-1
Mar 16 12:37:23 host kernel: [ 676.244017] Hardware name: Acer Aspire R3610/FMCP7A-ION, BIOS P01-A2 08/10/2009
Mar 16 12:37:23 host kernel: [ 676.244017] task: f60bd400 task.stack: f0dcc000
Mar 16 12:37:23 host kernel: [ 676.244017] EIP: 0060:[<f9425f3c>] EFLAGS: 00203282 CPU: 2
Mar 16 12:37:23 host kernel: [ 676.244017] EIP is at os_io_read_byte+0xc/0x10 [nvidia]
Mar 16 12:37:23 host kernel: [ 676.244017] EAX: 00000348 EBX: 0000c000 ECX: 00000001 EDX: 000003d5
Mar 16 12:37:23 host kernel: [ 676.244017] ESI: 00001b82 EDI: ffffffff EBP: f0dcdd78 ESP: f0dcdd78
Mar 16 12:37:23 host kernel: [ 676.244017] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Mar 16 12:37:23 host kernel: [ 676.244017] CR0: 80050033 CR2: 805c916c CR3: 325b6f20 CR4: 000006f0
Mar 16 12:37:23 host kernel: [ 676.244017] Stack:
Mar 16 12:37:23 host kernel: [ 676.244017] f61e5f8c f9912fa7 000003d5 f98f92f6 000003d5 f98f1164 000000ec f99134b4
Mar 16 12:37:23 host kernel: [ 676.244017] 00004f02 f61e5fb0 f0dd4004 f9904e13 f0dd4004 f61e5fac f61e5fb0 f61e5fb4
Mar 16 12:37:23 host kernel: [ 676.244017] f61e5fb8 00000000 f6845304 00000010 f0dd4004 f99087d5 f0dd4004 f61e5fac
Mar 16 12:37:23 host kernel: [ 676.244017] Call Trace:
Mar 16 12:37:23 host kernel: [ 676.244017] [<f9912fa7>] ? rm_shutdown_gvi_device+0x73/0x244 [nvidia]
Mar 16 12:37:23 host kernel: [ 676.244017] [<f98f92f6>] ? _nv017293rm+0x76b6/0xacb0 [nvidia]
Mar 16 12:37:23 host kernel: [ 676.244017] [<f98f1164>] ? _nv000909rm+0x74/0x8c [nvidia]
Mar 16 12:37:23 host kernel: [ 676.244017] [<f99134b4>] ? _nv013089rm+0x14c/0x780 [nvidia]
Mar 16 12:37:23 host kernel: [ 676.244017] [<f9904e13>] ? _nv013383rm+0x63/0x118 [nvidia]
Mar 16 12:37:23 host kernel: [ 676.244017] [<f99087d5>] ? _nv000798rm+0x2b1/0x310 [nvidia]
Mar 16 12:37:23 host kernel: [ 676.244017] [<f9908b03>] ? _nv000720rm+0x2cf/0x4b8 [nvidia]
Mar 16 12:37:23 host kernel: [ 676.244017] [<f9911276>] ? _nv000732rm+0xd6/0x354 [nvidia]
Mar 16 12:37:23 host kernel: [ 676.244017] [<f990a3be>] ? rm_disable_adapter+0x46/0xb4 [nvidia]
Mar 16 12:37:23 host kernel: [ 676.244017] [<f941ee0b>] ? nvidia_close+0x3eb/0x4a0 [nvidia]
Mar 16 12:37:23 host kernel: [ 676.244017] [<f941ebfe>] ? nvidia_close+0x1de/0x4a0 [nvidia]
Mar 16 12:37:23 host kernel: [ 676.244017] [<f942832d>] ? nvidia_frontend_compat_ioctl+0x1d/0x30 [nvidia]
Mar 16 12:37:23 host kernel: [ 676.244017] [<f942824d>] ? nvidia_frontend_close+0x3d/0x90 [nvidia]
Mar 16 12:37:23 host kernel: [ 676.244017] [<ce1d9f69>] ? __fput+0xc9/0x1d0
Mar 16 12:37:23 host kernel: [ 676.244017] [<ce0824a7>] ? task_work_run+0x77/0x90
Mar 16 12:37:23 host kernel: [ 676.244017] [<ce003095>] ? exit_to_usermode_loop+0xc5/0xd0
Mar 16 12:37:23 host kernel: [ 676.244017] [<ce00379f>] ? do_fast_syscall_32+0x12f/0x150
Mar 16 12:37:23 host kernel: [ 676.244017] [<ce59ecca>] ? sysenter_past_esp+0x47/0x75
Mar 16 12:37:23 host kernel: [ 676.244017] Code: 89 e5 3e 8d 74 26 00 8b 45 0c 8b 55 08 ef 5d c3 eb 0d 90 90 90 90 90 90 90 90 90 90 90 90 90 55 89 e5 3e 8d 74 26 00 8b 55 08 ec <5d> c3 66 90 55 89 e5 3e 8d 74 26 00 8b 55 08 66 ed 5d c3 90 55
Mar 16 12:37:23 host kernel: [ 687.128017] INFO: rcu_sched self-detected stall on CPU
Mar 16 12:37:23 host kernel: [ 687.128017] 2-...: (21000 ticks this GP) idle=60f/140000000000001/0 softirq=11140/11140 fqs=10492
Mar 16 12:37:23 host kernel: [ 687.128017] (t=21003 jiffies g=7362 c=7361 q=6559)
Mar 16 12:37:23 host kernel: [ 687.128017] Task dump for CPU 2:
Mar 16 12:37:23 host kernel: [ 687.128017] Xorg R running task 0 4253 4251 0x00400008
Mar 16 12:37:23 host kernel: [ 687.128017] f0dcdbf8 ce091681 ce6a231e 00000000 0000109d 0000109b 00400008 ce770140
Mar 16 12:37:23 host kernel: [ 687.128017] ce770140 00000002 f0dcdc10 ce165854 00203087 f79df280 ce770140 ce770140
Mar 16 12:37:23 host kernel: [ 687.128017] f0dcdc5c ce0d1de1 ce698b78 0000520b 00001cc2 00001cc1 0000199f f79dea40
Mar 16 12:37:23 host kernel: [ 687.128017] Call Trace:
Mar 16 12:37:23 host kernel: [ 687.128017] [<ce091681>] ? sched_show_task+0xf1/0x160
Mar 16 12:37:23 host kernel: [ 687.128017] [<ce165854>] ? rcu_dump_cpu_stacks+0x79/0x95
Mar 16 12:37:23 host kernel: [ 687.128017] [<ce0d1de1>] ? rcu_check_callbacks+0x631/0x780
Mar 16 12:37:23 host kernel: [ 687.128017] [<ce094c4a>] ? account_process_tick+0x5a/0x150
Mar 16 12:37:23 host kernel: [ 687.128017] [<ce0d7278>] ? update_process_times+0x28/0x50
Mar 16 12:37:23 host kernel: [ 687.128017] [<ce0e8736>] ? tick_sched_handle.isra.11+0x26/0x60
Mar 16 12:37:23 host kernel: [ 687.128017] [<ce0e87aa>] ? tick_sched_timer+0x3a/0x80
Mar 16 12:37:23 host kernel: [ 687.128017] [<ce0d7d0f>] ? __remove_hrtimer+0x3f/0x80
Mar 16 12:37:23 host kernel: [ 687.128017] [<ce0d7f30>] ? __hrtimer_run_queues+0xc0/0x260
Mar 16 12:37:23 host kernel: [ 687.128017] [<ce0e8770>] ? tick_sched_handle.isra.11+0x60/0x60
Mar 16 12:37:23 host kernel: [ 687.128017] [<ce0d8753>] ? hrtimer_interrupt+0x93/0x1a0
Mar 16 12:37:23 host kernel: [ 687.128017] [<ce5a0063>] ? smp_apic_timer_interrupt+0x33/0x50
Mar 16 12:37:23 host kernel: [ 687.128017] [<ce59f778>] ? apic_timer_interrupt+0x34/0x3c
Mar 16 12:37:23 host kernel: [ 687.128017] [<f991303a>] ? rm_shutdown_gvi_device+0x106/0x244 [nvidia]
Mar 16 12:37:23 host kernel: [ 687.128017] [<f9913063>] ? rm_shutdown_gvi_device+0x12f/0x244 [nvidia]
Mar 16 12:37:23 host kernel: [ 687.128017] [<f98f11fd>] ? _nv007201rm+0x25/0x2c [nvidia]
Mar 16 12:37:23 host kernel: [ 687.128017] [<f98f7779>] ? _nv017293rm+0x5b39/0xacb0 [nvidia]
Mar 16 12:37:23 host kernel: [ 687.128017] [<f98f1164>] ? _nv000909rm+0x74/0x8c [nvidia]
Mar 16 12:37:23 host kernel: [ 687.128017] [<f99134b4>] ? _nv013089rm+0x14c/0x780 [nvidia]
Mar 16 12:37:23 host kernel: [ 687.128017] [<f9904e13>] ? _nv013383rm+0x63/0x118 [nvidia]
Mar 16 12:37:23 host kernel: [ 687.128017] [<f99087d5>] ? _nv000798rm+0x2b1/0x310 [nvidia]
Mar 16 12:37:23 host kernel: [ 687.128017] [<f9908b03>] ? _nv000720rm+0x2cf/0x4b8 [nvidia]
Mar 16 12:37:23 host kernel: [ 687.128017] [<f9911276>] ? _nv000732rm+0xd6/0x354 [nvidia]
Mar 16 12:37:23 host kernel: [ 687.128017] [<f990a3be>] ? rm_disable_adapter+0x46/0xb4 [nvidia]
Mar 16 12:37:23 host kernel: [ 687.128017] [<f941ee0b>] ? nvidia_close+0x3eb/0x4a0 [nvidia]
Mar 16 12:37:23 host kernel: [ 687.128017] [<f941ebfe>] ? nvidia_close+0x1de/0x4a0 [nvidia]
Mar 16 12:37:23 host kernel: [ 687.128017] [<f942832d>] ? nvidia_frontend_compat_ioctl+0x1d/0x30 [nvidia]
Mar 16 12:37:23 host kernel: [ 687.128017] [<f942824d>] ? nvidia_frontend_close+0x3d/0x90 [nvidia]
Mar 16 12:37:23 host kernel: [ 687.128017] [<ce1d9f69>] ? __fput+0xc9/0x1d0
Mar 16 12:37:23 host kernel: [ 687.128017] [<ce0824a7>] ? task_work_run+0x77/0x90
Mar 16 12:37:23 host kernel: [ 687.128017] [<ce003095>] ? exit_to_usermode_loop+0xc5/0xd0
Mar 16 12:37:23 host kernel: [ 687.128017] [<ce00379f>] ? do_fast_syscall_32+0x12f/0x150
Mar 16 12:37:23 host kernel: [ 687.128017] [<ce59ecca>] ? sysenter_past_esp+0x47/0x75
Mar 16 12:37:23 host sddm[4251]: Display server failed to start. Exiting
Mar 16 12:37:23 host systemd[1]: sddm.service: Main process exited, code=killed, status=6/ABRT
Mar 16 12:37:23 host systemd[1]: sddm.service: Unit entered failed state.
Mar 16 12:37:23 host systemd[1]: sddm.service: Failed with result 'signal'.
draco
 
Posts: 4
Joined: 2017-03-15 21:33

Re: stretch nvidia-legacy-340xx-driver trouble

Postby horgh » 2017-03-16 23:07

I ran into this exact issue. It looks like I may even have the same card as you.

There is a bug report about it: https://bugs.debian.org/cgi-bin/bugrepo ... bug=830203 (I'm the last poster there as of October)

I am sorry to say that after fighting with it for hours I was unable to get it working. I gave up.

In the bug I linked, one person with the same issue reinstalled Debian with 64bit instead of 32bit, and it began working for them. This might be a solution for you. It is something I did not try as I did not want to reinstall.

One thing also I should mention. If you do happen to leave it broken like I did, you will want to make sure to disable X. It is spinning at 100% CPU when those soft lockup messages are occurring.

Trying 64bit is about all I can suggest. Sorry to be the bearer of bad news. If you do find a solution though, I'd be very interested to hear about it! Good luck!
horgh
 
Posts: 56
Joined: 2008-12-13 10:28

Re: stretch nvidia-legacy-340xx-driver trouble

Postby draco » 2017-03-17 06:17

Thanks for that. So I gave up and move back to nouveau driver. Odd thing, I notice is nouveau driver is saying kms is still enabled. I wonder if those kernel options are not working. I thought nomodeset should disable kms.

BOOT_IMAGE=/boot/vmlinuz-4.9.0-2-686-pae root=UUID=f51652fc-9cde-475c-a1fd-c7d4872e4d14 ro splash nomodeset
(II) modesetting: Driver for Modesetting Kernel Drivers: kms

I guess root cause is a bug in the nvidia driver. I tried to install a Beta version of the nvidia driver but that failed with ERROR: Unable to load the kernel module 'nvidia.ko'. This happens most frequently when this kernel module was built against the wrong or improperly configured kernel sources, with a version of gcc that differs from the one used to build the target kernel
draco
 
Posts: 4
Joined: 2017-03-15 21:33

Re: stretch nvidia-legacy-340xx-driver trouble

Postby TonyT » 2017-03-17 11:49

ERROR: Unable to load the kernel module 'nvidia.ko'. This happens most frequently when this kernel module was built against the wrong or improperly configured kernel sources, with a version of gcc that differs from the one used to build the target kernel
That's the error I got when trying to install the legacy driver from the nvidia site. And I ended up using the nvidia legacy driver from the repositories, which installed properly and works well. But I'm running 64bit.
TonyT
 
Posts: 439
Joined: 2006-09-04 11:57

Re: stretch nvidia-legacy-340xx-driver trouble

Postby Segfault » 2017-03-17 12:00

You also get this error when some framebuffer driver is loaded - like nouveau KMS. It grabs the card and nvidia module cannot load. If you install the blob manually you need to blacklist nouveau by hand, too. Debian package does it for you. 32 bit is dead, I wonder how long it takes to sink in. Officially 32 bit may be supported, but nobody really cares any more.
Segfault
 
Posts: 412
Joined: 2005-09-24 12:24

Re: stretch nvidia-legacy-340xx-driver trouble

Postby debiman » 2017-03-17 19:49

draco wrote:nouveau driver is saying kms is still enabled. I wonder if those kernel options are not working. I thought nomodeset should disable kms.

i'm pretty sure "nomodeset" has nothing to do with disabling KMS.
User avatar
debiman
 
Posts: 974
Joined: 2013-03-12 07:18

Re: stretch nvidia-legacy-340xx-driver trouble

Postby TonyT » 2017-03-17 19:57

To disable KMS for nVidia cards, either:
Boot with the nomodeset kernel command line parameter.
Blacklist the nouveau kernel module, e.g. with
echo blacklist nouveau > /etc/modprobe.d/blacklist-nouveau.conf
and create a minimal /etc/X11/xorg.conf specifying the desired driver, e.g.

https://wiki.debian.org/KernelModesetting
TonyT
 
Posts: 439
Joined: 2006-09-04 11:57

Re: stretch nvidia-legacy-340xx-driver trouble

Postby draco » 2017-03-18 20:47

reinstalled 64bit, now on Linux host 4.9.0-2-amd64 #1 SMP Debian 4.9.13-1 (2017-02-27) x86_64 GNU/Linux

Now it works!!

Thanks all.
draco
 
Posts: 4
Joined: 2017-03-15 21:33


Return to System configuration

Who is online

Users browsing this forum: 4D696B65, darkpenguin and 5 guests

fashionable