PDA

View Full Version : F23-Nvidia users -- Heads-up!



Dan
15th May 2016, 12:52 PM
Just got this warning in from Leigh, folks. This one could nail a lot of users!



Hi, There is a major nvidia issue about to hit f23

https://bugzilla.redhat.com/show_bug.cgi?id=1335173

https://devtalk.nvidia.com/default/topic/928352/crash-with-kernel-4-5-and-4-6/

As per usual the kernel guys are blaming nvidia http://jwboyer.livejournal.com/52241.html

I don't know why they needed CONFIG_DEBUG_VM_PGFLAGS=y in a release kernel

seems pretty dumb to me.

Could you issue a forum wide warning please?

kingsombra
16th May 2016, 12:10 AM
Does this only apply to v346.42?

The reason I am asking is that I have 3 machines with older nvidia hardware, all happily running akmod 304xx under Korora 23.

But now this has got me a bit worried even though I have not received a panic. :(
(knock on wood especially after going through the MTRR fiasco)

Leigh Scott
16th May 2016, 06:15 AM
Does this only apply to v346.42?

The reason I am asking is that I have 3 machines with older nvidia hardware, all happily running akmod 304xx under Korora 23.

But now this has got me a bit worried even though I have not received a panic. :(
(knock on wood especially after going through the MTRR fiasco)


It affects nvidia-340xx and nvidia-358.16 up to and including the latest version @nvidia.com (364.19), they both crash on boot up with the 4.5/4.6 kernels.

Leigh Scott
16th May 2016, 06:59 AM
Hopefully rpmfusion will accept my pull request for nvidia-kmod and release it quickly.

https://github.com/rpmfusion/nvidia-kmod/pull/1

Maryyy
16th May 2016, 08:02 AM
Aaah, that's why I have kernel, among other things, excluded.
But VBox affected too? I have that excluded as well. :D

So, hardly just Nvidia problem. I surely understand that kernel devs can't easily make it simpler for Nvidia users, but I also understand some of the heat in that bugzilla report.

Anyway, thanx for the warning!

smr54
16th May 2016, 11:14 AM
It does seem, when it's a simple thing to revert, that they'd do it more quickly.

Hello, your kernel breaks things, other kernels don't.

Oh, look, Leigh found the problem, here's the fix.

Maybe someone can get it on the front page of slashdot, which sometimes shames them into fixing it.

Leigh, if you're feeling generous, perhaps you could put in a step by step for beginners of what to do, especially as
Fedora does seem to aim itself at the beginner most of the time.

Leigh Scott
16th May 2016, 05:58 PM
It looks like this wont be an issue now as the 4.5 kernel in updates-testing wont be pushed till it's fixed.

https://bugzilla.redhat.com/show_bug.cgi?id=1335173#c15

smr54
16th May 2016, 06:01 PM
Now _that_ answer makes more sense to me. (That is, on the bug report).

Not that it matters what I think, though. :)

smr54
16th May 2016, 10:59 PM
And by the way Leigh, though I don't use NVidia on Fedora right now, thank you for making the effort to find the issue and offer a patch.

Dan
17th May 2016, 12:37 AM
You can add my thanks to that, too.

hiGuys
17th May 2016, 02:09 AM
Mine too. Your work is appreciated.

damonh
17th May 2016, 03:42 AM
Hey guys,

While I was reading I was simultaneously excluding the kernel from updates, but now it's seems to be safe. I have a nVidia GeForce GT 240 with nVidia drivers v340.96 (manually installed). Do I have to keep my kernel 4.4.9-300 or I can let dnf update it safely?

Thank you.

wintonian
18th May 2016, 12:49 PM
It looks like this wont be an issue now as the 4.5 kernel in updates-testing wont be pushed till it's fixed.

https://bugzilla.redhat.com/show_bug.cgi?id=1335173#c15

I thought this was what rawhide was for? So that us updates-testing guys wouldn't have to find out the hard way. :doh: :p

smr54
18th May 2016, 02:42 PM
It's called testing for a reason.... :)

(I'm not unsympathetic, but I do think that when you run testing anything, that's part of it, having things break, then reporting it.)

In this case, Leigh did some testing and research, pinpointed the problem, and notified them, making it easier for them to revert for now.

wintonian
18th May 2016, 03:12 PM
It had already been obsoleted in bodhi (https://bodhi.fedoraproject.org/updates/FEDORA-2016-0b989bd135) when I got hit - obviosly it takes a while for things to get pushed out and propagated.

Suspect it's been mentioned that kernel-4.5.4-200 (https://bodhi.fedoraproject.org/updates/FEDORA-2016-9d91338972) is in testing now and with all the same issues plus some new bluetooth ones.

shadders
20th May 2016, 02:55 PM
Hi,

On a related note - can someone validate the following on how to install NVidia drivers ? :

https://www.if-not-true-then-false.com/2015/fedora-nvidia-guide/

I have not examined other sites.

Should we use bumblebee project as the correct method ?

http://bumblebee-project.org/

Thanks and regards,

Shadders.

TruboXL
20th May 2016, 05:35 PM
Desktop -> negativo17 repo

Notebook -> Bumblebee repo

Hopefully this is simple enough for you :lol:

shadders
20th May 2016, 07:17 PM
Hi,

Thanks - we all have to start somewhere. :p

Regards,

Shadders.

wintonian
30th May 2016, 01:31 PM
Thought I might just mention that this has been fixed in kernel 4.5.5, currently in updates-testing.