How to create i2c device-files
![](https://seccdn.libravatar.org/avatar/7527ff019b7a5078cb8647683a49d303.jpg?s=120&d=mm&r=g)
Hi, I'm trying to setup my sensors. My first sensors-detect went fine (some weeks ago), but I had problems (don't remember which). Now that I have time again I wanted to run sensors-detect again but it complains : No i2c device-files found. Use prog/mkdev/mkdev.sh to create them. When I did ls -l /dev/i2c* there appeared a number of device-files, but it seems i2c-0 and i2c-1 are missing. How can I create these ? I found out that the mkdev-command is mknod in SuSE9.2, but I need to know the parameters of the command. Any place where I could lookup these ? TIA. P.S. I presume a cp of a device file is not good enough ? -- Met vriendelijke groeten, Koenraad Lelong R&D Manager ACE electronics n.v.
![](https://seccdn.libravatar.org/avatar/7527ff019b7a5078cb8647683a49d303.jpg?s=120&d=mm&r=g)
Koenraad Lelong schreef:
Hi, I'm trying to setup my sensors. My first sensors-detect went fine (some weeks ago), but I had problems (don't remember which). Now that I have time again I wanted to run sensors-detect again but it complains : No i2c device-files found. Use prog/mkdev/mkdev.sh to create them. When I did ls -l /dev/i2c* there appeared a number of device-files, but it seems i2c-0 and i2c-1 are missing. How can I create these ? I found out that the mkdev-command is mknod in SuSE9.2, but I need to know the parameters of the command. Any place where I could lookup these ? TIA. P.S. I presume a cp of a device file is not good enough ? Google is my friend. From what I read I concluded that the command could be : mknod /dev/i2c-0 c 89 0 Anyone can confirm this ? I dare not to try this on my own.
-- Met vriendelijke groeten, Koenraad Lelong R&D Manager ACE electronics n.v.
![](https://seccdn.libravatar.org/avatar/7527ff019b7a5078cb8647683a49d303.jpg?s=120&d=mm&r=g)
Koenraad Lelong schreef:
Koenraad Lelong schreef:
Hi, I'm trying to setup my sensors. My first sensors-detect went fine (some weeks ago), but I had problems (don't remember which). Now that I have time again I wanted to run sensors-detect again but it complains : No i2c device-files found. Use prog/mkdev/mkdev.sh to create them. When I did ls -l /dev/i2c* there appeared a number of device-files, but it seems i2c-0 and i2c-1 are missing. How can I create these ? I found out that the mkdev-command is mknod in SuSE9.2, but I need to know the parameters of the command. Any place where I could lookup these ? TIA. P.S. I presume a cp of a device file is not good enough ?
Google is my friend. From what I read I concluded that the command could be : mknod /dev/i2c-0 c 89 0 Anyone can confirm this ? I dare not to try this on my own.
Since no-one replied I tried this and it seems to work. -- Met vriendelijke groeten, Koenraad Lelong R&D Manager ACE electronics n.v.
![](https://seccdn.libravatar.org/avatar/6d198f8c8f1c94ccef873cebcf4f5dfa.jpg?s=120&d=mm&r=g)
Koenraad Lelong wrote:
Koenraad Lelong schreef:
Koenraad Lelong schreef:
Hi, I'm trying to setup my sensors. My first sensors-detect went fine (some weeks ago), but I had problems (don't remember which). Now that I have time again I wanted to run sensors-detect again but it complains : No i2c device-files found. Use prog/mkdev/mkdev.sh to create them. When I did ls -l /dev/i2c* there appeared a number of device-files, but it seems i2c-0 and i2c-1 are missing. How can I create these ? I found out that the mkdev-command is mknod in SuSE9.2, but I need to know the parameters of the command. Any place where I could lookup these ? TIA. P.S. I presume a cp of a device file is not good enough ?
Google is my friend. From what I read I concluded that the command could be : mknod /dev/i2c-0 c 89 0 Anyone can confirm this ? I dare not to try this on my own.
Since no-one replied I tried this and it seems to work.
I obviously missed the original post, that's an easy one. mknod has been there dating back to old Unix. They should have been created at install time on SuSE, on Mandriva they are created bu udev at boot time. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks
participants (2)
-
Koenraad Lelong
-
Sid Boyce