I2c r/w permission

Support
, ,
1

What is the correct solution to this problem?

journalctl -p 4 -b -1 --no-hostname --no-pager

org_kde_powerdevil[1109]: [  1265] Device /dev/i2c-3 lacks R/W permissions
org_kde_powerdevil[1109]: [  1265] Device /dev/i2c-4 lacks R/W permissions
org_kde_powerdevil[1109]: [  1265] Device /dev/i2c-5 lacks R/W permissions
org_kde_powerdevil[1109]: [  1265] Device /dev/i2c-6 lacks R/W permissions
org_kde_powerdevil[1109]: [  1265] Device /dev/i2c-7 lacks R/W permissions
org_kde_powerdevil[1109]: [  1265] Device /dev/i2c-8 lacks R/W permissions
org_kde_powerdevil[1109]: [  1265] Device /dev/i2c-9 lacks R/W permissions

ls -ls /dev/i2c*                                                                                                                                                           ✔ 
0 crw-rw----  1 root i2c 89,  0 29. Nov 01:50 /dev/i2c-0
0 crw-rw----  1 root i2c 89,  1 29. Nov 01:50 /dev/i2c-1
0 crw-rw----  1 root i2c 89, 10 29. Nov 01:50 /dev/i2c-10
0 crw-rw----  1 root i2c 89,  2 29. Nov 01:50 /dev/i2c-2
0 crw-rw----+ 1 root i2c 89,  3 29. Nov 01:50 /dev/i2c-3
0 crw-rw----+ 1 root i2c 89,  4 29. Nov 01:50 /dev/i2c-4
0 crw-rw----+ 1 root i2c 89,  5 29. Nov 01:50 /dev/i2c-5
0 crw-rw----+ 1 root i2c 89,  6 29. Nov 01:50 /dev/i2c-6
0 crw-rw----+ 1 root i2c 89,  7 29. Nov 01:50 /dev/i2c-7
0 crw-rw----+ 1 root i2c 89,  8 29. Nov 01:50 /dev/i2c-8
0 crw-rw----+ 1 root i2c 89,  9 29. Nov 01:50 /dev/i2c-9
2

Hmm - these are some entries in the log.
You checked and they are, of course, correct - as far as permissions for everyone (others) go.
(there are rw permissions for user and group)

On my system (Mint) , there are only rw permissions for user - none for group and others

But:
What is the actual problem?

3

I don’t have any problems, I mean the PC.
I looked at the entries that are added during shutdown. There are quite a few.

First, I found this, but I don’t know how up-to-date or relevant it is for us

4

don’t worry, the i2c-bus is a bus for controlling internal silicon like the usb-controller etc. . you need root-privileges to access them and this is to prevent that “ordinary” processes can manipulate them by malware.

2 Likes
5

But you asked for a solution to a problem. :man_shrugging:

The permissions might actually be “too open” rather than too restrictive
(per your first link).

6

Leave it as is. Writing something wrong there can burn something, that is why writing is disabled by default. Some softwares for clocking or temperature monitoring explicitly warn for the risk and by default ignore them.

7

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.