> >> Interesting. Here is the only (non-comment) difference: > >> > >> < CONFIG_RTC_HCTOSYS_DEVICE="rtc0" > >>> CONFIG_RTC_SYSTOHC_DEVICE="rtc0" > >> > > Two different options: > > > > http://cateee.net/lkddb/web-lkddb/RTC_HCTOSYS_DEVICE.html > > http://cateee.net/lkddb/web-lkddb/RTC_SYSTOHC_DEVICE.html > > > > Maybe that will lead you somewhere. > > Yes, I believe it will. I think I need to statically link rtc0: > > "The driver for this RTC device must be loaded before late_initcall > functions run, so it must usually be statically linked." > > What's the best way to do this in LFS?
Maybe not. I listed the host /dev/rtc0 and noted major and minor device numbers and mode, and used mknod to create a static node as was done when creating the null and console devices: mknod -m 644 $LFS/dev/rtc0 c 254 0 but I still get this message when booting: rtc_cmos 00:03: hctosys: unable to read the hardware clock This is a show stopper for me. I can't go to the latest LFS.
-- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
