# Log full with "rk3x-i2c timeout" **URL:** \ **Category:** Troubleshooting\ **Created:** [14 January 2024 13:16 UTC](https://dietpi.com/forum/t/log-full-with-rk3x-i2c-timeout/18959 "2024-01-14T13:16:24Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![Auxili](https://dietpi.com/forum/user_avatar/dietpi.com/auxili/32/5657_2.png) [@Auxili](https://dietpi.com/forum/u/Auxili)\ **Post date:** [14 January 2024 13:16 UTC](https://dietpi.com/forum/t/log-full-with-rk3x-i2c-timeout/18959/1 "2024-01-14T13:16:24Z")
Hello everyone, this is my first post in this forum and I need your help. I installed DietPi on my Nanopi M4 and it works fine but in the log I discovered that every second the following line > kernel: rk3x-i2c ff3d0000.i2c: timeout, ipd: 0x80, state: 2 I looked for a similar problem here in the forum but didn’t really find anything. I have to mention that I use a SATA HAT, maybe that’s why this problem occurs, I have no idea why the error appears every second. The system is running Openmediavault 7 but this error occurred before I had installed omv. The power supply I use has enough power, the system ran on Armbian for a few years until I switched to DietPi. More information: > cat /boot/dietpi/.version > G\_DIETPI\_VERSION\_CORE=8 > G\_DIETPI\_VERSION\_SUB=25 > G\_DIETPI\_VERSION\_RC=1 > G\_GITBRANCH=‘master’ > G\_GITOWNER=‘MichaIng’ > echo $G\_DISTRO\_NAME $G\_RASPBIAN > bookworm > uname -a > Linux omv 6.1.63-current-rockchip64 I would be very happy if someone has a solution for me ---
**Author:** ![Auxili](https://dietpi.com/forum/user_avatar/dietpi.com/auxili/32/5657_2.png) [@Auxili](https://dietpi.com/forum/u/Auxili)\ **Post date:** [14 January 2024 20:56 UTC](https://dietpi.com/forum/t/log-full-with-rk3x-i2c-timeout/18959/2 "2024-01-14T20:56:57Z")
Hello again, I found the solution to the problem here [https://dietpi.com/forum/t/dietpi-i2c-problem/66](https://dietpi.com/forum/t/dietpi-i2c-problem/66) I don’t need i2c, so I disabled it with raspi-config. To install raspi-config on the DietPi use the script here: [https://github.com/EmilGus/install\_raspi-config](https://github.com/EmilGus/install_raspi-config) Thanx @all ---
**Author:** ![Jappe](https://dietpi.com/forum/user_avatar/dietpi.com/jappe/32/1788_2.png) [@Jappe](https://dietpi.com/forum/u/Jappe)\ **Post date:** [14 January 2024 21:22 UTC](https://dietpi.com/forum/t/log-full-with-rk3x-i2c-timeout/18959/3 "2024-01-14T21:22:16Z")
You can enable and disable `i2c` also via `dietpi-config` 🙂 ---
**Author:** ![Auxili](https://dietpi.com/forum/user_avatar/dietpi.com/auxili/32/5657_2.png) [@Auxili](https://dietpi.com/forum/u/Auxili)\ **Post date:** [14 January 2024 21:43 UTC](https://dietpi.com/forum/t/log-full-with-rk3x-i2c-timeout/18959/4 "2024-01-14T21:43:59Z")
Thank you for the answer @Jappe Unfortunately I didn’t find such an option in dietpi-config. Can you please be more specific? ---
**Author:** ![Jappe](https://dietpi.com/forum/user_avatar/dietpi.com/jappe/32/1788_2.png) [@Jappe](https://dietpi.com/forum/u/Jappe)\ **Post date:** [15 January 2024 07:53 UTC](https://dietpi.com/forum/t/log-full-with-rk3x-i2c-timeout/18959/5 "2024-01-15T07:53:19Z")
I have to correct myself, under `advanced options` you can set UART, I2C, SPI etc pp. not for all devices, but for example RPi, OPi Zero 3 and some more. But it’s interesting that `raspi-config`, which is also RPi only, works for the NanoPi. When I compare [raspi-config](https://github.com/RPi-Distro/raspi-config/blob/c0e5bdb94417d7bfadb9905d07b88c9fadbf5950/raspi-config#L1048) to [dietpi-config](https://github.com/MichaIng/DietPi/blob/7f8fe89f4e21921cc043f94cde3107e4ec682e2a/dietpi/dietpi-config#L1100C17-L1100C17) then the two scripts do basically the same for I2C, they add `dtparam=i2c_arm=on` to `/boot/firmware/config.txt` but `raspi-config` does also a `modprobe i2c-dev`. If your are motivated you can implement this into the DietPi script 😃 ---
**Author:** ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)\ **Post date:** [15 January 2024 11:10 UTC](https://dietpi.com/forum/t/log-full-with-rk3x-i2c-timeout/18959/6 "2024-01-15T11:10:32Z")
> [@Jappe](#): > > If your are motivated you can implement this into the DietPi script 😃 Maybe something for @MichaIng to have a look if we can enable I2C management on this board as well. ---
**Author:** ![Auxili](https://dietpi.com/forum/user_avatar/dietpi.com/auxili/32/5657_2.png) [@Auxili](https://dietpi.com/forum/u/Auxili)\ **Post date:** [15 January 2024 18:22 UTC](https://dietpi.com/forum/t/log-full-with-rk3x-i2c-timeout/18959/7 "2024-01-15T18:22:18Z")
But it is clear that the image for NanoPi M4 is missing this function in the dietpi-config 😉 ---
**Author:** ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)\ **Post date:** [15 January 2024 18:25 UTC](https://dietpi.com/forum/t/log-full-with-rk3x-i2c-timeout/18959/8 "2024-01-15T18:25:44Z")
That’s why I gave a ping to our developer 😉 ---
**Author:** ![Auxili](https://dietpi.com/forum/user_avatar/dietpi.com/auxili/32/5657_2.png) [@Auxili](https://dietpi.com/forum/u/Auxili)\ **Post date:** [15 January 2024 18:33 UTC](https://dietpi.com/forum/t/log-full-with-rk3x-i2c-timeout/18959/9 "2024-01-15T18:33:09Z")
Perfect, thank you @Joulinar 🤝 ---
**Author:** ![MichaIng](https://dietpi.com/forum/user_avatar/dietpi.com/michaing/32/7_2.png) [@MichaIng](https://dietpi.com/forum/u/MichaIng)\ **Post date:** [25 January 2024 19:03 UTC](https://dietpi.com/forum/t/log-full-with-rk3x-i2c-timeout/18959/10 "2024-01-25T19:03:10Z")
Sorry for the late reply. `raspi-config` did even install and start on a NanoPi M4? 🤔 The `/boot/config.txt` of course does not exist there, and the overlay it aims to use is RPi-only. So the problem is that the I2C kernel module is triggered, even that ni I2C device is attacked? I guess the HAT is the reason for this. It should work to just blacklist the module, and this is probably what `raspi-config` did. Check `/etc/modprobe.d` for a related file. It would contain `blacklist i2c-dev`. Probably it is an alias, but more fitting would be `blacklist rk3x-i2c`. ---
**Author:** ![system](https://dietpi.com/forum/uploads/default/original/1X/7e1021de2213860bce185915ce2c1786e56490ec.png) [@system](https://dietpi.com/forum/u/system)\ **Post date:** [24 April 2024 19:03 UTC](https://dietpi.com/forum/t/log-full-with-rk3x-i2c-timeout/18959/11 "2024-04-24T19:03:56Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.