ARM – Updates to 4.1-rc4, and Pi 2 to 4.0.4

Updated the DreamPlug, CuBox-i4Pro, and Odroid U3 to Kernel 4.1-rc4..

DreamPlug and CuBox using the standard code from kernel.org:

Fedora release 18 (Spherical Cow)
Kernel 4.1.0-rc4 on an armv5tel (ttyS0)
...............
]# uname -a
Linux rgdreamplug 4.1.0-rc4 #1 Wed May 20 09:12:43 PDT 2015 armv5tel armv5tel armv5tel GNU/Linux
Fedora release 22 (Twenty Two)
Kernel 4.1.0-rc4 on an armv7l (ttymxc0)
..............
]# uname -a
Linux rgcubox 4.1.0-rc4 #1 SMP Tue May 19 01:13:02 EDT 2015 armv7l armv7l armv7l GNU/Linux

– and the Odroid with the latest code from here: https://github.com/tobiasjakobi/linux-odroid/tree/odroid-4.1.y

Fedora release 22 (Twenty Two)
Kernel 4.1.0-rc4 on an armv7l (ttySAC1)
.............
# uname -a
Linux rgodroid 4.1.0-rc4 #1 SMP Tue May 19 13:58:46 PDT 2015 armv7l armv7l armv7l GNU/Linux

The Raspberry Pi 2 was updated to Kernel 4.0.4, with code from here:  https://github.com/raspberrypi/linux/tree/rpi-4.0.y

Fedora release 22 (Twenty Two)
Kernel 4.0.4-v7 on an armv7l (ttyAMA0)
................
# uname -a
Linux rgpi2 4.0.4-v7 #1 SMP PREEMPT Tue May 19 00:18:06 PDT 2015 armv7l armv7l armv7l GNU/Linux

Brief instructions can be found in earlier articles (use the search site box)..

Robert Gadsdon.   May 20, 2015.

KERNEL – 4.1-rc4 Released – Slightly Late..

Just updated the test system to Kernel 4.1-rc4, and this is OK with the latest NVIDIA drivers (346.72 and 352.09) and with vmnet-patched VMware 11.1..

# uname -a 
Linux rg6830l 4.1.0-rc4 #1 SMP Mon May 18 16:00:31 PDT 2015 x86_64 x86_64 x86_64 GNU/Linux
Details of changes from -rc3 are here:  http://lkml.iu.edu/hypermail/linux/kernel/1505.2/01224.html
Robert Gadsdon.  May 18, 2015.

ARM – DreamPlug and CuBox to 4.1-rc3..

Updated the DreamPlug and CuBox-i4 Pro to Kernel 4.1-rc3, from kernel.org..

Fedora release 18 (Spherical Cow)
Kernel 4.1.0-rc3 on an armv5tel (ttyS0)
...............
# uname -a
Linux rgdreamplug 4.1.0-rc3 #2 Mon May 11 15:04:52 PDT 2015 armv5tel armv5tel armv5tel GNU/Linux
Fedora release 22 (Twenty Two)
Kernel 4.1.0-rc3 on an armv7l (ttymxc0)
................
# uname -a
Linux rgcubox 4.1.0-rc3 #1 SMP Mon May 11 18:03:36 EDT 2015 armv7l armv7l armv7l GNU/Linux

The DreamPlug had a problem booting 4.1-rc1 and -rc2, but -rc3 booted OK..

Robert Gadsdon.   May 11, 2015.

Kernel – 4.1-rc3 – Now OK with NVIDIA..

Just updated the test system to Kernel 4.1-rc3, and confirmed that this is now OK with the latest NVIDIA drivers, and includes the change to linux/arch/x86/kernel/process.c as detailed in a previous article.    Patched VMware 11.x is OK, as before..

# uname -a 
Linux rg6830l 4.1.0-rc3 #1 SMP Mon May 11 07:10:01 PDT 2015 x86_64 x86_64 x86_64 GNU/Linux

Brief details of changes from -rc2 are here:  http://lkml.iu.edu/hypermail/linux/kernel/1505.1/01216.html

Including:

Marc Dionne (1):
x86: Make cpu_tss available to external modules

Robert Gadsdon.   May 11, 2015.

NVIDIA – Kernel 4.1 GPL-only Fixed

The GPL error with NVIDIA drivers and kernel 4.1-rc has been fixed with a patch to linux/arch/x86/kernel/process.c

Details are at http://lkml.iu.edu/hypermail/linux/kernel/1505.0/03818.html.    EXPORT_PER_CPU_SYMBOL_GPL(cpu_tss); has been replaced by EXPORT_PER_CPU_SYMBOL(cpu_tss);

I have applied the patch to Kernel 4.1-rc2, and rebooted, and NVIDIA driver 346.59 now compiles and loads OK..

Robert Gadsdon.   May 6, 2015.

ARM – Odroid to 4.1-rc2

Updated the Odroid U3 to Kernel 4.1-rc2, from https://github.com/tobiasjakobi/linux-odroid/tree/odroid-4.1.y

Apart from the SELinux shenanigans (see previous post..) there were no problems..

Fedora release 22 (Twenty Two)
Kernel 4.1.0-rc2 on an armv7l (ttySAC1)
.....
]# uname -a
Linux rgodroid 4.1.0-rc2 #1 SMP Wed May 6 11:44:37 PDT 2015 armv7l armv7l armv7l GNU/Linux

I had updated to Fedora 22 by using # yum update.. –distro-sync…, as described here:  http://fedoraproject.org/wiki/Upgrading_Fedora_using_yum#Fedora_21_-.3E_Fedora_22_.28not_yet_released.29

Robert Gadsdon.   May 6, 2015

ARM – More SELinux Problems..

After updating the Odroid U3 to kernel 4.1-rc2 (see separate post) I encountered more SELinux / Fedora 22 issues..

This time, SELinux tried to enable itself in ‘targeted’ mode on reboot, despite being ‘disabled’ in the config file..

....
[ OK ] Started Tell Plymouth To Write Out Runtime Data.
[ OK ] Started Preprocess NFS configuration.
*** Warning -- SELinux targeted policy relabel is required.
*** Relabeling could take a very long time, depending on file
*** system size and speed of hard drives.
[ OK ] Started Restore /run/initramfs on shutdown.
[ OK ] Started Rebuild Journal Catalog.
......

SELinux on the CuBox had forced a default to ‘permissive’, but the Odroid defaulted to ‘targeted’, which would force a relabel of all files on the system! As I didn’t want this, I aborted the boot process (pulled the power!)

This would appear to be a possible bug in Fedora 22 – but only on certain armv7 systems.. I have updated one of the x86_64 systems to Fedora 22 and rebooted, and SELinux is staying ‘disabled’.. The Raspberry Pi 2 (armv7) has SELinux configured in the kernel, and has been updated to Fedora 22 – and rebooted – but SELinux stays ‘disabled’..

[root@rgpi2 ~]# sestatus
SELinux status: disabled

Tried setting the kernel boot commands on the Odroid U3 to disable SELinux by adding ‘selinux=0‘ but this had no effect..

I aborted the boot process again, and (cross-)re-compiled the kernel – on another system – to take out SELinux completely..

With that, the Odroid booted without problems..

Robert Gadsdon.  May 6, 2015.

ARM – Rogue SELinux Fixed..?

I updated the CuBox-i4-Pro (Fedora 22) to Kernel 4.1-rc2, but the (re)boot process was very sluggish, with several key commands failing:

.....
systemd[1]: Unit dbus.service entered failed state
.....
[FAILED] Failed to start Login Service.
.....
[FAILED] Failed to start Modem Manager.
.....
[FAILED] Failed to start Avahi mDNS/DNS-SD Stack.
.....
[FAILED] Failed to start Network Manager.

The boot process eventually completed, but there was no networking, and various systemctl commands failed:

Error getting authority: Error initializing authority: Could not connect: Connection refused (g-io-error-quark, 39)

dbus-daemon was not running at all, and attempts to start it manually failed..

My first suspicion was that 4.1-rc2 was the culprit, but reverting to known/good 4.1-rc1 and 4.0.0 resulted in the same problems..

I then tried (re)installing dbus, systemd, etc, but with no change..

I then checked SELinux – which I always have configured as ‘disabled’ – but it appeared to be active, despite this..:

# sestatus
SELinux status: enabled
SELinuxfs mount: /sys/fs/selinux
SELinux root directory: /etc/selinux
Loaded policy name: targeted
Current mode: permissive
Mode from config file: disabled
Policy MLS status: disabled
Policy deny_unknown status: denied
Max kernel policy version: 29
# getenforce
Permissive

Attempts to disable SELinux manually did nothing, and so I decided to ‘remove’ SELinux by de-selecting it in the kernel config, and re-compiling/installing the kernel.

After this, everything worked OK!

I have other ARM systems with similar configurations, where SELinux is behaving correctly (staying ‘disabled’!) and I have another Fedora 22 system (X86_64) with the same software versions where everything also works OK, so have no explanation as to the real cause of this – apart from some possible SELinux persistent aberration on this single system..

But… at least I have an acceptable – if somewhat drastic – fix..

Robert Gadsdon.   May 05, 2015.

ARM – CuBox to 4.1-rc1..

Updated the CuBox-i4Pro to kernel 4.1-rc1 from kernel.org..

Fedora release 22 (Twenty Two)
Kernel 4.1.0-rc1 on an armv7l (ttymxc0)
..........
# uname -a
Linux rgcubox 4.1.0-rc1 #1 SMP Sun Apr 26 23:15:50 EDT 2015 armv7l armv7l armv7l GNU/Linux

I did try to do the same with the DreamPlug, but for some reason it would not boot…   More testing needed..

Robert Gadsdon.   April 27, 2015.

Kernel – 4.1-rc1 – OK with VMware, not with NVIDIA..

I should have known that 4.1-rc1 would show up just after I published my linux-next article, and here it is..  ftp://ftp.kernel.org/pub/linux/kernel/v4.x/testing/linux-4.1-rc1.tar.xz

$ uname -a Linux rg6830l 4.1.0-rc1 #1 SMP Sun Apr 26 18:56:05 PDT 2015 x86_64 x86_64 x86_64 GNU/Linux

Brief details are here:   http://lkml.iu.edu/hypermail/linux/kernel/1504.3/01263.html

As with linux-next from April 24, the (patched) VMware 11.1.0 compiled and loaded OK, but the latest NVIDIA driver – 349.16 – failed:

FATAL: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol 'cpu_tss'

Some have suggested fixing these errors by simply editing the offending kernel code to disable the GPL-only rule, but this is in fact the wrong thing to do.    Either the kernel development team makes the change, or NVIDIA has to change their code.

It is worth mentioning again that the VMware patch is still the one for Kernel 3.19 – which also works for kernel 4.0 and now 4.1..     Full instructions – and a copy of the patch – can be found at the excellent ArchLinux wiki:   https://wiki.archlinux.org/index.php/VMware#3.19_kernels_and_up

Robert Gadsdon  April 26, 2015.