Raspberry Pi Forums

The ACT LED has been renamed from "led0" to "ACT" to match its function, the dtparams that configure it, and the upstream kernel. Similarly, the PWR LED has been renamed from "led1" to "PWR". But in general it's better to test that the numeric result of "...

The aggressive OoM killer problem is now the subject of a GitHub issue: https://github.com/raspberrypi/linux/issues/5395

Since you've requested to stay on the 32-bit kernel with arm_64bit=0, aside from the jump to 6.1 the main change with this release is an increase to the CMA allocation to 512MB. Does changing your config.txt from "dtoverlay=vc4-kms-v3d" to "dtoverlay=vc4-kms-v3d,cma-320", or even...

tryboot.txt is an alternative config.txt, not an alternative cmdline.txt. If you want to use a different kernel command line you can either use "cmdline=" or "os_prefix=<subdir>/", and put the test kernel, overlays and cmdline.txt in "/boot/<subdir>", i.e. directory &qu...

The DTB load address is not fixed - it varies based on the size of the DTB and other settings - but for any given configuration it is fixed and can be determined by the output of "sudo vcdbg log msg": 003774.994: Device tree loaded to 0x2eff7a00 (size 0x855c) In almost all cases on a Pi 3 ...

Only a reboot is required - it is just telling the firmware which kernel to load. Adding it to the [pi4] section is sufficient, but there's no harm in putting it in the [all] section unless you want a Pi 3 to load the 64-bit kernel.

And yes, the documentation does need to be updated.

Most users will find that a Pi 4 runs better on a 64-bit kernel, so the default for Pi 4s (including Pi 400 and CM4) has been changed to arm_64bit=1.

To force the 32-bit kernel to be used on Pi 4s:

Code: Select all

arm_64bit=0

Which applications don't work for you with a 64-bit kernel?

Thanks, nikal. I've closed the Pull Request for now - more work is clearly needed.

Does a regular "sudo reboot" also hang? There should be no difference in that regard. You can enable logging from the bootloader using the BOOT_UART setting: https://www.raspberrypi.com/documentati ... #BOOT_UART

No, just tell me if it seems to work for you.

@nikal Here is the command to install the test kernel into a "test" subdirectory:

Code: Select all

sudo WANT_32BIT=1 FW_SUBDIR=test rpi-update pulls/5388

To select the new kernel, add the following to config.txt:

Code: Select all

os_prefix=test/

(note the trailing slash character)

I honestly think this is a low risk test, the risk being that the 6.2 kernel doesn't support your use cases. The best protection is to clone your SD card, but short of that we can minimise the risk by installing the kernel to a different directory, with a config.txt check to switch between the two. ...

The relevant options and driver support appear with 6.2: config RTW88_8822BU tristate "Realtek 8822BU USB wireless network adapter" Select this option will enable support for 8822BU chipset 802.11ac USB wireless network adapter config RTW88_8822CU tristate "Realtek 8822CU USB wireless...

This looks like a race between udev and systemd running the hciuart service. The service exists to run btuart, which is effectively a wrapper around hciattach that invokes it with the correct parameters. One of these parameters is the name of the UART device, for which btuart uses "/dev/serial1...

This command should do what you want:

Code: Select all

sudo apt remove pi-bluetooth bluez-firmware bluez

N.B. I have not tested this, and the advice comes with no warranty - use at your own risk.

There are several config options that may be relevant: config RTW88_8822BE tristate "Realtek 8822BE PCI wireless network adapter" Select this option will enable support for 8822BE chipset 802.11ac PCIe wireless network adapter config RTW88_8822CE tristate "Realtek 8822CE PCI wireless ...

If that's the case we can look at back-porting it into our 6.1 branch.

Cross-compiling modules is not a use case I had considered before Friday. Apart from the need to use a different toolchain, I don't believe that any of your module building problems will be difficult to overcome given a bit of time. With arm_64bit=0, are you able to build and install your external m...

The krnbt option (letting the kernel initialise the HCI device) is likely to become the default in the future so it's slightly better than a workaround, but I need to investigate to understand the failure you are seeing.

And does adding "dtparam=krnbt" to config.txt improve things?

I have no explanation for the apparent link between /boot and Bluetooth. What does ”systemctl status hciuart" report?

See here for instructions: viewtopic.php?t=344246&start=275#p2091356

The names have changed to align with upstream, and to be more logical. They are called ACT and PWR.

To expand on my earlier post a bit, after installing the ARM 32 -> 64-bit compiler toolchain: sudo apt install gcc-aarch64-linux-gnu you just need to ensure that your kernel "make" lines include "ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu-", e.g. make ARCH=arm64 CROSS_COMPILE=aar...

Search found 4575 matches

Re: Moving Linux Kernel to 6.1

Re: Moving Linux Kernel to 6.1

Re: Moving Linux Kernel to 6.1

Re: Reboot tryboot hangs on my CM4

Re: Device Tree blob Load Address - RPI 3B

Re: apt-get dist-upgrade installs aarch64 kernel

Re: apt-get dist-upgrade installs aarch64 kernel

Re: apt-get dist-upgrade installs aarch64 kernel

Re: After apt upgrade my 32 Bit OS runs on a 64 bit kernel and now I can't compile an external module.

Re: Reboot tryboot hangs on my CM4

Re: After apt upgrade my 32 Bit OS runs on a 64 bit kernel and now I can't compile an external module.

Re: After apt upgrade my 32 Bit OS runs on a 64 bit kernel and now I can't compile an external module.

Re: After apt upgrade my 32 Bit OS runs on a 64 bit kernel and now I can't compile an external module.

Re: After apt upgrade my 32 Bit OS runs on a 64 bit kernel and now I can't compile an external module.

Re: /boot partition after kernel is loaded

Re: How do you remove Bluetooth in bullseye?

Re: After apt upgrade my 32 Bit OS runs on a 64 bit kernel and now I can't compile an external module.

Re: After apt upgrade my 32 Bit OS runs on a 64 bit kernel and now I can't compile an external module.

Re: After apt upgrade my 32 Bit OS runs on a 64 bit kernel and now I can't compile an external module.

Re: /boot partition after kernel is loaded

Re: /boot partition after kernel is loaded

Re: /boot partition after kernel is loaded

Re: After apt upgrade my 32 Bit OS runs on a 64 bit kernel and now I can't compile an external module.

Re: Moving Linux Kernel to 6.1

Re: Moving Linux Kernel to 6.1