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

[dom]

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.

Doing another rpi-update should get the missing start.elf file and you should be able to remove start_x=1 after that.

I don't think anything should have changed the text size.
Possibly the Pi has booted into a lower HDMI resolution.

What does "tvservice -s" report when booted with the "big text". What was it before?

[verkerkbr]

Without the text in the config.txt. System boots now normal. But still in a low resolution startup sequence. After the startup then the text etc is the style as before.

tvservice -s:

state 0x120009 [HDMI DMT (4) RGB full 4:3 640x480 @ 60.00 Hz progressive

Have to start on the former 4.19.50 version on another system to look what it was before.

Never seen this before. I came with the update to the revised 4.19.55.

Regards,

Bram

[alsa]

I have RPi3b+

rpi-update breaks the load. It somehow deletes the start.elf file.
Even if you copy this lost file from somewhere and place it to /boot, Pi is able to boot but starts to work very unstable and slow, and no matter which firmware you have. Even if you rollback to previous kernel, it still work slow and unstable.
I had one more SD card, so I just replaced everything from /boot partition, leaving only my tuned cmdline.txt and config.txt.
After that I booted successfully and performed "apt-get install --reinstall raspberrypi-kernel" to update very old kernel 4.14 to Raspbian 4.19.42 from APT repository. It works now.

P.S. I played around with update to other kernel versions (not latest), and I am absolutely sure that problem is with updater itself, not the kernel.

[dom]

rpi-update breaks the load. It somehow deletes the start.elf file.

When did you update? This should have been fixed at 12:36 today. Any updates after that point should include the start.elf file.

[verkerkbr]

Without the text in the config.txt. System boots now normal. But still in a low resolution startup sequence. After the startup then the text etc is the style as before.

tvservice -s:

state 0x120009 [HDMI DMT (4) RGB full 4:3 640x480 @ 60.00 Hz progressive

Have to start on the former 4.19.50 version on another system to look what it was before.

Never seen this before. I came with the update to the revised 4.19.55.

Regards,

Bram

Looked at the former version 4.19.50. The outcome of Tvservice -s is the same as reported.

Now the system is started with small print sentences.

I'am running the Pi as a marine chartplotter system. Works very well with the VC4 driver on and OpenGL in us with the software.

Thanks for all your efforts.

Regards,

Bram

[verkerkbr]

I'am sorry, but the startup sentences are still in the large fast moving sentences. Difficult to read what is started.

The only thing that I have changed from the 4.19.50 kernel is the latest update 4.19.55.

Bram

[alsa]

When did you update? This should have been fixed at 12:36 today. Any updates after that point should include the start.elf file.

Yesterday. Happy to hear that it is fixed now.
Thanks.

[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+

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.

Commented on existing, but closed GitHub issue for CAKE support on RPi kernel:

https://github.com/raspberrypi/linux/issues/3006

I would appreciated reconsidering adding CAKE to RPi kernel by default as it will be available in 4.19 in all main distros which incorporate it. For example it is with official Debian Buster (amd64).

Regards,
MK

[verkerkbr]

Although it is not recommanded, I always like to try new developments.

Updated to kernel version 4.19.60. But now the the RPI locks up with the cursor in the left upper corner. I found no ways to get around this problem.

Regards,


Bram

[Sirlord]

Hi guys did an update from kernel 4.14.xx to 4.19.66-v7+, 2 days ago using apt-update same audio stuttering as described by Chimneyfactory Mon May 20, 2019 11:59 pm post.

Running:
Rpi 3

Below is the link similiar to mine

https://www.raspberrypi.org/forums/view ... y#p1470973

No solutions for the sound issue yet???

[DougieLawson]

Does the problem persist if you run sudo rpi-update && sudo reboot?

If it does open an issue at https://GitHub.com/raspberrypi/linux with details of how to recreate it.

[dom]

Hi guys did an update from kernel 4.14.xx to 4.19.66-v7+, 2 days ago using apt-update same audio stuttering as described by Chimneyfactory Mon May 20, 2019 11:59 pm post.
No solutions for the sound issue yet???

Possibly this issue: https://github.com/raspberrypi/linux/issues/2983
There is a fix but are waiting for it to be merged upstream.
It looks like it's been submitted and acked, so probably will be merged soon.

[Sirlord]

DougieLawson, thank you, still have problem, it seems like it is similar to problem logged above...will rollback to suggestion.

[Sirlord]

@dom, thank you.

[Sirlord]

Hi guys by rolling back the kernel as suggested in https://github.com/raspberrypi/linux/issues/2983 problem has gone away.

Thanks for the suggestions and help...

[dom]

Hi guys by rolling back the kernel as suggested in https://github.com/raspberrypi/linux/issues/2983 problem has gone away.

Rolling back shouldn't be needed now. Latest rpi-update has been reported to cure the audio issues.

[kozman]

Is the performance enhancing tweak for SPI in 5.4 kernel (https://www.phoronix.com/scan.php?page= ... Better-SPI) likely to be back-ported to the 4.19 series?

[dom]

Is the performance enhancing tweak for SPI in 5.4 kernel (https://www.phoronix.com/scan.php?page= ... Better-SPI) likely to be back-ported to the 4.19 series?

Only if there is a compelling reason. Backporting does have some risk so we'd need a user who had tested the backport and can provide information on the benefits and give us some confidence it doesn't break things.

It's looking like 5.4 will probably be the next upstream LTS kernel, so we are keeping an eye on that as the next stable kernel for raspbian (there are DRM, V3D, V4L2 features coming that would be useful for raspbian users). But it is not always simple - we are still struggling to get the 5.3 kernel working reliably.

[kozman]

Is the performance enhancing tweak for SPI in 5.4 kernel (https://www.phoronix.com/scan.php?page= ... Better-SPI) likely to be back-ported to the 4.19 series?

Only if there is a compelling reason. Backporting does have some risk so we'd need a user who had tested the backport and can provide information on the benefits and give us some confidence it doesn't break things.

It's looking like 5.4 will probably be the next upstream LTS kernel, so we are keeping an eye on that as the next stable kernel for raspbian (there are DRM, V3D, V4L2 features coming that would be useful for raspbian users). But it is not always simple - we are still struggling to get the 5.3 kernel working reliably.

Understandable. Hard to know who'd benefit from that kind of an update without some numbers to show its worthiness. I've loosely been watching what's going into 5.4 via Phoronix and it seems like a worthy upgrade down the road even compared to the goodies in 5.3. The SPI update will be in it anyhow so probably no rush really.. I'd surmise that the 5.3 kernel is just not mature enough yet. Probably won't be playing nice until at least 5.3.25 I would guess. Same for 5.4.

[Gavinmc42]

interesting SPI stuff in 5.4, all those SPI based LCD get faster framerates?
Got some 480 x 320 that have been borderline.
Driver rewrites for them all?
Hey, I have not even tested them on Pi4's yet, they are probably ok now anyway.
Next size up is 640x480? How many SPI ports do we have on Pi4?
5.4 is looking interesting, Pi's becoming more mainstream?

[swahren]

I'd surmise that the 5.3 kernel is just not mature enough yet. Probably won't be playing nice until at least 5.3.25 I would guess. Same for 5.4.

Linux 5.3 is matured enough, the problem is to port all the downstream changes without breaking things.

[kozman]

I'd surmise that the 5.3 kernel is just not mature enough yet. Probably won't be playing nice until at least 5.3.25 I would guess. Same for 5.4.

Linux 5.3 is matured enough, the problem is to port all the downstream changes without breaking things.

Ahem...https://www.phoronix.com/scan.php?page= ... M-Hardware

[trejan]

Ahem...https://www.phoronix.com/scan.php?page= ... M-Hardware

You're aheming the maintainer for the BCM2835 platform in mainline Linux. They only stepped down the other week.

The Pi kernel at https://github.com/raspberrypi/linux/ has a lot of changes that aren't in the mainline kernel so what they're saying is correct.

[swahren]

I'd surmise that the 5.3 kernel is just not mature enough yet. Probably won't be playing nice until at least 5.3.25 I would guess. Same for 5.4.

Linux 5.3 is matured enough, the problem is to port all the downstream changes without breaking things.

Ahem...https://www.phoronix.com/scan.php?page= ... M-Hardware

Just posting a link which summarize the upstreaming efforts of the Raspberry Pi 4 is a different topic. My statement was that with release of Mainline 5.3, there won't be any new feature in this branch. So the RPi folks have to port all there changes from 4.19 into newer kernel releases, which isn't trivial and it's very likely that things break. But i guess you want to point out that the Mainline kernel doesn't have all features of the vendor tree. That's correct.

[Gavinmc42]

Just been using 5.3 on the new release Ubuntu Server.
Don't care enough about Ubuntu to do much more than install a Desktop and see if it worked.
It did, seems slower and takes longer to boot.

I have seen a bunch of Pi commits going into 5.0+.
Wondering why 4.19 is till been worked on?
That post looks like 5.5 for Pi4's will be very mainstream.

Should there be a new post "Moving to kernel 5.5"?