Bryan Kadzban wrote:
>>> Do you have CONFIG_SYSFS_DEPRECATED turned on in the kernel .config
>>> file?
>
> Did you have that setting on? We might want to warn about that in the
> book in the kernel-config section, actually. Hmm.
>
>>> What does "/sbin/udevadm info -q path -n /dev/rtc" say? Where does
>>> the /sys/$(/sbin/udevadm info -q path -n /dev/rtc)/subsystem
>>> symlink point to?
>> udevadm returns '/devices/platform/rtc_cmos/rtc/rtc0'
>
> OK; here I get:
>
> /devices/pnp0/00:02/rtc/rtc0
On a 64-bit system, I get:
/devices/pnp0/00:05/rtc/rtc0
> which is close (after the PNPBIOS ID), but under PNPBIOS, not a platform
> driver. Not sure if that matters or not, though, because:
>
>> The symlink points to /sys/class/rtc.
> Yeah, same here. I *think* that means that SUBSYSTEM will be set to
> "rtc" at runtime, but if you're not getting that either, then maybe
> that's wrong.
Yes, I get the same.
> What about the standard:
>
> /sbin/udevadm --attribute-walk -n /dev/rtc
I get:
/sbin/udevadm: unrecognized option '--attribute-walk' :)
But for /sbin/udevadm info --attribute-walk -n /dev/rtc, I get
> for the SUBSYSTEM? (And what about parent devices?) I get:
>
> looking at device '/devices/pnp0/00:02/rtc/rtc0':
> KERNEL=="rtc0"
> SUBSYSTEM=="rtc"
> DRIVER==""
> ATTR{name}=="rtc_cmos"
> ATTR{date}=="2009-09-16"
> ATTR{time}=="03:32:10"
"03:56:50"
> ATTR{since_epoch}=="1253071930"
"1253073410"
> ATTR{max_user_freq}=="1024"
"64" !!!
> ATTR{wakealarm}==""
> looking at parent device '/devices/pnp0/00:02':
> KERNELS=="00:02"
> SUBSYSTEMS=="pnp"
> DRIVERS=="rtc_cmos"
> ATTRS{options}==""
> ATTRS{id}=="PNP0b00"
> ATTRS{nvram}==""
Basically the same.
> looking at parent device '/devices/pnp0':
> KERNELS=="pnp0"
> SUBSYSTEMS==""
> DRIVERS==""
The same.
> ...but I'm using the rtc_cmos (rtc-class) driver, not the older setup
> that creates its own misc device.
# CONFIG_SYSFS_DEPRECATED_V2 is not set
CONFIG_HPET_EMULATE_RTC=y
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
# CONFIG_RTC_HCTOSYS is not set
# CONFIG_RTC_DEBUG is not set
#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
# CONFIG_RTC_INTF_DEV_UIE_EMUL is not set
# CONFIG_RTC_DRV_TEST is not set
#
# I2C RTC drivers
None set
# Platform RTC drivers
#
CONFIG_RTC_DRV_CMOS=y
The rest are not set.
The udev rule is
SUBSYSTEM=="rtc", MODE="0644", ACTION=="add", RUN+="/etc/rc.d/init.d/setclock
start"
and setclock does not have a path to hwclock, but that shouldn't be an issue
because it just sets the time, not the permissions. If the udev rule fires,
you
should have:
$ ls -l /dev/rtc*
lrwxrwxrwx 1 root root 4 Sep 12 00:43 /dev/rtc -> rtc0
crw-r--r-- 1 root root 254, 0 Sep 12 00:43 /dev/rtc0
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
