2.6.26.8-rt12 - No hwclock - works under 2.6.24-rt1

2.6.26.8-rt12 - No hwclock - works under 2.6.24-rt1

[Mark Knecht]

I'm just getting around to trying 2.6.26.8-rt12 from the Gentoo
pro-audio overlay. I built the kernel using an older .config and make
oldconfig so maybe it didn't catch something correctly. Anyway, at
boot the system is complaining about all file times are in the future
and later on I see a message that it couldn't set the clock and I'll
have to do that by hand. The machine then finishes booting and I get
as far as X. Haven't tested anything more than that.

the issue seems to be that the system cannot find my hardware clock,
and frankly neither can I in make menuconfig so maybe someone can tell
me where is the hardware clock? I'm hoping it's just misconfiguration
and not something more devious.

Motherboard is an Asus A8N-E which is nVidia based. More info provided
if need be.

Thanks,
Mark

[NEW KERNEL]

lightning ~ # uname -a
Linux lightning 2.6.26.8-rt12 #1 PREEMPT RT Fri Jan 30 12:39:38 PST
2009 x86_64 AMD Athlon(tm) 64 Processor 3000+ AuthenticAMD GNU/Linux
lightning ~ # hwclock -r
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access method.
lightning ~ #


[OLD KERNEL]

lightning ~ # uname -a
Linux lightning 2.6.24-rt1 #1 PREEMPT RT Tue Feb 5 07:03:44 PST 2008
x86_64 AMD Athlon(tm) 64 Processor 3000+ AuthenticAMD GNU/Linux
lightning ~ # hwclock -r
Fri 30 Jan 2009 03:49:39 PM PST  -0.555966 seconds
lightning ~ #

Re: 2.6.26.8-rt12 - No hwclock - works under 2.6.24-rt1

[Norval Watson]

2.6.26.8-rt14 has just been released that includes important changes...
Steven Rostedt posted the news here on Thursday.


      Make Yahoo!7 your homepage and win a trip to the Quiksilver Pro. Find out more

Re: 2.6.26.8-rt12 - No hwclock - works under 2.6.24-rt1

[Clark Williams]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, 30 Jan 2009 16:00:27 -0800
Mark Knecht <markknecht@gmail.com> wrote:

> I'm just getting around to trying 2.6.26.8-rt12 from the Gentoo
> pro-audio overlay. I built the kernel using an older .config and make
> oldconfig so maybe it didn't catch something correctly. Anyway, at
> boot the system is complaining about all file times are in the future
> and later on I see a message that it couldn't set the clock and I'll
> have to do that by hand. The machine then finishes booting and I get
> as far as X. Haven't tested anything more than that.
> 
> the issue seems to be that the system cannot find my hardware clock,
> and frankly neither can I in make menuconfig so maybe someone can tell
> me where is the hardware clock? I'm hoping it's just misconfiguration
> and not something more devious.
> 
> Motherboard is an Asus A8N-E which is nVidia based. More info provided
> if need be.
> 
> Thanks,
> Mark
> 
> [NEW KERNEL]
> 
> lightning ~ # uname -a
> Linux lightning 2.6.26.8-rt12 #1 PREEMPT RT Fri Jan 30 12:39:38 PST
> 2009 x86_64 AMD Athlon(tm) 64 Processor 3000+ AuthenticAMD GNU/Linux
> lightning ~ # hwclock -r
> Cannot access the Hardware Clock via any known method.
> Use the --debug option to see the details of our search for an access method.
> lightning ~ #

As I recall this was a change in the rtc driver where it uses classes
(and you can have multiple rtc device instances).  The result is that
the rtc driver no longer creates /dev/rtc but rather /dev/rtc0. 

You might try just creating a symlink in /dev from rtc -> rtc0 and see
if that makes your startup logic happy. I don't think that using udev
to create your symlink on the fly is an option, because most distros
access the RTC before udev gets run.

You might also make sure that CONFIG_RTC_DRV_CMOS=y, so that you don't
have to load a module from an initrd to get to the cmos clock.

Clark

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (GNU/Linux)

iEYEARECAAYFAkmEZakACgkQHyuj/+TTEp2DRACfetL2DJO0oRz9ZTb8hbIbXl1t
crEAoLNbX6hzFcbsozOObAxTkcdEAdqi
=0X1+
-----END PGP SIGNATURE-----

Re: 2.6.26.8-rt12 - No hwclock - works under 2.6.24-rt1

[Mark Knecht]

On Sat, Jan 31, 2009 at 6:52 AM, Clark Williams <williams@redhat.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Fri, 30 Jan 2009 16:00:27 -0800
> Mark Knecht <markknecht@gmail.com> wrote:
>
>> I'm just getting around to trying 2.6.26.8-rt12 from the Gentoo
>> pro-audio overlay. I built the kernel using an older .config and make
>> oldconfig so maybe it didn't catch something correctly. Anyway, at
>> boot the system is complaining about all file times are in the future
>> and later on I see a message that it couldn't set the clock and I'll
>> have to do that by hand. The machine then finishes booting and I get
>> as far as X. Haven't tested anything more than that.
>>
>> the issue seems to be that the system cannot find my hardware clock,
>> and frankly neither can I in make menuconfig so maybe someone can tell
>> me where is the hardware clock? I'm hoping it's just misconfiguration
>> and not something more devious.
>>
>> Motherboard is an Asus A8N-E which is nVidia based. More info provided
>> if need be.
>>
>> Thanks,
>> Mark
>>
>> [NEW KERNEL]
>>
>> lightning ~ # uname -a
>> Linux lightning 2.6.26.8-rt12 #1 PREEMPT RT Fri Jan 30 12:39:38 PST
>> 2009 x86_64 AMD Athlon(tm) 64 Processor 3000+ AuthenticAMD GNU/Linux
>> lightning ~ # hwclock -r
>> Cannot access the Hardware Clock via any known method.
>> Use the --debug option to see the details of our search for an access method.
>> lightning ~ #
>
> As I recall this was a change in the rtc driver where it uses classes
> (and you can have multiple rtc device instances).  The result is that
> the rtc driver no longer creates /dev/rtc but rather /dev/rtc0.
>
> You might try just creating a symlink in /dev from rtc -> rtc0 and see
> if that makes your startup logic happy. I don't think that using udev
> to create your symlink on the fly is an option, because most distros
> access the RTC before udev gets run.
>
> You might also make sure that CONFIG_RTC_DRV_CMOS=y, so that you don't
> have to load a module from an initrd to get to the cmos clock.
>
> Clark

Norval,
   I'll see about using a newer one soon. Thanks!

Clark,
   CONFIG_RTC_DRV_CMOS=y is set. However all of the specific chip
versions immediately below it are not set so without at least one of
those is the CONFIG_RTC_DRV_CMOS doing anything?

   If by change I need to set at least one of those chip options how
do I determine what's on this motherboard?

   Scanning around this area I also notice that I've going none of the
I2C RTC drivers selected either.

   I haven't had time to check yet but the 2.6.27-gentoo-r8 kernel
didn't have this problem. I'll compare .config files between the two
and see what differences I can find.

Thanks,
Mark

Re: 2.6.26.8-rt12 - No hwclock - works under 2.6.24-rt1

[Clark Williams]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sat, 31 Jan 2009 09:58:28 -0800
Mark Knecht <markknecht@gmail.com> wrote:
> 
> Clark,
>    CONFIG_RTC_DRV_CMOS=y is set. However all of the specific chip
> versions immediately below it are not set so without at least one of
> those is the CONFIG_RTC_DRV_CMOS doing anything?
> 
>    If by change I need to set at least one of those chip options how
> do I determine what's on this motherboard?
> 
>    Scanning around this area I also notice that I've going none of the
> I2C RTC drivers selected either.
> 
>    I haven't had time to check yet but the 2.6.27-gentoo-r8 kernel
> didn't have this problem. I'll compare .config files between the two
> and see what differences I can find.
> 
> Thanks,
> Mark

Mark,

I don't have any of the platform drivers set for my laptop (Lenovo T60)
other than the CMOS driver.  None of the I2C or SPI drivers set. I
still think you need to look at what device the startup scripts are
looking for (probably /dev/rtc).

Here's a snippet of my config:

CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
CONFIG_RTC_DEBUG=y

#
# 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
#
# CONFIG_RTC_DRV_DS1307 is not set
# CONFIG_RTC_DRV_DS1374 is not set
# CONFIG_RTC_DRV_DS1672 is not set
# CONFIG_RTC_DRV_MAX6900 is not set
# CONFIG_RTC_DRV_RS5C372 is not set
# CONFIG_RTC_DRV_ISL1208 is not set
# CONFIG_RTC_DRV_X1205 is not set
# CONFIG_RTC_DRV_PCF8563 is not set
# CONFIG_RTC_DRV_PCF8583 is not set
# CONFIG_RTC_DRV_M41T80 is not set
# CONFIG_RTC_DRV_S35390A is not set
# CONFIG_RTC_DRV_FM3130 is not set

#
# SPI RTC drivers
#
#
# Platform RTC drivers
#
CONFIG_RTC_DRV_CMOS=y
# CONFIG_RTC_DRV_DS1511 is not set
# CONFIG_RTC_DRV_DS1553 is not set
# CONFIG_RTC_DRV_DS1742 is not set
# CONFIG_RTC_DRV_STK17TA8 is not set
# CONFIG_RTC_DRV_M48T86 is not set
# CONFIG_RTC_DRV_M48T59 is not set
# CONFIG_RTC_DRV_V3020 is not set


Clark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (GNU/Linux)

iEYEARECAAYFAkmEpI4ACgkQHyuj/+TTEp0tBQCfW3H9E1Wq22d0K9kIoitVcO24
/GcAoNeqZaMmv0V9eB0stusKn8g3Wo1j
=Mg8X
-----END PGP SIGNATURE-----

Re: 2.6.26.8-rt12 - No hwclock - works under 2.6.24-rt1

[Mark Knecht]

On Sat, Jan 31, 2009 at 11:20 AM, Clark Williams <williams@redhat.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Sat, 31 Jan 2009 09:58:28 -0800
> Mark Knecht <markknecht@gmail.com> wrote:
>>
>> Clark,
>>    CONFIG_RTC_DRV_CMOS=y is set. However all of the specific chip
>> versions immediately below it are not set so without at least one of
>> those is the CONFIG_RTC_DRV_CMOS doing anything?
>>
>>    If by change I need to set at least one of those chip options how
>> do I determine what's on this motherboard?
>>
>>    Scanning around this area I also notice that I've going none of the
>> I2C RTC drivers selected either.
>>
>>    I haven't had time to check yet but the 2.6.27-gentoo-r8 kernel
>> didn't have this problem. I'll compare .config files between the two
>> and see what differences I can find.
>>
>> Thanks,
>> Mark
>
> Mark,
>
> I don't have any of the platform drivers set for my laptop (Lenovo T60)
> other than the CMOS driver.  None of the I2C or SPI drivers set. I
> still think you need to look at what device the startup scripts are
> looking for (probably /dev/rtc).
>
> Here's a snippet of my config:
>
> CONFIG_RTC_LIB=y
> CONFIG_RTC_CLASS=y
> CONFIG_RTC_HCTOSYS=y
> CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
> CONFIG_RTC_DEBUG=y
>
> #
> # 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
> #
> # CONFIG_RTC_DRV_DS1307 is not set
> # CONFIG_RTC_DRV_DS1374 is not set
> # CONFIG_RTC_DRV_DS1672 is not set
> # CONFIG_RTC_DRV_MAX6900 is not set
> # CONFIG_RTC_DRV_RS5C372 is not set
> # CONFIG_RTC_DRV_ISL1208 is not set
> # CONFIG_RTC_DRV_X1205 is not set
> # CONFIG_RTC_DRV_PCF8563 is not set
> # CONFIG_RTC_DRV_PCF8583 is not set
> # CONFIG_RTC_DRV_M41T80 is not set
> # CONFIG_RTC_DRV_S35390A is not set
> # CONFIG_RTC_DRV_FM3130 is not set
>
> #
> # SPI RTC drivers
> #
> #
> # Platform RTC drivers
> #
> CONFIG_RTC_DRV_CMOS=y
> # CONFIG_RTC_DRV_DS1511 is not set
> # CONFIG_RTC_DRV_DS1553 is not set
> # CONFIG_RTC_DRV_DS1742 is not set
> # CONFIG_RTC_DRV_STK17TA8 is not set
> # CONFIG_RTC_DRV_M48T86 is not set
> # CONFIG_RTC_DRV_M48T59 is not set
> # CONFIG_RTC_DRV_V3020 is not set
>
>
> Clark

Clark,
   Thanks. This is helpful. Turns out I have a number of
inconsistencies in these 3 kernels. Neither of my old RT kernels have
CONFIG_RTC_DRV_CMOS set. However 2.6.24-rt1 worked and 2.6.26.8-rt12
doesn't. Now, the newer Gentoo kernel, 2.6.27-gentoo-r8 did have that
set and that kernel works, so for now I'm suspecting that if I enable
that maybe 2.6.26.8-rt12 will start working. We'll see. I cannot do
anything until some other work on the machine finishes. In the
meantime I'm looking around for how Gentoo sets the /dev/rtc link.

I've snipped out anything not set for readability.

[[ Real-Time - WORKS ]]

lightning src # cat linux-2.6.24-rt1/.config | grep CONFIG_RTC
CONFIG_RTC=y
CONFIG_RTC_LIB=m
CONFIG_RTC_CLASS=m
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y



[[ Real-Time - FAILS ]]

lightning src # cat linux-2.6.26.8-rt12/.config | grep CONFIG_RTC
CONFIG_RTC_LIB=m
CONFIG_RTC_CLASS=m
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y



[[ Gentoo non-RT - WORKS]]

lightning src # cat linux-2.6.27-gentoo-r8/.config | grep CONFIG_RTC
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
CONFIG_RTC_DRV_CMOS=y

thanks much!

- Mark

Re: 2.6.26.8-rt12 - No hwclock - works under 2.6.24-rt1

[Mark Knecht]

Clark,
   To finish up, thanks for your help. It's booting fine now with the
following settings.

Cheers,
Mark

On Sat, Jan 31, 2009 at 2:36 PM, Mark Knecht <markknecht@gmail.com> wrote:
<SNIP>

lightning ~ # uname -a
Linux lightning 2.6.26.8-rt12 #2 PREEMPT RT Sun Feb 1 08:06:03 PST
2009 x86_64 AMD Athlon(tm) 64 Processor 3000+ AuthenticAMD GNU/Linux
lightning ~ # cat /usr/src/linux-2.6.26.8-rt12/.config | grep CONFIG_RTC
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
# CONFIG_RTC_DEBUG is not set
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
# CONFIG_RTC_DRV_DS1307 is not set
# CONFIG_RTC_DRV_DS1374 is not set
# CONFIG_RTC_DRV_DS1672 is not set
# CONFIG_RTC_DRV_MAX6900 is not set
# CONFIG_RTC_DRV_RS5C372 is not set
# CONFIG_RTC_DRV_ISL1208 is not set
# CONFIG_RTC_DRV_X1205 is not set
# CONFIG_RTC_DRV_PCF8563 is not set
# CONFIG_RTC_DRV_PCF8583 is not set
# CONFIG_RTC_DRV_M41T80 is not set
# CONFIG_RTC_DRV_S35390A is not set
# CONFIG_RTC_DRV_FM3130 is not set
CONFIG_RTC_DRV_CMOS=y
# CONFIG_RTC_DRV_DS1511 is not set
# CONFIG_RTC_DRV_DS1553 is not set
# CONFIG_RTC_DRV_DS1742 is not set
# CONFIG_RTC_DRV_STK17TA8 is not set
# CONFIG_RTC_DRV_M48T86 is not set
# CONFIG_RTC_DRV_M48T59 is not set
# CONFIG_RTC_DRV_V3020 is not set
lightning ~ #