[Bug 1926911] Re: hctosys not reading hardware clock on CM4

2021-06-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-raspi - 5.4.0-1036.39 --- linux-raspi (5.4.0-1036.39) focal; urgency=medium * focal/linux-raspi: 5.4.0-1036.39 -proposed tracker (LP: #1927614) * Raspberry Pi kernel config doesn't match generic for NFT, breaks LXD (LP: #1927108) -

[Bug 1926911] Re: hctosys not reading hardware clock on CM4

2021-05-11 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-raspi (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/1926911 Title:

[Bug 1926911] Re: hctosys not reading hardware clock on CM4

2021-05-07 Thread Tim Gardner
** Changed in: linux-raspi (Ubuntu Focal) Status: Confirmed => 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/1926911 Title: hctosys not reading hardware clock on CM4 To manage

[Bug 1926911] Re: hctosys not reading hardware clock on CM4

2021-05-03 Thread Juerg Haefliger
** Description changed: + [Impact] + + At boot, the kernel does not synchronize the system clock from an RTC, + if the driver that manages the RTC device is built as a module. + + [Test Case] + + $ dmesg|grep rtc + [1.593561] hctosys: unable to open rtc device (rtc0) + [ 10.767256]

[Bug 1926911] Re: hctosys not reading hardware clock on CM4

2021-05-03 Thread Oliver Grawert
https://github.com/snapcore/core-initrd/issues/17 ** Bug watch added: github.com/snapcore/core-initrd/issues #17 https://github.com/snapcore/core-initrd/issues/17 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1926911] Re: hctosys not reading hardware clock on CM4

2021-05-03 Thread Oliver Grawert
hirsute does not have Ubuntu Core images ;) It seems to be solvable via a simple defconfig change according to: https://github.com/raspberrypi/linux/issues/4205 We have at least one UC customer implementing a CM4 baseboard with TPM for Full disk encryption and secureboot in UC20, for this the

[Bug 1926911] Re: hctosys not reading hardware clock on CM4

2021-05-03 Thread Juerg Haefliger
Hirsute looks fine: $ uname -a Linux rpi-cm4-rev1d0-e428 5.11.0-1005-raspi #5 SMP PREEMPT Mon Apr 19 09:04:31 UTC 2021 armv7l armv7l armv7l GNU/Linux $ sudo dmesg | grep rtc [0.00] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0

[Bug 1926911] Re: hctosys not reading hardware clock on CM4

2021-05-03 Thread Juerg Haefliger
Seem focal: $ uname -a Linux rpi-cm4-rev1d0-e428 5.4.0-1034-raspi #37-Ubuntu SMP PREEMPT Mon Apr 12 23:14:49 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux $ sudo dmesg | grep rtc [0.00] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0

[Bug 1926911] Re: hctosys not reading hardware clock on CM4

2021-05-03 Thread Oliver Grawert
ogra@CM4:~$ snap list pi-kernel Name VersionRev Tracking Publisher Notes pi-kernel 5.4.0-1035.38 282 20/edge canonical✓ kernel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1926911] Re: hctosys not reading hardware clock on CM4

2021-05-03 Thread Juerg Haefliger
Which kernel? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926911 Title: hctosys not reading hardware clock on CM4 To manage notifications about this bug go to:

[Bug 1926911] Re: hctosys not reading hardware clock on CM4

2021-05-02 Thread Oliver Grawert
** Description changed: There is a timing issue when using the CM4 with the official CM4 IO baseboard. The CM4 baseboard comes with a built in rtc and a battery holder by default, to enable it a devicetree overlay needs to be enabled and a matching module gets loaded ... $ tail