Skip to contentSkip to conversation

Device node '/dev/rtc' already exists, link to '/dev/rtc0' ,wil not

DISCUSSION Harald Hoyer 3 participants 3 messages Sep 18, 2007

lore
Share & tools
lore

Harald Hoyer

author
#0 lore raw

Looks like 50-udev-default.rules:

KERNEL=="rtc0", SYMLINK+="rtc"

has to be modified...

$ udevinfo -a -n /dev/rtc
  looking at device '/class/misc/rtc':
    KERNEL=="rtc"
    SUBSYSTEM=="misc"
    DRIVER==""
    ATTR{dev}=="10:135"
$ udevinfo -a -n /dev/rtc0

looking at device '/class/rtc/rtc0':

    KERNEL=="rtc0"
    SUBSYSTEM=="rtc"
    DRIVER==""
    ATTR{wakealarm}==""
    ATTR{since_epoch}=="1190109813"
    ATTR{time}=="10:03:33"
    ATTR{date}=="2007-09-18"
    ATTR{name}=="rtc_cmos"
    ATTR{dev}=="254:0"

looking at parent device '/devices/pnp0/00:05':

    KERNELS=="00:05"
    SUBSYSTEMS=="pnp"
    DRIVERS=="rtc_cmos"
    ATTRS{id}=="PNP0b00"
    ATTRS{options}==""

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

#1 lore raw

Re: Device node '/dev/rtc' already exists, link to '/dev/rtc0' ,wil

Quoted 26 lines · Harald Hoyer

Looks like 50-udev-default.rules:

KERNEL="rtc0", SYMLINK+="rtc"

has to be modified...

$ udevinfo -a -n /dev/rtc
  looking at device '/class/misc/rtc':
    KERNEL="rtc"
    SUBSYSTEM="misc"
    DRIVER=""
    ATTR{dev}="10:135"
$ udevinfo -a -n /dev/rtc0

looking at device '/class/rtc/rtc0':

    KERNEL="rtc0"
    SUBSYSTEM="rtc"
    DRIVER=""
    ATTR{wakealarm}=""
    ATTR{since_epoch}="1190109813"
    ATTR{time}="10:03:33"
    ATTR{date}="2007-09-18"
    ATTR{name}="rtc_cmos"
    ATTR{dev}="254:0"
Quoted 6 lines

looking at parent device '/devices/pnp0/00:05':

    KERNELS="00:05"
    SUBSYSTEMS="pnp"
    DRIVERS="rtc_cmos"
    ATTRS{id}="PNP0b00"
    ATTRS{options}=""

It looks like your kernel configuration is not valid. You have compiled both the old-style "rtc" (or "genrtc"?) driver and the new "rtc_cmos" driver. Please remove one of them, and the problem will go away.

(please correct me if I am wrong - I have never played with the new RTC drivers).

Signature · 10 lines
Alexander E. Patrakov

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
#2 lore raw

Re: Device node '/dev/rtc' already exists, link to '/dev/rtc0' ,

In reply to Harald Hoyer
Quoted 34 lines · Alexander E. Patrakov
Quoted 26 lines · Harald Hoyer

Looks like 50-udev-default.rules:

KERNEL="rtc0", SYMLINK+="rtc"

has to be modified...

$ udevinfo -a -n /dev/rtc
  looking at device '/class/misc/rtc':
    KERNEL="rtc"
    SUBSYSTEM="misc"
    DRIVER=""
    ATTR{dev}="10:135"
$ udevinfo -a -n /dev/rtc0

looking at device '/class/rtc/rtc0':

    KERNEL="rtc0"
    SUBSYSTEM="rtc"
    DRIVER=""
    ATTR{wakealarm}=""
    ATTR{since_epoch}="1190109813"
    ATTR{time}="10:03:33"
    ATTR{date}="2007-09-18"
    ATTR{name}="rtc_cmos"
    ATTR{dev}="254:0"
Quoted 6 lines

looking at parent device '/devices/pnp0/00:05':

    KERNELS="00:05"
    SUBSYSTEMS="pnp"
    DRIVERS="rtc_cmos"
    ATTRS{id}="PNP0b00"
    ATTRS{options}=""
Quoted 6 lines

It looks like your kernel configuration is not valid. You have compiled both the old-style "rtc" (or "genrtc"?) driver and the new "rtc_cmos" driver. Please remove one of them, and the problem will go away.

(please correct me if I am wrong - I have never played with the new RTC drivers).

Yes, the old "rtc" module should not be provided if the new ones are enabled. The info message of udev is the expected behavior, as no symlink should overwrite a device node of a different device.

Kay

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel