Kernel 4.6-rc6 has been released, and details of changes since -rc5 are here: http://lkml.iu.edu/hypermail/linux/kernel/1605.0/00190.html It seems that there will be (at least..) an rc7, before ‘Final’.. Tested with patched VMware 12.1.0 (vmnet and vmmon) and patched NVIDIA (364.19) and both still compile OK.. See my previous article https://rglinuxtech.com/?p=1709 for more info.. Robert Gadsdon. May 2, 2016.
Continue reading →Kernel 4.6-rc5 is out, and brief details of changes from -rc4 are here: http://lkml.iu.edu/hypermail/linux/kernel/1604.3/00178.html Kernel 4.6 seems to have a habit of continuing later-rc breakages with VMware and NVIDIA, compared to previous kernel releases.. The VMware 12 fix for 4.6-rc4 (see https://rglinuxtech.com/?p=1706 ) still works OK with 4.6-rc5, but even the latest NVIDIA driver – 364.19 breaks … Continue reading →
Thanks to Justin Palermo, there is a patch for VMware 12 vmmon and vmnet problems he identified with the later Kernel 4.6-rcs. See comments on my earlier 4.6-rc1 article for details: https://rglinuxtech.com/?p=1679 I have applied the patch to VMware 12.1.0, on Kernel 4.6-rc4, and VMware now compiles and runs OK.. Robert Gadsdon. April 22, 2016.
Continue reading →Being the pioneer/masochist type (aka ‘early-adopter’..), I was intrigued by the new Intel Atom x5-Z8350-powered UP Board, and now have one on (pre)order.. Basic info, with too much graphics.. http://www.up-board.org/specifications/ Not much info on their forum, yet, but it does have UEFI, so (speculation!) should boot with good old GRUB.. One thing it does not have is … Continue reading →
I recently acquired on of the rather quirky Geekbox ARM64 devices, together with the oddly-named ‘Landingstrip’ expansion board.. http://www.cnx-software.com/2015/11/19/geekbox-is-a-hackable-android-and-linux-tv-box-powered-by-rockchip-rk3368-soc/ http://forum.geekbox.tv/ The similarity in overall design to the ARMv7 Radxa Rock2 will be seen from the photo: If you are ordering one, it is worth getting the USB/UART connector as well, as the 3-pin micro flat-pin connection is … Continue reading →
Tested the latest stable NVIDIA driver – 361.42 – with just-released Kernel 4.6-rc2, and it compiles cleanly, with no need for any patches.. …. Building modules, stage 2. MODPOST 3 modules CC /home/rgadsdon/NVIDIA-Linux-x86_64-361.42/kernel/nvidia-modeset.mod.o LD [M] /home/rgadsdon/NVIDIA-Linux-x86_64-361.42/kernel/nvidia-modeset.ko CC /home/rgadsdon/NVIDIA-Linux-x86_64-361.42/kernel/nvidia-uvm.mod.o LD [M] /home/rgadsdon/NVIDIA-Linux-x86_64-361.42/kernel/nvidia-uvm.ko CC /home/rgadsdon/NVIDIA-Linux-x86_64-361.42/kernel/nvidia.mod.o LD [M] /home/rgadsdon/NVIDIA-Linux-x86_64-361.42/kernel/nvidia.ko Robert Gadsdon. April 3, 2016.
Continue reading →Just installed Kernel 4.6-rc1 on the test system. Depending on your configuration, you may encounter a compilation error: CC drivers/thermal/mtk_thermal.o drivers/thermal/mtk_thermal.c: In function ‘mtk_thermal_probe’: drivers/thermal/mtk_thermal.c:560:8: error: implicit declaration of function ‘device_reset’ [-Werror=implicit-function-declaration] ret = device_reset(&pdev->dev); ^ cc1: some warnings being treated as errors ……………………………. This is due to a Mediatek thermal driver being ‘selected’ by default (and … Continue reading →
Kernel 4.5 Final is out, and – as expected – is OK with the latest NVIDIA (361.28) and VMware (12.1.0).. There was nearly one more -RC, but it seems Final was released, instead.. Brief details here: http://lkml.iu.edu/hypermail/linux/kernel/1603.1/04467.html Robert Gadsdon. March 14, 2016.
Continue reading →I recently acquired a vintage (2006?) Minolta Elite 5400 II scanner, and – according to the VueScan support info, I needed to ”set up libusb device protections”.. That info included a link to a somewhat ancient SANE USB support page – last changed in 2003!.. That rang a bell, and I guessed that I had to mess … Continue reading →
I did a clean install of Fedora 23 on my new ‘built from recycled components‘ crash-and-burn test system recently, and all went reasonably well – apart from – apparently – having to re-partition an already-partitioned drive (!)… After booting for the first time, I found that a ‘bridged’ network link – virtbr0 – was active.. As I … Continue reading →