# Hwclock failed with “hwclock: Cannot access the Hardware Clock via any known method.”

**URL:** https://community.solid-run.com/t/hwclock-failed-with-hwclock-cannot-access-the-hardware-clock-via-any-known-method/345
**Category:** NXP LX2160
**Tags:** NXP-LX2160
**Created:** [June 7, 2022, 4:34am UTC](https://community.solid-run.com/t/hwclock-failed-with-hwclock-cannot-access-the-hardware-clock-via-any-known-method/345 "2022-06-07T04:34:52Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![vader](https://avatars.discourse-cdn.com/v4/letter/v/9d8465/32.png) [@vader](https://community.solid-run.com/u/vader)
#### Post date: [June 7, 2022, 4:34am UTC](https://community.solid-run.com/t/hwclock-failed-with-hwclock-cannot-access-the-hardware-clock-via-any-known-method/345/1 "2022-06-07T04:34:52Z")

</div>

new LX2160A Board and I download the newest image，but when I  
update hwclock ,unfortunately, I failed.

err msgs:

> root@bogon:~# hwclock -w  
> hwclock: Cannot access the Hardware Clock via any known method.  
> hwclock: Use the --verbose option to see the details of our search for an access method.

image info

> root@bogon:~# uname -a  
> Linux bogon 5.10.35-00020-g8814ea753738 #1 SMP PREEMPT Tue May 31 12:48:15 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux

---

<div class="post-metadata">

### Author: ![jnettlet](https://dub1.discourse-cdn.com/flex005/user_avatar/community.solid-run.com/jnettlet/32/62_2.png) [@jnettlet](https://community.solid-run.com/u/jnettlet)
#### Post date: [June 7, 2022, 10:53am UTC](https://community.solid-run.com/t/hwclock-failed-with-hwclock-cannot-access-the-hardware-clock-via-any-known-method/345/2 "2022-06-07T10:53:16Z")

</div>

please post a link to the output of `dmesg`, thanks.

---

<div class="post-metadata">

### Author: ![Josua](https://avatars.discourse-cdn.com/v4/letter/j/e47774/32.png) [@Josua](https://community.solid-run.com/u/Josua)
#### Post date: [June 8, 2022, 7:50am UTC](https://community.solid-run.com/t/hwclock-failed-with-hwclock-cannot-access-the-hardware-clock-via-any-known-method/345/3 "2022-06-08T07:50:53Z")

</div>

@vader module loading is currently broken in our latest images by default, so the driver for the rtc is not actually loaded during boot.

Please run `depmod -a` as root, then reboot and retry.

We will try to fix this loading problem soon™.

---

<div class="post-metadata">

### Author: ![vader](https://avatars.discourse-cdn.com/v4/letter/v/9d8465/32.png) [@vader](https://community.solid-run.com/u/vader)
#### Post date: [June 8, 2022, 9:32am UTC](https://community.solid-run.com/t/hwclock-failed-with-hwclock-cannot-access-the-hardware-clock-via-any-known-method/345/4 "2022-06-08T09:32:22Z")

</div>

thx,it’s working

---

<div class="post-metadata">

### Author: ![Josua](https://avatars.discourse-cdn.com/v4/letter/j/e47774/32.png) [@Josua](https://community.solid-run.com/u/Josua)
#### Post date: [June 8, 2022, 12:39pm UTC](https://community.solid-run.com/t/hwclock-failed-with-hwclock-cannot-access-the-hardware-clock-via-any-known-method/345/5 "2022-06-08T12:39:45Z")

</div>

We have pushed an update to lx2160a\_build that should fix the module loading, so images dated June 8. 2022 and newer should work out of the box.
