Udev doesn't work when modules used

[ismail dönmez]

I saw this twice in a row :

- I had cdrom as a module and /dev/hdc & /dev/hdd devices are not created although kernel seems them fine
- /dev/rtc is not created although rtc module is loaded

Seen with kernels : 2.6.13-rc2/rc3 and Ubuntu installation is latest Breezy :

[~]> dpkg -l|grep udev
ii udev 0.060-1ubuntu2 /dev/ management daemon

[Matt Zimmerman (mdz)]

We need more information about the problem. Show us which modules are loaded,
which devices exist, and which devices are present on the system

[Scott James Remnant (Canonical) (canonical-scott)]

Could you also include the output of:

  udevinfo -p /class/misc/rtc -q all

[Martijn vdS (martijn)]

I have the same problem, except with /dev/input/mice:

$ udevinfo -p /class/input/mice -q all
device not found in database

A /etc/init.d/udev restart then solves my problems.

Contents of /dev/input:
 $ ls /dev/input/ -l
total 0
crw-rw---- 1 root root 13, 64 2005-08-21 10:39 event0
crw-rw---- 1 root root 13, 65 2005-08-21 10:39 event1
crw-rw---- 1 root root 13, 66 2005-08-21 10:39 event2
crw-rw---- 1 root root 13, 67 2005-08-21 10:39 event3
crw-rw---- 1 root root 13, 68 2005-08-21 10:39 event4
crw-rw---- 1 root root 13, 33 2005-08-21 10:39 mouse1
crw-rw---- 1 root root 13, 128 2005-08-21 10:39 ts0
crw-rw---- 1 root root 13, 129 2005-08-21 10:39 ts1

Contents of /sys/class/input:
$ ls -l /sys/class/input/
total 0
drwxr-xr-x 2 root root 0 2005-08-21 10:39 event0
drwxr-xr-x 2 root root 0 2005-08-21 10:39 event1
drwxr-xr-x 2 root root 0 2005-08-21 10:39 event2
drwxr-xr-x 2 root root 0 2005-08-21 10:39 event3
drwxr-xr-x 2 root root 0 2005-08-21 10:39 event4
drwxr-xr-x 2 root root 0 2005-08-21 10:39 mice
drwxr-xr-x 2 root root 0 2005-08-21 10:39 mouse0
drwxr-xr-x 2 root root 0 2005-08-21 10:39 mouse1
drwxr-xr-x 2 root root 0 2005-08-21 10:39 ts0
drwxr-xr-x 2 root root 0 2005-08-21 10:39 ts1

The relevant modules _are_ loaded (the /sys path exists, and dmesg contains a
message about it)

[Martijn vdS (martijn)]

Somehow, this was fixed (it might be a one-time event) by setting loglevel to
"info" in /etc/udev/udev.conf

[Scott James Remnant (Canonical) (canonical-scott)]

This bug has been marked as a duplicate of bug 19171.