Fisslefink, since you are the original bug reporter and confirm this is
no longer an issue, I'm marking this Fix Released. Karl, it may be the
issue you are seeing is related to a known upstream bug
http://bugzilla.kernel.org/show_bug.cgi?id=12013 . Thanks.
** Changed in: linux (Ubuntu)
S
In response to Karel's question about the date setting. If the alarm is
set, and the computer is rebooted manually, then "cat /proc/driver/rtc"
shows the following:
rtc_time: 22:18:23
rtc_date: 2009-01-22
alrm_time : 02:25:00
alrm_date : -**-**
alarm_IRQ : no
I tested wakealarm with changed BIOS setting. I set PowerUp method to
"Everyday" instead of "ByDate". Then applied same procedure:
$ sudo sh -c 'echo 0 > /sys/class/rtc/rtc0/wakealarm'
$ sudo sh -c 'echo `date "+%s" -d "+ 5 minutes"` >
/sys/class/rtc/rtc0/wakealarm'
Computer woke up after 5 minu
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
install
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
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
I had experienced this bug with Gutsy and Hardy. It started working again
with Intrepid. I currently use it all the time... I have kernel
"2.6.27-7-generic #1 SMP Tue Nov 4 19:33:20 UTC 2008 i686 GNU/Linux" My
motherboard is an Asus P4P800-E Deluxe
I use the script below, called "MythWakeSet".
Hi Karl,
Could you test the more recent 2.6.27 kernel available in Intrepid? Or
even the 2.6.28 based kernel which will be available in the upcoming
Jaunty release - http://cdimage.ubuntu.com/releases/jaunty/ . I think
they provide a newer interface to use - /sys/class/rtc/rtc0/wakealarm .
Note
I just experienced similar problem with acpi wakeup. I followed steps
found on http://www.mythtv.org/wiki/index.php/ACPI_Wakeup:
1) set alarm timestamp
$ sudo sh -c 'echo "+00-00-00 00:05:00" > /proc/acpi/alarm'
2) checked
$ cat /proc/acpi/alarm
2008-09-20 14:56:33
3) shutdown
$ sudo shutdown -h
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
Fisslefink,
Thank you for taking the time to report this bug and helping to make Ubuntu
better. You reported this bug a while ago and there hasn't been any activity in
it recently. We were wondering is this still an issue for you? Can you try with
latest Ubuntu release? Thanks in advance.
--
I was finally able to solve the problem. According to
http://www.mythtv.org/wiki/index.php/ACPI_Wakeup I had to change the
/etc/init.d/hwclock.sh as follows:
...
stop|restart|reload|force-reload)
==> ACPITIME=`cat /proc/acpi/alarm`
if [ "$HWCLOCKACCESS" != no ]
I can confirm the same bug for ASUS P5LD2 Deluxe motherboard in Ubuntu
7.10 and 8.04 alpha 3.
In 7.10, the file /proc/acpi/alarm shows 00 in place of a date in month
(like described above) after reboot.
In 8.04 alpha 3, the file is missing at all. According to mythtv wiki,
the /proc/acpi/alarm sh
A new task is open against the actively developed kernel. However,
against the linux-source-2.6.22 task, this report does not meet the
criteria for a stable release update and will be closed. You can learn
more about the stable release update process at
https://wiki.ubuntu.com/StableReleaseUpdates
Thanks for testing and providing and update. Per the kernel team's bug
policy, can you please attach the following information when running the
newer kernel:
* uname -a > uname-a.log
* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log
Please be sur
Same problem to me with Ubuntu 7.10. Before the update from Feisty
everything worked like a charm, but immediately after the update i can
write the wakeup time a thousand times to /proc/acpi/alarm, use or don't
use the poweroff - kernel, the machine sleeps forever.
@Leann:
Even the new kernel from
Hi,
Just curious if this was still an issue in the official 7.10 Gutsy
Gibbon release (kernel 2.6.22-14)? If so, the Hardy Heron kernel was
recently uploaded for testing. We'd really appreciate it if you could
try testing with this newer kernel and verify if this issue still
exists. Unfortunate
** Description changed:
Binary package hint: linux-source-2.6.22
Ubuntu version: Kubuntu Gutsy (development) ... last upgraded 9/16/2007
Kernel version: 2.6.22-11-386
Motherboard: ASUS P4P800E-Deluxe
BIOS RTC Alarm Setting: Disabled
First broken: This worked fine with Feisty an
18 matches
Mail list logo
