# No keyboard input with LS1028 board and latest image?

**URL:** <https://community.mnt.re/t/no-keyboard-input-with-ls1028-board-and-latest-image/1994>\
**Category:** MNT Reform\
**Created:** [April 7, 2024, 4:02pm UTC](https://community.mnt.re/t/no-keyboard-input-with-ls1028-board-and-latest-image/1994 "2024-04-07T16:02:24Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![minute](https://community.mnt.re/user_avatar/community.mnt.re/minute/32/3_2.png) [@minute](https://community.mnt.re/u/minute)\
**Post date:** [June 3, 2024, 4:44pm UTC](https://community.mnt.re/t/no-keyboard-input-with-ls1028-board-and-latest-image/1994/13 "2024-06-03T16:44:33Z")

</div>

You won’t believe it, but it seems like a timing issue that was revealed by us setting `loglevel=3` in the latest images.

If you set the `loglevel` back to 7, it works again (most of the time at least, how it used to be). My hunch is that the log prints introduce tiny delays that are required for the functionality of `dwc3` on LS1028A.

If you have serial connected you can test this even dynamically by doing something like this:

```auto
rmmod dwc3
dmesg -n 7
modprobe dwc3

```

Then USB should work. If you set `dmesg -n 3`, it should again cease to work.

This is so far the most ridiculous issue I have encountered. To root cause this we would need to find all the log print sites and sprinkle with delays (or it could also be cache flush related).

---

_[View the full topic](https://community.mnt.re/t/no-keyboard-input-with-ls1028-board-and-latest-image/1994)._
