Kernel 3.19-rc4 – OK on CuBox-i4 Pro.. No fixes yet for NVIDIA and VMware on x86..

Updated the test system to Kernel 3.19-rc4, and the same comments apply as for -rc3..  Still no fixes for NVIDIA and VMware, yet..

I tried the CuBox-i4 Pro with a ‘standard’ kernel from kernel.org, rather than the ‘patched’ version used previously, and it booted OK..

Fedora release 21 (Twenty One)
Kernel 3.19.0-rc4 on an armv7l (ttymxc0)
.............
$ uname -a
Linux rgcubox 3.19.0-rc4 #2 SMP Sun Jan 11 20:27:21 EST 2015 armv7l armv7l armv7l GNU/Linux

Details of -rc3 are here:  http://lkml.iu.edu/hypermail/linux/kernel/1501.1/02001.html

And -despite what you may have read elsewhere – there is still no real fix for the ‘lockup’ problem…

It may possibly be that not running systems as just ‘preempt’ may help to mitigate the problem, and I have been running 3.18.2 like this on my main system for a couple of days now, with no lockups – so far!

CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not set

Robert Gadsdon.   January 11, 2015


Comments

Kernel 3.19-rc4 – OK on CuBox-i4 Pro.. No fixes yet for NVIDIA and VMware on x86.. — 2 Comments

  1. Hey there is a fix for NVIDIA as “quoted” from Ubuntu Forums http://ubuntuforums.org/showthread.php?t=2258601 post#4 by 9d9

    “If anyone is having problems with Nvidia drivers and 3.19-rc? kernel, here is how to make them work:
    Change f_dentry to f_path.dentry in nv.c and nv-frontend.c files. And change MODULE_LICENSE(“NVIDIA”); to MODULE_LICENSE(“GPL”); in the same files”

    • This was mentioned in the NVIDIA forums some time ago, but is not an acceptable fix, as changing the license this way is ‘illegal’..

      RG.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.