It appears that currently the rtc subsystem tries to set the clock before detecting devices and loading modules, which results in the error message "unable to open rtc device": [ 1.032601] drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 1.033133] Freeing unused kernel memory: 416k freed [ 1.063882] NET: Registered protocol family 1 [ 1.064444] udevd[484]: starting version 181 [ 1.094839] rtc_cmos 00:05: RTC can wake from S4 [ 1.095180] rtc_cmos 00:05: rtc core: registered rtc_cmos as rtc0 I suggest detecting devices earlier or setting the clock later, to prevent this.
That seems to be a distribution build error - you've got the hctosys driver compiled in and your rtc driver as a module so there is nothing the kernel can do about ordering here.
(In reply to comment #1) > That seems to be a distribution build error - you've got the hctosys driver > compiled in and your rtc driver as a module so there is nothing the kernel > can > do about ordering here. Can't you make the hctosys function also a module? Then udev could load it after loading the rtc driver. Or maybe you could run the code only after the specified rtc device was found?