Moving Linux kernel to 4.19 [Already moved for many months now (in january 2020)]

[dom]

And yes, I can confirm 4.19 is now available in apt repo.

[Chimneyfactory]

And yes, I can confirm 4.19 is now available in apt repo.

And it's this that seems to have made my HDMI sound intermittently choppy / strange sounding. This problem was persistent across reboots.

Reverting to 4.14.98

Code: Select all

sudo rpi-update a08ece3d48c3c40bf1b501772af9933249c11c5b

resolved the problem.

If I can provide any further info that might be useful, please let me know.

[girante]

Since today I am having issues with accessing i2c channel 0, which I fixed by rolling back to kernel 4.14, as suggested by Chimneyfactory (Thanks!)

Can you create an issue here: https://github.com/raspberrypi/linux/issues
and describe the minimum steps you need to do to see the problem with 4.19 vs 4.14.

Done: https://github.com/raspberrypi/linux/issues/2981

[dom]

And it's this that seems to have made my HDMI sound intermittently choppy / strange sounding. This problem was persistent across reboots.

If I can provide any further info that might be useful, please let me know.

Can you create an issue here:
https://github.com/raspberrypi/linux/issues

where we can try to work out what caused the behaviour change.

[Chimneyfactory]

And it's this that seems to have made my HDMI sound intermittently choppy / strange sounding. This problem was persistent across reboots.

If I can provide any further info that might be useful, please let me know.

Can you create an issue here:
https://github.com/raspberrypi/linux/issues

where we can try to work out what caused the behaviour change.

Having tinkered a bit more today, I've discovered a problem with reporting it - I can't reproduce the problem outside of this pi and it's installation

Existing installation :
4.14.98 : I get 2 brief dropouts within first 2 seconds of MP3 playback in VLC. X-RDP audio works fine
4.19.42 : As above, but continued occasional dropout and clicks can be heard. X-RDP audio very distorted

New installation :
4.14.98 : Sound works fine, no dropouts at all
4.19.42 : Sound works fine, no dropouts at all

(I didn't test X-RDP on the new installation)

So, there's something weird with my installation, which is made worse with the new 4.19.42 kernel / driver package

I'll hold off from reporting it through github unless I can make it reliably reproducable - looks like somethings wrong with my install.

Thanks

[Chimneyfactory]

And it's this that seems to have made my HDMI sound intermittently choppy / strange sounding. This problem was persistent across reboots.

If I can provide any further info that might be useful, please let me know.

Can you create an issue here:
https://github.com/raspberrypi/linux/issues

where we can try to work out what caused the behaviour change.

I've managed to get it repeatable on a fresh install, so logged here https://github.com/raspberrypi/linux/issues/2983

Summary :

Clean install 4.14.98 works fine
Clean install 4.19.42 works fine
4.14.98 with additional software (listed in issue) - some MP3 dropout at start of play, X-RDP is fine
4.19.42 with same additional software (listed in issue) MP3 dropout worse and clicks audible, X-RDP audio distorted

Thanks

[kozman]

I was looking at what was going into 4.19.45 the other day and saw a ton of ARM related work. Hopefully the Pi will benefit.

[itsmedoofer]

Hi,

Should we be seeing the 4.19 kernel when we do an apt update ?

Two of my Pis are on 4.19 now, a Zero and Pi1B but the Pi2 is still on 4.14 with no sign of an update.

Have I missed something?

[rpdom]

Should we be seeing the 4.19 kernel when we do an apt update ?

It seems so. I just did an update and reboot on one Pi and it's now running 4.19.42

Is your Pi 2 running Raspbian Stretch?

[itsmedoofer]

Should we be seeing the 4.19 kernel when we do an apt update ?

It seems so. I just did an update and reboot on one Pi and it's now running 4.19.42

Is your Pi 2 running Raspbian Stretch?

Yea all on stretch.....

[binaryhermit]

I can't help but think the pi2's update slipped through unnoticed and it'll be on 4.19 once rebooted?

[itsmedoofer]

I can't help but think the pi2's update slipped through unnoticed and it'll be on 4.19 once rebooted?

Doh !! Just looked at the up time, 30 odd days, rebooted and I'm magically on 4.19 now.

I usually reboot after an update, must have got distracted here though, thanks for the top tip:)

[dariuszb]

with upgrade to 4.19.46 I seem not to be able to disable internal wifi card on RPi 3 B+.

Until now dtoverlay=pi3-disable-wifi in /boot/config.txt did the job. With 46 wifi is on again despite unchanged /boot/config.txt

as I can tell there is no change in Device Tree overlays for wifi (but it was changed for other things)

https://github.com/raspberrypi/firmware ... ays/README

[DarkPlatinum]

Using fake KMS, 192mb split on RPi 3B+ chromium 72. Getting stuttering in 480p video (non fullscreen).

[kozman]

Using fake KMS, 192mb split on RPi 3B+ chromium 72. Getting stuttering in 480p video (non fullscreen).

And you're on 4.19.42 or 4.19.46?

[DarkPlatinum]

Using fake KMS, 192mb split on RPi 3B+ chromium 72. Getting stuttering in 480p video (non fullscreen).

And you're on 4.19.42 or 4.19.46?

I am on 4.19.42.

[dom]

Using fake KMS, 192mb split on RPi 3B+ chromium 72. Getting stuttering in 480p video (non fullscreen).

Are you saying this configuration has worked better with a previous kernel? If so, which one.

[DarkPlatinum]

Using fake KMS, 192mb split on RPi 3B+ chromium 72. Getting stuttering in 480p video (non fullscreen).

Are you saying this configuration has worked better with a previous kernel? If so, which one.

It had worked better on the 4.14 kernel, (not sure what version but one of the latest ones).

[dom]

It had worked better on the 4.14 kernel, (not sure what version but one of the latest ones).

Can you identify the exact update which caused this. See:
https://github.com/Hexxeh/rpi-firmware/commits/master

If you click on each commit the end of the url contains a git hash. Run

Code: Select all

sudo rpi-update <hash>

to revert back to that version. Report the first version with this problem.

[DarkPlatinum]

What I have found so far with the 4.19.42 kernel is the full-kms driver works fine in 720p fullscreen whereas the fake-kms lags. Could just be a driver issue?

[kozman]

What I have found so far with the 4.19.42 kernel is the full-kms driver works fine in 720p fullscreen whereas the fake-kms lags. Could just be a driver issue?

Probably not likely to help much but is it any different under 4.19.46?

[DarkPlatinum]

Probably not likely to help much but is it any different under 4.19.46?

Upgrading to 4.19.46 is going to be a problem. I use this Raspberry Pi for daily use so if I have issues with the kernel I may lose some data. For the time being I only update with apt-get update (rather than rpi-updat/upgrade).

What I can do is provide data to be used as a comparison on your system.

Kernel 4.19.42, Raspberry Pi 3B+, 192mb split, full-kms:
glxgears averages 53 fps

Raspberry Pi desktop opengl test averages 6 fps.

[kozman]

Probably not likely to help much but is it any different under 4.19.46?

Upgrading to 4.19.46 is going to be a problem. I use this Raspberry Pi for daily use so if I have issues with the kernel I may lose some data. For the time being I only update with apt-get update (rather than rpi-updat/upgrade).

What I can do is provide data to be used as a comparison on your system.

Kernel 4.19.42, Raspberry Pi 3B+, 192mb split, full-kms:
glxgears averages 53 fps

Raspberry Pi desktop opengl test averages 6 fps.

I understand. Do you by chance have a spare micro SD card you could clone your current setup to for testing?

[Twell]

Today ( 2 Jun 2019 ) I did the controversial update and for now everything seems to go well.
My system before the update :

Code: Select all

df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/root        58G  1.2G   55G   3% /
devtmpfs        459M     0  459M   0% /dev
tmpfs           464M     0  464M   0% /dev/shm
tmpfs           464M  6.2M  457M   2% /run
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           464M     0  464M   0% /sys/fs/cgroup
/dev/mmcblk0p1   43M   23M   21M  53% /boot
tmpfs            93M     0   93M   0% /run/user/1000

Code: Select all

uname -a
Linux raspberrypi 4.19.42-v7+ #1219 SMP Tue May 14 21:20:58 BST 2019 armv7l GNU/Linux

Code: Select all

lsb_release -a
No LSB modules are available.
Distributor ID:	Raspbian
Description:	Raspbian GNU/Linux 9.9 (stretch)
Release:	9.9
Codename:	stretch

My system now - after the update - :

Code: Select all

df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/root        58G  1.3G   55G   3% /
devtmpfs        459M     0  459M   0% /dev
tmpfs           464M     0  464M   0% /dev/shm
tmpfs           464M   12M  452M   3% /run
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           464M     0  464M   0% /sys/fs/cgroup
/dev/mmcblk0p1   43M   23M   21M  53% /boot
tmpfs            93M     0   93M   0% /run/user/1000

Code: Select all

uname -a
Linux raspberrypi 4.19.46-v7+ #1230 SMP Tue May 28 16:18:48 BST 2019 armv7l GNU/Linux

In your opinion do I need to check something?
Thank you.

[dom]

In your opinion do I need to check something?

Nope. Minor kernel bumps rarely cause issues so you shouldn't expect a problem, but there are rare exceptions.
The major kernel bumps (e.g. 4.14->4.19) have a higher chance of issues, but they seem to have been resolved now.