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

Re: Moving Linux kernel to 4.14

Tue May 01, 2018 10:35 pm

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
I was using a Debian 64 bit 9.4 box - 4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) where I was having issues I didn't see with Pi 4.9.

I've now tried Pi3 4.14.34-v7+ to Pi zero W 4.14.34+ and that works. The only issue I have is that stty does not appear to be able to set speed on the zero side

Code: Select all

stty: /dev/ttyGS0: unable to perform all requested operations
There is no error if attempted from the host side but miniterm.py still reports the original 9600.

A workround seems to be using miniterm.py's speed option on both sides and that is reported as being used.

Many thanks Ernst for your reply.

Unfortunately this doesn't help with ejolson's jumbo frame issue.

Now onto the "non-legacy" configfs method pi to pi to see if the "missing" kernel settings are required for that.

Dave

Note I've edited my original to 4.14.34+ (fat fingers)

edge0f17
Posts: 17
Joined: Sun Oct 25, 2015 6:55 am

Re: Moving Linux kernel to 4.14

Wed May 02, 2018 7:46 am

I have looked at the jumbo frames issue, and it was already broken in Linux 4.12. Likely due to the commit: https://github.com/raspberrypi/linux/co ... 183ed30443

This had unintended consequences that I in no way understand:
https://github.com/raspberrypi/linux/co ... e825711a94

Needs to be reported and fixed upstream.

edge0f17
Posts: 17
Joined: Sun Oct 25, 2015 6:55 am

Re: Moving Linux kernel to 4.14

Wed May 02, 2018 12:26 pm

https://github.com/raspberrypi/linux/co ... f41103d422

fixed max_mtu in the function gether_setup_name(), but that one is not used: they should have fixed gether_setup_name_default()

Looks like an easy fix.

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

Re: Moving Linux kernel to 4.14

Thu May 03, 2018 2:19 pm

edge0f17 wrote:
Wed May 02, 2018 12:26 pm
they should have fixed gether_setup_name_default()

Looks like an easy fix.
That's great news! Thanks for checking into this. I wonder how soon the fix for this regression will be included in the official kernel.

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

Re: Moving Linux kernel to 4.14

Wed May 09, 2018 5:05 pm

Another regression with the 4.14 series kernel is reported here. The issue seems to be that the new kernel requires an additional module in the initial ram filesystem, if booting that way. This could also be fixed by building the necessary module into the kernel.

Alex.
Posts: 6
Joined: Sun Feb 25, 2018 9:49 pm

Re: Moving Linux kernel to 4.14

Wed May 09, 2018 8:21 pm

ejolson wrote:
Wed May 09, 2018 5:05 pm
Another regression with the 4.14 series kernel is reported here. The issue seems to be that the new kernel requires an additional module in the initial ram filesystem, if booting that way. This could also be fixed by building the necessary module into the kernel.
It seems that's the same (or similar) FIQ bug issued here viewtopic.php?f=29&t=197689&start=50#p1272684
Don't know why it triggers only with a ramfs

DennisT
Posts: 3
Joined: Tue Jul 05, 2016 8:45 pm

Re: Moving Linux kernel to 4.14

Tue Jun 12, 2018 5:17 pm

Hi,
I ran this update and am now having a problem. Hopefully there's a fix available. I have a RPi3B set up as a kiosk device (Raspbian Jesse). It feeds a VGA monitor via a HDMI to VGA adapter. The application is a python script run full screen under xterm.
Startup is like:

Code: Select all

# disable DPMS (Energy Star) features.
xset -dpms
# disable screen saver
xset s off
# don't blank the video device
xset s noblank
# disable mouse pointer
unclutter &
# run window manager
matchbox-window-manager -use_cursor no -use_titlebar no  &
#start x11vnc for remote access
x11vnc -forever -usepw -display :0 &
# run xterm
lxterminal --geometry=150x50 --command /usr/local/bin/TC.sh
abbreviated TC.sh is

Code: Select all

unbuffer $BASEPATH/TimeClock.py
The application monitors activity and turns off the display by making an OS call:
tvservice -o
When activity occurs it then turns the display back on:
tvservice -p >/dev/null 2>&1
fbset -depth 8;
fbset -depth 16;

This has all been working fine for months. I need to add some capability and upgrade some things. That lead me to rpi-update.
rpi-update results:

Code: Select all

root@DC0:/home/pi# rpi-update
 *** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
 *** Performing self-update
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 13403  100 13403    0     0   111k      0 --:--:-- --:--:-- --:--:--  111k
 *** Relaunching after update
 *** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
 *** We're running for the first time
 *** Backing up files (this will take a few minutes)
 *** Backing up firmware
 *** Backing up modules 4.4.13-v7+
#############################################################
This update bumps to rpi-4.14.y linux tree
Be aware there could be compatibility issues with some drivers
Discussion here:
https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=197689
##############################################################
 *** Downloading specific firmware revision (this will take a few minutes)
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   168    0   168    0     0    744      0 --:--:-- --:--:-- --:--:--   746
100 55.8M  100 55.8M    0     0  4227k      0  0:00:13  0:00:13 --:--:-- 3808k
 *** Updating firmware
 *** Updating kernel modules
 *** depmod 4.14.48-v7+
 *** depmod 4.14.48+
 *** Updating VideoCore libraries
 *** Using HardFP libraries
 *** Updating SDK
 *** Running ldconfig
 *** Storing current firmware revision
 *** Deleting downloaded files
 *** Syncing changes to disk
 *** If no errors appeared, your firmware was successfully updated to 31eb6c5d0f7374ba8404104e60618d40f54f1e8c
 *** A reboot is needed to activate the new firmware
root@DC0:/home/pi# reboot
Finally, the issue I'm having. Once I've run rpi-update the script to turn the display back on doesn't work properly. The display comes back on, but the screen is scrambled. Colors are messed up and it appears as if the data being displayed is at a different resolution:
Image
Running this
root@DC0:/home/pi# fbset

mode "800x600"
geometry 800 600 800 600 16
timings 0 0 0 0 0 0 0
rgba 5/11,6/5,5/0,0/16
endmode

shows the correct settings.

Any help would be appreciated.

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

Re: Moving Linux kernel to 4.14

Tue Jun 12, 2018 7:24 pm

DennisT wrote:
Tue Jun 12, 2018 5:17 pm
Finally, the issue I'm having. Once I've run rpi-update the script to turn the display back on doesn't work properly. The display comes back on, but the screen is scrambled. Colors are messed up and it appears as if the data being displayed is at a different resolution:
This sounds more like a firmware than kernel issue. Can you create an issue here?
https://github.com/raspberrypi/firmware/issues

DennisT
Posts: 3
Joined: Tue Jul 05, 2016 8:45 pm

Re: Moving Linux kernel to 4.14

Wed Jun 13, 2018 4:16 pm

Thanks, I opened a issue there. It turns out the upgrade goes from a 16bpp framebuffer to a 32bpp for the console.
fbset -depth 32
should fix the problem.
However I found
vcgencmd display_power
command during my research and went with that instead.

adamreisnz
Posts: 4
Joined: Sat Sep 16, 2017 9:29 am

Re: Moving Linux kernel to 4.14

Thu Jun 14, 2018 12:09 am

I am experiencing issues with 4.14 crashing the Raspberry Pi when reading inputs from the GPIO.
The issue is documented here: https://github.com/raspberrypi/linux/issues/2550

How can I run `apt-get upgrade` on an older version of Raspbian but avoid the kernel being upgraded from 4.9 to 4.14?

Return to “Advanced users”

Who is online

Users browsing this forum: No registered users and 8 guests