[Bug 259149] Re: [INTREPID] /sys/class/rtc/rtc0/wakealarm is not working

2008-11-18 Thread Leann Ogasawara
So it seems this really isn't a bug. Closing. ** Changed in: linux (Ubuntu) Status: Triaged => Invalid -- [INTREPID] /sys/class/rtc/rtc0/wakealarm is not working https://bugs.launchpad.net/bugs/259149 You received this bug notification because you are a member of Ubuntu Bugs, which is su

[Bug 259149] Re: [INTREPID] /sys/class/rtc/rtc0/wakealarm is not working

2008-10-26 Thread JB5
I have also managed to get wakealarm working in Intrepid. I can confirm that, for me also, MythTV & mythwelcome required UTC times passing across i.e. time_t rather than -- hh:mm:ss as mentioned by smo above. -- [INTREPID] /sys/class/rtc/rtc0/wakea

[Bug 259149] Re: [INTREPID] /sys/class/rtc/rtc0/wakealarm is not working

2008-10-25 Thread Leann Ogasawara
Can anyone else confirm smo's comment above? Thanks. -- [INTREPID] /sys/class/rtc/rtc0/wakealarm is not working https://bugs.launchpad.net/bugs/259149 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-b

[Bug 259149] Re: [INTREPID] /sys/class/rtc/rtc0/wakealarm is not working

2008-10-04 Thread smo
Actually I got it working by reverting back to UTC hardware clock. Looks like wakealarm expects UTC time instead of localtime (which is what /proc/acpi/alarm wanted). -- [INTREPID] /sys/class/rtc/rtc0/wakealarm is not working https://bugs.launchpad.net/bugs/259149 You received this bug notificati

[Bug 259149] Re: [INTREPID] /sys/class/rtc/rtc0/wakealarm is not working

2008-10-04 Thread josesuarez1983
Well, just an update: you can disable hpet by adding hpet=disable to the kernel boot line in grub's menu.lst. I added that hpet=disable to the kernel and no luck. The PC didn't wakeup. -- [INTREPID] /sys/class/rtc/rtc0/wakealarm is not working https://bugs.launchpad.net/bugs/259149 You received

[Bug 259149] Re: [INTREPID] /sys/class/rtc/rtc0/wakealarm is not working

2008-10-04 Thread josesuarez1983
I think the problem is with the HPET_emulated flag. Check if with previous kernel HPET_emulated was true or false. For me, 2.6.24 had it HPET_emulated disabled and rtc wakeup worked OK. With 2.6.26 HPET_emulated was true and it never waked up, althought the alarm time was correct. However this

[Bug 259149] Re: [INTREPID] /sys/class/rtc/rtc0/wakealarm is not working

2008-10-03 Thread Leann Ogasawara
** Changed in: linux (Ubuntu) Importance: Undecided => Medium Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team) Status: New => Triaged -- [INTREPID] /sys/class/rtc/rtc0/wakealarm is not working https://bugs.launchpad.net/bugs/259149 You received this bug notificatio

[Bug 259149] Re: [INTREPID] /sys/class/rtc/rtc0/wakealarm is not working

2008-09-07 Thread smo
Doesn't work for me either. /proc/acpi/alarm was working fine with Hardy on the same box. -- [INTREPID] /sys/class/rtc/rtc0/wakealarm is not working https://bugs.launchpad.net/bugs/259149 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -

[Bug 259149] Re: [INTREPID] /sys/class/rtc/rtc0/wakealarm is not working

2008-08-28 Thread Leann Ogasawara
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test: 1) If you are comfortable

[Bug 259149] Re: [INTREPID] /sys/class/rtc/rtc0/wakealarm is not working

2008-08-18 Thread Brian Murray
** Changed in: linux (Ubuntu) Sourcepackagename: None => linux -- [INTREPID] /sys/class/rtc/rtc0/wakealarm is not working https://bugs.launchpad.net/bugs/259149 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list