This bug was fixed in the package linux-raspi2 - 5.3.0-1028.30
---
linux-raspi2 (5.3.0-1028.30) eoan; urgency=medium
* eoan/linux-raspi2: 5.3.0-1028.30 -proposed tracker (LP: #1882700)
* Eoan update: upstream stable patchset 2020-06-01 (LP: #1881657)
- [Config] updateconfigs
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux-raspi2 (Ubuntu Eoan)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881631
Title:
arm64 Ubuntu kernel builds missing CONFIG_NLS_ASCII
To
** Description changed:
+ 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.
+
+ [Impact]
+ users reported that the raspi ubuntu core has some problem to mount
+ filessytem, need to enable the
ubuntu raspi-5.3 kernel (both armhf and arm64) set this config to m
while ubutnu raspi-5.4 kernel set it to y. Maybe the initrd of ubuntu
core doesn't contain nls_ascii.ko, so we need to set it to y in the
raspi-5.3 too?
--
You received this bug notification because you are a member of Ubuntu
@fginther
I opened this bug report on behalf of @brentk4 from a support ticket.
Please refer to the kernel that referenced in #4.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881631
Title:
arm64
@fginther
Just to make sure that it was not my comment that misled you, I am not
aware of any currently fixed version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881631
Title:
arm64 Ubuntu
@arbell,
Do you have the specific kernel and version you observed this on? A
`uname -a` or `dmesg` log would be sufficient. Based on some of the
comments here, the config value may have changed between versions so I
want to make sure we have the failing one identified correctly.
--
You received
** Attachment removed: "image.png"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1881631/+attachment/5379838/+files/image.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881631
Perhaps looking backward from this Raspberry pi kernel will help locate the
issue, which was definitely present in the build below:
5.3.0-1026-raspi2 #28~18.04.1-Ubuntu SMP Thu May 21 14:48:58 UTC 2020
aarch64 aarch64 aarch64 GNU/Linux
The final kernel that was getting built on arm64 did not
ubuntu-focal.git, focal/raspi2 branch:
debian.raspi2/config/config.common.ubuntu:CONFIG_NLS_ASCII=y
ubuntu-bionic.git, bionic/raspi2 branch:
debian.raspi2/config/config.common.ubuntu:CONFIG_NLS_ASCII=y
So not quite sure where this is coming from
--
You received this bug notification because
this is definitely a regression, mounting partitions should work ...
marking as critical.
** Changed in: linux-raspi2 (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-raspi2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881631
13 matches
Mail list logo
