For what it's worth, here is the result of "cat /proc/driver/rtc" on my
system:

myt...@mythtv-ibex:~$ cat /proc/driver/rtc
rtc_time        : 00:03:51
rtc_date        : 2009-01-22
alrm_time       : 02:25:00
alrm_date       : ****-**-**
alarm_IRQ       : no
alrm_pending    : no
24hr            : yes
periodic_IRQ    : no
update_IRQ      : no
HPET_emulated   : yes
DST_enable      : no
periodic_freq   : 1024
batt_status     : okay

Fisslefink

On Wed, Jan 21, 2009 at 4:03 PM, Erin Simonds
<[email protected]>wrote:

> Karel,
>
> I think in your "workaround" you have effectively tried the steps that my
> script accomplishes (echo 0, echo time_t), and I'm sorry to hear that did
> not work for you.  It is possible that I got it working through some
> additional trick, which I have now forgotten.  I'll see if a fresh
> installation of Intrepid on my system works as I claimed above.
>
> Fisslefink
>
>
>
>
> On Wed, Jan 21, 2009 at 3:10 PM, Karel Marik <[email protected]> wrote:
>
>> I repeated my tests just after I installed Intrepid.  Here are my results:
>> 1) echo 0 > /sys/class/rtc/rtc0/wakealarm
>> doesn't work due to Permission denied error
>>
>> 2) I found workaround :
>> usern...@comp:~$ sudo sh -c 'echo 0 > /sys/class/rtc/rtc0/wakealarm'
>> usern...@comp:~$ sudo sh -c 'echo `date "+%s" -d "+ 5 minutes"` >
>> /sys/class/rtc/rtc0/wakealarm'
>> usern...@comp:~$ cat /sys/class/rtc/rtc0/wakealarm
>> usern...@comp:~$ cat /proc/driver/rtc
>> rtc_time        : 23:20:51
>> rtc_date        : 2009-01-21
>> alrm_time       : 23:25:29
>> alrm_date       : ****-**-21
>> alarm_IRQ       : no
>> alrm_pending    : no
>> 24hr            : yes
>> periodic_IRQ    : no
>> update_IRQ      : no
>> HPET_emulated   : no
>> DST_enable      : no
>> periodic_freq   : 1024
>> batt_status     : okay
>> usern...@comp:~$
>>
>> It is interesting "cat /sys/class/rtc/rtc0/wakealarm" gives no output.
>>
>> Computer didn't boot at specified time. Manual inspection of BIOS
>> setting revealed correctly changed time (23:25:29). However date (of
>> month) was wrong - 1.
>>
>> 3) I repeated step 2 with changed /etc/default/rcS file according to
>> advice in  http://www.mythtv.org/wiki/ACPI_Wakeup
>>
>> Same result as in (2) in BIOS. Warning! I had serious problem to boot
>> then! Finally, I had to boot using live CD and reject changes in
>> /etc/default/rcS in order to boot again.
>>
>> I am strongly interested to turn it working. So far without success. I
>> am planning to test Fisslefink's solution next time.
>>
>> Regards
>>
>> Karel
>>
>> --
>> [GUTSY]  RTC alarm does not retain setting from /proc/acpi/alarm
>> https://bugs.launchpad.net/bugs/139846
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>
>

-- 
[GUTSY]  RTC alarm does not retain setting from /proc/acpi/alarm
https://bugs.launchpad.net/bugs/139846
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to