Updated the test system to Kernel 4.9-rc3, and the patch for NVIDIA mentioned in my article for -rc2 still works OK.. I Compiled 370.28 and 375.10 successfully.. As I could not find any patches for VMware – and the latest version 12.5.1 still fails to compile, I created a nasty hack myself.. Warning – This is not … Continue reading →
Updated the test system to Kernel 4.9-rc2, and both VMware (12.5.0) and NVIDIA (370.28 and 375.10) failed to compile.. Fedora 25 (Workstation Edition) Kernel 4.9.0-rc2 on an x86_64 (ttyS0) ………….. # uname -a Linux rgtest 4.9.0-rc2 #1 SMP Sun Oct 23 20:33:10 PDT 2016 x86_64 x86_64 x86_64 GNU/Linux NVIDIA compile fail: ………….. /home/rgadsdon/kernel/NVIDIA-Linux-x86_64-370.28/kernel/nvidia/os-mlock.c:120:55: error: passing argument 5 … Continue reading →
I had been constantly frustrated by the Odroid C2 meson8b-dwmac Ethernet ‘hang’ problem, which has persisted over (at least..) eight different ‘patched kernel’ versions that I have tested.. The network link hung/stopped after a short time at full (1000Mbps) speed, and also – sometimes after a bit longer – at reduced (100Mbps) speed.. The driver does show … Continue reading →
After some of the code for the C2 has been removed from various git repositories, there is a new 4.9-rc1-based tree at https://git.kernel.org/cgit/linux/kernel/git/khilman/linux-amlogic.git/?h=v4.10/integ , which now includes the ‘new’ rewritten MMC driver. To select this, choose ‘Amlogic S905/GX* SD/MMC Host Controller support (MMC_MESON_GX)‘ in the kernel config.. …… Fedora 24 (Workstation Edition) Kernel 4.9.0-rc1-c2 on an aarch64 … Continue reading →
The only missing OS component on the new UP Board (x5-Z8350) was that sound (HDMI) was not present.. After a bit of digging, I found some patches for Kernel 4.5, and a later patched kernel version that was supposed to work.. I tried the patched version of 4.7.0 from here: https://github.com/plbossart/sound/tree/byt-cht-hdmi-v4.7 but found that the compile failed: … Continue reading →
NVIDIA have released their latest driver – 370.23 – which (finally!) works with Kernel 4.7, without any patches.. The driver fails to compile with Kernel 4.8, but the previous 367.35 patch fixes this (See article here: http://rglinuxtech.com/?p=1788). Tested with 4.8-rc2: ………….. ld -r -o /home/rgadsdon/kernel/NVIDIA-Linux-x86_64-370.23-patched/kernel/nvidia-modeset/nv-modeset-interface.o /home/rgadsdon/kernel/NVIDIA-Linux-x86_64-370.23-patched/kernel/nvidia-modeset/nvidia-modeset-linux.o Building modules, stage 2. MODPOST 4 modules CC /home/rgadsdon/kernel/NVIDIA-Linux-x86_64-370.23-patched/kernel/nvidia-drm.mod.o LD [M] … Continue reading →
Kernel 4.7-rc7 is out, and 4.7 Final should be next, but the latest NVIDIA driver released – 367.35 – still fails to compile with 4.7-rc7.. The patch for 367.xx still works OK… Details here: http://rglinuxtech.com/?p=1750 In case you need to create an executable (NVxx.xxx.run) incorporating the patch, details on how to do this are in an older … Continue reading →
Tested some of the kernel versions possible (or not..) for the Next CHIP ARMv7, with mixed results.. I added an Ethernet/USB device (ax88179-based) on the USB hub, and the network connection works fine.. Linux-Next does not yet have the drivers for the Hynix NAND in the CHIP, although – with the rootfs separate on a USB stick … Continue reading →
After the – partial – success with the 96Boards Hikey, I tried the Qualcomm Dragonboard 410c, but the June 29 Linux-Next failed to boot successfully, with only one CPU initialising, and MMC errors, and eventual hang…. ……………………….. psci: failed to boot CPU1 (-95) CPU1: failed to boot: -95 CPU1: failed in unknown state : 0x0 psci: failed … Continue reading →
I have tried the latest 4.7-next patched kernel, from https://github.com/anholt/linux/tree/bcm2837-64-next After some trials, I did manage to – just – get it to boot – after falling to an ’emergency console’, but the system is very unstable, with multiple recurring MMC errors.. ….. Give root password for maintenance (or press Control-D to continue): Error getting authority: Error … Continue reading →