Moving Linux kernel to 4.14

[dom]

EDIT:
###############################################################################
4.14 kernel is now available from apt-get. No need to use rpi-update just for getting 4.14 kernel.
###############################################################################

We are planning to move to the 4.14 kernel in the near future.
One advantage is there is a lot more raspberry pi specific support in the newer upstream kernels which reduces the number of downstream raspberry pi patches and so reduces maintenance effort.
The 4.14 kernel is planned to be an LTS kernel (long term support).

Obviously a newer kernel will bring additional kernel features and support for more devices (e.g. USB devices like wifi and dvb).
You can read up on what appeared in 4.10, 4.11 ,4.12, 4.13 and 4.14.

We will do this in a few stages. Starting now, we are updating the "next" firmware branch to the 4.14 kernel.
Assuming testing is positive, we'll update the master rpi-update firmware branch.
Eventually the 4.14 kernel will appear in "apt-get upgrade" and on new raspbian images in the future.

The 4.14 kernel has been used in LibreELEC nightly builds (as an optional build over last couple of months, and now the default for last couple of days).

Update with:

Code: Select all

sudo rpi-update

and reboot. Ideally nothing much will change.
Please report if there are any regressions compared to the 4.9 kernel.

Obviously this release is for testers who like to live on the bleeding edge. It's not intended for beginners, or users who need stability.
Backing up is always advisable. There may be regressions. There may be improvements. But we won't know without testers trying it and reporting back.

[beta-tester]

Code: Select all

NICE  __
      ) )
     / /_____
____/  (_____)
       (_____)
       (_____)
---\___(____)

[jahboater]

Works fine for me, as you predicted its much the same!
Pi3 full Raspbian accessed over VNC and ssh.
No special drivers.

[beta-tester]

RPi2B, Raspbian Stretch,

Code: Select all

Linux ... 4.14.0-v7+ #1050 SMP Tue Nov 14 13:28:57 GMT 2017 armv7l GNU/Linux

so far no issues...
no errors in dmesg...
nfs/exports/tftp working...
used additional packages are working:
samba, dnsmasq, nfs-kernel-server, rpcbind, chrony, ...
the RPi is acting as PXE-server.

[sphinxou]

bonjour

depuis mise à jour je ne peux plus utiliser les GPIO.

merci

[cjan]

enable FKMS boot fail, black screen.

[DougieLawson]

Code: Select all

NICE  __
      ) )
     / /_____
____/  (_____)
       (_____)
       (_____)
---\___(____)

+1

I've got one RPi3B running a locally built 4.14 kernel. BRANCH=next will save me the bother of kernel building.

[dom]

depuis mise à jour je ne peux plus utiliser les GPIO.

English only here. You'll need to report exactly what you are doing (e.g. which gpio library and what commands you ran and what was the output).

[notro]

It seems that the papirus overlay and tinydrm defconfig from PR 2119 didn't make it over to rpi-4.14.y (the drivers are present).
https://github.com/raspberrypi/linux/pu ... 271466d7bd
https://github.com/raspberrypi/linux/pu ... 9fcb9c3ad8

[dom]

It seems that the papirus overlay and tinydrm defconfig from PR 2119 didn't make it over to rpi-4.14.y (the drivers are present).
https://github.com/raspberrypi/linux/pu ... 271466d7bd
https://github.com/raspberrypi/linux/pu ... 9fcb9c3ad8

No problem - will add.

[cjan]

enable FKMS boot fail, black screen.

so, ignore it or it just me?

[DougieLawson]

enable FKMS boot fail, black screen.

so, ignore it or it just me?

What do you expect running a still very broken pre-alpha testing graphics module on a beta testing kernel?

[Gavinmc42]

Been wondering when this was going to happen.
Does that mean Eric Anholt can relax about back porting all his new stuff to Raspbian 4.9.x?
4.15 is just out, too soon?

Bleeding edge? Yep, some people like to live there, some like Eric have Obsidian scalpels.
Others like me follow behind with old bread knives, good enough to hack a loaf of bread to make toast
I have bandaids

[cjan]

enable FKMS boot fail, black screen.

so, ignore it or it just me?

What do you expect running a still very broken pre-alpha testing graphics module on a beta testing kernel?

NO, i don't use VC4 driver just test, OP ask feedback then I do, but no respond.

[ShiftPlusOne]

NO, i don't use VC4 driver just test, OP ask feedback then I do, but no respond.

It's probably something that will take some looking into and can't be addressed straight away.

[jamesh]

so, ignore it or it just me?

What do you expect running a still very broken pre-alpha testing graphics module on a beta testing kernel?

NO, i don't use VC4 driver just test, OP ask feedback then I do, but no respond.

We cannot respond to every post of a bug request thread like this, since there are usually loads of them for a new release. But all reports are useful, and they are all kept in one place in this thread so we have easy access to them.

[dom]

It seems that the papirus overlay and tinydrm defconfig from PR 2119 didn't make it over to rpi-4.14.y (the drivers are present).

Commits are cherry-picked (but untested) to 4.14 tree. Will be in next rpi-update.

[dom]

enable FKMS boot fail, black screen.

Noted. I believe I have seen FKMS driver working on an earlier 4.14 kernel, but haven't tested very recently. Wil do soon.

[asavah]

Can anyone running 4.14 confirm RPi.GPIO not working?

Code: Select all

Nov 18 22:06:42 rpi3 systemd[1]: Started keypad handler.
Nov 18 22:06:43 rpi3 keypad.py[1234]: starting button: 21
Nov 18 22:06:43 rpi3 keypad.py[1234]: starting button: 20
Nov 18 22:06:43 rpi3 keypad.py[1234]: button 21 (kodi) pid: 1237
Nov 18 22:06:43 rpi3 keypad.py[1234]: button 20 (reboot) pid: 1238
Nov 18 22:06:43 rpi3 keypad.py[1234]: button 16 (poweroff) pid: 1239
Nov 18 22:06:43 rpi3 keypad.py[1234]: button 12 (toggle_clock) pid: 1240
Nov 18 22:06:43 rpi3 keypad.py[1234]: tmon pid: 1241
Nov 18 22:06:43 rpi3 keypad.py[1234]: clock pid: 1242
Nov 18 22:06:43 rpi3 kernel: export_store: invalid GPIO 21
Nov 18 22:06:43 rpi3 keypad.py[1234]: starting button: 16
Nov 18 22:06:43 rpi3 kernel: export_store: invalid GPIO 20
Nov 18 22:06:43 rpi3 kernel: export_store: invalid GPIO 16
Nov 18 22:06:43 rpi3 keypad.py[1234]: starting button: 12
Nov 18 22:06:43 rpi3 keypad.py[1234]: starting tmon: 26
Nov 18 22:06:43 rpi3 kernel: export_store: invalid GPIO 12

This seems to be reported here https://sourceforge.net/p/raspberry-gpi ... ckets/150/

Haven't tried the patch yet, will do and report later.

Code: Select all

ls /sys/class/gpio/ -alh
total 0
drwxrwx---  2 root gpio    0 Nov 18 00:24 .
drwxr-xr-x 51 root root    0 Nov 18 00:24 ..
-rwxrwx---  1 root gpio 4.0K Nov 18 00:24 export
lrwxrwxrwx  1 root gpio    0 Nov 18 00:24 gpiochip100 -> ../../devices/gpiochip2/gpio/gpiochip100
lrwxrwxrwx  1 root gpio    0 Nov 18 00:24 gpiochip128 -> ../../devices/gpiochip1/gpio/gpiochip128
lrwxrwxrwx  1 root gpio    0 Nov 18 00:24 gpiochip458 -> ../../devices/platform/soc/3f200000.gpio/gpio/gpiochip458
-rwxrwx---  1 root gpio 4.0K Nov 18 00:24 unexport

[Kordon]

Tested both kms and fkms driver. The kms boots but with black screen (tested with any parameters like hdmi_boost), fkms doesn't boot.

[dom]

Updated to upstream 4.14.1. Also includes some missing commits from this PR.
Also added a commit that fixes the gpio numbering to start from zero which could fix asavah's issue.
As usual, to update run:

Code: Select all

sudo BRANCH=next rpi-update

[asavah]

.
Also added a commit that fixes the gpio numbering to start from zero which could fix asavah's issue.

Thanks.
Yep, that's fixed, built the kernel yesterday and RPi.GPIO/gpiozero work as expected.
Haven't tried that RPi.GPIO patch I linked, busy week ...

[djlegge]

This does not seem to work with a version 1 compute module. I have stripped everything down to :
- Flash CM1 with 2017-09-07-raspbian-stretch-lite.img
- Enable ssh, use USB ethernet adaptor.

Code: Select all

sudo apt update
sudo apt upgrade
sudo reboot

All okay. Now :

Code: Select all

sudo BRANCH=next rpi-update
reboot

Fails to boot (stuck on rainbow screen). It does this even on the original CM1 I/O carrier board.
Replacing the /boot contents with the backup reverts the update and it boots up once more.
It's not actually an issue for me but as I don't need to upgrade but I'd be interested to know what's going on...

[fluffysheap]

I can confirm the issues with kms and fkms. I don't know what's wrong with fkms, maybe I'll hook up a serial console tomorrow, the system doesn't boot far enough to start networking so no logs available without serial console. I have a fully upgraded Stretch (and also Gentoo, but no difference in the results though).

My somewhat longer comments on KMS are here: https://github.com/raspberrypi/firmware/issues/909

HDMI with KMS driver works well, but the DSI screen is unusable. FKMS doesn't boot no matter what kind of display is connected. Tested HDMI and headless on pi2 and HDMI and DSI on pi3.

I have tried a wide variety of config.txt options to get KMS to work, including the usual ones like various settings for CMA/gpu_mem and obsolete ones like mask_gpu_interrupt1, and got no results.

[paul433]

How is the testing going? Has there been a decision made to make the transition official?