User avatar
kneekoo
Posts: 19
Joined: Mon Dec 29, 2014 7:08 am

Re: Moving Linux kernel to 4.14

Fri Mar 30, 2018 3:26 pm

dom wrote:
Fri Mar 30, 2018 10:47 am
Can you explain exactly what you mean by the audio applet menu? Where is this menu, what did it used to do and how has it changed?

This is the sound applet menu, and clicking vc4-hdmi has absolutely no effect, other than closing the menu.
Image

robgill
Posts: 1
Joined: Sun Apr 01, 2018 5:30 am

Re: Moving Linux kernel to 4.14

Sun Apr 01, 2018 5:47 am

One issue to be aware of if you host an L2TP/IPsec vpn on your pi : There is a known bug in kernel 4.14 causing issues with ipsec.

This bug is present in 4.14.30-v7+, and 4.14.31-v7+.

Reverting to 4.9.79-v7+ works as a temporary solution until 4.14 is patched.


https://libreswan.org/wiki/FAQ#L2TP_.2F ... tem_update

gerardf87
Posts: 3
Joined: Mon Apr 02, 2018 3:37 pm

Re: Moving Linux kernel to 4.14

Mon Apr 02, 2018 3:39 pm

I have some kernel crashes using plex media server with 4.14. Reverted to 4.9 and now it's working fine again.

itsacoolaccount
Posts: 17
Joined: Sun Mar 18, 2018 8:04 pm

Re: Moving Linux kernel to 4.14

Tue Apr 03, 2018 4:44 am

:o

Code: Select all

echo thats amazing!

Code: Select all

sudo apt-get install coffee

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5138
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Moving Linux kernel to 4.14

Tue Apr 03, 2018 11:43 am

kneekoo wrote:
Fri Mar 30, 2018 3:26 pm
This is the sound applet menu, and clicking vc4-hdmi has absolutely no effect, other than closing the menu.
Image
vc4-hdmi isn't a default option in that menu. Did you enable the experimental vc4 graphics driver?

User avatar
kneekoo
Posts: 19
Joined: Mon Dec 29, 2014 7:08 am

Re: Moving Linux kernel to 4.14

Sat Apr 07, 2018 9:24 pm

dom wrote:
Tue Apr 03, 2018 11:43 am
vc4-hdmi isn't a default option in that menu. Did you enable the experimental vc4 graphics driver?
Indeed, I enabled it so I can play Need For Speed II Special Edition. :D But I think it was there before I enabled the experimental driver. I'm just not sure... Anyway, there should be some feedback when we click that option, or it shouldn't be there.

I really wonder when the VC4 driver will get out of the experimental stage and become the default, and stable. Is there an effort to test it in a public/organized manner, so we can help with feedback?

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5138
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Moving Linux kernel to 4.14

Tue Apr 10, 2018 11:34 am

kneekoo wrote:
Sat Apr 07, 2018 9:24 pm
I really wonder when the VC4 driver will get out of the experimental stage and become the default, and stable. Is there an effort to test it in a public/organized manner, so we can help with feedback?
While the vc4 driver is working well for most for most desktop apps, there is still work ongoing to get GPU services like camera and video decode working well with it. We can't make it the default until everything works well.

drmullins
Posts: 26
Joined: Fri Jun 23, 2017 9:22 pm

Re: Moving Linux kernel to 4.14

Tue Apr 10, 2018 12:00 pm

I have just updated a couple of my raspberry pis from 4.9.80 to 4.14.30 kernel

Unfortunately I have found issues with the new kernel
- autofs no longer working viewtopic.php?f=66&t=210429 and
- Realtek USB wifi adapter driver no longer compiling properly viewtopic.php?f=66&t=191844#p1299245
as reported in separate posts.
Reverting to the 4.9.80 kernel resolved both these issues

I use autofs extensively as I have a network of Raspberry Pis (and a couple of Debian x86 PCs) which act as portals to a group of servers and I need to use USB wifi adapters on some devices remote from a wireless hub. Work arounds would be needed to work with current 4.14 kernel hence to avoid these I have decided to revert to 4.9.80 kernel for the immediate future . Nevertheless I appreciate the reasons for moving to kernel 4.14 for long term support.

However my key question is whether there are any disadvantages or risks associated with sticking with the 4.9.80 kernel for the short to medium term while the kernel issues are (hopefully) resolved ?

jamesh
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 19352
Joined: Sat Jul 30, 2011 7:41 pm

Re: Moving Linux kernel to 4.14

Tue Apr 10, 2018 12:41 pm

drmullins wrote:
Tue Apr 10, 2018 12:00 pm
I have just updated a couple of my raspberry pis from 4.9.80 to 4.14.30 kernel

Unfortunately I have found issues with the new kernel
- autofs no longer working viewtopic.php?f=66&t=210429 and
- Realtek USB wifi adapter driver no longer compiling properly viewtopic.php?f=66&t=191844#p1299245
as reported in separate posts.
Reverting to the 4.9.80 kernel resolved both these issues

I use autofs extensively as I have a network of Raspberry Pis (and a couple of Debian x86 PCs) which act as portals to a group of servers and I need to use USB wifi adapters on some devices remote from a wireless hub. Work arounds would be needed to work with current 4.14 kernel hence to avoid these I have decided to revert to 4.9.80 kernel for the immediate future . Nevertheless I appreciate the reasons for moving to kernel 4.14 for long term support.

However my key question is whether there are any disadvantages or risks associated with sticking with the 4.9.80 kernel for the short to medium term while the kernel issues are (hopefully) resolved ?
We won't be updating 4.9 any more (e.g. security issues), but TBH, you should be fine with it as it stands, until all the issues with 4.14 are sorted.
Principal Software Engineer at Raspberry Pi (Trading) Ltd.
Please direct all questions to the forum, I do not do support via PM.

daz.uk
Posts: 7
Joined: Sat Mar 15, 2014 10:11 am
Location: Leeds, UK
Contact: Website

Re: Moving Linux kernel to 4.14

Wed Apr 25, 2018 5:30 am

Hello,
Just a courtesy question. Is there any progress on the horizon for 4.14 (or maybe newer) issue with VPN XL2TP as described here:
https://github.com/xelerance/xl2tpd/issues/147

Tried to bo back to kernel 4.9.x but Pi3B+ stucking on rainbow.

beta-tester
Posts: 1206
Joined: Fri Jan 04, 2013 1:57 pm
Location: de_DE

Re: Moving Linux kernel to 4.14

Wed Apr 25, 2018 12:21 pm

daz.uk wrote:
Wed Apr 25, 2018 5:30 am
Tried to bo back to kernel 4.9.x but Pi3B+ stucking on rainbow.
did you tried 2018-03-13-raspbian-stretch.zip? this is the first version that supports RPi3B+ at all and has Kernel 4.9.80+.
{ I only give negative feedback }
RPi Model B (rev1, 256MB) & B (rev2, 512MB) & B+, RPi2B (1GB), 64GB microSDXC1 class 10, HDMI 1920x1080, keyboard-mouse-combo (wireless), PiCamera, ethernet-cable, 5V/1.2A power supply, Wifi dongle (rt5370)

gerardf87
Posts: 3
Joined: Mon Apr 02, 2018 3:37 pm

Re: Moving Linux kernel to 4.14

Sat Apr 28, 2018 2:06 pm

gerardf87 wrote:
Mon Apr 02, 2018 3:39 pm
I have some kernel crashes using plex media server with 4.14. Reverted to 4.9 and now it's working fine again.
I quote my publication only to inform that with the latest version 4.14.34 everything is working perfectly and I have zero issues.
Great work, thank you. :D

User avatar
DougieLawson
Posts: 32380
Joined: Sun Jun 16, 2013 11:19 pm
Location: Basingstoke, UK
Contact: Website

Re: Moving Linux kernel to 4.14

Sat Apr 28, 2018 2:35 pm

gerardf87 wrote:
Sat Apr 28, 2018 2:06 pm
gerardf87 wrote:
Mon Apr 02, 2018 3:39 pm
I have some kernel crashes using plex media server with 4.14. Reverted to 4.9 and now it's working fine again.
I quote my publication only to inform that with the latest version 4.14.34 everything is working perfectly and I have zero issues.
Great work, thank you. :D
You're out of date, current rpi-update kernel is 4.14.37+ or 4.14.37-v7+.
Microprocessor, Raspberry Pi & Arduino Hacker
Mainframe database troubleshooter
MQTT Evangelist
Twitter: @DougieLawson

2012-18: 1B*5, 2B*2, B+, A+, Z, ZW, 3Bs*3, 3B+

Any DMs sent on Twitter will be answered next month.

fred44nl
Posts: 246
Joined: Sat Jun 25, 2016 11:59 am
Location: Scharendijke, NL

Re: Moving Linux kernel to 4.14

Sat Apr 28, 2018 5:49 pm

when will we get kernel 4.14.37 with sudo apt-get upgrade or dist-upgrade ??
or is rpi-update the only way ??
headless RPi 3B running from usbhdd.

hommar
Posts: 124
Joined: Sat Mar 25, 2017 1:55 pm
Location: Russia, Yekaterinburg

Re: Moving Linux kernel to 4.14

Sat Apr 28, 2018 6:35 pm

daz.uk wrote:
Wed Apr 25, 2018 5:30 am
Tried to bo back to kernel 4.9.x but Pi3B+ stucking on rainbow.
for install official release 4.9.80 kernel with 3B+ support run command

Code: Select all

sudo rpi-update 936a8dc3a605c20058fbb23672d6b47bca77b0d5

User avatar
DougieLawson
Posts: 32380
Joined: Sun Jun 16, 2013 11:19 pm
Location: Basingstoke, UK
Contact: Website

Re: Moving Linux kernel to 4.14

Sat Apr 28, 2018 7:05 pm

fred44nl wrote:
Sat Apr 28, 2018 5:49 pm
when will we get kernel 4.14.37 with sudo apt-get upgrade or dist-upgrade ??
or is rpi-update the only way ??
It's not in Raspbian 2018-04-18 (it's got 4.14.34+ 4.14.34-v7+). The next Raspbian will have a newer kernel.

So right now rpi-update is the only way, but you MUST backup your SDCard before you start and you must understand what rpi-update does to your system before running it. You also need to have a positive reason to move to the testing kernel and boot code from the the stable 4.14.34 kernel.
Microprocessor, Raspberry Pi & Arduino Hacker
Mainframe database troubleshooter
MQTT Evangelist
Twitter: @DougieLawson

2012-18: 1B*5, 2B*2, B+, A+, Z, ZW, 3Bs*3, 3B+

Any DMs sent on Twitter will be answered next month.

gerardf87
Posts: 3
Joined: Mon Apr 02, 2018 3:37 pm

Re: Moving Linux kernel to 4.14

Sun Apr 29, 2018 2:49 am

DougieLawson wrote:
Sat Apr 28, 2018 2:35 pm
gerardf87 wrote:
Sat Apr 28, 2018 2:06 pm
gerardf87 wrote:
Mon Apr 02, 2018 3:39 pm
I have some kernel crashes using plex media server with 4.14. Reverted to 4.9 and now it's working fine again.
I quote my publication only to inform that with the latest version 4.14.34 everything is working perfectly and I have zero issues.
Great work, thank you. :D
You're out of date, current rpi-update kernel is 4.14.37+ or 4.14.37-v7+.
Yes, I know, I mean the latest stable update via apt update

fred44nl
Posts: 246
Joined: Sat Jun 25, 2016 11:59 am
Location: Scharendijke, NL

Re: Moving Linux kernel to 4.14

Sun Apr 29, 2018 8:16 am

gerardf87 wrote:
Sun Apr 29, 2018 2:49 am
DougieLawson wrote:
Sat Apr 28, 2018 2:35 pm
You're out of date, current rpi-update kernel is 4.14.37+ or 4.14.37-v7+.
Yes, I know, I mean the latest stable update via apt update
if you look at Debian.org there is an overview of the available kernel versions.
like old-stable, stable, unstable, testing, etc.etc.
is there a similar overview for Raspbian ??
headless RPi 3B running from usbhdd.

ejolson
Posts: 1448
Joined: Tue Mar 18, 2014 11:47 am

Re: Moving Linux kernel to 4.14

Sun Apr 29, 2018 5:16 pm

I'm having some troubles using jumbo packets with USB gadget driver on the 4.14 kernel. I doubt additional limitations were introduce into the upstream kernel sources; however, maybe configuration options are now different. If anyone has time to look, it would be interesting to know what needs to be done to get jumbo packets back in the gadget driver.

d_older
Posts: 90
Joined: Mon Jun 25, 2012 5:04 pm
Location: East Yorkshire, UK

Re: Moving Linux kernel to 4.14

Mon Apr 30, 2018 10:39 pm

Hi Folks,

as I posted in the thread mentioned above, viewtopic.php?f=63&t=212289&p=1309317#p1309317, the g_cdc module /manually set combined ethernet and ecm via configfs fails with 4.14.35+34+.(edit 2018-05-01) (I was wondering in that thread if it was related to ejolson's gadget ethernet jumbo frame issue.)

After loading the config module and looking at /proc/config.gz I have noticed both

Code: Select all

# CONFIG_USB_CONFIGFS is not set

and

# CONFIG_USB_FUNCTIONFS is not set

which surprised me as the setup phase appears to work - the correct modules appear to be loaded after creating the /sys/kernel/config/usb_gadget entries and the ecm and acm interfaces are seen by a Debian 4.9 kernel host - but the ethernet doesn't connect and the serial is slow to be initialised and only operates in one direction.

Note that the g_cdc module works perfectly with the zero(W) with stretch on 4.9

Hope this another piece in the jigsaw of a solution to the gadget issues.

Dave
Last edited by d_older on Tue May 01, 2018 9:28 pm, edited 1 time in total.

hommar
Posts: 124
Joined: Sat Mar 25, 2017 1:55 pm
Location: Russia, Yekaterinburg

Re: Moving Linux kernel to 4.14

Tue May 01, 2018 5:38 am

d_older wrote:
Mon Apr 30, 2018 10:39 pm
Hope this another piece in the jigsaw of a solution to the gadget issues.
You should create an issue on github: https://github.com/raspberrypi/linux/issues

ejolson
Posts: 1448
Joined: Tue Mar 18, 2014 11:47 am

Re: Moving Linux kernel to 4.14

Tue May 01, 2018 5:44 am

hommar wrote:
Tue May 01, 2018 5:38 am
d_older wrote:
Mon Apr 30, 2018 10:39 pm
Hope this another piece in the jigsaw of a solution to the gadget issues.
You should create an issue on github: https://github.com/raspberrypi/linux/issues
If you open an issue, could also mention the Jumbo packets? I don't personally have a GitHub account and don't see getting one any time soon.

Ernst
Posts: 426
Joined: Sat Feb 04, 2017 9:39 am
Location: Germany

Re: Moving Linux kernel to 4.14

Tue May 01, 2018 7:10 am

d_older wrote:
Mon Apr 30, 2018 10:39 pm
Note that the g_cdc module works perfectly with the zero(W) with stretch on 4.9
The g_cdc module works perfectly with the Pi zero using stretch with 4.14.34

This is what uname reports on the systems connected to a clusterhat on a Pi3B:

Code: Select all

pi@raspi1:~ $ for a in 3 3p1 3p2 3p3 3p4; do ssh raspi$a uname -a; done
Linux raspi3 4.14.34-v7+ #1110 SMP Mon Apr 16 15:18:51 BST 2018 armv7l GNU/Linux
Linux raspi3p1 4.14.34+ #1110 Mon Apr 16 14:51:42 BST 2018 armv6l GNU/Linux
Linux raspi3p2 4.14.34+ #1110 Mon Apr 16 14:51:42 BST 2018 armv6l GNU/Linux
Linux raspi3p3 4.14.34+ #1110 Mon Apr 16 14:51:42 BST 2018 armv6l GNU/Linux
Linux raspi3p4 4.14.34+ #1110 Mon Apr 16 14:51:42 BST 2018 armv6l GNU/Linux
My first computer was an ICT1500, my first "personal" computer was the Sinclair MK14

ejolson
Posts: 1448
Joined: Tue Mar 18, 2014 11:47 am

Re: Moving Linux kernel to 4.14

Tue May 01, 2018 7:37 am

Ernst wrote:
Tue May 01, 2018 7:10 am
d_older wrote:
Mon Apr 30, 2018 10:39 pm
Note that the g_cdc module works perfectly with the zero(W) with stretch on 4.9
The g_cdc module works perfectly with the Pi zero using stretch with 4.14.34

This is what uname reports on the systems connected to a clusterhat on a Pi3B:

Code: Select all

pi@raspi1:~ $ for a in 3 3p1 3p2 3p3 3p4; do ssh raspi$a uname -a; done
Linux raspi3 4.14.34-v7+ #1110 SMP Mon Apr 16 15:18:51 BST 2018 armv7l GNU/Linux
Linux raspi3p1 4.14.34+ #1110 Mon Apr 16 14:51:42 BST 2018 armv6l GNU/Linux
Linux raspi3p2 4.14.34+ #1110 Mon Apr 16 14:51:42 BST 2018 armv6l GNU/Linux
Linux raspi3p3 4.14.34+ #1110 Mon Apr 16 14:51:42 BST 2018 armv6l GNU/Linux
Linux raspi3p4 4.14.34+ #1110 Mon Apr 16 14:51:42 BST 2018 armv6l GNU/Linux
That looks promising. Could you check whether you can enable Jumbo packets with something like

# ip link set usb0 mtu 7418

on each of the Zero nodes as well as the Pi host?

Ernst
Posts: 426
Joined: Sat Feb 04, 2017 9:39 am
Location: Germany

Re: Moving Linux kernel to 4.14

Tue May 01, 2018 7:52 am

ejolson wrote:
Tue May 01, 2018 7:37 am
That looks promising. Could you check whether you can enable Jumbo packets with something like

# ip link set usb0 mtu 7418

on each of the Zero nodes as well as the Pi host?
The command fails on the Pi Zero:

Code: Select all

Raspbian GNU/Linux 9 raspi3p1 ttyGS0
IPv4: 192.168.0.231 IPv6:

raspi3p1 login: pi
Password:
Last login: Tue May  1 09:39:04 CEST 2018 from 192.168.0.5 on pts/0
Linux raspi3p1 4.14.34+ #1110 Mon Apr 16 14:51:42 BST 2018 armv6l
pi@raspi3p1:~$ ifconfig
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 4  bytes 392 (392.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 4  bytes 392 (392.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

usb0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.231  netmask 255.255.255.0  broadcast 192.168.0.255
        ether 00:22:82:ff:ff:01  txqueuelen 1000  (Ethernet)
        RX packets 56557  bytes 16245829 (15.4 MiB)
        RX errors 0  dropped 2733  overruns 0  frame 0
        TX packets 7695  bytes 541599 (528.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

pi@raspi3p1:~$ sudo ip link set usb0 mtu 7418
RTNETLINK answers: Invalid argument
pi@raspi3p1:~$ sudo ip link set usb0 mtu 9000
RTNETLINK answers: Invalid argument
pi@raspi3p1:~$ 
On the controller the command is accepted:

Code: Select all

pi@raspi3:~ $ ifconfig
br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.230  netmask 255.255.255.0  broadcast 192.168.0.255
        ether b8:27:eb:81:b2:bf  txqueuelen 1000  (Ethernet)
        RX packets 58602  bytes 20845500 (19.8 MiB)
        RX errors 0  dropped 2656  overruns 0  frame 0
        TX packets 9311  bytes 690104 (673.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether b8:27:eb:81:b2:bf  txqueuelen 1000  (Ethernet)
        RX packets 161206  bytes 89531752 (85.3 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 38472  bytes 3033900 (2.8 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ethpi1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether 00:22:82:ff:fe:01  txqueuelen 1000  (Ethernet)
        RX packets 7697  bytes 433933 (423.7 KiB)
        RX errors 3  dropped 0  overruns 0  frame 0
        TX packets 56631  bytes 17044218 (16.2 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ethpi2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether 00:22:82:ff:fe:02  txqueuelen 1000  (Ethernet)
        RX packets 7310  bytes 397054 (387.7 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 56457  bytes 17018578 (16.2 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ethpi3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether 00:22:82:ff:fe:03  txqueuelen 1000  (Ethernet)
        RX packets 7001  bytes 386164 (377.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 56470  bytes 17020573 (16.2 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ethpi4: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether 00:22:82:ff:fe:04  txqueuelen 1000  (Ethernet)
        RX packets 7290  bytes 397394 (388.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 56559  bytes 17033906 (16.2 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 5  bytes 421 (421.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 5  bytes 421 (421.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

pi@raspi3:~ $ sudo ip link set ethpi1 mtu 7418
pi@raspi3:~ $ ifconfig ethpi1
ethpi1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 7418
        ether 00:22:82:ff:fe:01  txqueuelen 1000  (Ethernet)
        RX packets 7698  bytes 433965 (423.7 KiB)
        RX errors 3  dropped 0  overruns 0  frame 0
        TX packets 56647  bytes 17045658 (16.2 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

pi@raspi3:~ $ sudo ip link set ethpi1 mtu 1500
pi@raspi3:~ $
My first computer was an ICT1500, my first "personal" computer was the Sinclair MK14

Return to “Advanced users”

Who is online

Users browsing this forum: mfa298 and 12 guests