* Re: /proc/acpi/alarm -- does it work or not? [not found] <59D45D057E9702469E5775CBB56411F1013CF084@pdsmsx406> @ 2006-01-09 15:44 ` Pavel Machek 2006-01-10 3:20 ` Shaohua Li 0 siblings, 1 reply; 3+ messages in thread From: Pavel Machek @ 2006-01-09 15:44 UTC (permalink / raw) To: Li, Shaohua; +Cc: ronald.mythtv, kernel list Hi! > >I wanted to write some documentation about /proc/acpi/alarm, but > >failed to make it work. I was putting machine to suspend-to-ram and > >enabled everything in /proc/acpi/wakeup, still it would not do > >anything. I even went to bios (thinkpad x32), set "RTC alarm" to > >enabled and set time there. Nothing interesting > >happened. /proc/acpi/alarm could not see most of my changes done in > >BIOS, it only cleared century or something like that. > > > >I checked that RTC readout in BIOS shows same thing as system timer. > > > >Here are my attempts: [Commands were typed one-after-another where it > >makes sense, and I left machine suspended for long enough -- timer > >should have expired] > It appears we need enable rtc driver to make alarm work. I enabled CONFIG_RTC: pavel@amd:/data/l/linux$ grep CONFIG_RTC .config CONFIG_RTC=y # CONFIG_RTC_X1205_I2C is not set pavel@amd:/data/l/linux$ ...but /proc/acpi/alarm still behaves very strangely: 2006-01-00 12:42:00 root@amd:/proc/acpi# echo '2006-01-01 12:34:56' > alarm root@amd:/proc/acpi# cat alarm 2006-01-01 12:34:56 root@amd:/proc/acpi# echo '2006-09-01 12:34:56' > alarm root@amd:/proc/acpi# cat alarm 2006-01-01 12:34:56 root@amd:/proc/acpi# echo '2006-01-09 12:34:56' > alarm root@amd:/proc/acpi# cat alarm 2006-01-09 12:34:56 root@amd:/proc/acpi# echo '2006-02-09 12:34:56' > alarm root@amd:/proc/acpi# cat alarm 2006-01-09 12:34:56 root@amd:/proc/acpi# ...why does it hate february and september? Pavel -- Thanks, Sharp! ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: /proc/acpi/alarm -- does it work or not? 2006-01-09 15:44 ` /proc/acpi/alarm -- does it work or not? Pavel Machek @ 2006-01-10 3:20 ` Shaohua Li 2006-01-15 15:13 ` Pavel Machek 0 siblings, 1 reply; 3+ messages in thread From: Shaohua Li @ 2006-01-10 3:20 UTC (permalink / raw) To: Pavel Machek; +Cc: ronald.mythtv, kernel list On Mon, 2006-01-09 at 16:44 +0100, Pavel Machek wrote: > Hi! > > > >I wanted to write some documentation about /proc/acpi/alarm, but > > >failed to make it work. I was putting machine to suspend-to-ram and > > >enabled everything in /proc/acpi/wakeup, still it would not do > > >anything. I even went to bios (thinkpad x32), set "RTC alarm" to > > >enabled and set time there. Nothing interesting > > >happened. /proc/acpi/alarm could not see most of my changes done in > > >BIOS, it only cleared century or something like that. > > > > > >I checked that RTC readout in BIOS shows same thing as system timer. > > > > > >Here are my attempts: [Commands were typed one-after-another where it > > >makes sense, and I left machine suspended for long enough -- timer > > >should have expired] > > It appears we need enable rtc driver to make alarm work. > > I enabled CONFIG_RTC: > > pavel@amd:/data/l/linux$ grep CONFIG_RTC .config > CONFIG_RTC=y > # CONFIG_RTC_X1205_I2C is not set It appears CONFIG_RTC isn't related with the issue. In my test system, if I didn't CONFIG_RTC, `date` shows wrong time, that's why I need RTC. > pavel@amd:/data/l/linux$ > > ...but /proc/acpi/alarm still behaves very strangely: > > 2006-01-00 12:42:00 > root@amd:/proc/acpi# echo '2006-01-01 12:34:56' > alarm > root@amd:/proc/acpi# cat alarm > 2006-01-01 12:34:56 > root@amd:/proc/acpi# echo '2006-09-01 12:34:56' > alarm > root@amd:/proc/acpi# cat alarm > 2006-01-01 12:34:56 > root@amd:/proc/acpi# echo '2006-01-09 12:34:56' > alarm > root@amd:/proc/acpi# cat alarm > 2006-01-09 12:34:56 > root@amd:/proc/acpi# echo '2006-02-09 12:34:56' > alarm > root@amd:/proc/acpi# cat alarm > 2006-01-09 12:34:56 > root@amd:/proc/acpi# > > ...why does it hate february and september? No. Setting day, month, century for alarm is optional. This means your system doesn't support setting month and century. But maybe we should print some infos here ... Thanks, Shaohua ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: /proc/acpi/alarm -- does it work or not? 2006-01-10 3:20 ` Shaohua Li @ 2006-01-15 15:13 ` Pavel Machek 0 siblings, 0 replies; 3+ messages in thread From: Pavel Machek @ 2006-01-15 15:13 UTC (permalink / raw) To: Shaohua Li; +Cc: ronald.mythtv, kernel list Hi! > > pavel@amd:/data/l/linux$ > > > > ...but /proc/acpi/alarm still behaves very strangely: > > > > 2006-01-00 12:42:00 > > root@amd:/proc/acpi# echo '2006-01-01 12:34:56' > alarm > > root@amd:/proc/acpi# cat alarm > > 2006-01-01 12:34:56 > > root@amd:/proc/acpi# echo '2006-09-01 12:34:56' > alarm > > root@amd:/proc/acpi# cat alarm > > 2006-01-01 12:34:56 > > root@amd:/proc/acpi# echo '2006-01-09 12:34:56' > alarm > > root@amd:/proc/acpi# cat alarm > > 2006-01-09 12:34:56 > > root@amd:/proc/acpi# echo '2006-02-09 12:34:56' > alarm > > root@amd:/proc/acpi# cat alarm > > 2006-01-09 12:34:56 > > root@amd:/proc/acpi# > > > > ...why does it hate february and september? > No. Setting day, month, century for alarm is optional. This means your > system doesn't support setting month and century. But maybe we should > print some infos here ... Yes, more info would be nice. What is "correct" way to test if systen supports day/month/year/century in alarm? Pavel -- Thanks, Sharp! ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2006-01-18 14:16 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <59D45D057E9702469E5775CBB56411F1013CF084@pdsmsx406>
2006-01-09 15:44 ` /proc/acpi/alarm -- does it work or not? Pavel Machek
2006-01-10 3:20 ` Shaohua Li
2006-01-15 15:13 ` Pavel Machek
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®