So is it now changed to 'y'?  Last night I confirmed that the module is
missing in initrd.img and that is what was causing the mount error, so
this is great news.

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.

  arm64 Ubuntu kernel builds missing CONFIG_NLS_ASCII

Status in linux-raspi2 package in Ubuntu:
Status in linux-raspi2 source package in Eoan:
  Fix Committed

Bug description:
  The CONFIG_NLS_ASCII was already set to Y in the raspi-5.4 kernel
  and bionic kernel by Juerg, now do the same change in the
  raspi2-5.3 kernel.

  users reported that the raspi ubuntu core has some problem to mount
  filessytem, need to enable the NLS_ASCII and make it built-in.

  change it from m to y just as the focal and bionic raspi kernel.

  [Test Case]
  building the kernel and boot the kernel, it could mount the
  filesystem successfully.

  [Regression Risk]
  Low, just changing a kconfig to y from m.

  Remounting log mounts in Ubuntu core are failing on arm64 builds due to 
missing CONFIG_NLS_ASCII in the arm64 kernel build options.
  This option is enabled on the other kernel builds but somehow was overlooked 
on arm64 appears to affect our ability to access logs via journalctl with data 
from prior to restart because certain mounts are failing.
  Other Raspberry Pi kernel builds, such as the armhf build, have the option 
enabled and so do not encounter the mount error.
  The kernel option that needs to be turned on to resolve this is 
CONFIG_NLS_ASCII. It needs to be set to either 'm' or 'y'. Most of the other 
chips have it set to 'y', keeping it built-in.

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to