Problems with nvidia 370.23-1, fan to full speed

VxMxPx · 2016-08-23 09:03:06

I've upgraded nvidia packages to 370.23-1:

==> Software upgrade (new version) :
extra/nvidia                367.35-2 -> 370.23-1
extra/nvidia-libgl          367.35-1 -> 370.23-1
extra/nvidia-utils          367.35-1 -> 370.23-1
multilib/lib32-nvidia-libgl 367.35-1 -> 370.23-1
multilib/lib32-nvidia-utils 367.35-1 -> 370.23-1

==> Continue upgrade ? [Y/n]
==> [V]iew package detail   [M]anually select packages

After reboot system didn't start. It went through normal boot process but when login manager should show up, the screen stayed black and fan (possibly on graphic card) started running at full speed. I had to reboot and downgrade the driver in order for the system to boot properly.

Some information about my graphic card:

› glxinfo -B
name of display: :0.0
display: :0  screen: 0
direct rendering: Yes
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GTX 460/PCIe/SSE2
OpenGL core profile version string: 4.5.0 NVIDIA 367.35
OpenGL core profile shading language version string: 4.50 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.5.0 NVIDIA 367.35
OpenGL shading language version string: 4.50 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)

OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 367.35
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

Jounralctl, some errors (reversed):

Aug 23 10:16:44 mystic-home systemd[1]: lightdm.service: Failed with result 'exit-code'.
Aug 23 10:16:44 mystic-home systemd[1]: lightdm.service: Unit entered failed state.
Aug 23 10:16:44 mystic-home systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Aug 23 10:16:44 mystic-home kernel: NVRM: rm_init_adapter failed for device bearing minor number 0
Aug 23 10:16:44 mystic-home kernel: NVRM: RmInitAdapter failed! (0x53:0x3:1818)
...
Aug 23 10:16:40 mystic-home kernel: NVRM: rm_init_adapter failed for device bearing minor number 0
Aug 23 10:16:40 mystic-home kernel: NVRM: RmInitAdapter failed! (0x53:0x3:1818)
Aug 23 10:16:40 mystic-home nvidia-persistenced[381]: device 0000:01:00.0 - failed to attach.

Last edited by VxMxPx (2016-08-23 09:03:27)

dmitry_k · 2016-08-23 11:35:50

Same issue with GeForce GTX460.

V1del · 2016-08-23 11:41:41

There's https://wiki.archlinux.org/index.php/NV … iled.21.29 for a possible workaround. Maybe nvidia changed their initialization code again

gandalf3 · 2016-08-24 02:28:20

Same here, also with GTX 460

VxMxPx · 2016-08-24 07:11:12

Thanks for suggestion V1del, unfortunately that solution did not work for me.
For now I guess it should be wise if people who own GTX 460 does not go through with this upgrade until the situation is resolved.

dmitry_k · 2016-08-24 14:12:08

It seems 370.23 driver is considered Beta upstream. The latest stable driver 367.44 was released yesterday http://www.nvidia.com/download/driverRe … spx/106780.

zoop · 2016-08-25 08:37:23

Same issue here with a GTX 460. I have opened a bug report about this.

sultanoswing · 2016-08-26 11:31:23

I love this forum you guys. I was getting worried for a second - exactly the same symptoms, exactly the same vid card (GTX460).

/me downgrades nvidia....

Netflux · 2016-08-26 13:32:15

I'm using a GTX1070 and getting the same issue. Seems to be a version mismatch according to journalctl.

EDIT: Turns out the kernel didn't rebuild for me after updating the NVIDIA driver. Had to manually rebuild the kernel after the update.

mkinitcpio -p linux

Last edited by Netflux (2016-08-26 13:56:47)

Smoerrebroed · 2016-08-26 15:46:23

+1

GTX460 and fan@fullspeed. :-| For downgrade, I had to go through all of those nvidia packages and also revert the current kernel to 4.7.1 as somehow the old nvidia module seems incompatible with the most recent kernel. Does anybody have another solution to this? I wanted to avoid recompiling the module.

Cheers,

Smoerrebroed

sultanoswing · 2016-08-26 23:05:15

What a pain.

Had to recompile the older nvidia-lts and nvidia-utils packages in shell, since I didn't have a recent backup in "/var/pacman/cache/pkg". I've used 367.27 as neither 370.23 or nvidia-beta (also 370.23 as of the time of writing) seem to work with either the regular arch linux or the older linux-lts kernels for the GTX460.

Back up and running now after quite some frustration. Hopefully there's a fix soon so I can stop adding "--ignore nvidia-lts --ignore nvidia-utils --ignore nvidia-libgl --ignore opencl-nvidia" to my update routine!

Last edited by sultanoswing (2016-08-29 09:13:55)

Smoerrebroed · 2016-08-27 08:47:41

You can also add those to pacman.conf for as long as the issue persists. Moreover, I found that 367.35 was the last working version for me - perhaps that one will work for you as well?

I wonder if there's anybody with a GPU != GTX460 that has the same issue.

Cheers,

Smoerrebroed

petejones · 2016-08-27 09:19:33

Same issue here with a GTX460 on 370.23. I don't have any issues running 4.7.2 kernel with 367.35.

Last edited by petejones (2016-08-29 10:49:08)

Daerandin · 2016-08-27 10:04:54

I am not having any issues with a GTX980, so this is obviously not an issue for everyone with nvidia cards. It could be that just certain models are affected. The symptoms sounds similar to an issue that was present a couple of years back, so I would second that V1del's suggestion is worth a try.

I would also suggest that the issue is reported to the nvidia forums where the nvidia developers can see it:

https://devtalk.nvidia.com/default/board/98/

Netflux, that is not rebuilding the kernel. That is just rebuilding the initramfs, which should only be required if you use nvidia's DRM-KMS. In that case, it must be done on every nvidia update.

brrbrrbruno · 2016-08-27 16:10:39

Hello Everybody, I just ran into (perhaps) the same problem. After running the update yesterday evening (2016 August 26), the screen would turn black after the systemd startup procedure, the fans were starting to blow on maximum speed and I wasn't able to start a non gui shell session with the usual ctrl-alt-f2. Here is how I solved the problem.

I booted from a usb stick:
https://antergos.com/wiki/install/creat … -live-usb/
or
https://wiki.archlinux.org/index.php/US … tion_media

Once booted into the live session I started a terminal, changed root and looked at the update logs and immediately suspected the nvidia update ...
Read up on changing root here: https://wiki.archlinux.org/index.php/Change_Root

lsblk # to identify /dex/sdXXX of your root and home directory IN MY CASE -> /dev/sdc3 and /dev/sda1
mkdir /mnt/arch
mount /dev/sdc3 /mnt/arch
mount /dev/sda1 /mnt/arch/home
arch-chroot /mnt/arch /bin/bash

Next commands happen in the chroot environment:

cat /var/log/pacman.log | grep 2016-08-26

So I downgraded the nvidia packages and further down the road also the kernel and kernel-headers. Luckily all necessary packages were still in the cache ... Information on downgrading is here: https://wiki.archlinux.org/index.php/Do … g_Packages

cd /var/cache/pacman/pkg/
sudo pacman -U <file_name_of_the_package>

Here is a list of all the downgrades:

[...] downgraded nvidia-libgl (370.23-1 -> 367.35-1)
[...] downgraded lib32-nvidia-utils (370.23-1 -> 367.35-1)
[...] downgraded nvidia-utils (370.23-1 -> 367.35-1)
[...] downgraded lib32-nvidia-libgl (370.23-1 -> 367.35-1)
[...] downgraded linux (4.7.2-1 -> 4.7.1-1)
[...] downgraded linux-headers (4.7.2-1 -> 4.7.1-1)

This let me use my system again ... I have a nvidia gtx 460 and an intel cpu. Hope this helps !!!

Last edited by brrbrrbruno (2016-08-27 16:14:20)

Smoerrebroed · 2016-08-27 16:57:24

N. B.: It does NOT happen on my laptop with NVS 4200M, so it really looks like the GTX460 is part of the problem.

Cheers,

Smoerrebroed

sultanoswing · 2016-08-27 23:39:24

Smoerrebroed wrote:

You can also add those to pacman.conf for as long as the issue persists.

Nice. You learn something new every day!

@brrbrrbruno: I don't think you have to downgrade the kernel packages, just the nvidia and opencl ones.

EDIT: The conspiracy theorist in me suspects this is an evil nvidia plan to enforce upgrading my old GTX460. The realist in me favours cock up over conspiracy.

Last edited by sultanoswing (2016-08-27 23:43:38)

dmitry_k · 2016-08-28 09:14:06

In the meantime, I stick to nvidia-340xx drivers. No need to block anything in the pacman.conf.

Smoerrebroed · 2016-08-29 07:49:28

sultanoswing wrote:

@brrbrrbruno: I don't think you have to downgrade the kernel packages, just the nvidia and opencl ones.

At least for me it didn't work.

modprobe nvidia

will give an error with the most recent kernel so I also downgraded the kernel and that works.

Cheers,

Smoerrebroed

sultanoswing · 2016-08-29 09:16:48

It's interesting that both the 370.23 driver and the 4.7.2 kernel seem to be problematic. In other words older drivers break with the new kernel and the new driver breaks with older kernels, and of course they are broke with each other.

Last edited by sultanoswing (2016-08-29 09:35:08)

Smoerrebroed · 2016-08-29 16:40:27

I have to admit that I did not test any other drivers, and off the top of my head, I do not know about any kernel modules that are not part of the main kernel package (linux), so all modules get updated when the kernel does (which is not the case for nvidia). I agree, though, that in theory modules should not have to be rebuilt between kernel versions of the same major revision.

Cheers

Smoerrebroed

brrbrrbruno · 2016-08-31 15:21:02

sultanoswing wrote:

@brrbrrbruno: I don't think you have to downgrade the kernel packages, just the nvidia and opencl ones.

I had to downgrade the kernel too. Downgrading nvidia drivers only reenabled me to ctr + alt + f2 into shell sessions again. After downgrading the kernel I got me gnome back ...

Smoerrebroed · 2016-09-01 11:38:53

Yes, there seems to be some incompatibility between the older nvidia module and the latest kernel. It even throws an error when you try to load it manually.

Cheers,

Smoerrebroed

sultanoswing · 2016-09-03 22:10:34

dmitry_k wrote:

In the meantime, I stick to nvidia-340xx drivers. No need to block anything in the pacman.conf.

Have done the same thing now. Too much of a hassle compiling drivers from the shell. Don't exactly use the *nix environment for cutting edge gaming, so doubt there's any benefit to using the 'nvidia' drivers over the '340xx' line for me ol' GTX460.

maksle · 2016-09-05 20:36:17

Downgrading to nvidia-340xx didn't work for me for some reason, but downgrading to nvidia 367.35-2 and nvidia-utils 367.35-1 worked for me. I got them from vABS because I didn't have the proper versions in my cache.

Edit: In case it helps someone else avoid the same thing -- I was bitten by a stale initramfs after downgrading the packages -- probably because I was also trying to switch to nouveau entirely when I got frustrated. So you may want to check or edit the modules section of /etc/mkinitcpio.conf and run

mkinitcpio -p linux

and

lsinitcpio | grep nvidia
lsinitcpio | grep nouveau

before rebooting. Also, I did most things via the arch iso, but it was helpful to be able to boot into the OS sometimes with the kernel flag for run level 3, because building the downgraded packages is difficult in the iso due to makepkg not allowing you to build as root.

Last edited by maksle (2016-09-05 20:59:38)

Arch Linux

#1 2016-08-23 09:03:06

Problems with nvidia 370.23-1, fan to full speed

#2 2016-08-23 11:35:50

Re: Problems with nvidia 370.23-1, fan to full speed

#3 2016-08-23 11:41:41

Re: Problems with nvidia 370.23-1, fan to full speed

#4 2016-08-24 02:28:20

Re: Problems with nvidia 370.23-1, fan to full speed

#5 2016-08-24 07:11:12

Re: Problems with nvidia 370.23-1, fan to full speed

#6 2016-08-24 14:12:08

Re: Problems with nvidia 370.23-1, fan to full speed

#7 2016-08-25 08:37:23

Re: Problems with nvidia 370.23-1, fan to full speed

#8 2016-08-26 11:31:23

Re: Problems with nvidia 370.23-1, fan to full speed

#9 2016-08-26 13:32:15

Re: Problems with nvidia 370.23-1, fan to full speed

#10 2016-08-26 15:46:23

Re: Problems with nvidia 370.23-1, fan to full speed

#11 2016-08-26 23:05:15

Re: Problems with nvidia 370.23-1, fan to full speed

#12 2016-08-27 08:47:41

Re: Problems with nvidia 370.23-1, fan to full speed

#13 2016-08-27 09:19:33

Re: Problems with nvidia 370.23-1, fan to full speed

#14 2016-08-27 10:04:54

Re: Problems with nvidia 370.23-1, fan to full speed

#15 2016-08-27 16:10:39

Re: Problems with nvidia 370.23-1, fan to full speed

#16 2016-08-27 16:57:24

Re: Problems with nvidia 370.23-1, fan to full speed

#17 2016-08-27 23:39:24

Re: Problems with nvidia 370.23-1, fan to full speed

#18 2016-08-28 09:14:06

Re: Problems with nvidia 370.23-1, fan to full speed

#19 2016-08-29 07:49:28

Re: Problems with nvidia 370.23-1, fan to full speed

#20 2016-08-29 09:16:48

Re: Problems with nvidia 370.23-1, fan to full speed

#21 2016-08-29 16:40:27

Re: Problems with nvidia 370.23-1, fan to full speed

#22 2016-08-31 15:21:02

Re: Problems with nvidia 370.23-1, fan to full speed

#23 2016-09-01 11:38:53

Re: Problems with nvidia 370.23-1, fan to full speed

#24 2016-09-03 22:10:34

Re: Problems with nvidia 370.23-1, fan to full speed

#25 2016-09-05 20:36:17

Re: Problems with nvidia 370.23-1, fan to full speed

Board footer