Now that Cyanogenmod has summarily shut down, there is a planned new forked version, at http://lineageos.org/ Remains to be seen whether this will flourish, and whether it will survive any potential legal shenanigans, but at least it shows one of the core benefits of Open-Source code..! Robert Gadsdon. December 27, 2016. … Continue reading →
There is now an ‘official’ fix for the 4.10-rc1 compile failure with ARM64/aarch64, from Al Viro, and the patch itself is available here: https://git.kernel.org/cgit/linux/kernel/git/viro/vfs.git/commit/?h=arm64-fix&id=b4b8664d291ac1998e0f0bcdc96b6397f0fe68b3 I have applied this to kernel 4.10-rc1 on the Odroid C2, and the kernel compiles successfully.. Robert Gadsdon. December 27, 2016. … Continue reading →
After applying the aarch64 compile fix (see previous article) I was able to compile Kernel 4.10-rc1 on the Odroid C2, and it boots OK (headless..), and the Ethernet link stays up, but still needs the TX patch.. (updated, as the link did still hang – eventually.. RG).. ……….. meson8b-dwmac c9410000.ethernet eth0: Link is Up – 1Gbps/Full – … Continue reading →
Tried compiling Kernel 4.10-rc1 for aarch64, and got – literally – hundreds of errors: …… ./include/linux/sched.h:3299: Error: unknown mnemonic `return’ — `return test_ti_thread_flag(task_thread_info(tsk),flag)’ ./include/linux/sched.h:3300: Error: junk at end of line, first unrecognized character is `}’ ./include/linux/sched.h:3302: Error: unknown mnemonic `static’ — `static inline void set_tsk_need_resched(struct task_struct*tsk)’ ./include/linux/sched.h:3303: Error: junk at end of line, first unrecognized character is … Continue reading →
Kernel 4.10-rc1 is out, and brief details are here: http://lkml.iu.edu/hypermail/linux/kernel/1612.3/00220.html Installed it on the test system, and (4.9-patched) VMware 12.5.2 is OK, but the latest NVIDIA driver (375.26) fails to compile: ……………….. /home/rgadsdon/kernel/NVIDIA-Linux-x86_64-375.26/kernel/common/inc/nv-mm.h: In function ‘NV_GET_USER_PAGES_REMOTE’: /home/rgadsdon/kernel/NVIDIA-Linux-x86_64-375.26/kernel/common/inc/nv-mm.h:86:20: error: too few arguments to function ‘get_user_pages_remote’ return get_user_pages_remote(tsk, mm, start, nr_pages, flags, pages, vmas); ^~~~~~~~~~~~~~~~~~~~~ ……………….. There was already … Continue reading →
After some of the recent ‘Ethernet fix’ patches have not worked with more recent linux-next kernels, I have found one that – at least at the moment – does fix the ‘hang’ problem – again.. The patch is applied to meson-gxbb-odroidc2.dts, and can be found here: http://archive.arm.linux.org.uk/lurker/message/20161221.113134.3ac4d1e6.en.html I did have to revert this kasir_offset patch (…-R) to … Continue reading →
Recent versions of the Linux net-next tree could not be tested on the C2, as the meson-gx mmc driver was missing, but now it has been added, and I tested the latest version (December 17) – but the Ethernet hang is still there.. To be fair, this is probably because of the current patch conflict that has … Continue reading →
NVIDIA driver 375.26 has been released, and details are available here: http://www.nvidia.com/download/driverResults.aspx/112992/en-us I had been experiencing some odd window (KDE5) behaviour with 375.20, and hopefully things might be more stable with this version.. If not, then possibly kwin is to blame.. Robert Gadsdon. December 14, 2016. … Continue reading →
I had been trying to apply the latest round of Meson TX delay patches to the latest linux-next tree, but found that there seems to be a conflict with some of these.. The December 1 patched kernel now has some problems on my C2 with Ethernet traffic, so – for the time being – I have reverted … Continue reading →
Kernel 4.9 has been released, and (brief!) details of changes are here: http://lkml.iu.edu/hypermail/linux/kernel/1612.1/01831.html The latest NVIDIA (375.20) driver works OK, and VMware 12.5.2 with the vmnet and vmmon hack/patches, also works OK. Hack/patch details are at http://rglinuxtech.com/?p=1838 On my Intel I-7 system (Gigabyte motherboard) I did get some odd ACPI messages at boot time, and it seemed … Continue reading →