This article relates to compilation on the latest Fedora (21) but can also apply to other Distros… The Distro-supplied version of Audacity is typically functionality-challenged, and does not allow working with some of the more up-to-date audio formats, due to US Patent law concerns.. The necessary functionality can be achieved by compiling it yourself, and this is … Continue reading →
Just updated the Cubox-i4Pro to 3.19-rc1, after disabling the kernel options for ‘power management’, as the current patch does not compile cleanly.. Fedora release 21 (Twenty One) Kernel 3.19.0-rc1 on an armv7l (ttymxc0) ……….. [root@rgcubox ~]# uname -a Linux rgcubox 3.19.0-rc1 #1 SMP PREEMPT Mon Dec 22 15:22:15 EST 2014 armv7l armv7l armv7l GNU/Linux Details of Kernel … Continue reading →
Just installed Kernel 3.19-rc1 on the test system, and both VMware and NVIDIA fail to compile.. VMware (11.0) vmnet failed with: /tmp/modconfig-2fqpf2/vmnet-only/driver.c: In function ‘VNetFileOpUnlockedIoctl’: /tmp/modconfig-2fqpf2/vmnet-only/driver.c:1194:20: error: ‘struct file’ has no member named ‘f_dentry’ if (filp && filp->f_dentry) { ^ /tmp/modconfig-2fqpf2/vmnet-only/driver.c:1195:19: error: ‘struct file’ has no member named ‘f_dentry’ inode = filp->f_dentry->d_inode; ^ scripts/Makefile.build:257: recipe for target … Continue reading →
Just installed Kernel 3.18-rc6, and the latest NVIDIA drivers – 340.58 and 346.16 – compile and load OK… Although VMware have just released version 10.0.4, this still needs the ‘vmnet patch’ to compile OK, with kernels 3.17 and 3.18.. # uname -a Linux rg6830l 3.18.0-rc6 #1 SMP PREEMPT Sun Nov 23 23:41:40 PST 2014 x86_64 x86_64 x86_64 … Continue reading →
VMware have released VMware Workstation version 10.0.4, but it still doesn’t compile with Kernel 3.17 or later.. In fact, the only ‘fix’ appears to be for ‘memory problems with Windows 8.1 and Server 2012’, according to the release notes: https://www.vmware.com/support/ws10/doc/workstation-1004-release-notes.html It would appear that up-to-date compatibility is being kept for the next major release, which is due … Continue reading →
Just installed the kernel.org version of kernel 3.18-rc4 on the Odroid U3, and this time it completed the boot, but still had a ‘tombstone’: …………… cam-power-domain: Power-on latency exceeded, new value 413333 ns cam-power-domain: Power-on latency exceeded, new value 564291 ns Unable to handle kernel NULL pointer dereference at virtual address 00000010 pgd = ee328000 [00000010] *pgd=00000000 … Continue reading →
I had been trying to get USB working with 3.17 and 3.18-rc kernels on my Odroid U3 for some time, and had been looking for fixes in the source code. It turned out that I was looking in the wrong place – and a clue to this was the lack of any mention of the problem on … Continue reading →
Tested Kernel 3.18-rc3 and found that it would not boot with the .config that worked OK with -rc1.. Re-created a new .config from scratch, and now my temporary test system (HP6830 laptop) boots OK, but overall performance still seems rather sluggish.. # uname -a Linux rg6830l 3.18.0-rc3 #1 SMP PREEMPT Mon Nov 3 18:19:06 PST 2014 x86_64 … Continue reading →
Thanks to juston_li, there is a one-line fix to enable the latest NVIDIA drivers to compile with Kernel 3.18-rc1 See: https://devtalk.nvidia.com/default/topic/783364/linux/343-22-driver-incompatible-with-linux-3-18-/ The fix there is for Beta version 343.22, but I applied it to main version 340.46, as follows: In NVIDIA-Linux-x86_64-340.46/kernel/nv-drm.c , at line 19, change #if defined(NV_DRM_AVAILABLE) #include <drm/drmP.h> to #if defined(NV_DRM_AVAILABLE) #include <drm/drmP.h> #include <drm/drm_gem.h> … Continue reading →
Just installed Kernel 3.18-rc1 – released earlier than originally planned – on the test system: $ uname -a Linux rg6830l 3.18.0-rc1 #1 SMP PREEMPT Mon Oct 20 10:23:13 PDT 2014 x86_64 x86_64 x86_64 GNU/Linux Brief details are here: http://lkml.iu.edu/hypermail/linux/kernel/1410.2/01595.html VMware 10.0.3 (with the vmnet patch..) installs and runs OK, but the latest current NVIDIA (340.46) fails to … Continue reading →