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

[Twell]

Thanks you very much!
But if you would suggest me a simple check, who would it be?

[deemon]

Code: Select all

pi@raspberrypi:~ $ sudo 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 13545  100 13545    0     0  50063      0 --:--:-- --:--:-- --:--:-- 50166
 *** 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.14.83v7-aufs
#############################################################
WARNING: This update bumps to rpi-4.19.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=224931
##############################################################
Would you like to proceed? (y/N)
 *** 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    401      0 --:--:-- --:--:-- --:--:--   401
100 58.9M  100 58.9M    0     0  2472k      0  0:00:24  0:00:24 --:--:-- 2973k
 *** Updating firmware
 *** Updating kernel modules
 *** depmod 4.19.46+
 *** depmod 4.19.46-v7+
 *** 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 10854879f58a7cc8dbe8ad442b71daa81427e712
 *** A reboot is needed to activate the new firmware
pi@raspberrypi:~ $ sudo reboot

AND after reboot 0 of the 4 USB ports and ethernet port worked (everything else seems to work, shows image even when connected to monitor, just can't log into it because no mouse/keyboard and can't SSH either cause no network)! Same with several other reboots. So kind of borked my Pi / current SD card image.

Ethered/flashed newest Raspbian image to another SD card and after booting it up the USB ports and ETH are working again. No idea how to save my other SD card data though.

[dom]

*** Backing up modules 4.14.83v7-aufs

Are you using berryboot or some other custom kernel?
rpi-update is designed for updating the raspbian kernel. It is not designed for custom kernel builds.

[riavfbip]

Hi,

Would it be possible to enable in further updates to kernel 4.19 CAKE packet scheduler?

Code: Select all

# find /lib/modules/ | grep -c sch_cake
0
# uname -r
4.19.42-v7+

[dom]

Would it be possible to enable in further updates to kernel 4.19 CAKE packet scheduler?

For feature requests create and issue here: https://github.com/raspberrypi/linux/issues
Including links or test results that show the benefits will help.

[kozman]

A little off-topic but I was just reading that Buster will push out on July 6th (https://wiki.debian.org/ReleasePartyBuster) if no showstopper bugs are found. Very excited to see how much benefit Raspbian will reap from the new release.

[jamesh]

A little off-topic but I was just reading that Buster will push out on July 6th (https://wiki.debian.org/ReleasePartyBuster) if no showstopper bugs are found. Very excited to see how much benefit Raspbian will reap from the new release.

Very off topic, please use the buster thread. viewtopic.php?f=66&t=242062

[kozman]

A little off-topic but I was just reading that Buster will push out on July 6th (https://wiki.debian.org/ReleasePartyBuster) if no showstopper bugs are found. Very excited to see how much benefit Raspbian will reap from the new release.

Very off topic, please use the buster thread. viewtopic.php?f=66&t=242062

Apologies. Posted to the right thread.

[allfox]

Hi,

Would it be possible to enable in further updates to kernel 4.19 CAKE packet scheduler?

Code: Select all

# find /lib/modules/ | grep -c sch_cake
0
# uname -r
4.19.42-v7+

I have a little bit info about CAKE.

I've just tried to compile the CAKE module myself. The module itself could be cooked.

However, I still can't use CAKE. Beacuse the iproute2 package can not recognize CAKE. The "tc" command would complain about "unknown qdisc, hance options can not be parsed".

As a traffic shaper, CAKE must be the bottleneck of the network path. So at least, I need to pass a "bandwidth" option to it. Without "tc" command, this can't be done.

So I guess I need to compile iproute2 or I would wait until Raspbian Buster, which would have a newer iproute2 package.

EDIT one hour later: Compiling iproute2 is easy! I'm with CAKE now. HAPPY HACKING.

[HypnoToad]

Is there any change of having the Edimax EW-7811Un USB wifi adaptor work in the 4.19.x kernel?

It used to work OK in older kernels but I 4.19 I get a Kernel Panic.

I had a serial console cable connected at the time so the dump is here if it helps:

https://paste2.org/abJzkwHw

As soon as I switch to another Wifi adaptor, no more kernel panic, but the speed/range of the Edimax was better.

[cjan]

Is there any change of having the Edimax EW-7811Un USB wifi adaptor work in the 4.19.x kernel?

no problem here, just blacklist rtl8192cu and use 8192cu module.

[HypnoToad]

Is there any change of having the Edimax EW-7811Un USB wifi adaptor work in the 4.19.x kernel?

no problem here, just blacklist rtl8192cu and use 8192cu module.

Ok thanks, I'll look up how to do this and give it a try.

[verkerkbr]

Just updated the kernel with rpi-update. I had allready version 4.19.50. Now there is another update called 4.19.50. After the updating the Pi 3b+ did not start. This is the first time an update does not work.

Tried it with another SD card copy. Same result, Pi did not start after the kernel update.

No idea about the cause of this problem.

Otherwise the version 4.19.50 (The first one of course) works very well with the VC4 OpenGL driver (full).

Regards,

Bram

[fruitoftheloom]

Just updated the kernel with rpi-update. I had allready version 4.19.50. Now there is another update called 4.19.50. After the updating the Pi 3b+ did not start. This is the first time an update does not work.

Tried it with another SD card copy. Same result, Pi did not start after the kernel update.

No idea about the cause of this problem.

Otherwise the version 4.19.50 (The first one of course) works very well with the VC4 OpenGL driver (full).

Regards,

Bram

Maybe start afresh with the just released Raspbian Buster which has Kernel 4.19.50 by default ????

https://www.raspberrypi.org/downloads/raspbian/

[verkerkbr]

The kernel 4.19.50 works very well.

It is the latest update also called 4.19.50 that gives the problem with not starting the Pi3b+

Bram

Waiting now for the Pi 4.

[cjan]

latest update tag 4.19.55, Rpi2B won't boot.

[verkerkbr]

Same problem here on a RPI 3B+ with the latest kernel update to 4.19.55.

Boot problem not solved.

Bram

[cjan]

latest update tag 4.19.55, Rpi2B won't boot.

in Buster.img RELEASE note say,
* Boot partition size set to 256M

so, does old /boot 100M no space, cause the problem?

[Twell]

Same problem here on a RPI 3B+ with the latest kernel update to 4.19.55.

Boot problem not solved.

Bram

Really ? We must find what really happens!

[jamesh]

Are all these failures after using rpi-update? We do not recommend using that at all nowadays, and haven't for years. Use apt update to get recent but released and stable firmware and kernel.

[cjan]

Are all these failures after using rpi-update? We do not recommend using that at all nowadays, and haven't for years. Use apt update to get recent but released and stable firmware and kernel.

are you kidding? so what is this thread purpose, @dom asked people to test, right?

[dom]

latest update tag 4.19.55, Rpi2B won't boot.

Is start.elf present? There was a bug in rpi-update that should be fixed now.
Add start_x=1 to config.txt and see if it boots.

[dom]

Are all these failures after using rpi-update? We do not recommend using that at all nowadays, and haven't for years. Use apt update to get recent but released and stable firmware and kernel.

are you kidding? so what is this thread purpose, @dom asked people to test, right?

@jamesh if *everyone* waits for apt kernel/firmware then they will be as untested as rpi-update firmware/kernel.

We need people to test rpi-update kernels/firmwares to spot problems early on.
So thank you to testers who do test these builds.

Obviously people testing these builds should be aware that there may be regressions,
and either have a backup or test on a non-critical Pi.

[verkerkbr]

Just added start_x=1 to the config.txt and then updated to 4.19.55. And now the system boots.

The start sentences text at the startup however are now rather big. Putting the start_x=1 on a other location in the config.txt does not seem to help.

The final working of the system with small text worked well as before.

Regards,

Bram

[jamesh]

Are all these failures after using rpi-update? We do not recommend using that at all nowadays, and haven't for years. Use apt update to get recent but released and stable firmware and kernel.

are you kidding? so what is this thread purpose, @dom asked people to test, right?

Sorry, hadn't realised that this had been suggested. We do NOT recommend people use rpi-update unless asked to do so, in this case, you've obviously been asked to do so. I had to answer so many threads in the last two days it's all getting a bit merged together and I only have time to read a couple of posts back, Soz!